Minutes from today's (12/04/2013) cloud WG meeting

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El Thu, 5 Dec 2013 10:22:20 -0500 (EST)
Sam Kottler <skottler at redhat.com> escribió:
> 
> 
> ----- Original Message -----
> > From: "Dennis Gilmore" <dennis at ausil.us>
> > To: cloud at lists.fedoraproject.org
> > Sent: Wednesday, December 4, 2013 6:13:40 PM
> > Subject: Re: Minutes from today's (12/04/2013) cloud WG meeting
> > 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > El Wed, 4 Dec 2013 17:39:07 -0500
> > Matthew Miller <mattdm at fedoraproject.org> escribió:
> > > On Wed, Dec 04, 2013 at 04:16:25PM -0600, Dennis Gilmore wrote:
> > > > >   * AGREED: cadence release to be monthly + trigger-based
> > > > > updates until we're more confident on automated testing
> > > > > (rbergeron)
> > > > So we are not going to be able to do this period. you will only
> > > > be able to release as Fedora itself releases.  doing periodic
> > > > updated images can be doable, but we (with Release Engineering
> > > > hat on) does not have any ability to do what you mention here.
> > > > the Best we can do is to do
> > > 
> > > So, what would it take to be able to do it?
> > 
> > Well the Fedora release Cycle is what it is. I do not think you can
> > change that. I think that some of the wording used is poorly chosen.
> > 
> > I think you are actually talking about updates images and not
> > release images. We have no way to determine how big an update set
> > is so that would be needed. something to monitor updates for
> > security bugs to trigger image creation. you need to assume we have
> > no tooling to do anything you want. so someone will need to write
> > and maintain it. you will also need to take your proposal to FESCo
> > and have it signed off as okay.
> 
> Didn't spot propose something related to monthly pushes around the
> time that Flock took place? Seems like the rebuilds could occur
> simultaneously with pushes to reduce the burden of rebuilding images.
> That being said, we are still left in a position where it increases
> rel-eng load; not really sure how to avoid that other than having a
> group of people who are willing to help out.

That was proposed, and would be an awesome trigger for an updates
image. but nothing more than hey we should change how we push out
updates has been done. The problem with Ideas is they are great but far
from implementation. we need people to help write tooling so that the
cost of things like a updates compose is not high.

Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJSoPqCAAoJEH7ltONmPFDRjS8QALo6St5BHfBLWbMZhm+A7hSE
HDaZgc03uNCUTP48fiBFVqWbQEAYBu/a6JYd4IM85VeFIDlIEgzcRdcKcKW0mFyp
zAF8XqeC/6+8Pg6f5c/KFrDyGvq84GSuGqwtsTrjG0g7nucTfAfeInjlA9aWmflw
PKFY2iQG7k4Gd+nv2//Gb60uo3OzpZvL9a6DdX0QeDPEo5W8Ygdc5yalGF/Nhd3q
nvAw718NyzlXv7MNcR5n8iPOiDRFtzzslfA5uHFSq9GPk60jj33JhldObSmGxupp
bBf0JKUkkizS5tZluS9zVKzW0PpbMDa9nBVQycG3bjsVZPadfPrZsZcqb/uWRetA
XfluON55xkeYwEvsjXEfj1btIkWZkPaKdljF8oH88XCCBVEE36HJiAjt78yqVJRo
QakUgv0V3rp6/ykAin8NO1gqKnWQkD6v38OsSh2jAlHleh4jZASyOiSZxXbh1nTK
efUdPAMQdjgQYbagn7ugCdXalLHAijn9+paA48+EvAQoLPFkuiWRWQENoOf2HaPM
uAhb0JGOTjoSEoZ+RGZ2FjILLjTjzmHHkgHl4UN7iTfNaDTzlhCD0QucvSdeLU9C
6z+Ld9/cVISvwR0mC1K2Y9f1rOC+Wsuk9jf8xhkmP9kwZkikzl7DLsfsrcdqZKhq
20C34BxSuNAbVMELaY1I
=F948
-----END PGP SIGNATURE-----