14:00:18 <mriedem> #startmeeting nova
14:00:19 <openstack> Meeting started Thu Oct 20 14:00:18 2016 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:23 <openstack> The meeting name has been set to 'nova'
14:00:27 <mriedem> hi who is around?
14:00:30 <edleafe> \o
14:00:36 <sfinucan> o/
14:00:40 * edleafe is expecting the shortest nova meeting ever
14:00:46 <takashin> o/
14:01:06 <itoader> o/
14:01:19 <johnthetubaguy> o/
14:01:26 <mriedem> ok let's run through this
14:01:31 <mriedem> #link agenda https://wiki.openstack.org/wiki/Meetings/Nova
14:01:34 <raj_singh> o/
14:01:35 <pkoniszewski> o/
14:01:43 <mriedem> #topic release news
14:01:46 <mriedem> #link Draft Ocata release schedule: https://wiki.openstack.org/wiki/Nova/Ocata_Release_Schedule
14:02:01 <mriedem> we'll decide the full schedule at the summit next week thursday afternoon
14:02:13 <mriedem> #topic summit planning
14:02:18 <mriedem> #link Nova Ocata design summit schedule: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Nova%3A
14:02:28 <mriedem> #link Questions for ops folks welcome for the Nova & Ops: https://etherpad.openstack.org/p/BCN-ops-nova
14:02:39 <mriedem> #help If you are chairing a session please work on getting your agenda written in the session etherpad: https://wiki.openstack.org/wiki/Design_Summit/Ocata/Etherpads#Nova
14:02:49 <cdent> o/
14:02:54 <mriedem> i'll probably be harassing some people about filling in their etherpads today
14:02:57 <mriedem> so watch out
14:03:00 <diana_clarke> o/
14:03:13 <mriedem> questions about the summit?
14:03:25 <mriedem> moving on
14:03:28 <mriedem> #topic Bugs (stuck/critical)
14:03:37 <mriedem> there are no critical bugs
14:03:46 <mriedem> gate status
14:03:47 <mriedem> #link check queue gate status http://status.openstack.org/elastic-recheck/index.html
14:03:55 <mriedem> *is really check queue status ^
14:04:07 <mriedem> the pycparser release blew up the works this week, but was quickly resolved
14:04:29 <wznoinsk> o/
14:04:41 <mriedem> 3rd party ci status is pretty quiet
14:04:50 <mriedem> vmware is moving their ci from nova-net to neutron
14:04:57 <mriedem> i'm assuming with nsx but haven't had that confirmed
14:05:10 <mriedem> and no one around from vmware to confirm
14:05:35 <mriedem> #topic Stable branch status: https://etherpad.openstack.org/p/stable-tracker
14:05:53 <mriedem> stable is pretty quiet
14:06:00 <mriedem> liberty and mitaka are locked down more or less
14:06:24 <mriedem> lyarwood is keeping stable/newton populated with backports
14:06:39 <mriedem> #topic subteam highlights
14:06:47 <mriedem> i don't think alaski had a cells v2 meeting this week
14:06:53 <mriedem> edleafe: scheduler meeting?
14:07:02 * edleafe is expecting the shortest nova meeting ever
14:07:06 <edleafe> oops
14:07:11 <edleafe> damn coppy pasta
14:07:19 <edleafe> Quick meeting. Mostly concerned with identifying the stuff we need to have ready for Barcelona discussions.
14:07:22 <edleafe> jaypipes was missing, so not a lot of argument :)
14:07:23 <mriedem> good to know you had that zinger planned :)
14:07:24 <edleafe> That's it.
14:07:34 <edleafe> Always prepared!
14:08:09 <mriedem> ok i know he's in spain already
14:08:28 <mriedem> tdurakov: live migration meeting highlights?
14:08:38 <tdurakov> hi, status:
14:08:38 <tdurakov> - ceph re-enablement: https://review.openstack.org/#/c/387836/ - almost there
14:08:38 <tdurakov> - grenade job for live-migration: https://review.openstack.org/#/q/topic:lm-grenade
14:09:16 <mriedem> thanks
14:09:22 <tdurakov> reviews for grenade topic are very welcome
14:09:37 <mriedem> tdurakov: i expect those to probably sit until after the summit
14:09:41 <mriedem> because of QA people traveling
14:09:52 <mriedem> might want to ping sdague about those though, he's around next week
14:10:07 <mriedem> alex_xu: api meeting highlights?
14:10:36 <mriedem> moving on
14:10:38 <johnthetubaguy> mostly chatted about the summit and the param validation
14:10:59 <mriedem> param validation wrt sort/filter parametres?
14:11:23 <johnthetubaguy> more generally
14:11:26 <johnthetubaguy> but yes, that too
14:11:27 <mriedem> ok. i know there are a few api impact specs out there i've been reviewing
14:11:39 <mriedem> i wanted dansmith to review the v3 diagnostics one
14:11:59 <mriedem> ok thanks john, moving on
14:12:05 <mriedem> i don't think there was an sriov/pci meeting
14:12:07 <mriedem> lbeliveau: ^?
14:12:17 <lbeliveau> nope
14:12:22 <wznoinsk> nope, skipped last two weeks till summit
14:12:24 <mriedem> ok
14:12:30 <mriedem> gibi: notifications meeting highlights?
14:12:54 <mriedem> maybe there wasn't a notifications meeting
14:12:59 <mriedem> i need to update my calendar for ocata
14:13:07 <mriedem> 3 things on notifications i guess
14:13:14 <mriedem> 1. there are several specs up for new notifications
14:13:27 <mriedem> 2. several of those specs worry me about performance overhead - more on that in the dev ML
14:13:42 <mriedem> 3. the versioned notification transformation series - just a general reminder for reviews
14:13:48 <mriedem> https://review.openstack.org/#/q/topic:bp/versioned-notification-transformation-ocata
14:14:11 <mriedem> #topic stuck reviews
14:14:15 <mriedem> there is nothing in the agenda
14:14:23 <mriedem> anyone have a stuck review they want to bring up?
14:14:24 <johnthetubaguy> mriedem: overhead due to rabbit load? or just creating objects?
14:14:30 <mriedem> johnthetubaguy: and db
14:14:31 <johnthetubaguy> sorry, I am being slow today
14:14:39 <mriedem> johnthetubaguy: details are in the ML thread
14:14:47 <johnthetubaguy> mriedem: OK, I will go read that
14:15:02 <mriedem> johnthetubaguy: http://lists.openstack.org/pipermail/openstack-dev/2016-October/106120.html
14:15:22 <mriedem> #topic open discussion
14:15:26 <mriedem> 2 items in the agenda
14:15:32 <mriedem> (claudiub): Specless blueprint for PCI passthrough support in the hyper-v driver: https://blueprints.launchpad.net/nova/+spec/hyper-v-pci-passthrough
14:15:36 <claudiub|2> o/
14:16:05 <mriedem> i asked claudiub|2 to bring that up in the sriov/pci meeting, but the next one is after the summit
14:16:14 <mriedem> i'm ok with a specless blueprint on that since it's feature parity
14:16:31 <mriedem> i would like lbeliveau, wznoinsk, sfinucan, moshele and others to take a look though
14:16:40 <mriedem> as usual my main concern is CI coverage
14:16:54 <mriedem> claudiub|2: what's the plan for CI testing that?
14:16:59 <claudiub|2> that is a bit trickier
14:17:15 <claudiub|2> that is a windows server 2016 feature, and we have 2012 r2 in the ci
14:17:19 <mriedem> it would have to be a separate job
14:17:43 <mriedem> i'd suggest talking to moshele, lbeliveau and wznoinsk about how the libvirt stuff is tested with the mellanox and intel nfv CIs
14:17:56 <mriedem> the intel pci ci uses custom tests i believe
14:17:59 <mriedem> with a tempest plugin
14:18:17 <mriedem> anyway, that's my only reservation
14:18:25 <mriedem> johnthetubaguy: you ok with specless bp on that one?
14:18:30 <claudiub|2> interesting. will talk about them about the tests
14:18:44 <johnthetubaguy> its got minimal wide impact, so that seems OK
14:18:50 <mriedem> agreed
14:18:53 <johnthetubaguy> FWIW, I think reno really helps us here these days
14:19:05 <claudiub|2> as far as the ci goes, afaik, we'll have 2016 nodes when it is released
14:19:15 <mriedem> johnthetubaguy: reno as a replacement for ci testing? :)
14:19:39 <mriedem> "new feature, it's untested, buyer beware!"
14:19:41 <johnthetubaguy> mriedem: heh, I wish that were possible, I mean worrying about specs for documenting the new feature from the user point of view
14:19:56 <mriedem> yeah i wasn't thinking about the docs for it really
14:20:00 <johnthetubaguy> well, true, I want that to be feature classification I guess
14:20:02 <mriedem> i don't think reno replaces docs fwiw
14:20:14 <mriedem> and we lean on reno too heavily for that
14:20:24 <mriedem> but i digress
14:20:25 <johnthetubaguy> very true, but specs aren't really ops docs either
14:20:36 <claudiub|2> will talk with the hyper-v ci if we can do it any time earlier
14:20:38 <mriedem> it's like we need a...docs team or something
14:20:50 <mriedem> moving on
14:20:51 <mriedem> (claudiub): Specless blueprint for the continuation of Hyper-V BDM support: https://blueprints.launchpad.net/nova/+spec/hyper-v-block-device-mapping-support-ocata
14:21:16 <claudiub|2> yeah. the blueprint only has 2 patches that remained from the previous cycle
14:21:24 <claudiub|2> and they are small
14:21:40 <mriedem> that bp always seemed to do too much in it for me
14:21:49 <mriedem> b/c it also had device tagging in it for newton i think
14:21:52 <mriedem> or part of that
14:22:06 <claudiub|2> the device tagging was on top of it
14:22:08 <mriedem> claudiub|2: can we split that into 2 bps and work them separately, but otherwise i'm +2 on the specless bp for those
14:22:17 <mriedem> they are separate features
14:22:19 <claudiub|2> sure
14:22:23 <claudiub|2> will do
14:22:33 <mriedem> thanks, split them up and hit me up in -nova and i'll approve
14:22:42 <claudiub|2> ok, ty!
14:22:53 <mriedem> ok anything else for open discussion?
14:23:19 <mriedem> alright, that's it then. thanks everyone, see some of you next week. safe travels.
14:23:24 <mriedem> #endmeeting