[jira] [Commented] (AURORA-1014) Client binding_helper to resolve docker label to a stable ID at create

["Jay Buffington (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AURORA-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309429#comment-14309429 ] 

Jay Buffington commented on AURORA-1014:
----------------------------------------

My understanding of what you're proposing here is to modify the client to have a binding helper that queries the docker registry to resolve a tag like "latest" to an image id like "27be2329..."

In my .aurora file I would write

{{noformat}}
Task(
    container=Docker(
        image={{docker.resolve[private.repo.example.com/myimage:latest]}}
        ...
   )
{{noformat}}

When you run ```aurora create``` the binding helper would query private.repo.example.com and resolve ```myimage:latest``` to ```myimage:27be2329...``` before the web service call was made to the scheduler.

The necessary docker registry api call is documented here:
https://docs.docker.com/reference/api/registry_api/#get-image-id-for-a-particular-tag

This is a great idea.

> Client binding_helper to resolve docker label to a stable ID at create
> ----------------------------------------------------------------------
>
>                 Key: AURORA-1014
>                 URL: https://issues.apache.org/jira/browse/AURORA-1014
>             Project: Aurora
>          Issue Type: Bug
>          Components: Client, Packaging
>            Reporter: Kevin Sweeney
>
> Follow-up from discussion on IRC:
> Some docker labels are mutable, meaning the image a task runs in could change from restart to restart even if the rest of the task config doesn't change. This breaks assumptions that make rolling updates the safe and preferred way to deploy a new Aurora job
> Add a binding helper that resolves a docker label to an immutable image identifier at create time and make it the default for the Docker helper introduced in https://reviews.apache.org/r/28920/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)