20:00:26 #startmeeting ovsdb_weekly_call 20:00:26 Meeting started Tue Jan 20 20:00:26 2015 UTC. The chair is tbachman. Information about MeetBot at http://ci.openstack.org/meetbot.html. 20:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:26 The meeting name has been set to 'ovsdb_weekly_call' 20:00:40 #chair flaviof shague 20:00:40 Current chairs: flaviof shague tbachman 20:00:45 #topic agenda 20:01:43 #link https://meetings.opendaylight.org/opendaylight-ovsdb/2015/ovsdb_weekly_call/opendaylight-ovsdb-ovsdb_weekly_call.2015-01-13-20.01.html Minutes from last week’s meeting 20:05:04 #topic trello board 20:06:15 #info shague says that OVSDB has joined the Lithium simultaneous release 20:06:49 #info shague has been looking into pulling out the neutron services and putting it in it’s own project; will submit as project proposal to TSC 20:07:03 #info users of neutron should be able to point to the new bundle 20:07:42 #info edwarnicke has been working on creating a yang model to put in OVSDB for MD-SAL 20:08:11 #info michal_rehak has merged the nicira extension work in the openflowplugin 20:08:20 #info tbachman and flaviof are working on getting this set up in OVSDB 20:09:37 * tbachman wonders if plaurin_ is “patrick" 20:10:45 #info plaurin_ is working with mestery on the neutron side; something strange with the unit tests 20:12:18 #info sharad is working on DPDK, and has a few issues that he’s trying to resolve 20:12:31 tbachman: yep 20:12:40 #info sharad asks how to expose the capabilities of the switch and the host in ODL 20:12:53 #info sharad is looking into how to expose this to openstack 20:14:32 #info sharad says the OVS folks are proposing to change the OVSDB schema to add a capabilities field to bridges to support different port types, which could be provided to openstack 20:15:47 #info edwarnicke says we could look into adding to the model, as that’s how you can get this information represented in ODL so that it can be used for muiltiple apps 20:18:50 #topic MD-SAL model for OVSDB 20:22:08 #info edwarnicke says his understanding that there are 3 kinds of things that users of OVSDB want to do 20:22:22 #info the first one is that people might want to create a switch-like thing 20:22:33 #info the second is to CRUD a port for the datapath 20:22:42 #info the third is to CRUD a tunnel for a datapath 20:23:13 #info edwarnicke says that to do this, he’s created two models: an OVSDB model, and an OVSDB switch model 20:24:07 #link https://git.opendaylight.org/gerrit/#/c/14261/ Gerrit that edwarnicke is referencing 20:26:21 #info the ovsdb model creates augmentations to the nodes in topology 20:26:44 #info one of the model elements is to augment the node with an OVSDB node 20:26:59 #info another one of the model elements is to augment the node with bridges 20:27:12 #info edwarnicke says a lot of this was taken from SFC’s models 20:31:07 #info shague asks why we can’t use the OVSDB schema to generate the model 20:31:27 #info edwarnicke says there are two things to look at; you have to dynamic translation of schema to yang, which is doable, but a lot more work 20:31:42 #info edwarnicke says we’re describing high-level information about what we’re doing 20:34:35 #info anil asks if this nb would talk to the AD-SAL plugin 20:34:47 #info edwarnicke says this NB uses the library but does not talk to the AD-SAL lib 20:35:30 #info shague says that there’s a layer above the library, and now there’d be two different paths into the library 20:35:40 #info edwarnicke says the plugin currently pulls in the entire AD-SAL 20:35:52 #info shague says there are other places in OVSDB that use the AD-SAL 20:36:05 #info edwarnicke says there’s not maintenance for the AD-SAL going forward 20:36:23 #info shague says that you can’t just use the library today, as there are other pieces invovled 20:36:36 #info shague says that you have to include a couple of other pieces 20:36:51 #info edwarnicke says this already functions, asks why it required pulling in the entire AD-SAL 20:37:03 #info shague says you could extract out just the library, but you’d break the other users 20:37:48 #info there’s some discrepency between shague and edwarnicke about what the VTN project is going to be using for Lithium 20:42:22 #info LuisGomez asks about the API to use the v3 APIs 20:42:43 #info edwarnicke says he’s not opposed to that, but there are requests for the use cases that he’s created the yang models for 20:43:10 #info this is also driven by the M2 deadline 20:44:05 #info edwarnicke says that it’s possible that both ends of the tunnel might be on an OVSDB managed node, and another might be on a non-OVSDB managed node 20:47:15 #link https://lists.opendaylight.org/pipermail/ovsdb-dev/2015-January/000980.html email thread that talks about overlay APIs being looked into 20:49:59 #info flaviof points out that there’s a bunch of OVS-like things that might be represented (e.g. trunked links) 20:51:11 #info edwarnicke says he doesn’t mind binding things together that are intrinsicly bound together, but is against artificial glomming together of things in a NB model 20:53:16 #info the tunnel.yang model creates a bunch of tunnel types, which are used to augment a node with the tunnel type 20:53:34 #info anil asks what the link signifies 20:54:07 #info it depends on the topology that you’re looking at. 20:54:19 #info anil says if you’re talking about physical links, there could be many tunnels on that link 20:54:28 #info edwarnicke says these are tunnel links, not physical links 20:57:03 #info Eric Multanen asks where things like the DPDK port types would fit in the model 20:57:57 #info Eric Multanen says you set the type when you create the port 20:58:16 #info edwarnicke says he thinks this would be an attribute of the port that you’d augment 20:58:59 #info edwarnicke asks if port types are a capability of the bridge or the OVSDB instance 20:59:15 #info Eric Multanen says maybe both - it’s part of an instance of a bridge that you create 20:59:28 #info edwarnicke says in the bridge you could get a list of supported port types, which is extensible 20:59:55 these models looks interesting, but if i look at high level this modules are defining abstraction on top of real ovsdb schemas, am i correct? 21:00:02 #info edwarnicke asks if port type is really an attribute of the port, or of two port types put together 21:00:13 vishnoianil: any chance you can call on a land line? 21:00:21 vishnoianil: that’s the way I read it 21:00:50 vishnoianil: 1-855-244-8681 21:01:05 vishnoianil: meeting number: 196 498 415 21:01:18 vishnoianil: access code: 196 498 415 21:02:17 some logistic issues to join from phone :) will make sure next time i get better connectivity 21:02:26 vishnoianil: I feel your pain 21:02:35 we really want to hear from you…. just can’t :( 21:03:15 vishnoianil: best bet is to use this IRC as a relay, or use webex chat as relay 21:03:24 * tbachman can be vishnoianil’s proxy 21:03:43 * tbachman notes that we’re past 4pm EST 21:03:44 tbachman, thanks a lot! 21:03:47 vishnoianil: np! 21:03:55 just put your q’s here 21:04:18 #info sharad asks if we should be looking at using the MD-SAL model for the Lithium time frame 21:04:36 i think we are running out of time, so will put my question in mail and lets discuss there 21:04:39 #info shague says the real issue is what is our flow 21:04:42 vishnoianil: sounds good 21:05:56 #info edwarnicke asks if Eric is looking to use OVSDB to query the supported port types on the bridge 21:06:32 #info Eric says that’s the case, but the ports are actually created by openstack, via libvirt 21:07:52 #info shague says openstack queries the OVSDB database now, so why replicate this in OVSDB? 21:08:26 #info edwarnicke asks if this is a good first pass at the model 21:08:31 #info shague says this is a good start 21:15:09 #endmeeting