Earlier  
Posted Nick Remark
#openstack-nova - 2023-04-24
08:47:58 bauzas so operators upgrading to 2024.1 would have to raise their OS versions before the bump
08:48:22 opendevreview Elod Illes proposed openstack/nova master: Drop nova-tox-functional-py38 https://review.opendev.org/c/openstack/nova/+/881339
08:48:38 elodilles yes, but master is for 2023.2 Bobcat already :)
08:48:56 bauzas I know
08:49:29 bauzas I'm saying that the requirements we have for 2023.1 can't be used when upgrading to 2024.1 now
08:49:43 bauzas or rather 2023.2
08:50:01 bauzas I mean, I'm an operator wanting to upgrade from A to B
08:50:08 bauzas and ideally from A to C
08:50:40 bauzas if I check the common requirements between A and B, I know that I'll be able to use 22.04 but not py38
08:51:27 elodilles i see, but still, the same issue would happen from C to E, as clearly we can't expect to keep py38 till end of time
08:52:13 elodilles nevertheless i'm also not fond of dropping py38 support IF there is no compatibility issue
08:52:43 bauzas elodilles: sure, people have to upgrade anyway by some cadence
08:53:02 bauzas and we're not discussing of any distro, like the one I'm paid for
08:53:49 bauzas I'm just saying that dropping a python version for a release that's not purely required and will prevent operators to seamlessly upgrade from A to B is at least unfortunate
08:54:11 bauzas and I'd like us to take a bit of a thought before we merge this
08:59:26 elodilles bauzas: ack, unfortunately with the tooz release we already started that road :/
08:59:51 bauzas I've seen it
09:01:10 bauzas elodilles: what python version is shipped with 22.04 Jellyfish ?
09:01:43 bauzas 3.10, sorry found it
09:02:47 elodilles to be honest i'd rather keep the old python versions in all deliverables as long as the code is compatible with them. but that is harder to follow and we might not notice when we add incompatible changes (unless we keep old jobs, or lower-constraints like jobs around... :S)
09:07:06 bauzas elodilles: found the TC resolution
09:07:12 bauzas elodilles: read this :
09:07:13 opendevreview Elod Illes proposed openstack/nova master: Drop nova-tox-functional-py38 https://review.opendev.org/c/openstack/nova/+/881339
09:07:17 bauzas Testing: Just as we test and guarantee that upgrades are supported between adjacent releases today, we will also test and guarantee that upgrades between two “SLURP” releases are supported. Upgrades are tested for most projects today with grenade. A skip-level job will be maintained in the grenade repository that tests a normal configuration between the last two “SLURP” releases. The job will be updated on every new “
09:07:17 bauzas SLURP” release, and there will always be a regular single-release grenade job testing between the previous release and current one, as we have today.
09:08:13 bauzas it says nothing for the dependencies
09:08:57 elodilles yes, no word about runtimes
09:11:04 kashyap What are "SLURP" releases, again?
09:13:47 bauzas kashyap: this is the new upstream release cadence where you can skip some release https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html
09:27:14 elodilles bauzas: note that this failure can be now in other repositories as well, it is likely that other projects will start dropping their py38 support / job (neutron for example merged a similar patch already)
09:29:31 bauzas elodilles: yeah, looks like the boat has sailed, but at least for nova, I'd prefer us to take a bit of time for discussing it
09:29:41 bauzas elodilles: at least because of computes :)
09:36:19 kashyap bauzas: Thanks for the link!
10:22:50 sean-k-mooney bauzas: elodilles im +2 on the removal of python 3.8 testing because we should not be testing with 20.04 in the antelope to bobcat grenade job
10:23:48 sean-k-mooney you are required to upgrade your host os before you can upgrade form 2023.1 -> 2023.2
10:24:33 sean-k-mooney the upgrade order is zed -> 2023.1 , ubuntu 20.04 -> ubuntu 22.04, 2023.1->2023.2
10:25:00 sean-k-mooney bauzas: so not only should we expect that they have alredy upgraded there python we should require it
10:26:31 sean-k-mooney we support one release for 2 version of the base os. that was antelope for the ubuntu 20.04 -> 22.04 transtion
10:27:34 sean-k-mooney bobcat does not need to supprot python 3.8 computes even with the slurp cadance nor does C
10:27:55 sean-k-mooney before you can do the skip lelvel upgrade you will need to upgrade the host os
10:32:18 sean-k-mooney actully i have some other comments on https://review.opendev.org/c/openstack/nova/+/881339 so dropign down to -1 as that patch does not remove the 3.8 support in the setup.cfg and tox
10:33:11 sean-k-mooney we should not drop any test coverage until all jobs are usign at least python 3.9 includign grenade
11:10:07 elodilles sean-k-mooney: thanks, yes, that is what i understood as well. about the patch: it's more about dropping the py38 based job, not about 'dropping py38 support of nova', but yes, i can propose a patch (on top of the original patch) that removes py38 from setup.cfg
11:11:10 sean-k-mooney if we claim we supprot it it should be tested
11:11:19 sean-k-mooney so to me droping the jobs and dropign the supprot is tied
11:12:05 sean-k-mooney it could be two patches but i woudl prefer to merge them together in that case
11:12:45 sean-k-mooney do we currently ahve a gate blocker due to tooz?
11:13:09 sean-k-mooney or do we have time to do this proeprly
11:18:15 elodilles nova-tox-functional-py38 is blocking the gate
11:19:20 elodilles and it seem tempest-integrated-compute-ubuntu-focal and nova-ceph-multistore as well using py38
11:19:23 elodilles hmm
11:20:12 sean-k-mooney we can correct the tempest jobs by defining the python version in devstack to be 3.9 or 3.10
11:20:23 sean-k-mooney both are avaiabel on 20.04
11:21:11 elodilles ack, i'll add that to the patch
11:22:27 sean-k-mooney im usre you know this but just set PYTHON3_VERSION=3.9 in the job def
11:23:08 elodilles sean-k-mooney: ack, thanks!
11:23:18 sean-k-mooney tempest-integrated-compute-ubuntu-focal should be deleted this release
11:23:33 sean-k-mooney and nova-ceph-multinode shoudl move to 22.04 eventulaly
11:23:37 sean-k-mooney so this is just temporay
11:24:16 sean-k-mooney tempest-integrated-compute-ubuntu-focal is needed for stable/antelope but not bobcat
11:25:02 sean-k-mooney if you want to just remvoe that feel free but nova-ceph-multistore need to be moved in a seperate patch so seting they python version is the correct workaround for now
11:34:20 opendevreview Elod Illes proposed openstack/nova master: Drop py38 based zuul jobs https://review.opendev.org/c/openstack/nova/+/881339
11:34:24 elodilles sean-k-mooney: ^^^
11:35:08 elodilles ceph job change from focal to jammy would be better in a separate patch i think
11:40:05 opendevreview Elod Illes proposed openstack/nova master: Drop py38 support from setup.cfg and tox.ini https://review.opendev.org/c/openstack/nova/+/881365
11:41:28 elodilles sean-k-mooney: and this is the py38 support drop patch ^^^
11:45:19 sean-k-mooney +1 on both i have a minor comment on the second patch ill take a look again once they run true ci
11:51:22 opendevreview Elod Illes proposed openstack/placement master: Drop py38 based jobs and add py310 instead https://review.opendev.org/c/openstack/placement/+/881366
11:53:30 elodilles sean-k-mooney: thanks, then i'll wait until zuul results appear
12:32:10 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (db) https://review.opendev.org/c/openstack/nova/+/831193
12:32:10 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (objects) https://review.opendev.org/c/openstack/nova/+/839401
12:32:11 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (manila abstraction) https://review.opendev.org/c/openstack/nova/+/831194
12:32:11 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (drivers and compute manager part) https://review.opendev.org/c/openstack/nova/+/833090
12:32:12 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (api) https://review.opendev.org/c/openstack/nova/+/836830
12:32:12 opendevreview ribaudr proposed openstack/nova master: Check shares support https://review.opendev.org/c/openstack/nova/+/850499
12:32:13 opendevreview ribaudr proposed openstack/nova master: Add metadata for shares https://review.opendev.org/c/openstack/nova/+/850500
12:32:13 opendevreview ribaudr proposed openstack/nova master: Add instance.share_attach notification https://review.opendev.org/c/openstack/nova/+/850501
12:32:14 opendevreview ribaudr proposed openstack/nova master: Add instance.share_detach notification https://review.opendev.org/c/openstack/nova/+/851028
12:32:14 opendevreview ribaudr proposed openstack/nova master: Add shares to InstancePayload https://review.opendev.org/c/openstack/nova/+/851029
12:32:16 opendevreview ribaudr proposed openstack/nova master: Add helper methods to attach/detach shares https://review.opendev.org/c/openstack/nova/+/852085
12:32:16 opendevreview ribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working. https://review.opendev.org/c/openstack/nova/+/852086
12:32:18 opendevreview ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087
12:32:18 opendevreview ribaudr proposed openstack/nova master: Add share_info parameter to reboot method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/854823
12:32:20 opendevreview ribaudr proposed openstack/nova master: Support rebooting an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/854824
12:32:20 opendevreview ribaudr proposed openstack/nova master: Add instance.share_attach_error notification https://review.opendev.org/c/openstack/nova/+/860282
12:32:22 opendevreview ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283
12:32:22 opendevreview ribaudr proposed openstack/nova master: Add share_info parameter to resume method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/860284
12:32:24 opendevreview ribaudr proposed openstack/nova master: Support resuming an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/860285
12:32:24 opendevreview ribaudr proposed openstack/nova master: Add helper methods to rescue/unrescue shares https://review.opendev.org/c/openstack/nova/+/860286
12:32:26 opendevreview ribaudr proposed openstack/nova master: Support rescuing an instance with shares (driver part) https://review.opendev.org/c/openstack/nova/+/860287
12:32:26 opendevreview ribaudr proposed openstack/nova master: Support rescuing an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/860288
12:32:28 opendevreview ribaudr proposed openstack/nova master: Docs about Manila shares API usage https://review.opendev.org/c/openstack/nova/+/871642
12:32:28 opendevreview ribaudr proposed openstack/nova master: Mounting the shares as part of the initialization process https://review.opendev.org/c/openstack/nova/+/880075
12:42:13 ralonsoh sean-k-mooney, about PYTHON3_VERSION=3.9, I've tested that in Neutron and focal and doesn't work
12:42:23 ralonsoh even with https://review.opendev.org/c/openstack/devstack/+/881363
12:43:06 ralonsoh about https://review.opendev.org/c/openstack/nova/+/868419, is it possible to merge this patch this week? that will unblock the Neutron CI
12:43:29 ralonsoh tested in https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/879036
12:48:52 sean-k-mooney ralonsoh: well thats a problem since it was ment to be supported
12:49:20 ralonsoh 3.9 in focal? yes, we can install it
12:49:26 ralonsoh but uwsgi cannot

Earlier   Later