15:09:32 <tmorin> #startmeeting bgpvpn
15:09:33 <openstack> Meeting started Tue Jun 27 15:09:32 2017 UTC and is due to finish in 60 minutes.  The chair is tmorin. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:09:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:09:36 <openstack> The meeting name has been set to 'bgpvpn'
15:10:18 <tmorin> hi everyone
15:10:23 <tmorin> let's see who is around...
15:10:29 <pcarver_> hi
15:10:36 <tmorin> hi pcarver_!
15:11:07 <tmorin> hi doude matrohon timirnich lewo bfernando
15:11:46 <matrohon> hi tmorin
15:12:45 <tmorin> ok, let's start !
15:13:08 <tmorin> the main thing I have on the agenda is the BGPVPN routes control API extension
15:13:32 <tmorin> the API + doc has been +2+A last week, quickly after our meeting by kevinbenton
15:14:02 <tmorin> matrohon, you hadn't had the opportunity to comment, I hope that it's not a problem :-/
15:14:18 <matrohon> absolutly not
15:14:33 <tmorin> the good news is that since the implementation isn't done yet, we can revise all this
15:14:55 <tmorin> ok
15:15:14 <tmorin> I've updated the blueprint with a list of work items for an actual implementation
15:15:20 <tmorin> there are  a bunch of things there
15:15:54 <tmorin> #link https://blueprints.launchpad.net/bgpvpn/+spec/routes-control
15:16:06 <tmorin> the work items are:
15:16:06 <tmorin> * API, DB and driver hooks for Port Associations: TODO
15:16:06 <tmorin> * API, DB and driver hooks for new 'ports' attribute in BPGPVN resource: TODO
15:16:06 <tmorin> * API, DB and driver hooks for new 'advertise_extra_routes' attribute in Router Association: TODO
15:16:06 <tmorin> * OSC support for Port Associations: TODO
15:16:06 <tmorin> * OSC support for new 'advertise_extra_routes' attribute in Router Association: TODO
15:16:06 <tmorin> * python-neutronclient for Port Associations: TODO
15:16:07 <tmorin> * python-neutronclient for Port Associations for new 'advertise_extra_routes' attribute in Router Association: TODO
15:16:07 <tmorin> * Heat support for Port Associations: TODO
15:16:08 <tmorin> * Heat support for new 'advertise_extra_routes' attribute in Router Association: TODO
15:16:08 <tmorin> * dashboard: add the ability to control association attributes at create time, and to update them: TODO
15:16:09 <tmorin> * dashboard: support for Port Associations: TODO
15:16:09 <tmorin> * dashboard: support for new 'advertise_extra_routes' attribute in Router Association: TODO
15:16:10 <tmorin> * tempest: add/modify API tests for Port Associations and new attributes: TODO
15:16:30 <tmorin> ok, the IRC server truncated the list
15:16:45 <tmorin> the IRC server agrees that these are too many items :)
15:17:02 <tmorin> the good news is that we don't need all this on day 1 for a functional API
15:17:52 <tmorin> in particular Heat and horizon support are lower priority, and tempest additions are nice to have but not required on day 1 either
15:17:59 <matrohon> and you didn't mentionned TODOs for other providers
15:18:22 <tmorin> yep
15:18:28 <tmorin> do you think we should ?
15:18:48 <tmorin> other drivers are not in our tree anymore
15:18:59 <tmorin> but some are under openstack project and could refer to this blueprint
15:19:18 <tmorin> we can certainly add ODL
15:19:42 <pcarver> tmorin: It's a good general question about how we track feature support across backends (if we do)
15:19:55 <tmorin> pcarver: yes, I agree
15:20:38 <tmorin> my take is that something we could do is: track driver feature implementation in a document under networking-bgpvpn/doc/sources
15:21:22 <tmorin> this would give visibility to disparity in feature implementation, and a form of incentive to reduce it
15:21:29 <matrohon> that's the best we can do
15:21:40 <tmorin> and would give a view of the implementaton status for this API extension
15:21:58 <matrohon> we can also add blueritn to relevant launchpad project, once the API is coded
15:22:26 <pcarver> I agree, we can't make everything dependencies, we just need a place to document what's supported
15:23:31 <tmorin> pcarver: +1
15:24:42 <tmorin> I feel that today's meeting will quickly revolve around the question of who would volunteer to do X
15:24:43 <tmorin> :)
15:25:02 <tmorin> so let's jump head first
15:26:01 <tmorin> for this idea (documenting driver feature coverage) and the work items for the BGPVPN routes control extension... are there volunteers ?
15:26:24 <pcarver> I can work on a document
15:26:38 <tmorin> that's cool
15:26:43 <pcarver> probably just a table to start with, until/unless we come up with a better idea
15:26:56 <tmorin> that will be a good starting point
15:27:40 <tmorin> if you kickstart it, I can then try to help fill in the cells for which the answer would be unknown
15:27:49 <pcarver> ok
15:29:39 <tmorin> and for the bgpvpn routes control API extension... ?
15:29:55 <tmorin> there are a few items that should take a reasonable amount of time
15:30:20 <tmorin> I have started to work on the base: API/DB/driver-hooks
15:30:29 <tmorin> I should actually mark this on the blueprint
15:30:43 <matrohon> I have no time for bgpvpn coding currently, sorry
15:30:56 <tmorin> the OSC and python-neutronclient changes should, I think, be pretty straightforward to implement
15:31:06 <tmorin> matrohon: yes I was guessing so
15:32:29 <tmorin> tmorin: I'll probably have some Orange resource to help on that
15:32:53 <tmorin> I'll also reach out to bobmel and doude, to see if they'd be interested
15:33:02 <doude> hi
15:33:06 <tmorin> hi doude :)
15:33:29 <doude> on my side I have no time for the next month
15:33:49 <tmorin> doude: ok
15:33:50 <doude> no the 2 next months
15:34:03 <doude> (PTO)
15:34:33 <tmorin> Pike feature freeze is last week of July, so it does not make a difference :)
15:35:05 <tmorin> we will have to see if this can land for Pike of if we'll have to postpone to Queens
15:35:50 <doude> ok
15:37:48 <tmorin> ok, not much more to add for today I think
15:38:00 <tmorin> I'll make it clear in the meeting minutes that volunteers are welcome:
15:39:02 <tmorin> #help reach out if you're interested in helping on work items in https://blueprints.launchpad.net/bgpvpn/+spec/routes-control
15:39:12 <tmorin> #topic opendiscussion
15:39:31 <tmorin> do you guys have anything to bring up ?
15:40:03 <pcarver> nothing specifically bgpvpn related. Do you know of anyone planning to participate in the OpenContrail summit tomorrow?
15:41:00 <pcarver> It's a short "summit" so I don't know how much will be covered, but one of the topics could be the networking-opencontrail project and the plan for drivers for APIs such as bgpvpn, sfc, and Gluon/Proton APIs.
15:44:52 <tmorin> pcarver: no, I don't know for sure
15:45:19 <pcarver> ok, most likely it'll just be an organizational meeting
15:46:21 <pcarver> Mostly what I hope to get out of it with respect to networking-opencontrail is a general show of interest to see who might be potential consumers of the various Neutron API extensions if drivers get written for Contrail
15:47:08 <tmorin> yep
15:47:21 <tmorin> good question
15:47:29 <tmorin> I'm interesting to know the feedback
15:59:09 <tmorin> wow, time to free the floor
15:59:12 <tmorin> thanks everyone
15:59:15 <tmorin> #endmeeting