| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-01-10 | |||
| 15:43:35 | gibi | artom: sean-k-mooney: dansmith: do we want to put the new properties field into the existing image dict in server show or a top level image_properties field? | |
| 15:44:01 | sean-k-mooney | same | |
| 15:44:40 | gibi | today we have id and links there | |
| 15:44:42 | sean-k-mooney | im thinking new filed but let me check what it looks like today | |
| 15:44:43 | dansmith | ah "properties" inside existing image seems good.. would be weird to have image.. and image_properties I think | |
| 15:45:14 | gibi | in the past we had the same for flavor but we dropped the links and added the embedded fields | |
| 15:45:50 | sean-k-mooney | as long as properies is the key in image and its a map of string to string that work for me | |
| 15:46:01 | gibi | OK, that sounds good to me too | |
| 15:47:22 | sean-k-mooney | thats what we do for flavor extra specs i think too but we dont have an exampel in the api ref | |
| 15:47:37 | sean-k-mooney | well we have | |
| 15:47:39 | sean-k-mooney | "flavor": { | |
| 15:47:41 | sean-k-mooney | "disk": 1, | |
| 15:47:43 | sean-k-mooney | "ephemeral": 0, | |
| 15:47:45 | sean-k-mooney | "extra_specs": {}, | |
| 15:47:47 | sean-k-mooney | "original_name": "m1.tiny", | |
| 15:47:49 | sean-k-mooney | "ram": 512, | |
| 15:47:51 | sean-k-mooney | "swap": 0, | |
| 15:47:53 | sean-k-mooney | "vcpus": 1 | |
| 15:47:55 | sean-k-mooney | }, | |
| 15:48:00 | sean-k-mooney | so ya properties under image would be consistent with that | |
| 15:48:35 | sean-k-mooney | just an fyi im going to finish for the week shortly | |
| 15:49:52 | gibi | sean-k-mooney: OK. Thanks. Have a nice weekend | |
| 15:58:38 | sean-k-mooney | o/ catch ye next week | |
| 16:20:24 | opendevreview | Balazs Gibizer proposed openstack/nova-specs master: Image properties in server show https://review.opendev.org/c/openstack/nova-specs/+/938932 | |
| 16:21:12 | opendevreview | Balazs Gibizer proposed openstack/nova-specs master: Image properties in server show https://review.opendev.org/c/openstack/nova-specs/+/938934 | |
| 16:21:51 | opendevreview | Balazs Gibizer proposed openstack/nova-specs master: Image properties in server show https://review.opendev.org/c/openstack/nova-specs/+/938910 | |
| 16:23:10 | gibi | artom: dansmith: ^^ that is my first stab at the image properties spec | |
| 16:26:51 | dansmith | ack, will look in a sec | |
| 16:51:15 | gibi | dansmith: thanks for the review, I will respin it | |
| 16:51:30 | dansmith | cool, thanks | |
| 16:51:49 | dansmith | I hate that we have to make more work, but I also think this is long overdue, so I'm glad for the excuse :) | |
| 16:57:23 | gibi | yeah this feels like a low effort high value change regardless of the vTPM work | |
| 16:57:42 | opendevreview | Balazs Gibizer proposed openstack/nova-specs master: Image properties in server show https://review.opendev.org/c/openstack/nova-specs/+/938910 | |
| 16:57:55 | gibi | I've fixed the comments ^^ | |
| 17:00:23 | dansmith | I've +2d :) | |
| 17:01:34 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2024.2: Add a global limit on the number of allocation candidates https://review.opendev.org/c/openstack/placement/+/938939 | |
| 17:01:35 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2024.2: Add round-robin candidate generation strategy https://review.opendev.org/c/openstack/placement/+/938941 | |
| 17:01:35 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2024.2: Factor out allocation candidate generation strategy https://review.opendev.org/c/openstack/placement/+/938940 | |
| 17:01:38 | gibi | dansmith: thansk | |
| 17:01:43 | gibi | thanks even () | |
| 17:01:51 | gibi | :) | |
| 17:03:04 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2024.1: Factor out allocation candidate generation strategy https://review.opendev.org/c/openstack/placement/+/938943 | |
| 17:03:04 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2024.1: Add a global limit on the number of allocation candidates https://review.opendev.org/c/openstack/placement/+/938942 | |
| 17:03:05 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2024.1: Add round-robin candidate generation strategy https://review.opendev.org/c/openstack/placement/+/938944 | |
| 17:04:15 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2023.2: Factor out allocation candidate generation strategy https://review.opendev.org/c/openstack/placement/+/938946 | |
| 17:04:15 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2023.2: Add a global limit on the number of allocation candidates https://review.opendev.org/c/openstack/placement/+/938945 | |
| 17:04:16 | opendevreview | Balazs Gibizer proposed openstack/placement stable/2023.2: Add round-robin candidate generation strategy https://review.opendev.org/c/openstack/placement/+/938947 | |
| 21:51:15 | opendevreview | Balazs Gibizer proposed openstack/nova-specs master: Image properties in server show https://review.opendev.org/c/openstack/nova-specs/+/938910 | |
| 21:54:58 | melwitt | gibi: I had +W ^ but then saw in the backscroll this is supposed to wait for a spec freeze exception, so I pulled it from the gate | |
| 22:05:22 | sean-k-mooney | im also +2 on that too but ya we can chat about it in the team meeting on tuesday | |
| 22:26:01 | opendevreview | Ghanshyam proposed openstack/nova-specs master: Propose API policy service and manager role spec https://review.opendev.org/c/openstack/nova-specs/+/937650 | |
| #openstack-nova - 2025-01-11 | |||
| 07:57:25 | gibi | melwitt: sean-k-mooney: thanks, yeah I will formally ask for an exception on Monday from bauzas and we can discuss it on the meeting Tuesday | |
| 15:43:55 | opendevreview | Dmitriy Chubinidze proposed openstack/nova master: doc: nova service_user wrong auth_url https://review.opendev.org/c/openstack/nova/+/938680 | |
| 16:15:44 | opendevreview | Dmitriy Chubinidze proposed openstack/nova master: doc: nova service_user wrong auth_url https://review.opendev.org/c/openstack/nova/+/938680 | |
| 16:49:47 | opendevreview | Dmitriy Chubinidze proposed openstack/nova master: doc: nova service_user wrong auth_url https://review.opendev.org/c/openstack/nova/+/938680 | |
| 21:45:37 | opendevreview | Dmitriy Chubinidze proposed openstack/nova master: doc: nova service_user wrong auth_url https://review.opendev.org/c/openstack/nova/+/938680 | |
| #openstack-nova - 2025-01-13 | |||
| 04:55:50 | opendevreview | Takashi Kajinami proposed openstack/os-resource-classes master: Fix outdated envlist https://review.opendev.org/c/openstack/os-resource-classes/+/939018 | |
| 05:04:15 | opendevreview | Takashi Kajinami proposed openstack/python-novaclient master: Remove environment for Python 3.8 https://review.opendev.org/c/openstack/python-novaclient/+/939022 | |
| 05:11:14 | opendevreview | Takashi Kajinami proposed openstack/nova master: Drop environment for Python 3.8 https://review.opendev.org/c/openstack/nova/+/939027 | |
| 05:37:55 | opendevreview | Hemanth N proposed openstack/nova master: Add memory stats to compute monitor https://review.opendev.org/c/openstack/nova/+/939044 | |
| 06:08:17 | opendevreview | Hemanth N proposed openstack/nova master: Add memory stats to compute monitor https://review.opendev.org/c/openstack/nova/+/939044 | |
| 07:18:02 | opendevreview | Hemanth N proposed openstack/nova master: Add memory stats to compute monitor https://review.opendev.org/c/openstack/nova/+/939044 | |
| 07:48:39 | opendevreview | Hemanth N proposed openstack/nova master: Add memory stats to compute monitor https://review.opendev.org/c/openstack/nova/+/939044 | |
| 08:40:27 | gibi | bauzas: when you are up. I would like to formally ask for a spec freeze exception for https://review.opendev.org/c/openstack/nova-specs/+/938910 | |
| 08:40:35 | gibi | This is a spin off of the vTPM live migration spec | |
| 08:41:09 | gibi | but the impact is moved out of it as a) it has API impact b) it is independently useful feature | |
| 08:41:30 | gibi | we already have plenty of core approval on it so it does not seems to controversial | |
| 08:43:28 | gibi | the assignee of the impl is a questionmark today but just because we want to give the opportunity to auniyal or ratailor to pick it up. But if it does not fit to their timeline for E then I can be the fallback to push the implementation. Fortunately it is a small impact one | |
| 08:44:09 | gibi | more context is in the comment thread https://review.opendev.org/c/openstack/nova-specs/+/938843/1#message-c65ec478107012ab4c141bd79812528a74f7761d | |
| 09:10:10 | auniyal | hey gibi, can you please have a look at https://bugs.launchpad.net/nova/+bug/2093869/, nova-place placement bug | |
| 09:10:51 | ratailor | gibi, I could try to do that. | |
| 09:11:57 | gibi | ratailor: cool. Thanks for stepping up | |
| 09:12:01 | gibi | auniyal: looking | |
| 09:38:37 | opendevreview | Rajesh Tailor proposed openstack/nova master: Add support for showing finish_time https://review.opendev.org/c/openstack/nova/+/928933 | |
| 09:46:04 | gibi | auniyal: so this is a system with PCI in Placement enabled and after a while, even if the devstack sits idle the compute starts failing with the conflict exception | |
| 09:53:28 | gibi | auniyal: you wrote that "If we recreate resource provider, then new once does not have DISK_GB resource-class | |
| 09:53:31 | gibi | " | |
| 09:53:58 | gibi | does it mean you stopped the compute, deleted the RP tree, and then started the compute? | |
| 09:54:16 | gibi | did you have VMs running on this compute? | |
| 09:56:34 | gibi | do you just enabled PCI in Placement or also have some devices configured via [pci]device_spec config option? | |
| 09:56:56 | auniyal | that time, I teventually endup deleting R-P and creating new, | |
| 09:56:56 | auniyal | that time, I had VM, which was failing to start usin nova cmd, - on checking compute logs I saw this error. | |
| 09:56:56 | auniyal | not in right now- but I encountered the same issue, earlier (do not this VM-setup anymore ) | |
| 09:57:17 | auniyal | no | |
| 09:57:17 | auniyal | > enabled PCI in Placement or also have some devices configured via [pci]device_spec config option? | |
| 09:57:30 | auniyal | both time, there is no PCI changes | |
| 09:58:16 | auniyal | or any update in any service confs, the system is as same as how devstack deploy it | |
| 09:59:07 | auniyal | only thing is, I have ceph enabled for storage | |
| 09:59:39 | opendevreview | Dmitriy Chubinidze proposed openstack/nova master: Adding link for RabbitMQ installation during nova deployment on controller node. https://review.opendev.org/c/openstack/nova/+/938702 | |
| 10:03:06 | auniyal | meant, I do not have that setup anymore, and this is a new setup having similar issue | |
| 10:03:06 | auniyal | >>> not in right now- but I encountered the same issue, earlier (do not this VM-setup anymore ) | |
| 10:17:22 | gibi | auniyal: so the error is coming from https://github.com/openstack/nova/blob/a459467899d2b406aa8cf530ae481255eaf3c957/nova/compute/resource_tracker.py#L1360-L1370 Interstingly the comment in the code contradicts with the actual InventoryInUse exception in the logs. So I think the assumption that all the InventoryInUse exception from update_from_provider_tree is realted to PCI in Placement is wrong | |
| 10:18:13 | gibi | so that exception translation needs to be fixed to only react on real exceptions from the PCI in Placement codepath and do not react on other InventoryInUse exceptions. | |
| 10:18:35 | gibi | Still I'm wondering why the exception is raised in you env | |
| 10:19:01 | gibi | could you replace the raise exception.PlacementPciException(error=str(e)) | |
| 10:19:09 | auniyal | yes, I was surprised seeing PlacementPciException ! | |
| 10:19:10 | gibi | line with a raise e | |
| 10:19:25 | gibi | and try to start up the compute | |
| 10:20:04 | auniyal | ack, please give a min | |
| 10:23:56 | auniyal | gibi, https://paste.openstack.org/show/bqQZYiVU8NA5PdRxn7Rm/ | |