Thursday, 2025-05-08

opendevreviewmelanie witt proposed openstack/nova-specs master: Add reminder about Tempest API response schemas  https://review.opendev.org/c/openstack/nova-specs/+/94911302:28
melwittUggla, gmaan: this is a spec template update to add a note about API response schemas in Tempest ^02:30
melwitt(fyi)02:30
*** ralonsoh_out is now known as ralonsoh05:52
*** benj_6 is now known as benj_06:35
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks [FIX]: added error handling for .get() statements [FIX]: pep8 formatting fixed for changes [FIX]: added additional unit tests changes to mock validate_networks  https://review.opendev.org/c/openstack/nova/+/94520410:02
ishanwar[m]opendevreview: sean-k-mooney:  made a few changes as your requests UTs seems to be working fine now kindly have a look 10:04
sean-k-mooneygmaan: question for you https://docs.openstack.org/nova/latest/user/flavors.html11:20
sean-k-mooneywe currently default group_policy to non if request groups come form neutron ports11:20
sean-k-mooneybut we require group_policy to be passed if you pass multiple groups in the flavor11:21
sean-k-mooneyit almost never makes sesne to use isolate because it will break port based request if you ever want more then one port form the same nic11:21
sean-k-mooneyi.e. 2 ovs prot or 2 sriov ports11:21
sean-k-mooneyso we never recommend using that in general11:21
sean-k-mooneyso my question is if we jsut want to extend the defaulting to None to the falvor 11:22
sean-k-mooneycan tha tbe done without a microverison. i think the answer is know althoguh im hopeing i can argure that we coudl because we are relaxing the constraint11:22
sean-k-mooneyits a trivial spec to write if we decied we need a microversion for tha that but honestly i thinik havign server create fail if a user uses the old microvtion with a flavor and pass with the new versiuon and exactly the same flavor is terrible ux11:29
sean-k-mooneywe have previouysly said that new extra specs dont need a microvetion and that changing the default shoudl not either11:29
sean-k-mooneyso i think we can do this withou one simiarl to the fix for neutron prots https://github.com/openstack/nova/commit/ad4f79836264ec79068f087008367e2d2ae8cbea11:30
sean-k-mooneygibi: ^ you wrote that for the neutron port qos policy i belive do you see any reaons not to extend the defauling to none ot flavor based groups too.11:31
ishanwar[m]<ishanwar[m]> "sean-k-mooney:  made a few..." <- Build has passed as well. I think it looks good now 11:34
sean-k-mooneyishanwar[m]: i ment to push my comment a while ago but its going to fail our code style checks11:37
sean-k-mooneyishanwar[m]: i got pinged for soemthign else so i didnt finish the review but i pushed my comment about the whitespace sissue11:37
ishanwar[m]sean-k-mooney: pep checks seem to have passed though 11:37
ishanwar[m]sorry new to this 11:37
sean-k-mooneyi think i agree that this is good to go11:38
sean-k-mooneyyou shoudl stil fix https://review.opendev.org/c/openstack/nova/+/945204/6/nova/tests/unit/network/test_neutron.py#410111:38
sean-k-mooneybut i think the logic is correct11:38
ishanwar[m]sean-k-mooney: yeah I have double checked 11:39
ishanwar[m]let me fix the style 11:39
ishanwar[m]i'll ping back 11:39
opendevreviewStephen Finucane proposed openstack/nova master: wsgi: Don't create, use lock in same line  https://review.opendev.org/c/openstack/nova/+/94916111:40
sean-k-mooneyishanwar[m]: so running ti locally it fails both the trim trailign spaces check adn the lighleght check when i run tox -e pep811:45
sean-k-mooneyishanwar[m]: but it also fixes if for you11:45
sean-k-mooneywell it fixes the white space you will need to manually fix the linelenght issue11:46
gibisean-k-mooney: I think if the groups are coming from the flavor then we can simply ask the flavor creator to add policy according to the needs. I.e. if they want two vgpus from two different pgpus and they won't use qos ports then it is a case when isolate policy is needed. For the neutorn port case we need a defaulting as the person creating the port might not be the same as the one creating the 11:53
gibiflavor and we dont support adding policy to the port11:53
sean-k-mooneygibi: yes im aware11:57
sean-k-mooneywe currently require you to set it 11:57
sean-k-mooneybut i think it woudl be a better ux if we jsut defautl to none11:57
sean-k-mooneypartly because i honestly think we shoudl delete the suprpot for group_polcy in the flavor in its currnt form11:58
sean-k-mooneyi know its possibel to use isloate i fyou know exactly how the flavor will be used11:58
sean-k-mooneyi.e. if you have a flavor for a specific aplication that that will only be used with prots that either dont hav eresouce request or wont be fullfield form the same rp11:59
sean-k-mooneybut i think adding it to the flavor in its current form was a mistake  so if we can avoid admin ever settign it by defaulting to None11:59
sean-k-mooneyit hink that will server better longterm11:59
sean-k-mooneygibi: there is a similar but diffent issue with it too in that it breakes our filter because it not namespaced12:00
sean-k-mooneystephen and i fixed that in train for the only other extra spec that did not have a namespace12:00
sean-k-mooneywe created a namespaced version as an alias and maded the non name "deprecated" 12:01
sean-k-mooneyi think we shoudl do the same here and add group:policy=isolate|none12:01
sean-k-mooneybut again that for a slightly diffent reasons12:02
sean-k-mooneyuntil we can supprot expressign the policy betwen sepcific groups to me isolate is not practiclly usable unless  you a nova/placment core or have spent a very very long time lookign at all the details12:03
sean-k-mooneyso im wondering if we can take some fo the sharp edges off in a backwards compatible way12:04
sean-k-mooneyby 1 defaulting to none in all cases if not set, and 2 providing the namespaced version to fix the filters12:04
gibiI won't block the defaulting patch.12:53
gibiI'm OK to fix the  namespaceing 12:53
gibiI have no capacity to dig deeper in the discussion, but I'm happy to review the namespacing fix12:54
*** ykarel__ is now known as ykarel12:56
sean-k-mooneygibi: thanks. i just want to get some early feedback on direction. i will try and find time to file the relevent bug tracker and work on some kind of poc of this for wider dicussion13:17
gibithanks14:27
gibidansmith: sean-k-mooney: FYI: here are the pre-fork executor cleanup change https://review.opendev.org/c/openstack/nova/+/947966/9/nova/cmd/scheduler.py it is cleaner in my eyes. It works well in my local non testing and on the gate (CI result is in the nova-next job of the last patch in the series)14:50
dansmithnice14:51
gibioslo also did some changes based on our feedback about the fork issue but I haven't been able to check it out yet.14:52
gmaanmelwitt: thanks. ++15:00
opendevreviewMerged openstack/nova-specs master: Add reminder about Tempest API response schemas  https://review.opendev.org/c/openstack/nova-specs/+/94911315:09
sean-k-mooneygibi: how woudl you feall about getign rid of the glbal and doign this instead https://review.opendev.org/c/openstack/nova/+/947966/comment/dd7fc7e3_f4e926fb/15:20
sean-k-mooneygibi: and yes teh reset looks cleaner then i was expecting too so +1 on that15:20
sean-k-mooneygibi: by the way we likely should modify our base testcase to ensure we shutdown teh threadpool and reset it between test runs15:23
sean-k-mooneyi belive i had that in my verison ot prevent leakign thread betwen tests15:24
sean-k-mooneyif we ever do leak a thread in the pool it should fail the test15:24
sean-k-mooneythe same way our greenthread leak proctection works15:24
sean-k-mooneyin the test we can kind of get awar with it by using the synconousthreadpool via a fixture too15:26
sean-k-mooneybut we do have fixture to mange this currently https://github.com/openstack/nova/blob/master/nova/test.py#L197 https://github.com/openstack/nova/blob/master/nova/test.py#L324-L32915:27
sean-k-mooneyso we likely need to extend this to the new scather gather pool15:27
sean-k-mooneyi made the SynchronousThreadPoolExecutorFixture also apply to the futurist.ThreadPoolExecutor https://review.opendev.org/c/openstack/nova/+/922497/5/nova/tests/fixtures/nova.py#125415:29
sean-k-mooneygibi: bug i think you shoudl also update https://github.com/openstack/nova/blob/master/nova/tests/fixtures/nova.py#L1191-L1247 and https://github.com/openstack/nova/blob/master/nova/tests/fixtures/nova.py#L2056 or add new ones for this thread pool15:33
gmaansean-k-mooney: RE on group_policy, I think namespace is good idea, not sure why it was left in initial effort.16:59
gmaansean-k-mooney: about changing default to None. is not it None as default in ResourceRequest object and as you mentioned it is set 'None' explicitly if two group from different than flavor source17:01
gmaanI mean just checking what is value if it is not passed and groups from cmg from flavor only17:01
sean-k-mooneygmaan: right i know we set it if we get groups form 2 souces17:02
sean-k-mooneyim jsut suggesting updating that logic ot set it if we ever have 2 groups and its not set17:03
sean-k-mooneyso if you set it in the flavor that woudl alays overwrite it17:03
gmaansean-k-mooney: yeah, I agree on that. I am just saying we might be doing the same currently (not in flavor but somewhere in request spec/ResourceRequest )?17:04
sean-k-mooneygmaan: not based on gorkas testing of tryign to use 2 groups to ask for two vgpus17:04
sean-k-mooneybut maybe there are some code paths where we will17:05
gmaanhumm, and is it set 'isolated' in that case?17:05
sean-k-mooneyno its not pass to placement at all17:05
sean-k-mooneyand then placement raises an error i belive17:06
gmaanohk17:06
sean-k-mooneyi can ask for some logs or access to there enve where they hit this 17:06
sean-k-mooneywe likely can create a repoducer17:06
gmaanI think I agree with your proposal. As 'none' means request can be satisfied by different or same providers. if not passed, setting it default to None in flavor make sense. I do not think it change behavior from user perspective.   17:07
gmaanwe are just adding default here and not actually *changing* the default17:08
sean-k-mooneycorrect that is what it means17:08
sean-k-mooneygmaan: at least based on what we have documetned here https://docs.openstack.org/nova/latest/user/flavors.html17:09
gmaanyeah, I do not think we need microversion in that case, we can fix it as bug fix17:09
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks [FIX]: added error handling for .get() statements [FIX]: pep8 formatting fixed for changes [FIX]: added additional unit tests changes to mock validate_networks [FIX]: fixes using autopep8  https://review.opendev.org/c/openstack/nova/+/94923517:10
sean-k-mooneythansk for confirming.  as i said above i didnt like the idea of a server create failign with a given flavor based on the microversion used17:10
sean-k-mooneyor resize17:10
sean-k-mooneythat just seam very confussing for the end user to reason about17:11
gmaanyeah17:12
sean-k-mooneygmaan: there si already a bug for the filter part https://bugs.launchpad.net/nova/+bug/2048874 so ill likely resue that17:13
sean-k-mooneyill proably just take over the orgianl authors patch and try an dalign it to what we have dicussed https://review.opendev.org/c/openstack/nova/+/90521017:14
sean-k-mooneythey were orginall just oging to skip that key which may have worked but its nto really fixign the problem17:14
sean-k-mooneyalthough i might just reuse the bug and not the patch since the logic of the fix will end up beign differnt17:15
sean-k-mooneywhile i have this open https://review.opendev.org/c/openstack/nova/+/947541 is a nice small fix form melwitt that might be nice ot land if folks agree17:17
melwittsean-k-mooney: thanks for reviewing that :) I am happy to respin with code comment + release note btw17:19
sean-k-mooneyfrickler: fungi: do either of ye op access on the channel it might be nice to update the "development-planning: https://etherpad.opendev.org/p/nova-2025.1-status"  to "development-planning: https://etherpad.opendev.org/p/nova-2025.2-status" in the topic if Uggla agrees. i think the rest of the topic looks correct17:20
melwittthe above uploaded patch in the backscroll (https://review.opendev.org/c/openstack/nova/+/949235) looks like one of the garbage AI ones17:20
sean-k-mooneymelwitt: i got asked about that issue downstream, found the bug and was like oh melwitt has a fix up17:20
melwittsean-k-mooney: haha fun17:20
sean-k-mooneymelwitt: i have been thating to the reporter a bit17:21
sean-k-mooneynot the reportor17:21
sean-k-mooneythe sumbitter of https://review.opendev.org/c/openstack/nova/+/94923517:21
sean-k-mooneyso they are not really familary with workign in openstack and i think git17:21
sean-k-mooneybut ya the commit message is not forllwoing or normal convetion17:22
melwittyeah. it's such a tiny thing to fix I thought might as well + backport it. I agree with you that the long term thing will be to stop formatting eph disks17:22
sean-k-mooneyis more like what you do on mailing list where for each revision to expalin what you changed form the last one17:22
melwittsean-k-mooney: the commit message claims stuff that isn't in the patch though, like what is that17:22
melwitthuh ok17:22
sean-k-mooneymelwitt: so it explainging what has change over time17:22
sean-k-mooneywhic is fine in a mailing list btu weired in gerrit17:23
sean-k-mooneyalso the lost the change id so https://review.opendev.org/c/openstack/nova/+/945204/617:23
sean-k-mooneyis actully the review they shoudl of updated17:23
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks [FIX]: added error handling for .get() statements [FIX]: pep8 formatting fixed for changes [FIX]: added additional unit tests changes to mock validate_networks [FIX]: fixes using autopep8  https://review.opendev.org/c/openstack/nova/+/94520417:23
melwittI see17:23
sean-k-mooneyishanwar[m]: so you now have two reviews for the same thing because you lost the change id at one point17:24
sean-k-mooneyishanwar[m]: i think you ment to locally squash the two pathces before doing git review17:25
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks [FIX]: added error handling for .get() statements [FIX]: pep8 formatting fixed for changes [FIX]: added additional unit tests changes to mock validate_networks [FIX]: fixes using autopep8  https://review.opendev.org/c/openstack/nova/+/94520417:25
sean-k-mooneyishanwar[m]: ok ^ is better but as i was dissusing with melwitt above you shoudl update the commit message to expalin what the current revion of the patch is changing not how the patch changed over time17:27
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks [FIX]: added error handling for .get() statements [FIX]: pep8 formatting fixed for changes [FIX]: added additional unit tests changes to mock validate_networks [FIX]: fixes using autopep8  https://review.opendev.org/c/openstack/nova/+/94520417:27
sean-k-mooneyishanwar[m]: https://wiki.openstack.org/wiki/GitCommitMessages document the convetions we try to follow17:27
fungisean-k-mooney: i can update it, though separately i recommend the nova team consider adding some channel operators at https://opendev.org/openstack/project-config/src/branch/master/accessbot/channels.yaml#L23917:27
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks [FIX]: added error handling for .get() statements [FIX]: pep8 formatting fixed for changes [FIX]: added additional unit tests changes to mock validate_networks [FIX]: fixes using autopep8  https://review.opendev.org/c/openstack/nova/+/94520417:28
sean-k-mooneyfungi: oh i didnt know we could do that. i assuem we cant just update the topic via a git reivew?17:28
sean-k-mooneyfungi: i htink we used to be able to do this in the chanel before we moved to oftc17:29
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks [FIX]: added error handling for .get() statements [FIX]: pep8 formatting fixed for changes [FIX]: added additional unit tests changes to mock validate_networks [FIX]: fixes using autopep8  https://review.opendev.org/c/openstack/nova/+/94520417:29
sean-k-mooneybut its been so long i kind of forget the detials17:29
ishanwar[m]sean-k-mooney:  i have fixes the pep8 issue kindly have a look whenver you can 17:30
fungisean-k-mooney: you'd add people to an ops list for the channel in that file, then any of them can ask chanserv to set the channel topic like the example in https://docs.opendev.org/opendev/system-config/latest/irc.html#basic-channel-operator-commands17:30
sean-k-mooneyfungi: ah cool ill add that to the irc metting adgenda for next week so17:31
sean-k-mooneyand we can see what folks think17:31
ishanwar[m]sean-k-mooney: yep changing that 17:31
fungibut also if Uggla wants the topic updated in the meantime, i'm happy to do that myself too17:31
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: This feat optimises the validate_networks method by reducing networks calls to the database. Here we utilise the quota_details extension to gather the list of uses ports using the neutron extension, this is a smarter query as we don't have to list down all the ports which are in use. Instead we now utilise the quota details extension to get the count of used ports directly.  ht17:34
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks  https://review.opendev.org/c/openstack/nova/+/94520417:39
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: This feat optimises the validate_networks method by reducing networks calls to the database. Here we utilise the quota_details extension to gather the list of uses ports using the neutron extension, this is a smarter query as we don't have to list down all the ports which are in use. Instead we now utilise the quota details extension to get the count of used ports directly.  ht17:40
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: using quota_details to optimize validate networks  https://review.opendev.org/c/openstack/nova/+/94520417:41
ishanwar[m]Sorry for the spam everyone 17:41
ishanwar[m]i didn't realize opendev has been sending a notification here all this time 17:41
sean-k-mooneyya it does it also send an email to those on the review17:42
sean-k-mooneyits not  that distruptive but its goit to do those iteration locally and then push a reivew17:43
opendevreviewIshan Shanware proposed openstack/nova master: [FEAT]: This feat optimises the validate_networks method by reducing networks calls to the database. Here we utilise the quota_details extension to gather the list of uses ports using the neutron extension, this is a smarter query as we don't have to list down all the ports which are in use. Instead we now utilise the quota details extension to get the count of used ports directly.  ht17:43
sean-k-mooneyit avoids the spam and the ci churn but that comes with practice17:43
ishanwar[m]yeah sorry about that again, will be more careful from now on. 17:44
ishanwar[m]I think i have made all the changes i had to right now 17:44
ishanwar[m]you can have a look, whenever you can 17:44
opendevreviewmelanie witt proposed openstack/nova master: libvirt: Use common naming convention for ephemeral disk labels  https://review.opendev.org/c/openstack/nova/+/94754117:57
melwittsean-k-mooney: added code comment to the test and a release note ^17:58
opendevreviewMerged openstack/nova master: wsgi: Don't create, use lock in same line  https://review.opendev.org/c/openstack/nova/+/94916118:00
*** Callum0278 is now known as Callum02719:01
*** benj_0 is now known as benj_21:55
opendevreviewsean mooney proposed openstack/nova master: update pre-commit version pins  https://review.opendev.org/c/openstack/nova/+/94929122:52
opendevreviewsean mooney proposed openstack/nova master: Allow autopep8 to fix more things  https://review.opendev.org/c/openstack/nova/+/94929222:52

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