Earlier  
Posted Nick Remark
#openstack-nova - 2024-08-21
16:08:47 sean-k-mooney melwitt: yes and no
16:08:54 sean-k-mooney it mostly is
16:09:02 stephenfin sean-k-mooney: so the answer is it depends :)
16:09:04 sean-k-mooney you shoudl set it to 0 for bfv flavors
16:09:15 stephenfin if I pass an imageRef, then the BFV is totally ignored
16:09:33 sean-k-mooney in older release we used to claim it if not but in newer release if its BFV even if the falvor is not 0 we 0 it in placment ectra
16:09:42 stephenfin if I do not pass an imageRef, then the server goes to error state due an ImageNotFound error
16:09:43 sean-k-mooney so it depend on how old your nova is
16:09:50 melwitt I see
16:09:54 sean-k-mooney but like train did the right thing
16:10:18 sean-k-mooney so its been correctly ignoring it for bfv for a long time
16:10:22 stephenfin this is using a relatively recent deploy of DevStack (commit 8c4a2e1b4759b9932bcad10810143e61ec9b4c36 from Jul 20)
16:11:30 stephenfin sean-k-mooney: I was thinking that I would get a disk size of 6, but idk if that's necessarily something we want to support. Flavors are there for a reason and allowing users to do this provides a way to side-step what the operators want them to use
16:11:57 stephenfin then again, they could just request N ephemeral disks, so it probably doesn't matter: the operator has to reply on quota to save them
16:12:04 sean-k-mooney stephenfin: they kind of alreayd have that however
16:12:16 stephenfin you mean with Cinder?
16:12:21 sean-k-mooney and we do allow you do do it for the addtional ephmeral disk and for bfv
16:12:42 sean-k-mooney no so you can have a flavor with ephmeral_disk=100GB
16:12:51 stephenfin oh, yes
16:12:55 sean-k-mooney and hten you can subdevided that into multiple disks via the bdm
16:13:09 stephenfin me trying to figure out whether I could do that is what led me down this rabbit hole :)
16:13:17 sean-k-mooney https://docs.openstack.org/nova/train/user/launch-instance-from-volume.html#create-volume-from-image-and-boot-instance
16:13:46 stephenfin fwict, it's not really subdividing it so much as completely ignoring what's in the flavor
16:14:12 sean-k-mooney well if its using 6GB i think that is correct
16:14:37 sean-k-mooney provided the flavor is > 6GB
16:14:42 sean-k-mooney well >=
16:15:49 sean-k-mooney https://docs.openstack.org/ocata/user-guide/cli-nova-launch-instance-from-volume.html
16:16:13 sean-k-mooney the note makes it pretty clear for swap and ephermeral
16:16:15 sean-k-mooney "The flavor defines the maximum swap and ephemeral disk size. You cannot exceed these maximum values."
16:16:30 sean-k-mooney so it looks like we wanted the bdms to have precednce over the flavor
16:16:48 stephenfin Yup. That's what I'm seeing. Good point. I'd missed that nuance
16:18:44 sean-k-mooney i assume you followed the BFV example but changed source ot image and dest to local
16:18:48 sean-k-mooney $ openstack server create --flavor FLAVOR --block-device \
16:18:50 sean-k-mooney source=SOURCE,id=ID,dest=DEST,size=SIZE,shutdown=PRESERVE,bootindex=INDEX \
16:18:52 sean-k-mooney NAME
16:19:51 stephenfin sort of - I hacked in a `--root` option to OSC
16:20:05 stephenfin it was easier than figuring out a `--block-device` invocation 0:)
16:20:21 sean-k-mooney ok is there a reason yoru doing this
16:20:40 stephenfin <stephenfin> me trying to figure out whether I could do that is what led me down this rabbit hole :)
16:20:53 sean-k-mooney ok there are some things you can only do via the bdms
16:21:23 sean-k-mooney im confilictedc if i should tell you what those are
16:21:31 sean-k-mooney on one hand you might make it easy to do
16:21:52 sean-k-mooney on the other hand you might make it easy to do and ill have to support people doing it :)
16:22:57 sean-k-mooney the only way to specify a per disk device type is block_device_mapping_v2.device_type i.e. disk, cdrom.
16:22:58 stephenfin that ship has sailed. There are already a load of newish BDM-related options that I added over the past few years (like the `--block-device` option you refer to)
16:23:05 sean-k-mooney you can also set block_device_mapping_v2.disk_bus pre bdm
16:23:20 sean-k-mooney allowign diffent disks to have specific disk bus "fdc, ide, sata, scsi, usb, virtio, xen, lxc and uml."
16:24:08 sean-k-mooney so if you wanted your root disk to use stata and the rest to use virtio-blk or virtio-scsi
16:24:27 sean-k-mooney you should be able to express that in the bdms
16:25:40 auniyal (did not wanted to disturb on-going chat, but its late for me, so when you have some time) can you please look into these https://review.opendev.org/q/topic:%22lp/2012365%22 ; backports for stable/2023.1 merged in stable/2023.1
16:25:40 auniyal hey elodilles, sean-k-mooney, stephenfin,
16:27:42 elodilles auniyal: ACK, added to my TODO list, though probably will do only tomorrow
16:28:42 auniyal elodilles, thanks, yeah sure
16:38:39 opendevreview Pavlo Shchelokovskyy proposed openstack/nova master: Fix device type when booting from ISO image https://review.opendev.org/c/openstack/nova/+/909611
#openstack-nova - 2024-08-22
00:58:32 opendevreview melanie witt proposed openstack/nova master: Add [workarounds]unified_limits_permissive_enforcement https://review.opendev.org/c/openstack/nova/+/924025
01:51:19 opendevreview melanie witt proposed openstack/nova master: nova-manage: Add flavor scanning to migrate_to_unified_limits https://review.opendev.org/c/openstack/nova/+/924110
03:51:44 opendevreview Ghanshyam proposed openstack/placement master: Update test to use service role https://review.opendev.org/c/openstack/placement/+/926870
03:52:49 opendevreview Ghanshyam proposed openstack/placement master: DNM: testing latest oslo.policy https://review.opendev.org/c/openstack/placement/+/926088
06:36:43 opendevreview Michael Still proposed openstack/nova master: libvirt: Add config option to require secure SPICE. https://review.opendev.org/c/openstack/nova/+/922544
06:36:44 opendevreview Michael Still proposed openstack/nova master: libvirt: Add extra spec for sound device. https://review.opendev.org/c/openstack/nova/+/926126
06:36:44 opendevreview Michael Still proposed openstack/nova master: libvirt: allow direct SPICE connections to qemu https://review.opendev.org/c/openstack/nova/+/924844
06:36:45 opendevreview Michael Still proposed openstack/nova master: libvirt: direct SPICE console database changes https://review.opendev.org/c/openstack/nova/+/926877
06:36:45 opendevreview Michael Still proposed openstack/nova master: libvirt: direct SPICE console object changes https://review.opendev.org/c/openstack/nova/+/926876
07:21:00 opendevreview Viktor Křivák proposed openstack/nova master: Ensure claims to placement are freed after evacuate complete Improve resource_tracker delete_allocation_for_evacuated_instance to handle non-cached compute hosts Fix test to accept this change https://review.opendev.org/c/openstack/nova/+/926292
07:42:24 opendevreview Amit Uniyal proposed openstack/nova master: Libvirt: updates resource provider trait list https://review.opendev.org/c/openstack/nova/+/926521
07:42:25 opendevreview Amit Uniyal proposed openstack/nova master: zvm: updates resource provider trait list https://review.opendev.org/c/openstack/nova/+/926523
07:42:25 opendevreview Amit Uniyal proposed openstack/nova master: VMware: updates resource provider trait list https://review.opendev.org/c/openstack/nova/+/926522
07:42:26 opendevreview Amit Uniyal proposed openstack/nova master: Ironic: updates resource provider trait list https://review.opendev.org/c/openstack/nova/+/926524
08:38:42 opendevreview Pavlo Shchelokovskyy proposed openstack/nova master: Fix device type when booting from ISO image https://review.opendev.org/c/openstack/nova/+/909611
08:58:20 mikal sean-k-mooney: I've split up that first patch BTW.
12:04:14 songwenping hi team, i live migrate vgpu vm with lateast code by devstack and nova-scheduler except with 'No valid host was found, The instance has complex allocations on the source host so move cannot be forced.'
12:18:56 erlon Hey Nova core team, I brought [this patch series](https://review.opendev.org/q/topic:%22sg-shared-filter%22) for discussion a couple months ago, and we got the understanding that we will accept this feature for this release. Can you guys please review and approve the change?
15:35:53 opendevreview Merged openstack/nova master: Fix wrong nova-manage command in upgrade check https://review.opendev.org/c/openstack/nova/+/880819
15:55:29 elodilles hi nova team o/ it seems that python-novaclient's gate is broken: https://review.opendev.org/c/openstack/python-novaclient/+/926334
15:55:45 elodilles with python-novaclient-functional job
15:56:29 elodilles as some tests reports error, with "Multiple possible networks found, use a Network ID to be more specific. (HTTP 409)" error message
15:57:09 elodilles does anyone know from top off the head what this is related to?
16:44:29 melwitt elodilles: I don't know the cause but there is a bug open that reported it https://bugs.launchpad.net/python-novaclient/+bug/2077168
16:48:41 opendevreview Ghanshyam proposed openstack/placement master: Update test to use service role https://review.opendev.org/c/openstack/placement/+/926870
16:49:39 sean-k-mooney elodilles: ya i saw but didnt have a change to look into wy
16:50:45 sean-k-mooney elodilles: i assume its a change in devstack or somethign else that is now resulting in new networks or we have a test interaction issue
16:52:18 sean-k-mooney elodilles: i firsted notcied that on https://review.opendev.org/c/openstack/python-novaclient/+/926532
16:53:44 opendevreview Ghanshyam proposed openstack/placement master: Bump oslo.policy version to enable new RBAC by default https://review.opendev.org/c/openstack/placement/+/926935
16:54:29 sean-k-mooney there are 2 netowrks aviable the public and private network. i know there was a bug in neutron at one point where external networks(public) would not be visiable unless also marked as shared or something like that
16:54:35 sean-k-mooney so maybe that was fixed
16:54:52 sean-k-mooney it would be more helpful if the error actully listed the networks
16:59:12 sean-k-mooney neutron have been modifygin there rback policy around networks https://github.com/openstack/neutron/commit/f22f7ae012e75b34051945fcac29f955861896ab
17:25:48 elodilles thanks melwitt and sean-k-mooney , i'll try to look into these next week (though secretly hoping that the issue is familiar to someone and there will be a fix by then o:))
17:44:23 sean-k-mooney it sound like some of the issue we ocational have with tempest
17:45:03 sean-k-mooney but i dont recally anything sepficic
17:45:10 sean-k-mooney so maybe the neutron folks would know
18:19:21 melwitt I see there is code for handling multiple networks (https://github.com/openstack/python-novaclient/blob/2bd135c13793da48af5fbad5208b00aaba7e39dc/novaclient/tests/functional/v2/test_servers.py#L229) however that means test_boot_server_with_auto_network will be skipped. so even if we added a self.multiple_networks check to the failing test, we presumably have lost coverage of test_boot_server_with_auto_network
18:19:54 melwitt I have not been able to find the cause of the change in networks available in the test env
18:19:54 gmann sean-k-mooney: dansmith: melwitt: can you please check these two placement review, it is needed for oslo.policy 4.4.0 which enable new defaults by default https://review.opendev.org/c/openstack/placement/+/926870/2 https://review.opendev.org/c/openstack/placement/+/926935/1
18:20:39 opendevreview Dan Smith proposed openstack/nova master: Use format_inspector from oslo https://review.opendev.org/c/openstack/nova/+/925025
18:21:25 dansmith gmann: "X_ROLES" really?
18:23:02 sean-k-mooney melwitt: the test that is failing is expresssly testing booting without specifyign any network info
18:23:10 sean-k-mooney melwitt: on micorversion 2.1
18:23:21 sean-k-mooney melwitt: which shoudl use the default network
18:23:42 sean-k-mooney or rahter any network if there only one

Earlier   Later