Re: simplestreams json or index.asc for deliverables in the new list-of-deliverables?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 18, 2015 at 07:44:37PM -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.>

This could really do with an example.  FWIW several can be found here:

https://cloud-images.ubuntu.com/releases/streams/v1/

> A second option would be the index.asc as used by virt-builder:
> <https://fedorahosted.org/rel-eng/ticket/5805>

Example:

http://libguestfs.org/download/builder/index.asc

I agree it is long past time that we had a mechanical way to describe
the various cloud and other images we are shipping.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux