Open Stack

 ---- On Tue, 26 Apr 2022 19:15:41 -0500 Sean Mooney <smooney at redhat.com> wrote ----
 > On Tue, 2022-04-26 at 18:43 -0500, Ghanshyam Mann wrote:
 > >  ---- On Tue, 26 Apr 2022 18:24:49 -0500 Jeremy Stanley <fungi at yuggoth.org> wrote ----
 > >  > On 2022-04-26 17:46:14 -0500 (-0500), Ghanshyam Mann wrote:
 > >  > > As you know, in zed cycle we are targeting centos-9-stream in
 > >  > > testing runtime[1] and dropping the py3.6 support.
 > >  > [...]
 > >  > 
 > >  > Just a reminder, RHEL 9 is still only in beta and I've seen no
 > >  > indication it will necessarily be released by September, so there's
 > >  > every chance Zed will not be usable on RHEL at release.
 > > 
 > at least from a redhat prodct perspecive redhat does not suppport installing upstream
 > openstack on rhel so those choosign to install openstack on rhel out side of our productised version
 > woudl be doing so without support form redhat.
 > 
 > as such i dont think the status of rhel 9 is really a concern here.
 > 
 > redhat is currently workingon our next major version of redhat's openstack plathform (osp 17) which will be based on rhel 9
 > and will be relased before the zed cycle completes. it will not be based on zed, zed will likely form the basis of osp(18)
 > which will not be relased this year.
 > 
 > from a rhel 8 perspective python 3.8 was never intended for production deploymetn on python 3.6 was fully productised
 > and other interperters were only provdied for development and testing but 3.6 was the only fully supproted prodcution runtime.
 > >  I know that
 > >  > came up as a reason to keep 3.6 testing the last time we tried to
 > >  > remove it (for Yoga), so figure it's worth pointing out again.
 > > 
 > > Yes, that is a separate discussion and we already discussed it a lot about
 > > dropping py3.6 in Yoga cycle. We said that time that we would remove the
 > > support in Zed cycle and so does testing runtime is defined and updated
 > > on ML also. I did not see any objection to that at least during these two months
 > > we dropped the testing.
 > > 
 > > This discussion is if we want to continue test the centos-8-stream even we dropped
 > > the py3.6 support which can be done with python 3.8.
 > 
 > i really dont think that adds sginifcant value.
 > 
 > if we were to look at redhat downstream plathform then stable wallaby and zed will both be run on python 3.9 on rhel 9.x
 > testing with 3.8 wont align with what will be productised. so i think it woudl be better to focus on testign rdo wtih centos 9 stream only
 > so for master/zed rather then investign effort into 3.8
 > 
 > for what its worth i think centos 8 with 3.8 actully does work today, im pretty sure i have deploy with that combination in the past
 > i just dont really see that addign a lot of vaule vs ruing a centos 9 stream job with 3.9

Agree, that is why in QA we decided to drop the c8s testing and more concentrate on c9s testing.

-gmann

 > 
 > ubuntu 20.04 provides 3.8 coverage and the rest is disto/packaging realted so unless rdo or one of the other installers  speciricly
 > ask for centos 8 stream i dont think we need to keep the nodeset for master.
 > 
 > we do still requrie it for stable branches but for installers like devstack i think its long past time that we pushed people to move
 > to centos 9 stream instead. or any other recent release fo your prefered distro.
 > after all upstream we do not test rhel and never have we use centos as a proxy and centos 9 stream is fully relased and ready to use.
 > > 
 > > -gmann 
 > > 
 > >  > -- 
 > >  > Jeremy Stanley
 > >  > 
 > > 
 > 
 > 
 >