Actions
Idea #9618
closed
[Crunch2] [API] Reject ContainerRequests that don't specify valid ram constraint
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
API
Target version:
Start date:
08/03/2016
Due date:
Story points:
0.5
Release:
Release relationship:
Auto
Description
The runtime_constraints of a ContainerRequest must include a ram field. ram is a number of bytes, so it must be a positive integer. The API server must validate this on every create and update of a ContainerRequest when its state is Committed. If a request tries to set ram to an unacceptable value, the server must reject the request with HTTP error code 422, and the response JSON should include an error message close to "runtime_constraints ram must be a positive integer."
Updated by Brett Smith over 8 years ago
- Target version set to Arvados Future Sprints
Updated by Brett Smith over 8 years ago
- Subject changed from [Crunch2] [API] Reject ContainerRequests that don't specify ram when no default is set to [Crunch2] [API] Reject ContainerRequests that don't specify valid ram constraint
- Description updated (diff)
- Category set to API
Updated by Lucas Di Pentima over 8 years ago
- Assigned To set to Lucas Di Pentima
- Target version changed from Arvados Future Sprints to 2016-08-03 sprint
Updated by Lucas Di Pentima over 8 years ago
- Status changed from New to In Progress
b7f8614e177be3fb989f5ddf17ba474492d19af1
Ready for review
Updated by Lucas Di Pentima over 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:8fc5b6595fd1d544b5812d0807e9747c6eab5f8d.
Actions