Tuesday, 2024-05-14

opendevreviewmelanie witt proposed openstack/nova-specs master: Re-propose specs for ephemeral encryption  https://review.opendev.org/c/openstack/nova-specs/+/90765405:23
opendevreviewmelanie witt proposed openstack/nova-specs master: Re-propose specs for ephemeral encryption  https://review.opendev.org/c/openstack/nova-specs/+/90765405:45
gibibauzas: I'm not sure you saw it in the last weeks meeting log that we discussed https://blueprints.launchpad.net/nova/+spec/shared-security-groups as a specless bp. The cores present had no objection to approve it but we agreed to wait for you to have a final word on it and approve it if it is OK to you too07:19
gibirelevant meeting log https://blueprints.launchpad.net/nova/+spec/shared-security-groups07:20
bauzasgibi: I haven't yet looked at last week's meeting07:20
gibihttps://meetings.opendev.org/meetings/nova/2024/nova.2024-05-07-16.00.log.html#l-3407:21
bauzasbtw. today is a specs review day07:21
bauzasgibi: ack, I'll accept it then07:21
gibithanks07:21
opendevreviewMerged openstack/nova stable/2024.1: [ironic] Fix rebooting instance  https://review.opendev.org/c/openstack/nova/+/91818009:52
opendevreviewMerged openstack/nova-specs master: Repropose per-process-healthchecks for Dalmatian  https://review.opendev.org/c/openstack/nova-specs/+/91905009:57
opendevreviewMerged openstack/nova-specs master: Update and Re-propose "Allow Manila shares to be directly attached to an instance when using libvirt" for Dalmatian  https://review.opendev.org/c/openstack/nova-specs/+/91399709:57
sahido/10:02
opendevreviewsean mooney proposed openstack/nova master: use futerist for RBD calls  https://review.opendev.org/c/openstack/nova/+/91796211:13
gibidansmith: when you are around I'm wondering if you were part of the userdata discussion during the PTG as I see discrepancies here https://review.opendev.org/c/openstack/nova-specs/+/863884/7#message-e1f200505bbf81d0b9a254c4634f6fdc477871dd11:34
sean-k-mooneyim kind of having a hard time reading and parsing sepcs today so i think im oging to stop unless some one asks me specific for input on somethign11:56
opendevreviewKonrad Gube proposed openstack/nova master: Use Cinder's os-extend_volume_completion volume action.  https://review.opendev.org/c/openstack/nova/+/87356012:03
opendevreviewTakashi Kajinami proposed openstack/nova-specs master: libvirt: Stateless firmware support  https://review.opendev.org/c/openstack/nova-specs/+/90829712:13
opendevreviewMerged openstack/nova-specs master: libvirt: Stateless firmware support  https://review.opendev.org/c/openstack/nova-specs/+/90829713:01
opendevreviewStephen Finucane proposed openstack/placement master: Add placement.wsgi.api module  https://review.opendev.org/c/openstack/placement/+/91956913:24
opendevreviewTakashi Kajinami proposed openstack/nova-specs master: libvirt: AMD SEV-ES support  https://review.opendev.org/c/openstack/nova-specs/+/90770213:35
ykarelHi reported https://bugs.launchpad.net/nova/+bug/2065689 and https://bugs.launchpad.net/nova/+bug/2065693, please check if in case those are something known already13:40
dansmithbauzas: gibi: can you guys land this quick? it's blocking a devstack performance improvement: https://review.opendev.org/c/openstack/nova/+/91868913:41
dansmithit's trivial13:41
dansmithgibi: we had some discussion about it yeah, I can have a look13:42
bauzasdansmith: ack13:42
dansmithgibi: hmm, yeah I feel like some context is missing from the PTG summary.. I thought there was a different conclusion reached about what to do, but now I'm not sure what that is.. maybe bauzas remembers?13:48
* bauzas looks13:51
bauzasgibi: dansmith: I think we said the owner provided the right version eventually about our concerns13:58
gibidansmith: if you are OK to use the RPC cast to trigger the regeneration of the config drive instead of having a flag in sysmeta and do the regeneration at spawn then I'm OK with it. But reading back on the comments I felt that you regen at spawn idea was not discussed at the PTG14:08
dansmithgibi: no, it can't be a cast, right?14:12
opendevreviewStephen Finucane proposed openstack/placement master: tox: Remove envdir overrides  https://review.opendev.org/c/openstack/placement/+/91957814:13
opendevreviewStephen Finucane proposed openstack/placement master: Integrate pre-commit  https://review.opendev.org/c/openstack/placement/+/91957914:13
opendevreviewStephen Finucane proposed openstack/placement master: pre-commit: Add sphinx-lint  https://review.opendev.org/c/openstack/placement/+/91958014:13
gibiI think it is propsed as a cast now, and the compute sets the result of the instance action based on the success / failure of the regen14:13
gibithe nova-api can check the compute version but should not wait for the regen to happen via an RPC call14:14
gibias regen takes time14:14
opendevreviewsean mooney proposed openstack/nova master: add initial healthcheck support  https://review.opendev.org/c/openstack/nova/+/82501514:14
opendevreviewsean mooney proposed openstack/nova master: add healthcheck manager to manager base  https://review.opendev.org/c/openstack/nova/+/82784414:14
opendevreviewsean mooney proposed openstack/nova master: add healthcheck tracker to nova context  https://review.opendev.org/c/openstack/nova/+/82946814:14
opendevreviewsean mooney proposed openstack/nova master: add healthcheck endpoint to proxy commands  https://review.opendev.org/c/openstack/nova/+/83070314:14
opendevreviewsean mooney proposed openstack/nova master: [WIP] add iniital health check to compute agent  https://review.opendev.org/c/openstack/nova/+/90691114:14
opendevreviewsean mooney proposed openstack/nova master: [WIP] add libvirt connection healtcheck  https://review.opendev.org/c/openstack/nova/+/90742414:14
dansmithokay but then we've told the http client "yes, we will do that thing" even though it might show up at the compute that has no idea what to do with it14:15
gibiif the service version of the compute is old the the API can fail the instance action, but if the service version is new enough then the api can cast down to the compute to ask for the regen14:16
gibi(except for shelved_offloaded instances)14:16
gibiat least this is how I understand the PTG notes and the spec now14:16
dansmithokay I haven't re-read it this morning yet14:19
bauzasI'll try to review it too today14:20
bauzasbut that's an old spec14:20
gibiit was revised around the PTG so the content is fairly fresh14:22
opendevreviewStephen Finucane proposed openstack/placement master: Add placement.wsgi.api module  https://review.opendev.org/c/openstack/placement/+/91956914:22
opendevreviewStephen Finucane proposed openstack/placement master: setup: Remove pbr's wsgi_scripts  https://review.opendev.org/c/openstack/placement/+/91958214:22
gibiDoes anybody remember why we name our db contraints like uniq_key_pairs0user_id0name It feels like there is a reason for that specific structure but I never come accross the explanation14:25
gibihttps://github.com/openstack/nova/blob/7096423b343ffce9622fd078fc2b3a87fd3386f7/nova/db/api/models.py#L308-L31014:25
dansmithyeah I think there was a reason, but it might have just been "consistency"14:31
bauzasindeed14:45
gibiOK, then I ask Uggla_ to follow the pattern just for consistency14:56
gibihere https://review.opendev.org/c/openstack/nova/+/912518/2/nova/db/main/models.py#76714:56
Uggla_gibi, ok15:03
stephenfinfyi the sqlalchemy 2.x bump *finally* merged, so if you want to free up some resources we can merge these now https://review.opendev.org/c/openstack/nova/+/915562 https://review.opendev.org/c/openstack/placement/+/91556815:04
ykarel#topic Stable branches15:10
ykarelall good15:10
ykarel#topic Stadium projects15:10
ykarelall green15:10
ykarel#topic Rechecks15:10
ykarel6/14 bare rechecks15:10
fricklerykarel: wrong channel?15:10
ykarelahh right15:11
ykarelthx frickler 15:11
opendevreviewGorka Eguileor proposed openstack/nova master: Support os-brick specific lock_path  https://review.opendev.org/c/openstack/nova/+/84932815:16
bauzasnova meeting in 30 mins 15:32
opendevreviewTakashi Kajinami proposed openstack/nova-specs master: Remove template files from non-empty directories  https://review.opendev.org/c/openstack/nova-specs/+/91959715:33
bauzasgibi: shit, I forgot I'll need to travel to the French OpenInfra Day in Paris on next Tuesday15:56
bauzasso I couldn't be able to run the meeting15:56
gibibauzas: I will be off on next Tuesday15:59
bauzasno worries, I'll ask in our meeting today15:59
bauzas#startmeeting nova16:01
opendevmeetMeeting started Tue May 14 16:01:17 2024 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
opendevmeetThe meeting name has been set to 'nova'16:01
bauzashey folks16:01
tkajinamo/16:01
elodilleso/16:01
fwieselo/16:02
gibio/16:02
Uggla_o/16:02
bauzasokay, let's softly start16:02
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:02
bauzas#topic Bugs (stuck/critical) 16:03
bauzas#info No Critical bug16:03
bauzas#info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster16:03
bauzasanything important to tell about bugs ?16:03
bauzaslooks not16:03
bauzas#topic Gate status 16:04
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:04
bauzas#link https://etherpad.opendev.org/p/nova-ci-failures-minimal16:04
bauzas#link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status16:04
bauzas#info Please look at the gate failures and file a bug report with the gate-failure tag.16:04
bauzas#info Please try to provide meaningful comment when you recheck16:04
tkajinamjust fyi. global u-c was updated and sqlalchemy was bumped to 2.0. I don't expect any problems with core services since sqlahcmely 2.0 has been tested for some time, but we may need to pay some attention to gate.16:05
* bauzas still awaits Zull to provide me the peridic jobs 16:05
bauzasokay, all of the perodics are green, even the nova-emulation one16:05
dansmitho/16:05
sean-k-mooneythe emultaion one was just being OMM killed16:06
sean-k-mooneyso it can pass currently i have a patch to correct that 16:06
bauzasoh, for the moment, the latest master job for nova-emulation was still failing16:06
bauzaswe'll see it next week then16:06
bauzasdo people want to discuss about the guest kernel issues now or not  ?16:07
sean-k-mooneyjust an fyi https://review.opendev.org/c/openstack/nova/+/918464 is the fix for the emulator job16:08
sean-k-mooneyregarding panics16:08
sean-k-mooneyim not sure i have seen them get any worse but i know dansmith wants to try reverting the way we define the glance images16:08
sean-k-mooneydansmith: did you have time to push a patch for that16:08
bauzasokay16:08
dansmithno, I need to do that still16:09
sean-k-mooneyack if you dont get around to it by the next meeting ill push a patch to do it16:09
bauzaskk16:10
bauzasmoving on then16:11
bauzas#topic Release Planning 16:12
bauzas#link https://releases.openstack.org/dalmatian/schedule.html16:12
bauzas#link https://review.opendev.org/c/openstack/releases/+/918422 nova specific schedule is proposed16:12
bauzasI saw sean-k-mooney's comment, I'll provide a new revision16:12
bauzas(but fwiw, we discussed it on the PTG)16:12
bauzas#info Dalmatian-1 this week16:12
bauzas#info Spec review day is today16:12
bauzasI started to review some specs and I saw also some other comments16:13
bauzasthanks to the folks that already started to review <316:13
bauzas#topic Review priorities 16:13
bauzas#link https://etherpad.opendev.org/p/nova-dalmatian-status16:13
bauzastomorrow, I'll modify the etherpad by adding the new series related to the specs that will be merged today16:14
bauzas#topic Stable Branches 16:15
bauzaselodilles: hehe16:15
bauzas\o16:16
elodilles~o~16:16
elodilles#info all stable gates are OK (stable/2024.1, stable/2023.2, stable/2023.1) as grenade jobs are fixed and passing16:16
elodilles#info stable nova versions released: nova 28.1.0 (2023.2 Bobcat), nova 27.3.0 (2023.1 Antelope)16:16
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:16
elodillesthat's all for today :)16:16
bauzascool16:19
bauzas#topic vmwareapi 3rd-party CI efforts Highlights 16:19
elodillescool indeed16:19
bauzasfwiesel: anything to tell ?16:19
fwieselNot much...16:19
fwiesel#info Sync script in place. CI working through the backlog.16:20
sean-k-mooneyis https://review.opendev.org/c/openstack/nova/+/910627 the next patch on your review list16:20
fwieselSo, if you do not see any messages, it is because of that.16:20
fwieselsean-k-mooney: Yes, that would be the next one. That should cut down the errors to one, IRC.16:20
bauzasok16:21
fwieselThat would be from my side, unless there are more questions.16:21
bauzasnot from me 16:21
bauzascool16:21
bauzasand thanks16:21
bauzas#topic Open discussion 16:22
bauzasI have one item16:22
sean-k-mooneyi also have one but i can wait16:22
bauzasnext Tuesday, I'll be on a train when the meeting starts16:22
bauzas(going to the OpenInfra Day in Paris)16:22
bauzasso anyone happy to lead the meeting ?16:22
bauzasif not, we'll just punt it to the next week16:23
JayFHey, can16:23
JayFwhoops, one thing16:23
JayFCan https://blueprints.launchpad.net/nova/+spec/ironic-guest-metadata be re-approved for Dalmation?16:23
bauzasJayF: you're next in queue after sean-k-mooney's point :)16:23
bauzaswe're on meeting now :)16:24
bauzasso, anyone volunteering for running the meeting next week ?16:24
sean-k-mooneybauzas: if we dont have anything urgent i think we can skip next week16:24
bauzasno worries, then we'll skip it16:24
sean-k-mooneylets do JayF point first16:24
sean-k-mooneyim fine with reappoving that16:24
bauzas#agreed next nova meeting on May 21 is CANCELLED16:24
bauzas#action bauzas to communicate about the cancellation 16:25
bauzasokay, done for my item16:25
bauzasnext one then, Jay16:25
andrewbonneyOne query on bugs if I could too after others16:25
sean-k-mooneyandrewbonney: sure. JayF  do you want to summerise16:25
bauzasJayF: I don't see anything controversial with reapproving https://blueprints.launchpad.net/nova/+spec/ironic-guest-metadata as specless16:25
JayFthank!16:26
JayF*thanks16:26
bauzasmost of my concerns come with testing this, but this is not related to the blueprint itself16:26
bauzasanyone having concerns with reapproving ^ as specless ?16:26
bauzasspeak now or forever hold your peace16:27
bauzasokay, I'll do the paperwork stamp16:27
bauzas#agreed https://blueprints.launchpad.net/nova/+spec/ironic-guest-metadata reapproved as specless for Dalmatian16:27
bauzasnext one, who's this ? sean-k-mooney I think ?16:28
sean-k-mooneyso hopefully my item will be jsut as quick16:28
sean-k-mooneyhttps://blueprints.launchpad.net/nova/+spec/eventlet-removal-part-116:28
sean-k-mooneycan we appove that as specless16:28
sean-k-mooneyi mostly have it implmeneted16:28
dansmiththe critical bits are the implementation details,16:29
sean-k-mooneythere is some feedback form stephen on the implmentaion but i think it will be ready for review next week16:29
dansmithso I think it's reasonable to call this cleanup/maintenance and focus on the actual code, IMHO16:29
dansmithi.e. no API or RPC or DB changes, just internals16:29
bauzasyeah I think we said it's just for tracking16:29
bauzastracking progress and adding it to our review eyes16:29
sean-k-mooneycool well the patches are avaiable for review here https://review.opendev.org/q/topic:%22eventlet-removal-part-1%2216:29
bauzasI'm fine with approving it then as specless and I think we even agreed on that at the PTG16:30
sean-k-mooneyyep16:30
bauzasokay,16:30
bauzas#agreed https://blueprints.launchpad.net/nova/+spec/eventlet-removal-part-1 accepted as specless blueprint as agreed during the PTG16:30
sean-k-mooneyi belive andrewbonney had a question around a bug?16:30
sean-k-mooneyassuming there was nothign else on the adgenda16:31
andrewbonneyThanks. Just a procedure thing really. I have a few reports since March and just wanted to check if I should be following up here generally or in meetings for feedback?16:31
andrewbonneyI appreciate you get a lot so just trying to do the right thing16:31
sean-k-mooneyas in you filed a number of bug reporst since march?16:32
andrewbonneyYeah that's right, https://bugs.launchpad.net/nova/+bugs?field.bug_reporter=andrewbonney16:32
sean-k-mooneyand you want to knwo if they have been looked at or how to progress them16:32
andrewbonneySure. For maybe one I could propose a patch, but generally they need review from those more familiar with the codebase16:33
bauzasandrewbonney: we agreed on previous PTG that we can't really triage the new bugs every week as we lack volunteers and time for that16:33
andrewbonneySure16:33
sean-k-mooneylooking at the first one https://bugs.launchpad.net/nova/+bug/2058725 sound familar and im trying to recall if it was intentional16:34
bauzasunfortunately, we then let the reporters to communicate to us any bug in particular they could consider as critical16:34
bauzasandrewbonney: for the other bugs that are less important, our channel is always open for discussion and you shouldn't be afraid of pinging ourselves16:34
gibiandrewbonney: if you could try to push a test case that reproduces the issue in unit or functional test env would greatly increas the chance that we get to it16:35
bauzassome people usually bug ourselves in this chat, asking either for reviews, help or categorisation16:35
opendevreviewStephen Finucane proposed openstack/nova-specs master: Follow-up for openapi spec  https://review.opendev.org/c/openstack/nova-specs/+/91960316:35
andrewbonneyThanks, just don't want to annoy16:36
sean-k-mooneyits fine. https://bugs.launchpad.net/nova/+bug/2065403 sound like you are not running it in a loop until completion16:37
sean-k-mooneyalthough the interaction with -max-count problmeatic16:37
andrewbonneyI think the default behaviour does run in a loop, that's where the problem lies. With max-count it doesn't run in a loop as far as I can see16:37
bauzasif people agree, we can close the meeting now and let people to discuss about andrewbonney's bug reports just after16:38
sean-k-mooneysure16:38
bauzascool16:39
bauzasthanks all then16:39
bauzas#endmeeting16:39
opendevmeetMeeting ended Tue May 14 16:39:38 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:39
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2024/nova.2024-05-14-16.01.html16:39
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2024/nova.2024-05-14-16.01.txt16:39
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2024/nova.2024-05-14-16.01.log.html16:39
opendevreviewMerged openstack/nova master: Upload glance image with --file in ceph job  https://review.opendev.org/c/openstack/nova/+/91868916:40
fwieselThanks16:41
sean-k-mooneyhum  29147 instnace in batches of 50. i wonder if we are missing a marker/stable order16:41
andrewbonneyI was wondering why populate_instance_compute_id relied on exception handling rather than checking for 'node' presence in the initial DB query, but there may be good reasons16:45
andrewbonneyThe fact there's no DB cursor means it hits the same un-migratable records on each iteration16:46
sean-k-mooneywell node here https://opendev.org/openstack/nova/blame/commit/7096423b343ffce9622fd078fc2b3a87fd3386f7/nova/objects/instance.py#L136616:47
sean-k-mooneyis not coming form the instnace16:47
sean-k-mooneythat is looking up the compute node record16:48
sean-k-mooneyinstnace.node i think is the compute node name16:49
dansmithyeah I don't understand the question.. we're not "relying" on exception handling for anything in that code16:49
dansmith... and we do loop ...16:50
sean-k-mooneymy incliantion is to say that of the 30k instances a large proporation fo those recored are for deleted instnaces?16:51
sean-k-mooneythats a guess16:51
andrewbonneyYes that's right16:51
andrewbonneyI think this is only an issue where lots of records are not running instances16:51
andrewbonneyDo you end up in a state where the method exits because the first 50 records returned by the DB don't qualify for migration, which triggers the end of the loop16:52
andrewbonney*So16:52
sean-k-mooneyso a workaround in that case would be to run nova-manage archive-deleted-rows16:52
dansmithsorry I missed something, what is the issue ?16:52
sean-k-mooneywhen they run the commadn its printing "50 rows matched query populate_instance_compute_id, 6 migrated"16:53
dansmithoh I see above, you're expecting to be able to run just --max-count $number_of_active_instances ? 16:53
sean-k-mooneyhttps://bugs.launchpad.net/nova/+bug/206540316:53
dansmithyeah I mean you have to run those things untll they're done16:53
dansmithsometimes we can skip records that are deleted and other times we can't really16:54
andrewbonneyWe ran without max-count initially as part of a standard upgrade. It completed, but hasn't migrated everything because once the first 50 records are unsuitable it exits16:54
andrewbonneyI only realised our first deployment was in this state because I noticed the migration taking ~15 mins plus on a second deployment, because it keeps trying to migrate unsuitable records16:54
dansmithah, I see because you have a bunch of (hopefully deleted) instances that point to missing compute nodes?16:55
andrewbonneyYeah that's it16:55
dansmithgotcha16:55
andrewbonneyHappy to work around it for us, but I doubt we'll be the only ones to hit it16:55
sean-k-mooneyso just looking at our docs https://docs.openstack.org/nova/latest/cli/nova-manage.html#db-online-data-migrations16:55
sean-k-mooneywe state that if you dont pass --max-count16:56
dansmithyeah, I'm not sure the best way to handle that in the context of how that manage command works16:56
sean-k-mooneywe will loop internanlly in batchs of 5016:56
dansmithyeah, but we don't have marker stuff there to prevent us from looping over the same 50 over and over16:56
sean-k-mooneybut if you do pass --max-count you have to loop externally and look at the repsoce code16:56
sean-k-mooneywell we dont actully need that16:56
dansmithso I mean, we could just ignore deleted instances, but that means we may have a problem adding a constraint later where this will come up again16:57
sean-k-mooneysince we only get instnace that dont have the compute_id set16:57
sean-k-mooneybut the issue is we are not settign a sentinel for those that dont match16:57
dansmithright but the problem is that if the 50 are not migratable, we'll never mark them as identified and keey finding them16:57
dansmithyeah16:57
sean-k-mooneyso we need to set it to all 0  or something like that16:57
dansmithI mean, that's one way to go, but it's not really reasonable I think16:57
dansmithbecause that makes it not an FK16:57
sean-k-mooneyoh right ya it would fail the FK check16:58
sean-k-mooneycan we return the instance uuid as a marker if we add an orderby 16:58
dansmithI mean, it's not marked as an FK right now, because we suck at that, but still, it's "wrong" I think16:58
dansmithright, so we could add in marker stuff there, but that's kindof a bigger deal really16:59
dansmithchanges the interface of all of these migration routines16:59
sean-k-mooneywell it woudl need a new cli arg for a start and it woudl chnage the resonce so not backporable16:59
dansmithone thing we could do is if we get to the bottom of this loop and couldn't migrate any of the things we found, just raise an exception and say "yo dawg, you need to archive your db"17:00
dansmithit's not a CLI thing so much as the interface for these migration functions17:00
dansmiththey all return all,hit right now17:00
dansmithI need to be reviewing the monster EE spec, so let's just table this and I17:01
dansmithwill do some thinking on it later17:01
andrewbonneyThanks for the time17:03

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