Earlier  
Posted Nick Remark
#openstack-nova - 2023-11-08
10:00:15 zigo BTW, Python 3.12 thingy will start in Unstable next November.
10:00:24 zigo Expect bug reports and patches from me ...
10:00:33 bauzas I have the opinion that the lower you're a dependency, the longer you need to keep support
10:00:44 zigo Yet another thing: how come every single new version breaks my world ...
10:00:51 sean-k-mooney next november as in 2025 or as in that then next thing to start in novemerb on your backlog
10:01:00 bauzas and a language sounds to me like probably one of the lowest dependencies we have and the most commonly shared
10:01:04 zigo Oh sorry, as in this month !
10:01:10 sean-k-mooney ok :)
10:01:27 sean-k-mooney i was like that seams far off
10:01:44 zigo 3.14 is planned for Trixie (ie: debian 13).
10:01:45 bauzas forcing people to upgrade by 2 years if you're a very common library is kinda harsh
10:02:16 sean-k-mooney bauzas: your only forced to upgrade if you dont pin your deps
10:02:35 sean-k-mooney you can always you an older pip to get the old behavior
10:02:44 sean-k-mooney bauzas: the reason that is not viabel for us
10:03:12 sean-k-mooney is openvswitch now requried pep 517 to build in debian and newer releases then we ship in centos/ubuntu
10:03:29 bauzas that's my point
10:03:33 sean-k-mooney so pining pip breaks once you have a new enought ovs
10:03:44 bauzas if this wasn't ovs, this would be something else
10:04:03 bauzas since lots of projects are moving on their own timeframe, the other ones also need to adjusty
10:04:20 sean-k-mooney well the ovs issue is they did not keep supprot for both like i am
10:04:39 sean-k-mooney im just adding pyproject.toml supprot without removing setup.py support
10:04:49 sean-k-mooney zigo: ^ important point for you
10:04:56 bauzas sean-k-mooney: yeah, hence my +2
10:05:08 bauzas we're continuing to do the old way but we allow doing it the new way
10:05:14 sean-k-mooney we can drop setup.py support in the future but its not breaking anything so i didnt see a point
10:05:17 zigo sean-k-mooney: Yeah, I'll look at what you did!
10:05:19 bauzas again, my rant wasn't directed to your change
10:05:52 sean-k-mooney bauzas: i know
10:06:12 sean-k-mooney i just feel like i have to play devels avocate and defend the python core team
10:13:45 jrosser talking of gpu company starting with n, A100/A30 removal from the vGPU driver v16 is causing us a massive headache right now
10:14:03 sean-k-mooney jrosser: yep...
10:14:05 jrosser anyone with ideas what to do would be interesting
10:14:28 sean-k-mooney other then keepign the old driver and pinnign your kernel till you retire the hardware
10:14:34 sean-k-mooney there isnt much you can do
10:14:47 sean-k-mooney jrosser: what os are you on
10:14:54 jrosser ubuntu
10:15:18 sean-k-mooney cool well i think you can continue to use the 15.x driver for the lifetime of 22.04 right
10:15:31 sean-k-mooney although obviorulsy wihtout any future security/preformance improvements
10:15:44 jrosser i don't believe we are going to be able to get any more vCS licences once ours expire
10:16:22 sean-k-mooney oh right the lisciense have an experation date...
10:16:31 jrosser yup
10:16:45 sean-k-mooney they have a diffent driver that the created for some of there skus
10:16:53 sean-k-mooney do you know fi the a100 moved to the new dirver
10:17:21 sean-k-mooney they are spliting there product skus between enterpirse and ai/ml usecases i belive
10:18:28 sean-k-mooney i havent really looked at the detail but i know the grid driver is being split in two for two diffent classes of hardware/workloads but i dont knwo where the a100 lands in that regard
10:30:57 jrosser sean-k-mooney: we have been attempting to PCI passthrough the MIG sriov VF (this might be pointless and never work, but it is at the advice of someone from nv) and get this https://paste.opendev.org/show/bTDDSu1EaNMhflc12ROB/ - do you see anything like that before with PCI passthrough?
10:32:57 sean-k-mooney jrosser: my understanding is while that could work the nvida driver in the guest does not curretnly work on the vf
10:33:17 jrosser i could totally believe that
10:33:46 sean-k-mooney header type 127 does seam famialr for some reason
10:34:08 sean-k-mooney i belive its one fo the extended pci capablity headers
10:34:09 jrosser and that certainly the case for vGPU/GRID driver on the host and free DataCenter driver in the guest which would be the most obvious licencing bypass you could do, so I expect that not to work
10:34:32 jrosser the advice we got was to try DataCenter driver on the host and in the guest
10:35:10 sean-k-mooney https://forum.level1techs.com/t/unknown-pci-header-type-127-for-device-000000-0/180125/4
10:35:27 sean-k-mooney appreently its somethign to do with the graphsics card sleep modes
10:35:46 opendevreview Merged openstack/nova-specs master: Re-propose spec for ephemeral storage encryption https://review.opendev.org/c/openstack/nova-specs/+/897502
10:35:48 opendevreview Merged openstack/nova-specs master: Re-propose spec for ephemeral encryption for libvirt https://review.opendev.org/c/openstack/nova-specs/+/897503
10:37:13 sean-k-mooney jrosser: so its apprently because the card is not reseting properly when attached/detached form the vm
10:37:41 sean-k-mooney jrosser: thats a pretty common thing on consumer graphics cards that are pci passhtough to a vm
10:37:47 jrosser hmm
10:38:09 sean-k-mooney im suprised thats a problem for a100 but since they never intended the vfs to be passed to the guest its not that surprising
10:41:03 sean-k-mooney https://forum.level1techs.com/t/solved-gpu-passthrough-suddently-stopped-working-on-windows-10-vm/171273/5
10:41:42 sean-k-mooney i have not tired this but apprently you can disbable the d3 idel state for that device
10:41:43 sean-k-mooney options vfio-pci ids=10de:2486,10de:228b disable_vga=1 disable_idle_d3=1
10:42:24 opendevreview Merged openstack/nova-specs master: Re-propose "Allow Manila shares to be directly attached to an instance when using libvirt" for Caracal https://review.opendev.org/c/openstack/nova-specs/+/898319
10:42:51 sean-k-mooney jrosser: if it is just a sleep issue i woudl give that a try for the mig vfs
10:43:23 jrosser ah thats interesting, thanks
10:43:46 bauzas jrosser: fwiw, please know that you could be hit with https://bugs.launchpad.net/nova/+bug/2041519 if you use A100
10:44:17 bauzas jrosser: and yeah, I send hugs to you about vGPU GRID16 EOL support for AI
10:44:42 jrosser bauzas: yeah i saw that discussion the other day - the whole thing is a total disaster /o\
10:44:50 bauzas you now need to buy a fancy expensive AIE license : https://docs.nvidia.com/ai-enterprise/4.0/release-notes/index.html
10:45:04 jrosser indeed, for 50 to 100% of the cost of the hardware
10:45:40 sean-k-mooney i recently bought an intel a750 apprently you can flash that to run there datacenter firmware
10:45:50 sean-k-mooney and get sriov supprot on the consumer card
10:45:54 bauzas jrosser: IMO, now working with some n guys, I can say that they're excellent hardware vendors but terrible software engineers
10:46:01 sean-k-mooney i have been debating about doing that
10:46:51 bauzas sean-k-mooney: btw. when you and dansmith have time, I'd like to discuss on what direction we should do with https://bugs.launchpad.net/nova/+bug/2041519
10:47:21 bauzas the alternative series I wrote is not helping as it doesn't delete existing RPs https://review.opendev.org/q/topic:bug%252F2041519-new
10:47:59 bauzas (the above patch is just a nice try to pass a PF in device_addr instead of VFs, but that's not mandatory)
10:49:00 sean-k-mooney ok ill need to load context on this again so let either set up a meeting ro choose a time to discuss it but it woudl be good to sumemrise what you have tried and what did/didnt work
10:49:20 bauzas sean-k-mooney: and you know, I haven't darken my view of the world, I'm just mattman as matthew perry said
10:49:23 sean-k-mooney bauzas: im currently reviewing dans spec
10:49:30 sean-k-mooney but i can take a look at the patches after
10:49:42 bauzas sean-k-mooney: sure, let's do a gmeet with dan when he's up
10:49:46 zigo jrosser: Am I reading well that the A100 removal is from the Linux kernel ?!?
10:49:49 bauzas sean-k-mooney: no urgency
10:50:14 sean-k-mooney zigo: i dont think soo i think its just being droped form the nvidia binary driver they ship via there portal
10:50:14 bauzas zigo: no, A100 are no longer supported in GRID, that's the point
10:50:26 bauzas zigo: starting with GRID16
10:50:44 sean-k-mooney it would work as a normal graphics card with teh opensouce neuvous driver
10:50:44 bauzas https://docs.nvidia.com/grid/16.0/whats-new-vgpu/index.html
10:50:54 dvo-plv Hello, All. I would like to discuss results of yesterday debate regarding packed ring. Currently we have tow way traits and prefilter based on the release version. How we properly can solve this problem, Should be ask gibi for his ?
10:51:04 sean-k-mooney but none of there vGPU stuff is supproted in the the opensouce dirver
10:51:15 bauzas dvo-plv: I said yesterday that eventually, I'll let the spec sail
10:51:24 bauzas so ask gibi for a review
10:52:15 bauzas dvo-plv: sean-k-mooney had a point on the fact we shouldn't conditionnally provide the trait, so update your spec and add testing and I'll let sean-k-mooney +2 it
10:52:42 dvo-plv okay, I see your point, thank you
10:52:45 bauzas for me, I'll pass as I don't want to give an approval for some direction I have arguments against, but on the other way, I don't wanna hold the series, so I defer to other cores
10:53:02 bauzas I'll just not vote on the spec
10:53:02 sean-k-mooney dvo-plv: tl;dr we bumped libvirt min to 7.0.0 last cycle so no need to do a check on the version anymore
10:53:09 sean-k-mooney either for the trait or in the driver

Earlier   Later