21:00:07 <mriedem> #startmeeting nova
21:00:08 <openstack> Meeting started Thu Jun  8 21:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:11 <openstack> The meeting name has been set to 'nova'
21:00:13 <dansmith> o/
21:00:19 <takashin> o/
21:00:24 <gibi> o/
21:00:24 <lbragstad> o/
21:00:26 <melwitt> o/
21:00:32 <dtp_> oo
21:00:50 <mikal> .
21:00:57 <cdent> o/
21:01:06 <edleafe> \o
21:01:22 <efried> /o\
21:01:36 <mriedem> alright let's get started
21:01:39 <mriedem> #link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
21:01:46 <mriedem> #topic release news
21:01:51 <mriedem> #link Pike release schedule: https://wiki.openstack.org/wiki/Nova/Pike_Release_Schedule
21:02:07 <mriedem> #info Today is the pike-2 milestone
21:02:19 <mriedem> i just posted the p-2 tag release request https://review.openstack.org/#/c/472409/
21:02:26 * bauzas waves latey
21:02:28 <mriedem> which i know bauzas has been fretting over
21:02:37 <bauzas> heh
21:02:57 <mriedem> #info next upcoming important date: Jul 20: non-client library (oslo, os-vif, os-brick, os-win, os-traits, etc) release freeze
21:03:09 <mriedem> with feature freeze the week after that
21:03:22 <mriedem> so we've got about 6 weeks left
21:03:35 <mriedem> #info Blueprints: 74 targeted, 69 approved, 18 completed, 4 not started
21:03:53 <mriedem> we're approving a couple of blueprints per week at this rate
21:03:57 <mriedem> the smaller ones
21:03:59 <mriedem> #info Blueprints which are blocked, not started or do not have an owner  after the p-2 milestone will likely be deferred to Queens.
21:04:22 <mriedem> questions about the release?
21:04:32 <mriedem> #topic bugs
21:04:38 <mriedem> nothing listed as critical
21:04:46 <mriedem> #help Need help with bug triage; there are 79 (down 14 from last week) new untriaged bugs as of today (June 8).
21:04:58 <mriedem> good news there is we're trending down in untriaged bugs week to week
21:05:06 <mriedem> getting back to that more manageable ~75 range :)
21:05:21 <bauzas> I have more time for that :)
21:05:25 <mriedem> gate status has been okish
21:05:41 <mriedem> top issue right now is probably http://status.openstack.org/elastic-recheck/index.html#1696125
21:05:55 <mriedem> that doesn't hit nova since we don't run the linuxbridge job,
21:05:58 <mriedem> but it's kind of crippling neutron
21:06:13 <mriedem> i've got a debug patch up to try and figure some of it out
21:06:15 <mriedem> but could use help
21:06:46 <mriedem> i don't have any news about 3rd part yci
21:06:51 <mriedem> *party ci
21:07:07 <mriedem> vmware is still off in the weeds i think, not sure about xen
21:07:23 <mriedem> anything for bugs?
21:07:33 <mriedem> #topic reminders
21:07:39 <mriedem> #link Pike Review Priorities etherpad: https://etherpad.openstack.org/p/pike-nova-priorities-tracking
21:07:53 <mriedem> #topic stable branch status
21:07:57 <mriedem> #link stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z
21:08:01 <mriedem> #link stable/newton: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/newton,n,z
21:08:15 <mriedem> we have a lot open there,
21:08:37 <mriedem> and we just recently did a release on both, but i feel like we've got some other high severity backports merged lately that aren't yet released
21:08:56 <mriedem> #topic subteam highlights
21:09:11 <mriedem> dansmith: i know there was no cells v2 meeting this week, but did you want to call out anything?
21:09:17 <dansmith> not really
21:09:27 <mriedem> boo
21:09:33 <mriedem> but alright
21:09:44 <mriedem> edleafe: scheduler?
21:09:52 <edleafe> Went over some current reviews - nothing to controversial
21:09:52 <edleafe> Most of the discussion was about how to claim against nested and/or shared providers.
21:09:55 <edleafe> Currently scheduler only has the compute node uuid, but some of the actual resource providers will be different in those cases.
21:09:58 <edleafe> Two widely different approaches came up, and were discussed until the end of the meeting and then further in a hangout.
21:10:01 <edleafe> The matter is still unresolved, and is being discussed in a ML thread starting with http://lists.openstack.org/pipermail/openstack-dev/2017-June/117913.html
21:10:04 <edleafe> EOM
21:10:15 <mriedem> i saw jaypipes also has a spec up
21:10:32 <mriedem> #link https://review.openstack.org/#/c/471927/
21:10:33 <edleafe> Yeah - a bit premature IMO, but whatever
21:10:48 * dansmith sighs
21:11:02 * edleafe there theres dansmith
21:11:17 <mriedem> ok i still need to digest all of this,
21:11:28 <mriedem> i've been more off in cells v2 land which is oddly comfortable at this point
21:11:41 <mriedem> i'll find any excuse not to have to be involved in the schedluer stuff :)
21:12:09 <mriedem> there was no api meeting
21:12:23 <mriedem> alex has a spec up for fixing server groups / members quota in the quota classes api
21:12:27 <mriedem> need to circle back on that
21:12:41 <mriedem> #link https://review.openstack.org/#/c/468619/
21:12:58 <mriedem> gibi is probably not around
21:13:02 <mriedem> but there was a notifications meeting
21:13:05 <mriedem> he and i
21:13:07 <gibi> Im here >D
21:13:08 <gibi> :D
21:13:09 <mriedem> oh wow
21:13:25 <mriedem> anything you want to mention?
21:13:39 <gibi> plenty of tranformation patches are waiting for core review
21:13:59 <gibi> the searchlight related patches still needs some care from me but mostly ready
21:14:08 <gibi> and we agreed the way forward on bug
21:14:23 <mriedem> the nova-api binary one?
21:14:32 <gibi> yeah
21:14:33 <mriedem> ok
21:14:36 <gibi> I cannot copy here for some reason
21:14:43 <gibi> 1696152
21:14:49 <mriedem> bug 1696152
21:14:50 <openstack> bug 1696152 in OpenStack Compute (nova) "nova notifications use nova-api as binary name instead of nova-osapi_compute" [Low,Confirmed] https://launchpad.net/bugs/1696152
21:15:01 <mriedem> let the bot do the work
21:15:02 <gibi> so we wont change the binary name
21:15:13 <gibi> in the notifications
21:15:24 <gibi> that was all
21:15:27 <mriedem> thanks gibi
21:15:36 <mriedem> for cinder/nova stuff, meeting was today
21:15:38 <mriedem> client-side microversion changes are merged (thanks!), now working on  live migration, swap volume and attach flows; need to close on swap  volume soon
21:15:52 <mriedem> stvnoyes is close on live migration working
21:15:59 <mriedem> jgriffith has a poc for new attach flow
21:16:06 <mriedem> the sticky thing right now is swap volume
21:16:25 <mriedem> jgriffith, cinder et al are going to write something up to the ML to state the problem and possible solutions
21:16:47 <mriedem> fire is, unfortunately, not an option
21:17:00 <mriedem> #topic stuck reviews
21:17:04 <mriedem> nothing on the agenda
21:17:09 <mriedem> anything anyone needs to bring up here?
21:17:22 <mriedem> #topic open discussion
21:17:30 <mriedem> lbragstad: Feedback on policy approach
21:17:35 <lbragstad> o/
21:17:41 <lbragstad> we've had a bunch of policy discussion recently and the result has been a collection of specs
21:18:10 <lbragstad> since the approach is going to affect the majority of projects, we want to make sure we get feedback before going off and just doing a bunch of stuff
21:18:24 <lbragstad> #link https://review.openstack.org/#/c/460344/ attempts to capture the overall policy needs we're not getting today
21:18:30 <lbragstad> #link https://review.openstack.org/#/c/462733/ attempts to detail a roadmap in the interest of security
21:18:41 <lbragstad> #link https://review.openstack.org/#/c/464763/ introduces a concept of global roles
21:19:01 <lbragstad> the second and third links detail work the is going to impact consuming projects
21:19:37 <lbragstad> i'm taking time this week to meet with projects and get feedback on what we've come up with
21:19:46 <lbragstad> johnthetubaguy: has been driving a bunch of this, too
21:20:36 <mriedem> ok
21:20:38 <lbragstad> if anyone has particular questions, please don't hesitate to come find me
21:20:50 <mriedem> i haven't looked at any of it
21:21:11 <lbragstad> it's not the most exciting stuff in the world ;)
21:21:20 <mriedem> well, it's also 2/3 of the way through pike
21:21:35 <mriedem> and we're way behind on major stuff we've already got planned
21:21:39 <lbragstad> mriedem: yeah - everything we're considering now is going to be staged for queens
21:21:41 <mriedem> i realize this is prepping for queens
21:22:00 <mriedem> i'd think any major decisions are going to be finalized at the ptg
21:22:13 <lbragstad> ++
21:22:20 <mriedem> lbragstad: are ops / user community groups/people providing feedback?
21:22:31 <lbragstad> mriedem: yeah - let me grab a link
21:22:58 <lbragstad> #link http://lists.openstack.org/pipermail/openstack-dev/2017-May/117419.html
21:23:10 <lbragstad> i started that thread in an attempt to get feedback from operators
21:23:34 <lbragstad> i sent an update today with the current direction based on the comments collected there
21:23:55 <mriedem> ok
21:24:02 <lbragstad> #link http://lists.openstack.org/pipermail/openstack-dev/2017-June/118047.html
21:24:23 <lbragstad> but since this is going to impact a lot of project, i want to make sure we get as much feedback as possible beforehand
21:24:54 <mriedem> ok, but you guys aren't planning on landing major changes in keystone in pike are you?
21:25:15 <lbragstad> mriedem: no - we don't have the bandwidth to do anything major this release
21:25:22 <mriedem> ok
21:25:33 <lbragstad> but i did want to get this in front of other groups early
21:25:47 <lbragstad> so that it didn't come as a surprise in a couple months
21:26:10 <mriedem> alright
21:26:18 <mriedem> anything else?
21:26:28 <lbragstad> nope - that does it for me, thanks!
21:26:38 <mriedem> anyone else have anything here?
21:26:52 * cdent wants a pony
21:26:57 <mriedem> denied
21:27:01 * cdent cries
21:27:03 <mriedem> ok that's it then
21:27:05 <mriedem> thanks everyone
21:27:08 <mriedem> #endmeeting