16:05:42 <tbachman> #startmeeting MD-SAL interest call
16:05:42 <odl_meetbot> Meeting started Tue Sep  9 16:05:42 2014 UTC.  The chair is tbachman. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:05:42 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:05:42 <odl_meetbot> The meeting name has been set to 'md_sal_interest_call'
16:05:45 <tbachman> chair devinavery
16:05:47 <devinavery> Thanks. :)
16:05:48 <tbachman> #chair devinavery
16:05:48 <odl_meetbot> Current chairs: devinavery tbachman
16:05:49 <tbachman> np
16:05:54 <tbachman> #chair colindixon
16:05:54 <odl_meetbot> Current chairs: colindixon devinavery tbachman
16:05:56 <devinavery> Never seem to remember the commands
16:06:16 <tbachman> #topic agenda
16:06:23 <colindixon> I can help if you need
16:06:52 <tbachman> #info Agenda items: tatus update, Recap on Modeling Network Topologies, Bug reporting/Fixing
16:06:57 <tbachman> colindixon: thx
16:07:06 <tbachman> made you a chair — welcome to join :)
16:07:23 <tbachman> #info colindixon asks to add wildcard queries as opposed to wildcard subscriptions on the MD-SAL
16:09:57 <tbachman> #topic recap on modeling network topologies
16:10:58 <colindixon> #info the discussion offline didn’t happen, here so starting here (allocating 15 minutes)
16:11:09 <tbachman> colindixon: thx!
16:11:41 <colindixon> #info the network topology model supports multiple topologies, today we have one openflow-oriented topology with the key “flow:1”
16:12:53 <devinavery> #info Ramkumar is sharing screen as he walks through examples
16:13:02 <tbachman> devinavery: thx! :)
16:14:07 <tbachman> #info ramkumar says his understanding is that each link has a reference back to the node
16:15:07 <tbachman> #info colindixon says that in the long run we probably won’t have this separation between inventory and topology
16:15:15 <tbachman> #info but will be augmentations instead
16:16:01 <tbachman> #info ramkumar says this might be better, b/c regardless of the node type (flow-capable, etc.), the topology doesn’t care
16:17:12 <tbachman> #info ramkumar asks if there are multiple topologies, and if there are multiple toplogies, how do relate between different nodes
16:17:32 <tbachman> #info jmedved says that’s difficult to model, and you need something to reconcile, which would be another plugin
16:20:12 <tbachman> #info ramkumar says that whatever’s using different node types has to know how to talk to each of them
16:20:44 <tbachman> #info ramkumar says that the plugins (e.g. openflow, BGP, etc.) only need to know how to talk to their nodes
16:25:40 <devinavery> #info Jan states that each plugin should create its own topology and then a second plugin should be used to relate two topologies together
16:28:50 <tbachman> #info colindixon says you can create an overlay topology which the different toplogies can attach to
16:30:02 <tbachman> #info jmedved notes there is a producer and a consumer of the topology, and that the consumers don’t need to understand the details of the producer
16:30:37 <tbachman> #info colindixon says you could work on the global topology, which is created by flattening everything
16:30:53 <tbachman> #info ramkumar says that if you don’t have a flat topology, how do you know how to navigate between the topologies?
16:32:28 <tbachman> #info colindixon says that topologies can have references to other topologies
16:32:39 <tbachman> #info and the application can traverse a metatopology that links the two
16:33:09 <tbachman> #info colindixon notes that we don’t have interconnections today, but the model supports it
16:35:41 <colindixon> tbachman: sorry I’m not scribing, my brain wasn’t supporting both
16:35:57 <tbachman> colindixon: no worries — did I capture it accurately?
16:36:45 * tbachman notes that colindixon’s mind is probably page swapping between REM sleep and ODL ;)
16:36:59 <tbachman> #topic bugs
16:38:38 <colindixon> I’ll get the link
16:38:40 <tbachman> #link https://wiki.opendaylight.org/view/OpenDaylight_Bugs <= link that devinavery created to help with bugs
16:38:51 <colindixon> nm
16:39:24 <tbachman> #info The wiki page describes how to use fields like Target Milestones
16:40:03 <tbachman> #info The page has quick links to find bugs for each project in both Helium and (upcoming) Lithium releases
16:40:43 <tbachman> #info The bugs listed in the Helium links are the bugs that are intended to be fixed in the Helium release
16:44:56 <tbachman> #topic MD-SAL and wildcards
16:49:45 <tbachman> #info colindixon is trying to get the node in the topology that corresponds to a host with a given IP address
16:50:15 <tbachman> #info his first attempt was to get an instance identifier from NetworkTopology’s children
16:50:22 <tbachman> #info and that this would provide a list
16:50:39 <tbachman> #info however, that read returned a single host node, and not a list
16:51:15 <tbachman> #info The second attempt had to iterate through a higher level list
16:51:43 <tbachman> #info colindixon wants to know if there’s a way to wildcard the instance identifier
16:52:14 <tbachman> #info rovarga says that the datastore has to do precisely the same thing that’s being done in colindixon’s second attempt
16:53:09 <tbachman> #info rovarga says that instead of a wildcard, you’d rather have a query language to express what it is you’re looking for
16:55:26 <tbachman> #info an advantage of an xpath query is that you can do things like “give me all of the things that have host nodes”, which wouldn’t be available in the query language
16:55:48 <tbachman> #info jmedved asks if colindixon could discuss his use case with sharon
16:56:03 <tbachman> #info colindixon says that you can’t really do that with SQL because it breaks schemas
16:56:36 <tbachman> #info devinavery says that could be a lithium focus: making searching of MD-SAL easier
16:58:03 <tbachman> #endmeeting