Tuesday, 2024-07-23

*** bauzas_ is now known as bauzas01:47
*** bauzas_ is now known as bauzas03:11
*** bauzas_ is now known as bauzas06:13
opendevreviewAlexander Hild proposed openstack/nova master: feat: Include "vm uuid" in baseBoard asset tag in libvirt domain xml  https://review.opendev.org/c/openstack/nova/+/92469707:29
opendevreviewAlexander Hild proposed openstack/nova master: feat: Include "vm uuid" in baseBoard asset tag in libvirt domain xml  https://review.opendev.org/c/openstack/nova/+/92469707:31
*** bauzas_ is now known as bauzas07:38
mikalsean-k-mooney: are you around? I think https://review.opendev.org/c/openstack/nova/+/922544 is ready for review but I have questions about if there needs to be a tempest test for it.08:06
sean-k-mooneymikal: im not sure how you would tempet test that spice is secure. we recently tired to do that for vnc and vcrypt and we could not come up with a reasonable way ot do that just with a tcp connection becuase vnc uses tls to encypt the vnc packate payload not the entire tcp packet payload08:39
sean-k-mooneyso you can just connect without implementing the nvc protocal at least enought to negoicate the vencrypt session08:40
sean-k-mooneyunless there is a simple way to asssert that spice is using a secure connection without implemeting a portion of the spice protocoal i think unit and perhaps functional tests are enough08:41
sean-k-mooneymikal: it might be worth considerign extending the libvirt funcitonal tests to be able to test some of the spice direct support but im not sure where in the series it makes sense to do that08:43
mikalsean-k-mooney: so, it depends on if tempest can carry additional software. Kerbside does have a simple client which can parse enough of the protocol to know if its been redirected to a secure connection or not.09:20
mikalsean-k-mooney: but then we'd have to carry extra code in tempest for that. https://github.com/shakenfist/kerbside/blob/develop/kerbside/spiceprotocol/__init__.py#L102 is approximate the right code.09:21
mikalsean-k-mooney: also, should I move this spec from the "to be determined" bit of the dalmation etherpad to the "needs review" bit, or is that someone else's job?09:29
sean-k-mooneymikal: tempest is generally not allowed to have depencies on external tools unless you are writing your own plugin09:30
sean-k-mooneythere are some things like ssh ectra but for the most part we try to keep core tempest as depency free as is reasonable09:31
mikalsean-k-mooney: yeah, that's going to make any meaningful testing pretty hard to do.09:31
sean-k-mooneymikal: again it would be totally fine to depend on kerbside in a kerbside tempest plugin09:31
mikalsean-k-mooney: I'm happy enough to take a swing at writing such a plugin, but I'd like to see some more traction on the patch series and implement more of the changes requested (extra specs, new API flow) before pivoting to that.09:32
sean-k-mooneyand that can be in the kerbside repo or in a seperate one. if we want to do real end ot end testing i would suggest creating both a devstack adn tempest plugin which we can enable in a upstream job in the future09:33
sean-k-mooneyya i personally woudl love to see end ot end testing but im ok with it happenign after the feature is completed09:33
mikalI'd need someone to explain more to me what a tempest plugin in a separate repo gains as compared to just doing end to end CI with github actions in the kerbside project. I've never done much with tempest.09:33
sean-k-mooneyi think unit and functional tests woudl be enouch for now09:33
mikalWell, I'm a bit worried about only having like three or four weeks to get all this landed at the moment.09:34
sean-k-mooneyyep understandable09:34
mikalThe patches have unit tests already (except for the new bits).09:34
mikalI'm not particularly asking for special treatment, but there is only so much time before the deadline and I don't see a lot of value in writing lots of tempest stuff before the actual code is complete.09:35
mikalsean-k-mooney: so should I move the heading in the etherpad?09:45
sean-k-mooneysorry which etherpad?10:00
sean-k-mooneymikal: was distracted downstream10:00
mikalsean-k-mooney: no worries. The dalmatian etherpad (https://etherpad.opendev.org/p/nova-dalmatian-status) lists the SPICE stuff under "to be determined" not "needs code review". Should I just change that, or is it done by a designated person?10:31
sean-k-mooneymikal: oh ya you can move it to needs core review since its approved and you have code not in WIP state10:40
mikalsean-k-mooney: thanks done. I'm hesitant to un-WIP the next few patches because I'll have to redo CI on them, but I guess I'll do that too.10:52
opendevreviewMichael Still proposed openstack/nova master: libvirt: Add config option to require secure SPICE.  https://review.opendev.org/c/openstack/nova/+/92254410:54
opendevreviewMichael Still proposed openstack/nova master: libvirt: allow concurrent access to SPICE consoles.  https://review.opendev.org/c/openstack/nova/+/92254610:54
opendevreviewMichael Still proposed openstack/nova master: WIP: libvirt: Add guest devices to support SPICE USB.  https://review.opendev.org/c/openstack/nova/+/92254710:54
opendevreviewMichael Still proposed openstack/nova master: WIP: libvirt: Optionally enable SPICE debug logging.  https://review.opendev.org/c/openstack/nova/+/92254810:54
opendevreviewMichael Still proposed openstack/nova master: WIP: libvirt: Optionally support sound when using SPICE.  https://review.opendev.org/c/openstack/nova/+/92254910:54
opendevreviewAlexander Hild proposed openstack/nova master: feat: Include "vm uuid" in baseBoard asset tag in libvirt domain xml  https://review.opendev.org/c/openstack/nova/+/92471710:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for assisted volume snapshots APIs  https://review.opendev.org/c/openstack/nova/+/92458811:02
opendevreviewAlexander Hild proposed openstack/nova master: feat: Include "vm uuid" in baseBoard asset tag in libvirt xml  https://review.opendev.org/c/openstack/nova/+/92472011:05
opendevreviewStephen Finucane proposed openstack/nova master: api: Fix typo  https://review.opendev.org/c/openstack/nova/+/92472211:06
opendevreviewAlexander Hild proposed openstack/nova master: feat: "vm uuid" in baseBoard asset tag  https://review.opendev.org/c/openstack/nova/+/92472311:08
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for port interface APIs  https://review.opendev.org/c/openstack/nova/+/92458911:10
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for availability zone APIs  https://review.opendev.org/c/openstack/nova/+/92459011:11
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for bare metal node APIs  https://review.opendev.org/c/openstack/nova/+/92459111:12
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for console auth token APIs  https://review.opendev.org/c/openstack/nova/+/92459211:12
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for flavor access API  https://review.opendev.org/c/openstack/nova/+/92459311:12
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for flavor extra specs APIs  https://review.opendev.org/c/openstack/nova/+/92459411:12
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for flavors APIs  https://review.opendev.org/c/openstack/nova/+/92459511:12
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for floating IP pool APIs  https://review.opendev.org/c/openstack/nova/+/92459611:12
opendevreviewStephen Finucane proposed openstack/nova master: docs: Add contributor docs for response body validation  https://review.opendev.org/c/openstack/nova/+/92459711:12
*** chuanm9 is now known as chuanm12:16
*** iurygregory__ is now known as iurygregory12:17
elodilles_ooobauzas_: fyi, i'm off this week, so i won't participate on today's meeting13:03
bauzas_elodilles_ooo: ack thanks13:04
bauzas_have a good rest13:04
*** bauzas_ is now known as bauzas13:08
sean-k-mooneyelodilles_ooo: in that case please ignore irc and email until your pto is over :) you deserve a break13:13
opendevreviewJulien Le Jeune proposed openstack/nova master: Fix test_vmdk_bad_descriptor_mem_limit and test_vmdk_bad_descriptor_mem_limit_stream_optimized  https://review.opendev.org/c/openstack/nova/+/92414813:14
opendevreviewsean mooney proposed openstack/nova master: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473114:01
jlejeunesean-k-mooney: hello, what du you mean by your remark on my proposal in https://review.opendev.org/c/openstack/nova/+/924148 ? 14:01
opendevreviewsean mooney proposed openstack/nova stable/2024.1: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473214:01
opendevreviewsean mooney proposed openstack/nova stable/2023.2: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473314:02
opendevreviewsean mooney proposed openstack/nova stable/2023.1: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473414:03
opendevreviewsean mooney proposed openstack/nova stable/2024.1: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473214:04
opendevreviewsean mooney proposed openstack/nova stable/2023.2: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473314:05
opendevreviewsean mooney proposed openstack/nova stable/2023.1: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473414:05
sean-k-mooneyjlejeune: i woudl prefer not to try and do the convert and catch the exepction and instead check via the help text if qemu image is  present and supprots vmdk14:06
jlejeunehm ok, so a check with --help option before running the qemu-img command, just to verify that qemu(img binary is present or not, right ?14:10
sean-k-mooneyjlejeune: basically i dont want to do any of the extra setup in that function if its not installed and does not supprot the format14:10
dansmithpersonally I'd just go for consistency with the one above (which the current version pretty much does) and not worry about it as much since this is all moving to oslo14:11
dansmithI'd also say that I think a dependency on qemu-img being in path and available for tests is very reasonable14:12
dansmith...for anything in nova for sure14:12
dansmithand definitely for oslo.utils, since it has a bunch of tests for qemu-img info already14:12
jlejeunedansmith: that's was my first proposal, do the same as other tests and waiting for a global move in oslo14:12
jlejeune:/14:12
dansmithjlejeune: yep, that's fine with me fwiw.. I don't think we need to probe --help, but maybe sean-k-mooney can explain more14:13
sean-k-mooneyour downsstream version dont have some format compiled in and as you are aware many disues have an unsafe qemu image so i didnt want to run it even if its just on our local system14:14
sean-k-mooneywhat proaposed is fine i just wanted to aovid calllign convert/create ectra if we coudl14:14
dansmithchanging FileNotFound to Exception (as the previous one you pointed to does) will catch both cases right?14:15
sean-k-mooneyyep and i dont think we want to differenciate14:15
sean-k-mooneyill admign because of the other things i just pushed i only quickly skimmed the patch14:16
sean-k-mooneyso i might have missed somethign14:16
dansmithyeah, so I think just using bare exception like the case above makes the most sense, jlejeune bauzas probably just didn't realize (as mentioned by the comment above) that it covers format issues and missing file issues14:17
jlejeunedansmith: totally agree, that was my opinion at first14:18
bauzasyeah I missed the first catch14:19
bauzaswhat I explained is that I prefer to catch specific exceptions mostly14:20
bauzasbut we have some exceptions in code where we bare-catch14:20
bauzashere, sean-k-mooney is just pointing out an already existing pattern, so I'm cool with it14:20
bauzassorry if that created some misunderstanding14:20
dansmithyep, honestly we should raise on FileNotFound and call qemu-img a requirement, IMHO, and skip on anything else, but this code shouldn't be staying in nova so let's just do the consistent thing for now14:21
jlejeunedansmith: ok, so let's go back on my patchset1 :)14:21
bauzasagreed with dansmith here14:21
bauzaskeep consistency for now, but I'd appreciate some further rework on that whole crazy module :)14:22
jlejeune:)14:22
opendevreviewJulien Le Jeune proposed openstack/nova master: Fix test_vmdk_bad_descriptor_mem_limit and test_vmdk_bad_descriptor_mem_limit_stream_optimized  https://review.opendev.org/c/openstack/nova/+/92414814:27
sean-k-mooneyjlejeune: we have some thing in ci that we dont want this to conflict with so we will likely loop back to your review tomorrow or later today14:29
jlejeunesean-k-mooney: no problem14:31
dansmithsean-k-mooney: ++14:31
bauzassean-k-mooney: about that, I missed some comment, but could you please rebase the stable patches by adding [stable-only] tag so the order wouldn't be important for merging ?14:31
dansmiththat's not necessary, IMHO14:32
dansmiththey're up, we can land them in normal order now14:32
sean-k-mooneybauzas: i spoke to gibi about that and came to the same conlcution14:32
sean-k-mooneywe dont need to do that in this case14:32
dansmiththey just need to be posted so we have URLs for the advisory, but no need to force fast merge them or anything14:32
bauzaswell, sure14:32
sean-k-mooneyi also want a full set of check results so dont want to promot to gate directly14:33
bauzasI'm saying that because our SLURP branches could merge before the Bobcat one14:33
sean-k-mooneybauzas: that techncially breaking policy14:33
bauzasbut we can proceed by order, I'm fine14:33
sean-k-mooneywe could but they are equally supported while instable14:33
sean-k-mooneywe shoudl not priorities slurps over supported non slurps14:34
bauzasit was just a pragmatic question in terms of merging14:34
bauzasbut I'm cool14:34
sean-k-mooneywith that said i have promoated zuul to its own monitor which i will be watching until thsee land :)14:35
bauzas++14:35
fricklersean-k-mooney that might be a night shift ;-/14:38
fricklerdepending on the state of the gate I would still promote them to the head of gate if needed. also ping me if re-gates are needed due to unrelated failures14:39
dansmithwe should at least wait until we see a clean run in check, but yeah, thanks14:40
frickleryes, I won't submit them to gate before that14:40
sean-k-mooneyfrickler: ya we can consider that once the iniall run is complete. at least this time its one commit per branch14:48
sean-k-mooneyawsome post failure in one of the jobs....14:56
sean-k-mooneyand its related.14:56
sean-k-mooneywell i know what im doing for the next little while14:56
sean-k-mooneyhttps://4b125a6587520ffd7605-3e126156a22dab1f4ba4bdb0e9add880.ssl.cf2.rackcdn.com/924731/1/check/nova-live-migration/a83a99e/testr_results.html14:56
dansmithoye14:57
dansmithsean-k-mooney: thanks for doing that, I gotta run in a sec, but I'll be back later14:57
dansmithsean-k-mooney: in glance we found some tempest jobs were uploading qcows as AMI because AMI is the first format in the disk_image_formats list, so that could be related14:58
sean-k-mooneymaybe btu theses are migration test failrues14:58
dansmithsean-k-mooney: https://review.opendev.org/c/openstack/glance/+/92332114:58
sean-k-mooneybut ya ill check if that job has that fixed or not14:59
dansmithsean-k-mooney: yeah I know14:59
dansmithjust saying, something to look for14:59
sean-k-mooneyi think this is the job we use uec images in so it proably related14:59
dansmithahh right14:59
sean-k-mooneyif thats all it is then we can fix the ci without respining the patch14:59
sean-k-mooneywhic would be good14:59
sean-k-mooneylets see if it passes the same test in the hybrid plug job 15:00
sean-k-mooneysince that is using qcow15:00
sean-k-mooneyoh yep it did https://zuul.opendev.org/t/openstack/build/be52199567724f90a6017b7a33fd0e3b15:00
sean-k-mooneyso ya this looks liek a job config issue not a patch issue15:00
bauzasguys, we'll have a nova meeting15:06
bauzasbut I don't want to conflict with the effort here15:06
bauzasdansmith: sean-k-mooney: are you okay if we run the meeting for a short period of time, say 15 mins 15:07
sean-k-mooneyits fine15:07
sean-k-mooneywe likely wont need to cordiate much15:07
sean-k-mooneyso run it as normal15:07
bauzasokay, anyway I'll try to make it quick15:07
bauzasreminder : nova meeting in ~ 1 hour here15:08
opendevreviewsean mooney proposed openstack/nova master: update nova-live-migration to use corrrect disk-formats  https://review.opendev.org/c/openstack/nova/+/92474615:14
opendevreviewMerged openstack/nova master: conf: Add '[api] response_validation' option  https://review.opendev.org/c/openstack/nova/+/91574015:16
*** bauzas_ is now known as bauzas15:41
sbauzasorry folks, intermittent problems with my internet15:46
*** sbauza is now known as bauzas__15:46
bauzas__for the moment, I'll stick with bauzas__15:47
bauzas__can someone ping me please in order to doublecheck whether you can hear me ?15:47
sean-k-mooneybauzas__: nope sorry cant do that :P15:47
bauzas__okay cool15:47
bauzas__fucking French local fiber operator15:48
* bauzas__ raises fist with rage to XPFibre15:48
gibisean-k-mooney: re live-migration post failure, I see that the the live-migraton job passed on 2023.2 and 2023.1 on the backports15:48
sean-k-mooneygibi: ya i think https://review.opendev.org/c/openstack/nova/+/924746 will fix it on master15:48
sean-k-mooneyit also passed in the hybrid plug job15:48
sean-k-mooneywhich uses the same storage but qcow images15:49
gibifingres crossed15:49
sean-k-mooneythat just completed devstack so we will know one way or another soon15:49
sean-k-mooneyif it fails ill update it with the other possibel option i need to set before the jobs completes15:49
gibiOK15:50
sean-k-mooneyhttps://zuul.openstack.org/stream/9fb4f36837c644ae8ff100d21f8a0666?logfile=console.log so far so good15:50
*** bauzas_ is now known as bauzas15:51
bauzas__don't trust this guy, that's my znc bouncer that continues to fail ^15:51
bauzas__:)15:51
bauzas__#startmeeting nova16:00
opendevmeetMeeting started Tue Jul 23 16:00:05 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
bauzas__hey folks16:00
tkajinamo/16:00
bauzas__#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:00
* gibi lurks a bit16:00
bauzas__sorry, have unstable internet connection at home16:00
fwieselo/16:00
bauzas__let's try to make this meeting quick for a reason we'll discuss in a sec16:01
sean-k-mooneyo/16:01
bauzas__#topic Bugs (stuck/critical) 16:01
bauzas__#info One Critical bug16:01
bauzas__#link https://bugs.launchpad.net/nova/+bug/207173416:01
bauzas__#info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster16:02
bauzas__so, voila we have another CVE fix16:02
bauzas__do people want to discuss about it ?16:02
bauzas__if not, I have a question16:02
bauzas__given the problem with the image module, should we working on it this cycle ?16:04
bauzas__if so, it would be a priority16:04
sean-k-mooneythere may be more work we do to harden it but likely we will need to take a step back and do tha tnext cycle16:04
sean-k-mooneythis cycle we may do so prep work or adtopation with the moving of the code to oslo16:05
sean-k-mooneyi know dan cant attend today and he has some tought on this topic16:05
sean-k-mooneyso we can bring it up again next week16:05
bauzas__then at least we should maybe stop to merge new changes for that module16:05
bauzas__unless it's a priority16:06
bauzas__the more we accept, the more it could be difficult for the oslo usage16:06
bauzas__is dansmith around ?16:06
tkajinamare you talking about the image module in oslo or one in nova ?16:08
sean-k-mooneybauzas__: no they are away for the next while16:08
sean-k-mooneytkajinam: the one in nova16:08
bauzas__tkajinam: we want to move the module to oslo16:09
sean-k-mooneyyep so until that happens we likely shoudl stablise it16:09
sean-k-mooneywe dont wnat to have them diverge more while we are porting16:09
bauzas__if we don't have quorum for now, then let's disucss this next week16:09
sean-k-mooney+116:10
bauzas__moving on then16:10
tkajinamok then I'll try to follow the discussion before I do +2+A actual implementations16:10
bauzas__#topic Gate status 16:10
bauzas__#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:11
bauzas__#link https://etherpad.opendev.org/p/nova-ci-failures-minimal16:11
bauzas__#link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status16:11
bauzas__#link https://zuul.openstack.org/build/132eaea6e65c41a1a508163b9c1f82b2 tempest-integrated-placement FAILURE on unmaintained/zed branch16:11
bauzas__I just looked at it ^16:11
bauzas__this is just a problem when creating dbcounter16:12
bauzas__hopefully the next run won't have problems16:12
bauzas__so unless someone finds something for this job run, let's continue16:12
bauzas__#info Please look at the gate failures and file a bug report with the gate-failure tag.16:13
bauzas__#info Please try to provide meaningful comment when you recheck16:14
bauzas__anything else about the gate ?16:14
fricklerah, is that the setuptools issue? I think nova was having something similar16:14
bauzas__frickler: yeah looks to me16:14
fricklerfix should be https://review.opendev.org/c/openstack/devstack/+/924740 then, but maybe also dansmith will have some other idea16:15
bauzas__ack but this is for zed16:16
bauzas__as said, this branch is "unmaintained"16:16
bauzas__anyway, moving on16:16
bauzas__#topic Release Planning 16:17
bauzas__#link https://releases.openstack.org/dalmatian/schedule.html16:17
bauzas__#info Dalmatian-3 in 5 weeks16:17
bauzas__#info Spec approval freeze happened16:17
bauzas__#link https://blueprints.launchpad.net/nova/2024.2 16 approved blueprints16:17
bauzas__you can see all of them here ^16:18
bauzas__anything else to discuss ?16:18
bauzas__#topic Review priorities 16:18
bauzas__#link https://etherpad.opendev.org/p/nova-dalmatian-status16:18
bauzas__all of the approved blueprint series are there ^16:18
bauzas__#topic Stable Branches16:19
bauzas__elodilles is on PTO this week16:19
bauzas__so let's discuss that topic next week16:19
bauzas__#topic vmwareapi 3rd-party CI efforts Highlights 16:19
fwiesel#info No updates.16:20
bauzas__fwiesel: anything to report ?16:20
bauzas__cool16:20
bauzas__moving on then16:20
bauzas__#topic Open discussion 16:20
bauzas__I have one item16:20
bauzas__(bauzas) Aug 6, 13 and 20 nova meetings16:20
bauzas__I'll be on PTO those weeks16:20
bauzas__if someone wants to run them, cool16:20
bauzas__if not, I gonna skip those16:20
sean-k-mooneywe proably shoudl keep them but we dont need to decied that now16:22
bauzas__okay, I'll tell about that again next week16:22
bauzas__that's it for me16:22
weanewHi! I've submitted a patch  https://review.opendev.org/c/openstack/nova/+/923395 Could someone take a look at it please?16:22
bauzas__anything else people want to discuss ?16:22
bauzas__weanew: we try to avoid review requests during nova meetings16:22
sean-k-mooneythat is a pretty old bug16:22
sean-k-mooneyand im not sure its one we really want to fix16:23
sean-k-mooneyi dont have time today to review but it will depend on the perfomace impact of the fix16:24
sean-k-mooneywe proably dot want to downcall to all cells for example16:24
sean-k-mooneywith that said ill try and review it properly in the next few days16:25
sean-k-mooneyif there is nothign else i think we can close the meeting16:26
weanewThank you, I don't have quations16:26
bauzas__cool16:26
bauzas__then we can close this meeting16:27
bauzas__thanks all16:27
bauzas__#endmeeting16:27
opendevmeetMeeting ended Tue Jul 23 16:27:09 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:27
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2024/nova.2024-07-23-16.00.html16:27
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2024/nova.2024-07-23-16.00.txt16:27
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2024/nova.2024-07-23-16.00.log.html16:27
fwieselthanks a lot16:27
opendevreviewsean mooney proposed openstack/nova master: [DNM] testing nova-live-migation fix  https://review.opendev.org/c/openstack/nova/+/92476216:32
opendevreviewTakashi Kajinami proposed openstack/nova-specs master: Follow up for "libvirt: AMD SEV-ES support"  https://review.opendev.org/c/openstack/nova-specs/+/92456316:34
tkajinambauzas: Could you check the follow up of SEV-ES spec when you have time ?  https://review.opendev.org/c/openstack/nova-specs/+/92456316:38
tkajinamI left the comment in it as well as  https://review.opendev.org/c/openstack/nova-specs/+/907702 (original one)16:39
clarkbfrickler: I think the correct fix is to bump https://opendev.org/openstack/requirements/src/branch/stable/2023.1/upper-constraints.txt#L339 to package 22.0 or newer16:39
clarkband note that I expect 2023.1 is broken and not just unmaintained16:40
clarkbdue to upper contraints specifying 21.3 there16:40
sean-k-mooneyfun are there fixes in flight for that16:41
clarkbnot that I am aware of. The only thing I've seen is the patch taht disable the dbcounter which isn't really a fix16:42
clarkbhttps://github.com/pypa/setuptools/issues/4483 is the upstream issue fwiw16:42
sean-k-mooneyso we could fix this by pinning setuptools on stable until they move to unmaintainted16:45
sean-k-mooneywelll or after i guess16:45
sean-k-mooneyspecificlay 2023.1 and older16:46
clarkbno you cannot pin setuptools16:46
sean-k-mooneyno ?16:46
sean-k-mooneyi know we cant do it in requrieemnts16:46
clarkbsetuptools must be installed before your package installations occur. It is a chicken and egg problem unless you use pyproject.toml universally (which we do not)16:46
sean-k-mooneybut cant we do it explcitly in the jobs to <70.0.016:46
clarkbno16:47
sean-k-mooneyok cause im pretty sure we pinned in in the past16:47
clarkbI mean maybe you could make the ci jobs do that but it is a bad approach because you can't do that in the outside world16:47
sean-k-mooneyim aware of the chicken and egg situration16:47
clarkbits the wrong approach until you switch to pyproject.toml16:47
clarkbonce you do that you can specify what packages you need to build and install your package16:47
sean-k-mooneywell the other option is to raise the min of packaging on stable16:47
clarkbuntil then you need to assume someone is pulling latest setuptools and it will explode for them16:48
sean-k-mooneywhich we coudl do but its agaisnt stable policy to raise miniums16:48
clarkbyes this is a perfect example of where that policy should probably be bent16:48
clarkbthe software is broken as is. The fix is to change the constraints. Policy shouldn't stand in the way of that16:48
sean-k-mooneyis there a patch to do that? it would be good to get ci results and see what the fallout is16:48
clarkbI am not aware of any such patch16:49
*** bauzas_ is now known as bauzas16:56
clarkbI ended up pushing https://review.opendev.org/c/openstack/requirements/+/92476417:07
clarkbWe can see if testing works and take it from there17:08
*** bauzas_ is now known as bauzas17:26
sean-k-mooneyclarkb: sorry was on an internal call but yes that is what i was thinking of doing too17:40
opendevreviewsean mooney proposed openstack/nova master: update nova-live-migration to use corrrect disk-formats  https://review.opendev.org/c/openstack/nova/+/92474617:43
opendevreviewsean mooney proposed openstack/nova master: [DNM] testing nova-live-migation fix  https://review.opendev.org/c/openstack/nova/+/92476217:43
*** bauzas_ is now known as bauzas17:48
opendevreviewMerged openstack/os-vif master: Remove old excludes  https://review.opendev.org/c/openstack/os-vif/+/91761118:05
opendevreviewDan Smith proposed openstack/nova master: DNM: Test additional AMI exclusion  https://review.opendev.org/c/openstack/nova/+/92477518:45
dansmithsean-k-mooney: we can squash this ^ if it works18:45
dansmithmight as well start the check timer on it while we look further18:46
sean-k-mooneyack18:57
*** bauzas_ is now known as bauzas19:09
_colbyHey All. We have been runing vGPU on openstack Yoga on centos  8 just fine. We recently added a new hypervisor and went with centos9 since 8 has been moved to EOL. The node with CentOS9 seems to be acting very differently. Its creating all the resource providers (even though we specify the addresses to use in nove). Are there issues with the software versionf of libvirt in centos 9 that are causing issues?19:19
*** bauzas_ is now known as bauzas19:34
opendevreviewsean mooney proposed openstack/nova master: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473119:38
_colbyalso when we attempt to spin up a vgpu instance it does not seem to be creating any of the mediated devices. Is there a way to get this working on centos9? We plan to upgrade openstack versions soo but would like to get this hypervisor running19:57
opendevreviewsean mooney proposed openstack/nova stable/2024.1: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473220:00
opendevreviewsean mooney proposed openstack/nova stable/2024.1: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473220:03
opendevreviewsean mooney proposed openstack/nova stable/2023.2: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473320:03
opendevreviewsean mooney proposed openstack/nova stable/2023.1: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473420:05
sean-k-mooney_colby: it is possibel to use vgpus on centos 9 however nvidia chagned the feature set for some of there existign gpus in later driver version and remvoed vgpu support for some older cards20:07
sean-k-mooney_colby: that may be whaat you are encoutering but im not sure20:07
_colbywe are using A40 cardsd20:08
_colbyI did upgrade the nvidia drivers from the other hypervisors20:09
_colbyIll try reverting nvidia software version to match other hypervisors and see what happens20:17
sean-k-mooney_colby: bauzas know more about this then i do and might be able to tell you what version things changed in20:22
sean-k-mooney_colby: but they are based in france and done for today so they may be able to respond in the morning20:22
_colbyok thanks @sean-k-mooney20:28
*** bauzas_ is now known as bauzas21:20
opendevreviewMerged openstack/nova master: conf: Clarify '[api] response_validation help' text  https://review.opendev.org/c/openstack/nova/+/92450121:23
*** bauzas_ is now known as bauzas23:01
opendevreviewMerged openstack/nova master: Change force_format strategy to catch mismatches  https://review.opendev.org/c/openstack/nova/+/92473123:39

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