Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2024-11-11
15:51:51 moot I think I am already in the time slicing mode
15:54:16 opendevreview Takashi Kajinami proposed openstack/nova master: Skip functional tests on pre-commit config update https://review.opendev.org/c/openstack/nova/+/933192
15:56:40 moot I am double checking about the mig mode that you talked about to be sure
15:59:42 moot I get :
15:59:42 moot >> sudo nvidia-smi -mig 0
15:59:42 moot Unable to disable MIG Mode for GPU 00000000:41:00.0: Not Supported
15:59:42 moot >> sudo nvidia-smi -mig 1
15:59:42 moot Unable to enable MIG Mode for GPU 00000000:41:00.0: Not Supported
16:15:48 sean-k-mooney so i think you are only ment to run "/usr/lib/nvidia/sriov-manage -e" if you dont want timesilcing
16:15:56 sean-k-mooney with that said nvidia keep changing how that works
16:16:06 sean-k-mooney so even if that was ture once it may not be anymore
16:16:52 moot MIG mode is not enabled on my gpu I can see that using nvidia-smi -q
16:16:59 sean-k-mooney moot: if you dont have any usecase for usign the mdevs on the host you can ommit the device address and instead define the maxum mdevs i think
16:18:12 sean-k-mooney oh thats missing form our docs entirly
16:18:47 sean-k-mooney that might be becasue its an option in an dynmic config section
16:19:27 sean-k-mooney https://github.com/openstack/nova/blob/master/nova/conf/devices.py#L108-L115
16:20:04 sean-k-mooney that is not invoked as part of our docs generation. not really sure how to fix that
16:20:45 moot I will try that but it does not work in a senario with multiple PF right ?
16:21:22 sean-k-mooney it does provided you do not want to use diffent mdev typs per pf
16:21:34 sean-k-mooney the second you want to do that you need to staticly partion them
16:22:08 moot even if I am using time sliced gpus ?
16:22:43 sean-k-mooney so in the past for timesliced vgpu you did not use sriov-manage -e <addres>
16:23:02 sean-k-mooney so it might be worth testing without doing that and see fi the mdevs move back to the pf
16:23:22 sean-k-mooney that is how it used to work before nvidia relased card that supprot sriov
16:23:54 moot you mean testing out without enabling VF so no sriov-manage -e <addres> ?
16:23:56 sean-k-mooney nviida have unfortually changed this behvior on the same card with diffent verions fo there driver/firmware
16:24:04 sean-k-mooney moot: correct
16:24:43 sean-k-mooney if you dont enabel sriov i would expect the mdev capablity to be adversed on the PF isntead and then in nova you could list jut the pf adress
16:24:57 moot I can do that, I will look into contributing to the doc if you think it needs some updates
16:25:12 sean-k-mooney thats how it worked on the T and older generation of cards
16:25:31 sean-k-mooney this is kind of why we just say "look at the vendor docs" for that part
16:26:03 sean-k-mooney i.e. https://docs.nvidia.com/vgpu/5.0/pdf/grid-vgpu-user-guide.pdf
16:26:26 moot well nvidia doc just tell to enable the VF if am not mistaken
16:29:20 moot btw I tried to remove the pci address from the nova conf add a ressource provider was created for each VF
16:29:45 moot 'If not set, it implies that we use the maximum allowed by the type."
16:32:58 moot and not add *
16:45:49 zigo sean-k-mooney: Thanks for helping my (intern) colleague that was kind of lost! :)
16:46:50 sean-k-mooney zigo: vgpus are not a kind thing to expose interns too :P happy to help
16:47:16 sean-k-mooney this is one of the case where nova is kind of helpless to document proeprly becasue it not only depends on the vendor but also the card and the driver used
16:47:51 sean-k-mooney and you know the phase of the moon, your choice in wiskey and if you are feelign lucky today
16:47:53 zigo sean-k-mooney: Yeah, but that one intern is special and knows his stuff ... :P
16:48:29 sean-k-mooney moot: if you do see a way to make the docs better please feel free too
16:55:10 zigo I'll beat him until all is right! :P
17:02:22 moot sean-k-mooney: I tried not to enable SRIOV as discussed but the PF does not seems to be mdev capable, so no RP is created.
17:02:22 moot when I do not specifies either the device id nor the mdev max number nova does seem to manage well I did not test extensivly I will do that tomorrow!
17:02:22 moot Any way thank you for your help I will try my best to find a way to add this information to the docs!
21:29:19 opendevreview Ghanshyam proposed openstack/nova master: Remove default override for config options policy_file https://review.opendev.org/c/openstack/nova/+/934578
#openstack-nova - 2024-11-12
03:55:06 opendevreview melanie witt proposed openstack/nova master: nova-manage: Add flavor scanning to migrate_to_unified_limits https://review.opendev.org/c/openstack/nova/+/924110
04:45:46 opendevreview melanie witt proposed openstack/nova master: nova-manage: Add flavor scanning to migrate_to_unified_limits https://review.opendev.org/c/openstack/nova/+/924110
06:47:12 opendevreview Tony Breeds proposed openstack/nova stable/2023.1: Critical change for 2023.1/Antelope https://review.opendev.org/c/openstack/nova/+/934720
06:56:02 opendevreview Rajesh Tailor proposed openstack/nova master: Add support for showing finish_time https://review.opendev.org/c/openstack/nova/+/928933
08:22:16 opendevreview melanie witt proposed openstack/nova master: Add [quota]unified_limits_required_resources list https://review.opendev.org/c/openstack/nova/+/924025
09:35:30 opendevreview Amit Uniyal proposed openstack/nova master: Update Nova bdm with updated swap info https://review.opendev.org/c/openstack/nova/+/929858
12:22:08 opendevreview Merged openstack/nova master: docs: Change note:: to warning:: for service user token https://review.opendev.org/c/openstack/nova/+/928308
12:22:14 opendevreview Merged openstack/nova master: docs: Correct unified limits CLI commands https://review.opendev.org/c/openstack/nova/+/924888
13:07:25 ratailor melwitt, Could you please review https://review.opendev.org/c/openstack/nova/+/873901
13:17:34 mina Hi everyone, I've just sent a merge request for Nova and was wondering if someone can have a look when that's possible. The MR link is https://review.opendev.org/c/openstack/nova/+/933311. Thank you very much in advance!
13:21:51 opendevreview Rajesh Tailor proposed openstack/nova master: Fix case-sensitivity for metadata keys https://review.opendev.org/c/openstack/nova/+/873901
13:23:38 opendevreview Rajesh Tailor proposed openstack/nova master: Fix concurrent migration of vms with multiattach volume failure https://review.opendev.org/c/openstack/nova/+/872278
13:41:01 opendevreview Merged openstack/nova-specs master: Repropose per-process-healthchecks for Epoxy https://review.opendev.org/c/openstack/nova-specs/+/934028
14:23:41 sean-k-mooney mina: im sorry to say that i dont think that change is inlien with how nova should operate
14:24:46 sean-k-mooney i get why you may want to block callign it on instnaces that are shleved but as gibi noted in the bug https://bugs.launchpad.net/nova/+bug/1913016/comments/2 we dont want to make reset-sate smarter
14:26:15 sean-k-mooney i could see use removing the api entirly or expanding the state you can reset too or other api changes via a new microversion i.e. blockign it when its shelve in a new microversion
14:26:53 sean-k-mooney but config driven api behaivor is not inline with how the nova api is intended to work
14:40:47 mina gibi & sean-k-mooney: Thank you for the comments and suggestions. I understand that. I will rewrite my proposal, probably introducing the changes via a new microversion as suggested. Thank you all again.
14:41:03 artom_ bauzas, hey, because of the downstream chat about mdev live migration, I'm looking at your series - you've thought of rolling upgrades, right? I just don't see a compute service version bump, or similar checks at first glance, but I'm probably missing something
14:41:48 bauzas artom_: no, we automatically detect whether the target supports it by the object
14:42:00 sean-k-mooney mina: a new microversion solve the interop issue and upgrade impact, peopel depending on the old behavior can use the old microversion, and in general we can make it safer for people using the newest microversion
14:42:33 sean-k-mooney artom_: we didnt add one because of how its working
14:42:48 artom_ sean-k-mooney, bauzas, OK OK, I trust you, thanks :)
14:48:28 mina sean-k-mooney: Thanks for the clarification. That helps me work on the spec, then.
15:49:24 tkajinam ummmmmmm https://bugs.launchpad.net/os-vif/+bug/2087982
16:00:33 bauzas #startmeeting nova
16:00:33 opendevmeet Meeting started Tue Nov 12 16:00:33 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:33 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:33 opendevmeet The meeting name has been set to 'nova'
16:01:00 elodilles o/
16:01:55 fwiesel o/
16:02:35 tkajinam o/
16:02:36 Uggla o/
16:06:31 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:06:37 bauzas sorry, the agenda was not prepared
16:07:06 bauzas #topic Bugs (stuck/critical)
16:07:16 bauzas #info No Critical bug
16:07:22 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:08:11 tkajinam there is an issue with os-vif which is currently blocking its CI. https://bugs.launchpad.net/os-vif/+bug/2087982
16:08:27 tkajinam this needs to be fixed to merge https://review.opendev.org/c/openstack/os-vif/+/932436 which is required to bump oslo.utils
16:09:23 tkajinam I'm unsure if I can take time immediately to dig into it... it'd be really appreciated if anyone can help fixing it
16:09:54 bauzas eesh ok
16:10:38 bauzas any volunteer is appreciated, indeed
16:10:59 bauzas moving on
16:11:02 bauzas #topic Gate status
16:11:09 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:11:15 bauzas #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:11:24 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:11:38 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:11:43 bauzas #info Please try to provide meaningful comment when you recheck
16:12:00 bauzas so the os-vif bug doesn't impact our gate but blocks new os-vif features
16:13:30 bauzas anything else to mention about CI ?
16:14:32 tkajinam nothing else from me

Earlier   Later