Monday, 2025-07-28

opendevreviewTakashi Kajinami proposed openstack/nova master: Migrate MEM_ENCRYPTION_CONTEXT from root provider  https://review.opendev.org/c/openstack/nova/+/92181401:15
opendevreviewTakashi Kajinami proposed openstack/nova master: Detect AMD SEV-ES support  https://review.opendev.org/c/openstack/nova/+/92568501:15
opendevreviewTakashi Kajinami proposed openstack/nova master: Add hw_mem_encryption_model image property  https://review.opendev.org/c/openstack/nova/+/92770601:15
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Launch instances with SEV-ES memory encryption  https://review.opendev.org/c/openstack/nova/+/92610601:15
*** mhen_ is now known as mhen01:19
opendevreviewTakashi Kajinami proposed openstack/nova master: Add hw_mem_encryption_model image property  https://review.opendev.org/c/openstack/nova/+/92770602:01
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Launch instances with SEV-ES memory encryption  https://review.opendev.org/c/openstack/nova/+/92610602:01
opendevreviewTakashi Kajinami proposed openstack/nova master: Add hw_mem_encryption_model image property  https://review.opendev.org/c/openstack/nova/+/92770602:31
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Launch instances with SEV-ES memory encryption  https://review.opendev.org/c/openstack/nova/+/92610602:31
opendevreviewFriedrich Hiekel proposed openstack/nova master: Fix nova-scheduler placement error  https://review.opendev.org/c/openstack/nova/+/95193607:00
opendevreviewFriedrich Hiekel proposed openstack/nova master: Fix nova-scheduler placement error  https://review.opendev.org/c/openstack/nova/+/95193607:46
*** ykarel_ is now known as ykarel08:02
opendevreviewFlorian proposed openstack/nova master: Add check for PCIe devices attach limit for volume and ports  https://review.opendev.org/c/openstack/nova/+/95558411:02
opendevreviewFlorian proposed openstack/nova master: Add check for PCIe devices attach limit for volume and ports  https://review.opendev.org/c/openstack/nova/+/95558411:04
*** ykarel_ is now known as ykarel11:12
*** ykarel_ is now known as ykarel11:48
opendevreviewFlorian proposed openstack/nova master: Add check for PCIe devices attach limit for volume and ports  https://review.opendev.org/c/openstack/nova/+/95558412:53
opendevreviewWesley Hershberger proposed openstack/nova stable/2024.2: Use dict object for request_specs_dict in the _list_view  https://review.opendev.org/c/openstack/nova/+/95531015:27
opendevreviewWesley Hershberger proposed openstack/nova stable/2024.1: Use dict object for request_specs_dict in the _list_view  https://review.opendev.org/c/openstack/nova/+/95530515:30
opendevreviewWesley Hershberger proposed openstack/nova stable/2024.2: Use dict object for request_specs_dict in the _list_view  https://review.opendev.org/c/openstack/nova/+/95531016:38
opendevreviewWesley Hershberger proposed openstack/nova stable/2024.1: Use dict object for request_specs_dict in the _list_view  https://review.opendev.org/c/openstack/nova/+/95530516:41
opendevreviewWesley Hershberger proposed openstack/nova stable/2024.1: Use dict object for request_specs_dict in the _list_view  https://review.opendev.org/c/openstack/nova/+/95530516:42
sean-k-mooneydansmith: gibi  i mentioned this a few day ago but before the end fo the release we probly need to add a license file to nova-contibe and decied if that shoudl be refactored into a actul python package or not17:00
sean-k-mooneythe latter topic does not nessisarly need to be decied now17:00
sean-k-mooneybut we should have a license file in the repo ideally before rc1 and figure out what the release model for that repo is ectra17:01
sean-k-mooneyat the moment i dont think its possibel to use the release repo to actully do releases of it17:02
dansmithlicense file is fine, I think we should mark it as non-released (like os-test-images)17:02
gibiyeah I'm OK to add a licence file and make it non-released17:02
sean-k-mooneyi dont really have a stong opion currently 17:03
sean-k-mooneyit might be nice to release it eventually but i kind fo wanted use to have a dicussion about what it should and shoudl not contains and docuemnt that somehere like in a readme file17:03
sean-k-mooneybut we dont need to have that dicusssion now17:04
melwittdansmith, gibi, sean-k-mooney: I expect this question will need context load time so no worries to answer right away but in the vTPM patches I have up for review, I did not do a service version bump. the reason is because I could not find how it is needed,19:11
melwittnew instances require compute traits that old computes will not have, so attempts to live migrate from new to old will fail with NoValidHost if there are no eligible new computes to go to19:12
melwittwere you thinking maybe of rejecting in the API if the min service version in the deployment is still old? to not allow live migration at all even to new computes when mid-upgrade? if so, then I do understand that 19:13
sean-k-mooneyi need to load context but it may have been related to how the traits usage is implemented19:14
melwittI might be missing something totally obvious but so far I was not understanding the requirement19:14
sean-k-mooneyim not sure we need a comptue service version bump19:14
sean-k-mooneybut if you requet say user mode vs one of the other modes you need to be sure the host that the vm land on understands the new iamge metadata19:15
sean-k-mooneyif we are doign that via traits uncondtionaly 19:15
sean-k-mooneythen we are prorbaly fine as you said19:15
melwittyeah I kind of wondered if the service version bump was a discussion before the traits were decided on, so something like that. so I wanted to talk and find out if there is something I'm missing19:15
melwitt*or something like that19:15
sean-k-mooneyi would honestly need to reload context by reading the spec19:16
melwittyeah, np. I wasn't sure when to ask this because I know it is complicated19:16
sean-k-mooneyi mean if i had recently read your patchs askign here woudl be fine but i have not looked at the vtpm stuff this cycle so this has all been paged out of my workign memory19:17
melwittfor now I'm working on more func tests and maybe some more whitebox coverage and maybe some plain tempest coverage19:17
sean-k-mooneymelwitt: so based on yoru current undersdainding yoru not seeign a need for a bump is that correct19:18
melwittyep 100% understand19:18
melwittsean-k-mooney: that is my belief yes but I am aware I might be missing understanding19:18
sean-k-mooneyi wonder if maybe it was related to the image show changes?19:19
sean-k-mooneydid we ant to make sure tha tyou could see the policy or something19:19
sean-k-mooneythat in epoxy so at this poitn we woudl not need it19:19
melwittoh, hm, that's an angle I didn't think of19:19

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!