Earlier  
Posted Nick Remark
#openstack-nova - 2025-11-06
13:46:29 sean-k-mooney for 4k
13:47:13 sean-k-mooney so if your doing anythign related to numa you are not allowed to oversibcsribe memory
13:47:52 jkulik ok. then for NUMA `max_unit` would be wrong :D but nevermind
13:48:00 sean-k-mooney and you use `reserved_huge_pages = node:0,size:4,count=256`
13:48:47 sean-k-mooney well yes but if we implent numa in placment we can define the sematic of the livbirt driver to limit it
13:49:04 sean-k-mooney since we know that numa memory will always have an allcoaiton ration of 1.0
13:49:18 sean-k-mooney the max_unit shoudl never exceed (total-reserved) in that case
13:49:36 jkulik yes. but that's not there, yet, right?
13:49:53 sean-k-mooney correct but we track numa memory diffently in nova already
13:49:59 sean-k-mooney and do the enfocement diffently
13:50:11 sean-k-mooney so placement will say this host might be valid
13:50:22 sean-k-mooney and hten numa toploty filter will then do the enforcement
13:51:09 jkulik ... and fail and then we go into retries for spawning in conductor, in case that's configured?
13:51:30 sean-k-mooney because numa requireds an allocation ratio of exactly 1 it drops out of the equation and max unit is just total-reserved
13:51:38 jkulik ah. no. it's an actual scheduler filter
13:51:52 sean-k-mooney right its a scheduler filter
13:52:15 sean-k-mooney we do the check again on the compute in case 2 diffent api request race for the last resouce on a given host
13:52:44 sean-k-mooney but for the most part that wont hapen in a reasonable size cloud or if you say use a weigher to spread based on ram usage
13:53:53 jkulik hm ... we have bad experience with spreading ... then parts of too many hosts are used, which disallows full-host-sized VMs :/
13:54:08 jkulik thank you again.
13:54:23 sean-k-mooney :) well you can also opt to pack for that use case
13:54:28 sean-k-mooney but ya its a trade off
13:54:37 sean-k-mooney and no worries this is one of hte more complex parts of nova
14:30:33 stephenfin gmaan: Not necessarily for today, but what are the chances of getting the remainder of the OpenAPI series reviewed in the next few weeks? Happy to trade reviews
14:30:51 opendevreview Takashi Kajinami proposed openstack/placement master: Make sure [cors] allowed_origin accepts a list value https://review.opendev.org/c/openstack/placement/+/966275
14:32:06 stephenfin sean-k-mooney: ditto for you: gmaan has hit the bottom 9 patches of the 28 (sorry /o\) outstanding
14:40:45 opendevreview Takashi Kajinami proposed openstack/nova master: Use common utility to parse Host header https://review.opendev.org/c/openstack/nova/+/966280
15:19:04 opendevreview Max proposed openstack/nova master: fix: return cross_az_attach errors directly https://review.opendev.org/c/openstack/nova/+/966284
16:19:22 sean-k-mooney stephenfin: so apprenly https://review.opendev.org/c/openstack/devstack/+/966239 is the short term fix
16:19:45 sean-k-mooney but i also think this is likely incorrect
16:20:01 sean-k-mooney becasue 2025.1 shoudl still be using tempest master not a pin
17:01:20 gmaan stephenfin: sure, not this week but I can see if I can start it again during end of next week. but it is still in my list to continue in this cycle.
17:02:08 gmaan sean-k-mooney: we should be using the master on 2025.1 but let me check chat in qa channel and see what is issue
17:02:40 stephenfin sean-k-mooney: I see there's a run-tempest-26 role in the tempest repo. I would imagine we probably want something similar if there are Python issues, but that's one for gmaan et al
17:02:48 stephenfin *new Python version issues
17:21:40 sean-k-mooney oh i ment to respoend in the ohter channle on the tempst thing lets keep that converstaion in openstack-qa my bad
17:21:52 gmaan ++
17:44:15 opendevreview Merged openstack/nova master: [CI]nova-alt-configurations tests eventlet https://review.opendev.org/c/openstack/nova/+/965922
18:50:37 opendevreview Balazs Gibizer proposed openstack/nova master: Default native threading for sch, api and metadata https://review.opendev.org/c/openstack/nova/+/965924
18:52:12 gibi sean-k-mooney: ^^ renamed the parameter as requested
18:55:41 sean-k-mooney gibi: +2 on both
19:01:07 gibi sean-k-mooney: thanks!
19:01:27 gibi dansmith: when you have time we are ready to close one item off the my eventlet list ^^ :)
19:02:35 dansmith gibi: yeah I was going to do that this morning until I saw the request..I'll circle back in a bit
19:02:41 gibi thanks
23:48:37 opendevreview Merged openstack/nova master: Move monkey_patch from init to the entrypoints https://review.opendev.org/c/openstack/nova/+/965923
#openstack-nova - 2025-11-07
05:59:29 koya Hi Uggla, bauzas, thank you very much for discussing “Instance metadata protection” at the recent OpenInfra Summit.
05:59:58 koya Based on the comments you kindly provided, I’ve been reviewing and updating (revising) the blueprint; https://blueprints.launchpad.net/nova/+spec/instance-metadata-protection. I’ll reach out to you again when it’s ready.
10:38:19 artem_vasilyev Hi, I stumbled upon the _cleanup_incomplete_migrations function and can't quite get whether this is intended logic or not. I couldn't find answers in the documentation. As I understand, the purpose of this function is to clean orphan files of already deleted instances. But when deleting instances, their migrations are also marked as soft-deleted (see https://github.com/openstack/nova/blob/master/nova/db/main/api.py#L1348). So this function
10:38:23 opendevreview Adrien Cunin proposed openstack/os-vif master: Fixed bridge name when per_port_bridge is used https://review.opendev.org/c/openstack/os-vif/+/966410
10:39:35 jkulik artem_vasilyev: fyi, your message is cut off after ". So this function"
10:40:28 artem_vasilyev thanks. So this function can't get error migrations, because it doesn't query migrations with read_deleted context. Is this the expected behavior, or am I missing something?
10:43:46 artem_vasilyev _cleanup_incomplete_migrations function is here: https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L11944
10:50:50 jkulik the tests mock away MigrationList.get_by_filters(), so they can't see it. from looking at the code, I'd agree with you artem_vasilyev
12:33:17 opendevreview Balazs Gibizer proposed openstack/nova master: Run nova-compute in native threading mode https://review.opendev.org/c/openstack/nova/+/965467
12:33:18 opendevreview Balazs Gibizer proposed openstack/nova master: Do not use libvirt before Host is initialized https://review.opendev.org/c/openstack/nova/+/966430
12:52:35 opendevreview Merged openstack/nova master: Default native threading for sch, api and metadata https://review.opendev.org/c/openstack/nova/+/965924
13:34:21 gibi dansmith: this might be interesting to you https://bugs.launchpad.net/nova/+bug/2130881
13:34:46 gibi dansmith: I'm fairly certain that we break libvirt lifecycle event handling with the patch https://review.opendev.org/c/openstack/nova/+/897076 - Sanity check that new hosts have no instances
13:35:06 gibi but only for the first nova-compute startup case. Later nova-compute restarts are not affected
13:36:18 gibi we need to reorder ComputeManager.init_host a bit to call driver.init_host before doing any libvirt driver queries
13:44:23 gibi I will push a fix
13:48:38 opendevreview Balazs Gibizer proposed openstack/nova master: DNM: Show libvirt lifecycle event issue https://review.opendev.org/c/openstack/nova/+/966436
13:48:55 gibi this should show the problem clearly ^^
14:41:32 opendevreview Balazs Gibizer proposed openstack/nova master: Reproduce bug/2130881 https://review.opendev.org/c/openstack/nova/+/966443
14:54:11 opendevreview Balazs Gibizer proposed openstack/nova master: Init virt driver before use https://review.opendev.org/c/openstack/nova/+/966446
15:07:07 opendevreview Balazs Gibizer proposed openstack/nova master: Make RBD Tpool usage conditional https://review.opendev.org/c/openstack/nova/+/956089
15:07:08 opendevreview Balazs Gibizer proposed openstack/nova master: Make guestfs' Tpool usage optional https://review.opendev.org/c/openstack/nova/+/965821
15:07:08 opendevreview Balazs Gibizer proposed openstack/nova master: Make libvirt Tpool proxying conditional https://review.opendev.org/c/openstack/nova/+/956090
15:07:09 opendevreview Balazs Gibizer proposed openstack/nova master: [test]Further categorization of disabled unit tests https://review.opendev.org/c/openstack/nova/+/956092
15:07:09 opendevreview Balazs Gibizer proposed openstack/nova master: Fix ProviderTree copying with threading Lock https://review.opendev.org/c/openstack/nova/+/956091
15:07:10 opendevreview Balazs Gibizer proposed openstack/nova master: Compute manager to use native thread pools https://review.opendev.org/c/openstack/nova/+/966016
15:07:10 opendevreview Balazs Gibizer proposed openstack/nova master: Do not fork compute workers in native threading mode https://review.opendev.org/c/openstack/nova/+/965466
15:07:11 opendevreview Balazs Gibizer proposed openstack/nova master: Run nova-compute in native threading mode https://review.opendev.org/c/openstack/nova/+/965467
15:07:11 opendevreview Balazs Gibizer proposed openstack/nova master: Libvirt event handling without eventlet https://review.opendev.org/c/openstack/nova/+/965949
15:14:08 dansmith gibi: oof
15:20:51 opendevreview Dan Smith proposed openstack/nova master: DNM: Test with >1 parallel migrations https://review.opendev.org/c/openstack/nova/+/966447
15:20:51 opendevreview Dan Smith proposed openstack/nova master: Allow to perform parallel live migrations https://review.opendev.org/c/openstack/nova/+/955784
15:20:57 dansmith noonedeadpunk: ^
15:46:05 dansmith Uggla: (cc gibi) I thought we agreed to do specless blueprint for the parallel live migration during the PTG and we've had a meeting since then.. did we need to do some other step to actually approve the LP blueprint?
15:46:18 dansmith ...in the meeting this week?
15:46:50 noonedeadpunk I probably should abandon the spec as well
15:46:59 dansmith yep
15:47:08 dansmith leave it linked in the LP blueprint though so we have an easy reference for it
15:50:32 Uggla Hi dansmith, no it is ok. I'll approve the BP if it is not.
15:50:48 dansmith Uggla: okay I thought we were good to go.. yeah if you could approve I'd appreciate it
15:57:08 gibi ohh cool, then I can upgrade my vote
16:00:23 opendevreview sean mooney proposed openstack/nova-specs master: Add ResourceProviderWeigher scheduler spec https://review.opendev.org/c/openstack/nova-specs/+/951222
16:13:39 razoff Is it possible in any way to access dirty blocks of volume mounted on an instance through openstack API ?
16:13:39 razoff I've been struggling to run efficient incremental backups.
16:13:39 razoff At my company I developed a backup solution (through a proxy instance) for openstack instances and I have one question for you.
16:13:39 razoff Hi there !
16:13:40 razoff I am asking this on the Nova channel because I noticed that you are using libvirt for virtualization and I know that it is possible to get dirty blocks from that lib.
16:13:43 razoff Thank you in advance !
16:20:21 dansmith Uggla: can you do the needful? https://blueprints.launchpad.net/nova/+spec/libvirt-parallel-migrate
16:26:09 Uggla dansmith, I think that's ok
16:28:28 dansmith Uggla: oh, did you change it to approved? I was looking at "approver" and it is still empty so maybe I missed that it flipped state, thanks
16:28:55 dansmith ah I see the comment in the whiteboard too.. I'm not subscribed so I didn't get the detailed notification
16:30:46 Uggla dansmith, should be fully completed, I have added also that this is a specless BP.
16:31:20 dansmith thanks

Earlier   Later