Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2026-06-15
15:40:39 sean-k-mooney the minitum valid numa flavor to day has hw:mem_page_size set to anything
15:41:01 bauzas but that's a tribal knowledge, right?
15:41:02 sean-k-mooney everythign else builds form that baseline otherwise your vm will get OOM killed eventually
15:41:32 sean-k-mooney bauzas: sort of
15:41:34 bauzas because I wonder why we should just use this flavor extraspec (mem_page_size) just for NUMA usage ?
15:41:53 sean-k-mooney because without it we do non numa aware memroy tracking
15:42:17 sean-k-mooney and we pin you to a numa ndoe without chekcign if the sum of vms on that numa ndoe fit
15:42:27 bauzas so that's a tech debt
15:42:41 sean-k-mooney yep from day one of numa supprot in tree
15:42:52 bauzas operators should be able to ask for NUMA nodes without needing to ask page sizes
15:42:55 sean-k-mooney and its tech debt i hav eproposed fixing multipel time
15:43:08 sean-k-mooney but we have rejected because it breaks upgrades
15:43:15 bauzas but at least for the bug report, I think we can still accept it
15:43:34 sean-k-mooney we can accpt the bug for limits
15:43:36 bauzas if the scheduler provides limits, we could provide them to the conductor and then the compute
15:43:40 sean-k-mooney not for numa without pagesize
15:44:02 bauzas then the scheduler shouldn't provide the limits
15:44:06 bauzas right?
15:46:41 sean-k-mooney sorry im not following the question
15:47:12 bauzas lemme explain it better my question
15:48:09 bauzas if we don't want nova to accept flavors asking numa cores with no page sizes, then we should not pass limits down to the conductor
15:48:46 sean-k-mooney https://etherpad.opendev.org/p/nova-wallaby-ptg#L712
15:48:52 bauzas if we're passing scheduler limits to the conductor, this means "oh, yeah, I accept this instance, please check those limits when you run the claims"
15:48:56 sean-k-mooney that was the last time i brought up chagnitn this at the ptg
15:49:17 bauzas sorry, my brain is bad about remembering things in general :-(
15:49:21 sean-k-mooney bauzas: the limits we are checkign are cpu ram and disk
15:49:29 sean-k-mooney those are enfocced by placment at the host level
15:49:42 sean-k-mooney the have never applied with the host at the numa level
15:49:45 bauzas like, I wasn't even to recollate the bug with my own numa vswitches
15:50:36 sean-k-mooney that whwere the diconnect is. we have never considerd the allcation tratios when it comes to numa affinity
15:52:19 sean-k-mooney bauzas: back in wallaby https://etherpad.opendev.org/p/r.321f34cf3eb9caa9d87a9ec8349c3d29#L712 we agreed an aproch to adress this so that any numa instance woudl be give a hw:mem_page_size if not set
15:52:42 sean-k-mooney that didnt happen because it was internally depriorised by our pm so i didnt end up workign on that
15:53:12 bauzas thanks, again, I wasn't able to remember this, sorry
15:54:05 bauzas but now we stora kind of accepting those flavors and we can't say 'well, doh, we don't support this, thanks'
15:54:10 sean-k-mooney no worries. so to have a path forward, i have no issues with passing limit when they shoudl be passed, and i have no issue with closign this numa footgun
15:54:17 bauzas I'm looking at the upstream docs to see whether we call it
15:54:49 sean-k-mooney bauzas: ya that has been the main concurn how do we fix this without breakign upgrades
15:55:33 bauzas sean-k-mooney: so, to clarify, you say "let's provide limits when we have them, but let's not pass those limits if those shouldn't be supported". Am I correct with this assumptio ?
15:56:10 sean-k-mooney more or less.
15:56:40 sean-k-mooney im kind fo ok wiht alwasy passign them but my main issue with the bug is expecting that nova will do the numa blancing as a side effeict
15:56:53 sean-k-mooney it might but that was never inteded to work
15:57:06 bauzas hmmmm
15:57:28 bauzas (I'm trying to find how we couldn't provide the limits if we have a specific flavor)
15:57:56 bauzas well, not really 'how' but 'where'
15:57:56 sean-k-mooney its a littel tricky because you can change the limite via placement
15:58:10 bauzas yeah
15:58:39 sean-k-mooney so there are 2 sepreate thing there are the numa toplogy constratis which we can create form flavor and iamge metadta
15:58:49 sean-k-mooney and seperate there is the limige for the allcoation ratios
15:59:06 opendevreview huangjs3 proposed openstack/nova master: cpu monitor: split zero/negative cputime paths https://review.opendev.org/c/openstack/nova/+/993205
15:59:09 sean-k-mooney i think we get those in the prover summaries
15:59:20 sean-k-mooney but i think the metign is stating now issh?
15:59:34 sean-k-mooney so we can pick this up after
15:59:58 opendevmeet The meeting name has been set to 'nova'
15:59:58 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:59:58 opendevmeet Meeting started Mon Jun 15 15:59:58 2026 UTC and is due to finish in 60 minutes. The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:59:58 Uggla #startmeeting nova
16:00:06 Uggla Hello everyone
16:01:27 jayaanand hi
16:01:31 sambork o/
16:02:03 Uggla starting in a mn.
16:02:11 erlon \o
16:02:20 gibi o/
16:02:53 bauzas o/
16:03:02 fwiesel o/
16:03:32 Uggla #topic Bugs (stuck/critical)
16:03:37 Uggla #info No Critical bug
16:03:44 Uggla #topic Gate status
16:03:51 Uggla #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:03:51 dansmith o/
16:03:57 tkajinam o/
16:03:58 Uggla #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:04:05 Uggla #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:04:11 Uggla #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:04:17 Uggla #info Please try to provide a meaningful comment when you recheck
16:05:04 Uggla I have not seen something special with the gate. Last week we had 2 bugs that progressed thx to gibi
16:05:09 Uggla #info https://bugs.launchpad.net/nova/+bug/2155773 entered by Gibi. Seems to be a duplicate.
16:05:14 Uggla #info https://bugs.launchpad.net/nova/+bug/2155462 entered by Helen. Valid one in progress.
16:05:23 sean-k-mooney o/
16:05:23 Uggla anything you want to say about them gibi ?
16:06:06 gibi https://bugs.launchpad.net/nova/+bug/2155773 as been fixed by melwitt. thanks for the fix
16:06:26 Uggla \o/
16:06:52 sean-k-mooney i belvie gibes bug was the orginal but its fixed in any case
16:06:52 gibi I have no news on the second one
16:06:57 gibi yea
16:06:58 gibi h
16:07:01 gibi but no wories
16:07:25 Uggla good so moving on.
16:07:31 Uggla #topic Release Planning
16:07:38 Uggla #link https://releases.openstack.org/hibiscus/schedule.html
16:07:43 Uggla #info Nova deadlines are set in the above schedule
16:07:49 Uggla #info PTG etherpad for 2026.2 is available: https://etherpad.opendev.org/p/nova-2026.2-ptg
16:07:55 Uggla #info Spec freeze was last week.
16:08:05 Uggla #topic Review priorities
16:08:10 Uggla #link New file for Hibiscus https://etherpad.opendev.org/p/nova-2026.2-status
16:08:17 Uggla #info I have updated Launchpad and the above doc. Please ping me if you spot something missing.
16:08:32 Uggla #info 471815: Expose vlan trunking in metadata/configdrive | https://review.opendev.org/c/openstack/nova-specs/+/471815 --> Sean +2, Gibi +1 thanks. Can we make a exception on that one.
16:09:27 Uggla I'd like to have a little exception on that one to let cardoe answer. I could not last weak. So unless someone is really against that, let's have a couple of days to approved that one.
16:09:45 Uggla s/I/he
16:09:59 gibi do we have some cores with capacity to review the impl this cycle?
16:10:19 bauzas -

Earlier   Later