Earlier  
Posted Nick Remark
#openstack-nova - 2021-12-17
16:14:14 sean-k-mooney gibi_pto_back_on_10th: im currently updating the health check spec and incoperating some design element form https://inadarei.github.io/rfc-healthcheck/#RFC8259
16:14:29 sean-k-mooney gibi_pto_back_on_10th: but no rush to review it
16:14:43 sean-k-mooney ill push it before i leave today but it can wait until we are all back
16:23:10 gibi_pto_back_on_10th sean-k-mooney: OK, I will take a look at some point :)
16:29:28 bauzas gibi: happy new year !
16:29:36 gibi_pto_back_on_10th bauzas: same to you too
16:30:01 bauzas have good holidays :)
16:33:04 gmann gibi_pto_back_on_10th: happy holiday and take rest
16:34:42 gmann bauzas: good to have your ack in this (placement IRC channel retiring ) https://review.opendev.org/c/openstack/project-config/+/821889
16:35:03 bauzas gmann: sure
16:35:10 gmann thanks
16:35:29 gibi_pto_back_on_10th gmann: same to you
17:40:41 opendevreview sean mooney proposed openstack/nova-specs master: add per process healthcheck spec https://review.opendev.org/c/openstack/nova-specs/+/821279
17:41:44 sean-k-mooney gibi_pto_back_on_10th: bauzas ^ that is proably going to be the last thing i do until the new year. ill respin the external cpu managment spec when i retrun form PTO. enjoy your time off o/
17:42:06 gibi_pto_back_on_10th sean-k-mooney: enjoy o/
20:06:25 opendevreview Jonathan Race proposed openstack/nova master: Adds Emulation for aarch64, and ppc64 on x86_64 processors https://review.opendev.org/c/openstack/nova/+/822053
#openstack-nova - 2021-12-19
12:37:45 opendevreview Federico Ressi proposed openstack/nova master: Debug Nova APIs call failures https://review.opendev.org/c/openstack/nova/+/806683
18:33:16 opendevreview Ghanshyam proposed openstack/nova master: Convert SYSTEM_ADMIN|READER to Admin and system scope https://review.opendev.org/c/openstack/nova/+/819390
#openstack-nova - 2021-12-20
02:13:06 Jorhson sean-k-mooney:do you help to review the patch 761264?
08:44:43 bauzas good morning Nova
12:51:06 arne_wiebalck Hi! In one of the conductor groups in our Nova/Ironic cell, some compute nodes have been soft-deleted (for not yet understood reasons). While hard-deleting from the compute_nodes table lets Nova re-insert it, it seems the allocations are not fixed by this. The result is that placement is advertising physical nodes which are active ... is there a straight-forward/automatic way to correct this? (This is on Nova Stein :)
13:26:24 opendevreview Jorhson Deng proposed openstack/nova master: process instance in soft-deleting task state during _init_instance https://review.opendev.org/c/openstack/nova/+/761264
13:35:24 opendevreview Jorhson Deng proposed openstack/nova master: process instance in soft-deleting task state during _init_instance https://review.opendev.org/c/openstack/nova/+/761264
13:57:14 opendevreview Jonathan Race proposed openstack/nova master: Adds Emulation for aarch64, and ppc64 on x86_64 processors https://review.opendev.org/c/openstack/nova/+/822053
14:10:01 bauzas arne_wiebalck: hola, sorry wasn't looking at the IRC chan given it was quiet :)
14:10:32 bauzas arne_wiebalck: so you mean you have persisted allocations for some not longer compute services, right?
14:10:40 arne_wiebalck bauzas: heh, yeah, wasn't sure if anyone is still around :)
14:10:51 bauzas until tonight :)
14:11:50 arne_wiebalck bauzas: so, the compute are marked as deleted, but placement offers them, which makes me think the allocations have been deleted with the nodes ... but did not come back when the nodes were re-inserted
14:12:43 arne_wiebalck bauzas: we had this in the past, and Belmiro did some magic, but he is not available at the moment
14:13:22 arne_wiebalck bauzas: I will not risk too much either, just in case there is some sync I need to kick off, I may try it
14:13:58 arne_wiebalck bauzas: my main worry is that placement offers physical nodes which are installed :-S
14:14:31 arne_wiebalck bauzas: Ironic stops the installation, but free nodes cannot be installed either (since placement offers all nodes)
14:15:20 arne_wiebalck bauzas: I wasn't sure either if it is safe to remove active nodes from the placement aggregrate (or even deleted the resource providers)
14:15:40 arne_wiebalck bauzas: I have done this with available nodes, but not with active ones
14:15:58 bauzas arne_wiebalck: tbc, do you have resource providers for the deleted compute services ?
14:16:23 arne_wiebalck bauzas: I must have otherwise placement would not offer them, no?
14:16:41 arne_wiebalck bauzas: but let me check for one ...
14:16:42 bauzas arne_wiebalck: sorry I still don't understand
14:16:56 arne_wiebalck bauzas: it is probable since I do not use the correct terms
14:17:13 bauzas arne_wiebalck: so, which Resource Providers do you have ?
14:17:23 bauzas arne_wiebalck: is the usage for every RP good or not ?
14:17:40 bauzas arne_wiebalck: and do you have "orphaned" allocations ?
14:18:11 bauzas an orphaned allocation is an allocation telling it's about some RP UUID but with the RP no longer here
14:18:24 bauzas RP : Resource Provider
14:19:17 arne_wiebalck bauzas: I have resource providers which placement offers me as allocation candidates, but the nodes are actually active in Ironic, so there is an instance on them
14:19:59 bauzas arne_wiebalck: I see so you no longer have allocations for this RP
14:20:23 arne_wiebalck bauzas: right, this is what I think
14:20:23 bauzas they were deleted when the compute service was deleted
14:20:33 arne_wiebalck bauzas: right, this is my understanding
14:21:16 arne_wiebalck bauzas: and I was thinking the resource tracker would update this, but it does not
14:21:25 opendevreview Jorhson Deng proposed openstack/nova master: recheck the attachment_id after the reschedule successful https://review.opendev.org/c/openstack/nova/+/796209
14:21:39 bauzas arne_wiebalck: just verifying, could you please ask : "openstack resource provider usage show " ? https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-usage-show
14:22:17 bauzas if so, we have a nova-manage command helping for you
14:22:24 arne_wiebalck usage 0
14:22:53 bauzas \o/
14:22:54 arne_wiebalck https://paste.opendev.org/show/811772/
14:23:01 bauzas okay, so please https://docs.openstack.org/nova/rocky/cli/nova-manage.html#placement
14:23:04 bauzas shit
14:23:12 bauzas nevermind, same for stein
14:23:21 bauzas nova-manage placement heal_allocations [--max-count <max_count>] [--verbose] [--dry-run] [--instance <instance_uuid>]
14:23:33 bauzas this should heal your allocations
14:23:40 bauzas verify it with --dry-run firstr
14:24:10 arne_wiebalck uh, that looks like what I was looking for, let me try it :)
14:24:23 arne_wiebalck what can go wrong one day before the break :)
14:24:49 bauzas https://docs.openstack.org/nova/latest/cli/nova-manage.html#placement-heal-allocations
14:25:10 bauzas arne_wiebalck: that's why you should test it first :D
14:29:16 arne_wiebalck bauzas: give me a sec, I need to find a good node ...
14:29:23 bauzas sure
14:36:13 arne_wiebalck bauzas: hmm, seems that our client neither has --dry-run, nor --instance ... at least the one I found so far
14:37:14 bauzas looks like it was added in Train
14:37:35 bauzas so maybe we added it in a backport that you don't have in your client
14:37:50 arne_wiebalck yeah, totally possible
14:37:51 bauzas the master doc is explaning it
14:38:05 bauzas but I can doublecheck the stable/stein branch
14:38:15 arne_wiebalck thanks, will do!
14:38:48 bauzas YUUUP https://github.com/openstack/nova/commits/stable/stein/nova/cmd/manage.py
14:39:45 arne_wiebalck ok, let me confirm on our side ...
14:39:57 bauzas https://review.opendev.org/c/openstack/nova/+/693199
14:40:03 bauzas Branches: stable/stein Tags: 19.1.0 19.2.0 19.3.0 19.3.1 19.3.2 stein-em
14:40:27 bauzas 19.0.0 doesn't have it
14:41:05 arne_wiebalck seems like ours is based on 19.0.1
14:41:11 arne_wiebalck yeah, that fits
14:42:40 arne_wiebalck without these two options I will rather wait until Belmiro is back :)
14:42:57 arne_wiebalck sounds too risky to run it across the whole deployment
14:44:31 arne_wiebalck is that a sychronous command, i.e. would it block on the CLI ?
14:45:00 arne_wiebalck (or does it launch healing on the background?)
14:51:00 bauzas arne_wiebalck: agreed on holding until belmiro is back
14:51:18 bauzas arne_wiebalck: yes, it's synchronous, it won't fork threads
14:51:36 arne_wiebalck bauzas: thanks a lot for your help!
15:29:38 gmann bauzas: before you start you leave, can you please check these Yoga py3.6 testing updates https://review.opendev.org/c/openstack/nova/+/821636 https://review.opendev.org/c/openstack/os-traits/+/819205 https://review.opendev.org/c/openstack/placement/+/819206
15:46:01 opendevreview Ilya Popov proposed openstack/nova master: Fix to implement 'pack' or 'spread' VM's NUMA cells https://review.opendev.org/c/openstack/nova/+/805649
15:48:21 bauzas gmann: ack
15:50:57 bauzas gmann: I just gave you a Christmas present for those 3 :)
15:51:52 gmann bauzas: thanks :), happy Christmas in advance and enjoy your vacation.
15:52:04 bauzas gmann: sure, will be on the ski slopes :)
15:52:17 gmann :)
16:12:56 opendevreview Ghanshyam proposed openstack/nova stable/train: DNM: test tempest train-last tag https://review.opendev.org/c/openstack/nova/+/816598
17:01:45 bauzas folks, calling it a year. Have good times and hopefully, 2022 will be a better year.
17:29:58 gmann o/

Earlier   Later