Skip to content
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.

Make the HTTP API use the same restrictions as the scheduler #33

Closed
dgrnbrg opened this issue Sep 18, 2015 · 0 comments
Closed

Make the HTTP API use the same restrictions as the scheduler #33

dgrnbrg opened this issue Sep 18, 2015 · 0 comments
Milestone
Scheduler Robustness

Comments

@dgrnbrg
Copy link
Contributor

dgrnbrg commented Sep 18, 2015

Currently, the API hardcodes 32 CPUs and 200GB ram for blocking HTTP job submission. The API should instead use the same scheduler constraints that are provided as :task-constraints.
@dgrnbrg dgrnbrg added this to the Robustification milestone Sep 18, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Scheduler Robustness
Development

No branches or pull requests
1 participant
@dgrnbrg