Tuesday, 2022-03-08

opendevreviewnorman shen proposed openstack/nova master: Narrow mdev uuid range  https://review.opendev.org/c/openstack/nova/+/83248902:48
bauzasgood morning Nova07:48
bauzasa bit remotely working, so on and off for the morning07:48
rribaud__bauzas, good morning.08:21
bauzasgood morning08:21
kashyapbauzas: How much remote can you become :D  Bonjour, in any case08:50
bauzaslike I said in the internal chan, https://photos.app.goo.gl/jkMW5MmAjD11r8xP908:51
gibibauzas: that looks nice :)09:13
kashyapbauzas: Nice!09:20
opendevreviewAlexey Stupnikov proposed openstack/nova master: Add functional tests to reproduce bug #1960412  https://review.opendev.org/c/openstack/nova/+/83001010:06
opendevreviewAlexey Stupnikov proposed openstack/nova master: Clean up when queued live migration aborted  https://review.opendev.org/c/openstack/nova/+/82857010:16
admin1if a migration fails to happen, do i debug the nova-compute or the nova-placement  ? 12:31
sean-k-mooneya migration invovles all the nova componetns so it depens on how it failed12:32
sean-k-mooneyand when in the migration12:32
sean-k-mooneybauzas: oh your picking up your new car congrats12:34
kashyapadmin1: 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
bauzassean-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-mooneyah ok13:51
sean-k-mooneyhappy with it so far13:51
erlon@sean-k-mooney hey sean, can you revisit these patches when you have a chance? https://review.opendev.org/q/topic:bug%252F194461913:52
erlonwhen is the cut date for RC1?13:53
erlonwould be nice to have those included13:53
sean-k-mooneyya i can have a look bauzas its this thursday?13:53
sean-k-mooneyrc113:54
sean-k-mooneyMar 07 - Mar 1113:54
sean-k-mooneyso ya it will be thursday of this week13:54
erlongreat, let me know as soon as possible just in case I need to adjust something else13:55
erlonbut I believe I addressed all your concerns listed there13:55
sean-k-mooneyim reviewing them now, i added  yoga-rc-potential  to it and added that as an offical tag13:58
sean-k-mooneynot sure why that was not added to the offical tag list before13:58
yuvalIs there a weekly meeting now?14:02
sean-k-mooneyits in 2 hours i think14:03
sean-k-mooneyRegular MEETING TIME: Tuesdays 16:00 UTC (#openstack-nova on OFTC)14:03
AndroUserTest114:06
yuvalThanks sean-k-mooney14:06
sean-k-mooneyerlon: can you add a release not to the second patch14:14
sean-k-mooneyotherwise im +2 on the repoducere and +1 on the fix14:14
erlonok, give some14:15
sean-k-mooneyim happy to upgrade to +2 on the second patch once added so feel free to ping me when its up14:15
*** dasm|off is now known as dasm14:35
opendevreviewErlon R. Cruz proposed openstack/nova master: Fix pre_live_migration rollback  https://review.opendev.org/c/openstack/nova/+/81532415:00
bauzasyuval: sean-k-mooney: sorry was discussing with Uggla15:03
bauzasyes we have a team weekly meeting in 57 mins15:03
bauzasand yes, the RC1 deadline is on Thursday EOB15:05
sean-k-mooneybauzas: can you review https://review.opendev.org/q/topic:bug%252F1944619 its short and would be nice to land before RC115:19
elodillesbauzas: sorry, may i quickly update the Stable Branches section at our wiki?15:22
*** hemna8 is now known as hemna15:25
bauzaselodilles: sure, do it15:35
bauzassean-k-mooney: ack, will look15:36
elodillesbauzas: ack, done15:37
bauzashah, fun https://bugs.launchpad.net/nova/+bug/196355315:46
*** hemna7 is now known as hemna15:47
bauzasreminder: nova meeting in 10 mins here 15:49
bauzas#startmeeting nova16:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
bauzashello everyone16:00
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:00
elodilleso/16:00
rribaud__o/16:01
gibio/16:01
bauzaslet's start16:01
bauzas #topic Bugs (stuck/critical) 16:01
bauzasdamn16:01
* kashyap waves16:01
bauzas#topic Bugs (stuck/critical) 16:01
bauzas#info No Critical bug16: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
gmanno/16:01
bauzas#help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage16:01
bauzas#link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (-1 since the last meeting) in Storyboard for Placement 16:01
bauzasI triaged a few of them16:02
kashyapbauzas: The call is only on IRC, should we perhaps send a reminder to the list too?16:02
bauzashaven't seen any issue fwiw16:02
kashyapBy "call" I mean, call for helping triage.16:02
bauzaskashyap: I see that gibi would be discussed about this during the PTG16:02
bauzasdiscussing*16:02
gibiyeah I added to topic16:02
kashyapNod, but that can go on parallely16:02
bauzasfor the moment, let's continue to do the same, but indeed we should think about it for the PTG16:03
bauzasthe problem is that I'm not sure that contributors are supported by their managers for upstream bug triage if they do it :)16:04
gibifor me it is a bit about allocating a specific timeslot when I focus on bugs16:04
bauzasanyway, let's not discuss this by now16:04
gibiack16:05
bauzasany bug people want to discuss ?16:05
bauzasI have one 16:05
bauzas#link https://bugs.launchpad.net/nova/+bug/196272616:05
kashyapOuch16:06
gibithat seems like a very valid bug16:06
kashyapYeah, definitely16:06
bauzasyeah, but it should not be a bug 16:06
kashyapDon't say an "RFE"; it's definitely a bug in my eyes :)16:06
bauzasat least, I'd say a Wishlist16:07
gibissh key creation worked before should still work :)16:07
sean-k-mooneywell didnt we already agree not to add supprot for generating other keytypes16:07
bauzasthat ^16:07
sean-k-mooneywe talked about this for the fips work16:07
sean-k-mooneyand said we shoudl deprecate that part of the api16:07
sean-k-mooneytempest was being modifed to generate teh keys its self16:07
gibiohh, so we support importing other ecdsa already16:08
bauzasthat's why I say it shouldn't be a bug16:08
gibi*other like16:08
sean-k-mooneynova will accpeat any public key you provide and we also support x509 certs for windows16:08
sean-k-mooneywe just dont support turning the parmaters if you ask nova ot generate the key16:09
gibithen yeah, I can be convinced to drop the key generation support16:09
kashyapgibi: Good to know; I've read somewhere (unless I'm hallucinating) that ECDSA keys weren't supported16:09
bauzasimporting should continue to work16:09
bauzasgenerating should stop if so16:09
bauzasbut,16:09
sean-k-mooneykashyap: there was a limiation imposed by pycryptography16:09
bauzas"should" means a spec I guess16:10
bauzasdefinitely not a bug16:10
sean-k-mooneywe use the ssh public key to encypt some things16:10
sean-k-mooneyso if you use a ECDSA key you need a pycryptography version that also supprot it16:10
sean-k-mooneybut i belive our min requiremnts cover that now16:10
gibibauzas: so a spec for removing ssh key generation support in a new microversion16:10
gibibauzas: as far as I understand16:10
sean-k-mooney+1 16:11
bauzasyup16:11
gibiworks for me16:11
bauzasI can ask the reporter at least but I'm not sure he would do it :)16:11
bauzasif we really want to deprecate the generation, someone elso would need to provide the spec16:12
gibilet's add it to the PTG etherpad to see if somebody volunteers16:12
bauzasyup16:12
sean-k-mooneyi mean i can proably do it if no one else puts there hand pu16:12
bauzasI'll close the bug and say we'll discuss this at the PTG 16:12
gibisean-k-mooney: I will have free time too probably ;)16:12
bauzassean-k-mooney: I'm just afraid of deprecating it without explaining why correctly16:12
sean-k-mooneyim pretty sure we have a downstream bug for this which we set to wontfix 16:13
sean-k-mooneyack ya we shoudl explain the reasoning in the spec16:13
bauzasanyway, closing the upstream bug and discussing this at the TPG16:13
bauzas.16:13
bauzasany other bug ?16:13
gibi-16:13
bauzascool, moving on16: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
bauzasnothing new here16:14
bauzasand I haven't seen any CI job failure for the moment16:15
bauzasmoving on, then ,16:15
bauzas?16:15
bauzaslooks so16:16
bauzasthere it goes to the crux16: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 10th16:16
bauzas#link https://etherpad.opendev.org/p/nova-yoga-rc-potential Etherpad for RC tracking16:16
bauzasthe etherpad is pretty silent16:16
sean-k-mooneyi have one other bug to add to that16:16
bauzascool then16:17
opendevreviewsean mooney proposed openstack/nova master: reenable greendns in nova.  https://review.opendev.org/c/openstack/nova/+/83096616:17
sean-k-mooneyhttps://bugs.launchpad.net/nova/+bug/196414916:17
sean-k-mooneythat one ^16:17
bauzaswe only have 2 days and fwiw the RC1 patch is already created16:17
bauzas#link https://review.opendev.org/c/openstack/releases/+/832412 RC1 patch for nova16:17
bauzasI'll -1 until we merge what we want16:17
bauzaselodilles: ^16:17
elodillesbauzas: ack16:18
gibisean-k-mooney: I will check after the meeting16:18
sean-k-mooneygibi: ack16:18
bauzasthat being said, I'm happy with +1ing https://review.opendev.org/c/openstack/releases/+/83241616:19
bauzasdo people are afraid if we merge the placement RC1 change by now ?16:19
bauzasI haven't seen any bugfixes so far needing to hold16:19
gibiI have no objections16:20
sean-k-mooneyi dont think we have anything pendign for placement16:20
sean-k-mooneyso no objection16:20
bauzascool, will do after the meeting16:21
bauzasso, I'll review the RC1 related bugs today and tomorrow16:21
bauzasany other bug people think it would be needed to merge before RC1 ?16:22
bauzasreminder, after RC1, we branch stable/yoga which means that only regression bugs would be accepted for RC2 and other RCs16:22
bauzasany other bugfix would need to hold until Yoga GA (end of March) for being backported to stable/yoga 16:23
bauzasand 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
elodillesyes, that's an important info ^^^16:24
bauzasI have said it loud16:24
elodilles:]16:24
bauzasif you care abour your bugs, it's your time16:24
bauzas1.16:25
bauzas2.16:25
bauzas3.16:25
bauzasok, 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 release16:26
elodillesthanks :]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-potential16:27
bauzasnow, this is even louder16:27
elodillesindeed16:27
bauzaslast item I have on RC116:27
bauzas#link https://review.opendev.org/c/openstack/nova/+/832292 Prelude patch that needs to be merged before RC116:27
bauzasI have seen gmann, dansmith and melwitt reviewing it16:28
gibibauzas: I left a comment before the meeting on the prelude16:28
bauzasgibi: ack, will look16:28
bauzasreminder, 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 :p16:28
bauzaselodilles: as a reminder, this prelude patch is holding the RC1 patch16:29
gmannpolicy statements lgtm, thanks bauzas 16:29
bauzaskk16:29
bauzaslet's continue to look at this change before end of Thursday then16:29
bauzasthat's it for me16:29
elodillesbauzas: ack16:29
bauzasnext topic, I guess ?16:29
bauzasthis is time of the year 16:30
bauzas#topic PTG preparation 16:30
bauzasI've created an etherpad16:30
bauzas#link https://etherpad.opendev.org/p/nova-zed-ptg Nova Zed PTG etherpad16:30
bauzasand hopefully you saw that I provided 4 options for the PTG schedule16:30
bauzasdo people want me to tell them before we officially vote ?16:31
gmannsure16:31
bauzasOption A "The short one"  : we ask for 3 days from Wednesday to Friday with 4 hours each (13UTC-17UTC)  16:31
bauzasOption B "The week used": we ask for 4 days from Tuesday to Friday with 3 hours each (14UTC-17UTC) 16:32
bauzasOption C "The largest one" : we ask for 4 days from Tuesday to Friday with 4 hours each (13UTC-17UTC)  16:32
bauzasOption 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
bauzastake a few time to think about them16:32
bauzasin 1 min, I'll start a vote16:32
bauzasonce we vote, I'll officially provide the schedule to the fondation folks16: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 schedule16:33
bauzaslet's start the vote16:34
bauzas#startvote Which schedule option do you prefer for the PTG ? (A, B, C, D, other)16:34
opendevmeetBegin voting on: Which schedule option do you prefer for the PTG ? Valid vote options are , A, B, C, D, other, .16:34
opendevmeetVote using '#vote OPTION'. Only your last vote counts.16:34
bauzas#vote B16:34
gmann#vote B16:34
gibi#vote B16:34
gibi(or D if we forsee some topics from Asia)16:34
sean-k-mooney#vote B16:34
elodilles#vote B16:35
bauzasgibi: I can ask for a specific timeslot if needed 16:35
bauzasafter that16:35
bauzasI'm pretty sure the foundation folks wouldn't be against16:35
gibiyeah, I agree16:36
bauzasok, any other vote ? I'll close the vote in 30 sec16:36
gibiand I can be present 16:36
bauzasme too16:36
bauzas#endvote16:36
opendevmeetVoted on "Which schedule option do you prefer for the PTG ?" Results are16:36
opendevmeetB (5): gibi, sean-k-mooney, elodilles, bauzas, gmann16: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 head16:37
bauzasI'm glad this worked16:37
bauzasthis was fun16:37
bauzasmoving on16:37
gmann+1, better way to do than doodle :P16:37
bauzas#topic Review priorities 16:38
dansmithgmann: :P16: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%252B116:38
sean-k-mooneywell the only advantage of doodle is its async if you cant be here16:38
bauzassean-k-mooney: that's why I said people can vote on the etherpad if they want16:38
dansmithsean-k-mooney: doodle has been causing trouble lately16:38
sean-k-mooneyah16:38
dansmithhence my tongue-in-cheek16:38
sean-k-mooneydansmith: ack 16:38
bauzassean-k-mooney: but I haven't seen anyone doing it but me 16:39
bauzasok, about the review prios, nothing to tell16:39
bauzasI'm happy to see we have the important bugfixes related to RC1 be there16:39
bauzasthanks to the one who labeled them16:40
bauzasI guess we have nothing to say16:40
bauzasso we can move on quickly16:40
bauzasfor the sake of the audience :)16:40
bauzas#topic Stable Branches 16:41
bauzaselodilles: take the mic16:41
elodilles#info queens and pike branches are blocked16: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
elodillesrelease patches (xena, wallaby, victoria): https://review.opendev.org/q/project:openstack/releases+intopic:nova+is:open16:41
elodilleshopefully they will be accepted soon ^^^16:42
bauzasfor once, I'm happy to say I made my homework :)16:42
elodillesby 2nd release core16:42
elodillesbauzas: :) thanks! :)16:42
elodillesthough victoria patch could use a PTL-approved ;)16:42
elodilles* flag :)16:42
bauzaselodilles: yup, because the PTL said no before for the previous revision :p16:43
elodillestrue :)16:43
bauzasbut I have seen you rebased, so I'll vote16:43
*** hemna0 is now known as hemna16:43
bauzaseasy peasy16:43
elodillesbauzas: ack, thx16:43
bauzasnothing other to add ?16:43
elodillesand i think that's it16:43
elodillesnothing else16:43
bauzask16:44
bauzas#topic Open discussion 16:44
bauzasnothing on the agenda16:44
bauzasany item before we close ?16:44
bauzasOK, if so16:45
bauzaslet's call it's 15 to beer o'clock16:45
bauzas#endmeeting16:45
opendevmeetMeeting ended Tue Mar  8 16:45:51 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:45
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2022/nova.2022-03-08-16.00.html16:45
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2022/nova.2022-03-08-16.00.txt16:45
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2022/nova.2022-03-08-16.00.log.html16:45
gibibauzas: thanks!16:45
elodillesthanks bauzas o/16:46
bauzasdamn, I forgot to thank you all16:46
bauzasmy manners16:46
bauzasI'm gross16:46
bauzasand I prefer talking of alcohol instead16:46
* bauzas hides16:46
elodilles:]16:46
gibidon't drink and drive :)(16:47
sean-k-mooneybauzas: by the way whe you say it louder this is what i here https://www.youtube.com/watch?v=ZaI2IlHwmgQ16:47
bauzasgibi: I have Autopilot (c) 16:47
gibinice :)16:47
bauzasnah, kidding16:47
gibidon't give alcohol to the Autopilot then :)16:48
bauzasin Europe, you need to hold your steering wheel every 15 fucking seconds16:48
gibibut I guess it is enough to hold it with one hand, so with the other you can still hold the beer :)16:49
gibisean-k-mooney: lol16:49
bauzasgibi: this works with any automatic gearbox :p16:50
gibidon't tell me your tesla has a stick :D16:50
bauzassean-k-mooney: lol about the black eyed peas16:51
gibianyhow I hope you enjoy the new car16:51
bauzasgibi: indeed16:52
sean-k-mooneyyou know its one thing ill miss when i swap to eletric. i like driving a manual/stick shift16:53
sean-k-mooneythat said i do like the curse control in my i30 too16:53
bauzassean-k-mooney: fwiw, my first daughter is about to start driving16:56
bauzasin 2 years-ish16:56
sean-k-mooneydo ye have the same rule that if you passs in an automatic you cannot drive a manual16:57
bauzassean-k-mooney: given we only have automatic gearbox cars, she'll learn on those16:57
bauzassean-k-mooney: correct but,16:57
sean-k-mooneyhonestly in her lifetime it might be at the point were it wont matter for most people16:58
bauzasonce she gets her driving licence (only accepting to drive automatic cars), she'll be able to take 6 hours of lessons with manual gearbox cars16:58
bauzasthat's the plan we have16:58
sean-k-mooneywell in ireland she woudl have to resit the test16:58
bauzaseasier to get the license first, and then learn with the manual cars16:58
bauzasthis is different here, you have about to pass a formal theorical exam when you are 1517:00
bauzasand then you're on a "learning period" when you can drive your parent's car provided an adult is with you 17:00
bauzasat 18, you can pass the practical exam when you drive17:01
bauzaswhich allows you to be on probation for 2 years only17:01
bauzasbut you can drive alon17:01
bauzasalone17:01
sean-k-mooneythat basically the same here17:02
sean-k-mooneybut 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 again17:02
sean-k-mooneylike add the -e option to allow trailers or addign another catagory17:03
bauzassean-k-mooney: I see, the only difference then is that there is no practical driving "official" test17:04
bauzas(again I mean)17:04
*** hemna7 is now known as hemna17:05
bauzassean-k-mooney: after 3 months once you get your license, you can take a 7-hour class about driving a manual17:05
sean-k-mooneyya that is simpler if she wants to do that17:05
bauzasafter those 7 hours, the driving school gives you a paper that validates your skills17:05
bauzasand you don't need to pass an exam again17: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
bauzasrribaud__: this is just about deprecating an API17:06
bauzastechnically an easy peasy17:06
bauzasbut there be dragons with the explanation17:06
sean-k-mooneyrribaud__: 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 too17:07
sean-k-mooneyrribaud__: for the most part we dont actully remove api code17:07
sean-k-mooneywe just disable it in the new microverion17:07
sean-k-mooneysince we key the fucntionality in old microverions17:08
bauzassean-k-mooney: IIUC, zed would be tock release17:08
sean-k-mooneyyes so we cant actully remvoe it until A17:09
bauzasno17:09
bauzasthat's not what I understood17:09
sean-k-mooneyif we deprecate in yoga or zed we cant remove it until the next tick17:09
bauzasgiven yoga was a tick release17:09
dansmithto be clear, neither are tick or tock17:09
bauzaswe can't remove in the next tick release17:09
dansmithtick-tock starts at A.. but thinking about this in terms of tick-tock is good exercise for sure17:10
bauzasdansmith: damn, you should write a book "New OpenStack release cadence for Dummies"17:10
sean-k-mooneydansmith: the patch mentioned treatign yoga to A as a dry run17:10
dansmithbauzas: just consider tock as a milestone release17:10
bauzasdansmith: that's what I understood 17:11
dansmithsean-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 saying17:11
bauzasdansmith: so removing an API deprecated in zed would be C, right?17:11
bauzasit would be harsh if we would remove in A17:11
dansmithbauzas: 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 renos17: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
bauzasdansmith: that's what I understood again17:12
sean-k-mooneyin anycase we woudl not remove this till A beacuew we likely wont deprecate in y at this point so the deprecation will be in zed17:12
bauzasI'm assuming our relnotes won't be that read for Zed17:12
dansmithbauzas: btw, doc fro the p-t-g: https://review.opendev.org/c/openstack/project-team-guide/+/832126/1/doc/source/deprecation.rst17:12
sean-k-mooneybauzas: why i think that is not something we should assume17:13
bauzasthat reminds me to add an item to the nova etherpad about the cadence17:13
sean-k-mooneyim expecting that each tick will have the deperaction fomr the previous tick and tock17:13
bauzasfortunately, we only have tick and tock releases and not Huey, Dewey and Louie releases17:14
sean-k-mooneyif 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 tick17:14
bauzassean-k-mooney: the new release cadence implies that tock releases are intermediate 17:15
gmannsean-k-mooney: issue in that is notification, if anyone not monitoring tock release as they can upgrade tick->tick17:15
dansmithyes, because you haven't deprecated it in a release that those people are running17:15
gmannso they miss the deprecation in tock17:15
dansmithright17:15
bauzassean-k-mooney: there is no benefit into deprecating anything in a tock release17:15
dansmithbauzas: pretty much that, yeah17:16
sean-k-mooneyhum ok so that basically means that we only deprecate in ticks17:16
bauzasdansmith: again, are we assuming zed like a tock release unofficially, then ?17:16
sean-k-mooneyand then remove in the next tick at the earliest17:16
bauzassean-k-mooney: you're correct17:16
bauzasto quote dansmith, tock releases are tick-4 releases17:17
dansmithbauzas: unofficially yeah, yoga is "practice tick", zed is "practice tock" and then we commit on AA17:17
bauzastick-4 s/releases/milestones my bad17:17
sean-k-mooneyif we deprecated in a tick is there any reason not to remove in the next tock17:17
bauzasdansmith: ack, pretty clear now17:17
sean-k-mooneysince the notice would have been given17:18
sean-k-mooneyand for tick to tick upgrades ther is no delta17:18
bauzassean-k-mooney: no, you need to wait the next tick to remove17:18
sean-k-mooneywhy if its tick to tick you cant tell the difference17:18
bauzassean-k-mooney: again, thinking in terms of milestones helps17:18
dansmithsean-k-mooney: well, for people deploying all of them, you'd normally give two cycles yeah? depending on what it is17:18
sean-k-mooneywell we give at least one but up to two but sure17:19
bauzasfun, timeout on the PTG schedule agenda https://ethercalc.openstack.org/7yxdas7suqnd17:19
bauzasis it me ?17:19
sean-k-mooney*not up to but offten two17:19
bauzassean-k-mooney: that's why I'm adding the release cadence to the PTG agenda17:19
bauzassean-k-mooney: given zed would be a dryrun tock release, let's practice and avoid deprecations in it17:19
gmannbauzas: ethercal seems down for me too at least. 17:19
sean-k-mooneybasiically if feels asymetic to me17:20
bauzasgmann: ok, I'll try to jab diablo_rojo17:20
sean-k-mooneydeprecations in ticks vs tocks have diffeent notice periods17:20
gmannbauzas: 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-mooneyi could see jus extendign to at least 2 release working17:20
sean-k-mooneye.g. depreacte in a tick (cant remove till next tick) deprecate in tock (cant remove until next tock)17:21
bauzasgmann: sure, I think I got the memo but discussing the outcomes is a good idea17:21
sean-k-mooneythat way all deprecation have at least 2 cycles of notice17:21
sean-k-mooneybut it does not end up pilling up 2 cycles of removals into every tick17:22
bauzassean-k-mooney: take it as we won't do any removal or deprecation during a tock release17:22
sean-k-mooneybauzas: i really dont like that idea17:22
bauzasthose are just skipped releases for ops by now17:22
dansmithbauzas: right, that's the easiest thing to do17:22
dansmithbauzas: for something that's really big, if we wanted two ticks of deprecation, removing in the following tock would be reasonable17:23
dansmithmaybe something like n-net or virt/xen where we wanted lots of notice17:23
bauzassean-k-mooney: we have the TC+PTL session before our nova PTG sessions, it's good you gonna attend those17:23
sean-k-mooneyi proably will17:23
bauzasdansmith: I see17:24
sean-k-mooneybut we will see we need to do this consitently across openstack17:24
bauzasdansmith: deprecate in A, B, C and drop in D17:24
bauzaswhich means operators would notice it in E17:24
dansmithbauzas: for something really major yeah.. just an example17:24
sean-k-mooneyfor big things perhaps17:24
sean-k-mooneybut in general that feels pretty heavy weight17:25
bauzasdansmith: oh, yeah, got it17:25
dansmithsean-k-mooney: well, I think it's in line with how we've handled things like virt/xen17:25
dansmithand n-net certainly had looots of time between effective death and removal :)17:25
bauzasyeah I see17:25
sean-k-mooneyright but that means things like the rpc proxy shoudl not be removed for 3-4 cycles17:26
bauzaswe can remove things in a tock release as ops would catch up on it on the next tick release17:26
sean-k-mooneyor reshapes which granted we have nver removed yet17:26
bauzassean-k-mooney: like the RPC compatibilities17:26
sean-k-mooneyits not just deprecation it affect17:26
bauzaswe can technically drop RPC compat on a tock release, it's just ops won't get it in effect until the next tick17:27
sean-k-mooneyso this feels abit like longer release cycles by stelth in a way that i am not sure is sustainable17:27
dansmithsean-k-mooney: it is like that, and not by stealth17:27
dansmiththe whole point of this was to strike a balance17:28
sean-k-mooneyya which this does not really do17:28
dansmiththe benefit here over longer cycles is that, deprecation aside, we can release *features* every cycle :)17:28
dansmithand we can deliver code, fixes, changes to people more often than once a year17:28
bauzasdansmith: but I guess we'd think of forward porting the relnotes to the next tick release ?17:28
sean-k-mooneyyes17:28
dansmithbauzas: I'd say just prelude items17:29
bauzasdansmith: a good reno tooling opportunity 17:29
dansmithbauzas: i.e. anything major enough to make it into prelude in a tock is candidate for tick17:29
sean-k-mooneybut we are addign teh cost of maintianing things we want to deprecate and remove for 2-3 release instead of just one to two17:29
dansmithsean-k-mooney: yep, this is not free for sure.. but it's benefit to people, which has a cost17:29
gmannwhich is what we do in most of the case currently 17:29
sean-k-mooneylike 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 it17:29
bauzasdansmith: this sounds reasonable, I need to see how to split the prelude in multiple patches17:30
bauzasdansmith: so we could forward port the big prelude patch to the next release17:30
dansmithbauzas: or just manually copy the items.. I don't think you need to get too sophisticated :)17:30
bauzasare you asking copy/paste ? man !17:30
sean-k-mooneybauzas: actuly i think we want reno to know what tick and tock releases are17:31
sean-k-mooneyand include the release notes form the previous tock in the tick17:31
dansmithsean-k-mooney: personally, I wouldn't do that17:31
sean-k-mooneyno17:31
dansmithI think that's a mistake17:31
sean-k-mooneywhy ?17:31
dansmithdon't make them read double the release notes, as compiled by a computer17:31
dansmithbring forward the important bits (i.e. likely the content of the prelude)17:32
sean-k-mooneyan operator goign form tick 1 to tick 2 need to know everythign that happend in tock 1 right17:32
dansmiththey can read the intermediate release notes if they want, but don't just concat them17:32
sean-k-mooneyi guess17:32
sean-k-mooneyi hate having to look in mulitple places17:32
gmannwe can add a line in the top or so that 'to know all change from tick1->tick2 read these tock releasenotes too'17:32
dansmithjust MHO, but I think we're already incredibly verbose on the renos17:32
sean-k-mooneybut you coudl do it either way17:32
sean-k-mooneydansmith: i mean perhaps prelude and upgrades section maybe17:33
sean-k-mooneyi guess we will figure it out17:33
gmannwill there be any upgrade section in tock? i mean we want to avoid those like depreaction right17:33
dansmithgmann: sometimes features bring upgrade items I think17:33
sean-k-mooneygmann: there should be17:34
sean-k-mooneygmann: i really dont thinik we shoudl try to avoid either in a tock17:34
gmannah new feature. got it17:34
sean-k-mooneyif we do it will slow down devleopment17:34
sean-k-mooneygmann: addin a db migraition for a new feature woudl be an upgrade impact i coudl see in a tock17:34
dansmithsean-k-mooney: remember this is a compromise, some things will have to change.. hopefully less with this than the alternative17:35
gmannmaking 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 fine17:35
dansmithgmann: agree17:35
sean-k-mooneydansmith: right but if we cant do db changes in a tock or rpc change for example then tha tis not a compromise17:35
* sean-k-mooney not that we have really done db change in a few releases17:36
dansmithsean-k-mooney: as noted, I think it's totally fine to *add* things to db and rpc in tock17:36
bauzasyup17:38
bauzaswe can rpc bump things in a tock17:39
bauzasif we have rpc compat of courser17:39
bauzaswe can add a db upgrade script too17:39
bauzaswe can even remove a rpc compat on a tock release if compat was there on the previous tick17:40
bauzasrpc aliases will continue to exist17:40
bauzasand microversions too17:40
bauzasbut somehow we need to settle a couple of rules we gonna write on our contrib docs17:41
bauzasthat's why I want us to agree on the impacts for nova so we can write it down17:41
gmannbauzas: +1.17:42
gmannbauzas: sean-k-mooney added it on TC+PTL slots, L27 - https://etherpad.opendev.org/p/tc-ptl-interaction-zed17:43
sean-k-mooneygmann: thanks17:45
sean-k-mooneybauzas: yes we have time to figure that out before AA17:45
sean-k-mooneyok 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 evning17:53
opendevreviewSylvain Bauza proposed openstack/nova master: Add the Yoga prelude section  https://review.opendev.org/c/openstack/nova/+/83229217:53
bauzasgmann: dansmith: melwitt: sean-k-mooney: gibi: new revision for the Yoga prelude ^17:54
gibibauzas: +2 from me17:55
gibithanks for writing it up17:55
bauzasthanks17:55
* bauzas goes off17:55
dansmithbauzas: looks good content-wise to me, but a bunch of nit corrections17:58
opendevreviewribaudr proposed openstack/python-novaclient master: Microversion 2.91: Support specifying destination host to unshelve  https://review.opendev.org/c/openstack/python-novaclient/+/83165118:08
*** sfinucan is now known as stephenfin19:03

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!