19:03:19 <tbachmanAfk> #startmeeting ovsdb_weekly_call
19:03:19 <odl_meetbot> Meeting started Tue Mar 17 19:03:19 2015 UTC.  The chair is tbachmanAfk. Information about MeetBot at http://ci.openstack.org/meetbot.html.
19:03:19 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:03:19 <odl_meetbot> The meeting name has been set to 'ovsdb_weekly_call'
19:03:29 <tbachman> #chair flaviof
19:03:34 <tbachman> #chair shague
19:03:46 <tbachmanAfk> #chair flaviof
19:03:46 <odl_meetbot> Current chairs: flaviof tbachmanAfk
19:03:50 <tbachmanAfk> #chair shague
19:03:50 <odl_meetbot> Current chairs: flaviof shague tbachmanAfk
19:03:52 <tbachmanAfk> lol
19:04:00 <tbachmanAfk> I can’t chair after changing my nic
19:04:13 <flaviof> lol
19:04:17 <tbachman> flaviof: shague can one of you re-chair me as tbachman?
19:04:26 <flaviof> #chair tbachman
19:04:26 <odl_meetbot> Current chairs: flaviof shague tbachman tbachmanAfk
19:04:30 <tbachman> flaviof: thx!
19:04:36 <tbachman> #unchair tbachmanAfk
19:04:36 <odl_meetbot> Current chairs: flaviof shague tbachman tbachmanAfk
19:04:56 <tbachman> #link https://meetings.opendaylight.org/opendaylight-ovsdb/2015/ovsdb_weekly_call/opendaylight-ovsdb-ovsdb_weekly_call.2015-02-24-19.59.html Last recorded meeting minutes
19:05:01 <tbachman> #topic agenda
19:06:08 <tbachman> #info topics: status and Trello
19:06:09 <tbachman> #topic Trello
19:06:09 <tbachman> ugh
19:06:12 <tbachman> there we go
19:08:38 <tbachman_> shague: can you hit the record?
19:09:24 <shague> tbachman_: the recording button is greyed out now.
19:09:30 <shague> phrobb: can you hit record?
19:10:26 <tbachman_> flaviof: keeeeeel-o
19:10:32 <tbachman_> not kill-o
19:10:37 <tbachman_> lol
19:11:03 <phrobb> shague:  done
19:11:10 <tbachman> #info flaviof says there have been problems with the bulk tests — not sure why it’s failing yet
19:11:13 <tbachman> phrobb: thx!
19:11:27 <flaviof> #link https://gist.github.com/a223d79b648c51128223
19:11:45 <tbachman> #undo
19:11:45 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x194b1d0>
19:12:00 <tbachman> #link https://gist.github.com/a223d79b648c51128223 Output when bulk tests fail
19:12:21 <tbachman> #info shague says the tempest tests are running now, so now the debugging of those tests can begin, because we can actually see the results
19:12:31 <tbachman> #info flaviof says we need to use the latest ODL rather than Helium ODL
19:12:55 <tbachman> #info shague asks about the report that gets generated — does the latest gerrit allow the report to be generated
19:13:05 <tbachman> #info flaviof says he’s not sure — he needs to circle back with mestery on that
19:13:18 <tbachman> #info flaviof says it’s basically knowing where the file is and having JJB putting in the artifact of the build
19:13:53 <tbachman> #info LuisGomez_ asks if there’s already automation in place to deploy devstack
19:14:07 <tbachman> #info flaviof says they have it - just needs to be modfiied to support what the integration test folks need
19:14:21 <tbachman> #info flaviof says it uses an unstable openstack with a stable ODL, which needs to be reverted
19:14:46 <tbachman> #info flaviof says there’s a caveat in that it’s just a single host test — so, no multinode testing, which is something that the OVSDB project is interested in
19:15:02 <tbachman> #info flaviof has been talking with dfarrell07 re: his efforts on this same task (devstack use)
19:15:48 <tbachman> #info mlemay says there’s two types of reports he’s been looking into: the openstack one and another one
19:15:57 * tbachman couldn’t hear the second one — getting dropping audio
19:16:45 <tbachman> #info mohnish says one of his colleagues is trying to reproduce the tempest tests, and was wondering if the instructions have been sent out as to how to reproduce this?
19:17:28 <tbachman> #info flaviof says there are two ways. The easiest is using the vagrant VM that dave_tucker and mestery created and use; with that vagrant file, you can stamp out a VM, run the stack, and then the tempest tests
19:17:32 <flaviof> #link https://etherpad.openstack.org/p/odl-virtual-ci-hackfest hackfest on running tempets
19:17:34 <mlemay> tbachman: sorry ... other one is simply vagrant + OVS and have a DUT (device under test) structure to simply test basic OVSDB operations (crud bridge, tunnels, etc.)
19:17:36 <tbachman> flaviof: thx!
19:17:49 <flaviof> #undo
19:17:49 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x1c3d050>
19:17:50 <mlemay> trying to do that without having to bring in devstack
19:17:55 <flaviof> #link https://etherpad.openstack.org/p/odl-virtual-ci-hackfest hackfest on running temptests
19:18:01 <tbachman> mlemay: no need to apologize — flakey internetz on my end :(
19:18:03 <tbachman> flaviof:  thx!
19:18:10 <flaviof> tbachman: np, ty!
19:18:26 <tbachman> #info mlemay says that his other reporting is simply vagrant + OVS and have a DUT (device under test) structure to simply test basic OVSDB operations (crud bridge, tunnels, etc.)
19:18:44 <tbachman> #info edwarnicke says there’s one more feature that he’s likely to add for the MD-SAL southbound
19:19:29 <tbachman> #info edwarnicke says the mapping of the OVSDB stuff back to the flow model is challenging, so he’s adding something that if a flownode comes up for a particular OVSDB managed bridge, you get an instance identifier that points to the flownode — he’s thinking of doing this as a separate feature
19:21:28 <tbachman> #info repenno asks with M3 approaching, he sent an email to the list about CRUD for interfaces, bridges, etc. and some folks said they were working on that. This functionality is needed by SFC project
19:22:47 <tbachman> #info shague says that OVSDB doesn’t have an API freeze, but offset 0 projects do
19:23:35 <tbachman> #info colindixon says he believes we don’t need to have the YANG model nailed down until a couple of weeks
19:23:57 <tbachman> #info edwarnicke says most of the model is picking up extensions, rather than changes
19:24:28 <tbachman> #awkward
19:24:33 <tbachman> lol
19:26:07 <tbachman> #info repenno says he’s wondering if folks are working on the CRUD APIs; the APIs that he’s looking for needs to be callable from SFC
19:27:43 <tbachman> #info SharadMishra says he provided the patches and added repenno as a reviewer
19:28:01 <tbachman> #info repenno will look at the patch and provide feedback
19:28:37 <tbachman> #info shague says edwarnicke has done most of the bridge side — bridge, port, interface
19:29:15 <tbachman> #info edwarnicke says for bridges, there’s a patch out; there are patches out that bring in the datapath information and protocols
19:31:20 <tbachman> #info edwarnicke says right now, datapath is coming back from the library API as a set, and he didn’t think the datapath was multi-valued in the schema
19:31:37 <tbachman> #info edwarnicke asks if that’s a bug in the library, or if that’s actually part of the schema
19:31:48 <tbachman> #info shague says it may be — they haven’t used the datapath much
19:33:38 <tbachman> #info repenno asks if there’s an API exposed that SFC can use
19:33:53 <tbachman> #info edwarnicke says repenno is probably looking for the overlay API; that’s next after the CRUD is working
19:34:22 <tbachman> #info repenno asks how he creates bridges, ports, etc. and do that on OVS nodes
19:34:38 <tbachman> #info edwarnicke says if you want to create those, you can use the stuff in the ovsdb.yang model directly
19:34:49 <tbachman> #info edwarnicke says you can write to the datastore directly
19:35:02 <tbachman> #info repenno says then you’ll have a multi-writer issue
19:35:13 <tbachman> #info edwarnicke says it’s intended to allow multiple applications to ask for things
19:36:14 <tbachman> #info edwarnicke says this should be reflected in the operational datastore
19:37:24 <tbachman> #info shague says there’s a southbound shim and southbound factory methods
19:37:40 <tbachman> #info repenno says that’s what he’s referring to — the shim
19:38:01 <tbachman> #info repenno says SFC needs something like “create this interface”, “create this bridge”, or “create this port"
19:38:24 <tbachman> #info repenno says the question is whether this is a datastore access or something that calls in to OVSDB
19:38:39 <tbachman> #info edwarnicke asks if repenno’s asking about convenience methods or RPCs
19:38:49 <tbachman> #info repenno says whatever works
19:39:52 <tbachman> #info repenno says if OVSDB creates an API, then that API may have extra sanitization for accessing the data store; if SFC does it, then it has to create the extra sanitization to access the data store
19:40:41 <tbachman> #info mohnish asks if some portion of the SB yang models are going to go through the network, and some will be non-network
19:41:36 <tbachman> #info mohnish asks if the network needs to be notified of the se changes
19:41:46 <tbachman> #info edwarnicke says anyone can subscribe to the datastore to get norifications for the changes
19:42:02 <tbachman> #info mohnish asks if netvirt is listening to those changes
19:42:13 * tbachman realizes he was probably mis-hearing “network” with “net-virt”
19:42:27 <tbachman> like Checkov — “wessels"
19:43:32 <tbachman> #info mohnish asks if groupbasedpolicy is going to use the neutron APIs and will use the OVSDB APIs, and stil manage the openflow APIs
19:43:45 <tbachman> #info edwarnicke says exactly — it would manage the flows directly, OVSDB SB to manage bridges, etc.
19:43:56 <tbachman> #info edwarnicke says he believes SFC is also managing the flows directly as well
19:44:10 <tbachman> #info repenno says that’s correct
19:44:44 <tbachman> #info shague says the documentation needs to be started by this Thursday
19:45:34 <tbachman> #info colindixon says the documentation in Lithium is attempting to get a more uniform agreement on what each document type is for — may require some massaging in order to adhere to the new outlines
19:46:14 <tbachman> #info shague says this may be just taking a lot of the documentation from helium and putting it in the new format
19:47:01 <tbachman> #info shague says they’ve gotten rid of the majority of the AD-SAL pieces
19:47:13 <tbachman> #info shague says they will then start looking at the tempest tests pretty heavily
19:48:39 <tbachman> #info shague says right now, the net-virt doesn’t come down through the MD-SAL; if they have time, they’ll look into whether that can be migrated as well
19:49:27 <tbachman> #info mohnish says if net-virt is the top-most application, then the consumer is net-virt itself; are we going to push that information into a data store?
19:49:45 <tbachman> #info shague says with the existing plugin, you get all of OVSDB
19:50:05 <tbachman> #info edwarnicke says the idea of the overlay model is that no single domain of control is consistent
19:50:50 <tbachman> #info mohnish says he’s thinking from the net-virt application itself — asks if there’s work going on there as well
19:51:02 <tbachman> #info shague says the net-virt application is only going to work with OVS specifically
19:52:09 <tbachman> #info flaviof asks if mohnish was asking about the L3 forwarding
19:52:46 <tbachman> #info mohnish says yes — understood that some of the tempest tests were failing b/c of L3; some of his team-members were looking at these failures as well
19:54:06 <tbachman> #info flaviof says for L3 forwarding, it’s less about OVSDB, and more about openflow
19:55:03 <tbachman> #info flaviof says there’s a question of where that router’s intelligence lives — Linux IP stack, or OpenDaylight
19:55:26 <tbachman> #info flaviof says L3 forwarding is using Nicira extensions to flow-mods
19:56:53 <tbachman> #info mohnish says when the APIs are invoked, the expectation is that ODL would be implementing something equivalent to DVR; the question is the user wants to manage the bridges and routers through opendaylight?
19:57:25 <tbachman> #info flaviof says as of now it’s a DVR replacement; there’s a hybrid approach where ODL fills in OpenStack’s DVR shortcomings and vise-versa
19:58:01 <tbachman> #info flaviof says there’s a distributed way of replying to ARPs; but there’s no way of doing an ICMP reply to TTL expirations
19:58:39 <tbachman> #info mohnish says this needs more discussion — asks if shague and flaviof would want a separate call for this
19:58:59 <tbachman> #info flaviof says we can, but there currently isn’t enough cycles to do this for Lithium
19:59:53 <tbachman> #info Swami says we can have a discussion, but as flaviof said, for Lithium, there’s no focus on DVR on par wtih neutron; would like to be included in any such discussion tho
20:00:15 <tbachman> #endmeeting