Wednesday, 2026-02-04

opendevreviewGhanshyam proposed openstack/nova master: Add manager graceful shutdown timeout and wait  https://review.opendev.org/c/openstack/nova/+/97558602:00
gmaanbauzas: this is ready, gate is failed due to known broken nova-next job otherwise it pass the gate https://review.opendev.org/c/openstack/nova/+/975242/402:01
opendevreviewGhanshyam proposed openstack/nova master: Add manager graceful shutdown timeout and wait  https://review.opendev.org/c/openstack/nova/+/97558602:02
melwittsean-k-mooney: thanks, +202:18
*** mhen_ is now known as mhen02:30
opendevreviewGhanshyam proposed openstack/nova master: WIP: Use 2nd RPC server in compute operations  https://review.opendev.org/c/openstack/nova/+/97558804:16
opendevreviewTaketani Ryo proposed openstack/nova master: mem-enc: stop using _get_mem_encryption_config() for SEV checks  https://review.opendev.org/c/openstack/nova/+/96797008:06
opendevreviewTaketani Ryo proposed openstack/nova master: mem-enc: refactor memory encryption trait logic for extensiblity  https://review.opendev.org/c/openstack/nova/+/96797108:06
opendevreviewTaketani Ryo proposed openstack/nova master: mem-enc: make RP creation independent of specific encryption models  https://review.opendev.org/c/openstack/nova/+/96797208:06
opendevreviewTaketani Ryo proposed openstack/nova master: mem-enc: refactor _guest_configure_mem_encryption() for extensibility  https://review.opendev.org/c/openstack/nova/+/96797308:06
opendevreviewTaketani Ryo proposed openstack/nova master: mem-enc: adjust requirement checks for mem_encryption guests  https://review.opendev.org/c/openstack/nova/+/96797408:06
opendevreviewTaketani Ryo proposed openstack/nova master: mem-enc: introduce a check between mem_encryption and locked_memory  https://review.opendev.org/c/openstack/nova/+/97130008:06
sean-k-mooneygmaan: gibi speakign of the nova-next jobs if i can get a second core to review https://review.opendev.org/c/openstack/nova/+/975542 that will fix it10:10
sean-k-mooneyactully bauzas ^ if your around you might have time to take a look also10:19
bauzassure, I saw the gate failing10:20
sean-k-mooneyits basically the same issue we had with the disk serial for device_type=lun in lun mode the phsical aspect fo the backing lun like the serial and in this case sector size cannot be overriden by qemu/libvirt the are presented as is form the storage array to the vm so the fix is to just not set those parmaters in the xml for lun type volumes10:25
bauzasyup, I reviewed it10:26
*** ralonsoh_ is now known as ralonsoh10:26
bauzasthanks for amending the fixture, as I said10:26
sean-k-mooneyi spoke to the virt folks about it yesterday and they have created a rhel/libvirt bug to actully have libvirt validate this in the future instead of having ti fail at the qemu level10:26
sean-k-mooneybauzas ++ thanks once thats merged ill reply to mel's email to let folk know its safe to recheck10:27
opendevreviewBalazs Gibizer proposed openstack/nova master: Use an executor to delay STOPPED events  https://review.opendev.org/c/openstack/nova/+/97444511:15
opendevreviewBalazs Gibizer proposed openstack/nova master: Remove spawn_after  https://review.opendev.org/c/openstack/nova/+/97539611:15
opendevreviewBalazs Gibizer proposed openstack/nova master: Cleanup libvirt driver at service stop  https://review.opendev.org/c/openstack/nova/+/97512811:15
opendevreviewBalazs Gibizer proposed openstack/nova master: Fix full executor warning on noname executor  https://review.opendev.org/c/openstack/nova/+/97517211:15
opendevreviewBalazs Gibizer proposed openstack/nova master: Run nova-compute in native threading mode  https://review.opendev.org/c/openstack/nova/+/96546711:15
gibibauzas: ^^ removed the print() call11:15
*** debian is now known as Guest146312:21
opendevreviewBalazs Gibizer proposed openstack/nova master: DNM: Troubleshoot deadlocks in threading mode  https://review.opendev.org/c/openstack/nova/+/97551512:32
opendevreviewsean mooney proposed openstack/nova-specs master: add pci passthrough groups spec for 2026.2  https://review.opendev.org/c/openstack/nova-specs/+/97563513:27
opendevreviewsean mooney proposed openstack/nova-specs master: add pci passthrough groups spec for 2026.2  https://review.opendev.org/c/openstack/nova-specs/+/97563513:36
*** ralonsoh_ is now known as ralonsoh14:19
opendevreviewMax proposed openstack/nova master: fix: device_by_alias should respect config type  https://review.opendev.org/c/openstack/nova/+/97565116:04
sean-k-mooneygibi: ya so that was the orginal comemnt on the delay behavior. which is being adressed by https://review.opendev.org/c/openstack/nova/+/974445/14 so ill review it properly after i grab somethign to drink but we can likely proceed.16:14
sean-k-mooneynote i need to recheck the gate fix again because it had a network timeout downloaing pip packages form teh mirror16:14
sean-k-mooneygibi: i was thinking of https://review.opendev.org/c/openstack/nova/+/922497 and https://review.opendev.org/c/openstack/nova/+/905287/9  which on master is now https://github.com/openstack/nova/blob/master/nova/image/glance.py#L580-L586 so it looks like in threaded mode we jsut execute it inline and block on the upload16:39
sean-k-mooneyso unless we move snapshots to the long runting thread pool that will tie up an rpc thread for the entirty fo the galnce snapshot upload16:40
sean-k-mooneygibi: when you took over the eventlet work you didnt add a dedicated io thread pool but rather a defult thread pool but we didnt update that code to dispatch the upload to the thread pool.16:42
gibisean-k-mooney: thanks for the pointers. I don't see how that io executor helps, the usage in RBD is spawning a task to the executor and immediately blocking on waiting for the result. Logically that is the same as executing the function on the caller thread in my eyes (in native threading)17:18
gibihttps://review.opendev.org/c/openstack/nova/+/917962/8/nova/storage/rbd_utils.py#5617:19
sean-k-mooneyi wrote it before dan told me that the rbd client was doing that internally17:19
sean-k-mooneyso its not useful for that17:20
gibiack17:20
sean-k-mooneyso the up shot is we have 1 less executor then i tought we had (i.e. we dont have a dedicated io executor for long running file and api calls17:20
sean-k-mooney)17:21
sean-k-mooneyit was orgilly suggestign puting the neutron netrokign call on that but i guess the only thing that impoant to consider is the _upload_data function 17:22
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/image/glance.py#L580-L58617:22
gibiOK, I will check the _upload_data codepath17:22
sean-k-mooneyim not sure we want to block the RPC thread with doing the file upload for snapshots17:23
sean-k-mooneybut as dan also pointed out unless we have a futre we can pass in or simialr i dont know hwe we are going to deal with returning the image uuid that is created form this call17:24
sean-k-mooneywhen you do openstack server image create we need to return teh glance image id for the snapshot form the api if i recall correctly17:24
gibiyepp, I need to think about all these. 17:24
sean-k-mooneydoign it inline is fine if we move thie operation entrily to teh long runing thread pool but th ereply path is still an unknow i guess17:26
gibisean-k-mooney: food for thought. How do you feel about https://github.com/openstack/futurist/blob/master/futurist/_futures.py#L232 as a way out of deadlocks due to limited executor sizes?17:26
gibiDynamicThreadPoolExecutor17:26
sean-k-mooneyi have not looked at that before but i was debeating about creatin a new executor propsosla that handeled prities canclation and delayed exection17:27
gibifor the delayed execution I have this WIP in futurist https://review.opendev.org/c/openstack/futurist/+/97550817:27
sean-k-mooneygibi: but i dont feel terible about one that cna grow as a way out17:27
gibiyeah we still need to limit our parallel work due to IO and overall memory usage but at least the deadlock becomes something else :)17:28
sean-k-mooneyso the lib that watcher and zuul uses has lots of interest feature but the reason im not really suggesting that at the morment is that lib is 4? yes int a v4 rewirte which break backward compatiblity17:28
sean-k-mooney*4 years?17:29
sean-k-mooneygibi: ill try and rominate on it. im not a huge fan of async io. i dont hate it but i  was also wonderign if we could/should consider limited use fo an asynio executor 17:30
sean-k-mooneyif we were to use the DynamicThreadPoolExecutor17:32
sean-k-mooneyare you suggesting we woudl not set a max workers or set it relitivly high with the expcation taht in reality it will stay small?17:32
gibiI have to read on what the Dynamic supports regarding sizing but I see that it can grow and shrink17:33
sean-k-mooney""" If threads are not created often in your application, the number of idle17:33
sean-k-mooney    threads may stay high for a long time. To avoid it, you can call17:33
sean-k-mooney    :py:meth:`.maintain` periodically to keep the number of threads within17:33
sean-k-mooney    the thresholds."""17:33
sean-k-mooneywe might need to do that ^17:34
sean-k-mooneygibi: i dont hate that idea if im honest. but its proably the rpc pool in oslo service that woudl be the most benifical to use that with right?17:35
sean-k-mooneysorry in oslo.messaging17:36
gibiyeah that too :)17:36
sean-k-mooneyi know we can set an executor type when we create the rpc servier im wondering if we can just provide an rpc instance17:37
sean-k-mooney*executor instance17:37
sean-k-mooneyya its just the name https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/server.py#L226-L24017:38
sean-k-mooneyso we woudl have ot update https://github.com/openstack/oslo.messaging/blob/master/pyproject.toml#L5317:41
sean-k-mooneyor add a new value17:41
sean-k-mooneymight be worth suggeting that to the oslo folks and see what they think17:41
dansmithI'm not sure how the dynamic one really helps18:03
dansmithyou still have to set your max to the upper limit of what you're willing tolerate.. it uses less memory in slow times, which is a benefit, but it's still the same problem when you hit the limit18:03
gmaanyeah, it does not solve the limit issue. I think we should be gradually learning about those limit issue (after solving the known one) and keep improving the defaults limit or better separate executor if any specific operations causing problem18:06
* gibi need more brains18:19
gibihttps://etherpad.opendev.org/p/eventlet-executor-semaphore-limit this is my brain dump looking at the long running task executor possibilities18:36
gibiwe have a list of pros and cons to choose from18:36
gmaanthanks for catching those in etherpad18:38
opendevreviewBalazs Gibizer proposed openstack/nova master: Move the concurrent builds to its own Executor  https://review.opendev.org/c/openstack/nova/+/97569419:01
gibithis is the very raw idea of optionA) from the etherpad ^^ not tested at all :)19:01
gibiand that marks my end of day19:01
gibio/19:01
opendevreviewMarius Leustean proposed openstack/nova-specs master: Add spec for handling orphan BDMs from late RPC processing  https://review.opendev.org/c/openstack/nova-specs/+/97569819:43
opendevreviewMerged openstack/nova master: Fix blockio generation for LUN volumes  https://review.opendev.org/c/openstack/nova/+/97554222:20

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