| opendevreview | norman shen proposed openstack/nova master: Narrow mdev uuid range https://review.opendev.org/c/openstack/nova/+/832489 | 02:48 |
|---|---|---|
| bauzas | good morning Nova | 07:48 |
| bauzas | a bit remotely working, so on and off for the morning | 07:48 |
| rribaud__ | bauzas, good morning. | 08:21 |
| bauzas | good morning | 08:21 |
| kashyap | bauzas: How much remote can you become :D Bonjour, in any case | 08:50 |
| bauzas | like I said in the internal chan, https://photos.app.goo.gl/jkMW5MmAjD11r8xP9 | 08:51 |
| gibi | bauzas: that looks nice :) | 09:13 |
| kashyap | bauzas: Nice! | 09:20 |
| opendevreview | Alexey Stupnikov proposed openstack/nova master: Add functional tests to reproduce bug #1960412 https://review.opendev.org/c/openstack/nova/+/830010 | 10:06 |
| opendevreview | Alexey Stupnikov proposed openstack/nova master: Clean up when queued live migration aborted https://review.opendev.org/c/openstack/nova/+/828570 | 10:16 |
| admin1 | if a migration fails to happen, do i debug the nova-compute or the nova-placement ? | 12:31 |
| sean-k-mooney | a migration invovles all the nova componetns so it depens on how it failed | 12:32 |
| sean-k-mooney | and when in the migration | 12:32 |
| sean-k-mooney | bauzas: oh your picking up your new car congrats | 12:34 |
| kashyap | admin1: Yeah, migration problems can also be in the virtualization layer too. So it depends on the precise error (whether it be from -compute, -api, or wherever in Nova) | 13:47 |
| bauzas | sean-k-mooney: nah I already had it since 2 weeks, but I was there because I asked for a tow hitch :) | 13:50 |
| sean-k-mooney | ah ok | 13:51 |
| sean-k-mooney | happy with it so far | 13:51 |
| erlon | @sean-k-mooney hey sean, can you revisit these patches when you have a chance? https://review.opendev.org/q/topic:bug%252F1944619 | 13:52 |
| erlon | when is the cut date for RC1? | 13:53 |
| erlon | would be nice to have those included | 13:53 |
| sean-k-mooney | ya i can have a look bauzas its this thursday? | 13:53 |
| sean-k-mooney | rc1 | 13:54 |
| sean-k-mooney | Mar 07 - Mar 11 | 13:54 |
| sean-k-mooney | so ya it will be thursday of this week | 13:54 |
| erlon | great, let me know as soon as possible just in case I need to adjust something else | 13:55 |
| erlon | but I believe I addressed all your concerns listed there | 13:55 |
| sean-k-mooney | im reviewing them now, i added yoga-rc-potential to it and added that as an offical tag | 13:58 |
| sean-k-mooney | not sure why that was not added to the offical tag list before | 13:58 |
| yuval | Is there a weekly meeting now? | 14:02 |
| sean-k-mooney | its in 2 hours i think | 14:03 |
| sean-k-mooney | Regular MEETING TIME: Tuesdays 16:00 UTC (#openstack-nova on OFTC) | 14:03 |
| AndroUser | Test1 | 14:06 |
| yuval | Thanks sean-k-mooney | 14:06 |
| sean-k-mooney | erlon: can you add a release not to the second patch | 14:14 |
| sean-k-mooney | otherwise im +2 on the repoducere and +1 on the fix | 14:14 |
| erlon | ok, give some | 14:15 |
| sean-k-mooney | im happy to upgrade to +2 on the second patch once added so feel free to ping me when its up | 14:15 |
| *** dasm|off is now known as dasm | 14:35 | |
| opendevreview | Erlon R. Cruz proposed openstack/nova master: Fix pre_live_migration rollback https://review.opendev.org/c/openstack/nova/+/815324 | 15:00 |
| bauzas | yuval: sean-k-mooney: sorry was discussing with Uggla | 15:03 |
| bauzas | yes we have a team weekly meeting in 57 mins | 15:03 |
| bauzas | and yes, the RC1 deadline is on Thursday EOB | 15:05 |
| sean-k-mooney | bauzas: can you review https://review.opendev.org/q/topic:bug%252F1944619 its short and would be nice to land before RC1 | 15:19 |
| elodilles | bauzas: sorry, may i quickly update the Stable Branches section at our wiki? | 15:22 |
| *** hemna8 is now known as hemna | 15:25 | |
| bauzas | elodilles: sure, do it | 15:35 |
| bauzas | sean-k-mooney: ack, will look | 15:36 |
| elodilles | bauzas: ack, done | 15:37 |
| bauzas | hah, fun https://bugs.launchpad.net/nova/+bug/1963553 | 15:46 |
| *** hemna7 is now known as hemna | 15:47 | |
| bauzas | reminder: nova meeting in 10 mins here | 15:49 |
| bauzas | #startmeeting nova | 16:00 |
| opendevmeet | Meeting started Tue Mar 8 16:00:04 2022 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| opendevmeet | The meeting name has been set to 'nova' | 16:00 |
| bauzas | hello everyone | 16:00 |
| bauzas | #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | 16:00 |
| elodilles | o/ | 16:00 |
| rribaud__ | o/ | 16:01 |
| gibi | o/ | 16:01 |
| bauzas | let's start | 16:01 |
| bauzas | #topic Bugs (stuck/critical) | 16:01 |
| bauzas | damn | 16:01 |
| * kashyap waves | 16:01 | |
| bauzas | #topic Bugs (stuck/critical) | 16:01 |
| bauzas | #info No Critical bug | 16:01 |
| bauzas | #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 28 new untriaged bugs (+0 since the last meeting) | 16:01 |
| gmann | o/ | 16:01 |
| bauzas | #help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage | 16:01 |
| bauzas | #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (-1 since the last meeting) in Storyboard for Placement | 16:01 |
| bauzas | I triaged a few of them | 16:02 |
| kashyap | bauzas: The call is only on IRC, should we perhaps send a reminder to the list too? | 16:02 |
| bauzas | haven't seen any issue fwiw | 16:02 |
| kashyap | By "call" I mean, call for helping triage. | 16:02 |
| bauzas | kashyap: I see that gibi would be discussed about this during the PTG | 16:02 |
| bauzas | discussing* | 16:02 |
| gibi | yeah I added to topic | 16:02 |
| kashyap | Nod, but that can go on parallely | 16:02 |
| bauzas | for the moment, let's continue to do the same, but indeed we should think about it for the PTG | 16:03 |
| bauzas | the problem is that I'm not sure that contributors are supported by their managers for upstream bug triage if they do it :) | 16:04 |
| gibi | for me it is a bit about allocating a specific timeslot when I focus on bugs | 16:04 |
| bauzas | anyway, let's not discuss this by now | 16:04 |
| gibi | ack | 16:05 |
| bauzas | any bug people want to discuss ? | 16:05 |
| bauzas | I have one | 16:05 |
| bauzas | #link https://bugs.launchpad.net/nova/+bug/1962726 | 16:05 |
| kashyap | Ouch | 16:06 |
| gibi | that seems like a very valid bug | 16:06 |
| kashyap | Yeah, definitely | 16:06 |
| bauzas | yeah, but it should not be a bug | 16:06 |
| kashyap | Don't say an "RFE"; it's definitely a bug in my eyes :) | 16:06 |
| bauzas | at least, I'd say a Wishlist | 16:07 |
| gibi | ssh key creation worked before should still work :) | 16:07 |
| sean-k-mooney | well didnt we already agree not to add supprot for generating other keytypes | 16:07 |
| bauzas | that ^ | 16:07 |
| sean-k-mooney | we talked about this for the fips work | 16:07 |
| sean-k-mooney | and said we shoudl deprecate that part of the api | 16:07 |
| sean-k-mooney | tempest was being modifed to generate teh keys its self | 16:07 |
| gibi | ohh, so we support importing other ecdsa already | 16:08 |
| bauzas | that's why I say it shouldn't be a bug | 16:08 |
| gibi | *other like | 16:08 |
| sean-k-mooney | nova will accpeat any public key you provide and we also support x509 certs for windows | 16:08 |
| sean-k-mooney | we just dont support turning the parmaters if you ask nova ot generate the key | 16:09 |
| gibi | then yeah, I can be convinced to drop the key generation support | 16:09 |
| kashyap | gibi: Good to know; I've read somewhere (unless I'm hallucinating) that ECDSA keys weren't supported | 16:09 |
| bauzas | importing should continue to work | 16:09 |
| bauzas | generating should stop if so | 16:09 |
| bauzas | but, | 16:09 |
| sean-k-mooney | kashyap: there was a limiation imposed by pycryptography | 16:09 |
| bauzas | "should" means a spec I guess | 16:10 |
| bauzas | definitely not a bug | 16:10 |
| sean-k-mooney | we use the ssh public key to encypt some things | 16:10 |
| sean-k-mooney | so if you use a ECDSA key you need a pycryptography version that also supprot it | 16:10 |
| sean-k-mooney | but i belive our min requiremnts cover that now | 16:10 |
| gibi | bauzas: so a spec for removing ssh key generation support in a new microversion | 16:10 |
| gibi | bauzas: as far as I understand | 16:10 |
| sean-k-mooney | +1 | 16:11 |
| bauzas | yup | 16:11 |
| gibi | works for me | 16:11 |
| bauzas | I can ask the reporter at least but I'm not sure he would do it :) | 16:11 |
| bauzas | if we really want to deprecate the generation, someone elso would need to provide the spec | 16:12 |
| gibi | let's add it to the PTG etherpad to see if somebody volunteers | 16:12 |
| bauzas | yup | 16:12 |
| sean-k-mooney | i mean i can proably do it if no one else puts there hand pu | 16:12 |
| bauzas | I'll close the bug and say we'll discuss this at the PTG | 16:12 |
| gibi | sean-k-mooney: I will have free time too probably ;) | 16:12 |
| bauzas | sean-k-mooney: I'm just afraid of deprecating it without explaining why correctly | 16:12 |
| sean-k-mooney | im pretty sure we have a downstream bug for this which we set to wontfix | 16:13 |
| sean-k-mooney | ack ya we shoudl explain the reasoning in the spec | 16:13 |
| bauzas | anyway, closing the upstream bug and discussing this at the TPG | 16:13 |
| bauzas | . | 16:13 |
| bauzas | any other bug ? | 16:13 |
| gibi | - | 16:13 |
| bauzas | cool, moving on | 16:13 |
| bauzas | #topic Gate status | 16:14 |
| bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | 16:14 |
| bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status | 16:14 |
| bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | 16:14 |
| bauzas | nothing new here | 16:14 |
| bauzas | and I haven't seen any CI job failure for the moment | 16:15 |
| bauzas | moving on, then , | 16:15 |
| bauzas | ? | 16:15 |
| bauzas | looks so | 16:16 |
| bauzas | there it goes to the crux | 16:16 |
| bauzas | #topic Release Planning | 16:16 |
| bauzas | #topic Release Planning | 16:16 |
| bauzas | #link https://releases.openstack.org/yoga/schedule.html#y-rc1 RC1 is now due on March 10th | 16:16 |
| bauzas | #link https://etherpad.opendev.org/p/nova-yoga-rc-potential Etherpad for RC tracking | 16:16 |
| bauzas | the etherpad is pretty silent | 16:16 |
| sean-k-mooney | i have one other bug to add to that | 16:16 |
| bauzas | cool then | 16:17 |
| opendevreview | sean mooney proposed openstack/nova master: reenable greendns in nova. https://review.opendev.org/c/openstack/nova/+/830966 | 16:17 |
| sean-k-mooney | https://bugs.launchpad.net/nova/+bug/1964149 | 16:17 |
| sean-k-mooney | that one ^ | 16:17 |
| bauzas | we only have 2 days and fwiw the RC1 patch is already created | 16:17 |
| bauzas | #link https://review.opendev.org/c/openstack/releases/+/832412 RC1 patch for nova | 16:17 |
| bauzas | I'll -1 until we merge what we want | 16:17 |
| bauzas | elodilles: ^ | 16:17 |
| elodilles | bauzas: ack | 16:18 |
| gibi | sean-k-mooney: I will check after the meeting | 16:18 |
| sean-k-mooney | gibi: ack | 16:18 |
| bauzas | that being said, I'm happy with +1ing https://review.opendev.org/c/openstack/releases/+/832416 | 16:19 |
| bauzas | do people are afraid if we merge the placement RC1 change by now ? | 16:19 |
| bauzas | I haven't seen any bugfixes so far needing to hold | 16:19 |
| gibi | I have no objections | 16:20 |
| sean-k-mooney | i dont think we have anything pendign for placement | 16:20 |
| sean-k-mooney | so no objection | 16:20 |
| bauzas | cool, will do after the meeting | 16:21 |
| bauzas | so, I'll review the RC1 related bugs today and tomorrow | 16:21 |
| bauzas | any other bug people think it would be needed to merge before RC1 ? | 16:22 |
| bauzas | reminder, after RC1, we branch stable/yoga which means that only regression bugs would be accepted for RC2 and other RCs | 16:22 |
| bauzas | any other bugfix would need to hold until Yoga GA (end of March) for being backported to stable/yoga | 16:23 |
| bauzas | and those bugfixes wouldn't be within 25.0.0 release, but rather a later stable release (per say, 25.0.1 or other) | 16:23 |
| elodilles | yes, that's an important info ^^^ | 16:24 |
| bauzas | I have said it loud | 16:24 |
| elodilles | :] | 16:24 |
| bauzas | if you care abour your bugs, it's your time | 16:24 |
| bauzas | 1. | 16:25 |
| bauzas | 2. | 16:25 |
| bauzas | 3. | 16:25 |
| bauzas | ok, done. | 16:25 |
| bauzas | #info reminder, thursday is the last day for merging bugfixes in 25.0.0 release, other bugfixes would need to wait after Yoga GA (end of march) to be backported in a later stable release | 16:26 |
| elodilles | thanks :] | 16:26 |
| bauzas | #info as a notice, please provide the changes you'd like nova cores to look at before end of Wed in https://etherpad.opendev.org/p/nova-yoga-rc-potential | 16:27 |
| bauzas | now, this is even louder | 16:27 |
| elodilles | indeed | 16:27 |
| bauzas | last item I have on RC1 | 16:27 |
| bauzas | #link https://review.opendev.org/c/openstack/nova/+/832292 Prelude patch that needs to be merged before RC1 | 16:27 |
| bauzas | I have seen gmann, dansmith and melwitt reviewing it | 16:28 |
| gibi | bauzas: I left a comment before the meeting on the prelude | 16:28 |
| bauzas | gibi: ack, will look | 16:28 |
| bauzas | reminder, we need to merge this one *before RC1* or we wouldn't have a prelude for 25.0.0 and operators wouldn't like it :p | 16:28 |
| bauzas | elodilles: as a reminder, this prelude patch is holding the RC1 patch | 16:29 |
| gmann | policy statements lgtm, thanks bauzas | 16:29 |
| bauzas | kk | 16:29 |
| bauzas | let's continue to look at this change before end of Thursday then | 16:29 |
| bauzas | that's it for me | 16:29 |
| elodilles | bauzas: ack | 16:29 |
| bauzas | next topic, I guess ? | 16:29 |
| bauzas | this is time of the year | 16:30 |
| bauzas | #topic PTG preparation | 16:30 |
| bauzas | I've created an etherpad | 16:30 |
| bauzas | #link https://etherpad.opendev.org/p/nova-zed-ptg Nova Zed PTG etherpad | 16:30 |
| bauzas | and hopefully you saw that I provided 4 options for the PTG schedule | 16:30 |
| bauzas | do people want me to tell them before we officially vote ? | 16:31 |
| gmann | sure | 16:31 |
| bauzas | Option A "The short one" : we ask for 3 days from Wednesday to Friday with 4 hours each (13UTC-17UTC) | 16:31 |
| bauzas | Option B "The week used": we ask for 4 days from Tuesday to Friday with 3 hours each (14UTC-17UTC) | 16:32 |
| bauzas | Option C "The largest one" : we ask for 4 days from Tuesday to Friday with 4 hours each (13UTC-17UTC) | 16:32 |
| bauzas | Option D "The Asian-nice one" : we ask for Wed to Friday with 3 hours each (14UTC-17UTC) but we also ask for Thursday with 2 hours (6UTC-8UTC) | 16:32 |
| bauzas | take a few time to think about them | 16:32 |
| bauzas | in 1 min, I'll start a vote | 16:32 |
| bauzas | once we vote, I'll officially provide the schedule to the fondation folks | 16:33 |
| bauzas | (hopefully meetbot will work this time with the startvote bot) | 16:33 |
| bauzas | #link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027529.html Proposed options for the PTG schedule | 16:33 |
| bauzas | let's start the vote | 16:34 |
| bauzas | #startvote Which schedule option do you prefer for the PTG ? (A, B, C, D, other) | 16:34 |
| opendevmeet | Begin voting on: Which schedule option do you prefer for the PTG ? Valid vote options are , A, B, C, D, other, . | 16:34 |
| opendevmeet | Vote using '#vote OPTION'. Only your last vote counts. | 16:34 |
| bauzas | #vote B | 16:34 |
| gmann | #vote B | 16:34 |
| gibi | #vote B | 16:34 |
| gibi | (or D if we forsee some topics from Asia) | 16:34 |
| sean-k-mooney | #vote B | 16:34 |
| elodilles | #vote B | 16:35 |
| bauzas | gibi: I can ask for a specific timeslot if needed | 16:35 |
| bauzas | after that | 16:35 |
| bauzas | I'm pretty sure the foundation folks wouldn't be against | 16:35 |
| gibi | yeah, I agree | 16:36 |
| bauzas | ok, any other vote ? I'll close the vote in 30 sec | 16:36 |
| gibi | and I can be present | 16:36 |
| bauzas | me too | 16:36 |
| bauzas | #endvote | 16:36 |
| opendevmeet | Voted on "Which schedule option do you prefer for the PTG ?" Results are | 16:36 |
| opendevmeet | B (5): gibi, sean-k-mooney, elodilles, bauzas, gmann | 16:36 |
| bauzas | #agreed option B for the PTG schedule, we'll have 4 days from Tuesday to Friday with 3 hours each (14UTC-17UTC) | 16:37 |
| * gibi pats meetbot's head | 16:37 | |
| bauzas | I'm glad this worked | 16:37 |
| bauzas | this was fun | 16:37 |
| bauzas | moving on | 16:37 |
| gmann | +1, better way to do than doodle :P | 16:37 |
| bauzas | #topic Review priorities | 16:38 |
| dansmith | gmann: :P | 16:38 |
| bauzas | #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+label:Review-Priority%252B1 | 16:38 |
| sean-k-mooney | well the only advantage of doodle is its async if you cant be here | 16:38 |
| bauzas | sean-k-mooney: that's why I said people can vote on the etherpad if they want | 16:38 |
| dansmith | sean-k-mooney: doodle has been causing trouble lately | 16:38 |
| sean-k-mooney | ah | 16:38 |
| dansmith | hence my tongue-in-cheek | 16:38 |
| sean-k-mooney | dansmith: ack | 16:38 |
| bauzas | sean-k-mooney: but I haven't seen anyone doing it but me | 16:39 |
| bauzas | ok, about the review prios, nothing to tell | 16:39 |
| bauzas | I'm happy to see we have the important bugfixes related to RC1 be there | 16:39 |
| bauzas | thanks to the one who labeled them | 16:40 |
| bauzas | I guess we have nothing to say | 16:40 |
| bauzas | so we can move on quickly | 16:40 |
| bauzas | for the sake of the audience :) | 16:40 |
| bauzas | #topic Stable Branches | 16:41 |
| bauzas | elodilles: take the mic | 16:41 |
| elodilles | #info queens and pike branches are blocked | 16:41 |
| elodilles | #info stable/queens gate fix waiting for 2nd +2: https://review.opendev.org/830327 (needs to be backported to pike as well) | 16:41 |
| elodilles | release patches (xena, wallaby, victoria): https://review.opendev.org/q/project:openstack/releases+intopic:nova+is:open | 16:41 |
| elodilles | hopefully they will be accepted soon ^^^ | 16:42 |
| bauzas | for once, I'm happy to say I made my homework :) | 16:42 |
| elodilles | by 2nd release core | 16:42 |
| elodilles | bauzas: :) thanks! :) | 16:42 |
| elodilles | though victoria patch could use a PTL-approved ;) | 16:42 |
| elodilles | * flag :) | 16:42 |
| bauzas | elodilles: yup, because the PTL said no before for the previous revision :p | 16:43 |
| elodilles | true :) | 16:43 |
| bauzas | but I have seen you rebased, so I'll vote | 16:43 |
| *** hemna0 is now known as hemna | 16:43 | |
| bauzas | easy peasy | 16:43 |
| elodilles | bauzas: ack, thx | 16:43 |
| bauzas | nothing other to add ? | 16:43 |
| elodilles | and i think that's it | 16:43 |
| elodilles | nothing else | 16:43 |
| bauzas | k | 16:44 |
| bauzas | #topic Open discussion | 16:44 |
| bauzas | nothing on the agenda | 16:44 |
| bauzas | any item before we close ? | 16:44 |
| bauzas | OK, if so | 16:45 |
| bauzas | let's call it's 15 to beer o'clock | 16:45 |
| bauzas | #endmeeting | 16:45 |
| opendevmeet | Meeting ended Tue Mar 8 16:45:51 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:45 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2022/nova.2022-03-08-16.00.html | 16:45 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2022/nova.2022-03-08-16.00.txt | 16:45 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2022/nova.2022-03-08-16.00.log.html | 16:45 |
| gibi | bauzas: thanks! | 16:45 |
| elodilles | thanks bauzas o/ | 16:46 |
| bauzas | damn, I forgot to thank you all | 16:46 |
| bauzas | my manners | 16:46 |
| bauzas | I'm gross | 16:46 |
| bauzas | and I prefer talking of alcohol instead | 16:46 |
| * bauzas hides | 16:46 | |
| elodilles | :] | 16:46 |
| gibi | don't drink and drive :)( | 16:47 |
| sean-k-mooney | bauzas: by the way whe you say it louder this is what i here https://www.youtube.com/watch?v=ZaI2IlHwmgQ | 16:47 |
| bauzas | gibi: I have Autopilot (c) | 16:47 |
| gibi | nice :) | 16:47 |
| bauzas | nah, kidding | 16:47 |
| gibi | don't give alcohol to the Autopilot then :) | 16:48 |
| bauzas | in Europe, you need to hold your steering wheel every 15 fucking seconds | 16:48 |
| gibi | but I guess it is enough to hold it with one hand, so with the other you can still hold the beer :) | 16:49 |
| gibi | sean-k-mooney: lol | 16:49 |
| bauzas | gibi: this works with any automatic gearbox :p | 16:50 |
| gibi | don't tell me your tesla has a stick :D | 16:50 |
| bauzas | sean-k-mooney: lol about the black eyed peas | 16:51 |
| gibi | anyhow I hope you enjoy the new car | 16:51 |
| bauzas | gibi: indeed | 16:52 |
| sean-k-mooney | you know its one thing ill miss when i swap to eletric. i like driving a manual/stick shift | 16:53 |
| sean-k-mooney | that said i do like the curse control in my i30 too | 16:53 |
| bauzas | sean-k-mooney: fwiw, my first daughter is about to start driving | 16:56 |
| bauzas | in 2 years-ish | 16:56 |
| sean-k-mooney | do ye have the same rule that if you passs in an automatic you cannot drive a manual | 16:57 |
| bauzas | sean-k-mooney: given we only have automatic gearbox cars, she'll learn on those | 16:57 |
| bauzas | sean-k-mooney: correct but, | 16:57 |
| sean-k-mooney | honestly in her lifetime it might be at the point were it wont matter for most people | 16:58 |
| bauzas | once she gets her driving licence (only accepting to drive automatic cars), she'll be able to take 6 hours of lessons with manual gearbox cars | 16:58 |
| bauzas | that's the plan we have | 16:58 |
| sean-k-mooney | well in ireland she woudl have to resit the test | 16:58 |
| bauzas | easier to get the license first, and then learn with the manual cars | 16:58 |
| bauzas | this is different here, you have about to pass a formal theorical exam when you are 15 | 17:00 |
| bauzas | and then you're on a "learning period" when you can drive your parent's car provided an adult is with you | 17:00 |
| bauzas | at 18, you can pass the practical exam when you drive | 17:01 |
| bauzas | which allows you to be on probation for 2 years only | 17:01 |
| bauzas | but you can drive alon | 17:01 |
| bauzas | alone | 17:01 |
| sean-k-mooney | that basically the same here | 17:02 |
| sean-k-mooney | but to get your licene updated to allow you to drive a manual if you passed in an automatic you have to do the pratical driving test again | 17:02 |
| sean-k-mooney | like add the -e option to allow trailers or addign another catagory | 17:03 |
| bauzas | sean-k-mooney: I see, the only difference then is that there is no practical driving "official" test | 17:04 |
| bauzas | (again I mean) | 17:04 |
| *** hemna7 is now known as hemna | 17:05 | |
| bauzas | sean-k-mooney: after 3 months once you get your license, you can take a 7-hour class about driving a manual | 17:05 |
| sean-k-mooney | ya that is simpler if she wants to do that | 17:05 |
| bauzas | after those 7 hours, the driving school gives you a paper that validates your skills | 17:05 |
| bauzas | and you don't need to pass an exam again | 17:06 |
| rribaud__ | bauzas, sean-k-mooney , regarding the ssh rsa key creation removal. Maybe it is something I can do ? That looks not too hard ? | 17:06 |
| bauzas | rribaud__: this is just about deprecating an API | 17:06 |
| bauzas | technically an easy peasy | 17:06 |
| bauzas | but there be dragons with the explanation | 17:06 |
| sean-k-mooney | rribaud__: well in this cycle it just deprecation and then it removal would happen in a new micoroverison but we need to consider the new tick tock life cycle too | 17:07 |
| sean-k-mooney | rribaud__: for the most part we dont actully remove api code | 17:07 |
| sean-k-mooney | we just disable it in the new microverion | 17:07 |
| sean-k-mooney | since we key the fucntionality in old microverions | 17:08 |
| bauzas | sean-k-mooney: IIUC, zed would be tock release | 17:08 |
| sean-k-mooney | yes so we cant actully remvoe it until A | 17:09 |
| bauzas | no | 17:09 |
| bauzas | that's not what I understood | 17:09 |
| sean-k-mooney | if we deprecate in yoga or zed we cant remove it until the next tick | 17:09 |
| bauzas | given yoga was a tick release | 17:09 |
| dansmith | to be clear, neither are tick or tock | 17:09 |
| bauzas | we can't remove in the next tick release | 17:09 |
| dansmith | tick-tock starts at A.. but thinking about this in terms of tick-tock is good exercise for sure | 17:10 |
| bauzas | dansmith: damn, you should write a book "New OpenStack release cadence for Dummies" | 17:10 |
| sean-k-mooney | dansmith: the patch mentioned treatign yoga to A as a dry run | 17:10 |
| dansmith | bauzas: just consider tock as a milestone release | 17:10 |
| bauzas | dansmith: that's what I understood | 17:11 |
| dansmith | sean-k-mooney: yep, that's why I say going through the exercise is good, but it's not in force yet, is all I'm saying | 17:11 |
| bauzas | dansmith: so removing an API deprecated in zed would be C, right? | 17:11 |
| bauzas | it would be harsh if we would remove in A | 17:11 |
| dansmith | bauzas: yes, but if you really deprecate it in zed, you would need to make sure that A *also* has it in the renos because people not deploying tock releases won't read those renos | 17:11 |
| sean-k-mooney | "Y->A should be a "dress rehearsal" where we have the jobs enabled to help smoke out any issues, but where hard guarantees are not yet made." | 17:12 |
| bauzas | dansmith: that's what I understood again | 17:12 |
| sean-k-mooney | in anycase we woudl not remove this till A beacuew we likely wont deprecate in y at this point so the deprecation will be in zed | 17:12 |
| bauzas | I'm assuming our relnotes won't be that read for Zed | 17:12 |
| dansmith | bauzas: btw, doc fro the p-t-g: https://review.opendev.org/c/openstack/project-team-guide/+/832126/1/doc/source/deprecation.rst | 17:12 |
| sean-k-mooney | bauzas: why i think that is not something we should assume | 17:13 |
| bauzas | that reminds me to add an item to the nova etherpad about the cadence | 17:13 |
| sean-k-mooney | im expecting that each tick will have the deperaction fomr the previous tick and tock | 17:13 |
| bauzas | fortunately, we only have tick and tock releases and not Huey, Dewey and Louie releases | 17:14 |
| sean-k-mooney | if we deprecate someitng in a tock are you sayign we need to keep it for a tick, tock and then we can remove in the second tick | 17:14 |
| bauzas | sean-k-mooney: the new release cadence implies that tock releases are intermediate | 17:15 |
| gmann | sean-k-mooney: issue in that is notification, if anyone not monitoring tock release as they can upgrade tick->tick | 17:15 |
| dansmith | yes, because you haven't deprecated it in a release that those people are running | 17:15 |
| gmann | so they miss the deprecation in tock | 17:15 |
| dansmith | right | 17:15 |
| bauzas | sean-k-mooney: there is no benefit into deprecating anything in a tock release | 17:15 |
| dansmith | bauzas: pretty much that, yeah | 17:16 |
| sean-k-mooney | hum ok so that basically means that we only deprecate in ticks | 17:16 |
| bauzas | dansmith: again, are we assuming zed like a tock release unofficially, then ? | 17:16 |
| sean-k-mooney | and then remove in the next tick at the earliest | 17:16 |
| bauzas | sean-k-mooney: you're correct | 17:16 |
| bauzas | to quote dansmith, tock releases are tick-4 releases | 17:17 |
| dansmith | bauzas: unofficially yeah, yoga is "practice tick", zed is "practice tock" and then we commit on AA | 17:17 |
| bauzas | tick-4 s/releases/milestones my bad | 17:17 |
| sean-k-mooney | if we deprecated in a tick is there any reason not to remove in the next tock | 17:17 |
| bauzas | dansmith: ack, pretty clear now | 17:17 |
| sean-k-mooney | since the notice would have been given | 17:18 |
| sean-k-mooney | and for tick to tick upgrades ther is no delta | 17:18 |
| bauzas | sean-k-mooney: no, you need to wait the next tick to remove | 17:18 |
| sean-k-mooney | why if its tick to tick you cant tell the difference | 17:18 |
| bauzas | sean-k-mooney: again, thinking in terms of milestones helps | 17:18 |
| dansmith | sean-k-mooney: well, for people deploying all of them, you'd normally give two cycles yeah? depending on what it is | 17:18 |
| sean-k-mooney | well we give at least one but up to two but sure | 17:19 |
| bauzas | fun, timeout on the PTG schedule agenda https://ethercalc.openstack.org/7yxdas7suqnd | 17:19 |
| bauzas | is it me ? | 17:19 |
| sean-k-mooney | *not up to but offten two | 17:19 |
| bauzas | sean-k-mooney: that's why I'm adding the release cadence to the PTG agenda | 17:19 |
| bauzas | sean-k-mooney: given zed would be a dryrun tock release, let's practice and avoid deprecations in it | 17:19 |
| gmann | bauzas: ethercal seems down for me too at least. | 17:19 |
| sean-k-mooney | basiically if feels asymetic to me | 17:20 |
| bauzas | gmann: ok, I'll try to jab diablo_rojo | 17:20 |
| sean-k-mooney | deprecations in ticks vs tocks have diffeent notice periods | 17:20 |
| gmann | bauzas: sean-k-mooney and we can plan something in TC+PTL sessions too where dansmith can explain/answer the question. | 17:20 |
| rribaud__ | bauzas, same for me https://ethercalc.openstack.org/7yxdas7suqnd seems not answering. | 17:20 |
| sean-k-mooney | i could see jus extendign to at least 2 release working | 17:20 |
| sean-k-mooney | e.g. depreacte in a tick (cant remove till next tick) deprecate in tock (cant remove until next tock) | 17:21 |
| bauzas | gmann: sure, I think I got the memo but discussing the outcomes is a good idea | 17:21 |
| sean-k-mooney | that way all deprecation have at least 2 cycles of notice | 17:21 |
| sean-k-mooney | but it does not end up pilling up 2 cycles of removals into every tick | 17:22 |
| bauzas | sean-k-mooney: take it as we won't do any removal or deprecation during a tock release | 17:22 |
| sean-k-mooney | bauzas: i really dont like that idea | 17:22 |
| bauzas | those are just skipped releases for ops by now | 17:22 |
| dansmith | bauzas: right, that's the easiest thing to do | 17:22 |
| dansmith | bauzas: for something that's really big, if we wanted two ticks of deprecation, removing in the following tock would be reasonable | 17:23 |
| dansmith | maybe something like n-net or virt/xen where we wanted lots of notice | 17:23 |
| bauzas | sean-k-mooney: we have the TC+PTL session before our nova PTG sessions, it's good you gonna attend those | 17:23 |
| sean-k-mooney | i proably will | 17:23 |
| bauzas | dansmith: I see | 17:24 |
| sean-k-mooney | but we will see we need to do this consitently across openstack | 17:24 |
| bauzas | dansmith: deprecate in A, B, C and drop in D | 17:24 |
| bauzas | which means operators would notice it in E | 17:24 |
| dansmith | bauzas: for something really major yeah.. just an example | 17:24 |
| sean-k-mooney | for big things perhaps | 17:24 |
| sean-k-mooney | but in general that feels pretty heavy weight | 17:25 |
| bauzas | dansmith: oh, yeah, got it | 17:25 |
| dansmith | sean-k-mooney: well, I think it's in line with how we've handled things like virt/xen | 17:25 |
| dansmith | and n-net certainly had looots of time between effective death and removal :) | 17:25 |
| bauzas | yeah I see | 17:25 |
| sean-k-mooney | right but that means things like the rpc proxy shoudl not be removed for 3-4 cycles | 17:26 |
| bauzas | we can remove things in a tock release as ops would catch up on it on the next tick release | 17:26 |
| sean-k-mooney | or reshapes which granted we have nver removed yet | 17:26 |
| bauzas | sean-k-mooney: like the RPC compatibilities | 17:26 |
| sean-k-mooney | its not just deprecation it affect | 17:26 |
| bauzas | we can technically drop RPC compat on a tock release, it's just ops won't get it in effect until the next tick | 17:27 |
| sean-k-mooney | so this feels abit like longer release cycles by stelth in a way that i am not sure is sustainable | 17:27 |
| dansmith | sean-k-mooney: it is like that, and not by stealth | 17:27 |
| dansmith | the whole point of this was to strike a balance | 17:28 |
| sean-k-mooney | ya which this does not really do | 17:28 |
| dansmith | the benefit here over longer cycles is that, deprecation aside, we can release *features* every cycle :) | 17:28 |
| dansmith | and we can deliver code, fixes, changes to people more often than once a year | 17:28 |
| bauzas | dansmith: but I guess we'd think of forward porting the relnotes to the next tick release ? | 17:28 |
| sean-k-mooney | yes | 17:28 |
| dansmith | bauzas: I'd say just prelude items | 17:29 |
| bauzas | dansmith: a good reno tooling opportunity | 17:29 |
| dansmith | bauzas: i.e. anything major enough to make it into prelude in a tock is candidate for tick | 17:29 |
| sean-k-mooney | but we are addign teh cost of maintianing things we want to deprecate and remove for 2-3 release instead of just one to two | 17:29 |
| dansmith | sean-k-mooney: yep, this is not free for sure.. but it's benefit to people, which has a cost | 17:29 |
| gmann | which is what we do in most of the case currently | 17:29 |
| sean-k-mooney | like with the xen removeal we woudl have deprecated it in one relase and had to wait 2 release to remove it after noone stepped up to maintian it | 17:29 |
| bauzas | dansmith: this sounds reasonable, I need to see how to split the prelude in multiple patches | 17:30 |
| bauzas | dansmith: so we could forward port the big prelude patch to the next release | 17:30 |
| dansmith | bauzas: or just manually copy the items.. I don't think you need to get too sophisticated :) | 17:30 |
| bauzas | are you asking copy/paste ? man ! | 17:30 |
| sean-k-mooney | bauzas: actuly i think we want reno to know what tick and tock releases are | 17:31 |
| sean-k-mooney | and include the release notes form the previous tock in the tick | 17:31 |
| dansmith | sean-k-mooney: personally, I wouldn't do that | 17:31 |
| sean-k-mooney | no | 17:31 |
| dansmith | I think that's a mistake | 17:31 |
| sean-k-mooney | why ? | 17:31 |
| dansmith | don't make them read double the release notes, as compiled by a computer | 17:31 |
| dansmith | bring forward the important bits (i.e. likely the content of the prelude) | 17:32 |
| sean-k-mooney | an operator goign form tick 1 to tick 2 need to know everythign that happend in tock 1 right | 17:32 |
| dansmith | they can read the intermediate release notes if they want, but don't just concat them | 17:32 |
| sean-k-mooney | i guess | 17:32 |
| sean-k-mooney | i hate having to look in mulitple places | 17:32 |
| gmann | we can add a line in the top or so that 'to know all change from tick1->tick2 read these tock releasenotes too' | 17:32 |
| dansmith | just MHO, but I think we're already incredibly verbose on the renos | 17:32 |
| sean-k-mooney | but you coudl do it either way | 17:32 |
| sean-k-mooney | dansmith: i mean perhaps prelude and upgrades section maybe | 17:33 |
| sean-k-mooney | i guess we will figure it out | 17:33 |
| gmann | will there be any upgrade section in tock? i mean we want to avoid those like depreaction right | 17:33 |
| dansmith | gmann: sometimes features bring upgrade items I think | 17:33 |
| sean-k-mooney | gmann: there should be | 17:34 |
| sean-k-mooney | gmann: i really dont thinik we shoudl try to avoid either in a tock | 17:34 |
| gmann | ah new feature. got it | 17:34 |
| sean-k-mooney | if we do it will slow down devleopment | 17:34 |
| sean-k-mooney | gmann: addin a db migraition for a new feature woudl be an upgrade impact i coudl see in a tock | 17:34 |
| dansmith | sean-k-mooney: remember this is a compromise, some things will have to change.. hopefully less with this than the alternative | 17:35 |
| gmann | making release notes page too verbose and long make them hard to read good things. I think link to tock releease notes in tick releasenotes should be fine | 17:35 |
| dansmith | gmann: agree | 17:35 |
| sean-k-mooney | dansmith: right but if we cant do db changes in a tock or rpc change for example then tha tis not a compromise | 17:35 |
| * sean-k-mooney not that we have really done db change in a few releases | 17:36 | |
| dansmith | sean-k-mooney: as noted, I think it's totally fine to *add* things to db and rpc in tock | 17:36 |
| bauzas | yup | 17:38 |
| bauzas | we can rpc bump things in a tock | 17:39 |
| bauzas | if we have rpc compat of courser | 17:39 |
| bauzas | we can add a db upgrade script too | 17:39 |
| bauzas | we can even remove a rpc compat on a tock release if compat was there on the previous tick | 17:40 |
| bauzas | rpc aliases will continue to exist | 17:40 |
| bauzas | and microversions too | 17:40 |
| bauzas | but somehow we need to settle a couple of rules we gonna write on our contrib docs | 17:41 |
| bauzas | that's why I want us to agree on the impacts for nova so we can write it down | 17:41 |
| gmann | bauzas: +1. | 17:42 |
| gmann | bauzas: sean-k-mooney added it on TC+PTL slots, L27 - https://etherpad.opendev.org/p/tc-ptl-interaction-zed | 17:43 |
| sean-k-mooney | gmann: thanks | 17:45 |
| sean-k-mooney | bauzas: yes we have time to figure that out before AA | 17:45 |
| sean-k-mooney | ok im hungery so im going to grab something to eat i might be on irc later but i will likely just work on some reviews for the evning | 17:53 |
| opendevreview | Sylvain Bauza proposed openstack/nova master: Add the Yoga prelude section https://review.opendev.org/c/openstack/nova/+/832292 | 17:53 |
| bauzas | gmann: dansmith: melwitt: sean-k-mooney: gibi: new revision for the Yoga prelude ^ | 17:54 |
| gibi | bauzas: +2 from me | 17:55 |
| gibi | thanks for writing it up | 17:55 |
| bauzas | thanks | 17:55 |
| * bauzas goes off | 17:55 | |
| dansmith | bauzas: looks good content-wise to me, but a bunch of nit corrections | 17:58 |
| opendevreview | ribaudr proposed openstack/python-novaclient master: Microversion 2.91: Support specifying destination host to unshelve https://review.opendev.org/c/openstack/python-novaclient/+/831651 | 18:08 |
| *** sfinucan is now known as stephenfin | 19:03 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!