Project

General

Profile

Actions

Feature #8470

closed

[Crunch2] [API] Use exact values for runtime_constraints and mounts in Container records

Added by Peter Amstutz over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Crunch
Target version:
Story points:
1.0
Release:
Release relationship:
Auto

Description

Currently, the API satisfies a Container Request by copying its attributes into a new Container.

However, a Container record is meant to specify a container unambiguously, while a Container Request describes a set of acceptable Containers (e.g., "between 1 and 2 GB of RAM") and uses identifiers like UUIDs and git branch names, which resolve to different values at different times.

New behavior:
  • If cr.container_image is not already a collection PDH, resolve it (as a docker tag or a collection UUID) to a PDH. Use the resulting PDH as the container_image for the new Container.
  • If any entries in cr.mounts specify collection UUIDs, look them up and specify them as PDH instead in the new Container.
  • If any entries in runtime_constraints specify ranges (e.g., "vcpus":[2,null] signifying "at least two cores"), use the minimum (2 in this case) as the value for the corresponding key in the new Container's runtime_constraints.

Subtasks 4 (0 open4 closed)

Task #9477: Use numbers for runtime constraintsResolvedTom Clegg06/23/2016Actions
Task #9478: Resolve collections to PDHResolvedTom Clegg06/23/2016Actions
Task #9479: Resolve docker image tag to PDHResolvedTom Clegg06/24/2016Actions
Task #9480: Review 8470-resolve-container-reqResolvedRadhika Chippada06/27/2016Actions

Related issues

Related to Arvados - Idea #9273: [Crunch2] Do not satisfy container requests that use non-content-address names for docker images, git commits, or collectionsClosedActions
Actions

Also available in: Atom PDF