| *** dtantsur_ is now known as dtantsur | 02:24 | |
| *** bauzas_ is now known as bauzas | 03:10 | |
| *** bauzas_ is now known as bauzas | 07:19 | |
| ttx | Hi everyone, we have hit the point in the release process where the release managers need to make sure Python runtimes have been determined for the next development cycle and that Zuul job templates have been created to include those runtimes. Are we good on that? | 13:14 |
|---|---|---|
| *** bauzas_ is now known as bauzas | 13:51 | |
| gouthamr | ttx: o/ nope; we haven't.. i can take a look at this and get back to you. | 14:39 |
| ttx | ++ thanks gouthamr | 15:00 |
| gmann | yeah, I have not started those yet. I will push something today. | 16:13 |
| gouthamr | gmann: o/ i cloned the 2024.2 document and started making some edits.. i'd like to understand the process.. | 16:28 |
| gouthamr | the linux distros for this upcoming release should be ubuntu noble, debian bookworm and cs9 | 16:29 |
| gouthamr | but, we don't yet have any noble testing iiuc.. | 16:29 |
| clarkb | gouthamr: the test nodes are there any one of my near term goals (need to keep the release in mind) is to switch the default nodeset in zuul globally to noble as well | 16:30 |
| clarkb | gouthamr: it should be trivial to get the jobs running on noble, whether or not they will work is another story (I know there was a lot of discussion about eventlet support and setuptools no longer being in place by default and so on) | 16:31 |
| gmann | we test it in devstack, we have the platform job running on noble | 16:32 |
| gouthamr | clarkb: ah... eventlet should be working for python 3.12.. i am not aware of the setuptools restriction | 16:32 |
| gmann | but for all projects this is a community wide goal | 16:32 |
| gouthamr | gmann: is it already? or should one be proposed? | 16:32 |
| clarkb | gouthamr: the setuptools "issue" is that python3.12 doesn't include setuptools by default any longer. This means you have to manually install it if you rely on it. Not a major issue but something that has tripped people up | 16:32 |
| gmann | gouthamr: proposed, once we define the testing runtime | 16:35 |
| gmann | I mean need to proposed | 16:35 |
| gouthamr | clarkb: ah yes; ""devstack-platform-ubuntu-noble" should have uncovered some of it.. but, maybe when we start extending it to the "tempest-full-py3" by default we'll see things failing | 16:35 |
| gouthamr | gmann: ack; egg before the chicken :) thank you.. i was confused about that part. | 16:36 |
| gouthamr | gmann: do you mind me pushing up the pti update, or would you like to do it? | 16:36 |
| gouthamr | s/pti update/runtime update | 16:37 |
| gmann | gouthamr: I can do, I am almost ready. As 2025.1 is SLURP release, we need to take care of previous distro version also | 16:37 |
| gouthamr | gmann: ack; thank you | 16:37 |
| opendevreview | Ghanshyam proposed openstack/governance master: Define testing runtime for 2025.1 release https://review.opendev.org/c/openstack/governance/+/926150 | 16:42 |
| gmann | ^^ | 16:42 |
| gmann | dansmith: as 2025.1 is SLURP release, I am keeping 22.04 (supported in previous release 2024.1) as additional testing. means we will be testing 22.04 (at least single job) and 24.04 version both | 16:44 |
| gmann | dansmith: but min python version supported in 2024.1 is py3.8 and 2025.2 is py3.9. hope it is fine from upgrade perspective? | 16:44 |
| clarkb | gmann: is 2025.2 a typo? should it be 2025.1? | 16:45 |
| gmann | clarkb: ah yeah, i mean 2025.1 | 16:46 |
| gmann | * min python version supported in 2024.1 is py3.8 and 2025.1 will be py3.9. hope it is fine from upgrade perspective? | 16:46 |
| clarkb | my perspective on that is as long as there is overlap between the range of python supported in 2024.1 and 2025.1 this is fine. People can update the runtime platform to a version within the overlap then upgrade the openstack version | 16:50 |
| dansmith | Yep, and I'm quite sure we said we'd not be including 3.8 in the next round | 16:50 |
| clarkb | we can't support all the old stuff forever, instead the goal should be to provide a viable path from old systems to newer systems and that may require you update the operating system and python version | 16:50 |
| gmann | yeah, there is overlap and we did not see much big changes from py3.8 to py3.9 when we were tested both together so things get tested step by step with overlap | 16:52 |
| opendevreview | Ghanshyam proposed openstack/governance master: Define testing runtime for 2025.1 release https://review.opendev.org/c/openstack/governance/+/926150 | 16:54 |
| gmann | gouthamr: pushed the python testing template also https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926152 and https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926153 | 18:15 |
| gmann | ttx: ^^ | 18:16 |
| opendevreview | Ghanshyam proposed openstack/governance master: Opt-in the oslo DPL model for 2025.1 cycle https://review.opendev.org/c/openstack/governance/+/926154 | 18:24 |
| opendevreview | Ghanshyam proposed openstack/election master: Add Watcher candidates/2025.1 placeholder directories https://review.opendev.org/c/openstack/election/+/926156 | 18:32 |
| gmann | from DPL model reset, watcher is the only project moving to PTL model. ^^ adding it for election. | 18:33 |
| gouthamr | gmann: thanks | 18:33 |
| gmann | gouthamr: can we merge this https://review.opendev.org/c/openstack/governance/+/925834 I have pushed the DPL opt-in with latest liaisons https://review.opendev.org/c/openstack/governance/+/926154/ | 18:33 |
| JayF | This was really nice to see us do, thanks for running it gmann +++ | 18:34 |
| JayF | this specifically addresses something I was vocal about and I want you to know it doesn't go unnoticed, I really really appreciate it | 18:34 |
| gmann | yeah, it is little extra work but it make sure things are up to date and monitored for DPL | 18:35 |
| *** bauzas_ is now known as bauzas | 19:17 | |
| gouthamr | gmann: lets wait for damani, tkajinam to +1 the other change? | 19:43 |
| gouthamr | s/other change/https://review.opendev.org/c/openstack/governance/+/926154/ | 19:43 |
| gmann | gouthamr: yeah, I added them as reviewer but yes we need to wait for their +1 | 19:44 |
| gouthamr | ++ | 19:44 |
| gmann | gouthamr: but reset should be ok to merge and 926154 once they +1 | 19:44 |
| gouthamr | i wanted to avoid it just in case slaweq and ianychoi are looking to redo the list of projects | 19:45 |
| gouthamr | i just peeked at #openstack-election, and saw that you did the watcher directory | 19:46 |
| gouthamr | thanks for being on top of it.. | 19:46 |
| gmann | The candidate list is almost final and if any change in leadership model now and before nomination then we can update it. | 19:46 |
| gmann | oslo is going for DPL model which is what we got confirmation on reset state | 19:46 |
| gouthamr | did we? i saw some notes around "being okay for PTL" | 19:47 |
| gouthamr | i didn't want to misinterpret that, but, its an option that the team seems to be okay with | 19:47 |
| gmann | both option are ok and DPL seems more suitable. | 19:47 |
| gmann | either way it should not block reset state change to merge | 19:48 |
| gmann | but anyways if you want to hold it, it is ok. hope they will be able to +1 on another change by tomorrow | 19:48 |
| gmann | tc-members: this is ready for review (should be quick one) https://review.opendev.org/c/openstack/governance/+/925926 | 19:49 |
| opendevreview | Merged openstack/election master: Add Watcher candidates/2025.1 placeholder directories https://review.opendev.org/c/openstack/election/+/926156 | 19:59 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!