21:00:08 <mriedem> #startmeeting nova
21:00:09 <openstack> Meeting started Thu Jan  4 21:00:08 2018 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:12 <openstack> The meeting name has been set to 'nova'
21:00:17 <edleafe> \o
21:00:17 <mriedem> hi
21:00:22 <takashin> o/
21:00:55 <mriedem> takashin: i hope you sleep in on other days
21:01:09 <jaypipes> o/
21:01:16 <takashin> mriedem: Hi.
21:01:20 <efried> \o
21:01:52 <mriedem> alright let's get started
21:01:55 <mriedem> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
21:01:59 <mriedem> #topic release news
21:02:05 <mriedem> #link Queens release schedule: https://wiki.openstack.org/wiki/Nova/Queens_Release_Schedule
21:02:11 <mriedem> #link Release schedule recap email: http://lists.openstack.org/pipermail/openstack-dev/2018-January/125953.html
21:02:33 <mriedem> thanks to efried for writing up details on the placement work
21:02:41 <mriedem> #info Jan 18: non-client library (oslo, os-vif, os-brick, os-win, os-traits, etc) release freeze
21:03:07 <mriedem> as i said in the recap email, i'll be out the week of jan 15, so i'll plan on doing the final non-client library releases at the end of next week
21:03:14 <mriedem> so let me know if you need to get something into os-vif or os-traits
21:03:29 <mriedem> #info Jan 25: q-3 milestone, Feature Freeze, final python-novaclient release, requirements freeze, Soft String Freeze
21:03:43 <efried> jaypipes Was there os-traits work you were going to do for ironic?  RAID stuff or whatever?
21:03:54 <efried> maybe you did and I just wasn't watching.
21:04:06 <efried> (From the halloween meeting)
21:04:13 <mriedem> https://review.openstack.org/#/q/project:openstack/os-traits+status:open
21:04:21 <mriedem> https://review.openstack.org/#/q/project:openstack/os-vif+status:open+branch:master
21:04:28 <jaypipes> efried: I have not done anything, no. my ironic work is focusing around aggregate affinity stuff right now.
21:04:46 <efried> ight
21:05:33 <mriedem> #info Blueprints: 53 targeted, 53 approved, 17 complete (2 completed since the last meeting)
21:05:47 <mriedem> slowly making progress
21:06:41 <mriedem> questions about the release?
21:06:50 <mriedem> #topic bugs
21:06:58 <mriedem> nothing marked critical
21:07:02 <mriedem> #info 43 new untriaged bugs (down 1 since the last meeting)
21:07:23 <mriedem> did some triage last night to help get those numbers down, the usual misconfiguration / support request bugs to flush out
21:07:48 <mriedem> #link tracking queens rc blockers here https://etherpad.openstack.org/p/nova-queens-release-candidate-todo
21:08:00 <mriedem> #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
21:08:06 <mriedem> gate on master is okish,
21:08:11 <mriedem> gate on stable/pike has been busted for about 3 weeks,
21:08:18 <mriedem> there are patches floating around to get that working again
21:08:33 <mriedem> 3rd party ci on master, i don't have any news
21:08:41 <mriedem> #topic reminders
21:08:44 <mriedem> #link queens blueprint status https://etherpad.openstack.org/p/nova-queens-blueprint-status
21:08:54 <mriedem> I'm continuing to update stuff in there
21:09:06 <mriedem> #topic stable brach status
21:09:08 <mriedem> #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z
21:09:13 <mriedem> #link Etherpad for bugs tracked for Pike backports: https://etherpad.openstack.org/p/nova-pike-bug-fix-backports
21:09:19 <mriedem> #link stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z
21:09:24 <mriedem> #info Ocata 15.1.0 released
21:09:30 <mriedem> #link stable/newton: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/newton,n,z
21:09:35 <mriedem> #link Newton 14.1.0 release request: https://review.openstack.org/#/c/529102/
21:09:41 <mriedem> newton eol is dependent on a series of changes
21:09:48 <mriedem> https://review.openstack.org/#/q/I1aa3ca6cc70cef65d24dec1e7db9491c9b73f7ab
21:10:13 <mriedem> #topic subteam highlights
21:10:21 <mriedem> i see that dansmith is lurking
21:10:25 <mriedem> cellsv2?
21:10:37 <dansmith> ohai
21:10:52 <dansmith> we had a meeting, not a lot changed since last year being that most people weren't around
21:11:03 <dansmith> we went over some bugs and things that are waiting review,
21:11:20 <dansmith> but nothing major that is new of note that I recall
21:11:32 <mriedem> yup
21:11:37 <mriedem> edleafe: scheduler?
21:11:41 <edleafe> No meeting this week.
21:11:48 <edleafe> We're slowly emerging from the holiday coma.
21:12:10 * jaypipes working on nested resource providers integration with allocation candidates.
21:12:12 <edleafe> So good progress, and it should continue as we are all back
21:12:24 <edleafe> that's about it
21:12:34 <mriedem> still looking for a meeting chair? or did efried take that?
21:12:37 <efried> Some discussion about having a new host (or a new time) for sched meetings.
21:13:03 <edleafe> yeah, either we move the meeting or efried takes over for now
21:13:15 <mriedem> ok
21:13:16 <edleafe> at least until I can get my office situation resolved
21:13:30 <efried> edleafe What time would work?  An hour later?
21:13:39 <edleafe> maybe 2
21:13:54 <edleafe> I don't get to the office now until around 9:30 CST
21:14:13 <mriedem> see what's available on http://eavesdrop.openstack.org/ maybe
21:14:31 <efried> Okay, well, I suppose rather than moving it and then moving it back when edleafe gets settled, I can take over for a couple weeks.
21:14:31 <mriedem> i know we had like a bug team meeting in the past which was dropped, so that slot should be open
21:14:38 <mriedem> or that
21:14:40 <edleafe> last time we moved it we surveyed the main contributors to find a time that worked for all
21:14:57 <efried> We don't have a lot of lead time for that right now.
21:15:08 <edleafe> yeah, we could do this next week
21:15:15 <edleafe> hold the meeting on monday as usual for now
21:15:26 <mriedem> ok, so how about just same time for now and settle if later once we're out of the shit show that is closing out queens
21:15:29 <efried> Right, so I'll chair for now, and if your situation doesn't "improve" long term...
21:15:32 <edleafe> so efried - you good for running it on monday?
21:15:36 <efried> Yes
21:15:47 <edleafe> cool
21:16:09 <mriedem> ok i'm not sure if there was an api meeting this week
21:16:14 <mriedem> or if anyone here was there
21:16:25 <mriedem> there was no notification meeting this week
21:16:32 <mriedem> for cinder
21:16:32 <mriedem> Working on multi-attach patches in nova: https://review.openstack.org/#/q/topic:bp/multi-attach-volume+status:open
21:16:41 <mriedem> #link Tracking multiattach issues and TODOs here: https://etherpad.openstack.org/p/multi-attach-volume-queens
21:17:05 <mriedem> i found some nasty qemu/libvirt issues with multiattach last night, so we've hit a bump
21:17:17 <mriedem> currently working on workarounds for testing
21:17:32 <mriedem> #topic stuck reviews
21:17:36 <mriedem> there was nothing in the agenda
21:17:45 <mriedem> #topic open discussion
21:17:50 <mriedem> there is one item
21:17:54 <mriedem> (ab2434 / hemanth-n): Blueprint review https://blueprints.launchpad.net/nova/+spec/add-physical-pci-info-for-sriov-ports
21:18:11 <ab2434> hi. I'd like to discuss https://blueprints.launchpad.net/nova/+spec/add-physical-pci-info-for-sriov-ports
21:18:13 <mriedem> my understanding is this is just adding/handling "pf_pci_slot" in the binding profile
21:18:21 <ab2434> correct
21:18:29 <mriedem> are there changes on the neutron side for this?
21:18:34 <ab2434> no
21:18:54 <mriedem> what is consuming this then?
21:19:04 <mriedem> vif plugin?
21:19:09 <ab2434> yes
21:19:50 <ab2434> this is the codereview https://review.openstack.org/#/c/530107/
21:20:27 <mriedem> would need jaypipes or someone more familar with sriov/pci stuff to comment here
21:20:29 <mriedem> or moshele
21:20:47 <mriedem> i don't really want to add this into the mix when we're <3 weeks from feature freeze for queens
21:21:20 <ab2434> when can we target this then?
21:21:44 <mriedem> rocky is the next release
21:21:59 <mriedem> queens feature freeze is jan 25
21:22:15 <mriedem> we cut queens rc1 on feb 8 and then open master for rocky dev
21:22:27 <ab2434> ok
21:22:54 <jackie-truong> Unsure if this is the right venue for this, but the nova-queens-blueprint-status etherpad mentioned that Johns Hopkins needs to sync up with Sean on the certificate validation feature, but he is no longer available. Who should we be talking to? We created an etherpad (https://etherpad.openstack.org/p/queens-nova-certificate-validation) to walk through usage and testing.
21:22:55 <mriedem> i'm particularly uneasy about this https://review.openstack.org/#/c/530107/1/nova/pci/utils.py
21:23:08 <mriedem> if ^ will work for all environments
21:23:37 <mriedem> jackie-truong: honestly i'm not sure
21:23:52 <mriedem> there are lots of things in flight right now and i expect a lot of blueprints to get deferred
21:24:02 <mriedem> which is not the answer anyone wants to hear
21:24:29 <efried> mriedem That (utils.py method) will definitely break PowerVM.  We don't have sysfs on the hypervisor.
21:24:44 <efried> We have to avoid the other sysfs
21:24:48 <mriedem> efried: powervm is what i was thinking of :)
21:24:49 <efried> -usin' code paths for that reason.
21:25:06 <efried> Aw, that's so sweet
21:26:08 <jaypipes> ab2434: we already store the physical function's PCI address in the pci_devices table so there shouldn't be a need to to the get_pf_pci_by_vfpci_adddress() function at all. mriedem, since this blueprint is proposing adding (yet another) key/value to the binding profile (and nothing else), I'm ok with it.
21:26:36 <mriedem> jaypipes: as long as they don't try to read files from disk...
21:26:53 <jaypipes> mriedem: there's no need for that. see my comment above.
21:26:57 <jaypipes> mriedem: I will review the patch.
21:27:02 <mriedem> jaypipes: right - want to mention that in the change?
21:27:03 <mriedem> thanks
21:27:07 <ab2434> thanks
21:27:07 <jaypipes> yes, of course
21:27:24 <mriedem> ok anything else?
21:27:27 <jackie-truong> mriedem: Okay. We added a link to the usage and testing etherpad in the nova-queens-blueprint-status for now. We'll keep an eye out for any questions.
21:27:46 <mriedem> jackie-truong: yup, thanks for that
21:28:08 <mriedem> ok if nothing else, we'll wrap up
21:28:23 <mriedem> #endmeeting