Tuesday, 2024-04-16

opendevreviewAmit Uniyal proposed openstack/nova master: DNM: test evacuation  https://review.opendev.org/c/openstack/nova/+/91592305:49
*** elodilles_pto is now known as elodilles07:17
opendevreviewKien Nguyen proposed openstack/python-novaclient master: support get and list server's metadata  https://review.opendev.org/c/openstack/python-novaclient/+/91597709:23
opendevreviewAmit Uniyal proposed openstack/nova master: DNM: test evacuation  https://review.opendev.org/c/openstack/nova/+/91592311:27
sean-k-mooneyauniyal: ^ fyi when you create DNM patches like that its better to disable the jobs that you dont need to save ci resouces11:33
dansmithgibi: I cc'd you but just in case it's under a mountain of other notification emails, I'm looking for pre-approval on this method of determining the trailing threshold: https://review.opendev.org/c/openstack/nova/+/915911/113:50
dansmithfrom our version support discussion13:50
dansmithjust the algorithm for picking the version, and then I'll flesh out everything else13:51
auniyalsean-k-mooney ack, but I am not sure how to disable jobs, 14:01
auniyalby doing -1 to workflow ?14:02
auniyalits a depends-on patch, so I do not really need to run any job in nova-ci for this14:03
dansmithauniyal: by commenting out or removing jobs from the .zuul14:05
auniyaldansmith, ack, thanks14:06
auniyalyeah, I knew workflow is stop stop merging, but thought may it also work for jobs14:06
samcat116Hi all, I seem to be hitting the following issue pretty consistently on a 2023.2 deployment: https://bugs.launchpad.net/nova/+bug/1931707. Specifically when trying to delete a large number of instances with many ports attached to each at once. For instance on the last run we had computes with over 100 vms on a given compute node with 10 ports on each vm. Out of our deletion of about 100 vms, over 150 went into error due to this14:06
samcat116reason. I've also seen the error on vm creation, but much less common. Not sure if there's anything I can do to debug further.14:06
gibidansmith: thanks for the ping, otherwise I would have missed the patch14:06
dansmithgibi: no problem and no big rush, just wanted to at least get some agreement while things are still fresh14:08
auniyaldansmith, its okay to comment whole file right ?14:09
dansmithauniyal: probably not, and obviously not if you want to run *any* tests14:14
dansmithauniyal: sean-k-mooney was likely suggesting you comment out all but the tests you want to run on your WIP14:14
auniyalack14:20
sean-k-mooneydansmith: auniyal yes14:20
erlonsean-k-mooney: hey, can you give a look on the RBAC change (https://review.opendev.org/c/openstack/nova/+/811521) again when you have a chance?14:21
erlonI was trying to add some core reviewers to the list as well, but I don't know how to find them anymore. It use to be in the project groups, core-reviewers, but now there's a lot of groups.14:23
sean-k-mooneysure i see you created a blue print for it14:28
sean-k-mooneyso we still need to approve that in the nova team meeting14:28
sean-k-mooneyi dont really have any objection to enabing this as a specless blueprint14:28
erlonThe other thing I was wondering, is the likelihood of this being backported. The fact that it has a blueprint, make it sounds like there's a feature which this is not, but might raise some eyebrows14:33
erlonThe next meeting will be only next week right? Do I need to add the top in the agenda? Or there's already a slot for review requests14:42
erlonsean-k-mooney: ^14:42
dansmitherlon: sounds like a feature to me, FWIW14:46
kashyapgibi: When you get a min, can you look at this (needs to reload some context, though): https://review.opendev.org/c/openstack/nova/+/89918514:50
sean-k-mooneydansmith: erlon yes this is a feature and not something that is upstrema backporable14:51
*** efried1 is now known as efried15:19
*** haleyb_ is now known as haleyb15:27
gibikashyap: I remember we discussed doing that change in the past but I don't know where it is stopped, what is the next step there?j15:31
kashyapgibi: The next step is discussed in the bug you filed: https://bugs.launchpad.net/nova/+bug/203980315:41
bauzasreminder : nova meeting here in ~20 mins15:41
kashyapgibi: Our aim is ge this fixed with as less churn as possible15:42
gibikashyap: OK your comment https://bugs.launchpad.net/nova/+bug/2039803/comments/2 make sense15:49
kashyaps/ge/to get/15:50
kashyapgibi: Okay, please also give a quick look at the draft patch.  Tomm; not tonight, it requires to load up on the context15:51
sean-k-mooneyso why is this listed as a bug15:52
sean-k-mooneyto me this is a feature15:52
sean-k-mooneyits technial debth15:52
sean-k-mooneybut i dotn thinkw e woudl backport this right15:52
sean-k-mooneyi mean we shoudl not eb breakign live migration by calling the worng api15:53
sean-k-mooneybut im nnot sure how i feel about changign all those libvirt api methods in somethign we would backport15:54
sean-k-mooneyi would epect the test fallout to be non trivial15:54
sean-k-mooneyalthough i guess we coudl see what it looks like and make the deicsion about if this could be backported later15:54
kashyapYeah, we don't want to update all those methods.  If you see the WIP patch, it's targetted as a bug fix15:55
sean-k-mooneyi saw all the red ci jobs15:56
kashyapThat comment is just written to show what we've already considered and eliminated.15:56
sean-k-mooneyi briefly skimmed it15:56
sean-k-mooneythe ci jobs logs all rotated so this need a rebase at a minium15:56
kashyap(Just on the bug comment: we shouldn't update all those methods.  And not all those methods listed there make sense in this context.)15:57
kashyapYeah, needs a rebase for sure.15:57
kashyapThank you for looking (even if it's skimming)15:58
sean-k-mooneythe change is basically s/host_cpu = self._host.get_capabilities().host.cpu/host_cpu = self._host.get_domain_capabilities().host.cpu/15:59
sean-k-mooneythe side effect being that domain caps the new api also has awareness of what the qemu instance on the host can emulate ectra16:00
sean-k-mooneyso we will be useing the capablity of the cpu that woudl be presented to the guest16:00
sean-k-mooneyrather the hte host caps16:00
bauzas(meeting now)à16:00
bauzas#startmeeting nova16:00
opendevmeetMeeting started Tue Apr 16 16:00:53 2024 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
bauzashowdy folks16:01
dansmitho/16:01
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:01
elodilleso/16:01
auniyalo/16:01
sean-k-mooneyo/16:01
bauzaslet's try to have a short meeting, I could have someone going to my home around 4.30pm16:02
bauzas#topic Bugs (stuck/critical) 16:02
bauzas#info No Critical bug16:02
bauzas#link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 74 new untriaged bugs (+7 since the last meeting)16:02
bauzasI definitely need to do what we agreed on the PTG :)16:02
bauzas#info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster16:03
bauzasso,16:03
bauzas#info bug baton is ?16:03
elodilleso/16:03
bauzasanyone wanting to take the baton ?16:03
elodillesi can volunteer16:03
bauzascool thanks16:03
bauzas#undo16:03
opendevmeetRemoving item from minutes: #info bug baton is ?16:03
bauzas#info bug baton is for elodilles16:03
bauzaselodilles: <316:03
bauzasmoving on16:04
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
bauzasall greens16: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
bauzasvoila16:04
bauzasany gate failure you had found ?16:04
bauzasokayokay16:05
bauzas#topic Release Planning 16:05
bauzas#link https://releases.openstack.org/dalmatian/schedule.html16:05
bauzas#info Dalmatian-1 in 4 weeks16:05
bauzas#action bauzas to add the nova deadlines in the Dalmatian schedule page16:05
bauzas#topic vPTG Summary 16:06
bauzas#info The vPTG was held on Apr 8-1216:06
bauzas#link https://etherpad.opendev.org/p/nova-dalmatian-ptg Topics that were discussed16:06
bauzas#action bauzas to provide a summary this week16:06
bauzasanything people want to discuss about the vPTG ?16:07
bauzaslooks not16:07
bauzas#topic Stable Branches 16:07
bauzaselodilles: heya16:07
elodillesnothing news actually16:08
elodilleszed branch is still broken due to nova-ceph-multistore job :/16:08
elodillesother maintained branches' gates are in OK state16:09
bauzaskk16:09
bauzas#topic vmwareapi 3rd-party CI efforts Highlights 16:09
bauzasfwiesel: are you here?16:09
fwieselYes, sorry for being late.16:10
fwiesel#info No updates16:10
bauzascool no worries16:10
bauzas#topic Open discussion 16:10
bauzasanyone ?16:10
bauzasI don't see any item in our page16:10
sean-k-mooneyi had one thing16:11
bauzasshoot16:11
sean-k-mooneyfwiesel: you have and had some patches up for vmware for a while16:11
sean-k-mooneywe might want to try an cordiante soem review of those16:11
sean-k-mooneyas otherwise i feel like they are just going to bitrot16:12
fwieselsean-k-mooney: That would be great.16:12
sean-k-mooneyim not really sure how to go about that othe rthen perhapsp tryign to use the review etherpad but im not sure if we have a new one for 2024.216:12
sean-k-mooneybauzas: have you created one?16:12
bauzassean-k-mooney: yes, see above ^16:13
bauzasoh f... I forgot a topic :)16:13
bauzas#link https://etherpad.opendev.org/p/nova-dalmatian-status16:13
sean-k-mooneydo we want to say chosse one to review before week or perhaps have a prioritesed list16:13
opendevreviewKashyap Chamarthy proposed openstack/nova master: libvirt: Avoid getCapabilities() to calculate host CPU definition  https://review.opendev.org/c/openstack/nova/+/89918516:13
Uggla_o/16:14
fwieselThe most important one would be the image import... as otherwise you cannot boot an instance :)16:14
fwieselShall I add it then to the etherpad?16:14
sean-k-mooneyack can you add that on eto the ether pad16:14
fwieselOkay, I will.16:14
bauzassean-k-mooney: we said in the PTG that we'll ask folks to ask to have feature liaisons16:14
sean-k-mooneyplease do and perhaps we should add a vmware dirver section to list the in order of priority16:14
bauzassean-k-mooney: sure, we could organize a specific section16:15
bauzasare we done with that ?16:15
sean-k-mooneyso the thing is currently non of the core team really know how that driver works in detail an di feel like if fwiesel does not remind us often that they are trying ot fix it we wont be encliend ot go looking to review vmware code16:16
sean-k-mooneyya that all i wanted to bring ups16:16
bauzaswell, we could create a separate etherpad for that if you want16:16
sean-k-mooneyim fine with having it in the main one16:16
bauzasor we could have some gmeet 16:16
kashyapgibi: Thanks for the rebase :)16:16
bauzasanyway, it's related to what we discussed on the PTG16:17
sean-k-mooneyi just want to make sure if i look at some of theose patches someone else will16:17
sean-k-mooneybauzas: ya i was not in those ptg dicussions16:17
sean-k-mooneyso im not aware of that discussion or if i agree with it16:17
bauzasthis cycle, we'll try to have some subteams for each of the blueprints16:17
sean-k-mooneybut i guess ill read back the notes16:17
bauzasso each of the subteam people could organiaz some gmeets if they want16:18
sean-k-mooneyok... im not sure how that is goign to work but maybe it could16:18
bauzashere, we could have some kind of '"vmware subteam"16:18
bauzasI mean, people reviewing vmware driver changes 16:19
sean-k-mooneywell i would either like to fix the dirver or delete it. both work for me but im sure fwiesel has a prefernce given the work they have done16:19
fwieselShall I get more of our people involved?16:19
bauzasfwiesel: nope, we'll softly start16:19
sean-k-mooneyfwiesel: i dont think thats need 16:19
bauzasand see how we organize ourselves16:19
sean-k-mooneywe just need some cores to say yes ill review your patchs16:19
bauzaszactly16:19
bauzasanyway I think we're done here16:20
bauzasthanks all16:20
sean-k-mooneysure let end the meetign and we can chat after16:20
fwieselThanks, have a good one.16:20
bauzas#endmeeting16:20
opendevmeetMeeting ended Tue Apr 16 16:20:38 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:20
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2024/nova.2024-04-16-16.00.html16:20
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2024/nova.2024-04-16-16.00.txt16:20
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2024/nova.2024-04-16-16.00.log.html16:20
sean-k-mooneyso i was previously, tentiitively +2 on https://review.opendev.org/c/openstack/nova/+/90947416:20
fwieselSo, how does the subteams work?16:20
sean-k-mooneywell normally the subteam has a meeting and then updtate the broader team like your already doing16:21
sean-k-mooneywe have not used subtemas out side of the stable team in a long time16:21
sean-k-mooneyit could somethign as simple as choose 15-30mins during the week to meet and disucss a given patch16:22
gibikashyap: sean-k-mooney: it is bug to me as it breaks live migration. If we decide not to backport the fix that is fine by mej16:24
gibiI will try to check the CI results on the rebase tomorrow16:25
fwieselsean-k-mooney: How does it get organised? Next Nova meeting?16:28
sean-k-mooneythat really up to the memeber of the subteam i guess. i was not part of the ptg disucssion so im not sure what bauzas had in mind16:30
sean-k-mooneybauzas: do you intend to review https://review.opendev.org/c/openstack/nova/+/90947416:30
bauzassean-k-mooney: I'm not a super expert on the glance side, but I can try to help16:32
bauzasthat said, dansmith could also have some opinions16:33
dansmithI might, but tied up right now16:34
kashyapgibi: I agree it's a bug.  I need to head out now; we can talk more tomm.16:37
fwieselI've to drop of as well. Have a good one.16:38
*** dmitriis is now known as Guest133323:06

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