21:00:10 #startmeeting nova 21:00:11 Meeting started Thu Jul 5 21:00:10 2018 UTC and is due to finish in 60 minutes. The chair is melwitt. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:14 The meeting name has been set to 'nova' 21:00:16 o/ 21:00:17 o/ 21:00:18 o/ 21:00:18 o/ 21:00:23 howdy friends 21:00:39 hopefully this will be a quick meeting 21:00:44 o/ 21:00:57 #topic Release News 21:01:01 \o 21:01:07 #link Rocky release schedule: https://wiki.openstack.org/wiki/Nova/Rocky_Release_Schedule 21:01:25 milestone 3, r-3 feature freeze is coming up in 3 weeks 21:02:12 so we've not too much time left for features 21:02:45 are there any things on the radar that will be subject to a FF exception? 21:03:34 I think we're gonna hit FFE's for some placement stuff :( 21:03:41 assuming we want to get the reshaper in 21:03:50 yeah, that's one I was thinking about 21:03:50 is the handle down cell an exception ? 21:04:31 that's the other I was thinking about. I think probably but we'll need to discuss it 21:04:44 ack 21:04:53 the bug-ish part of down-cell has merged, 21:05:03 the rest is pretty feature-y given that it will have a microversion and new behavior 21:05:12 so, I would think we'd need to consider that an FFE 21:05:33 roger that 21:06:36 okay, to summarize, we've 3 weeks to r-3 and let us know if you've concerns over your feature not making it. we've got https://etherpad.openstack.org/p/nova-rocky-blueprint-status to track status 21:07:10 #link rocky feature tracking status https://etherpad.openstack.org/p/nova-rocky-blueprint-status 21:07:17 #link Rocky review runways: https://etherpad.openstack.org/p/nova-runways-rocky 21:07:25 #link runway #1: Report CPU features as traits - https://blueprints.launchpad.net/nova/+spec/report-cpu-features-as-traits [END DATE: 2018-07-06] https://review.openstack.org/560317 21:07:32 #link runway #2: NUMA aware vSwitches - https://blueprints.launchpad.net/nova/+spec/numa-aware-vswitches (stephenfin) [END DATE: 2018-07-06] https://review.openstack.org/#/q/topic:bp/numa-aware-vswitches 21:07:38 #link runway #3: Complex Anti Affinity Policies: https://blueprints.launchpad.net/nova/+spec/complex-anti-affinity-policies (yikun) [END DATE: 2018-07-06] https://review.openstack.org/#/q/topic:bp/complex-anti-affinity-policies 21:07:55 all 3 of these runways end at EOD tomorrow 21:08:02 mriedem and I have been hitting 2 and 3 pretty hard 21:08:11 i also -1ed #1 on friday 21:08:21 doubt either will make it, but they have some inertia I think 21:08:23 otherwise efried helped shape that one up 21:08:45 okay, that's good to hear. thank you dansmith efried_off mriedem 21:09:28 anyone have anything else for release news or runways before we move on? 21:10:02 #topic Bugs (stuck/critical) 21:10:10 no critical bugs in the link 21:10:23 #link 51 new untriaged bugs (up 2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 21:10:52 untriaged count still creeping up slowly 21:11:06 #link 7 untagged untriaged bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 21:11:18 #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags 21:11:23 #help need help with bug triage 21:11:29 Gate status: 21:11:34 #link check queue gate status http://status.openstack.org/elastic-recheck/index.html 21:12:29 I'm not aware of any major issues 21:12:38 3rd party CI: 21:12:43 #link 3rd party CI status http://ci-watch.tintri.com/project?project=nova&time=7+days 21:13:10 anything else for bugs, gate status, or 3rd party CI? 21:13:25 #topic Reminders 21:13:29 #link Rocky Subteam Patches n Bugs https://etherpad.openstack.org/p/rocky-nova-priorities-tracking 21:13:56 I updated a few things on there for the placement subteam section. need to take another look and update more that I find 21:14:04 anything else for reminders? 21:14:26 #topic Stable branch status 21:14:32 #link stable/queens: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/queens,n,z 21:14:38 lots o queens backports with a +2 on them 21:14:56 lyarwood has been busy 21:15:03 #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z 21:15:15 several pike backports need review 21:15:22 #link stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z 21:15:35 nothing ready for ocata 21:15:49 anything else for stable branch status? 21:16:14 #topic Subteam Highlights 21:16:19 no 21:16:30 yesterday was a US holiday so we didn't hold a cells meeting 21:16:35 :) 21:16:50 tssurya: anything you'd like to call out for cells? 21:16:58 no all good :) 21:17:04 k 21:17:14 i see there is a -1 on the down cell spec 21:17:45 mriedem: yes, we should talk about some stuff later after this meeting 21:17:49 is that waiting for core review to see if the -1 is legit? 21:18:06 mriedem: yea its waiting for more opinions 21:18:09 ok i've been focused on stuff in runways so i just haven't looked at the latest 21:18:23 yeah, upon a glance is talking about blocking a nova boot over a down cell. that is something that will be contentious 21:18:44 melwitt: correct 21:19:02 I don't like it either but I don't have a better idea, is kinda what I think about that 21:19:33 since we've got no way to do all of the quota stuff thru placement because of the inability to know allocation owners (i.e. "which nova?") 21:19:36 anyway 21:20:01 we can move on for now 21:20:01 scheduler meeting was short, we talked about several bugs with being able to reparent providers and miscellaneous problems handling consumers and consumer generations. fixes in progress on most things. some discussion remains on others. those bugs are the highlight of the week. 21:20:46 cool, thanks cdent. the reparent providers thing is blocking mriedem's heal allocations patch 21:20:53 s/thing/bug/ 21:21:06 not re-parent, 21:21:08 change owner 21:21:21 if we're talking about healing consumer project/user 21:21:25 oh, k. I thought reparent meant that. thanks for correcting 21:22:09 I don't think gibi is going to be around right now, he didn't leave any notes about notifications subteam on the agenda 21:22:21 *and he didn't leave any notes 21:22:30 anything else for subteam highlights? 21:22:30 there is a fix up for a thing that's been in the ML thread 21:22:48 https://review.openstack.org/#/c/579925/ 21:23:09 people with really really old instances might not be able to use versioned notifications because the really old embedded instance.flavor is missing a field 21:23:10 #link notifications bug patch https://review.openstack.org/579925 21:23:23 ah, okay. will check that out 21:23:26 dansmith has context so i'll gently remind him to review it 21:23:32 oh so gentle 21:23:34 even better 21:23:35 oh baby 21:23:41 is this the flavor thing? 21:23:42 yeah 21:23:48 okay yeah 21:23:54 kewl 21:24:05 #topic Stuck Reviews 21:24:14 nothing on the agenda. does anyone in the room have anything for stuck reviews? 21:24:43 #topic Open discussion 21:24:52 one agenda item from this morning 21:24:57 specless blueprint approval wanted (jmlowe) https://blueprints.launchpad.net/nova/+spec/rbd-erasure-coding 21:25:24 doesn't say anything about what is involved? 21:25:27 this is about enabling the use of ceph rbd erasure encoding. it would involve adding a new config option 21:25:48 would be nice to at least explain what we need to do.. is it just "if flag, pass true for erasure coding" ? 21:25:59 which would be used to pass a data_pool kwarg to our existing call during clone/create 21:26:28 yeah, I can ask jmlowe to add a bit more detail to the description 21:26:51 if it's just a flag that gets passed through during image create or whatever, it seems reasonable for specless 21:27:45 yeah, that was also my opinion. we discussed it a bit in #openstack-nova today and he said it should be that simple 21:28:30 so bp approval is contingent on poc i'd say 21:28:37 if it's that simple 21:29:11 okay, that sounds fair enough. I did tell him if he wants to get this done this cycle the code is gonna have to show up ASAP being that FF is only 3 weeks away 21:29:44 so we can just adjust that to, upload the POC and approve after that 21:30:26 i think we should also have 2 cores signed up to review it 21:30:37 just like jangutter's exception bp 21:30:49 I mentioned that to jmlowe too. I volunteer as one 21:30:54 i.e. if cores want to allow these things in post spec freeze, they need to sign up to review them 21:31:16 let's move on until code is up 21:31:27 okay, I'll make a note on the bp and let him know 21:31:30 yass 21:31:42 anyone have anything else for open discussion before we wrap up? 21:32:12 send it. 21:32:18 okay, thanks y'all 21:32:21 #endmeeting