21:00:09 <melwitt> #startmeeting nova
21:00:10 <openstack> Meeting started Thu Feb 14 21:00:09 2019 UTC and is due to finish in 60 minutes.  The chair is melwitt. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:14 <openstack> The meeting name has been set to 'nova'
21:00:33 <melwitt> greetings all, welcome to the nova meeting
21:00:37 <takashin> o/
21:00:40 <dansmith> o/
21:00:41 <melwitt> agenda is at https://wiki.openstack.org/wiki/Meetings/Nova
21:00:43 <edleafe> \o
21:00:58 <melwitt> lettuce start
21:01:06 <melwitt> #topic Release News
21:01:15 <melwitt> #link Stein release schedule: https://wiki.openstack.org/wiki/Nova/Stein_Release_Schedule
21:01:21 <melwitt> #info s-3 feature freeze is March 7
21:01:29 <melwitt> three weeks left until feature freeze
21:01:38 <mriedem> .
21:01:52 <melwitt> and two weeks left until non-client library freee
21:01:55 <melwitt> *freeze
21:02:17 <melwitt> if you need to get new changes out into new library releases, get those merged asap
21:02:46 <melwitt> (os-vif, os-traits, and friends)
21:02:57 <melwitt> #link Stein blueprint status tracking: https://etherpad.openstack.org/p/nova-stein-blueprint-status
21:03:09 <melwitt> we're tracking approved blueprint status there ^
21:03:26 <melwitt> help is appreciated in keeping it updated. I'm going to go through and update things today
21:03:52 <melwitt> and I want to send another update to the ML
21:04:14 <melwitt> currently the volume-backed detach root volume and volume-backed rebuild series are in the danger zone
21:04:25 <melwitt> but the owners of those are going to be updating soon
21:04:40 <melwitt> #link Stein runway etherpad: https://etherpad.openstack.org/p/nova-runways-stein
21:04:46 <melwitt> #link runway #1: https://blueprints.launchpad.net/nova/+spec/libvirt-neutron-sriov-livemigration (adrianc, moshele) [END 2019-02-19] https://review.openstack.org/#/q/status:open+topic:bp/libvirt-neutron-sriov-livemigration
21:04:52 <melwitt> #link runway #2: https://blueprints.launchpad.net/nova/+spec/handling-down-cell (tssurya) [END 2019-02-19] https://review.openstack.org/#/q/status:open+branch:master+topic:bp/handling-down-cell
21:05:01 <melwitt> #link runway #3: https://blueprints.launchpad.net/nova/+spec/expose-virtual-device-tags-in-rest-api (mriedem) [END 2019-02-25] https://review.openstack.org/#/q/status:open+topic:bp/expose-virtual-device-tags-in-rest-api
21:05:13 <tssurya> o/
21:05:43 <melwitt> I think we have active review going on for everything in runways, good progress being made
21:06:02 <adrianc> i dont think runway #1 will converge till the 19th
21:06:39 <melwitt> adrianc: for lack of review or is there a blocker?
21:06:54 <adrianc> review is slow
21:07:21 <melwitt> ok, thanks for mentioning that. so we need more review on the SRIOV live migration series
21:07:51 <melwitt> #help additional review needed on the SRIOV live migration patch series https://review.openstack.org/#/q/status:open+topic:bp/libvirt-neutron-sriov-livemigration
21:08:04 <adrianc> the procedure is to re-add to the queue right ?
21:08:25 <melwitt> yes, you can re-add as soon as the end date is done
21:08:55 <adrianc> ack
21:09:22 <melwitt> anyone have anything else to add or ask about release stuff?
21:09:44 <melwitt> #topic Bugs (stuck/critical)
21:09:56 <melwitt> no critical bugs in the link
21:10:03 <melwitt> #link 69 new untriaged bugs (up 11 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
21:10:15 <melwitt> #link 9 untagged untriaged bugs (up 6 since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW
21:11:00 <melwitt> crunch time is upon us as the climbing bug count reflects, but we need to get in there and triage so we can fix what we can before the RC
21:11:07 <melwitt> #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags
21:11:14 <melwitt> #help need help with bug triage
21:11:20 <melwitt> Gate status
21:11:29 <melwitt> #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
21:12:04 <melwitt> mriedem has been working on lots of patches to alleviate gate issues
21:12:14 <melwitt> (see his posts to the ML for details)
21:12:18 <mriedem> speaking of http://status.openstack.org/elastic-recheck/#1783405
21:12:21 <mriedem> new patches there
21:12:28 <mriedem> ping your favorite tempest core
21:13:11 <melwitt> coolness
21:13:27 <melwitt> we can get gmann
21:13:44 <melwitt> 3rd party CI
21:13:51 <melwitt> #link 3rd party CI status http://ciwatch.mmedvede.net/project?project=nova&time=7+days
21:14:40 <melwitt> I think that's all I have for bugs and gate status. anyone have anything to add?
21:15:14 <melwitt> #topic Reminders
21:15:47 <melwitt> not really a reminder, but we do have a train ptg etherpad started (thanks efried)
21:16:04 <melwitt> #link train ptg etherpad: https://etherpad.openstack.org/p/nova-ptg-train
21:16:11 * efried waves late due to ping, thanks melwitt
21:16:22 * efried frantically composes n-sch summary
21:17:05 <melwitt> I can't think of any other reminders at the moment
21:17:15 <melwitt> anyone have anything to add?
21:17:38 <melwitt> #topic Stable branch status
21:17:44 <melwitt> #link stable/rocky: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/rocky,n,z
21:18:26 <melwitt> handful of reviews there need a second +2
21:18:39 <melwitt> #link stable/queens: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/queens,n,z
21:19:02 <melwitt> I went through and did a bunch of queens reviews recently, but there are still a lot now
21:19:22 <melwitt> #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z
21:19:35 <melwitt> lots of pike reviews too
21:19:43 <melwitt> queens and pike review help needed
21:20:03 <melwitt> ok, moving on to subteams
21:20:12 <melwitt> #topic Subteam Highlights
21:20:33 <melwitt> efried: ready for scheduler notes?
21:20:43 <efried> can you come back to me?
21:20:51 <efried> or I can wing it :)
21:20:54 <melwitt> not really
21:21:00 <melwitt> winging it is good
21:21:09 <melwitt> gmann didn't leave any notes for API subteam
21:21:26 <efried> ight
21:21:33 <efried> #link n-sch meeting minutes http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-02-11-14.00.html
21:21:41 <efried> VGPU series is ongoing, hitting some interesting snags, but they're being worked through. Bottom of series has moved due to one of these.
21:21:41 <efried> #link new bottom of vgpu reshaper https://review.openstack.org/#/c/636591
21:21:50 <efried> The TL;DR here is that we need a way to correlate the allocated RP back to the "real thing" (in this case the pgpu). The virt driver (not placement) needs to be responsible for this mapping. The proposed solution is for update_provider_tree to save its ProviderTree object to the driver object as an attribute; and then spawn() can use it to look up the provider name from the UUID. Because the name is encoded with the pgpu's PCI
21:22:30 <efried> #link in_tree allocation candidates series starting at https://review.openstack.org/#/c/635722/
21:22:30 <efried> Extraction, all significant news has gone through the ML.
21:23:01 <efried> And the only other thing was the placement governance deal, which has been on the ML as well.
21:23:25 <efried> #link placement governance discussion http://lists.openstack.org/pipermail/openstack-discuss/2019-February/thread.html#2575
21:23:58 <efried> TL;DR unless any snags, it's looking like we're going to elect a placement PTL in the regular elections coming up, and make placement its own thing \o/
21:24:02 <efried> END
21:24:52 <melwitt> cool, thanks
21:25:06 <melwitt> ok, anything else for subteams?
21:25:21 <melwitt> #topic Stuck Reviews
21:25:30 <melwitt> nothing on the agenda, so will assume there are no stuck reviews
21:25:41 <melwitt> #topic Open discussion
21:25:45 <melwitt> some agenda items
21:26:14 <melwitt> noted this may not be needed bc discussions have occurred, but just going to link them here anyway
21:26:17 <melwitt> Placement governance switch
21:26:20 <edleafe> I put that on the agenda a few days ago before things had been discussed on the ML and in the -tc channel
21:26:34 <edleafe> So unless someone has something new to add...
21:27:04 <melwitt> yeah, I was thinking only if it might help people who read the minutes but don't keep up as much with the ML. I dunno
21:27:22 <melwitt> Governance change patch: https://review.openstack.org/636416
21:27:40 <melwitt> ok, the other two agenda items are from me, just FYI things
21:27:51 <melwitt> propose removal of 'project_only=True' in DB layer: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002740.html
21:28:13 <melwitt> replies welcome and wanted ^
21:28:21 <melwitt> help appreciated with cloud vision reflection doc: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002501.html
21:28:36 <melwitt> help appreciated on this ^
21:28:53 <melwitt> does anyone have anything else they'd like to discuss for open discussion?
21:28:57 <efried> I'd like to bring attention to the
21:28:57 <efried> #link Placement OVO-ectomy series starting at https://review.openstack.org/#/c/636631/
21:28:57 <efried> In case like me you start to ignore ML threads after a while, and missed when the
21:28:57 <efried> #link "goals aligned with TC" thread went off into the topic of de-OVO-ification http://lists.openstack.org/pipermail/openstack-discuss/2019-February/thread.html#2712
21:28:57 <efried> ...please take a look.
21:29:15 <efried> ...because it's a fairly substantial philosophical shift
21:29:57 <efried> So far the feedback has been positive, so if you have objections, speak now and all that.
21:30:00 <efried> END
21:30:10 <melwitt> cool, thanks for bringing that to attention
21:30:33 <melwitt> anything else for open discussion before we wrap up?
21:30:43 <melwitt> going
21:30:48 <melwitt> going
21:30:59 <melwitt> ok, thanks all for attending
21:31:02 <melwitt> #endmeeting