| *** pojadhav- is now known as pojadhav|ruck | 02:53 | |
| opendevreview | Belmiro Moreira proposed openstack/governance master: Release identification and release name https://review.opendev.org/c/openstack/governance/+/829563 | 09:54 |
|---|---|---|
| opendevreview | Belmiro Moreira proposed openstack/governance master: Release identification and release name https://review.opendev.org/c/openstack/governance/+/829563 | 09:59 |
| opendevreview | Belmiro Moreira proposed openstack/governance master: Release identification and release name https://review.opendev.org/c/openstack/governance/+/829563 | 10:01 |
| *** pojadhav|ruck is now known as pojadhav|dinner | 14:58 | |
| dansmith | gouthamr: skip-level job worked, it looks like | 15:28 |
| gmann | \o/ | 15:29 |
| opendevreview | Ghanshyam proposed openstack/governance master: Define Zed cycle testing runtime https://review.opendev.org/c/openstack/governance/+/830454 | 15:32 |
| opendevreview | Ghanshyam proposed openstack/governance master: Define Zed cycle testing runtime https://review.opendev.org/c/openstack/governance/+/830454 | 15:33 |
| *** pojadhav|dinner is now known as pojadhav|ruck | 15:33 | |
| gmann | tc-members ^^ Zed testing runtime | 15:59 |
| fungi | elodilles: ^ per question in last week's release meeting | 15:59 |
| gmann | yeah, pinged him in release channel also. | 16:00 |
| elodilles | thanks, both of you :) | 16:01 |
| gmann | one thing is about Ubuntu 22.04 which is not yet released and supposed to be in APril, we can discuss in PTG if we want to include that in Zed or AA testing. based on when it is planned to releases | 16:01 |
| opendevreview | Jeremy Stanley proposed openstack/governance master: Remove the vulnerability:managed tag https://review.opendev.org/c/openstack/governance/+/830478 | 16:25 |
| opendevreview | Jeremy Stanley proposed openstack/governance master: Remove the vulnerability:managed tag https://review.opendev.org/c/openstack/governance/+/830478 | 16:28 |
| fungi | just realized it was also referenced for one deliverable in legacy.yaml | 16:29 |
| *** pojadhav|ruck is now known as pojadhav|out | 17:05 | |
| dansmith | gmann: so, 20.04 for Zed, makes sense.. surely AArdvark will be on 22.04 right? | 17:05 |
| dansmith | if we pretend that we're doing tick-tock from yoga to AA, then will we still have 3.8 and 20.04 in the window for AArdvark so that we can do an in-place upgrade? | 17:06 |
| dansmith | then AA->CC would be 22.04 and be good I think | 17:06 |
| gmann | dansmith: yeah as per current scenario. we will iterate it in PTG if ubuntu 22/04 is released early in april (before PTG) | 17:07 |
| dansmith | gmann: meaning we could revise zed to be 22.04? | 17:07 |
| gmann | dansmith: may be but less possible. I am ok to decide not to revise as we define it now and do not create more work later/in between of cycle. | 17:08 |
| dansmith | gmann: ack, seems better to be conservative, personally, | 17:08 |
| gmann | sure. | 17:08 |
| dansmith | what about my question for Y->AA? | 17:09 |
| gmann | dansmith: yeah for Y->AA, it will be 20.04 -> 22.04 but we test upgrade on 20.04. I am thinking we should keep previous version distro tested for tick release at least? | 17:10 |
| dansmith | right, okay that's my point, so testing runtime for AA will be 22.04 and 20.04 (the latter only for upgrade testing?) | 17:10 |
| gmann | like for AA, we will support both ubuntu 20.04 + 22.04 (doing more testing on 22.04 but keep few jobs for 20.04 too) | 17:10 |
| dansmith | ++ cool, I think that makes sense | 17:11 |
| gmann | yeah | 17:11 |
| dansmith | just want to make sure we're thinking about these things | 17:11 |
| gmann | yeah, I am thinking we should add it somewhere. in resolution ? | 17:12 |
| gmann | or we can create a note document in reference/runtime/ ? so that we keep that while defining the runtime for tick release | 17:12 |
| gmann | I think reference/runtime/ will be better for reference each time someone define the runtime | 17:13 |
| dansmith | yeah, because it technically applies today right? | 17:13 |
| dansmith | when we move the distro support, we need to still support the upgrades from N-1 to N on the common-supported distro, it's just a smaller gap | 17:13 |
| mnaser | my hot take is distros matter less and less these days since im pretty sure most deployments are relying either on from source (venv) or containerized | 17:15 |
| gmann | oh, you mean to do same for tock release too? like BB, CC is on 22.04 and if DD is on 24.04 then test both 22.04 + 24.04 for DD also to support CC->DD upgade ? | 17:15 |
| dansmith | no, I mean today we already kinda have to do this right? | 17:16 |
| dansmith | when we started supporting 20.04, we had to do upgrades on 18.04 for whatever release didn't support 20.04 before we moved, yeah? | 17:16 |
| dansmith | some release had to support both, either as source or target in grenade | 17:16 |
| mnaser | osa is venv, kolla is containers, devstack is venv, tripleo is containers, osh is containers | 17:16 |
| gmann | ah yeah, with greande at some extend we do | 17:16 |
| dansmith | gmann: maybe if we merge the resolution I can just propose another change to project-testing-interface to make that note, even though it's tribal knowledge today, it's worth pointing out if the span becomes two releases instead of one? | 17:17 |
| gmann | dansmith: +1, that will be good. I will add that in PTG topic too if any discussion needed | 17:18 |
| dansmith | cool | 17:18 |
| *** Guest7 is now known as diablo_rojo_phone | 17:24 | |
| *** diablo_rojo_phone is now known as Guest229 | 17:24 | |
| fungi | mnaser: a venv still needs a python interpreter (and any libs/headers for linked c extensions) | 17:27 |
| fungi | those are typically supplied by a linux distro | 17:27 |
| mnaser | fungi: fair mount | 17:28 |
| clarkb | note that devstack doesn't use venvs last I checked | 17:28 |
| fungi | unless you put the venv inside some other container (and even those have distros, be it minimal debian like the official python docker images, or alpine, or...) | 17:28 |
| clarkb | I tried to make that happen when pip broke uninstallation of packages but it gets difficult with grenade in particular | 17:29 |
| clarkb | (tehre were also some weird things ironic is doing that we'd need to address to do devstack in venvs) | 17:29 |
| fungi | "distros are irrelevant" has become the new "virtual machines are irrelevant" | 17:30 |
| mnaser | sometimes i really wish we had a very minimal openstack-y distro | 17:30 |
| fungi | or that great idea of "serverless" computing where you don't need servers any more | 17:30 |
| mnaser | i think what i meant by that is that it doesnt matter if you run ubuntu 18.04 hosts since you can run your contaienrs in 20.04 or vice versa | 17:31 |
| fungi | but you still need to be able to run on at least one of them | 17:31 |
| gmann | tc-members: for PTG planning, I have created the doodle poll, please add your preferred time, https://doodle.com/poll/gz4dy67vmew5wmn9 | 18:42 |
| gmann | tc-members: also for the TC + Community Leaders interaction doodle poll https://doodle.com/poll/dcer6i3wk2b8eim3 | 18:42 |
| gmann | these are etherpads for details https://etherpad.opendev.org/p/tc-zed-ptg https://etherpad.opendev.org/p/tc-ptl-interaction-zed | 18:43 |
| gmann | I think we can go with two-4 hrs sessions for TC and 2hrs TC + Community leaders sessions. | 18:44 |
| opendevreview | Merged openstack/governance master: Revert "Switch Keystone to DPL" https://review.opendev.org/c/openstack/governance/+/829037 | 19:34 |
| *** tbarron is now known as Guest252 | 19:40 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!