Earlier  
Posted Nick Remark
#openstack-nova - 2026-02-02
16:04:56 Uggla Shame on me, I have not looked at the gate today, anything special with it ?
16:05:24 gmaan nova-alt-configurations is fixed now
16:05:44 gmaan tempest change is merged, so feel free to recheck for this failure
16:05:46 gmaan #link https://review.opendev.org/c/openstack/tempest/+/975356
16:07:15 Uggla ok gmaan, good to know and thanks
16:07:29 Uggla anything else ?
16:07:53 bauzas -
16:08:22 Uggla ok so moving on
16:08:31 Uggla #link https://releases.openstack.org/gazpacho/schedule.html
16:08:39 Uggla oops
16:08:41 Uggla #topic Release Planning
16:08:48 Uggla #link https://releases.openstack.org/gazpacho/schedule.html
16:08:55 Uggla #info Nova deadlines are set in the above schedule
16:09:09 Uggla #info 4 weeks before feature freeze
16:09:18 Uggla #info PTG etherpad for 2026.1 is available: https://etherpad.opendev.org/p/nova-2026.1-ptg
16:09:29 Uggla #topic Review priorities
16:09:39 Uggla #link https://etherpad.opendev.org/p/nova-2026.1-status
16:09:49 Uggla #info I have updated Launchpad and the above doc. Please ping me if you spot something missing.
16:10:31 bauzas ++
16:10:40 Uggla TBH, I'm a bit worried by the vTPM series.
16:11:07 Uggla Is there still some things that needs to be clarified discussed ?
16:11:19 Uggla Does an adhoc meeting could help ?
16:11:34 bauzas mel and dan are not here
16:11:37 bauzas afaics
16:11:46 bauzas so let's discuss this when they're back
16:12:03 bauzas oh, sorry, at least mel, dan is here
16:12:54 Uggla bauzas, from your perspective could an adhoc meeting help ?
16:14:06 dansmith eh?
16:14:17 bauzas yes and no, I reviewed the series, maybe melwitt could change the relationship, but that's not an issue IMHO
16:14:25 dansmith I've been tied up with other stuff for the last week, but I think it's moving forward
16:14:29 bauzas I'm continuing to review the series
16:15:02 Uggla dansmith, bauzas, good if you think it is progressing.
16:15:57 Uggla ok I don't want to bother you more about it, if you think it is ok.
16:15:59 Uggla moving on
16:16:08 Uggla #topic OpenAPI
16:16:15 Uggla #link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned
16:16:27 Uggla #info still 11 remaining atm. (-3)
16:16:45 Uggla #topic Stable Branches
16:17:02 elodilles thanks
16:17:14 elodilles first of all, thanks bauzas for your nova release liaison reviews ;) a couple of stable/2024.2 releases merged today (nova, placement, os-vif)
16:17:26 elodilles otherwise,
16:17:29 elodilles #info stable gates seem to be in good state
16:17:38 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:17:49 elodilles and that's all from me
16:18:28 opendevreview Takashi Kajinami proposed openstack/nova master: libvirt: Remove tpm supoort detection for libvirt < 8.0.0 https://review.opendev.org/c/openstack/nova/+/952308
16:18:40 Uggla thanks elodilles and thanks bauzas for the reviews.
16:18:48 elodilles ++
16:19:09 Uggla #topic vmwareapi 3rd-party CI efforts Highlights
16:19:20 opendevreview Takashi Kajinami proposed openstack/nova master: libvirt: Drop redundant chown of tpm data directory https://review.opendev.org/c/openstack/nova/+/962446
16:19:29 Uggla fwiesel do you have something to share ?
16:20:21 opendevreview Takashi Kajinami proposed openstack/nova master: libvirt: Remove tpm supoort detection for libvirt < 8.0.0 https://review.opendev.org/c/openstack/nova/+/952308
16:20:22 fwiesel No, nothing from my side. Working on getting the cross-project dependencies in
16:20:22 opendevreview Takashi Kajinami proposed openstack/nova master: libvirt: Drop redundant chown of tpm data directory https://review.opendev.org/c/openstack/nova/+/962446
16:20:42 Uggla fwiesel ok thanks
16:20:53 Uggla #topic Gibi's news about eventlet removal
16:21:07 gibi o/
16:21:32 gibi Last week fwiesel reported issues from the compute eventlet removal series
16:21:56 gibi I'm fixed one problem https://review.opendev.org/c/openstack/nova/+/975172/5?usp=related-change
16:22:07 opendevreview Takashi Kajinami proposed openstack/nova master: AMD SEV: omit iommu='on' for virtio devices https://review.opendev.org/c/openstack/nova/+/909635
16:22:14 gibi and found a deeper one https://review.opendev.org/c/openstack/nova/+/965467/48#message-62f7ef828c38c33f322f72737b4016ace9b9f242
16:22:42 bauzas ack, will look at them
16:22:49 gibi The second is not resolved yet but I have plans to fix it
16:23:28 gibi other than that the improvement on the event delaying mechanism is now ready to (re)-review https://review.opendev.org/c/openstack/nova/+/974445/12
16:23:48 bauzas yup, on my plan
16:23:50 gibi and I think that is it
16:23:59 gibi Uggla: mic is back to you
16:24:16 gmaan nice, I will check it. It was ok both way for me as i commented in that change
16:24:18 gmaan i saw the next change in that series where libvirt driver was canceling all the submitted event during shutdown which is better.
16:24:32 gmaan but I will check the latest change
16:24:32 Uggla thanks gibi.
16:24:55 Uggla #topic Open discussion
16:25:10 erlon hey Uggla
16:25:16 erlon hey today :)
16:25:22 erlon *here
16:25:37 erlon first, sorry about missing the previous meeting. I dropped in the topic but couldn't attend.
16:26:18 erlon I have a customer who wants this bug fixed. After some investigation, I concluded that what is currently affecting them is bug #1741364, which is a different manifestation of a similar problem: the VM devices not being updated if the Ceph monitors change during the virtual machines' lifetime.
16:26:51 erlon #link https://bugs.launchpad.net/nova/+bug/1452641
16:27:09 erlon Bug #1741364 addresses the ephemeral part of it, while bug #1452641 deals with Cinder volume devices.
16:27:30 erlon #link launchpad.net/bugs/1741364
16:28:03 erlon With that said, I want to get some feedback regarding a potential fix for the issue: https://review.opendev.org/c/openstack/nova/+/974032
16:28:28 erlon I believe we don't need anything fancy; we just need to ensure that the ephemeral disk information is also updated whenever we do that for the RBD volumes. I think that change is close to what we need, but I was also considering whether it would be possible to patch nova-manage to allow batch operations, just like we do for volume attachments.
16:32:35 erlon so, I suppose nobody opposes :p
16:32:51 gibi :)
16:33:12 Uggla erlon, I guess everybody needs to load context too.
16:33:16 tkajinam so the point is that you don't want to stop and start the vm and looking for the way to update mon addrs keeping vms running ?
16:33:17 bauzas yeah
16:33:44 tkajinam if you stop and start the vm then I guess xml is regenerated and picks up the new mon addrs (correct me if I'm wrong)
16:34:40 erlon tkajinam: starting and stopping the VMs should be okay, actually I don't think should be possible to update the block device mapping without stopping.
16:35:22 tkajinam ah, ok
16:35:49 erlon tkajinam: so, that behaves like you're saying for the volume attachments. But if the virtual machine has ephemeral devices back it by RBD, those are not refreshed. The ask is to, make them behave like volumes.
16:37:43 erlon so, when you shelve, or migrate, you would get all volume mappings (cinder and ephemeral) updated (today only cinders are)
16:38:54 tkajinam sounds fair
16:38:55 Uggla erlon to my mind that sounds reasonable. I will add this patch to the review list.
16:39:57 erlon right, thanks. I will do a full review on it as well since I believe there's a few bits missing. And I'll propose something for nova-manage
16:40:26 Uggla ok
16:40:27 erlon nova-manage ephemeral_attachments refresh [INSTANCE_UUID]
16:40:27 erlon or
16:40:27 erlon nova-manage volume_attachment refresh --ephemeral [INSTANCE_UUID] [VOLUME_ID] [CONNECTOR_PATH]
16:40:45 tkajinam I'm wondering if a few other operations can resolve it. I feel like only providing live-migration to fix bdm would be incomplete from operator's perspective
16:41:56 erlon The first, would mix concepts (volume vs ephemeral), but in my opinion would make a smoother for the user experience. The second is more consistent, what would require more code and a new command

Earlier   Later