22:01:24 <armax> #startmeeting neutron_drivers
22:01:24 <openstack> Meeting started Thu Aug  4 22:01:24 2016 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:01:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:27 <openstack> The meeting name has been set to 'neutron_drivers'
22:01:34 <armax> let’s start, and see who shows up
22:01:48 <armax> perhaps we can have a quick one
22:02:19 <armax> did any of you see the email I sent eaerlier today?
22:02:27 <HenryG> yes
22:02:31 <amotoki> I just saw it
22:02:40 <armax> amotoki: makes sense?
22:02:50 <amotoki> yes
22:03:07 <armax> #link http://lists.openstack.org/pipermail/openstack-dev/2016-August/100881.html
22:03:16 <armax> amotoki: now that I have you here
22:03:22 <armax> any updaet on https://blueprints.launchpad.net/neutron/+spec/dhcp-options-per-subnet?
22:03:34 <armax> the blueprint is full of cobwebs and dust
22:03:42 <armax> do we just forget it about it?
22:03:48 <armax> and move on with our lives?
22:04:19 <armax> last update is on https://bugs.launchpad.net/neutron/+bug/1512666/comments/20
22:04:19 <openstack> Launchpad bug 1512666 in neutron "[RFE] Allow for per-subnet/network dhcp options" [Wishlist,Incomplete] - Assigned to Sam Betts (sambetts)
22:04:22 <kevinbenton> Hi
22:04:27 <armax> kevinbenton: hi
22:05:20 <amotoki> I think this is not so high priority for ironic folks. It helps us reduce configuraitons, but it is not a requirement.
22:06:18 <armax> amotoki: ok, so I suppose we’ll have to shelve for Newton?
22:06:35 <amotoki> I think so.
22:06:45 <amotoki> this is useful when it is combined with the other one (serve unknown DHCP port)
22:07:02 <amotoki> but it is not so useful only with that.
22:07:46 <armax> ok
22:09:21 <armax> amotoki: as for https://blueprints.launchpad.net/neutron/+spec/neutron-in-tree-api-ref
22:09:33 <armax> do you want someone that can help with the approval process?
22:10:07 <amotoki> i'd like to discuss here it is okay with self-approve.
22:10:19 <amotoki> this is just the reason I make the approver blank.
22:10:34 <HenryG> I can help with that
22:10:37 <armax> amotoki: what do to you mean exactly?
22:10:56 <HenryG> Put me as the approver
22:10:59 <amotoki> I think there is some place to track the whole effort. some link.
22:11:12 <amotoki> *some link in commit message.
22:11:21 <armax> HenryG: ok
22:11:28 <amotoki> it helps us track the whole efforts
22:11:37 <armax> amotoki: keep me in the loop too
22:11:42 <HenryG> amotoki: someone from docs?
22:12:06 <amotoki> HenryG: nobody at now
22:12:52 <amotoki> I think we can ask Anne to check some of reviews. I will contact her later.
22:14:01 <armax> amotoki: those are the things that are on your radar but the looks of https://blueprints.launchpad.net/neutron/newton/+assignments
22:14:12 <armax> amotoki: obviously you’re helping with the OSC too
22:15:00 <amotoki> yeah. fwaas folks contacted me for fwaas CLI.
22:15:22 <amotoki> they want to start FWaaS v2 CLI impl.
22:15:22 <armax> I’ll sync up with carl_baldwin about the latest status of the bp’s assigned to him
22:15:35 <armax> amotoki: any idea where FWaaS v2 effort is at in general?
22:16:22 <amotoki> I am not following FWaaS v2 progress itself.
22:16:51 <amotoki> is anyone watching it?
22:17:06 <armax> the entire list of commits between Feb and now fits into two gerrit pages
22:17:08 <armax> that’s not good
22:17:44 <armax> neutron’s two pages view covers just one week
22:17:50 <armax> oh well
22:17:52 <amotoki> most patches are marked as WIP...
22:18:17 <armax> ok, we’ll try to reach out to sridar
22:18:19 <armax> offline
22:18:31 <armax> HenryG: now that mother all of patches went in
22:18:37 <armax> for Keystone v5343
22:18:41 <armax> what’s next?
22:19:00 <HenryG> project_id in/out of API
22:19:11 <armax> ack
22:19:15 <HenryG> And then incremental renames internally
22:19:18 <armax> you got a WIPPY patch?
22:19:27 <armax> I did see Ihar starting somewhere
22:19:35 <armax> I wondered if he was coordinating with you
22:19:58 <HenryG> no, but I will try to get some coordination started
22:20:05 <armax> ok
22:20:22 <HenryG> dasm has indicated he will propose an API patch soon
22:20:24 <armax> one thing worth considering is whether we wanna do the rename in one bulk after feature freeze
22:20:34 <armax> like we did for other massive rename efforts
22:20:38 <armax> it worked well in the past
22:20:40 <dasm> HenryG: yes. that's the plan
22:20:42 <HenryG> I'll keep that in mind
22:21:06 <armax> ok none of the other approvers for blueprints are in channel
22:21:10 <armax> by the looks of it
22:21:13 <amotoki> bulk rename sounds good.
22:21:16 <armax> kevinbenton: routed networks?
22:21:41 <armax> rossella_s and ajo are way past their bedtime
22:21:49 <armax> I’ll reach out to them offline
22:21:52 <kevinbenton> Still proceeding
22:22:00 <kevinbenton> Not sure how much is left
22:22:02 <armax> I need to sync up with ryan about the BGP hingy
22:22:13 <kevinbenton> carl_baldwin around?
22:22:17 <haleyb> https://review.openstack.org/#/q/topic:bp/routed-networks shows good progress
22:22:23 <armax> kevinbenton: can we get a progress bar like type of update?
22:22:33 <armax> 70%, 50%, 90%?
22:22:47 <armax> last update on the bp goes back to Apr
22:23:08 <kevinbenton> Maybe like 70 if you include the scheduling changes in Nova
22:23:18 <armax> kevinbenton: ok
22:23:29 <kevinbenton> But higher if we exclude that since that won't make Newton anyway
22:23:30 <armax> ok folks
22:23:39 <armax> anything else you want to touch base on?
22:23:53 <kevinbenton> What's happening with VPNaas?
22:24:11 <kevinbenton> It's not like it's fundamentally broken, it just needs maintenance right?
22:25:18 <armax> not sure the latest
22:26:08 <kevinbenton> Ack
22:26:23 <amotoki> one missing point on vpnaas is document (networking guide and devref). if we keep only ipsec vpn, it looks maintenance mode.
22:27:44 <kevinbenton> Yeah, it seems like it would be worth keeping alive if it just needs bitrot prevention
22:27:52 <armax> yes, it seems like the projects will eventually rot
22:28:15 <armax> kevinbenton: but bitrot prevention can only get you so far
22:28:28 <armax> that said, we have a few folks from IBM who are helping
22:28:39 <kevinbenton> Ok
22:28:40 <armax> so I would expect mestery and regxboi to know more
22:29:05 <amotoki> I heard from mestery IBM uses it.
22:30:12 <kevinbenton> Yeah, there are others out there too
22:30:22 <kevinbenton> Seems to work with its known limitations
22:30:33 <armax> the project is there for anyone to pick it up
22:32:29 <armax> ok folks
22:32:31 <armax> anything else?
22:33:50 <amotoki> nothing from me
22:34:27 <HenryG> me neither
22:34:36 <armax> ok
22:34:42 <armax> thanks for joining!
22:35:04 <armax> #endmeeting