[openstack-dev] [all][qa] Migrating devstack jobs to Bionic (Ubuntu LTS 18.04)

Ghanshyam Mann gmann at ghanshyammann.com
Thu Nov 22 06:26:52 UTC 2018

Hi All,

Let's go with approach 1 means migrating the Devstack and Tempest base jobs to Bionic. This will move most of the jobs to Bionic.

We have two patches up which move all Devstack and Tempest jobs to Bionic and it's working fine. 

1. All DevStack jobs to Bionic - https://review.openstack.org/#/c/610977/
     - This will move devstack-minimal, devstack, devstack-ipv6, devstack-multinode jobs to bionic only for master which means it will be stein onwards. All these jobs will use 
        xenial till stable/rocky. 

2. All Tempest base jobs (except stable branches job running on master) to Bionic - https://review.openstack.org/#/c/618169/
     - This will move devstack-tempest, tempest-all, devstack-tempest-ipv6, tempest-full, tempest-full-py3, tempest-multinode-full, tempest-slow jobs to bionic. 
Note- Even Tempest is branchless and these tempest jobs have been moved to Bionic, they will still use xenial for all stable branches(till stable/rocky) testing. with zuulv3 magic and devstack base jobs nodeset for stable branch (xenial) and master (stein onwards -bionic) will take care of that. Tested on [1] and working fine. Thanks corvus and clarkb for guiding to this optimized way. 

3. Legacy jobs are not migrated to bionic. They should get migrated to Bionic while they are moved to zuulv3 native. So if your projects have many legacy jobs then, they will still run on xenial. 

Any job inherits from those base jobs will behave the same way (running on bionic from stein onwards and xenial till stable/rocky). 

I am writing the plan and next action item to complete this migration activity:

1 Project teams:  need to test their jobs 1. which are inherited from devstack/tempest base jobs and should pass as it is 2. Any zuulv3 jobs not using devstack/tempest base job required to migrate to use bionic (Devstack patch provide the bionic nodeset) and test it.  Start writing the results on etherpad[2]

2 QA team will merge the above patches by 10th Dec so that we can find and fix any issues as early and to avoid the same during release time. 

Let's finish the pre-testing till 10th Dec and then merge the bionic migration patches. 

[1] https://review.openstack.org/#/c/618181/  https://review.openstack.org/#/c/618176/
[2] https://etherpad.openstack.org/p/devstack-bionic


 ---- On Wed, 07 Nov 2018 08:45:45 +0900 Doug Hellmann <doug at doughellmann.com> wrote ---- 
 > Ghanshyam Mann <gmann at ghanshyammann.com> writes: 
 > >  ---- On Wed, 07 Nov 2018 06:51:32 +0900 Slawomir Kaplonski <skaplons at redhat.com> wrote ----  
 > >  > Hi, 
 > >  >  
 > >  > > Wiadomość napisana przez Jeremy Stanley <fungi at yuggoth.org> w dniu 06.11.2018, o godz. 22:25: 
 > >  > >  
 > >  > > On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote: 
 > >  > > [...] 
 > >  > >> also add jobs like "devstack-xenial" and "tempest-full-xenial" 
 > >  > >> which projects can use still for some time if their job on Bionic 
 > >  > >> would be broken now? 
 > >  > > [...] 
 > >  > >  
 > >  > > That opens the door to piecemeal migration, which (as we similarly 
 > >  > > saw during the Trusty to Xenial switch) will inevitably lead to 
 > >  > > projects who no longer gate on Xenial being unable to integration 
 > >  > > test against projects who don't yet support Bionic. At the same 
 > >  > > time, projects which have switched to Bionic will start merging 
 > >  > > changes which only work on Bionic without realizing it, so that 
 > >  > > projects which test on Xenial can't use them. In short, you'll be 
 > >  > > broken either way. On top of that, you can end up with projects that 
 > >  > > don't get around to switching completely before release comes, and 
 > >  > > then they're stuck having to manage a test platform transition on a 
 > >  > > stable branch. 
 > >  >  
 > >  > I understand Your point here but will option 2) from first email lead to the same issues then? 
 > > 
 > > seems so. approach 1 is less risky for such integrated testing issues and requires less work. In approach 1, we can coordinate the base job migration with project side testing with bionic. 
 > > 
 > > -gmann 
 > I like the approach of updating the devstack jobs to move everything to 
 > Bionic at one time because it sounds like it presents less risk of us 
 > ending up with something that looks like it works together but doesn't 
 > actually because it's tested on a different platform, as well as being 
 > less likely to cause us to have to do major porting work in stable 
 > branches after the release. 
 > We'll need to take the same approach when updating the version of Python 
 > 3 used inside of devstack. 
 > Doug 

More information about the openstack-discuss mailing list