On Mon, 18.05.15 19:44, Matthew Miller (mattdm@xxxxxxxxxxxxxxxxx) wrote: > FESCo Ticket #1427 <https://fedorahosted.org/fesco/ticket/1427> > formalizes the list of deliverables for each Fedora release. Cool. > > Let's go a step beyond this and make a machine-readable list, at least > of image-based deliverables. One approach would be to use using Ubuntu's simplestreams > format, documented at > <http://bazaar.launchpad.net/~smoser/simplestreams/trunk/view/head:/doc/README.> > > A second option would be the index.asc as used by virt-builder: > <https://fedorahosted.org/rel-eng/ticket/5805> > > That way, we'd have a standardized way for applications to find and > download/launch/whatever various Fedora images. This is a definite need > (see https://fedorahosted.org/cloud/ticket/93) and rather than > inventing a new wheel, maybe we could see if we could pound one of > these into shape. There's also the ACI discovery stuff: https://github.com/appc/spec/blob/master/SPEC.md#app-container-image-discovery Doesn't really apply to non-ACI images right now, but the concepts in it are a bit nicer I think then the alternatives (i.e. the fact that it renders the image names into URL via a fixed template, and that it uses <meta> tags for exposing this information is pretty nice). Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct