Earlier  
Posted Nick Remark
#openstack-nova - 2025-02-11
14:14:21 sean-k-mooney MengyangZhang[m]: its quite common for larger clouds to do rolling uprgardes potentially over the course of several mantiance window over a period of months
14:14:52 sean-k-mooney i.e. where the operatrion team need to work with the teants to organise outages
14:15:15 sean-k-mooney not all feature in nova allow live migration for example vgpus or pci passthough
14:15:40 sean-k-mooney so depenidng on the constraitnt the admin has they may not be able to upgrade all host ot the same version at once
14:17:56 sean-k-mooney MengyangZhang[m]: https://github.com/openstack/governance/blob/master/resolutions/20220210-release-cadence-adjustment.rst describe the skip level upgrade requirments that all project must support
14:51:12 opendevreview Takashi Kajinami proposed openstack/nova master: Replace oslo_utils.encodeutils.exception_to_unicode https://review.opendev.org/c/openstack/nova/+/940619
15:30:11 gmann bauzas: can you please check this rbac spec, need 2nd +2. I would not be able to attend the meeting, in case it needs to be discussed as feature freeze exception but I think you know the context of it. I started the code change also in parallel https://review.opendev.org/c/openstack/nova-specs/+/937650
16:01:09 bauzas #startmeeting nova
16:01:09 opendevmeet Meeting started Tue Feb 11 16:01:09 2025 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:09 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:09 opendevmeet The meeting name has been set to 'nova'
16:01:32 fwiesel o/
16:01:47 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:53 sp-bmilanov hello!
16:02:06 elodilles_pto o/
16:02:46 Uggla o/
16:03:01 bauzas I guess we can softly starty
16:04:26 bauzas #topic Bugs (stuck/critical)
16:04:32 bauzas #info No Critical bug
16:04:37 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:04:45 bauzas any bugs people wanna discuss ?
16:05:41 bauzas apparently not
16:06:25 bauzas moving on
16:06:32 bauzas #topic Gate status
16:06:38 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:06:44 bauzas #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:06:57 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status
16:07:04 bauzas all periodics seem to be green
16:07:23 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:07:28 bauzas #info Please try to provide meaningful comment when you recheck
16:07:37 bauzas any gate failures to discuss ?
16:08:03 bauzas I have one actually
16:08:33 bauzas when looking at https://review.opendev.org/c/openstack/nova/+/940642, even by rechecking, I got the same exceptions on nova-next and nova-multi-cell jobs
16:08:37 bauzas for the same test
16:09:06 bauzas https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_ba0/940642/5/check/nova-next/ba009c2/testr_results.html
16:09:12 bauzas https://6ae015e4c924496dfda3-74c26bb67ca36871e200d07f3210a3f0.ssl.cf1.rackcdn.com/940642/5/check/nova-multi-cell/c2a2f68/testr_results.html
16:09:19 bauzas have people seen the same failure ?
16:09:43 bauzas last time I looked, I saw nova-next failing once over 5 times
16:10:00 bauzas this would create some problems later in the week
16:10:39 bauzas so I wonder whether we should skip that specific test
16:11:26 Uggla @bauzas, the one I pushed yesterday pass the tests
16:12:01 bauzas hmmm
16:12:11 bauzas okay, will wee
16:12:13 bauzas see*
16:12:41 Uggla maybe you were not unlucky.
16:13:25 bauzas oh, nvm found the root case, PEBKAC
16:13:55 bauzas https://6ae015e4c924496dfda3-74c26bb67ca36871e200d07f3210a3f0.ssl.cf1.rackcdn.com/940642/5/check/nova-multi-cell/c2a2f68/controller/logs/screen-n-sch.txt
16:14:02 bauzas this is because of my patch
16:14:09 bauzas so we can move on
16:14:29 bauzas any other failure to discuss ?
16:15:05 bauzas #topic Release Planning
16:15:30 bauzas #link https://releases.openstack.org/epoxy/schedule.html
16:15:35 bauzas #info Nova deadlines are set in the above schedule
16:15:41 bauzas #info 2 weeks before Feature Freeze
16:16:01 bauzas so maybe we should go straight to the next topic
16:16:07 bauzas #topic Review priorities
16:16:14 bauzas #link https://etherpad.opendev.org/p/nova-2025.1-status
16:16:39 bauzas I'll be honest, I was swamped by other priorities but I want to review a long list of changes this week
16:16:45 bauzas that becomes super urgent
16:17:35 dviroel fyi, I added at line 131 links to the blueprint and gerrit topic wrt scheduler-hints-in-server-details
16:17:45 dviroel please take a look when you folks have some time :)
16:18:02 bauzas noted, appreciated
16:18:23 bauzas given my on-off presence on IRC, I appreciate any way to discuss async
16:18:45 bauzas #topic PTG planning
16:19:14 bauzas well, I won't run that PTG by myself but this is a reminder that we'll have a PTG
16:19:23 bauzas #info Next PTG will be held on Apr 7-11
16:19:39 bauzas I started to draft some etherpad for that PTG
16:19:46 bauzas #link https://etherpad.opendev.org/p/nova-2025.2-ptg
16:19:55 bauzas feel free to add your topics worth of interest into it ^
16:21:07 bauzas #topic Stable Branches
16:21:16 bauzas elodilles_pto: oh he's not here
16:21:30 bauzas no worries, let's skip it for this week
16:21:37 bauzas #topic vmwareapi 3rd-party CI efforts Highlights
16:21:41 bauzas fwiesel: anything to talk ?
16:21:51 fwiesel Hi, yes... some progress on the last outstanding failure.
16:22:15 elodilles (sorry, i'm here, just forgot to change my nick o:) but stable gates seems to be healthy, fwiw)
16:22:30 fwiesel I suspect I do have a possible patch for that, but now I run into a bug into Cinder. I've created a bug report for it (https://bugs.launchpad.net/cinder/+bug/2097771) and want to fix that.
16:22:35 bauzas elodilles: noted.
16:22:51 bauzas fwiesel: ack, thanks for the reporting
16:22:59 fwiesel If that works out, I will ask you to review my solution for nova making use of that.
16:23:05 fwiesel That's from my side.
16:24:35 bauzas thanks
16:24:54 bauzas #topic Open discussion
16:25:30 bauzas we have one topic to discuss today
16:25:38 bauzas sp-bmilanov -- 927474: libvirt: Fetch the available vCPUs from the respective cgroup
16:25:40 bauzas sp-bmilanov: around ?
16:25:44 sp-bmilanov hi! yep
16:25:50 bauzas #link https://review.opendev.org/c/openstack/nova/+/927474
16:26:05 bauzas sean-k-mooney: are you here ?
16:26:13 sean-k-mooney yes
16:26:28 sp-bmilanov the topic is about how to handle the case where Nova is running in a hyperconverged setup where the are CPUs that are not available to Nova
16:26:33 sean-k-mooney i do not belive nova should do that but ill let sp-bmilanov explain
16:26:54 sp-bmilanov I was hoping to crowd-source alternatives
16:27:27 sean-k-mooney perhaps some context will help
16:27:49 sp-bmilanov the fundamental problem IMO is with libvirt -- it assumes all online CPUs == schedulable CPUs, and does not provide an API to query actually schedulable CPUs
16:27:53 gibi > CPUs that are not available to Nova < that feels like the existing cpuset config can handle
16:27:54 sean-k-mooney its possible to use the cgroups api to subdevied the host and mark some host as reserved for exclusive use fo a slice/partion
16:28:02 sean-k-mooney gibi: it can
16:28:20 sean-k-mooney sp-bmilanov would like nova to parse the cgroups toplogy and try and auto comput eit
16:28:43 sean-k-mooney one of my bigest issues with that is libvirt and nova-comptue might have diffent view of the cgroups

Earlier   Later