Wednesday, 2024-08-07

*** ministry is now known as __ministry00:54
opendevreviewmelanie witt proposed openstack/nova master: DNM testing  https://review.opendev.org/c/openstack/nova/+/92563501:00
*** bauzas_ is now known as bauzas01:12
opendevreviewTakashi Kajinami proposed openstack/nova master: Detect AMD SEV-ES support  https://review.opendev.org/c/openstack/nova/+/92568502:45
opendevreviewmelanie witt proposed openstack/nova master: DNM testing cont'd  https://review.opendev.org/c/openstack/nova/+/92583806:57
opendevreviewmelanie witt proposed openstack/nova master: DNM testing cont'd  https://review.opendev.org/c/openstack/nova/+/92583807:04
melwittsean-k-mooney: just for illustrating how the fetch_func stuff is not used at all in this poc ^ (hopefully I didn't mess up in deleting)07:10
*** bauzas_ is now known as bauzas07:36
gibimelwitt: thanks for proposing the fix for the persistent mdev bug07:41
*** bauzas_ is now known as bauzas08:57
ykarelcan someone check the zed backport https://review.opendev.org/c/openstack/nova/+/92574910:06
opendevreviewTakashi Kajinami proposed openstack/nova master: Detect AMD SEV-ES support  https://review.opendev.org/c/openstack/nova/+/92568510:11
elodillesykarel: clean cherry pick so +2+W'd it11:48
ykarelthx elodilles 11:48
gibiykarel: as that targets an unmaintained branch nova core team is not involved reviewing and landing it 11:48
gibibut I guess elodilles is in the global unmaintained core team :)11:51
ykarelgibi, ack11:53
sean-k-mooneyso i have debated this in the past with my self but i think the unmatined branches woudl benifit form a dedicated channel that is seperate form the proejct channels to cordinate unmatined branch reviews11:53
elodillessean-k-mooney: there is a semi-official channel: #openstack-unmaintained o:)11:54
sean-k-mooneyack provided the unmaintained pings are not excessive i dont entirly object to havign them here too but we were very clear in teh resolution that core teams would not review patches too or genericallly maintiane the unmainted branches as part fo the resolution11:57
elodillesyepp11:58
sean-k-mooneyso unless an unmainted branch maitiner wants input on a patch they are unsure about i woudl prefer to avoid the day to day work of maintainign them here11:58
sean-k-mooneyelodilles: if you are unsure about somethign imporant liek a cve back port we will proably be fine with a quick skim over a patch you have prepared11:59
sean-k-mooneyor if your trying to resolve a merge conflcit and we are not too busy but in general for can we review x i would prefer to keep that in  #openstack-unmaintained12:00
elodillessean-k-mooney: ACK, thanks in advance! o:)12:13
* gibi don't even have +2 rights on unmaintaned/12:23
gibi(not that I want it)12:23
sean-k-mooneysame i considerd puting my name forward but i have too much on my plate currently to really consier it12:24
sean-k-mooneyi know many are in that both but im jsut relecting reality that i cant spend time on the unmainited branches at present12:25
gibiwe set them unmaintaned as we don't want to / cannot maintain them. So it is fair to say that we dont care :)12:35
*** tkajinam is now known as Guest241512:52
*** tkajinam is now known as Guest241613:00
*** ministry is now known as __ministry13:55
*** whoami-rajat_ is now known as whoami-rajat13:56
stephenfinelodilles: Speaking of unmaintained, we have a variety of git-review proposal patches open against cliff, python-openstackclient and openstacksdk. Can you or someone abandon those since it's very unlikely anyone will use those branches for client tooling15:34
opendevreviewmelanie witt proposed openstack/nova master: libvirt: Remove node device XML validate flags  https://review.opendev.org/c/openstack/nova/+/92582616:34
JayFsean-k-mooney: & other cores; https://review.opendev.org/q/topic:ironic-guest-metadata is tested working in devstack, I wanted some review feedback before moving beyond this point into migration/tempest. I've asked Ironic cores to look at them as well.16:39
sean-k-mooneyi was ment to loop back to those after the cve16:40
JayFI figured :). No real rush just sometime in the next few days would be nice16:40
JayFI'm pretty crushed right now too and wouldn't be able to do anything immediately with the feedback, but I know the queue is long so wanted to take my number ;)16:41
sean-k-mooneyJayF: does the ironic patch depend on the nova one and is that tested in ci16:42
sean-k-mooneyi.e. can we use that to demonstrate thsi end to end16:42
sean-k-mooneywe do have results form https://zuul.opendev.org/t/openstack/build/0c7147a1aea541eb88ae387cb5487fe0 also16:43
sean-k-mooneywhich i guess we can reference im just not sure if the metadta will be visable in the ironic logs but i woudl hope we can see it properly there16:43
JayFsean-k-mooney: I tested it manually in devstack. automatic_lessee defaults to false in Ironic so it won't show up in CI until we explicitly test it; and I'm not going to add to the chain until I get some directional feedback (i.e. this is good if tested)16:43
JayFsean-k-mooney: mainly just trying to avoid a thing where I write 5 patches across 5 repos and get feedback to change a single word that takes an hour because of the stacking :P 16:44
JayFI knew I shoulda done a quick+dirty demo video; CID did that for his recent Ironic API change and it was WONDERFUL as a reviewer to see16:45
sean-k-mooneyack we can likely turn it on in that job in a follwo up testing patch16:45
sean-k-mooneyby the way 16:45
sean-k-mooneyJul 25 20:34:42.508653 np0038062841 nova-compute[106292]: ERROR nova.network.neutron [req-a7169636-31a7-4d11-9017-a6865cd16b59 req-102a3eac-094a-42f8-a114-8ac7a841a33c service nova] [instance: 929bb573-a06a-4fa7-a77a-c643bd9655ce] The vnic_type of the bound port 88d554aa-8c7a-46ac-b54b-efeac135c643 has been changed in neutron from "normal" to "baremetal". Changing vnic_type of16:45
sean-k-mooneya bound port is not supported by Nova. To avoid breaking the connectivity of the instance please change the port vnic_type back to "normal".16:45
sean-k-mooneythat is a sideffect of ironic doing somethign that is not allowed that related to a cve previously16:46
JayFCan you document that in a bug somewhere please?16:47
sean-k-mooneyin this speicic case its not problematic form a secuirty point of view but is a side effect of the exisitng tech debt16:47
sean-k-mooneysure my guess is the job is not configure properly to set the tempest config option for the vnic_type to baremental 16:47
sean-k-mooneyspeicicaly https://github.com/openstack/tempest/blob/master/tempest/config.py#L784-L79116:48
sean-k-mooneyif you need a prot type other the normal nova only supprot that by passing a precreated port as part of the server create request16:52
sean-k-mooneyso ironic just like sriov ports required tempest to be configued to use the relevent vnic type in the job16:53
sean-k-mooneyJayF: https://bugs.launchpad.net/ironic/+bug/2076265 os for the issue in the job config althoguh i think the larger issue of nova/ironic/neutron interaction is really a seprate problem17:08
JayFsean-k-mooney: I'd suggest sending an email to the mailing list proposing a joint PTG session then. It's not a topic I can address well in the moment as networking is far from my area of expertise in Ironic and I'd need to get more context17:09
elodillesstephenfin: i guess those are mainly the .gitreview patches. i'll rather check if we could merge them now. (i also don't think that we will get (many) backports to these projects, but at least the .gitreview file should be correct)17:10
*** bauzas_ is now known as bauzas18:15
*** bauzas_ is now known as bauzas18:26
*** bauzas_ is now known as bauzas19:36
*** ministry is now known as __ministry20:06

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