Open wking opened 7 years ago
I recommend we move the layout spec out of image-spec and into this project...
Layout is part of image, branch 1 seems to only explain contents inside image package, but not mentioned anything about discovery mechanism. I think it is much more helpful to discovery by landing it in image-spec
master. With it inside image-spec
, discovery can go on depended on a canonical protocol
template. If it is just landed in discovery, we have only internal canonicalization.
And, I think it is very possible and soon to land branch 1. If it is in this project, it will be so long time to be landed to OCI canonicalization.
On Mon, Sep 18, 2017 at 10:09:51PM -0700, xiekeyang wrote:
And, I think it is very possible and soon to land branch [1].
I don't think there's any chance of that branch landing in image-spec before the refEngines and casEngines definitions are part of an OCI Project.
And I'd rather avoid a dependency cycle. If there is a separate discovery Project, it should depend on image-spec, and not image-spec component should depend on any discovery components.
I don't think there's any chance of that branch landing in image-spec before the refEngines and casEngines definitions are part of an OCI Project.
If image-spec
is hard to accept it currently, it is no problem to land it to this project.
image-spec's image-layout is extremely similar to a special case of ref-engine discovery. I've stubbed out an image-spec branch to demonstrate this, which makes for a more compact and powerful layout spec (although it now depends on the additional ref-engine discovery wording from this repo). If this project, or something like it, ends up in an OCI Project, I recommend we move the layout spec out of image-spec and into this project (unless this project ends up being merged with image-spec).
One of the examples of increased power is the ability to shard the blob store (opencontainers/image-spec#449).