Earlier  
Posted Nick Remark
#openstack-nova - 2021-07-13
17:22:24 dansmith I was having a hard time seeing the value, and clearly lyarwood was as well
17:22:41 dansmith it's definitely a workaround, but doesn't really fit what the workarounds conf section was supposed to be
17:23:05 sean-k-mooney dansmith: so am i in that apprcoh but as a workaround option we could remvoe it in a sort period of time
17:23:13 dansmith I think I'd rather see it done as a generally-useful thing to avoid landing the workaround and then never closing on it
17:23:23 sean-k-mooney dansmith: i think we have a similar workaroud alredy
17:23:26 alistarle Actually it is not really an issue for me to see it in Yoga if it need more work, my only concern is if I need to wait 6 month to work on it
17:23:29 sean-k-mooney for live snapshots
17:23:46 dansmith alistarle: you can work on it now, just don't expect to merge before Y opens
17:23:47 sean-k-mooney https://docs.openstack.org/nova/latest/configuration/config.html#workarounds.disable_libvirt_livesnapshot
17:24:21 alistarle Oh I see, there is a dedicated workaround section
17:24:37 alistarle But does the workaround section follow the same deprecation cycle than others ?
17:24:39 sean-k-mooney alistarle: on no you would not need to wait 6 months
17:24:42 lyarwood I'd be happy with another workaround to disable_live_directsnapshot with this replacement approach being worked on in Y
17:25:10 sean-k-mooney we have actully just created the yoga spec folder
17:25:54 sean-k-mooney so you could actully submit a spec to that folder for next cycle which we coudl review, and then you could work on the implemation to merge in early y
17:26:27 sean-k-mooney althoguh we normally dont approve specs for the next release until later in the cycle
17:26:59 sean-k-mooney alistarle: yes workaround follow the same dperecation cycle
17:27:18 sean-k-mooney alistarle: although we have in the passed intoduced workarounds as deprecated imidetly
17:27:26 dansmith if alistarle is fine with Y, then why not do it just once, in Y?
17:29:09 alistarle Actually I don't really care about when it will be officially released, as I can backport my commit easily, I just hope we can freeze the implementation as soon as possible, so I will not backport a different commit in the future
17:29:11 lyarwood If there's no pressing need in some env then yeah
17:29:32 sean-k-mooney alistarle: you mean backprot downstream/out of tree
17:29:41 alistarle Yeah exactly
17:30:06 sean-k-mooney ok just makeing sure since as a blueprit or spec it would not qualify to backport upstream
17:30:40 sean-k-mooney then can i suggest you submit a spec agaisnt the yoga specs directory and we can review it with Y in mind
17:31:09 alistarle Ok fine, let's go for Y then, and dive the "glance store" option in nova_compute config then
17:31:32 sean-k-mooney +1
17:35:40 opendevreview Lee Yarwood proposed openstack/nova master: WIP/DNM nova-manage: Introduce bdm show and refresh commands https://review.opendev.org/c/openstack/nova/+/800634
17:36:30 lyarwood stephenfin: ^ dumped some example output, need to help with bedtime then I'll try to clean the spec up this evening before I drop
18:01:00 opendevreview Merged openstack/nova master: Make test_archive_task_logs deterministic https://review.opendev.org/c/openstack/nova/+/800313
18:16:22 stephenfin melwitt: Could you also look at https://review.opendev.org/c/openstack/nova/+/794007/4 ? lyarwood is happy with it now
18:18:13 melwitt stephenfin: ah, cool, I had been waiting for his ack. will do
18:25:32 opendevreview Lee Yarwood proposed openstack/nova master: WIP/DNM libvirt: register device bus and model image properties https://review.opendev.org/c/openstack/nova/+/800708
18:34:55 lyarwood right, I'm out of here, catch you all in ~2 weeks hopefully! \o
19:55:17 sean-k-mooney melwitt: am regarding https://review.opendev.org/c/openstack/nova-specs/+/800570 i thikn it would be better if we made all the time spans relitive ages insted of date ranges
19:55:34 sean-k-mooney but other then that i still like the idea of this
20:14:25 opendevreview Merged openstack/nova-specs master: Repropose: Support Consumer Types in placement https://review.opendev.org/c/openstack/nova-specs/+/800569
22:16:21 NobodyCam Good Afternoon Nova Folks
22:19:00 NobodyCam looking for a little guidance on deleting an instance. I have a instance that is stuck in building. it shows up with openstack server list. But we get "No server with a name or ID" when attempting to run a server show.. would anyone be able to point me in the right direction to remove this
23:55:58 melwitt stephenfin: sorry, still have one question from PS12 and a new question on PS14 https://review.opendev.org/c/openstack/nova/+/706295
#openstack-nova - 2021-07-14
01:37:08 opendevreview Merged openstack/nova master: docs: Replace 'nova boot' with 'openstack server create' https://review.opendev.org/c/openstack/nova/+/794007
06:07:15 opendevreview Takashi Kajinami proposed openstack/nova master: Clean up allocations left by evacuation when deleting service https://review.opendev.org/c/openstack/nova/+/778696
06:19:49 opendevreview Takashi Kajinami proposed openstack/nova master: Clean up allocations left by evacuation when deleting service https://review.opendev.org/c/openstack/nova/+/778696
08:12:16 opendevreview Yongli He proposed openstack/nova master: Smartnic support - cyborg drive https://review.opendev.org/c/openstack/nova/+/771362
08:12:17 opendevreview Yongli He proposed openstack/nova master: smartnic support - new vnic type https://review.opendev.org/c/openstack/nova/+/771363
08:12:19 opendevreview Yongli He proposed openstack/nova master: smartnic support - build instance with smartnic arqs https://review.opendev.org/c/openstack/nova/+/798249
08:12:19 opendevreview Yongli He proposed openstack/nova master: smartnic support - create arqs https://review.opendev.org/c/openstack/nova/+/758944
08:12:20 opendevreview Yongli He proposed openstack/nova master: smartnic support - cleanup arqs https://review.opendev.org/c/openstack/nova/+/798054
08:12:21 opendevreview Yongli He proposed openstack/nova master: smartnic support - reject server move and suspend https://review.opendev.org/c/openstack/nova/+/779913
08:12:23 opendevreview Yongli He proposed openstack/nova master: smartnic support - functional tests https://review.opendev.org/c/openstack/nova/+/780147
08:42:36 gibi stephenfin: can we get this in https://review.opendev.org/c/openstack/os-resource-classes/+/796591 I'd like to get a os-release-classes lib released as neutron also needs this
09:34:21 opendevreview Merged openstack/os-resource-classes master: Add packet rate related resource classes https://review.opendev.org/c/openstack/os-resource-classes/+/796591
10:21:26 opendevreview Stephen Finucane proposed openstack/nova master: Use neutronclient's port binding APIs https://review.opendev.org/c/openstack/nova/+/706295
10:21:27 opendevreview Stephen Finucane proposed openstack/nova master: fixtures: Raise HTTP 409 if binding is already active https://review.opendev.org/c/openstack/nova/+/800767
10:21:49 stephenfin gibi: Respun that again (hopefully the last time) if you care to take a look ^
10:23:16 gibi on it
10:23:21 stephenfin ta
10:26:25 gibi done
10:26:37 gibi thanks for fixig the todo I left in the fixture
10:28:14 opendevreview Takashi Kajinami proposed openstack/nova master: Clean up allocations left by evacuation when deleting service https://review.opendev.org/c/openstack/nova/+/778696
10:33:43 opendevreview Takashi Kajinami proposed openstack/nova master: Clean up allocations left by evacuation when deleting service https://review.opendev.org/c/openstack/nova/+/778696
10:36:08 opendevreview Takashi Kajinami proposed openstack/nova master: Clean up allocations left by evacuation when deleting service https://review.opendev.org/c/openstack/nova/+/778696
10:47:14 opendevreview Balazs Gibizer proposed openstack/placement master: Move placement specs from nova https://review.opendev.org/c/openstack/placement/+/800769
11:32:02 sean-k-mooney stephenfin: if the recheck fails on https://review.opendev.org/c/openstack/os-vif/+/798055 ill adress the remaining typos
11:32:46 sean-k-mooney otherwise ill fix them in a followup when i start working on the trunk bridge deletion bug.
12:04:14 opendevreview Balazs Gibizer proposed openstack/nova-specs master: Move placement specs to placement repo https://review.opendev.org/c/openstack/nova-specs/+/800775
12:05:45 gibi melwitt: I think the best is to move the placement targeting specs to the placement repository. So I proposed a nova-specs and a placement patch to do so
12:05:48 gibi melwitt: https://review.opendev.org/c/openstack/nova-specs/+/800775
12:05:55 gibi melwitt: https://review.opendev.org/c/openstack/placement/+/800769
12:09:33 sean-k-mooney was that motivated by my comment on melwitt's consumer types path
12:09:36 sean-k-mooney *patch
12:11:55 gibi sean-k-mooney: I already detected my mistake when we merged my re-parent RP spec
12:12:03 gibi sean-k-mooney: just haven't had the time to do the move since
12:46:04 gibi \
13:03:20 opendevreview Stephen Finucane proposed openstack/nova master: db: Final cleanups https://review.opendev.org/c/openstack/nova/+/800484
14:45:16 gibi sean-k-mooney: I looked through the cyborg smartnic impl. I do miss the part when the smartnic arq triggers a piece of domain xml generated to pass through a VF. The flavor based arqs are handled via the arq uuids passed to the libvirt driver but the smartnic impl does not pass the smartnic arqs this way. Does this xml generation happens becuase of the port has some pci info in the bindig profile?
14:48:19 gibi the last bullet in the spec https://specs.openstack.org/openstack/nova-specs/specs/xena/approved/support-sriov-smartnic.html#nova seems to confirm my above guess
15:26:17 melwitt gibi: ack will review them, thanks for doing that
15:32:11 gibi melwitt: thanks
15:46:09 mnaser hmm, i ran into an interesting scenario. i have 2 az in a cloud with cross_az_attach=False, everything works as expected, but for bfv, since a volume type is only available in a specific az, volumes go to 'error' right away
15:47:08 mnaser would this be a 'cinder' bug technically because nova is requesting a volume with no type included but az=<foobar> and it's going to the default that is not available in az=<foobar> ?
15:48:33 mnaser yeah, i think that's more of a cinder thing now that i'm writing it out.. i'll take it there if anyone is curious
15:56:12 opendevreview Balazs Gibizer proposed openstack/placement master: Add support for RP re-parenting and orphaning https://review.opendev.org/c/openstack/placement/+/784020
15:56:24 gibi sean-k-mooney: I fixed nits and replied to your comment in ^^
15:56:55 NobodyCam morning Nova Folks.. I have a instance that is stuck in build state. it shows up with openstack server list. But I get "No server with a name or ID" when attempting to run a openstack server show.. would anyone be able to point me in the right direction to remove this failed instance
15:59:58 melwitt NobodyCam: you might have an orphaned build_requests record for the instance. if you have one of those records and no instance_mappings record for the instance, you will need to delete the build_requests record from the database manually
16:00:16 melwitt these tables are both in the nova_api database
16:00:54 NobodyCam ahh Thank you melwitt !!
16:01:09 NobodyCam been looking at nova db. haven't even looked at the api side ;p
16:06:25 melwitt was this bug https://bugs.launchpad.net/nova/+bug/1784093
16:06:25 melwitt NobodyCam: yeah.. you likely don't have any trace of the instance in the nova db. usually the reason you can see the instance in the 'server list' but not the 'server show' is because 'server list' will count build_requests as instances as well in order to preserve the behavior where you can see an instance immediately after you request to boot it. but if there's no instance_mappings record, nova will think it can't find anything. it
16:06:37 melwitt are you running a version older than queens?
16:09:16 NobodyCam actually in this region it is Queens, it's in process of migrating to ussuri but not complete yet
16:10:35 melwitt hm, ok. there might be another corner case but ^ was the most common one
16:11:22 melwitt released in 17.0.11
16:20:31 NobodyCam Interesting not in build_requests but did find reference to the instance_id in instance_mappings table in nova_api DB
16:24:00 melwitt oh, so the inverse? hm
16:25:21 NobodyCam I should not this region had a network outage, caused some strange things, I am attempting to recover
16:25:32 NobodyCam snot/note/
16:26:11 melwitt I need to go back through and look at all those again, there's some places where if one db write succeeds while another fails, you get these bad states

Earlier   Later