Bug #7695

[API] Accept collection UUID as a job's docker_image constraint

Added by Brett Smith almost 4 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
Start date:
10/29/2015
Due date:
% Done:

0%

Estimated time:
Story points:
0.5

Description

This behavior should work identically to specifying a collection's portable data hash: if the user can read the collection, and it contains a single file that looks like a Docker image, record the Docker image's content address as the job's docker_image_locator.

Update the Collection.find_all_for_docker_image method to recognize and accept collection UUIDs, just like it recognizes collection PDHs. Apply the same conditions to accepting those collections: look at the manifest text, and confirm it contains a single .tar file that looks like a Docker image.

Update the docker_image documentation in /doc/user/topic/arv-docker.html and /doc/api/schema/Job.html to note that collection UUIDs are accepted.

Associated revisions

Revision d70d9b25 (diff)
Added by Brett Smith almost 4 years ago

7695: Docs reflect that docker_image can't be a collection UUID.

We intended to allow this, but it's not actually implemented. Update
the docs for now. We'll add the functionality in refs #7695.

History

#1 Updated by Brett Smith almost 4 years ago

  • Description updated (diff)

#2 Updated by Brett Smith almost 4 years ago

  • Description updated (diff)
  • Story points set to 0.5

#3 Updated by Brett Smith over 3 years ago

  • Target version set to Arvados Future Sprints

#4 Updated by Jiayong Li over 3 years ago

  • Target version changed from Arvados Future Sprints to 2016-03-30 sprint

#5 Updated by Radhika Chippada over 3 years ago

  • Target version changed from 2016-03-30 sprint to Arvados Future Sprints

Also available in: Atom PDF