| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-02-25 | |||
| 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 | sean-k-mooney | to descibe the expecations | |
| 16:42:44 | dansmith | I'd also be interested in knowing how widely it is used/deployed | |
| 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 | |
| 16:47:10 | sean-k-mooney | nova generate a semi hypervior indepent xml | |
| 16:47:31 | sean-k-mooney | we "supprot" libvirt with lxc, qemu and i think openvz | |
| 16:47:47 | sean-k-mooney | althoug everything excpt for qemu is basiclly not tested or maintaiend anymore | |
| 16:48:19 | sean-k-mooney | tpressure: hertrste based on https://libvirt.org/drvch.html provied by dan there si already some supprot for cloud-hypervior in libvirt | |
| 16:48:31 | hertrste | yeah we know of that support | |
| 16:48:36 | sean-k-mooney | so the question woudl be what does a full virt driver provide that cant be done vai that | |
| 16:49:04 | dansmith | and more than that, why would it be worth maintaining that *and* a separate full nova driver | |
| 16:49:29 | dansmith | like, what will never be possible via libvirt that would be if we have a whole separate implementation in nova | |
| 16:49:31 | hertrste | we decided not to use it because we felt the overhead of dealing with the existing 14k LoC for the libvirt backend in Nova was not worth. at least for a proof of concept | |
| 16:49:53 | dansmith | because libvirt brings all kinds of things like network and storage abstraction that would have to be written from scratch in a nova driver | |
| 16:50:03 | hertrste | Further, libvirt only has very basic support for cloud hypervisor. so we basically would need to add features in 2 complex code bases | |
| 16:50:31 | sean-k-mooney | the main concern i would have iwth the current poc | |
| 16:50:41 | sean-k-mooney | is its directly invoking a command line client correct | |
| 16:50:52 | dansmith | hertrste: that's only true if you're talking about a feature that isn't supported at all by libvirt, which is honestly going to be a hard sell in nova anyway | |
| 16:51:01 | sean-k-mooney | which means you are commiting to providign a forward compatiable stable cli fro nova to use | |
| 16:51:40 | bauzas | folks, because we have another item to discuss, can we stop here ? | |
| 16:51:46 | dansmith | sean-k-mooney: and hopefully there is some way to not kill those instances when nova restarts.. I hope it doesn't make nova responsible for being the init system for those binaries... | |
| 16:51:59 | sean-k-mooney | sure we can move on | |
| 16:52:05 | dansmith | bauzas: yes, I have to run anyway.. but a preview of my concerns for PTG :) | |
| 16:52:06 | sean-k-mooney | dansmith: ack | |
| 16:52:19 | hertrste | thanks for the feedback | |
| 16:52:30 | bauzas | hertrste: ping me if you have any questions about the PTG, I'll try to answer your concerns | |
| 16:52:40 | bauzas | moving on then | |
| 16:52:50 | bauzas | (mzhang741) Add Burst Length Support to Cinder QoS | |
| 16:52:58 | bauzas | is mzhang741 here ? | |