Open Stack

----- Original Message -----
> 
> 
> Well we probably need some backwards compat glue to keep deploying supported
> versions. More on that in the spec I'm drafting.

A spec around deploying multiple versions of the overcloud? If so, great :-)

Re: https://bugs.launchpad.net/tripleo/+bug/1330735 and deploying older 
versions of the overcloud. Trying an icehouse overcloud using the latest (fixed) 
undercloud should just work right? Assuming the stable/icehouse branches of 
tripleo-image-elements were used to build the overcloud images and same 
for tripleo-heat-templates to deploy it?

> On 21 Jun 2014 12:26, "Dan Prince" < dprince at redhat.com > wrote:
> 
> 
> On Fri, 2014-06-20 at 16:51 -0400, Charles Crouch wrote:
> > 
> > ----- Original Message -----
> > > Not a great week for TripleO CI. We had 3 different failures related to:
> > > 
> > > Nova [1]: we were using a deprecated config option
> > > Heat [2]: missing heat data obtained from the Heat CFN API
> > > Neutron [3]: a broken GRE overlay network setup
> > 
> > The last two are bugs, but is there anything tripleo can do about avoiding
> > the first one in the future?:
> 
> Yes. Reviewing and monitoring our log files would have been helpful
> here. Nova did nothing wrong... we were just plain using an old option
> which was deprecated in Icehouse.
> 
> With TripleO's upstream focus we need to maintain a balancing act and
> try to avoid using new option names until a release has been made. I
> think once the release is made however (Icehouse in this case) we should
> immediately move to drop all deprecated options and use the new
> versions. If we follow a process like this we should be safe guarded
> from this sort of failure in the future.
> 
> Dan
> 
> > e.g. reviewing a list of deprecated options and seeing when they will be
> > removed.
> > 
> > do the integrated projects have a protocol for when an option is deprecated
> > and at what point it can be removed?
> > e.g. if I make something deprecated in icehouse I can remove it in juno,
> > but if I
> > make something deprecated at the start of juno I can't remove it at the end
> > of juno?
> > 
> > > 
> > > The TripleO check jobs look to be running stable again today so if your
> > > patch had failures from earlier this week then recheck away (perhaps
> > > referencing one of these bugs if appropriate). The queue is fairly empty
> > > right now...
> > > 
> > > Thanks for all the help in tracking these down and getting things fixed.
> > > 
> > > [1] https://bugs.launchpad.net/tripleo/+bug/1292105
> > 
> > I think [1] was meant to be
> > https://bugs.launchpad.net/tripleo/+bug/1330735
> > 
> > > [2] https://bugs.launchpad.net/heat/+bug/1331720
> > > [3] https://bugs.launchpad.net/tripleo/+bug/1292105
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > 
> > 
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>