Thursday, 2020-04-16

*** hongbin has quit IRC00:22
*** jamesmcarthur has joined #openstack-meeting-300:27
*** hongbin has joined #openstack-meeting-300:29
*** jamesmcarthur has quit IRC00:36
*** jamesmcarthur has joined #openstack-meeting-300:58
*** jamesmcarthur has quit IRC01:26
*** jamesmcarthur has joined #openstack-meeting-301:26
*** ricolin has joined #openstack-meeting-301:32
*** jamesmcarthur has quit IRC01:32
*** jamesmcarthur has joined #openstack-meeting-302:04
*** jamesmcarthur_ has joined #openstack-meeting-302:07
*** apetrich has quit IRC02:08
*** jamesmcarthur has quit IRC02:11
*** jamesmcarthur_ has quit IRC02:13
*** artom has quit IRC02:30
*** lifeless_ is now known as liffeless02:40
*** liffeless is now known as lifeless02:40
*** jamesmcarthur has joined #openstack-meeting-302:41
*** jamesmcarthur has quit IRC02:43
*** jamesmcarthur has joined #openstack-meeting-302:44
*** hongbin has quit IRC02:50
*** jamesmcarthur_ has joined #openstack-meeting-303:02
*** jamesmcarthur has quit IRC03:05
*** psachin has joined #openstack-meeting-303:26
*** jamesmcarthur has joined #openstack-meeting-304:06
*** jamesmcarthur_ has quit IRC04:09
*** jamesmcarthur has quit IRC04:22
*** jamesmcarthur has joined #openstack-meeting-304:23
*** jamesmcarthur has quit IRC04:28
*** jamesmcarthur has joined #openstack-meeting-304:30
*** jamesmcarthur has quit IRC04:30
*** jamesmcarthur has joined #openstack-meeting-304:36
*** jamesmcarthur has quit IRC04:38
*** jamesmcarthur has joined #openstack-meeting-304:39
*** jamesmcarthur has quit IRC04:47
*** jamesmcarthur has joined #openstack-meeting-305:14
*** ralonsoh has joined #openstack-meeting-305:56
*** jamesmcarthur_ has joined #openstack-meeting-306:16
*** jamesmcarthur has quit IRC06:20
*** jamesmcarthur_ has quit IRC06:21
*** apetrich has joined #openstack-meeting-306:51
*** jamesmcarthur has joined #openstack-meeting-306:54
*** apetrich has quit IRC07:08
*** e0ne has joined #openstack-meeting-307:11
*** slaweq has joined #openstack-meeting-307:11
*** maciejjozefczyk has joined #openstack-meeting-307:13
*** e0ne has quit IRC07:13
*** apetrich has joined #openstack-meeting-307:26
*** apetrich has quit IRC07:38
*** apetrich has joined #openstack-meeting-307:42
*** e0ne has joined #openstack-meeting-307:47
*** links has joined #openstack-meeting-308:02
*** jamesmcarthur has quit IRC08:55
*** lpetrut has joined #openstack-meeting-309:56
*** liuyulong has quit IRC09:59
*** jamesmcarthur has joined #openstack-meeting-310:53
*** e0ne has quit IRC10:58
*** e0ne has joined #openstack-meeting-311:09
*** artom has joined #openstack-meeting-311:29
*** rubasov has quit IRC11:29
*** rubasov has joined #openstack-meeting-311:34
*** e0ne has quit IRC11:48
*** e0ne has joined #openstack-meeting-311:49
*** negronjl has quit IRC11:53
*** negronjl has joined #openstack-meeting-311:59
*** raildo has joined #openstack-meeting-312:01
*** psachin has quit IRC12:16
*** links has quit IRC12:45
*** links has joined #openstack-meeting-312:56
*** e0ne has quit IRC12:58
*** e0ne has joined #openstack-meeting-312:58
*** tellesnobrega has joined #openstack-meeting-313:02
*** tellesnobrega has left #openstack-meeting-313:22
*** jeremyfreudberg has joined #openstack-meeting-313:52
*** tosky has joined #openstack-meeting-313:58
jeremyfreudberg#startmeeting sahara14:00
openstackMeeting started Thu Apr 16 14:00:09 2020 UTC and is due to finish in 60 minutes.  The chair is jeremyfreudberg. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
jeremyfreudbergo/14:00
toskyo/14:01
jeremyfreudberg#topic news/updates14:02
*** openstack changes topic to "news/updates (Meeting topic: sahara)"14:02
toskypython-saharaclient is fixed (yay)14:02
jeremyfreudbergi've been working on the contrib doc goal for ussuri and looking at the sqlalchemy unit test bug14:02
tosky(and released)14:02
jeremyfreudberg#topic sqlalchemy unit test bug14:05
*** openstack changes topic to "sqlalchemy unit test bug (Meeting topic: sahara)"14:05
jeremyfreudberghttps://opendev.org/openstack/sahara/src/branch/master/sahara/db/sqlalchemy/models.py#L52214:06
jeremyfreudbergso the traceback points to this line14:06
toskythe nasty one14:06
jeremyfreudberghowever line 518 is of a very similar form, and that does not cause problems14:06
jeremyfreudbergso i am just beginning to look at what's different in the treatment of these two classes in the unit tests14:06
jeremyfreudbergsorry, that first link should be L53914:07
jeremyfreudberganyway, i have not solved it yet but am working on it at least for a couple additional minutes today14:07
toskythanks! That's complicated14:08
toskybasically we miss a session somewhere14:08
jeremyfreudbergyeah14:08
jeremyfreudberganyway, moving on14:08
jeremyfreudberg#topic contrib doc goal14:08
*** openstack changes topic to "contrib doc goal (Meeting topic: sahara)"14:08
jeremyfreudbergi think tosky and i are already in sync about this goal14:08
jeremyfreudbergbut for the logs, i will mention anyway14:08
toskyI think I added most of the comments I had in mind to the review14:08
toskyyep14:09
jeremyfreudbergwe have an initial patch for sahara14:09
jeremyfreudbergi need to do a bit more work to remove some newly-redundant files and put some of their content into the new file14:09
jeremyfreudbergand we need some patches for the other repos14:09
jeremyfreudbergbut we are in good shape and the released ussuri docs will almost definitely be in accordance with the goal14:09
jeremyfreudberg#topic open discussion14:10
*** openstack changes topic to "open discussion (Meeting topic: sahara)"14:10
jeremyfreudbergtosky do you have anything else to mention today?14:11
toskywe just may have a few sahara-image-elements new linting issues14:11
toskyI haven't checked the logs in details14:11
toskyand that's it14:11
jeremyfreudbergyeah, i think i noticed that14:11
jeremyfreudbergtosky: on the topic of images, i think sahara-buildimages-* also fails?14:13
jeremyfreudbergfor example https://review.opendev.org/#/c/717575/14:13
toskyyes, another things to check14:13
toskyslightly less urgent because it does not block the release (saharaclient and unit tests are/were)14:13
toskybut I will look into it14:13
jeremyfreudbergok, makes sense, thanks14:14
jeremyfreudbergalright, we can close it14:15
toskyI'd say yes14:16
toskythanks!14:16
jeremyfreudbergthank you!14:16
jeremyfreudberg#endmeeting14:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:16
openstackMeeting ended Thu Apr 16 14:16:15 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-16-14.00.html14:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-16-14.00.txt14:16
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-16-14.00.log.html14:16
*** jeremyfreudberg has left #openstack-meeting-314:16
*** tosky has left #openstack-meeting-314:17
*** lpetrut has quit IRC14:34
*** alex_xu has joined #openstack-meeting-315:31
*** ttx has quit IRC15:38
*** ttx has joined #openstack-meeting-315:38
*** elod has joined #openstack-meeting-315:59
gibi#startmeeting nova16:00
openstackMeeting started Thu Apr 16 16:00:11 2020 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: nova)"16:00
openstackThe meeting name has been set to 'nova'16:00
gibio/16:00
artomo/16:00
melwitto/16:00
alex_xuo/16:00
dansmitho/16:00
bauzas\o16:01
gibi#topic Last meeting16:02
*** openstack changes topic to "Last meeting (Meeting topic: nova)"16:02
gibi#link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-09-16.00.log.html16:02
gibiFeature Freeze happened last week. We finished 18 blueprints, 1 got FFE, 11 bp got deferred16:02
gibinovaclient has been released for Ussuri16:02
gibianything to mention from the last meeting?16:02
gibi#topic Release Planning16:03
*** openstack changes topic to "Release Planning (Meeting topic: nova)"16:03
gibi(will go back to bugs in after this)16:03
gibiTODOs are tracked in the etherpad #link https://etherpad.opendev.org/p/nova-ussuri-rc-potential16:03
lyarwood\o16:04
gibiWe have one feature open: #link https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+status:open16:04
gibilast week we agreed to finish it until end of this week16:04
gibigmann: where we are with this?16:04
gmannsorry forgot about meeting16:04
*** tframbo has joined #openstack-meeting-316:04
gibiI saw that things are moving but I don't see how much is still needed16:04
*** sean-k-mooney has joined #openstack-meeting-316:04
gmannall the patches need for ussuri are up, few are stuck on gate since yesterday16:05
gmannI am trying to get them merged soon16:05
gmanndoc and release patch is also up which i need to re-work for melwitt comments16:05
gmannbut that will be last one to merge16:05
gibigmann: cool. so we still has some patches to review but we don't expect new ones16:05
gmannyeah most of them are updated for review comment so will be quick to do16:06
gibilet's try to approve all the open patches until Friday EOB16:06
dansmithI've been trying to grok this whole effort this morning and I'm definitely missing something about what deployers are going to have to do here16:06
dansmithhopefully once I figure that out it'll just be some revisions to the spec (or maybe they're already covered in the docs patch, which I haven't read yet)16:07
gmanndansmith: i am trying to capture those in this doc with migration plan - https://review.opendev.org/#/c/720129/4/doc/source/configuration/policy-new-defaults.rst16:07
gibias far as I understand the feaure is turned off by default16:07
dansmithyeah, I need to read that and see if it clears things up for me16:08
gmannyeah it is off by default and we have flag to turn it on without need of overwriting the policy file16:08
dansmithgibi: well, I'm more wondering about what we're going to be requiring admins to do at some point before we can complete this migration, not so much the impact of the current ones16:08
dansmithgmann: yep, understand that16:08
melwittgmann: I added new comments to the doc patch a little while ago. need to clearly explain whether operators will need to add new keystone roles to use scope types and also explain how end users will need to know how to request scoped tokens from keystone and point to keystone docs for that16:08
gmannmelwitt: ok, i think pointed to keystone doc but i will check, i agree that is imp16:09
gibidansmith: I see, so what the admins need to do before they can upgrade to V where we remove the old compat code16:09
melwittgmann: yeah, if it is, I missed it. would like to see it very concisely and clearly stated what are the action items for operators16:10
dansmithgibi: right, because it sounds like they might have to adjust all their users' roles or something, but again I don't fully grok it16:10
gmannmelwitt: sure, I will check the comments.16:10
dansmithgibi: and since more people are skipping releases these days,16:10
dansmithwe need to make sure we're not expecting them to have to do somethign where they have to turn the cloud off, migrate a bunch of users, and then turn it back on16:10
gibidansmith: worst case we cannot remove the compat code in V16:11
dansmithor worse, some problem where they do that and it affects a user in another service because they have to for nova, or something16:11
dansmithgibi: well, worst case we do all this and then never remove it,16:11
gmannwe are keeping compat code till W. for 2 cycle as this is big change for migration16:11
dansmithand then there's two ways, two sets of docs, and confusion :)16:11
gibidansmith: like notifications :)16:11
dansmithgibi: yep16:12
gibiit is 95% merged so merging the last 5% does not change much for us now16:12
gibibut I agree that we need a comprehensive doc16:12
gibiif it turns out that it is hard to migrate to the new policies then we have to figure out a way to help16:13
gibibut I think not merging the last 5% does not help much with that16:14
dansmithI'm not arguing against merging it,16:14
gmanni think at some point keystone is also going to remove the support of old role in their policy.16:14
dansmithI'm just saying I'm *personally* missing context here, and I hope I'm in the minority, and we need to make sure we've got our attack plan well thought-out16:15
dansmithpersonally missing the big picture and the end game, I mean16:15
gibiOK lets work on those attack plans together if it turns out something is missing16:16
gibican we move on?16:16
dansmithsurely16:16
gibicool16:16
gibiNext week (Apr 23) we have to cut RC116:16
gibiplease tag any RC critical bug with ussuri-rc-potential tag in launchpad16:16
gibibauzas volunteered to write the release notes prelude. It is due before RC116:16
gibiI will propose an patch with an RPC alias for Ussuri16:17
gibi             Do we want to make a major compute RPC version bump?16:17
bauzasthanks for the reminder16:17
bauzasgibi: we generally made such bumps, nope ?16:17
bauzas#link https://wiki.openstack.org/wiki/Nova/ReleaseChecklist16:18
gibibauzas: it was a loong time when we bumped to 5.x in compute RPC16:18
bauzasI know16:18
melwittthere's a patch proposed already for rpc alias fyi https://review.opendev.org/71931516:18
bauzasI only remember the old ages16:18
gibihttps://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L39216:18
sean-k-mooneygibi: as an fyi ill try and rebase https://review.opendev.org/#/c/706276/ today and after rc1 ill create a similar patch to updated the implemented specs for ussuri16:18
sean-k-mooneywe forgot to do it last cycle.16:19
gibimelwitt: thanks. I did not notice that.16:19
dansmithgibi: an rpc bump at this point would likely be difficult16:19
dansmithwe need to plan that a little further in advance, IMHO16:19
gibidansmith: OK then this answers my question.16:19
gibisean-k-mooney: thanks16:20
gibi#info we won't bump compute RPC to 6.0 in Ussuri16:21
gibidansmith: for the future, how much time would need to do such bump?16:21
artomAlso, and it sucks to leak "downstream" stuff like this, but don't we have to think about what releases operators/vendors are skipping, and make sure to *not* major-bump RPC in those?16:21
dansmithartom: no16:22
sean-k-mooneywe can pin the rpc version so no16:22
dansmithgibi: depends on the delta really16:22
dansmithartom: people skipping versions can't use rpc compatibility anyway16:22
artomdansmith, so in theory we could bump to 6.0 in U, and not break OSP 16 -> 17 FFWD upgrade?16:22
artomOh right, the control plane is down anyways16:23
dansmithartom: rpc versions have no impact on an FFU16:23
dansmithand even still OSP 16 is T, so no either :)16:23
artomdansmith, yep, thanks for setting me straight16:23
gibidansmith: OK, I will add some note to the V release schedule to plan a such bump earlier, maybe around M316:24
sean-k-mooneytoo gibi question i assume we can move to 6.0 in train but likely would not want to do a major version bump after m316:24
sean-k-mooney* in Victoria16:24
gibisean-k-mooney: so it is need to be planned even eariler?16:25
dansmithgibi: I'll have to look at the current delta, but.. is there anything begging for a bump?16:26
dansmithI mean, the only reason to do it is really if we desperately need to drop something,16:26
dansmithbut if not it's just perceptual purity, which isn't a good reason16:26
bauzasfwiw https://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L372-L37916:26
bauzasdansmith: ^16:26
gibidansmith: I have to look at the delta too but I vaguely remember discussing the 6.0 bump for reasons16:26
dansmithbauzas: right, none of those are things we need to drop16:27
bauzasdansmith: I only see additive changes between 5.1 and now16:27
dansmithbauzas: that's my point.. a bunch of additions will be identical in 6.016:27
dansmithright16:27
bauzasactually, 5.1 could be debatable16:27
melwittyeah so would more be looking at how many things have notes like "remove this in the next major bump"16:27
bauzasdansmith: I agree16:27
bauzasexcept 5.1 maybe16:28
dansmithmelwitt: not really, those are often no-ops anyway16:28
dansmithmelwitt: more like thing like 5.1, but even that is just uuber minor, IMHO16:28
bauzasright16:28
melwittI guess I thought eventually would be looking to clean them up16:28
dansmithI mean things like "if <5.5, then do an extra DB lookup to reconstruct some information we're missing"16:28
bauzasnow we objectified all rpc apis, changes are mostly additive16:28
melwittoh16:28
dansmithmelwitt: right, that's what I'm saying.. just cleanups aren't worth it.. things that actually have an impact are why we need to16:28
melwittok16:29
gibiOK. I made a note to myself to double check it but let's move on16:29
bauzasmoving on ? :)16:29
bauzasheh16:29
gibianything else for the release planning before we jump back to bugs?16:29
dansmithmoving....on.16:29
gibi#topic Bugs (stuck/critical)16:30
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: nova)"16:30
gibiNo critical16:30
gibi#link 71 new untriaged bugs (-40 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New16:30
gibigood progress to eating our backlog16:30
gibibut we keep continue as RC1 is close16:30
gibiRC critical bugs are tagged with ussuri-rc-potential #link https://bugs.launchpad.net/nova/+bugs?field.tag=ussuri-rc-potential16:30
gibithere is now 1 bug on that list16:31
gibiit has a patch up and I gave review feedback16:31
gibiI'm not 100% sure it is that critical though16:31
bauzasnot RC holding16:31
bauzasi mean it's not a U regression16:32
bauzasbut I thought it was worth looking at it before we branch16:32
gibisure16:33
gibisomebody added an bug to the agenad16:33
gibihow to solve the bug ? #link https://bugs.launchpad.net/nova/+bug/1841932 Could we add compat for os:hide_hypervisor_id and reference that in docs and code?so that we can use AggregateInstanceExtraSpecsFilter and hide_hypervisor_id at the same time.16:33
openstackLaunchpad bug 1841932 in OpenStack Compute (nova) "hide_hypervisor_id extra_specs in nova flavor cannot pass AggregateInstanceExtraSpecsFilter" [Undecided,Expired]16:33
bauzasleave it for open discussion ?16:33
gibiOK, I hope the person added it to the agenda will show up until then16:34
gibiany other bug related business?16:34
sean-k-mooneyso the problem with that extra spec is we did not namespace it16:34
sean-k-mooneyso it breaks the AggregateInstanceExtraSpecsFilter16:34
gibiOK so it is not a regression at least16:35
sean-k-mooneyno16:35
gibigood16:35
gibimoving on16:35
tframboyeah ,i added the bug16:35
gibitframbo: let's discuss it a bit at the end of the meeitng16:35
gibi#topic Stable Branches16:35
*** openstack changes topic to "Stable Branches (Meeting topic: nova)"16:35
bauzasthe whole hide_hypervisor_id thing is... hacky :p16:35
tframbook16:35
gibilyarwood any news?16:36
gibiwe discussed a need for a train release last week16:36
bauzastl;dr: shhhhht, QEMU, don't tell the nvidia driver I don't have the right to use you16:36
melwittstable train and stein were recently broken bc placement started requiring python 3.6 and our func test stuff in tox.ini was pulling placement from master,16:36
melwitttrain is fixed and stein fix is en route to the gate16:37
gmann#link https://review.opendev.org/#/c/719121/16:37
gibimelwitt: thanks16:37
gmannhope it get node in gate16:37
melwittyeah there might be some gate issue, I've been discussing in -infra. might be a nova bug even. yay! (not)16:37
gibiit seems lyarwood is not here I will ping him about the stable release tomorrow16:38
lyarwoodyeah sorry ^ I've also hit a few other issues slowing things down16:38
lyarwoodwe should still be able to release before RC (iirc that was the plan)16:38
gibilyarwood: cool thanks16:39
gibi#topic Sub/related team Highlights16:39
*** openstack changes topic to "Sub/related team Highlights (Meeting topic: nova)"16:39
gibiAPI (gmann)16:39
gibianything besides the policy work?16:39
gmannno, all what we discussed earlier  .16:40
gibicool16:40
gibimoving on16:40
gibi#topic Stuck Reviews16:40
*** openstack changes topic to "Stuck Reviews (Meeting topic: nova)"16:40
gibi(bauzas) https://review.opendev.org/#/c/589085/8 (Merging virt API changes after FeatureFreeze)16:40
bauzasnothing crucial here but I think we need a consensus on things we can accept16:41
bauzastl;dr: I'm touching the virt API signature of revert_resize and resize')16:41
gibiwe need to choose between allowing the virt driver interface to change post FF and allow the same interfacechange on stable/ussuri branch later16:41
bauzasboth are internal APIs but are in use by out-of-tree drivers16:41
bauzasso for convenience (since virt APIs aren't public), we notify them16:41
bauzasthere are two options16:42
bauzas1/ we consider it's a breaking change hence not acceptable post FF16:42
bauzasand in this case, we shouldn't allow this to be backportable16:42
bauzas2/ we assume this isn't a breaking change and in this case, we also consider it as acceptable post-FF16:43
gibijust looking at the interface change patch it feels lower risk to do it now than to do it on the stable branch16:43
bauzasand the corollar being, if this punts to V, this can be backportable to U16:43
bauzasso, 1/ or 2/ ?16:43
gibi2/16:43
bauzasI thought we had disagreements on such things16:44
bauzasI won't vote on it, since I'm involved in the change16:44
melwittand there is no desire to backport this earlier than ussuri right? I see that the bug was reported a long time ago16:44
bauzas(but you get my opinion by seeing the change)16:44
bauzasmelwitt: I honestly have no energy for it16:44
bauzasor, in other words, this wouldn't be backported upstream16:45
stephenfinyeah, maybe downstream. Can't see us doing that upstream, tbh16:45
melwittok. well, the change looks simple at least. so seems low risk16:45
bauzasmelwitt: but your question remains, if we go with 2/, in theory we could accept virt API changes to be backportable down to T or whatever16:45
bauzasor we just say "no policy, it's case-by-case" and we move on16:46
gibiif I were a out of tree virt driver maintainer I would expect changes on that interface to happen more at major version than at minor version16:46
stephenfinthat's where I'm at too ^16:47
melwittyeah, agree with that16:47
gibi(for the record I'm not maintainting out of tree drivers)16:47
gibiso we agree to change the interface then do it where it is expected to change16:47
stephenfinbut, with that said, if this was a more critical issue with a move operation that affected more people, I imagine out-of-tree drivers would have to deal with it16:48
sean-k-mooneystephenfin: i dont really want use to do it downstream either16:48
bauzasstephenfin: out-of-tree driver maintainers would have to maintain compatibility with the backport, whatever the use is16:48
bauzasit's not about the use of the parameter16:48
*** ricolin has quit IRC16:48
*** e0ne has quit IRC16:49
bauzasit's just that if we backport it to Train, Stein or Rocky, then we break them16:49
bauzas(for resize and revert resize here)16:49
sean-k-mooneybauzas: unless you catch the type error and call the function again without the parmater which we have dont in the past16:49
gibidansmith: do you have a hard NO against merging the interface change now? (I'm asking you as you expressed a preference to not do it in U)16:49
sean-k-mooneythat would support out of tree driver but i dont think we shoudl have to do that16:49
*** e0ne has joined #openstack-meeting-316:49
bauzaswe can honestly defer it to V if we are able to merge it sooner than later16:49
bauzassean-k-mooney: I'm opposed to it16:50
bauzassean-k-mooney: there is one thing to notify and have a gentleman agrement16:50
bauzasthere is another thing to implement some kind of public and maintained API for them16:50
stephenfinyeah, that would imply actual support16:50
bauzasokay, so, I don't hear any disagreement on merging it post-FF if we can16:51
bauzasand if we can't, no backport to U16:51
bauzasI'm cool with both things16:51
sean-k-mooneyi know im jsut saying what we have done in the past. im pretty sure we did this recently for one of the migration specs. my preference is to defer to V16:51
sean-k-mooneywith no backport16:51
stephenfinCool. I'll take another look at that in the morning and send it through so16:51
bauzaslet's just leave a chance of this thing to be reviewed during this RC period and if we are not able to merge it, merge it in V16:52
bauzasstephenfin: the last patch needs a revision, hold your pen16:52
gibi#info give a chance to https://review.opendev.org/#/c/589085/ to merge before RC116:52
bauzasI think we're mostly on agreement, let's move on16:52
bauzasgibi: also, the consensus is "don't backport any virt API changes"16:52
bauzaswhich is a solid argument16:53
gibilet's discuss that part of the agreemet at another time.16:53
bauzasall good, thanks folks16:53
gibimoveing on16:53
gibi#topic Open discussion16:53
*** openstack changes topic to "Open discussion (Meeting topic: nova)"16:53
gibi(gibi): Virtual PTG planning. #link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014148.html16:53
gibiI need to book slots in the common schedule so we need to know how much slots we need, and what time slots we want to use.16:54
gibidoodle link is in the mail16:54
gibiand if you have any feeling about the amount of time we need the please ping me on #openstack-nova later16:54
gibitframbo: your turn16:55
gibi#link https://bugs.launchpad.net/nova/+bug/184193216:55
openstackLaunchpad bug 1841932 in OpenStack Compute (nova) "hide_hypervisor_id extra_specs in nova flavor cannot pass AggregateInstanceExtraSpecsFilter" [Undecided,Expired]16:55
bauzasI'm sad the Foundation only provided a week slot16:55
bauzasbut meh16:55
tframboMaybe we could add compat for "os:hide_hypervisor_id” like other extra specs and reference that in docs and code to solve it?16:55
sean-k-mooneytframbo: we coudl specical case for that yes for backport only16:56
bauzastframbo: can't you just use aggregates with random keys ?16:56
sean-k-mooneybut i think we shoudl be removing support for unnamespaced extra specs form the filter16:56
bauzasI'm personnally opposed to expose any single libvirt knob as an image metadata property16:57
sean-k-mooneybauzas: the image metadata is how we are ment to expose them16:57
sean-k-mooneyits why this feature originally only supported that16:57
sean-k-mooneyand not extra specs16:58
bauzassean-k-mooney: no16:58
sean-k-mooneythe extra sepcs supprot was added after16:58
bauzasyou can achieve the same thing without automatically exposing your capabilities16:58
bauzaswe have traits, we have filters that do this for you16:58
sean-k-mooneythis change how the vm is virutalsed16:58
bauzasI don't see the need to add yet another knob16:58
sean-k-mooneyso trait wont help16:59
gibiwe are running out of time16:59
bauzasthat's a scheduling problem16:59
bauzasnot a boot issue16:59
sean-k-mooneylets talk about this on #openstack-nova16:59
gibitframbo: I see that bauzas and sean-k-mooney has oppinion about the bugfix so let's talk to them on #openstack-nova16:59
bauzasyeah, agreed, let's punt this to -nova16:59
gibithanks everyone16:59
tframbook16:59
sean-k-mooneyo/17:00
gibi#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Thu Apr 16 17:00:01 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-16-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-16-16.00.txt17:00
*** sean-k-mooney has left #openstack-meeting-317:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-16-16.00.log.html17:00
*** tframbo has quit IRC17:28
*** maciejjozefczyk has quit IRC17:39
*** links has quit IRC17:44
*** diablo_rojo has joined #openstack-meeting-317:51
*** ralonsoh has quit IRC18:16
*** diablo_rojo has quit IRC18:18
*** jamesmcarthur has quit IRC18:44
*** jamesmcarthur has joined #openstack-meeting-318:44
*** e0ne has quit IRC19:04
*** jamesmcarthur has quit IRC19:29
*** jamesmcarthur has joined #openstack-meeting-319:33
*** jamesmcarthur has quit IRC19:37
*** jamesmcarthur has joined #openstack-meeting-319:38
*** jamesmcarthur has quit IRC20:14
*** jamesmcarthur has joined #openstack-meeting-320:20
*** jamesmcarthur has quit IRC20:20
*** slaweq has quit IRC21:14
*** raildo has quit IRC21:31
*** jamesmcarthur has joined #openstack-meeting-322:48
*** jamesmcarthur has quit IRC23:19

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!