| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-05-13 | |||
| 16:28:24 | gibi | the two patches to land | |
| 16:28:35 | gibi | the long series is not ready but working on it | |
| 16:28:36 | sean-k-mooney | 37 is pretty short so i can proably look at that after the meeting | |
| 16:28:50 | gibi | that is all from me | |
| 16:28:56 | sean-k-mooney | and the hacking one i gues | |
| 16:29:02 | gibi | yepp | |
| 16:30:01 | Uggla | #topic Open discussion | |
| 16:30:21 | fwiesel | That would be my topic, I suppose. | |
| 16:30:23 | Uggla | fwiesel, can you go ahead with your topic | |
| 16:30:25 | fwiesel | Support for libvirt VIR_MIGRATE_PARAM_PARALLEL_CONNECTIONS | |
| 16:31:03 | fwiesel | So, since QEMU 2.11 and libvirt 5.2.0 there is support for using multiple threads in the precopy operation. | |
| 16:31:03 | sean-k-mooney | oh :) that could be useful | |
| 16:31:20 | fwiesel | I was wondering, if I can just to a specless blueprint for that? | |
| 16:31:50 | sean-k-mooney | i think that would be supported by our min qemu/libvirt versions | |
| 16:32:12 | sean-k-mooney | so it would really just be a config option to allow enabling it | |
| 16:32:16 | sean-k-mooney | and perhaps dicussing if it should be on or off by defualt | |
| 16:32:29 | gibi | would it be a compute config param to enable? Does it only need to be enabled on the source node? | |
| 16:32:41 | Uggla | I think because it require a config option a small spec will be worth it. | |
| 16:32:57 | sean-k-mooney | this is really only useful if you have more bandwith aviable on the migration link then a singel core can saturate. | |
| 16:33:01 | fwiesel | Ah, so a spec. I can do that | |
| 16:33:18 | fwiesel | Yes, we need roughly 12 threads to saturate our 200GigE links. | |
| 16:33:21 | sean-k-mooney | well it could be specless maybe but yes i blive this need to be set on the source | |
| 16:33:33 | Uggla | yes so we can bikeshed on the config name. :) | |
| 16:33:50 | sean-k-mooney | like the other migration parmaters i dont think it can be changed once the migration is started and that is done form the source node | |
| 16:34:39 | Uggla | sean-k-mooney, this is a parameter to pass to migrateToURI3, if I'm not wrong. | |
| 16:34:42 | sean-k-mooney | fwiesel: based on that math if you have a 25G link or grather you would benifit form this | |
| 16:34:52 | sean-k-mooney | Uggla: yes i belive it is | |
| 16:35:17 | gibi | Thanks. I'm OK with a specless but fine with a spec too | |
| 16:35:18 | Uggla | sean-k-mooney, I looked quickly before the call. | |
| 16:35:46 | sean-k-mooney | i belvie we were asked about this either in the ptg or on irc shourtly before it too | |
| 16:35:50 | Uggla | I think the spec is cool to discuss names and defaults | |
| 16:36:14 | Uggla | sean-k-mooney, more or less this is from masahito but this is another settigns | |
| 16:36:33 | sean-k-mooney | i think it makes sense to do so sepless or small spec is ok with me | |
| 16:36:44 | sean-k-mooney | *specless or a small spec | |
| 16:36:55 | sean-k-mooney | we can debate the name in the gerrit review | |
| 16:36:57 | fwiesel | The consensus seems then a small spec? | |
| 16:37:06 | sean-k-mooney | presumable its a new option in the libvirt section | |
| 16:37:15 | bauzas | I'd say that depends on the default value | |
| 16:37:32 | sean-k-mooney | like https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_inbound_addr | |
| 16:37:36 | bauzas | meaning whether we would have upgrade concerns | |
| 16:37:38 | fwiesel | I'd gone with a default that keeps the old settings. | |
| 16:37:46 | fwiesel | So, it is opt-in | |
| 16:38:03 | sean-k-mooney | if we default to off. i dont think there would be an upgrade concern | |
| 16:38:13 | sean-k-mooney | and we can consider changing the default in 2026.2+ | |
| 16:38:25 | bauzas | yup so then I specless works for me | |
| 16:38:27 | sean-k-mooney | we proably shoudl test it in nova-next | |
| 16:38:28 | gibi | opt-in works for me | |
| 16:38:39 | Uggla | ok so go for spec less | |
| 16:38:47 | bauzas | that's an easy enablement knob | |
| 16:38:55 | fwiesel | Perfect, saves me some work. | |
| 16:39:10 | sean-k-mooney | fwiesel: can you create a bluepirnt for this to tack it and detail that it will be off by default | |
| 16:39:29 | sean-k-mooney | unless you already have one? | |
| 16:39:37 | fwiesel | sean-k-mooney: will do. I haven't yet. | |
| 16:39:43 | Uggla | fwiesel, and ping me, so I would add it to the tracking doc. | |
| 16:39:57 | fwiesel | Uggla: Will do | |
| 16:40:02 | Uggla | thx | |
| 16:40:44 | Uggla | anything else to discuss, if not we can triage some bugs. | |
| 16:40:52 | sean-k-mooney | i have one quick item | |
| 16:41:06 | Uggla | shoot | |
| 16:41:13 | sean-k-mooney | so last week i asked frickler i think to update the channel topic if Uggla aggreed | |
| 16:41:32 | sean-k-mooney | which has now been done but they pointed out that we coudl also add ops to the channle https://opendev.org/openstack/project-config/src/commit/50197dce1589385b1256150bcd082093cf7e8898/accessbot/channels.yaml#L239 | |
| 16:41:38 | sean-k-mooney | nova currently does nto have any | |
| 16:41:49 | gibi | lets add some :) | |
| 16:41:53 | sean-k-mooney | do we want to do that so we can update the topic ectra our selves | |
| 16:41:54 | bauzas | I was thinking Dan was +o | |
| 16:42:08 | sean-k-mooney | dan might have it form something else | |
| 16:42:17 | sean-k-mooney | but we dont ahve anyone lised in the file today | |
| 16:42:25 | Uggla | I looked at it only gmaan if I recall well. | |
| 16:42:47 | bauzas | fair | |
| 16:42:49 | sean-k-mooney | shall i create a patch to do it? and if so who should we add | |
| 16:42:53 | dansmith | I was pretty sure I had ops at one point | |
| 16:42:54 | gmaan | I can do | |
| 16:43:02 | gmaan | I think I still have ops | |
| 16:43:05 | sean-k-mooney | Uggla: im also ok to delgate doign that to someone else | |
| 16:43:12 | bauzas | I could add french jokes to the chan title | |
| 16:43:45 | bauzas | but hey the PTL should have rights | |
| 16:44:21 | gmaan | I have from global ops, ++ to add nova specific also | |
| 16:44:26 | Uggla | sean-k-mooney, I can create this patch no worries. | |
| 16:44:36 | sean-k-mooney | Uggla: cool that all then | |
| 16:44:50 | sean-k-mooney | i just wanted to make sure we could udate the topic when needed | |
| 16:44:55 | Uggla | who wants to be ops ? | |
| 16:45:08 | bauzas | you should be | |
| 16:45:13 | gmaan | do we also need to update topic now or all good for now? | |
| 16:45:27 | Uggla | gmaan, topic is ok atm. | |
| 16:45:31 | gmaan | k | |
| 16:45:38 | sean-k-mooney | gmaan: it should be good now | |
| 16:45:51 | sean-k-mooney | the only thing that need to change was the status url | |
| 16:46:06 | gmaan | ++ | |
| 16:46:20 | sean-k-mooney | it was pointing to https://etherpad.opendev.org/p/nova-2025.1-status until last week | |
| 16:46:37 | sean-k-mooney | Uggla: that shoudl also proably get added to the nova PTL guide | |
| 16:46:43 | sean-k-mooney | as a thing to do at the start of each cycle | |
| 16:46:54 | Uggla | sean-k-mooney, ++ | |
| 16:46:57 | bauzas | yup | |
| 16:47:03 | bauzas | good idea | |
| 16:47:22 | Uggla | #action Update ptl guide to mention topic update | |
| 16:47:23 | sean-k-mooney | we have about 12 minutes left. want to traige a bug or two | |
| 16:47:33 | Uggla | yep | |
| 16:47:40 | Uggla | #topic Bug scrubbing | |
| 16:47:49 | Uggla | #link: https://etherpad.opendev.org/p/nova-bug-selection-for-triaging#L4 | |
| 16:48:25 | Uggla | First one: https://bugs.launchpad.net/nova/+bug/2106500 | |