[
https://issues.apache.org/jira/browse/AURORA-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380513#comment-14380513
]
Oskar Stenman commented on AURORA-1014:
---------------------------------------
Don't forget if i do a "aurora update" with a new :latest tag set in the update.
This should update the new job with the new :tag, and still keep the rollback
working properly with the old :tag.
If you do these decisions in aurora it should also show in the deploy config of
the job in the aurora job definition if you browse it through the api or the
web-interface. (I want to know what "build" the job is running by simply
checking the running job)
> 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)
