| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-12-05 | |||
| 10:18:51 | noonedeadpunk | yeah, I knew about os_type, but I didn't know about hidden logic behind it:) | |
| 10:19:35 | noonedeadpunk | will propose documentation update probably :) | |
| 10:19:58 | gibi | noonedeadpunk: thanks | |
| 10:32:57 | opendevreview | Balazs Gibizer proposed openstack/nova master: Upgrade note for concurrency mode default change https://review.opendev.org/c/openstack/nova/+/969888 | |
| 10:33:49 | gibi | gmaan: sean-k-mooney: dansmith: ^^ this is what I come up with based on the discussion about the upgrade impact of eventlet removal and our default mode change in G | |
| 10:54:20 | opendevreview | Lajos Katona proposed openstack/nova master: WIP: Use SDK for Neutron Ports https://review.opendev.org/c/openstack/nova/+/969298 | |
| 11:00:46 | sean-k-mooney | gibi: im not sure i agree with the recommendation to decouple the cahnge in mode in gerneal but its a more reasonable recomendtion for slurp upgrades | |
| 11:01:49 | sean-k-mooney | i dont really think we shoudl be recommendign that operators every use the env var out side of optin in to threadign to test early | |
| 11:02:15 | sean-k-mooney | it does exist as an escape hatch if we messed up | |
| 11:03:10 | sean-k-mooney | so i dont object to it existing just that for me makeing the swtich trasnparent to the end user is very imporant but i get the performance tuning concern | |
| 11:03:54 | sean-k-mooney | gibi: do we know if any of the larger operators have started testign treading mode since the 2025.2 release? | |
| 11:15:53 | opendevreview | Will Szumski proposed openstack/nova master: Fix race betweem instance claim and anti affinity check https://review.opendev.org/c/openstack/nova/+/969894 | |
| 11:15:53 | opendevreview | Will Szumski proposed openstack/nova master: WIP: Adds regression test for bug LP#2132984 https://review.opendev.org/c/openstack/nova/+/969380 | |
| 12:14:49 | gibi | sean-k-mooney: I got no indication if any large operator testing or tested threading mode in nova | |
| 12:16:03 | gibi | sean-k-mooney: I think one of the main reason to have a way to switch between modes is to avoid big bang integration of the threading mode during upgrade. Especially due to the performance tuning needs. | |
| 12:16:46 | gibi | sean-k-mooney: if it helps then I can try to give an oslo config flag instead of a env variable, but I don't see a good ROI of that at the moment | |
| 12:17:32 | sean-k-mooney | so that was explcit not a goal for me because i saw it as a failure on our part if operatos needed to think about htis to that degree | |
| 12:17:54 | sean-k-mooney | ie.. the uptrade shoudl be tansparent becuase we shoudl get the default right before chanigng them | |
| 12:18:11 | sean-k-mooney | but ya i dont think we need to make it an oslo config | |
| 12:18:51 | sean-k-mooney | im just really hoping that most operator will upgrade form 2026.1 to 2027.1 and not notice that we changed the threadning mode | |
| 12:19:23 | gibi | the problem for me is that I cannot define good default that will work for differntly sized and shaped deployments | |
| 12:19:42 | gibi | in the past we used large numbers as pool size so that covered a wide range of deployments | |
| 12:19:53 | gibi | with threading we cannot use those large numbers any more without consequences | |
| 12:26:42 | sean-k-mooney | yep i understand. given we only supprot say 10 boot operation on a server or a limite number of migraton ectra i think the small numbers for the comptue are actully likely to be reasonble | |
| 12:27:09 | sean-k-mooney | for the api the scaling mode has alwasy been mainly via proceses, | |
| 12:27:25 | sean-k-mooney | the schduler and conductor are probaly the ones i woudl be most concerned with | |
| 12:28:14 | sean-k-mooney | both are horizontally scable and virtucally scalabel with workers but ya they may need different tuneing | |
| 12:28:57 | sean-k-mooney | gibi: i am quitely hopeful that we will see a similar uplift in performance that ironic saw although we may have been using less problematic patterns | |
| 12:58:15 | gibi | scatter gather across multi cell clouds will not scale by scaling the nova-api process | |
| 12:58:30 | gibi | it will only scale if you scale the number of threads close to the number of cells in the threadpool | |
| 14:16:14 | opendevreview | Balazs Gibizer proposed openstack/nova master: Enable mypy on nova/utils.py https://review.opendev.org/c/openstack/nova/+/969936 | |
| 15:01:07 | dansmith | bauzas: can you +W this trivial one-liner mock fix? https://review.opendev.org/c/openstack/nova/+/969503 | |
| 15:01:23 | dansmith | we didn't catch it on initial merge because of the bug fixed by the patch above it | |
| 15:02:14 | bauzas | ack | |
| 15:02:49 | dansmith | thanks | |
| 15:03:02 | dansmith | the patch above would be nice too, but not as trivial | |
| 16:33:23 | gmaan | gibi: ack, will take alook today | |
| 16:34:15 | gmaan | bauzas: gibi sean-k-mooney I think +w was missed until something we are waiting for, otherwise, can either of you please hit +w https://review.opendev.org/c/openstack/nova-specs/+/969543 | |
| 16:53:18 | sean-k-mooney | gmaan: well for the backlog spec i guess | |
| 17:06:39 | gmaan | sean-k-mooney: did not get? this is in the backlog spec | |
| 17:33:44 | JayF | Stable backport of an Ironic bugfix, cleanly applied, V+1 already, for your consideration: https://review.opendev.org/c/openstack/nova/+/969833 | |
| 17:38:06 | sean-k-mooney | gmaan: we are now techinically past spec freeze but given that is a backlog spec change that was +2id but not +w to allow folks to review i think we can proceed with it | |
| 17:44:39 | opendevreview | Merged openstack/nova master: Fix missing guest.migrate(parallel=) mock arg https://review.opendev.org/c/openstack/nova/+/969503 | |
| 17:47:01 | opendevreview | Merged openstack/nova-specs master: Add spec3 in graceful shutdown backlog spec https://review.opendev.org/c/openstack/nova-specs/+/969543 | |
| 18:09:39 | opendevreview | sean mooney proposed openstack/nova-specs master: add spec for resource tracker notifications https://review.opendev.org/c/openstack/nova-specs/+/967712 | |
| 18:10:55 | opendevreview | Merged openstack/nova master: Collect result of _live_migration_operation https://review.opendev.org/c/openstack/nova/+/969501 | |
| 18:38:37 | opendevreview | melanie witt proposed openstack/nova master: Make QEMU_IMG_LIMITS process limits configurable https://review.opendev.org/c/openstack/nova/+/969538 | |
| 18:40:23 | melwitt | gibi: changed to Closes-Bug ^ and added a few more words to the commit message | |
| 19:06:31 | gmaan | sean-k-mooney: yeah, that is my understanding too. | |
| 20:42:00 | opendevreview | melanie witt proposed openstack/nova master: Make QEMU_IMG_LIMITS process limits configurable https://review.opendev.org/c/openstack/nova/+/969538 | |
| #openstack-nova - 2025-12-06 | |||
| 08:20:37 | opendevreview | Takashi Kajinami proposed openstack/nova master: DNM: testing ... https://review.opendev.org/c/openstack/nova/+/970011 | |
| 16:36:34 | opendevreview | Takashi Kajinami proposed openstack/nova master: Migrate upper functional job to Python 3.13 https://review.opendev.org/c/openstack/nova/+/970011 | |
| #openstack-nova - 2025-12-07 | |||
| 14:36:18 | opendevreview | Takashi Kajinami proposed openstack/nova master: Migrate upper functional job to Python 3.13 https://review.opendev.org/c/openstack/nova/+/970011 | |
| 14:39:32 | opendevreview | Takashi Kajinami proposed openstack/placement master: DNM: testing https://review.opendev.org/c/openstack/placement/+/970052 | |
| 14:53:46 | opendevreview | Takashi Kajinami proposed openstack/placement master: Migrate upper functional job to Python 3.13 https://review.opendev.org/c/openstack/placement/+/970052 | |
| 14:59:37 | opendevreview | Takashi Kajinami proposed openstack/placement master: Migrate upper functional job to Python 3.13 https://review.opendev.org/c/openstack/placement/+/970052 | |
| 15:00:54 | opendevreview | Takashi Kajinami proposed openstack/osc-placement master: Add Python 3.13 functional tests https://review.opendev.org/c/openstack/osc-placement/+/970058 | |
| 16:04:00 | opendevreview | Takashi Kajinami proposed openstack/osc-placement master: Add Python 3.13 functional tests https://review.opendev.org/c/openstack/osc-placement/+/970058 | |
| 16:18:17 | opendevreview | Takashi Kajinami proposed openstack/nova master: Replace obsolete PCRE packages https://review.opendev.org/c/openstack/nova/+/970063 | |
| 16:21:20 | opendevreview | Takashi Kajinami proposed openstack/python-novaclient master: Replace obsolete PCRE packages https://review.opendev.org/c/openstack/python-novaclient/+/970066 | |
| 16:22:24 | opendevreview | Takashi Kajinami proposed openstack/python-novaclient master: Replace obsolete PCRE packages https://review.opendev.org/c/openstack/python-novaclient/+/970066 | |
| 16:24:56 | opendevreview | Takashi Kajinami proposed openstack/osc-placement master: Replace obsolete PCRE packages https://review.opendev.org/c/openstack/osc-placement/+/970067 | |
| 16:25:34 | opendevreview | Takashi Kajinami proposed openstack/osc-placement master: Add Python 3.13 functional tests https://review.opendev.org/c/openstack/osc-placement/+/970058 | |
| 16:27:21 | opendevreview | Takashi Kajinami proposed openstack/placement master: Replace obsolete PCRE packages https://review.opendev.org/c/openstack/placement/+/970068 | |
| 16:38:09 | opendevreview | Takashi Kajinami proposed openstack/osc-placement master: Add Python 3.13 functional tests https://review.opendev.org/c/openstack/osc-placement/+/970058 | |
| 17:02:46 | opendevreview | Takashi Kajinami proposed openstack/nova master: Migrate upper functional job to Python 3.13 https://review.opendev.org/c/openstack/nova/+/970011 | |
| 17:26:47 | opendevreview | Takashi Kajinami proposed openstack/placement master: Migrate upper functional job to Python 3.13 https://review.opendev.org/c/openstack/placement/+/970052 | |
| 17:29:33 | opendevreview | Balazs Gibizer proposed openstack/nova master: Remove eventlet from CacheConcurrencyTestCase https://review.opendev.org/c/openstack/nova/+/970069 | |
| 17:32:36 | opendevreview | Takashi Kajinami proposed openstack/osc-placement master: Add Python 3.13 functional tests https://review.opendev.org/c/openstack/osc-placement/+/970058 | |
| 17:58:42 | opendevreview | Balazs Gibizer proposed openstack/nova master: Remove eventlet from CacheConcurrencyTestCase https://review.opendev.org/c/openstack/nova/+/970069 | |
| 17:58:43 | opendevreview | Balazs Gibizer proposed openstack/nova master: Remove eventlet from libvirt/test_driver https://review.opendev.org/c/openstack/nova/+/970070 | |
| 18:37:11 | opendevreview | Balazs Gibizer proposed openstack/nova master: Remove eventlet from libvirt/volume/test_mount https://review.opendev.org/c/openstack/nova/+/970071 | |
| #openstack-nova - 2025-12-08 | |||
| 00:45:40 | opendevreview | Seyeong Kim proposed openstack/nova master: libvirt: Support boot_index for multiple block devices https://review.opendev.org/c/openstack/nova/+/963665 | |
| 07:27:49 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: create generic check for mem encryption support by host https://review.opendev.org/c/openstack/nova/+/967969 | |
| 07:27:50 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: remove explicit SEV dependency from nova.scheduler.utils https://review.opendev.org/c/openstack/nova/+/967971 | |
| 07:27:50 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: stop using _get_mem_encryption_config() for SEV checks https://review.opendev.org/c/openstack/nova/+/967970 | |
| 07:27:51 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: fix code that assumes SEV in configuring guests https://review.opendev.org/c/openstack/nova/+/967973 | |
| 07:27:51 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: make RP creation independent of specific encryption models https://review.opendev.org/c/openstack/nova/+/967972 | |
| 07:27:52 | opendevreview | Taketani Ryo proposed openstack/nova master: mem-enc: fix requirement checks for mem_encryption guests https://review.opendev.org/c/openstack/nova/+/967974 | |
| 08:38:18 | opendevreview | Artem Vasilyev proposed openstack/nova master: Fix functional tests on macOS https://review.opendev.org/c/openstack/nova/+/937727 | |
| 08:38:50 | opendevreview | Artem Vasilyev proposed openstack/nova master: Fix functional tests on macOS https://review.opendev.org/c/openstack/nova/+/937727 | |
| 16:16:20 | opendevreview | Dmitriy Rabotyagov proposed openstack/nova-specs master: [spec] Add Cross-AZ scheduling blueprint https://review.opendev.org/c/openstack/nova-specs/+/900296 | |
| 16:41:28 | thill | Hello! Looking for additional feedback on this spec https://review.opendev.org/c/openstack/nova-specs/+/968065. Hoping to work through ideas/concerns to find a solution to our problem and it's proving to be a bit more difficult than anticipated. | |
| 18:35:31 | sean-k-mooney | thill: ignoring the detail of the spec for a minute teh spec freeze for this cycle was last thursday meaing that by defult this will have to be repropsoed for 2026.2 | |
| 18:37:29 | sean-k-mooney | in general usign teh nvoa user to allwo access to a resuce that a user could not otherwise use si privldage eslcaltion so allwoign a user to boot form a image they canot normally download is generally a security problem | |
| 18:38:31 | sean-k-mooney | the user can exfiltrate any data form teh image by just booting form a rescue image and copyint the block device or chreating a snapshot and download that | |
| 18:38:52 | sean-k-mooney | so im not really seaing a compleing reason to supprot booting from an image you cant download | |
| 19:01:35 | jgwentworth | sean-k-mooney: that's my thought on it as well ... if you can boot an instance from an image, you can effectively download the image. I appreciate that having to copy it is more difficult than being able to use the download API ... but the fact that the user can still effectively download it makes the idea of "can boot but cannot download" not so compelling to me either | |
| 19:38:13 | thill | Fair enough! I don't have any arguments against that logic at this point. I'll bubble this up and see what we want to do going forward. Thank you! | |
| 22:18:35 | opendevreview | Merged openstack/nova master: Use consistent program name for wsgi scripts and entry points https://review.opendev.org/c/openstack/nova/+/942605 | |
| 23:02:07 | JayF | Stable patch for Ironic 2024.2, already +2 from Elod, everything applied cleanly, if someone would help me land it'd be awesome: https://review.opendev.org/c/openstack/nova/+/969833 | |
| #openstack-nova - 2025-12-09 | |||
| 07:38:02 | opendevreview | Artem Vasilyev proposed openstack/nova master: Fix functional tests and mypy on macOS https://review.opendev.org/c/openstack/nova/+/937727 | |
| 09:31:41 | opendevreview | Merged openstack/nova master: Remove openSUSE/SLES from install guide https://review.opendev.org/c/openstack/nova/+/949324 | |
| 09:33:34 | opendevreview | Ivan Anfimov proposed openstack/nova master: doc: Enabling of using LibvirtDriver for compute node https://review.opendev.org/c/openstack/nova/+/939325 | |
| 09:33:39 | opendevreview | Ivan Anfimov proposed openstack/nova master: doc: Enabling of using LibvirtDriver for compute node https://review.opendev.org/c/openstack/nova/+/939325 | |
| 11:51:21 | opendevreview | Rajesh Tailor proposed openstack/nova master: Add functional reproducer for bug 2096884 https://review.opendev.org/c/openstack/nova/+/970238 | |
| 11:53:24 | DominikDanelski[m] | sean-k-mooney: Sorry, I wasn't on the other end of the discussion, so I'm not sure how it works. Are you normally notified on comments with replies that haven't been resolved by them? I refer to https://review.opendev.org/c/openstack/nova/+/969251/comment/7f85f631_a6a7fdbb/ Of course take your time, I only wanted to confirm that I've done it the right way. | |
| 11:55:04 | sean-k-mooney | DominikDanelski[m] so when yyou make the requeted change you shoudl mark it as done. if the ocmment is just geneal feedback but does not requrie a change you can mark it as acknolaged or you can reply and tick resolved in the ui to show the comment is nolonger relevnet | |
| 11:55:49 | sean-k-mooney | for that comment specificly i will get an emial when you updated the patch but not nessialy on a comment | |
| 11:56:15 | sean-k-mooney | the reason i asked you ot use a explcit flavor is its is not obvious why the excption should be raised without finding what the defualt flaovr is | |