[opensuse-cloud] Branching Grizzly
Hello fellow stackers, although the official Grizzly release is still some weeks ahead, we should branch Cloud:OpenStack:Master into Cloud:OpenStack:Grizzly in order to reduce the amount of breakage we have the fix every week. Branching (speak copypac'ing) effectively freezes all dependencies contrary to our rolling-release master branch. This alone reduces fallout. Currently, OpenStack compoment version upgrades are commited directly into C:OS:Master for fast turnaround and development times. Contrarily, Cloud:OpenStack:Grizzly is a staging branch and automated updates happen first in Cloud:OpenStack:Grizzly:Staging and are only forwarded to C:OS:Grizzly when unit tests pass. This should help or work on Chef cookbooks, since they can start using C:OS:G as a more stable basis. In order to keep C:OS:Master in sync, I would add a cronjob that periodically copypac's changed in C:OS:G back until the Grizzly release really happened. This way both OBS projects are kept in sync. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/15/2013 10:11 AM, Sascha Peilicke wrote:
Hello fellow stackers,
although the official Grizzly release is still some weeks ahead, we should branch Cloud:OpenStack:Master into Cloud:OpenStack:Grizzly in order to reduce the amount of breakage we have the fix every week. Branching (speak copypac'ing) effectively freezes all dependencies contrary to our rolling-release master branch. This alone reduces fallout. Currently, OpenStack compoment version upgrades are commited directly into C:OS:Master for fast turnaround and development times. Contrarily, Cloud:OpenStack:Grizzly is a staging branch and automated updates happen first in Cloud:OpenStack:Grizzly:Staging and are only forwarded to C:OS:Grizzly when unit tests pass. This should help or work on Chef cookbooks, since they can start using C:OS:G as a more stable basis.
In order to keep C:OS:Master in sync, I would add a cronjob that periodically copypac's changed in C:OS:G back until the Grizzly release really happened. This way both OBS projects are kept in sync.
Maybe I should add that this mostly helps to provide a more stable Grizzly repository which cookbooks and tests can be written against. It won't necessarily reduce the effort to fix Grizzly :-) -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Hello Sasche. Shouldn't we first make all packages usable? At the moment there are at least issues in openstack-quantum and I think openstack-ceilometer, openstack-cinder and openstack-heat will also have issues. I have not tested them yet. Christian. -- Christian Berendt Cloud Computing Solution Architect Tel.: +49-171-5542175 Mail: berendt@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/15/2013 11:02 AM, Christian Berendt wrote:
Hello Sasche.
Shouldn't we first make all packages usable? At the moment there are at least issues in openstack-quantum and I think openstack-ceilometer, openstack-cinder and openstack-heat will also have issues. I have not tested them yet.
Right, the posting may have been a bit premature, we're ATM (internally) discussing various options to have a more stable Grizzly without breaking the development model of Cloud:OpenStack:Master much. It seems like we will settle with updating packages there less frequently (i.e. only weekly) and set fixed revisions for all linked packages (i.e. python dependencies and co). I'll keep the list posted. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/15/2013 11:12 AM, Sascha Peilicke wrote:
Right, the posting may have been a bit premature, we're ATM (internally) discussing various options to have a more stable Grizzly without breaking the development model of Cloud:OpenStack:Master much.
Can you please involve us in such discussions in the future? I think it's a good idea to conduct all discussions regarding C:O on this mailinglist. I don't understand why this is an internally discussion at the moment. Christian. -- Christian Berendt Cloud Computing Solution Architect Tel.: +49-171-5542175 Mail: berendt@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/15/2013 11:18 AM, Christian Berendt wrote:
On 03/15/2013 11:12 AM, Sascha Peilicke wrote:
Right, the posting may have been a bit premature, we're ATM (internally) discussing various options to have a more stable Grizzly without breaking the development model of Cloud:OpenStack:Master much.
Can you please involve us in such discussions in the future?
I think it's a good idea to conduct all discussions regarding C:O on this mailinglist. I don't understand why this is an internally discussion at the moment.
This just sparked discussions in an internal irc channel, but you are absolutely right. For this very reason we have the list and the #opensuse-cloud channel which we all will use for such matters in the future. We just have to get used to the new channel yet, but we're getting there. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
Le vendredi 15 mars 2013, à 11:12 +0100, Sascha Peilicke a écrit :
On 03/15/2013 11:02 AM, Christian Berendt wrote:
Hello Sasche.
Shouldn't we first make all packages usable? At the moment there are at least issues in openstack-quantum and I think openstack-ceilometer, openstack-cinder and openstack-heat will also have issues. I have not tested them yet.
Right, the posting may have been a bit premature, we're ATM (internally) discussing various options to have a more stable Grizzly without breaking the development model of Cloud:OpenStack:Master much. It seems like we will settle with updating packages there less frequently (i.e. only weekly) and set fixed revisions for all linked packages (i.e. python dependencies and co). I'll keep the list posted.
Yeah, I think what we care about is making sure that we have Grizzly packages that don't break every day. That was the case recently because the trackupstream jenkins job was configured to run daily; it got fixed to run weekly now (thanks Daniel!). So it should help. It seems people prefer to stay with C:O:M for now, so that's definitely an option on the table. We might also look at other things we can do to help stabilize C:O:M in that case (Dirk was talking about freezing the python packages, instead of blindly following what's in d:l:p, iirc) Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
On 03/15/2013 11:59 AM, Vincent Untz wrote:
Le vendredi 15 mars 2013, à 11:12 +0100, Sascha Peilicke a écrit :
On 03/15/2013 11:02 AM, Christian Berendt wrote:
Hello Sasche.
Shouldn't we first make all packages usable? At the moment there are at least issues in openstack-quantum and I think openstack-ceilometer, openstack-cinder and openstack-heat will also have issues. I have not tested them yet.
Right, the posting may have been a bit premature, we're ATM (internally) discussing various options to have a more stable Grizzly without breaking the development model of Cloud:OpenStack:Master much. It seems like we will settle with updating packages there less frequently (i.e. only weekly) and set fixed revisions for all linked packages (i.e. python dependencies and co). I'll keep the list posted.
Yeah, I think what we care about is making sure that we have Grizzly packages that don't break every day. That was the case recently because the trackupstream jenkins job was configured to run daily; it got fixed to run weekly now (thanks Daniel!). So it should help.
It seems people prefer to stay with C:O:M for now, so that's definitely an option on the table. We might also look at other things we can do to help stabilize C:O:M in that case (Dirk was talking about freezing the python packages, instead of blindly following what's in d:l:p, iirc)
While following devel:languages:python (d:l:p) was ok as long as Grizzly development was open, we now have set a fixed revision on all python package links to d:l:p. This complements some fixed revisions we already had previously (i.e. Django-1.4 and jsonschema-0.7). Of course we can still bump particular packages when there is demand. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
participants (3)
-
Christian Berendt -
Sascha Peilicke -
Vincent Untz