[jira] [Updated] (MESOS-2968) Implement Shared Copy backend
[ https://issues.apache.org/jira/browse/MESOS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Massenzio updated MESOS-2968: --- Sprint: (was: Mesosphere Sprint 14) > Implement Shared Copy backend > - > > Key: MESOS-2968 > URL: https://issues.apache.org/jira/browse/MESOS-2968 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Timothy Chen >Assignee: Timothy Chen > Labels: mesosphere > > Currently Appc and Docker both implemented its own copy backend, but most of > the logic is the same where the input is just a image name with its > dependencies. > We can refactor both so that we just have one implementation that is shared > between both provisioners, so appc and docker can reuse the shared copy > backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2968) Implement Shared Copy backend
[ https://issues.apache.org/jira/browse/MESOS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-2968: Sprint: Mesosphere Sprint 14 > Implement Shared Copy backend > - > > Key: MESOS-2968 > URL: https://issues.apache.org/jira/browse/MESOS-2968 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Timothy Chen >Assignee: Timothy Chen > Labels: mesosphere > > Currently Appc and Docker both implemented its own copy backend, but most of > the logic is the same where the input is just a image name with its > dependencies. > We can refactor both so that we just have one implementation that is shared > between both provisioners, so appc and docker can reuse the shared copy > backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2968) Implement Shared Copy backend
[ https://issues.apache.org/jira/browse/MESOS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-2968: Labels: mesosphere (was: ) > Implement Shared Copy backend > - > > Key: MESOS-2968 > URL: https://issues.apache.org/jira/browse/MESOS-2968 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Timothy Chen >Assignee: Timothy Chen > Labels: mesosphere > > Currently Appc and Docker both implemented its own copy backend, but most of > the logic is the same where the input is just a image name with its > dependencies. > We can refactor both so that we just have one implementation that is shared > between both provisioners, so appc and docker can reuse the shared copy > backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2968) Implement Shared Copy backend
[ https://issues.apache.org/jira/browse/MESOS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-2968: Description: Currently Appc and Docker both implemented its own copy backend, but most of the logic is the same where the input is just a image name with its dependencies. We can refactor both so that we just have one implementation that is shared between both provisioners, so appc and docker can reuse the shared copy backend. was: Currently Appc and Docker both implemented its own copy backend, but most of the logic is the same. We can refactor both so that we just have one implementation that is shared. > Implement Shared Copy backend > - > > Key: MESOS-2968 > URL: https://issues.apache.org/jira/browse/MESOS-2968 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Timothy Chen >Assignee: Timothy Chen > > Currently Appc and Docker both implemented its own copy backend, but most of > the logic is the same where the input is just a image name with its > dependencies. > We can refactor both so that we just have one implementation that is shared > between both provisioners, so appc and docker can reuse the shared copy > backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2968) Implement Shared Copy backend
[ https://issues.apache.org/jira/browse/MESOS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-2968: Component/s: containerization > Implement Shared Copy backend > - > > Key: MESOS-2968 > URL: https://issues.apache.org/jira/browse/MESOS-2968 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Timothy Chen >Assignee: Timothy Chen > > Currently Appc and Docker both implemented its own copy backend, but most of > the logic is the same where the input is just a image name with its > dependencies. > We can refactor both so that we just have one implementation that is shared > between both provisioners, so appc and docker can reuse the shared copy > backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2968) Implement Shared Copy backend
[ https://issues.apache.org/jira/browse/MESOS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-2968: Story Points: 3 > Implement Shared Copy backend > - > > Key: MESOS-2968 > URL: https://issues.apache.org/jira/browse/MESOS-2968 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen >Assignee: Timothy Chen > > Currently Appc and Docker both implemented its own copy backend, but most of > the logic is the same. > We can refactor both so that we just have one implementation that is shared. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2968) Implement Shared Copy backend
[ https://issues.apache.org/jira/browse/MESOS-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-2968: Description: Currently Appc and Docker both implemented its own copy backend, but most of the logic is the same. We can refactor both so that we just have one implementation that is shared. > Implement Shared Copy backend > - > > Key: MESOS-2968 > URL: https://issues.apache.org/jira/browse/MESOS-2968 > Project: Mesos > Issue Type: Improvement >Reporter: Timothy Chen >Assignee: Timothy Chen > > Currently Appc and Docker both implemented its own copy backend, but most of > the logic is the same. > We can refactor both so that we just have one implementation that is shared. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
