Earlier  
Posted Nick Remark
#openstack-nova - 2026-04-13
17:23:31 phildree[m] I have to be honest, I first have to read up on what the PTG exactly is and how it works
17:24:15 sean-k-mooney ack its basically a workign session wehre user/operators/devleoper talk about our plans for the next release and pain points
17:24:51 sean-k-mooney it operats now as a virual event with an eterphad for notes and adgena and jitsi meet as the video confernce tool
17:25:01 sean-k-mooney its free to attend. they used ot be inperson events
17:25:15 phildree[m] Then this would probably make sense from my point of view (even if its just to gain a better understanding of the whole project)
17:25:23 sean-k-mooney if you cant attend thats fine too.
17:25:42 gmaan phildree[m]: I agree with sean-k-mooney that periodic handshake over RPC is expensive especially in scale env
17:26:26 sean-k-mooney gmaan: im kind of wondering if we can maybke marke the node as down sooner by monitoring failed/timedout rpc calls of soemthing liek that
17:26:35 gmaan I also have not read the spec but does compute service up check not enough? that is kind of periodic check if service is down or not
17:26:44 sean-k-mooney i.e. only do a condotor to compute ping in that case to confirm the state
17:27:26 sean-k-mooney gmaan: there was at least one case in the psat where the comptue service is up but the rabbit queue was deleted
17:27:45 sean-k-mooney so it coudl send rpc calles like the status update but not recive them
17:27:48 gmaan " failed/timedout rpc calls" might not give actual result and can end up in false result.
17:27:59 sean-k-mooney https://docs.openstack.org/nova/latest/configuration/config.html#oslo_messaging_rabbit.direct_mandatory_flag was partly added to prevent that
17:28:06 phildree[m] gmaan: I think if you do the service up check it relies on the DB entries based on heartbeats which is exactly what our issues was because the heartbeat may keep working while the requests from conductor to compute failed
17:28:15 gmaan yeah not RPC
17:28:47 phildree[m] Just like sean-k-mooney just described
17:29:26 gmaan yeah, that is true and existing challenge
17:30:38 sean-k-mooney phildree[m]: the reall issue is take an enve with 500 nodes and 3 conductors. we technically ahve a leader election fetrue in the conductor but if we didnt use that ever 300 second (our default perodic interval) we would send 1500 messages 3 form each conduxtor x 500 compute nodes
17:30:54 gmaan so what is actual issue? conductor to compute RPC call fail the it give status to check if compute service is up or not if yes then RPC is down right?
17:31:34 sean-k-mooney in rare cases the compute can be up enough for the status to be up but a call to the compute form the api will fail to boot a vm
17:31:52 phildree[m] In my proposal the handshake is compute initiated in order to avoid leader stuff and states in the conductor
17:32:37 sean-k-mooney phildree[m]: well we typiclly have 3-5 conductors per cell and can have 300-1500 compute per cell in large clouds
17:33:36 gmaan I am not saying 'service up' is reliable source but my question is do we want to automate it in conductor to check compute before call otherwise asl sch to select other dest? or just for clear troubleshooting and error message that what exactly is down?
17:33:49 gmaan s/asl/ask
17:34:55 sean-k-mooney gmaan: ya im not sayign we shoudl do this im just playing devils advocate
17:35:45 gmaan sean-k-mooney: or the healthcheck proposal is good fit here but is the latest proposal check RPC health also?
17:35:55 phildree[m] it like a tcp Syn (compute send a request to any conductor), Syn-Ack (conductor replies to that tiny request), Ack (compute initiates the regular heartbeat as is)
17:35:55 phildree[m] This way when any part of the communction is broken the node does not appear as up
17:35:55 phildree[m] But in order to reduce RPCs i think also just a periodic ping without compute base initiation might be feasible but will have the issue of coordination etc..
17:36:21 sean-k-mooney gmaan: it was goign to catch connection closed events and similar on the comptue and report if the rpc bus was working
17:36:26 sean-k-mooney but not by active probing
17:36:34 sean-k-mooney only by recoreding if we got an excption
17:36:34 gmaan k
17:36:41 sean-k-mooney so it woudl not really help in this case
17:36:41 gmaan ++
17:36:50 gmaan yeah
17:38:53 gmaan do not have any perfect solution as of now but let's discuss it in PTG
17:39:47 phildree[m] Ok, thanks anyway for the engagement, I really appreciate you guys taking your time :)
19:20:17 opendevreview Merged openstack/nova stable/2026.1: fix: device_by_alias should respect config type https://review.opendev.org/c/openstack/nova/+/983989
19:58:52 opendevreview John Garbutt proposed openstack/nova master: Make PCPUs not land on VCPUs by default https://review.opendev.org/c/openstack/nova/+/975779
19:59:20 opendevreview John Garbutt proposed openstack/nova master: Fix ironic instance rebuild with API >=2.93 https://review.opendev.org/c/openstack/nova/+/963298
20:24:21 melwitt dansmith: there is one more small patch that was split out from the 'user' live migration patch that is ready for review at your convenience https://review.opendev.org/c/openstack/nova/+/983505
21:00:29 dansmith ah yep, the other one, sorry I guess I missed that when hitting the first one
21:00:30 dansmith done now
21:16:32 melwitt dansmith: thanks!!
22:46:32 opendevreview melanie witt proposed openstack/nova master: [WIP] how borken is ipv6 only ceph. https://review.opendev.org/c/openstack/nova/+/982302
22:51:07 opendevreview melanie witt proposed openstack/nova master: [WIP] how borken is ipv6 only ceph. https://review.opendev.org/c/openstack/nova/+/982302
#openstack-nova - 2026-04-14
00:30:42 opendevreview melanie witt proposed openstack/nova master: CellDatabases: replace shared lock with thread-local cell routing https://review.opendev.org/c/openstack/nova/+/984480
00:30:43 opendevreview melanie witt proposed openstack/nova master: Database: use file-backed SQLite for native threading https://review.opendev.org/c/openstack/nova/+/984481
00:38:55 melwitt sean-k-mooney, gibi: I had read through the review comments on some database fixture patches yall have been working on and tried a couple of changes to try and help out ^ they may not be useful given my limited knowledge on the eventlet removal work
00:40:38 melwitt I have them rebased on Ashish's change https://review.opendev.org/c/openstack/nova/+/979850. the second patch complains of merge conflict for some reason though
01:02:48 opendevreview melanie witt proposed openstack/nova master: Database: use file-backed SQLite for native threading https://review.opendev.org/c/openstack/nova/+/984481
01:15:45 opendevreview melanie witt proposed openstack/nova master: Database: use file-backed SQLite for native threading https://review.opendev.org/c/openstack/nova/+/984481
06:20:42 opendevreview Merged openstack/nova master: mem-enc: stop using _get_mem_encryption_config() for SEV checks https://review.opendev.org/c/openstack/nova/+/967970
07:14:59 gibi melwitt: thanks for that. I wil check it out
07:38:07 opendevreview Kamil Sambor proposed openstack/nova master: Enable threading mode for proxy services https://review.opendev.org/c/openstack/nova/+/976089
07:42:05 opendevreview Kamil Sambor proposed openstack/nova master: Enable threading mode for proxy services https://review.opendev.org/c/openstack/nova/+/976089
08:21:43 gibi bauzas: stephenfin: can one of you push this CI timeout bump through https://review.opendev.org/c/openstack/nova/+/984417
08:45:03 opendevreview Konrad Gube proposed openstack/nova-specs master: Propose assisted-volume-extend API https://review.opendev.org/c/openstack/nova-specs/+/949504
09:25:37 opendevreview Kamil Sambor proposed openstack/nova master: Change nova-alt-configurations job https://review.opendev.org/c/openstack/nova/+/983179
09:31:09 opendevreview ribaudr proposed openstack/nova master: Add reproducer for bug #2141722 https://review.opendev.org/c/openstack/nova/+/984521
09:31:10 opendevreview ribaudr proposed openstack/nova master: Fix os-simple-tenant-usage pagination with duplicate instance_extra https://review.opendev.org/c/openstack/nova/+/984522
10:10:06 Uggla sean-k-mooney, I have opened https://blueprints.launchpad.net/nova/+spec/adopt-port-trusted-vif-extension and add a comment in the bug to it. Please tell me if ok.
10:33:01 opendevreview Merged openstack/nova master: [openstack-tox-cover]Increase timeout further https://review.opendev.org/c/openstack/nova/+/984417
10:44:42 opendevreview sean mooney proposed openstack/nova master: add agentic coding scaffold and contributor docs https://review.opendev.org/c/openstack/nova/+/984540
12:46:22 opendevreview Kamil Sambor proposed openstack/nova master: Enable threading mode for proxy services https://review.opendev.org/c/openstack/nova/+/976089
13:08:41 opendevreview Merged openstack/nova master: mem-enc: refactor memory encryption trait logic for extensibility https://review.opendev.org/c/openstack/nova/+/967971
13:58:52 opendevreview Balazs Gibizer proposed openstack/nova master: Speed up RetryDecorator in unit test https://review.opendev.org/c/openstack/nova/+/975443
13:58:52 opendevreview Balazs Gibizer proposed openstack/nova master: [py313-threading]Reenable last scatter-gather unit test https://review.opendev.org/c/openstack/nova/+/984349
13:59:28 opendevreview Balazs Gibizer proposed openstack/nova master: Speed up RetryDecorator in unit test https://review.opendev.org/c/openstack/nova/+/975443
13:59:28 opendevreview Balazs Gibizer proposed openstack/nova master: [py313-threading]Reenable last scatter-gather unit test https://review.opendev.org/c/openstack/nova/+/984349
14:21:51 artem_vasilyev Hi, could you please take a look at a Nova bug I’ve been investigating: https://bugs.launchpad.net/nova/+bug/2147776 (with reproducer tests https://review.opendev.org/c/openstack/nova/+/984007) and the proposed fix https://review.opendev.org/c/openstack/nova/+/984048 - it addresses a race between resize and update_available_resources affecting dedicated CPU accounting
15:05:58 Uggla gibi, regarding you eventlet topic. Would you prefer to have it after the "global" eventlet session (tue) ?
15:06:38 Uggla or it doesn't matter.
15:29:11 Uggla TheJulia, dansmith Thu 1500-1600UTC : Attestation integration Plugin (1h) does it work for you ?
15:31:13 lajoskatona Uggla: Hi, there is perhaps a beehive like topic (sorry for that) to use SDK for neutron to nova notifications (os-server-external-events API call ), see my patch in SDK:
15:32:25 lajoskatona Uggla: https://review.opendev.org/c/openstack/openstacksdk/+/983904 (and in Neutron to use the SDK patch: https://review.opendev.org/c/openstack/neutron/+/983905 ) we discussed today's Neutron meeting that perhaps this is a topic to chat during the PTG
15:35:17 melwitt bauzas: hi, there are a few small vtpm related patches that would appreciate your review if you get a chance please https://review.opendev.org/c/openstack/nova/+/978836 https://review.opendev.org/c/openstack/nova/+/983504 https://review.opendev.org/c/openstack/nova/+/983505
15:36:24 Uggla lajoskatona, please add the topic at the end of the PTG doc, if not already done.
15:37:05 bauzas melwitt: ack
15:37:13 Uggla lajoskatona, then I will check if that will be an "individual" topic or something in a X session. (Note the X session with Neutron is not yet defined).
15:44:06 Uggla dansmith Get on the same page about unpinning availability zone --> how much time do you need ? 1h ? 30 mn ?
15:56:01 croelandt bauzas: hey! I just came across https://github.com/sbauza/openstack-agentic-workflows , which at the moment seems mostly used for Nova. In its current form, /code-review can only be used for Nova, if I'm not mistaken. Would you be open to having a /openstack-code-review skill that dispatches the review of a given patch to project-specific agents?
15:56:36 TheJulia Uggla: that window works for me
15:57:06 bauzas croelandt: this is more a demonstrating POC at the moment for the Nova repository indeed, but other projects could add their own knowledge files for each of them
15:59:06 lajoskatona Uggla: thanks, I added it
15:59:26 croelandt bauzas: yeah but if I define workflows/glance-review/.claude/skills/code-review/SKILL.md , then /code-review will be defined twice, right?
16:00:56 bauzas good call, I could change the skill name to be nova-specific
16:01:26 croelandt yeah so at first you'd have nova-review and we'd have glance-review
16:01:36 croelandt wanna do it or want me to send a PR tonight? :)
16:01:56 bauzas croelandt: I already have some LLM session somewhere so I can fix that quickly :)
16:02:04 croelandt I could get CLaude to do it and try to understand the code better while I'm at it
16:02:22 croelandt bauzas: you say it's more of a POC but are you open to merging stuff for other projects?
16:02:27 bauzas croelandt: yeah all the PRs were generated by LLMs and only curated by me
16:02:40 croelandt ok so I'll try and send PRs :p
16:02:53 croelandt well I'll try not to write a single line and let Claude do it
16:03:15 bauzas croelandt: I'd prefer to have the knowledge files to be on the upstream repos, but for skills, it could be on other repos
16:03:48 croelandt hm not sure I get it
16:03:59 croelandt you want to move knowledge/nova.md somewhere else?

Earlier   Later