On Tue, Jan 17, 2017 at 10:42:18AM -0500, Emilien Macchi wrote: > On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel <mbul...@redhat.com> wrote: > > Hi Adriano > > > > On 01/17/2017 03:05 PM, Adriano Petrich wrote: > > > > So I want to make a backwards compatibility job upstream so from last scrum > > I got the feeling that we should not be adding more stuff to the > > experimental jobs due to lack of resources (and large queues) > > > > What kind of "test" do you want to add ? > > I ask because since few days we have upstream an upgrade job that does: > > master UC -> deploying a Newton OC with Newton OC + tht stable/newton -> > > then upgrade the OC to master with tht master branch. > > It's sounds like a "small backward compatibility" validation, but I'm not > > sure if it's cover what you need. > > While I understand what is the idea, I don't see the use case. > In which case you want to deploy a old version of overcloud by using a > recent undercloud? > Why don't use deploy a stable undercloud to deploy a stable overcloud?
For development & test usage it's actually really useful - I can deploy any version overcloud locally for testing (any kind of overcloud bugfixes etc, not only testing upgrades), and it's even possible to deploy two overclouds at once, with different versions, to easily do comparative testing. This is something we get "for free" because TripleO is using Heat/Glance etc which provide stable interfaces, and although I accept it's something of a specialist use-case, I think it is a valid one. Steve __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
