On 18/05/15 19:44 -0400, Matthew Miller 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.
Also, I'm wondering if this kind of image base deliveries could facilitate a more automated push to the docker-official[0] images (this is for `docker pull fedora` images). Presently this is an _overly_ manual process, which involves loosing git history, checking tarballs of rootfs into git, etc [1]. Most of this difficulty is imposed by the docker library team's process. Though surely they'll be amendable to opening the process to allow for pulling in an image produced by rel-eng (ideally automated per errata involved in the image's components). Main concern from upstream is this automation still needs a bit of review, like what all is included by default (i.e. systemd) and that it still smoke tests. Thoughts? vb [0] https://github.com/docker-library/official-images [1] https://github.com/fedora-cloud/docker-brew-fedora
pgpazn1ZrG6cq.pgp
Description: PGP signature
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
