Wednesday, 2024-10-23

*** thelounge5510 is now known as thelounge55100:22
mikalsean-k-mooney: sorry, I missed your message. I think some of the later patches might need some small tweaks, but I have them all passing on my private CI, that's just a case of merging them back to gerrit.02:48
mikalsean-k-mooney: that is, I can do that pretty quickkly once the spec is approved. I figured there wasn't much point before then.02:48
opendevreviewAmit Uniyal proposed openstack/nova master: Update Nova bdm with updated swap info  https://review.opendev.org/c/openstack/nova/+/92985806:32
*** bauzas_ is now known as bauzas09:57
*** bauzas_ is now known as bauzas10:26
sean-k-mooneymikal: feel free to update them if you have time no need to wait for the spec to be reappoved in this case but if you want to wait that is also ok10:30
opendevreviewRajesh Tailor proposed openstack/nova master: Fix case sensitive comparison  https://review.opendev.org/c/openstack/nova/+/93310713:33
bauzasreminder: our nova sessions will softly start at 1400UTC13:35
bauzasnova sessions start now14:03
bauzasgibi: sean-k-mooney: dansmith: want to join the nova session or prefer to stay on the eventlet room ?14:05
dansmithI have a glance topic right now14:05
dansmithI thought nova was vfio first?14:05
sean-k-mooneyill joing in a while 14:05
sean-k-mooneywe can start14:05
bauzasdansmith: yup, it will be vfio14:06
bauzassean-k-mooney: for the moment, I'm like the only core :)14:06
sean-k-mooneyim plannign to wait for 10 mins to see fi there are any other topics in the eventlet room14:06
gibieventlet room is finishing so I will jump soon to nova14:20
MengyangZhang[m]hello, I recently submitted a spec and blueprint to add burst length support to Cinder QoS: https://review.opendev.org/c/openstack/nova-specs/+/932653. I wanted to check if it has been successfully submitted and if it's on the community's radar. Since I've just joined the channel, I'm unable to view previous messages. Could you let me know if there's anything else I should be doing, or should I just wait for peer review?14:21
opendevreviewWill Szumski proposed openstack/nova stable/2023.1: Process unlimited exceptions raised by unplug_vifs  https://review.opendev.org/c/openstack/nova/+/93311514:23
tkajinamMengyangZhang[m], the spec is now visible in gerrit so was proposed successfully14:27
tkajinamMengyangZhang[m], you may add "blueprint: add-burst-length-support" to the commit message to associate the spec to the bp14:28
tkajinamthe past logs can be found at https://meetings.opendev.org/irclogs/14:28
opendevreviewPavlo Shchelokovskyy proposed openstack/placement master: CADF audit support for Placement API  https://review.opendev.org/c/openstack/placement/+/93311614:29
tkajinamMengyangZhang[m], this week is the vPTG week and have a few slots for video call to discuss the specs. I wonder if you can join to bring your topic14:30
tkajinamhttps://ptg.opendev.org/ptg.html14:30
MengyangZhang[m]<tkajinam> "Mengyang Zhang, this week is the..." <- what time is the meeting? I14:59
MengyangZhang[m]* meeting? I'd happy to talk about it14:59
tkajinamMengyangZhang[m], we are in the middle of meeting and the today's slot is reserved till 17UTC15:01
MengyangZhang[m]* meeting? I'm happy to talk about it15:02
tkajinamalternative we have 13UTC-17UTC slot reserved for Thursday and Friday.15:02
tkajinamhttps://etherpad.opendev.org/p/nova-2025.1-ptg15:02
tkajinamthe proposed topics are listed there15:02
MengyangZhang[m]Friday works for me15:03
tkajinamyou can put your topic at the bottom then. Note that we already have some topics scheduled so yours might be covered late15:04
tkajinam^^^ bauzas 15:04
MengyangZhang[m]tkajinam: np, have added it to the list of topics15:05
bauzastobias-urdin: are you available in 10 mins for discussing your topic in the etherpad ?15:13
opendevreviewMengyang Zhang proposed openstack/nova-specs master: Add Burst Length Support to Cinder QoS  https://review.opendev.org/c/openstack/nova-specs/+/93265315:16
bauzaslajoskatona: fancy discussing your topic in 5 mins ?15:21
bauzashttps://etherpad.opendev.org/p/nova-2025.1-ptg#L49915:22
opendevreviewTakashi Kajinami proposed openstack/nova master: Migrate MEM_ENCRYPTION_CONTEXT from root provider  https://review.opendev.org/c/openstack/nova/+/92181415:25
opendevreviewTakashi Kajinami proposed openstack/nova master: Detect AMD SEV-ES support  https://review.opendev.org/c/openstack/nova/+/92568515:26
opendevreviewTakashi Kajinami proposed openstack/nova master: Add hw_mem_encryption_model image property  https://review.opendev.org/c/openstack/nova/+/92770615:26
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Launch instances with SEV-ES memory encryption  https://review.opendev.org/c/openstack/nova/+/92610615:26
opendevreviewTakashi Kajinami proposed openstack/nova master: Detect AMD SEV-ES support  https://review.opendev.org/c/openstack/nova/+/92568515:27
opendevreviewTakashi Kajinami proposed openstack/nova master: Add hw_mem_encryption_model image property  https://review.opendev.org/c/openstack/nova/+/92770615:27
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Launch instances with SEV-ES memory encryption  https://review.opendev.org/c/openstack/nova/+/92610615:27
lajoskatonabauzas: Hi, I am on the Neutron room, so in worst case, but I liked the Friday time if that still can work15:28
bauzasnoted, we'll discuss this on Friday then15:28
lajoskatonabauzas: thanks15:29
bauzastmazur: as a reminder, horizon-nova x-p session at 1600UTC in the austin (nova) room15:49
tmazurbauzas, thanks! We will come. Can be late for a couple minutes since we have another cross project session now15:50
bauzasnoted15:51
atmarkhello, which table in the db is libvirt xml definition stored? 21:28
melwittatmark: libvirt xml definition are not stored in the db. they are not stored anywhere, they are generated on the fly22:30
atmarkmelwitt: does that mean I can edit xml file without nova overwritting it?  I have issue an  with live migrating an instance, libvirt thinks the disk.config of instance is stored locally where in fact it's in ceph https://paste.openstack.org/show/b1ABMBlvqzKQAZtvYnGc/22:58
melwittatmark: no, kind of the opposite. nova can overwrite it at certain times. you can temporarily edit it and it will stay until something triggers an xml regeneration, like a hard reboot of the guest for example23:00
melwittif you're trying to unwedge something it could work to edit the xml and do the thing you're trying to do but the root cause of why it's getting the wrong disk.config location would have to be solved for the issue to be really fixed23:02
atmarknova has to get the libvirt definitions somewhere to  generate xml, right ?23:04
melwittIIRC disk.config format/location is determined by the CONF.libvirt.images_type on the host, if it's 'rbd' it should generate xml for rbd. I'm not sure if you have a deployment with a mix of different CONF.libvirt.images_type on different compute hosts23:04
melwittit generates the definitions using a variety of data. if you're curious all the code is in nova/virt/libvirt/driver.py in get_*_xml methods23:06
melwittand all of the xml elements are represented as classes in nova/virt/libvirt/config.py23:08
atmarkSo this host used to  have `images_type = raw`  which tells to run VM locally and after a while decided mind  change to  `images_type = rbd`.   Do we need to rebuild the VM in order to switch definition to rbd?23:11
atmark after a while decided  to change it  `images_type = rbd`* 23:12
atmarkI'll look into the code23:13
atmarkThanks23:13
melwittah ok, that explains it. you may be able to fix it by doing a 'server reboot --hard'. that's the go-to for regenerating xml. as long as nova will re-read the CONF to generate, it should work, but I don't remember if it will re-read or not. I think it should but not 100% sure23:13
melwitt*re-read the conf for determining the config drive format23:13
atmarkI'll give that try23:14
atmarkThanks23:14

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!