Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-03-19
19:58:45 spbarbieri Thanks for the pointer. When creating the server I can specify "block_device_mapping_v2.delete_on_termination". This is saved somewhere because my volume is deleted on server termination. I was hoping that the "this is the boot device" was saved there as well. But, I couldn't find it in any of the server/volume/volume_attach apis.
20:05:47 artom spbarbieri, I *think* boot_index is what you're looking for, but it doesn't look like we expose it anywhere in the API
20:06:03 artom spbarbieri, you can also tag with 'boot' as a workaround
20:14:22 spbarbieri yeah, boot_index would be perfect. I couldn't find it anywhere either. I'm actually trying to do this after the fact. I have a running server and I want to know which volume was used as the boot drive. I only have access to the REST API...sounds like a MacGyver episode...find the boot drive using a paperclip and some duct tape
20:23:05 openstackgerrit Merged openstack/nova master: Use assertXmlEqual() helper for all XML comparison tests https://review.openstack.org/641852
20:23:13 openstackgerrit Merged openstack/nova stable/rocky: Allow utime call to fail on qcow2 image base file https://review.openstack.org/643011
20:24:00 mriedem spbarbieri: that's eventually going to show up in the API here https://review.openstack.org/#/c/623981/24
20:24:13 mriedem e.g. https://review.openstack.org/#/c/623981/24/doc/api_samples/os-volumes/v2.72/volume-attachment-detail-resp.json
20:25:56 mriedem if you're an admin, you could also see the OS-EXT-SRV-ATTR:root_device_name parameter in the response from the GET /servers/{server_id} API
20:26:21 mriedem and match that to the volume with the same device name, although those aren't guaranteed to be where the root volume is mounted in the guest
20:27:58 spbarbieri Thanks for the pointer to the volume-attach details. That will be helpful. I'm running against my local devstack, as admin, and I don't get that returned. I'm calling compute/v2.1/servers/{id}.
20:55:06 melwitt spbarbieri: are you using novaclient or openstackclient? if the latter, you need to pass the necessary compute API microversion to see the volume-attach info. i.e. --os-compute-api-version 2.3 (see https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-kilo)
20:55:35 melwitt s/volume-attach info/root_device_name/
20:57:51 spbarbieri melwitt: I'm using Postman with direct REST API calls
21:00:28 melwitt spbarbieri: OK, see this doc on how to specify compute API microversion with the HTTP header https://developer.openstack.org/api-guide/compute/microversions.html#client-interaction
21:04:41 spbarbieri melwitt: Yes! Thanks. Adding that header works. I guess now I can match the root_device_name against all of the attached volumes to find a match. Does that seem reasonable?
21:06:24 melwitt spbarbieri: I think so, based on what mriedem said earlier
21:07:07 spbarbieri melwitt: Thank you for the help.
21:07:18 melwitt np, good luck
21:58:27 openstackgerrit melanie witt proposed openstack/nova master: Add a prelude release note for the 19.0.0 Stein GA https://review.openstack.org/644412
22:05:13 efried melwitt: it's like VOIP in the '90s.
22:05:18 efried or, you know, skype today.
22:05:24 melwitt haha, yeah
22:20:05 mriedem melwitt: efried: cdent: dansmith: also dumped comments in the prelude https://review.openstack.org/#/c/644412/ about vgpu
22:20:12 mriedem i'd either remove that or really dumb it down
22:21:00 melwitt mriedem: thanks
22:21:30 efried mriedem: The part I was concerned about:
22:21:41 efried admins will sometimes list resource providers
22:21:48 mriedem the vcenter driver also supports live migration, that's a long-standing thing that might be worth mentioning
22:21:50 efried Now they're gonna see two instead of one for some hosts
22:22:02 efried that's a user-facing manifestation of the nrp-for-vgpus thing.
22:22:12 efried that's the only reason I think it's worth mentioning
22:22:20 melwitt mriedem: ack
22:22:23 efried otherwise I agree there would be no reason to talk about it.
22:22:46 efried "We did this thing, so don't be surprised if you see two resource providers for a libvirt host with VGPUs."
22:22:58 melwitt I see, yeah
22:23:33 mriedem there is an upgrade release note for it right? so as long as we can really distill the prelude comment on that to something short and sweet
22:24:06 efried sorry I've been entirely ineffectual phrasing that :( I've been trying to nail down the zillion UT failures that happen when you change how ksa is mocked. Different headspace.
22:24:08 melwitt there is an upgrade note, but it doesn't really spell out what an admin would see as a change when they list RPs
22:24:18 mriedem "Upon restarting nova-compute services using the libvirt driver which expose VGPU inventory, the inventory will be moved from the root compute node resource provider to a child resource provider. See the upgrade notes for details."
22:24:40 efried wfm
22:24:48 melwitt yeah, that sounds good
22:25:16 mriedem how about, ""Upon restarting nova-compute services using the libvirt driver which expose VGPU inventory, the inventory will be moved from the root compute node resource provider to a child resource provider. As a result, when listing resource providers, you may see two for the same compute node where there was one before. See the upgrade notes for details."
22:25:27 efried even better
22:25:30 melwitt thumbs up
22:29:28 openstackgerrit Adam Spiers proposed openstack/nova master: Move libvirt calculation of machine type to utils.py https://review.openstack.org/644554
22:34:01 openstackgerrit Matt Riedemann proposed openstack/nova master: Address old TODO in claim_resources_on_destination https://review.openstack.org/644596
22:40:07 openstackgerrit melanie witt proposed openstack/nova master: Add a prelude release note for the 19.0.0 Stein GA https://review.openstack.org/644412
22:53:23 openstackgerrit melanie witt proposed openstack/nova master: Add known issue for minimum bandwidth resource leak https://review.openstack.org/644694
22:55:03 melwitt mriedem: gibi recommended the above is not an RC blocker, but I thought it might help to add a known issue reno about it ^
23:04:18 openstackgerrit Eric Fried proposed openstack/nova master: WIP/PoC: Use SDK instead of ironicclient for node.get https://review.openstack.org/642899
23:04:18 openstackgerrit Eric Fried proposed openstack/nova master: WIP/PoC: Use openstacksdk for placement https://review.openstack.org/643664
23:04:19 efried dustinc: Warning: update here ^
23:04:36 dustinc thanks, I'll check it
23:04:38 efried you will need to refetch and put your changes onto the new commit
23:04:49 dustinc was just working on sdk_wrapper.py
23:04:57 efried easiest way if you haven't already committed locally would be to stash, review -d, and restore
23:05:05 efried dustinc: But we don't need sdk_wrapper.py
23:05:09 efried do we?
23:06:06 dustinc I thought we do...maybe we need to sync up on CONF tomorrow...I thought we needed to read everything and pass it to the SDK?
23:06:43 efried dustinc: Oh, that's done already :)
23:07:01 dustinc ok, I will stash my work and check yours out then I am going offline shortly
23:07:07 dustinc let's sync back up tomorrow
23:07:29 efried dustinc: See the predecessor patch at https://review.openstack.org/#/c/643664/5/nova/utils.py@1239
23:08:11 efried dustinc: So the only change needed to have ironic make use of that was here: https://review.openstack.org/#/c/642899/16/nova/virt/ironic/driver.py@188
23:08:31 efried dustinc: And tbc, this works, which you can tell by looking at the CI results, if you know what you're looking for:
23:08:55 efried The job called ironic-tempest-ipa-wholedisk-bios-agent_ipmitool-tinyipa only succeeds if ^ is copacetic
23:09:08 efried Here's the last run (before the latest rebase): http://logs.openstack.org/99/642899/15/check/ironic-tempest-ipa-wholedisk-bios-agent_ipmitool-tinyipa/c032d49/
23:09:14 efried http://logs.openstack.org/99/642899/15/check/ironic-tempest-ipa-wholedisk-bios-agent_ipmitool-tinyipa/c032d49/testr_results.html.gz
23:09:42 efried The other red stuff in the CI report is the unit and functional tests - for those, it's the actual tests that need to be fixed, not the code.
23:09:58 efried and most of the test fixage needs to happen in the predecessor patch - which is what I've been working on.
23:10:11 efried made a little progress today, but definitely didn't finish.
23:10:16 efried a couple of serious mysteries in there still.
#openstack-nova - 2019-03-20
01:55:03 eandersson What is the difference between disk_available_least and disk_free_gb ?
02:23:26 openstackgerrit Yongli He proposed openstack/nova master: Clean up orphan instances https://review.openstack.org/627765
02:26:38 eandersson It looks like maybe disk_available_least takes into account the qcow images on the host?
02:28:11 eandersson because the host has 79GB available, the flavor uses 74GB, but the scheduler thinks its out of disk space so refuses to schedule there
02:28:33 eandersson but if we schedule there manually using --availability-zone nova:<compute-name>
02:28:35 eandersson it works
02:29:01 eandersson and it now has ~4GB disk free according to the nova.compute logs
02:30:38 eandersson > does not have 76800 MB usable disk, it only has 44031.0 MB
02:31:10 eandersson So confusing that the disk space used to schedule isn't reported anywhere, or at the very least not the number the scheduler uses to make decisions upon isn't reported.
02:40:57 eandersson After scheduling manually I can see that disk_available_least is -33
02:41:07 eandersson but free_disk_gb is at 4
03:56:23 openstackgerrit Merged openstack/nova master: Remove "Fixing the Scheduler DB model" from schedule evolution doc https://review.openstack.org/643615
04:55:34 eandersson maybe jaypipes ? ^
05:09:14 openstackgerrit Merged openstack/nova master: Add docs for compute capabilities as traits https://review.openstack.org/644293
05:17:35 openstackgerrit Yongli He proposed openstack/nova master: Clean up orphan instances https://review.openstack.org/627765
07:15:46 openstackgerrit Seyeong Kim proposed openstack/nova stable/rocky: Share snapshot image membership with instance owner https://review.openstack.org/643853
09:02:54 openstackgerrit Michael Still proposed openstack/nova master: Complete remove fake_libvirt_utils. https://review.openstack.org/643897
09:02:55 openstackgerrit Michael Still proposed openstack/nova master: Remove fake_libvirt_utils users in functional testing. https://review.openstack.org/644793
09:28:10 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add known issue for minimum bandwidth resource leak https://review.openstack.org/644694
09:42:06 openstackgerrit Stephen Finucane proposed openstack/nova master: docs: Misc cleanups https://review.openstack.org/644616
10:08:53 mdbooth stephenfin: Hey, so it turns out sphinx also imports nova/api/openstack/__init__.py
10:09:15 mdbooth stephenfin: My patch is adding monkey patching there, so sphinx is still borked
10:10:11 mdbooth stephenfin: I moved monkey patching there for the wsgi entry point because I don't think it can be anywhere else, so I'm a bit stumped.
10:10:48 stephenfin mdbooth: Tried using the mock setting I was on about?
10:10:59 mdbooth stephenfin: In sphinx?
10:11:05 stephenfin aye
10:11:21 mdbooth Is that a valid thing to do?

Earlier   Later