Feature #14197
[controller] Federated container requests
Start date:
09/21/2018
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
Story points:
2.0
Release:
Release relationship:
Auto
Description
arvados-controller routes GET, PUT or POST operation on container requests to remote clusters based on the cluster id in the uuid (GET/PUT) or cluster_id request parameter (POST).
Must also be able to GET remote container records as well.
Subtasks
Related issues
Associated revisions
History
#1
Updated by Peter Amstutz about 1 year ago
- Status changed from New to In Progress
#2
Updated by Peter Amstutz about 1 year ago
- Status changed from In Progress to New
#3
Updated by Peter Amstutz about 1 year ago
- Description updated (diff)
#4
Updated by Peter Amstutz about 1 year ago
- Related to Feature #13619: [Controller] Federated multi object retrieval added
#5
Updated by Peter Amstutz about 1 year ago
- Description updated (diff)
#6
Updated by Peter Amstutz about 1 year ago
- Description updated (diff)
#7
Updated by Tom Morris about 1 year ago
- Story points set to 2.0
#8
Updated by Tom Morris about 1 year ago
- Target version changed from To Be Groomed to Arvados Future Sprints
#9
Updated by Tom Morris about 1 year ago
- Target version changed from Arvados Future Sprints to 2018-10-03 Sprint
#10
Updated by Peter Amstutz about 1 year ago
- Assigned To set to Peter Amstutz
#11
Updated by Peter Amstutz about 1 year ago
- Status changed from New to In Progress
#12
Updated by Peter Amstutz about 1 year ago
14197-federated-containers @ 1dd4997ebfe9e1bce4073aed9abb37f89ae90845
Support GET, PUT/PATCH and POST (object create) for containers and container requests.
https://ci.curoverse.com/view/Developer/job/developer-run-tests/902/
#13
Updated by Lucas Di Pentima about 1 year ago
- On the remote container request creation tests, I think it would be convenient to also assert that the created object’s uuid match with the desired cluster prefix, to confirm that the object was created on the correct cluster.
- Should we also test POSTs on unknown cluster_id prefixes?
#14
Updated by Peter Amstutz about 1 year ago
Lucas Di Pentima wrote:
- On the remote container request creation tests, I think it would be convenient to also assert that the created object’s uuid match with the desired cluster prefix, to confirm that the object was created on the correct cluster.
Added check to existing create requests.
- Should we also test POSTs on unknown cluster_id prefixes?
Added test.
14197-federated-containers @ 959fc42ba11fbe4f803511ffcb8945bae537ff21
https://ci.curoverse.com/view/Developer/job/developer-run-tests/903/
#15
Updated by Lucas Di Pentima about 1 year ago
This LGTM, please merge. Thanks!
#16
Updated by Peter Amstutz about 1 year ago
- Status changed from In Progress to Resolved
#17
Updated by Tom Morris about 1 year ago
- Release set to 14
Merge branch '14197-federated-containers' refs #14197
Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <pamstutz@veritasgenetics.com>