Skip to content
This repository has been archived by the owner on Aug 14, 2020. It is now read-only.

appc push specification proposal #418

Open
josephschorr opened this issue May 28, 2015 · 3 comments
Open

appc push specification proposal #418

josephschorr opened this issue May 28, 2015 · 3 comments
Milestone

Comments

@josephschorr
Copy link

Hi everyone,

I've started a proposal for pushing ACIs. Please see and comment here:
https://docs.google.com/document/d/1-zvY2tSGYOT853eGJMWkPet4yRZyP0LBgjmFjgE1-_I/edit?usp=sharing

@jonboulle jonboulle modified the milestone: v0.7.0 Jun 10, 2015
@jonboulle
Copy link
Contributor

Capturing OOB discussion - we should consider how to deal with image dependencies (layers).

/cc @jzelinskie @klizhentas @derekchiang

@blalor
Copy link
Contributor

blalor commented Oct 12, 2015

Why does appc need this functionality? I haven't seen the rationalization in the doc nor here.

@jonboulle
Copy link
Contributor

@blalor The simplest argument would be one of symmetry - if we describe a means for discovery retrieval it would also be good to have the inverse. This helps close the loop for distributing appc images (but still without prescribing means of transport, etc).

At a more practical level, we need something that works for Quay -- but we think it can be more generally useful.

Having said that, this is by no means a finished discussion. Would love to hear your viewpoint.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants