Story #9618

[Crunch2] [API] Reject ContainerRequests that don't specify valid ram constraint

Added by Brett Smith almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
API
Target version:
Start date:
08/03/2016
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
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."


Subtasks

Task #9643: ReviewClosedRadhika Chippada

Associated revisions

Revision 8fc5b659
Added by Lucas Di Pentima almost 5 years ago

Merge branch '9617-reject-container-reqs-without-vcpus'

9617, 9618: Require positive integers on both 'vcpus' and 'ram' runtime constraints when a container request is committed. Closes #9617, #9618

Revision ac4bbb86
Added by Lucas Di Pentima almost 5 years ago

Merge branch '9617-reject-container-reqs-without-vcpus'

9617, 9618: Added runtime constraints to fixtures.

refs #9617, #9618

History

#1 Updated by Brett Smith almost 5 years ago

  • Target version set to Arvados Future Sprints

#2 Updated by Brett Smith almost 5 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

#3 Updated by Brett Smith almost 5 years ago

  • Description updated (diff)

#4 Updated by Brett Smith almost 5 years ago

  • Story points set to 0.5

#5 Updated by Lucas Di Pentima almost 5 years ago

  • Assigned To set to Lucas Di Pentima
  • Target version changed from Arvados Future Sprints to 2016-08-03 sprint

#6 Updated by Lucas Di Pentima almost 5 years ago

  • Status changed from New to In Progress

#7 Updated by Lucas Di Pentima almost 5 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset arvados|commit:8fc5b6595fd1d544b5812d0807e9747c6eab5f8d.

Also available in: Atom PDF