21:00:08 <mriedem> #startmeeting nova
21:00:09 <openstack> Meeting started Thu Jan 31 21:00:08 2019 UTC and is due to finish in 60 minutes.  The chair is mriedem. 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:13 <openstack> The meeting name has been set to 'nova'
21:00:21 <mriedem> hello
21:00:23 <takashin> o/
21:00:41 <edleafe> \o
21:00:53 <dansmith> o/
21:01:17 <mriedem> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
21:01:22 <mriedem> ok let's get started
21:01:29 <mriedem> #topic Release News
21:01:34 <mriedem> #link Stein release schedule: https://wiki.openstack.org/wiki/Nova/Stein_Release_Schedule
21:01:48 <mriedem> #info s-3 feature freeze is March 7 so we have ~5 weeks
21:01:57 <mriedem> #link Stein runway etherpad: https://etherpad.openstack.org/p/nova-runways-stein
21:02:01 <mriedem> #link runway #1: https://blueprints.launchpad.net/nova/+spec/per-instance-libvirt-sysinfo-serial (Kevin_Zheng) [END 2019-02-04] https://review.openstack.org/#/c/619953/
21:02:06 <mriedem> more on ^ later
21:02:11 <mriedem> #link runway #2: https://blueprints.launchpad.net/nova/+spec/flavor-extra-spec-image-property-validation (jackding) [END 2019-02-07] https://review.openstack.org/#/c/620706/
21:02:22 <mriedem> #link runway #3: https://blueprints.launchpad.net/nova/+spec/vrouter-hw-offloads (jangutter) [END 2019-02-11] https://review.openstack.org/#/c/572082/
21:02:33 <mriedem> ^ needs one more core and it's pretty simple
21:02:48 <mriedem> #link https://etherpad.openstack.org/p/nova-stein-blueprint-status
21:02:55 <mriedem> i also went through and updated ^ todya
21:02:56 <mriedem> *today
21:03:07 <mriedem> questions about the release?
21:03:20 <mriedem> #topic bugs
21:03:27 <mriedem> there are no critical bugs
21:03:32 <mriedem> #link 57 new untriaged bugs (0 change since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
21:03:38 <mriedem> #link 4 untagged untriaged bugs (up 2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW
21:03:44 <mriedem> #link bug triage how-to: https://wiki.openstack.org/wiki/Nova/BugTriage#Tags
21:03:48 <mriedem> #help need help with bug triage
21:03:53 <mriedem> gate status
21:03:57 <mriedem> #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
21:04:02 <mriedem> #link mriedem's gate status email from last week: http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002090.html
21:04:11 <mriedem> really two big issues for the gate
21:04:15 <mriedem> #link http://status.openstack.org/elastic-recheck/gate.html#1813198 was the biggest issue but test_subnet_details is now being skipped until fixed
21:04:19 * efried waves late
21:04:24 <mriedem> because of the skip on ^ the gate is flowing again
21:04:32 <mriedem> bence has a fix up for it in tempest also
21:04:38 <mriedem> #help subunit parser failures are now our biggest gate issue: http://status.openstack.org/elastic-recheck/gate.html#1813147
21:04:43 <mriedem> ^ this is our big issue for nova now
21:05:02 <mriedem> from the ML thread above, it looks like neutron and cinder have had to deal with this also so there are some existing patches we should look at copying in nova
21:05:07 <mriedem> need someone to do that work though
21:05:19 <mriedem> #help The legacy-grenade-dsvm-neutron-multinode-live-migration (non-voting) job is broken: https://bugs.launchpad.net/nova/+bug/1813216
21:05:21 <openstack> Launchpad bug 1813216 in OpenStack Compute (nova) "legacy-grenade-dsvm-neutron-multinode-live-migration failing with "is not on shared storage: Shared storage live-migration requires either shared storage or boot-from-volume with no local disks." since Jan 21" [Undecided,Confirmed]
21:05:41 <mriedem> ^ this clearly regressed recently but I'm not sure due to what, it could have been a change in devstack but we need more eyes
21:06:10 <mriedem> if it's going to continue to fail and no one looks, i think i'll just push it to the experimental queue, but that would be unfortunate because that's the only job where we do n-1 and back live migration
21:06:29 <mriedem> #link 3rd party CI status http://ciwatch.mmedvede.net/project?project=nova&time=7+days
21:06:47 <mriedem> i don't really have any news there except several of the 3rd party CI jobs look spotty, either not running often enough or failing a lot
21:07:07 <mriedem> #topic reminders
21:07:09 <mriedem> #link Stein Subteam Patches n Bugs: https://etherpad.openstack.org/p/stein-nova-subteam-tracking
21:07:14 <mriedem> #info Chinese New Year is next week.
21:07:24 <mriedem> so expect some people to be out
21:07:35 <mriedem> #topic Stable branch status
21:07:41 <mriedem> #link stable/rocky: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/rocky,n,z
21:07:47 <mriedem> quite a few easy rocky backports that could be approved
21:07:53 <mriedem> #link stable/queens: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/queens,n,z
21:08:05 <mriedem> the queens backlog is getting big so we need to flush that soon
21:08:16 <mriedem> but there are also some hairy backports in there
21:08:20 <mriedem> #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z
21:08:29 <mriedem> lots of backports for pike
21:08:42 <mriedem> and a few stragglers for ocata https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata
21:08:59 <mriedem> #topic subteam highlights
21:09:03 <mriedem> Scheduler (efried)
21:09:18 <efried> #link n-sch meeting minutes http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-01-28-14.01.html
21:09:26 <efried> We brought up and got status on several in-progress efforts, including
21:09:26 <efried> #link bandwidth https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/bandwidth-resource-provider
21:09:26 <efried> #link libvirt reshaper https://review.openstack.org/#/c/599208/
21:09:26 <efried> #link xen reshaper (dead in the water for lack of maintainer) https://review.openstack.org/#/c/520313/
21:09:43 <efried> #link placement-status https://review.openstack.org/#/c/632600/
21:10:06 <efried> #link reportclient-to-placement traffic reduction series https://review.openstack.org/#/c/615695/
21:10:07 <mriedem> the bw provider changes are merging slowly
21:10:25 <mriedem> gibi is out the rest of this week and might not be around much next week
21:10:40 <mriedem> i will do some follow ups on some of the already +2ed changes in that series
21:10:45 <efried> traffic reduction series also merging slowly
21:11:19 <efried> oh, I guess current bottom is https://review.openstack.org/#/c/615705/
21:11:45 <efried> That's all for n-sch
21:12:04 <mriedem> agenda says no api office hour this week
21:12:07 <mriedem> so moving on
21:12:13 <mriedem> #topic Stuck reviews
21:12:24 <mriedem> ok this one is mine
21:12:24 <mriedem> per-instance serial number: https://review.openstack.org/#/c/619953/ is stuck on the ML thread http://lists.openstack.org/pipermail/openstack-discuss/2019-January/thread.html#2037  proposing to just always use instance uuid for the serial, don't add  new extra spec / image property / config option choice, and effectively  deprecate the [libvirt]/sysinfo_serial option.
21:12:43 <mriedem> #link ML thread summary http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002267.html
21:13:00 <mriedem> i tried to summarize the mess and propose my preference for what we'd do at the end of that,
21:13:12 <mriedem> mnaser and sean-k-mooney seem to agree,
21:13:24 <mriedem> so i guess waiting on jaypipes and stephenfin since they brought up the idea to just always use instance.uuid for the series
21:13:26 <mriedem> *serial
21:13:37 <stephenfin> mriedem: I agree with you
21:13:40 <mriedem> dansmith: if you have thoughts on ^ that would be appreciated
21:13:42 <mriedem> stephenfin: ok
21:13:56 <dansmith> um
21:13:59 <mriedem> if you go back over the old CVE launchpad bug for how sysinfo_serial came about it's kind of a mess
21:14:06 <dansmith> gotta keep that in the api db I guess
21:14:17 <mriedem> dansmith: no, it's nothing in the db
21:14:36 <mriedem> it's just something we shove into the guest xml for libvirt today
21:14:39 <dansmith> if it's a serial number you do, but.. I'll read
21:14:43 <mriedem> ok
21:14:47 <dansmith> oh, are you talking disk serial?
21:14:52 <mnaser> smbios serial
21:14:53 <mriedem> no
21:14:55 <mriedem> right
21:15:01 <dansmith> if you need it to be unique then it has to be in the apidb
21:15:11 <mriedem> the instance.uuid is already in the db...
21:15:15 <mnaser> isnt it a uuid? we can just use the actual instance uuid?
21:15:17 <mriedem> that's what is proposed to use
21:15:35 <dansmith> okay, okay, you said serial number so I assumed an actual serial number
21:15:42 <dansmith> but yeah, if it need not be SERIAL
21:15:45 <dansmith> then uuid.. :)
21:15:50 <mriedem> the bigger question is do we always do that and deprecate the old option to use the host serial
21:16:08 <mriedem> but, the "summary" email lays it out for you
21:16:34 <mriedem> ok moving on
21:16:40 <mriedem> #topic open discussion
21:16:44 <mriedem> there is nothing on the agenda
21:16:52 <mriedem> does anyone have anything to bring up here?
21:17:12 <mriedem> oh i'll mention,
21:17:30 <mriedem> i did send an email to gibi and alex_xu asking if alex wanted to take over https://blueprints.launchpad.net/nova/+spec/remove-force-flag-from-live-migrate-and-evacuate since gibi hasn't started it yet
21:17:42 <mriedem> but then i remembered alex is going to be gone next week for the new year holiday
21:17:58 <mriedem> anyway, looking for someone to work on that so it doesn't fall out of stein so we'll see what alex says
21:18:24 <mriedem> if there is nothing else we can close the meeting
21:18:32 <mriedem> thanks
21:18:34 <mriedem> #endmeeting