Earlier  
Posted Nick Remark
#openstack-nova - 2024-05-28
11:35:40 sean-k-mooney we are only using keyston auth in two places
11:35:48 sean-k-mooney and im not entirly sure we need to remove t
11:36:25 sean-k-mooney Uggla is currently adding new usage of the sdk in there manilla series
11:36:39 sean-k-mooney so we shoudl look at how they are intialising the sdk connection ectra
11:38:23 wncslln already have some patch with these changes on manilla?
11:38:31 sean-k-mooney https://review.opendev.org/c/openstack/nova/+/831194/46/nova/share/manila.py
11:39:00 sean-k-mooney so i have not reviewd that yet but that is where they are building the abstraction to talk to manilla using the sdk
11:39:13 zigo frickler: Thanks! :_
11:39:15 sean-k-mooney and they should be loading auth parmters from the config in that patch i belive
11:39:57 sean-k-mooney wncslln: they are using utils.get_sdk_adapter('shared-file-system', check_service=True) https://review.opendev.org/c/openstack/nova/+/831194/46/nova/share/manila.py#41
11:41:02 sean-k-mooney wncslln: which if i recall correctly replaces _get_session and https://github.com/openstack/nova/blob/master/nova/network/neutron.py#L261-L268 and https://github.com/openstack/nova/blob/master/nova/network/neutron.py#L70-L88
11:41:48 sean-k-mooney once we have converted to callign utils.get_sdk_adapter some of the auth exceptions will change form keystoneauth exception to sdk ones i think
11:42:42 sean-k-mooney so we will still need to update tests for that change but that should be fine
11:42:51 sean-k-mooney https://github.com/openstack/nova/blob/master/nova/utils.py#L969-L995 is the defintion of get_sdk_adapter
11:43:40 wncslln in a first moment, I'll try to change to get_sdk_adapter and see what comes, after that I push the WIP
11:43:46 wncslln what you think?
11:43:54 sean-k-mooney sure
11:43:58 sean-k-mooney sound good
12:49:55 zigo "Error starting thread.: nova.exception.InvalidCPUInfo: Configured CPU model: EPYC and CPU Flags [] ar not compatible with host CPU. Please correct your config and try again. Unacceptable CPU info: CPU doesn't have compatibility."
12:49:55 zigo I'm having a hard time setting a CPU model on computes with 2x "AMD EPYC 9734 112-Core Processor" in bookworm (worked with the EPYC-Rome under bullseye). Is this a known issue ? I'm getting:
12:58:01 zigo Even Opteron_G1-v1 doesn't work ... :/
13:02:44 sean-k-mooney so this depends on your libvirt version and the models it knwo about to some degree at least
13:02:54 sean-k-mooney if you do virsh capabilities
13:03:00 sean-k-mooney spelled correctly of couse
13:03:14 sean-k-mooney then it will print the closet model too the host cpu in the output
13:03:14 zigo <model>EPYC-Milan</model>
13:03:14 zigo <arch>x86_64</arch>
13:03:14 zigo <cpu>
13:03:14 zigo It tells:
13:03:15 zigo <vendor>AMD</vendor>
13:03:17 zigo <microcode version='178258451'/>
13:03:19 zigo <signature family='25' model='160' stepping='2'/>
13:03:38 sean-k-mooney ack so EPYC-Milan is what would be used if you use the default which is host_model
13:04:24 zigo So you'd recommend to use host-model ?
13:05:45 sean-k-mooney well that is the default if you dont set anything (indirectly but its effectivly the same)
13:06:15 sean-k-mooney the installer/package should not be setting a model by default
13:06:51 zigo By default, I'm setting host-passthrough, then things can be overridden on cluster level or per compute level.
15:39:27 sean-k-mooney zigo: i would not ship with host-passthrough, as a default in an installer or package. it will increase performance but severly limit livemigration
15:39:59 zigo sean-k-mooney: Yeah, I may switch to host-model as default.
15:41:07 sean-k-mooney i personlly use host-passthrough but i dont need live migration in my home setup. for a disto default just not settting naything or host-model will work better for more peopel
15:41:23 sean-k-mooney host-passthrough is good if you have effectivly all the same generation of hardware
15:47:06 bauzas reminder : nova meeting in 13 mins here
16:00:17 opendevreview Maxime Lubin proposed openstack/nova-specs master: USB over IP https://review.opendev.org/c/openstack/nova-specs/+/920687
16:00:36 opendevmeet The meeting name has been set to 'nova'
16:00:36 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:36 opendevmeet Meeting started Tue May 28 16:00:36 2024 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:36 bauzas #startmeeting nova
16:00:46 sean-k-mooney o/
16:00:47 bauzas welcome folks
16:00:52 fwiesel \o
16:00:53 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:04 bauzas I missed you last week :)
16:01:16 sean-k-mooney aw
16:01:26 sean-k-mooney it was quiter without you
16:01:50 bauzas :)
16:01:51 sean-k-mooney im not sure if we have folks form the us or not today
16:01:59 bauzas awaiting a few people before starting
16:02:02 dansmith o/
16:02:17 elodilles o/
16:02:28 bauzas okay, let's start
16:02:34 bauzas shall be quick
16:02:42 bauzas #topic Bugs (stuck/critical)
16:02:47 bauzas #info No Critical bug
16:02:51 gibi o/
16:02:52 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:03:07 bauzas I can try to dent at some new bugs next week
16:03:24 bauzas apart from that, anything to discuss about bugs ?
16:04:01 gibi I saw https://bugs.launchpad.net/nova/+bug/2061701 happening in my Antelope env
16:04:13 gibi it is strange it really happen only once
16:04:32 bauzas huh
16:04:58 gibi I will try to dig into it a bit later this week
16:05:13 bauzas okay
16:05:15 gibi But if it rings a bell for someone then ping me
16:05:33 bauzas okay
16:06:15 bauzas moving on ?
16:06:23 elodilles gibi: i remember some discussion about this will hit us in the future... but nothing more o:)
16:06:33 elodilles maybe future is now :)
16:07:11 bauzas lol
16:07:23 bauzas #topic Gate status
16:07:24 sean-k-mooney that bug would imply someone is using config_drive with vfat?
16:07:30 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:07:36 bauzas #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:07:44 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:07:59 sean-k-mooney oh no an ephmeral disk with the encyption format set to vfat which i think is the default
16:08:00 bauzas (all greens except nova-emulation for zed )
16:08:13 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:08:20 bauzas #info Please try to provide meaningful comment when you recheck
16:08:23 bauzas voila
16:08:59 bauzas about the bug, we can continue to discuss about it on the open discussion section :)
16:09:06 bauzas #topic Release Planning
16:09:10 bauzas #link https://releases.openstack.org/dalmatian/schedule.html
16:09:23 bauzas #info nova deadlines are now there ^
16:09:31 bauzas #info Dalmatian-2 in 5 weeks
16:09:37 bauzas that's it
16:10:05 bauzas moving on
16:10:13 bauzas #topic Review priorities
16:10:19 bauzas #link https://etherpad.opendev.org/p/nova-dalmatian-status
16:10:38 bauzas you can now look at it
16:10:53 bauzas I provided all the series for all the specs that were accepted
16:11:15 bauzas we also have a few bugfixes for CI and other stuff in there

Earlier   Later