16:00:29 <gibi> #startmeeting nova
16:00:30 <openstack> Meeting started Thu Mar 26 16:00:29 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:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:34 <openstack> The meeting name has been set to 'nova'
16:00:37 <gibi> o/
16:00:46 <dansmith> o/ (still on this call)
16:00:46 <gmann> o/
16:01:11 <bauzas> \o
16:01:17 <johnthetubaguy> o/
16:01:31 <artom> o/
16:01:49 <gibi> we have a pretty long agenda. Let's get started
16:01:55 <gibi> #topic Last meeting
16:02:00 <gibi> #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-03-19-16.00.log.html
16:02:06 <gibi> gibi promised to follow up on the ML about the plans for a virtual PTG.
16:02:10 <gibi> proposal sent to the ML #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013555.html but I'm open to any suggestion about the format.
16:02:50 <gibi> let's continue that on the ML
16:02:56 <gibi> We had a discussion about the two company rule last week.
16:03:05 <gibi> the resulting ML thread #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013423.html
16:03:08 <gibi> based on the different discussion I'm now proposing a compromise #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013553.html Please raise your voice if you don't like it til next Tuesday
16:03:24 <bauzas> cool, i need to write my opinions for the both threads
16:03:42 <gibi> bauzas: thanks
16:03:54 <gibi> we discussed the core situation last week as well. It is resulted in a nomination of two new cores. Cores, please cast your votes on the ML til next Monday
16:03:57 <gibi> lyarwood #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013511.html
16:04:00 <gibi> gmann #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013519.html
16:04:21 <gibi> Anything else we need to discuss from the last meeting?
16:05:19 <gibi> #topic Bugs (stuck/critical)
16:05:32 <gibi> No Critical bugs
16:05:39 <gibi> #link 102 new untriaged bugs (+3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
16:05:59 <gibi> I wanted but had no time to triage bugs this week :/
16:06:17 <gibi> any help is appreciated
16:06:41 <gibi> anything about bugs?
16:07:21 <gibi> melwitt, lyarwood, gmann: how is the gate doing recently?
16:07:27 <gmann> sorry did not get chance to do bug thins this week. few from previous week 'need-discussion' completed the discussion part and in progress of fix or in todo list.
16:07:38 <gibi> gmann: thanks
16:07:41 <bauzas> I'd love too
16:07:52 <bauzas> we're close to the RC period and I'm a bit afraid
16:08:10 <bauzas> but once I'm done with all the stuff I have, I'll try to triage
16:08:20 <gibi> thanks
16:08:51 <gmann> gibi: not seen any frequent occurring issue on gate but live migration job status can be updated by melwitt or lyarwood
16:09:20 <gibi> gmann: thanks.
16:09:50 <gmann> FYI, fluctuate network issue is merged now. (there might be few more tests, so keep reporting or push patch) - https://review.opendev.org/#/c/711049/
16:10:01 <gibi> awesome
16:10:08 <lyarwood> \o hey sorry just back
16:10:19 <lyarwood> gibi: LM job should be stable now, let me know if it isn't please.
16:10:26 <gibi> lyarwood: thank you
16:10:49 <gibi> #topic Release Planning
16:10:57 <gibi> One week until "Final release for non-client libraries" (Apr 3.)
16:11:02 <gibi> os-vif #link https://review.opendev.org/#/q/project:openstack/os-vif+status:open
16:11:09 <gibi> os-resource-classes #link https://review.opendev.org/#/q/project:openstack/os-resource-classes+status:open
16:11:16 <gibi> os-traits #link https://review.opendev.org/#/q/project:openstack/os-traits+status:open
16:11:22 <gibi> I see nothing open that is a must-have for Ussuri.
16:11:31 <gibi> but please shout if I missed something
16:11:32 <sean-k-mooney> gibi: the pending os-vif changes wont merge in ussuri
16:11:51 <gibi> sean-k-mooney: yeah I they have -W on them
16:11:52 <sean-k-mooney> they need ovs changes to merge first and that wont happen in time
16:12:28 <gibi> Who will propose the releases for these libs next week? sean-k-mooney could you take os-vif?
16:12:44 <sean-k-mooney> sure
16:12:47 <gibi> thanks
16:13:21 <gibi> if nobody signs up for os-traits and os-resource-classes then I will propose them
16:13:44 <gibi> Two weeks until Milestone 3
16:13:53 <sean-k-mooney> i can proably take a look at doing that too since ill be doing the os-vif one
16:14:03 <gibi> sean-k-mooney: that would be awesome
16:14:09 <gibi> ping me if you stuck
16:14:19 <gibi> M3 means Feature Freeze
16:14:30 <gibi> from the 30 approved BPs for Ussuri 8 is already implemented \o/
16:14:32 <johnthetubaguy> gibi: are those libs owned by placement now?
16:14:46 <gibi> johnthetubaguy: honestly I don't know
16:14:58 <gibi> I can ping tetsuro about it
16:15:00 <johnthetubaguy> I was just looking here: https://github.com/openstack/governance/blob/master/reference/projects.yaml#L2592
16:15:09 <johnthetubaguy> worth a chat to make sure I guess :)
16:15:28 <johnthetubaguy> they sure matter to us, either way
16:15:31 <gibi> jeah I will let tetsuro know that he is supposed to handle it :)
16:15:48 <sean-k-mooney> johnthetubaguy: yes they are
16:15:56 <sean-k-mooney> https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml#L2570-L2597
16:16:17 <gibi> moving back to FF
16:16:37 <gibi> I did a quick scan an targeted 12 from the remaining 22 BPs to ussuri-3 #link https://launchpad.net/nova/+milestone/ussuri-3 These are the ones I feel still has chance to be finished before the freeze.
16:16:57 <gibi> if something is missing then please let me know
16:18:04 <bauzas> I'll upload a new one soon but I'll ping you
16:19:08 <gibi> bauzas: yeah some of you bp was not started but If you have code now then I can target it to ussuri-3
16:19:22 <johnthetubaguy> I am still pretending my unified limits stuff might be ready, but I am not sure we have the review bandwidth
16:19:59 <gibi> johnthetubaguy: I glanced at the series but I had not time to dig into it maybe next week
16:20:29 <sean-k-mooney> speaking fo review bandwith we might want to start using the runways again to priortise it or just make a concouse effort to look at that list
16:20:41 <johnthetubaguy> no worries, its just one of those multi-year things that finally feels closer, like policy
16:21:15 <johnthetubaguy> +1 on runways again, to focus our efforts to get more things over the line
16:21:56 <gibi> sean-k-mooney, johnthetubaguy: sure, if you have or know about a bp that is really close then put that in the queue
16:21:57 <gmann> johnthetubaguy: i will start reviewing those but keeping policy stuff on priority for now. may be from Monday, I will be able to
16:22:19 <johnthetubaguy> gmann: +1 on getting policy stuff up for review being the highest priority there
16:23:07 <gibi> policy and cyborg integration is the two highest prio bp in lauchpad now
16:23:13 <johnthetubaguy> I haven't yet met an operator that isn't hurting because we don't have that policy stuff yet
16:23:42 <johnthetubaguy> there might be too many negatives there
16:24:10 <gibi> anything else on the FF ?
16:24:51 <sean-k-mooney> gibi: i assume we will try to avoid FF exceptions unless on of the bluepirts you have targeted to u3 misses
16:25:20 <sean-k-mooney> ideally we would not have any exceptions but i guess we will see how it goes
16:25:52 <gibi> I prefere not to have exception but if a bp is close (e.g. has +2) then I think we are willing to consider
16:26:56 <sean-k-mooney> ok we can proably move on
16:27:03 <gibi> Milestone 3 also means: Final release for client libraries
16:27:12 <gibi> we have patches open #link https://review.opendev.org/#/q/project:openstack/python-novaclient+status:open but these are still tight to open nova patches.
16:27:29 <gibi> you have have anything important then let me know
16:28:20 <gibi> anything else about the release?
16:29:03 <gibi> #topic Stable Branches
16:29:09 <gibi> lyarwood: anything newsworthy?
16:31:41 <gibi> I guess that means no :)
16:31:46 <gibi> #topic Sub/related team Highlights
16:31:57 <gibi> Placement (tetsuro)
16:32:54 <gibi> API (gmann)
16:32:56 <lyarwood> gibi: no sorry
16:33:05 <gmann> deleted_on_termination things you already have on agenda for Open Discussion. nothing else than ML updates or what we already discussed.
16:33:06 <gibi> lyarwood: np
16:33:09 <gibi> Updates on ML: http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013615.html
16:33:19 <gibi> gmann: thanks
16:33:26 <gibi> #topic Stuck Reviews
16:33:34 <gibi> (brinzhang_): https://review.opendev.org/#/q/topic:bp/destroy-instance-with-datavolume is stuck on whether we want a PATCH API or not.
16:33:47 <gibi> this was since discussed on #openstack-nova
16:34:11 <gibi> and the current consensus is to change the API design to use PUT instead
16:34:22 <dansmith> I didn't catch up on this yet,
16:34:36 <dansmith> but it sounds like everyone is okay with it, but we don't know about brin himself yet?
16:34:51 <gibi> dansmith: yes, brin said he cannot attend the meting
16:34:57 <dansmith> ack
16:35:20 <gibi> summary is in https://review.opendev.org/#/c/693828/ now so brin will see it tomorrow
16:35:36 <dansmith> I will commit to prioritized review of that when the change is done
16:35:38 <gibi> I think dansmith and I will help him if needed
16:35:43 <gmann> will we update spec doc also for that ?
16:35:55 <gibi> gmann: yes, that is needed too
16:35:55 <gmann> just replacing PUT to PATCH
16:35:57 <dansmith> we should, but we can do that later
16:36:01 <gmann> yeah
16:36:04 <gibi> yeah
16:36:17 <gmann> kind of doc update
16:36:17 <dansmith> let's focus on getting the code done
16:36:26 <gmann> +1
16:36:39 <gibi> agree
16:36:52 <gibi> any other stuck review we need to talk about?
16:37:04 <johnthetubaguy> I am suggesting we stop documenting the existing PUT API that should only be used by Cinder, to help remove confusion.
16:37:44 <gibi> johnthetubaguy: would that confuse Cinder devs?
16:37:44 <dansmith> johnthetubaguy: as I said, i think that it will be easier to document the put as primarily for updating the flag, but with a note:: that the volume_id can be updated under certain circumstances
16:38:06 <dansmith> not sure we should really remove it entirely, but make the swap look like the weird stepchild instead of the primary reason for a PUT of that resource
16:38:07 <johnthetubaguy> dansmith: true and gibi: possibly
16:38:25 <johnthetubaguy> dansmith: that is a nice way of looking at it, I am sold.
16:38:40 <gmann> dansmith:  removing swap things from api-ref can make it internal though
16:38:47 <dansmith> gmann: it's not internal
16:39:08 <gmann> but we except users not to use this right ?
16:39:22 <dansmith> if we had a separate document of "friend" APIs for services only, then we could put it there, but we don't
16:39:36 <dansmith> gmann: I've actually heard of people using that API for reasons they shouldn't
16:39:49 <dansmith> but still, I don't think we should un-document it just because we expect only cinder to call it
16:40:00 <dansmith> think of how much of the neutron api would be undocumented if they did that for nova
16:40:39 <sean-k-mooney> hopefully ironic a zun would close some of the gaps but that is a fair point
16:40:57 <gmann> ohk. +1 on making primary reason as update resource not swap at least.
16:41:10 <gmann> cinder is kind of users for nova
16:41:57 <gibi> any other stuck review we need to talk about?
16:42:45 <gibi> #topic Open discussion
16:42:55 <gibi> just a heads up
16:42:56 <gibi> (gibi): Note that this weekend EU goes to summer time (e.g. I will go from UTC + 1 to UTC + 2) but the meeting remains at 16:00 UTC.
16:43:49 <gibi> any other topic to discuss?
16:45:09 <gibi> then lets close this. Thanks for coming. Take case and wash your hands!
16:45:18 <gibi> Take care I mean
16:45:31 <gibi> #endmeeting