Earlier  
Posted Nick Remark
#openstack-nova - 2025-02-25
16:11:05 elodilles just an fyi as we have Epoxy-3 now o:)
16:11:06 sean-k-mooney so those have the same freeze deadline as nova right
16:11:08 bauzas noted, I'll review them
16:11:10 sean-k-mooney i.e. thrusday
16:11:18 elodilles yepp
16:11:30 sean-k-mooney but we will want to do a release at m3 to test with them for RC1
16:11:41 elodilles +1
16:12:11 sean-k-mooney we shoudl not haver anything pending for osc-palcement or novaclient that im aware of
16:12:18 sean-k-mooney so we can probly do those effectivly now
16:12:50 sean-k-mooney on clients
16:13:08 sean-k-mooney we have some new api versions this cycle and im not sure we will have osc suprot for those in time
16:13:20 sean-k-mooney so they may get enabled next cycle
16:13:54 sean-k-mooney but there isnt really anything we can do there at this point if the sdk supprot is not already merged
16:14:59 sean-k-mooney elodilles: am i correct in saying the sdk is subject to the non clinet code freeze so we should not expect to merge supprot for spice direct or image property shod api microversion between now and FF
16:15:32 elodilles sean-k-mooney: if i'm not mistaken sdk already merged it's final release patch recently
16:15:48 sean-k-mooney ack that what i was expecting
16:15:59 elodilles well,
16:16:06 elodilles it's still open,
16:16:32 elodilles waiting for a 2nd +2: https://review.opendev.org/c/openstack/releases/+/941859
16:16:38 elodilles from release team
16:17:06 sean-k-mooney i think we are missing a finaly release for os-traits and perhaps os-resouce classes too by the way
16:17:45 elodilles those are 'independent' projects, hence not picked up by release tools
16:17:46 sean-k-mooney we have not merged any content since the last release we did for either
16:17:53 sean-k-mooney ah ok
16:17:57 elodilles but wasn't there os-traits release recently?
16:18:30 sean-k-mooney yes but we had traits we wanted to add and have anouther release 3 days after that happend:)
16:18:49 sean-k-mooney the os-traits patch is still pending a second +2
16:18:56 elodilles sean-k-mooney: this is the content of SDK release (if it doesn't change anymore): https://zuul.opendev.org/t/openstack/build/24cc79c0e8e84d7d853e679e4e928585/log/tox/list-changes/list-changes-results.log#918-947
16:19:13 opendevreview Jay Faulkner proposed openstack/nova master: PoC: Allow unversioned-notify specific transport url https://review.opendev.org/c/openstack/nova/+/942710
16:19:26 sean-k-mooney ok we can likely move on and revisit in open dicuss if there is more to bring up
16:19:49 elodilles +1
16:21:19 bauzas can we move on ?
16:21:41 elodilles yepp
16:23:02 bauzas cool
16:23:13 bauzas #topic Review priorities
16:23:20 bauzas #link https://etherpad.opendev.org/p/nova-2025.1-status
16:25:30 bauzas nothing to tell about, I'm doing hard reviews
16:25:39 bauzas anything else ?
16:26:08 bauzas looks not
16:26:15 opendevreview Doug Goldstein proposed openstack/nova master: ironic: fix logging of validation errors https://review.opendev.org/c/openstack/nova/+/942019
16:26:17 bauzas #topic PTG planning
16:26:23 bauzas #info Next PTG will be held on Apr 7-11
16:26:38 bauzas usual reminder, please fill the agenda !
16:26:42 bauzas #link https://etherpad.opendev.org/p/nova-2025.2-ptg
16:27:59 bauzas #topic Stable Branches
16:28:04 bauzas elodilles: your turn
16:28:17 elodilles ACK
16:28:23 elodilles actually, same as last week:
16:28:31 elodilles #info stable gates seem to be healthy
16:28:39 elodilles #info stable/2023.2 release patch: https://review.opendev.org/c/openstack/releases/+/941420 (stable/2023.2 (bobcat) is going to transition to EOL in ~2 months)
16:28:47 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:28:57 elodilles that's all
16:31:22 bauzas cool
16:31:34 bauzas #topic vmwareapi 3rd-party CI efforts Highlights
16:31:37 bauzas fwiesel: around ?
16:31:48 fwiesel No updates from my side. I am a bit under the weather.
16:33:08 bauzas ditto here
16:33:10 bauzas I understand you
16:35:38 bauzas #topic Open discussion
16:35:45 bauzas I have one item
16:36:01 bauzas kudos to Uggla for being our next PTL \o/
16:36:10 Uggla thx
16:36:25 gibi congrats
16:36:40 gibi and thanks bauzas for the long service as PTL
16:36:45 fwiesel Congrats
16:36:53 elodilles yepp ++ \o/
16:38:26 bauzas I will !
16:38:29 masahito congrats and thank you
16:38:39 bauzas anyway, moving to the questions
16:39:09 bauzas (hertrste) Nova Cloud Hypervisor support
16:39:23 hertrste Hi o/
16:39:55 hertrste We would like to add support for the Cloud Hypervisor VMM to openstack Nova
16:40:12 hertrste As we have not contributed anything yet, we would like some guidance how to approach that
16:40:29 sean-k-mooney this yes https://github.com/cloud-hypervisor/cloud-hypervisor
16:40:31 hertrste As you can see in the meeting notes, we have a proof of concept
16:40:40 hertrste exactly
16:41:08 sean-k-mooney i breifly looked at that a few months ago out of interest when i was playing with rust
16:41:13 hertrste We also have a proof of concept adding some basic support for that VMM: https://github.com/openstack/nova/commit/617ac2f655492d1b84b2d924412ac7063d231110
16:41:14 sean-k-mooney it has an interesting feature set
16:41:29 gibi I think the next step there is to have PTG topic proposed for this
16:42:12 sean-k-mooney hertrste our main concerns would be likely testing, and building out a minimal supportrable feature set
16:42:36 bauzas yeah, looks to me a good PTG session
16:42:39 sean-k-mooney that would invovle defining a spec (if the propsal to add a new driver was green lit)
16:42:42 bauzas hertrste: can you attend it ?
16:42:44 dansmith I'd also be interested in knowing how widely it is used/deployed
16:42:44 sean-k-mooney to descibe the expecations
16:43:05 dansmith and also, why it's not just a libvirt driver :)
16:43:50 sean-k-mooney well i dont neesislay think we shoudl say all linux hyperviors shoudl be behind libvirt
16:43:55 hertrste I can very much attend a PTG. What would I need to prepare for that? When would that meeting take place?
16:43:57 sean-k-mooney it has its pros and cons
16:44:43 dansmith sean-k-mooney: no, doesn't have to be, but there's a lot of stuff to re-implement in nova if it's not, and so I'd expect there to be a good reason for it
16:44:50 gibi hertrste: https://openinfra.org/ptg/
16:44:54 bauzas hertrste: see the above discussion about PTG
16:45:32 Uggla hertrste, Apr 7-11
16:45:38 sean-k-mooney hertrste: i think the main things to prepare is an elevator pitch explaining why an operator may want ot use this
16:45:53 sean-k-mooney wwhat usecases and target workloads woudl it enable
16:46:02 tpressure libvirt has a poor hypervisor abstraction. If we would go the libvirt route, we would effectively have to maintain two components instead of only one. You cannot simply map qemu calls to cloud hypervisor
16:46:05 dansmith sean-k-mooney: especially since it appearently already exist: https://libvirt.org/drvch.html
16:46:19 sean-k-mooney and beyond that how you plan to test and develop supproted for it on an ongoing basis
16:46:58 sean-k-mooney tpressure: well we dont generate qemu calls today

Earlier   Later