Earlier  
Posted Nick Remark
#openstack-nova - 2025-10-29
12:18:16 sean-k-mooney its proably less broken then it was in the past now that we supprot the ironic sharding feature
12:18:18 iurygregory yeah, we only have two topics the graphical console and boot the machines from NVMe-over-TCP (nova+cinder)
12:18:27 sean-k-mooney cool
12:18:48 iurygregory feel free to add info in the etherpad if you want also
12:18:55 iurygregory https://etherpad.opendev.org/p/ironic-ptg-2026.1#L667
12:19:23 sean-k-mooney iurygregory: this might be of relevence to ironichttps://review.opendev.org/c/openstack/nova-specs/+/471815
12:20:06 iurygregory sean-k-mooney, for which topic?
12:20:14 sean-k-mooney although that more about supproting the vlan trunk info for neutron trunk ports in genreal in the metadata
12:20:54 sean-k-mooney iurygregory: not for any of the current ones it just hat mentionign it because one of the use cases is "Once the BM server is booted up with Ironic, its networking interfaces can be
12:20:56 sean-k-mooney automatically configured and brought up."
12:21:34 sean-k-mooney iurygregory: i belive ye implented a feature very much like this on your side in the last release or twoo so this may now onlybe relevent to other virt drivers
12:21:40 sean-k-mooney just sharing for awareness
12:26:35 iurygregory ack
12:26:46 iurygregory tks sean-k-mooney
12:26:52 iurygregory fyi TheJulia ^
12:49:41 TheJulia cardoe: w/r/t the spec sean mentioned, any n-g-s impact anticipated?
12:50:19 cardoe The vlan trunk? No
12:50:40 cardoe We run the patches and Mirantis runs the patches in prod for well over a year.
12:50:42 TheJulia but shouldn't there be switch configuration to represent it?
12:51:11 cardoe Of course. But this is about passing the trunk port data to the server so it knows how to configure its interfaces.
12:51:46 sean-k-mooney TheJulia: the vlan that is presented to the guest is a public atibute of neutorn turnk prot api meaning the end user get to choose it
12:51:46 cardoe This is just representing what’s in neutron to the server.
12:51:57 sean-k-mooney n-g-s would have to cofnigure that mapping on the switch port
12:52:12 sean-k-mooney but that seperate form passing the infor to the vm in the metadta
12:52:21 cardoe Exactly
12:54:12 TheJulia Okay, looks like there is already code there to handle trunks specifically
12:54:13 cardoe TheJulia: https://github.com/openstack/networking-generic-switch/blob/master/networking_generic_switch/trunk_driver.py
12:54:22 cardoe There's the implementation of n-g-s handling it already.
12:54:34 TheJulia yeah, I found that and in the mech driver, I just haven't had time and caffination to compeltely wrap my head around it so far this morning
12:54:57 TheJulia Anyway, thanks for the quick responses!
12:55:19 cardoe Yeah we implemented this ages ago in there.
12:55:38 cardoe Along with tests and tests for tempest which depend on the change to nova.
12:56:37 cardoe There’s additional tests for neutron as well and bug fixes for some corner cases with neutron and its trunk handling.
12:56:41 TheJulia ... yeah, I remember now
12:56:49 TheJulia I had to fix the tests from blindly running
12:57:22 cardoe Neutron accepted the change to tighten up the spec on their side as well.
12:58:49 cardoe It was a series of patches developed by Mirantis, Red Hat and another company. The unnamed company is who I pressed on their CTO to stop developing OpenStack downstream and get involved upstream. To pus their developers to join the projects.
13:00:48 cardoe I naively said I just got elected to the TC. Let me show you how it’s not hard to engage the community and get a benefit from that. I thought this has a spec and patches written by a group covering multiple companies. It’ll be easy.
13:02:45 cardoe I pointed the CTO to asks by projects for more people to get engaged. He told me their work just gets ignored. I thought I could get more developers to engage nova and neutron.
13:03:19 cardoe I was proven wrong.
13:42:41 Uggla Info: Start of PTG session in ~20mn
13:42:50 Uggla Topic: Discuss if the CPU comparison beetween src host and dst host can not be improved or is it still relevent ?
14:03:22 nisha04 uggla: Hi regarding the session schedule on etherpad. Japan morning with US folks also works for me. I can also join the original PTG timeslot (14:00 to 18:00 UTC) on Thu/Fri if the morning session is difficult. What do you think?
14:50:35 nicolairuckel How can I see which room I have to join for my topic?
14:50:44 nicolairuckel For the PTG
14:51:27 nicolairuckel Uggla, do I just join the Nova room?
14:51:39 auniyal https://ptg.opendev.org/ptg.html -
14:51:46 auniyal you can join here https://meetpad.opendev.org/nova-2026.1-ptg
14:52:11 nicolairuckel thanks!
14:52:21 Uggla nicolairuckel, yes please join using the link above from auniyal
14:52:38 Uggla We are still in the cinder/nova x team session.
15:41:39 opendevreview melanie witt proposed openstack/nova master: libvirt: add configuration option for volume AIO mode https://review.opendev.org/c/openstack/nova/+/964848
15:46:06 opendevreview melanie witt proposed openstack/nova master: libvirt: add configuration option for volume AIO mode https://review.opendev.org/c/openstack/nova/+/964848
16:05:17 dansmith Uggla: man, feels like this is not the best use of nova's time, eh?
16:07:37 Uggla dansmith it was not what was expected.
16:08:25 Uggla cinder should join later.
16:08:27 dansmith were there specific topics we were supposed to be getting discussed? because if so, we should probably decide if we're going to discuss those and if not, bail
16:08:32 dansmith cinder is on the call
16:08:41 dansmith this is all ironic->cinder discussion AFAICT
16:11:34 Uggla yep they have requested us too. But I agree.
16:11:56 Uggla I just hope this topic will stop soon to discuss ours.
16:15:58 tkajinam :-P
16:52:49 gibi I guess we break until the top of the hour
17:03:14 bauzas Uggla: where is the nova-neutron discussion ?
17:03:21 bauzas I joined the neutron room but I was alone
17:03:45 Uggla nop it is manilla one
17:03:48 Uggla on our room
17:03:57 Uggla bauzas ^
17:25:08 dansmith Uggla: is there a link to the room somewhere? I'm missing it
17:26:09 bauzas Uggla: I think we could discuss the AZ-soft-anti-affinity topic from noonedeadpunk at the very beginning of the nova sessions tomorrow
17:26:30 Uggla dansmith: https://meetpad.opendev.org/oct2025-ptg-neutron
17:26:46 bauzas 2 hours for confidential computing topics seems to be good, but we could throw 30 mins from that and give it to the AZ thing
17:27:26 Uggla bauzas, I agree but more at the end. Because confidential computing owners are located in Japan
17:27:31 dansmith Uggla: thanks, might be good to have these all linked
17:27:56 Uggla dansmith, https://ptg.opendev.org/ptg.html
17:28:15 dansmith I know where to find them, I mean on the etherpad :)
17:28:32 Uggla dansmith, you are a bit hard with me today. :)
17:30:24 dansmith not intending to be
17:40:53 noonedeadpunk bauzas: Uggla would be great to get info about timing today, as it would highly influence my plans for tomorrow (need to have a 8h drive during tomorrow, so need to schedule it or stops)
17:41:48 bauzas noonedeadpunk: what would be your preference time-wise ?
17:42:52 noonedeadpunk I think closer to the end would be better for me...
17:43:10 noonedeadpunk but probably can do 14 utc as well
17:43:54 noonedeadpunk I'm more flexible today then I'll be tomorrow :D
17:44:17 noonedeadpunk 15/16 utc slots are least convenient
17:44:40 Uggla noonedeadpunk, I think we can have something Thu around 15h30/15/45 --> 1600 UTV
17:44:47 Uggla *UTC
17:45:28 Uggla or Friday 16:30 UTC
17:45:51 noonedeadpunk friday 16-30 conflicts with TC
17:46:41 Uggla Friday 15:30 ?
17:47:05 noonedeadpunk works for me, yes
17:47:36 Uggla noonedeadpunk sold I will try to update the schedule to reflect that.
17:47:43 noonedeadpunk ++ thanks!
17:48:27 noonedeadpunk if you'll be re-shuffling schedule on Friday - I have another topic for there already
17:49:06 noonedeadpunk so if they could be relatively together - that would be grand
17:56:27 tbabel Hello, looking for help wrapping my head around instance boot workflow. In particular i'm curious how the image is downloaded to a compute node(in the event it doesn't exist). Does it use the nova service user or possibly user credentials themselves? Asking because i'm trying to resolve a glance/image polilcy issue and not quite sure where to target a fix at this point. Any tips are greatly appreciated!
17:58:51 bauzas Uggla: nice try for letting people hearing French
17:59:23 Uggla ?
17:59:38 bauzas but I'd propose you to cut your mic, there are other ways to learn French
18:00:00 Uggla just realize it was open, sorry about that
18:00:20 Uggla I hope it was not too much disturbing

Earlier   Later