21:00:12 <mriedem> #startmeeting nova
21:00:13 <openstack> Meeting started Thu Dec 21 21:00:12 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:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:17 <openstack> The meeting name has been set to 'nova'
21:00:30 <edleafe> \o
21:00:31 <mriedem> hi, who is still lurking this time of year?
21:00:34 <takashin> o/
21:00:35 <melwitt> o/
21:01:17 <mriedem> alright well we can get started
21:01:19 <mriedem> #link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
21:01:27 <mriedem> #topic release news
21:01:32 <mriedem> #link Queens release schedule: https://wiki.openstack.org/wiki/Nova/Queens_Release_Schedule
21:01:38 <mriedem> #info Jan 18: non-client library (oslo, os-vif, os-brick, os-win, os-traits, etc) release freeze
21:01:55 <mriedem> so 4 weeks to get library stuff in
21:02:02 <mriedem> really 3 if you exclude next week
21:02:16 <mriedem> not sure what we have pending for os-vif or os-traits at this time
21:02:22 <mriedem> #info Jan 25: q-3 milestone, Feature Freeze, final python-novaclient release, requirements freeze, Soft String Freeze
21:02:33 <mriedem> so realistically 4 weeks from feature freeze
21:03:01 <mriedem> and then we have 2 weeks for "stability"
21:03:03 <mriedem> before RC1
21:03:10 <mriedem> #info Blueprints: 52 targeted, 52 approved, 15 complete (2 completed since the last meeting)
21:03:21 <mriedem> steadily getting some blueprints completed
21:03:31 <mriedem> #link queens blueprint tracking etherpad https://etherpad.openstack.org/p/nova-queens-blueprint-status
21:03:44 <mriedem> questions about the release?
21:03:53 <mriedem> #topic bugs
21:03:58 <mriedem> nothing critical
21:04:02 <mriedem> #info 44 new untriaged bugs (up 12 since the last meeting)
21:04:14 <mriedem> we're falling behind on bug triage
21:04:22 <mriedem> #help need help with bug triage
21:04:33 <mriedem> generally some easy ones if you take some time to step through them
21:04:51 <mriedem> https://goo.gl/ZBw1Zw
21:05:02 <mriedem> gate status,
21:05:16 <mriedem> i posted to the ML last night about a py27 failure i've seen in the mysql db migrations
21:05:27 <mriedem> #link https://bugs.launchpad.net/nova/+bug/1739517
21:05:28 <openstack> Launchpad bug 1739517 in OpenStack Compute (nova) "TestNovaMigrationsMySQL randomly fails with "sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically."" [High,Confirmed]
21:05:44 <mriedem> i don't really know what is causing that, and it is hitting on all branches, so it's not like a recent regression
21:05:56 <mriedem> i wonder if there was a mysql update in the images we're testing on
21:06:27 <mriedem> otherwise i've been seeing quite a few random CI failures, reporting bugs and opening e-r queries
21:06:28 <mriedem> #link http://status.openstack.org/elastic-recheck/
21:06:40 <mriedem> e-r seems to not be reporting on patches though
21:06:55 <mriedem> 3rd party CI status
21:07:03 <mriedem> #info zKVM CI was made non-voting due to recurring failures
21:07:07 <mriedem> did that last week
21:07:16 <mriedem> questions about bugs?
21:07:32 <mriedem> #topic stable branch status
21:07:36 <mriedem> #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z
21:07:41 <mriedem> #info Pike 16.0.4 released
21:07:46 <mriedem> #link stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z
21:07:55 <mriedem> #link Ocata 15.1.0 release request: https://review.openstack.org/#/c/529100/
21:07:55 <patchbot> patch 529100 - releases - nova: release ocata 15.1.0
21:08:01 <mriedem> #link stable/newton: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/newton,n,z
21:08:05 <mriedem> #link Newton 14.1.0 release request: https://review.openstack.org/#/c/529102/
21:08:05 <patchbot> patch 529102 - releases - nova: release newton 14.1.0
21:08:14 <mriedem> ^ will be newton-eol unless something else comes up
21:08:22 <mriedem> but, we might just end up waiting until january at this point...
21:08:29 <mriedem> will need to talk with tonyb
21:08:42 <mriedem> questions about stable?
21:08:53 <mriedem> #topic subteam highlights
21:09:00 <mriedem> there was no cellsv2 meeting this week, or next week
21:09:06 <mriedem> bugs tracked in the wiki: https://wiki.openstack.org/wiki/Meetings/NovaCellsv2#Agenda
21:09:11 <mriedem> edleafe: scheduler stuff?
21:09:13 <edleafe> Just a quick meeting - just checking in on status of the different patch series
21:09:39 <mriedem> that it?
21:09:59 <mriedem> alright
21:10:04 <mriedem> not sure what happened in the api meeting
21:10:12 <mriedem> probably same - talking about status of patches
21:10:20 <mriedem> there was no notification meeting this week, or next
21:10:25 <mriedem> there was a nova/cinder meeting today
21:10:32 <mriedem> two things
21:10:33 <mriedem> 1. Working on multi-attach patches in nova: https://review.openstack.org/#/q/topic:bp/multi-attach-volume+status:open
21:10:38 <mriedem> 2. Need to get Tempest patch updated: https://review.openstack.org/#/c/266605/
21:10:39 <patchbot> patch 266605 - tempest - Add a test for cinder multiattach
21:10:48 <mriedem> and i guess,
21:10:52 <mriedem> 3. cinder multiattach spec https://review.openstack.org/#/c/523608/
21:10:53 <patchbot> patch 523608 - cinder-specs - Propose multi-attach using V3 Attachment API's
21:11:02 <mriedem> ^ is mostly about policy rules that will be added to cinder
21:11:09 <mriedem> and how things are going to work with the volume types
21:11:21 <mriedem> #topic stuck reviews
21:11:26 <mriedem> there is nothing on the agenda
21:11:30 <mriedem> anyone have something to mention here?
21:11:47 <mriedem> #topic open discussion
21:11:54 <mriedem> i added one item
21:11:56 <mriedem> Should we make an exception for this super trivial feature parity vmware blueprint change? https://review.openstack.org/#/c/448034/
21:11:57 <patchbot> patch 448034 - nova - VMware: add support for different firmwares
21:12:13 <mriedem> i don't like making exceptions because then people think all blueprints can get exceptions,
21:12:17 <mriedem> but this one is really really small
21:12:22 <mriedem> so i'm inclined to say it's fine
21:12:28 <mriedem> any other opinions?
21:12:57 <melwitt> if it's super small I'd agree
21:13:11 <mriedem> alright, the ayes have it
21:13:21 <mriedem> anyone else have something to talk about?
21:13:58 <mriedem> nope; alright. i'm on vacation next week, back in january. hope everyone has a safe and happy whatever you'll be doing.
21:14:06 <mriedem> o/
21:14:08 <mriedem> #endmeeting