16:09:08 #startmeeting: networking_ml2 16:09:08 Meeting started Wed Mar 22 16:09:08 2017 UTC and is due to finish in 60 minutes. The chair is Sukhdev_. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:09:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:09:11 The meeting name has been set to '__networking_ml2' 16:09:17 #topic: Agenda 16:09:28 #link: https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_March_15.2C_2017 16:09:53 #topic: Announcements 16:10:12 rkukura is out today - so, he can not chair the meeting this moring 16:11:20 #topic: QinQ Driver discussion 16:11:25 it doesn't look like there is an agenda for todays meeting. 16:11:59 trevormc : yes - rkukura missed it and I thought he was going to chair - minor confussion 16:12:02 hi 16:12:13 we will make the agenda as we go 16:12:17 dasanind : hi 16:12:17 ah ok. So the qinq driver is coming along nicely, I was able to create a network locally and verify the database entries 16:12:50 trevormc : lets discuss the QinQ driver here 16:12:57 #link https://review.openstack.org/#/c/446047/ 16:13:20 trevormc : that is good progress - 16:13:26 The tests are failing because of the added _verify_networks_match function but it passes for me locall. 16:13:50 Sean mooney reviewed it, and he is asking why I have the vlan_id in the L2 network segments table. 16:14:10 I told him I have no other way of looking up the records with the driver_api. 16:15:19 trevormc : one of the ML2 driver tables have this information already - can you not use that? 16:16:58 Sukhdev_ oh, what table? I was using the segment object here to retirieve the data https://review.openstack.org/#/c/446047/8/neutron/plugins/ml2/drivers/type_qinq.py@276 16:19:36 https://github.com/openstack/neutron/blob/master/neutron/db/models/plugins/ml2/vlanallocation.py#L39 16:20:06 actually I am looking for different table for ml2 driver - 16:20:26 ok, that one I thought was just for vlan type networks 16:21:22 trevormc : right scratch that - there is another one - trying to remember 16:21:38 the one used by ml2 drivers 16:22:01 here is a list http://paste.openstack.org/show/603792/ 16:22:11 maybe one of those will jog your memory :) 16:23:37 trevormc :-) 16:23:50 networkconnections table? 16:24:12 im just guessing here. Maybe we can get back to it later. 16:25:39 yes one of these - its been a while when I used them 16:26:11 I am thinking ml2_port_bindings 16:26:58 That just has port details in it. 16:27:24 and interface details. 16:28:11 ok well I'll consider it, I'm confused on how to use any other segment object other than the one given to the dirver 16:28:28 look in neutron_lib 16:28:54 there is db and model_base in there - I think it may be there 16:29:29 my wifi is bit slow here - ping me if you could not find it offline, and I will try to dig it for you 16:29:42 release_segment(self, context, segment): - the segment here is my concern. 16:29:56 i'll message you later 16:30:10 trevormc : sounds good - 16:30:27 I don't have any more updates. 16:31:07 trevormc : I will review your patch as well and see what Sean is suggesting - and reply accordingly 16:31:23 thank you! did you have anything on your end? 16:31:47 #topic : multiple bindings discussion 16:31:54 dasanind : are you there? 16:31:59 need some reviews on https://review.openstack.org/#/c/414251/ 16:32:12 #link: https://review.openstack.org/#/c/414251/ 16:32:36 I am working on the test cases currently 16:33:00 Is this ready? 16:34:06 ill take a look, i gotta run. 16:34:07 no still the integration with existing ml2 code is pending 16:34:29 dasanind : I see 16:34:39 but would like to get feedback on the apis 16:35:03 dasanind : OK makes sense 16:35:38 my next couple of days are kinda bad - but, will look it over the weekend and post comments 16:35:48 Sukhdev_: thank you 16:36:11 dasanind : no worries 16:36:19 anything else? 16:36:30 nothing else from my side 16:36:43 cool - 16:36:55 #topic Open Discussion 16:37:07 Anybody has anything to discuss? 16:37:28 I don't have anything 16:37:51 OK - I think in that case we are done 16:38:00 see you next week or on the reviewboard 16:38:07 Thanks for attending 16:38:12 #endmeeting