Mailing-List: contact issues-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Date: Fri, 6 Feb 2015 19:18:34 +0000 (UTC)
From: "Kevin Sweeney (JIRA)" <jira@apache.org>
To: issues@aurora.incubator.apache.org
Message-ID: <JIRA.12767535.1421265281000.282448.1423250314980@Atlassian.JIRA>
In-Reply-To: <JIRA.12767535.1421265281000@Atlassian.JIRA>
References: <JIRA.12767535.1421265281000@Atlassian.JIRA>
 <JIRA.12767535.1421265281669@arcas>
Subject: [jira] [Commented] (AURORA-1014) Client binding_helper to resolve
 docker label to a stable ID at create
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kevin Sweeney commented on AURORA-1014:
---------------------------------------

[~jaybuff] yes, that's exactly my suggestion

> 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)