*** hongbin has quit IRC | 00:22 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 00:27 | |
*** hongbin has joined #openstack-meeting-3 | 00:29 | |
*** jamesmcarthur has quit IRC | 00:36 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 00:58 | |
*** jamesmcarthur has quit IRC | 01:26 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 01:26 | |
*** ricolin has joined #openstack-meeting-3 | 01:32 | |
*** jamesmcarthur has quit IRC | 01:32 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 02:04 | |
*** jamesmcarthur_ has joined #openstack-meeting-3 | 02:07 | |
*** apetrich has quit IRC | 02:08 | |
*** jamesmcarthur has quit IRC | 02:11 | |
*** jamesmcarthur_ has quit IRC | 02:13 | |
*** artom has quit IRC | 02:30 | |
*** lifeless_ is now known as liffeless | 02:40 | |
*** liffeless is now known as lifeless | 02:40 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 02:41 | |
*** jamesmcarthur has quit IRC | 02:43 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 02:44 | |
*** hongbin has quit IRC | 02:50 | |
*** jamesmcarthur_ has joined #openstack-meeting-3 | 03:02 | |
*** jamesmcarthur has quit IRC | 03:05 | |
*** psachin has joined #openstack-meeting-3 | 03:26 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 04:06 | |
*** jamesmcarthur_ has quit IRC | 04:09 | |
*** jamesmcarthur has quit IRC | 04:22 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 04:23 | |
*** jamesmcarthur has quit IRC | 04:28 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 04:30 | |
*** jamesmcarthur has quit IRC | 04:30 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 04:36 | |
*** jamesmcarthur has quit IRC | 04:38 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 04:39 | |
*** jamesmcarthur has quit IRC | 04:47 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 05:14 | |
*** ralonsoh has joined #openstack-meeting-3 | 05:56 | |
*** jamesmcarthur_ has joined #openstack-meeting-3 | 06:16 | |
*** jamesmcarthur has quit IRC | 06:20 | |
*** jamesmcarthur_ has quit IRC | 06:21 | |
*** apetrich has joined #openstack-meeting-3 | 06:51 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 06:54 | |
*** apetrich has quit IRC | 07:08 | |
*** e0ne has joined #openstack-meeting-3 | 07:11 | |
*** slaweq has joined #openstack-meeting-3 | 07:11 | |
*** maciejjozefczyk has joined #openstack-meeting-3 | 07:13 | |
*** e0ne has quit IRC | 07:13 | |
*** apetrich has joined #openstack-meeting-3 | 07:26 | |
*** apetrich has quit IRC | 07:38 | |
*** apetrich has joined #openstack-meeting-3 | 07:42 | |
*** e0ne has joined #openstack-meeting-3 | 07:47 | |
*** links has joined #openstack-meeting-3 | 08:02 | |
*** jamesmcarthur has quit IRC | 08:55 | |
*** lpetrut has joined #openstack-meeting-3 | 09:56 | |
*** liuyulong has quit IRC | 09:59 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 10:53 | |
*** e0ne has quit IRC | 10:58 | |
*** e0ne has joined #openstack-meeting-3 | 11:09 | |
*** artom has joined #openstack-meeting-3 | 11:29 | |
*** rubasov has quit IRC | 11:29 | |
*** rubasov has joined #openstack-meeting-3 | 11:34 | |
*** e0ne has quit IRC | 11:48 | |
*** e0ne has joined #openstack-meeting-3 | 11:49 | |
*** negronjl has quit IRC | 11:53 | |
*** negronjl has joined #openstack-meeting-3 | 11:59 | |
*** raildo has joined #openstack-meeting-3 | 12:01 | |
*** psachin has quit IRC | 12:16 | |
*** links has quit IRC | 12:45 | |
*** links has joined #openstack-meeting-3 | 12:56 | |
*** e0ne has quit IRC | 12:58 | |
*** e0ne has joined #openstack-meeting-3 | 12:58 | |
*** tellesnobrega has joined #openstack-meeting-3 | 13:02 | |
*** tellesnobrega has left #openstack-meeting-3 | 13:22 | |
*** jeremyfreudberg has joined #openstack-meeting-3 | 13:52 | |
*** tosky has joined #openstack-meeting-3 | 13:58 | |
jeremyfreudberg | #startmeeting sahara | 14:00 |
---|---|---|
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
*** openstack changes topic to " (Meeting topic: sahara)" | 14:00 | |
openstack | The meeting name has been set to 'sahara' | 14:00 |
jeremyfreudberg | o/ | 14:00 |
tosky | o/ | 14:01 |
jeremyfreudberg | #topic news/updates | 14:02 |
*** openstack changes topic to "news/updates (Meeting topic: sahara)" | 14:02 | |
tosky | python-saharaclient is fixed (yay) | 14:02 |
jeremyfreudberg | i've been working on the contrib doc goal for ussuri and looking at the sqlalchemy unit test bug | 14:02 |
tosky | (and released) | 14:02 |
jeremyfreudberg | #topic sqlalchemy unit test bug | 14:05 |
*** openstack changes topic to "sqlalchemy unit test bug (Meeting topic: sahara)" | 14:05 | |
jeremyfreudberg | https://opendev.org/openstack/sahara/src/branch/master/sahara/db/sqlalchemy/models.py#L522 | 14:06 |
jeremyfreudberg | so the traceback points to this line | 14:06 |
tosky | the nasty one | 14:06 |
jeremyfreudberg | however line 518 is of a very similar form, and that does not cause problems | 14:06 |
jeremyfreudberg | so i am just beginning to look at what's different in the treatment of these two classes in the unit tests | 14:06 |
jeremyfreudberg | sorry, that first link should be L539 | 14:07 |
jeremyfreudberg | anyway, i have not solved it yet but am working on it at least for a couple additional minutes today | 14:07 |
tosky | thanks! That's complicated | 14:08 |
tosky | basically we miss a session somewhere | 14:08 |
jeremyfreudberg | yeah | 14:08 |
jeremyfreudberg | anyway, moving on | 14:08 |
jeremyfreudberg | #topic contrib doc goal | 14:08 |
*** openstack changes topic to "contrib doc goal (Meeting topic: sahara)" | 14:08 | |
jeremyfreudberg | i think tosky and i are already in sync about this goal | 14:08 |
jeremyfreudberg | but for the logs, i will mention anyway | 14:08 |
tosky | I think I added most of the comments I had in mind to the review | 14:08 |
tosky | yep | 14:09 |
jeremyfreudberg | we have an initial patch for sahara | 14:09 |
jeremyfreudberg | i need to do a bit more work to remove some newly-redundant files and put some of their content into the new file | 14:09 |
jeremyfreudberg | and we need some patches for the other repos | 14:09 |
jeremyfreudberg | but we are in good shape and the released ussuri docs will almost definitely be in accordance with the goal | 14:09 |
jeremyfreudberg | #topic open discussion | 14:10 |
*** openstack changes topic to "open discussion (Meeting topic: sahara)" | 14:10 | |
jeremyfreudberg | tosky do you have anything else to mention today? | 14:11 |
tosky | we just may have a few sahara-image-elements new linting issues | 14:11 |
tosky | I haven't checked the logs in details | 14:11 |
tosky | and that's it | 14:11 |
jeremyfreudberg | yeah, i think i noticed that | 14:11 |
jeremyfreudberg | tosky: on the topic of images, i think sahara-buildimages-* also fails? | 14:13 |
jeremyfreudberg | for example https://review.opendev.org/#/c/717575/ | 14:13 |
tosky | yes, another things to check | 14:13 |
tosky | slightly less urgent because it does not block the release (saharaclient and unit tests are/were) | 14:13 |
tosky | but I will look into it | 14:13 |
jeremyfreudberg | ok, makes sense, thanks | 14:14 |
jeremyfreudberg | alright, we can close it | 14:15 |
tosky | I'd say yes | 14:16 |
tosky | thanks! | 14:16 |
jeremyfreudberg | thank you! | 14:16 |
jeremyfreudberg | #endmeeting | 14:16 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 14:16 | |
openstack | Meeting ended Thu Apr 16 14:16:15 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:16 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-16-14.00.html | 14:16 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-16-14.00.txt | 14:16 |
openstack | Log: http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-16-14.00.log.html | 14:16 |
*** jeremyfreudberg has left #openstack-meeting-3 | 14:16 | |
*** tosky has left #openstack-meeting-3 | 14:17 | |
*** lpetrut has quit IRC | 14:34 | |
*** alex_xu has joined #openstack-meeting-3 | 15:31 | |
*** ttx has quit IRC | 15:38 | |
*** ttx has joined #openstack-meeting-3 | 15:38 | |
*** elod has joined #openstack-meeting-3 | 15:59 | |
gibi | #startmeeting nova | 16:00 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
*** openstack changes topic to " (Meeting topic: nova)" | 16:00 | |
openstack | The meeting name has been set to 'nova' | 16:00 |
gibi | o/ | 16:00 |
artom | o/ | 16:00 |
melwitt | o/ | 16:00 |
alex_xu | o/ | 16:00 |
dansmith | o/ | 16:00 |
bauzas | \o | 16:01 |
gibi | #topic Last meeting | 16: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.html | 16:02 |
gibi | Feature Freeze happened last week. We finished 18 blueprints, 1 got FFE, 11 bp got deferred | 16:02 |
gibi | novaclient has been released for Ussuri | 16:02 |
gibi | anything to mention from the last meeting? | 16:02 |
gibi | #topic Release Planning | 16:03 |
*** openstack changes topic to "Release Planning (Meeting topic: nova)" | 16:03 | |
gibi | (will go back to bugs in after this) | 16:03 |
gibi | TODOs are tracked in the etherpad #link https://etherpad.opendev.org/p/nova-ussuri-rc-potential | 16:03 |
lyarwood | \o | 16:04 |
gibi | We have one feature open: #link https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+status:open | 16:04 |
gibi | last week we agreed to finish it until end of this week | 16:04 |
gibi | gmann: where we are with this? | 16:04 |
gmann | sorry forgot about meeting | 16:04 |
*** tframbo has joined #openstack-meeting-3 | 16:04 | |
gibi | I saw that things are moving but I don't see how much is still needed | 16:04 |
*** sean-k-mooney has joined #openstack-meeting-3 | 16:04 | |
gmann | all the patches need for ussuri are up, few are stuck on gate since yesterday | 16:05 |
gmann | I am trying to get them merged soon | 16:05 |
gmann | doc and release patch is also up which i need to re-work for melwitt comments | 16:05 |
gmann | but that will be last one to merge | 16:05 |
gibi | gmann: cool. so we still has some patches to review but we don't expect new ones | 16:05 |
gmann | yeah most of them are updated for review comment so will be quick to do | 16:06 |
gibi | let's try to approve all the open patches until Friday EOB | 16:06 |
dansmith | I'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 here | 16:06 |
dansmith | hopefully 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 |
gmann | dansmith: 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.rst | 16:07 |
gibi | as far as I understand the feaure is turned off by default | 16:07 |
dansmith | yeah, I need to read that and see if it clears things up for me | 16:08 |
gmann | yeah it is off by default and we have flag to turn it on without need of overwriting the policy file | 16:08 |
dansmith | gibi: 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 ones | 16:08 |
dansmith | gmann: yep, understand that | 16:08 |
melwitt | gmann: 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 that | 16:08 |
gmann | melwitt: ok, i think pointed to keystone doc but i will check, i agree that is imp | 16:09 |
gibi | dansmith: I see, so what the admins need to do before they can upgrade to V where we remove the old compat code | 16:09 |
melwitt | gmann: yeah, if it is, I missed it. would like to see it very concisely and clearly stated what are the action items for operators | 16:10 |
dansmith | gibi: right, because it sounds like they might have to adjust all their users' roles or something, but again I don't fully grok it | 16:10 |
gmann | melwitt: sure, I will check the comments. | 16:10 |
dansmith | gibi: and since more people are skipping releases these days, | 16:10 |
dansmith | we 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 on | 16:10 |
gibi | dansmith: worst case we cannot remove the compat code in V | 16:11 |
dansmith | or worse, some problem where they do that and it affects a user in another service because they have to for nova, or something | 16:11 |
dansmith | gibi: well, worst case we do all this and then never remove it, | 16:11 |
gmann | we are keeping compat code till W. for 2 cycle as this is big change for migration | 16:11 |
dansmith | and then there's two ways, two sets of docs, and confusion :) | 16:11 |
gibi | dansmith: like notifications :) | 16:11 |
dansmith | gibi: yep | 16:12 |
gibi | it is 95% merged so merging the last 5% does not change much for us now | 16:12 |
gibi | but I agree that we need a comprehensive doc | 16:12 |
gibi | if it turns out that it is hard to migrate to the new policies then we have to figure out a way to help | 16:13 |
gibi | but I think not merging the last 5% does not help much with that | 16:14 |
dansmith | I'm not arguing against merging it, | 16:14 |
gmann | i think at some point keystone is also going to remove the support of old role in their policy. | 16:14 |
dansmith | I'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-out | 16:15 |
dansmith | personally missing the big picture and the end game, I mean | 16:15 |
gibi | OK lets work on those attack plans together if it turns out something is missing | 16:16 |
gibi | can we move on? | 16:16 |
dansmith | surely | 16:16 |
gibi | cool | 16:16 |
gibi | Next week (Apr 23) we have to cut RC1 | 16:16 |
gibi | please tag any RC critical bug with ussuri-rc-potential tag in launchpad | 16:16 |
gibi | bauzas volunteered to write the release notes prelude. It is due before RC1 | 16:16 |
gibi | I will propose an patch with an RPC alias for Ussuri | 16:17 |
gibi | Do we want to make a major compute RPC version bump? | 16:17 |
bauzas | thanks for the reminder | 16:17 |
bauzas | gibi: we generally made such bumps, nope ? | 16:17 |
bauzas | #link https://wiki.openstack.org/wiki/Nova/ReleaseChecklist | 16:18 |
gibi | bauzas: it was a loong time when we bumped to 5.x in compute RPC | 16:18 |
bauzas | I know | 16:18 |
melwitt | there's a patch proposed already for rpc alias fyi https://review.opendev.org/719315 | 16:18 |
bauzas | I only remember the old ages | 16:18 |
gibi | https://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L392 | 16:18 |
sean-k-mooney | gibi: 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 ussuri | 16:18 |
sean-k-mooney | we forgot to do it last cycle. | 16:19 |
gibi | melwitt: thanks. I did not notice that. | 16:19 |
dansmith | gibi: an rpc bump at this point would likely be difficult | 16:19 |
dansmith | we need to plan that a little further in advance, IMHO | 16:19 |
gibi | dansmith: OK then this answers my question. | 16:19 |
gibi | sean-k-mooney: thanks | 16:20 |
gibi | #info we won't bump compute RPC to 6.0 in Ussuri | 16:21 |
gibi | dansmith: for the future, how much time would need to do such bump? | 16:21 |
artom | Also, 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 |
dansmith | artom: no | 16:22 |
sean-k-mooney | we can pin the rpc version so no | 16:22 |
dansmith | gibi: depends on the delta really | 16:22 |
dansmith | artom: people skipping versions can't use rpc compatibility anyway | 16:22 |
artom | dansmith, so in theory we could bump to 6.0 in U, and not break OSP 16 -> 17 FFWD upgrade? | 16:22 |
artom | Oh right, the control plane is down anyways | 16:23 |
dansmith | artom: rpc versions have no impact on an FFU | 16:23 |
dansmith | and even still OSP 16 is T, so no either :) | 16:23 |
artom | dansmith, yep, thanks for setting me straight | 16:23 |
gibi | dansmith: OK, I will add some note to the V release schedule to plan a such bump earlier, maybe around M3 | 16:24 |
sean-k-mooney | too gibi question i assume we can move to 6.0 in train but likely would not want to do a major version bump after m3 | 16:24 |
sean-k-mooney | * in Victoria | 16:24 |
gibi | sean-k-mooney: so it is need to be planned even eariler? | 16:25 |
dansmith | gibi: I'll have to look at the current delta, but.. is there anything begging for a bump? | 16:26 |
dansmith | I mean, the only reason to do it is really if we desperately need to drop something, | 16:26 |
dansmith | but if not it's just perceptual purity, which isn't a good reason | 16:26 |
bauzas | fwiw https://github.com/openstack/nova/blob/master/nova/compute/rpcapi.py#L372-L379 | 16:26 |
bauzas | dansmith: ^ | 16:26 |
gibi | dansmith: I have to look at the delta too but I vaguely remember discussing the 6.0 bump for reasons | 16:26 |
dansmith | bauzas: right, none of those are things we need to drop | 16:27 |
bauzas | dansmith: I only see additive changes between 5.1 and now | 16:27 |
dansmith | bauzas: that's my point.. a bunch of additions will be identical in 6.0 | 16:27 |
dansmith | right | 16:27 |
bauzas | actually, 5.1 could be debatable | 16:27 |
melwitt | yeah so would more be looking at how many things have notes like "remove this in the next major bump" | 16:27 |
bauzas | dansmith: I agree | 16:27 |
bauzas | except 5.1 maybe | 16:28 |
dansmith | melwitt: not really, those are often no-ops anyway | 16:28 |
dansmith | melwitt: more like thing like 5.1, but even that is just uuber minor, IMHO | 16:28 |
bauzas | right | 16:28 |
melwitt | I guess I thought eventually would be looking to clean them up | 16:28 |
dansmith | I mean things like "if <5.5, then do an extra DB lookup to reconstruct some information we're missing" | 16:28 |
bauzas | now we objectified all rpc apis, changes are mostly additive | 16:28 |
melwitt | oh | 16:28 |
dansmith | melwitt: right, that's what I'm saying.. just cleanups aren't worth it.. things that actually have an impact are why we need to | 16:28 |
melwitt | ok | 16:29 |
gibi | OK. I made a note to myself to double check it but let's move on | 16:29 |
bauzas | moving on ? :) | 16:29 |
bauzas | heh | 16:29 |
gibi | anything else for the release planning before we jump back to bugs? | 16:29 |
dansmith | moving....on. | 16:29 |
gibi | #topic Bugs (stuck/critical) | 16:30 |
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: nova)" | 16:30 | |
gibi | No critical | 16:30 |
gibi | #link 71 new untriaged bugs (-40 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New | 16:30 |
gibi | good progress to eating our backlog | 16:30 |
gibi | but we keep continue as RC1 is close | 16:30 |
gibi | RC critical bugs are tagged with ussuri-rc-potential #link https://bugs.launchpad.net/nova/+bugs?field.tag=ussuri-rc-potential | 16:30 |
gibi | there is now 1 bug on that list | 16:31 |
gibi | it has a patch up and I gave review feedback | 16:31 |
gibi | I'm not 100% sure it is that critical though | 16:31 |
bauzas | not RC holding | 16:31 |
bauzas | i mean it's not a U regression | 16:32 |
bauzas | but I thought it was worth looking at it before we branch | 16:32 |
gibi | sure | 16:33 |
gibi | somebody added an bug to the agenad | 16:33 |
gibi | how 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 |
openstack | Launchpad bug 1841932 in OpenStack Compute (nova) "hide_hypervisor_id extra_specs in nova flavor cannot pass AggregateInstanceExtraSpecsFilter" [Undecided,Expired] | 16:33 |
bauzas | leave it for open discussion ? | 16:33 |
gibi | OK, I hope the person added it to the agenda will show up until then | 16:34 |
gibi | any other bug related business? | 16:34 |
sean-k-mooney | so the problem with that extra spec is we did not namespace it | 16:34 |
sean-k-mooney | so it breaks the AggregateInstanceExtraSpecsFilter | 16:34 |
gibi | OK so it is not a regression at least | 16:35 |
sean-k-mooney | no | 16:35 |
gibi | good | 16:35 |
gibi | moving on | 16:35 |
tframbo | yeah ,i added the bug | 16:35 |
gibi | tframbo: let's discuss it a bit at the end of the meeitng | 16:35 |
gibi | #topic Stable Branches | 16:35 |
*** openstack changes topic to "Stable Branches (Meeting topic: nova)" | 16:35 | |
bauzas | the whole hide_hypervisor_id thing is... hacky :p | 16:35 |
tframbo | ok | 16:35 |
gibi | lyarwood any news? | 16:36 |
gibi | we discussed a need for a train release last week | 16:36 |
bauzas | tl;dr: shhhhht, QEMU, don't tell the nvidia driver I don't have the right to use you | 16:36 |
melwitt | stable 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 |
melwitt | train is fixed and stein fix is en route to the gate | 16:37 |
gmann | #link https://review.opendev.org/#/c/719121/ | 16:37 |
gibi | melwitt: thanks | 16:37 |
gmann | hope it get node in gate | 16:37 |
melwitt | yeah there might be some gate issue, I've been discussing in -infra. might be a nova bug even. yay! (not) | 16:37 |
gibi | it seems lyarwood is not here I will ping him about the stable release tomorrow | 16:38 |
lyarwood | yeah sorry ^ I've also hit a few other issues slowing things down | 16:38 |
lyarwood | we should still be able to release before RC (iirc that was the plan) | 16:38 |
gibi | lyarwood: cool thanks | 16:39 |
gibi | #topic Sub/related team Highlights | 16:39 |
*** openstack changes topic to "Sub/related team Highlights (Meeting topic: nova)" | 16:39 | |
gibi | API (gmann) | 16:39 |
gibi | anything besides the policy work? | 16:39 |
gmann | no, all what we discussed earlier . | 16:40 |
gibi | cool | 16:40 |
gibi | moving on | 16:40 |
gibi | #topic Stuck Reviews | 16: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 |
bauzas | nothing crucial here but I think we need a consensus on things we can accept | 16:41 |
bauzas | tl;dr: I'm touching the virt API signature of revert_resize and resize') | 16:41 |
gibi | we need to choose between allowing the virt driver interface to change post FF and allow the same interfacechange on stable/ussuri branch later | 16:41 |
bauzas | both are internal APIs but are in use by out-of-tree drivers | 16:41 |
bauzas | so for convenience (since virt APIs aren't public), we notify them | 16:41 |
bauzas | there are two options | 16:42 |
bauzas | 1/ we consider it's a breaking change hence not acceptable post FF | 16:42 |
bauzas | and in this case, we shouldn't allow this to be backportable | 16:42 |
bauzas | 2/ we assume this isn't a breaking change and in this case, we also consider it as acceptable post-FF | 16:43 |
gibi | just looking at the interface change patch it feels lower risk to do it now than to do it on the stable branch | 16:43 |
bauzas | and the corollar being, if this punts to V, this can be backportable to U | 16:43 |
bauzas | so, 1/ or 2/ ? | 16:43 |
gibi | 2/ | 16:43 |
bauzas | I thought we had disagreements on such things | 16:44 |
bauzas | I won't vote on it, since I'm involved in the change | 16:44 |
melwitt | and there is no desire to backport this earlier than ussuri right? I see that the bug was reported a long time ago | 16:44 |
bauzas | (but you get my opinion by seeing the change) | 16:44 |
bauzas | melwitt: I honestly have no energy for it | 16:44 |
bauzas | or, in other words, this wouldn't be backported upstream | 16:45 |
stephenfin | yeah, maybe downstream. Can't see us doing that upstream, tbh | 16:45 |
melwitt | ok. well, the change looks simple at least. so seems low risk | 16:45 |
bauzas | melwitt: but your question remains, if we go with 2/, in theory we could accept virt API changes to be backportable down to T or whatever | 16:45 |
bauzas | or we just say "no policy, it's case-by-case" and we move on | 16:46 |
gibi | if 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 version | 16:46 |
stephenfin | that's where I'm at too ^ | 16:47 |
melwitt | yeah, agree with that | 16:47 |
gibi | (for the record I'm not maintainting out of tree drivers) | 16:47 |
gibi | so we agree to change the interface then do it where it is expected to change | 16:47 |
stephenfin | but, 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 it | 16:48 |
sean-k-mooney | stephenfin: i dont really want use to do it downstream either | 16:48 |
bauzas | stephenfin: out-of-tree driver maintainers would have to maintain compatibility with the backport, whatever the use is | 16:48 |
bauzas | it's not about the use of the parameter | 16:48 |
*** ricolin has quit IRC | 16:48 | |
*** e0ne has quit IRC | 16:49 | |
bauzas | it's just that if we backport it to Train, Stein or Rocky, then we break them | 16:49 |
bauzas | (for resize and revert resize here) | 16:49 |
sean-k-mooney | bauzas: unless you catch the type error and call the function again without the parmater which we have dont in the past | 16:49 |
gibi | dansmith: 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-mooney | that would support out of tree driver but i dont think we shoudl have to do that | 16:49 |
*** e0ne has joined #openstack-meeting-3 | 16:49 | |
bauzas | we can honestly defer it to V if we are able to merge it sooner than later | 16:49 |
bauzas | sean-k-mooney: I'm opposed to it | 16:50 |
bauzas | sean-k-mooney: there is one thing to notify and have a gentleman agrement | 16:50 |
bauzas | there is another thing to implement some kind of public and maintained API for them | 16:50 |
stephenfin | yeah, that would imply actual support | 16:50 |
bauzas | okay, so, I don't hear any disagreement on merging it post-FF if we can | 16:51 |
bauzas | and if we can't, no backport to U | 16:51 |
bauzas | I'm cool with both things | 16:51 |
sean-k-mooney | i 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 V | 16:51 |
sean-k-mooney | with no backport | 16:51 |
stephenfin | Cool. I'll take another look at that in the morning and send it through so | 16:51 |
bauzas | let'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 V | 16:52 |
bauzas | stephenfin: the last patch needs a revision, hold your pen | 16:52 |
gibi | #info give a chance to https://review.opendev.org/#/c/589085/ to merge before RC1 | 16:52 |
bauzas | I think we're mostly on agreement, let's move on | 16:52 |
bauzas | gibi: also, the consensus is "don't backport any virt API changes" | 16:52 |
bauzas | which is a solid argument | 16:53 |
gibi | let's discuss that part of the agreemet at another time. | 16:53 |
bauzas | all good, thanks folks | 16:53 |
gibi | moveing on | 16:53 |
gibi | #topic Open discussion | 16: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.html | 16:53 |
gibi | I 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 |
gibi | doodle link is in the mail | 16:54 |
gibi | and if you have any feeling about the amount of time we need the please ping me on #openstack-nova later | 16:54 |
gibi | tframbo: your turn | 16:55 |
gibi | #link https://bugs.launchpad.net/nova/+bug/1841932 | 16:55 |
openstack | Launchpad bug 1841932 in OpenStack Compute (nova) "hide_hypervisor_id extra_specs in nova flavor cannot pass AggregateInstanceExtraSpecsFilter" [Undecided,Expired] | 16:55 |
bauzas | I'm sad the Foundation only provided a week slot | 16:55 |
bauzas | but meh | 16:55 |
tframbo | Maybe 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-mooney | tframbo: we coudl specical case for that yes for backport only | 16:56 |
bauzas | tframbo: can't you just use aggregates with random keys ? | 16:56 |
sean-k-mooney | but i think we shoudl be removing support for unnamespaced extra specs form the filter | 16:56 |
bauzas | I'm personnally opposed to expose any single libvirt knob as an image metadata property | 16:57 |
sean-k-mooney | bauzas: the image metadata is how we are ment to expose them | 16:57 |
sean-k-mooney | its why this feature originally only supported that | 16:57 |
sean-k-mooney | and not extra specs | 16:58 |
bauzas | sean-k-mooney: no | 16:58 |
sean-k-mooney | the extra sepcs supprot was added after | 16:58 |
bauzas | you can achieve the same thing without automatically exposing your capabilities | 16:58 |
bauzas | we have traits, we have filters that do this for you | 16:58 |
sean-k-mooney | this change how the vm is virutalsed | 16:58 |
bauzas | I don't see the need to add yet another knob | 16:58 |
sean-k-mooney | so trait wont help | 16:59 |
gibi | we are running out of time | 16:59 |
bauzas | that's a scheduling problem | 16:59 |
bauzas | not a boot issue | 16:59 |
sean-k-mooney | lets talk about this on #openstack-nova | 16:59 |
gibi | tframbo: I see that bauzas and sean-k-mooney has oppinion about the bugfix so let's talk to them on #openstack-nova | 16:59 |
bauzas | yeah, agreed, let's punt this to -nova | 16:59 |
gibi | thanks everyone | 16:59 |
tframbo | ok | 16:59 |
sean-k-mooney | o/ | 17:00 |
gibi | #endmeeting | 17:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 17:00 | |
openstack | Meeting ended Thu Apr 16 17:00:01 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-16-16.00.html | 17:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-16-16.00.txt | 17:00 |
*** sean-k-mooney has left #openstack-meeting-3 | 17:00 | |
openstack | Log: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-16-16.00.log.html | 17:00 |
*** tframbo has quit IRC | 17:28 | |
*** maciejjozefczyk has quit IRC | 17:39 | |
*** links has quit IRC | 17:44 | |
*** diablo_rojo has joined #openstack-meeting-3 | 17:51 | |
*** ralonsoh has quit IRC | 18:16 | |
*** diablo_rojo has quit IRC | 18:18 | |
*** jamesmcarthur has quit IRC | 18:44 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 18:44 | |
*** e0ne has quit IRC | 19:04 | |
*** jamesmcarthur has quit IRC | 19:29 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 19:33 | |
*** jamesmcarthur has quit IRC | 19:37 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 19:38 | |
*** jamesmcarthur has quit IRC | 20:14 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 20:20 | |
*** jamesmcarthur has quit IRC | 20:20 | |
*** slaweq has quit IRC | 21:14 | |
*** raildo has quit IRC | 21:31 | |
*** jamesmcarthur has joined #openstack-meeting-3 | 22:48 | |
*** jamesmcarthur has quit IRC | 23:19 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!