17:02:30 #startmeeting tws 17:02:30 Meeting started Mon Jun 1 17:02:30 2015 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:02:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:02:30 The meeting name has been set to 'tws' 17:02:35 #topic agenda 17:03:37 #info today Michal Polkoráb will present info on the topology processing framework 17:04:40 #info if you have other topics, please let Keith and I know, and we’ll get you on the agenda 17:04:50 #link https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Meeting_Schedule_and_Logistics 17:04:58 #topic topology processing framework 17:05:09 if anyone wants a #chair, let me know 17:06:35 #info restarted recording around 10:07, and we’re starting things in case you’re trying to sync meeting minutes and the recording 17:07:02 #info the topology procesing framework sits in the controller 17:07:30 #info it’s primary role is to create aggregated topology interfaces instead of one (or more) topology per protocol 17:07:36 #undo 17:07:36 Removing item from minutes: 17:07:40 #info its primary role is to create aggregated topology interfaces instead of one (or more) topology per protocol 17:08:03 #info right now it works by creating logical nodes and embedding them in a single logical topology 17:10:12 #info in addition to logically merging topologies, topologies can be filtered so that you can see a subset of topology 17:10:56 #topic aggregation 17:11:17 #info there are two ways to aggregate nodes/topologies: unification and equality 17:11:24 #undo 17:11:24 Removing item from minutes: 17:11:34 #undo 17:11:34 Removing item from minutes: 17:12:20 #info right now there is a way for you to provide a Comparator (I think) which will say if two nodes should be unified when aggregated topologies are created 17:12:28 #info there is also a way to filter based on the Node IP 17:12:53 #topic live-view operations 17:13:56 #info the framework appropriately handles and produces node added, node removed, and node changed 17:14:01 #link https://wiki.opendaylight.org/view/Topology_Processing_Framework:Developer_Guide the developer guide 17:14:15 #link https://wiki.opendaylight.org/view/Topology_Processing_Framework:Main the project main page 17:14:29 #topic example 17:14:38 #undo 17:14:38 Removing item from minutes: 17:15:06 #topic equality aggregation use case 17:16:28 #info they show the 80-topoprocessin-confg.xml file 17:17:57 #info shows the running ODL karaf container: the bgp features are installed, the topology processing feature is installed, and the restconf feature is installed 17:18:43 #info they push a REST request telling topoprocessing to merge the 3 bpg topologies into one 17:19:06 #info show via a REST get that there is now a logical topology 17:20:04 #info they push 3 nodes with the same IP address into the 3 different pcep (bgp) topologies and show that they get aggreged into the same node in the logical topology 17:21:17 #info they change the IP address of one of the nodes so that it has a different IP addess, this is reflected in the logical topologies 17:21:26 #info they also demonstrate remving nodes 17:22:36 #info the key point here is that in the equality use case only published nodes that can be aggregated into the logical topology, if there are nodes which have no potential aggregations, they aren’t listed 17:22:53 #topic unification aggregagion use case 17:23:27 #info in this case, the logical topology will contain all nodes in the topologies it is reading from even if there is no way to aggregate it with anything else 17:24:33 #info colindixon asks if there’s any reason you’d use the equality use case over the unification, the answer is that seems likely but for now they suppor both because it wasn’t hard 17:25:00 #info they go through the demo of adding, changing, and removing nodes and showing they are appropriately represented 17:27:20 #Info colindixon asks how it finds the fields to compare equality, tony asks Michal to show the network topology configuration to answer the question 17:29:39 #info the config shows that they are specifying the fields to compare for equaity, but they have to be fields defined as augmentations to topoglogy node 17:30:56 Need to run to another meeting 17:31:17 #info critically, that means you can’t corelate OF nodes since they augment inventory nodes 17:31:38 #info colindixon asks abhijitkumbhare if there’s any plan to move OF from inventory to topology, he says no, not at this time 17:33:02 #info abhijitkumbhare notes that we can discuss this during the Beryllium release plans 17:33:48 #info michal says he hopes to work on fixing that during Beryllium 17:35:35 #info colindixon asks if we could use use comparators instead of just equality, micahal says that’s planned for Beryllium along with some scripting 17:36:06 #topic filtering use case 17:36:33 #info Micahal says that they have IP address filtering only right now, but he’s happy to implement whatever else you want if you ask 17:37:48 #info the demo shows that the logical topolgoy, does in fact, filter based on IP addresses 17:39:23 #info colindixon asks if you could extend this to be able to add new filters after compile time 17:39:30 #info Michal says not now, but maybe in Be 17:39:34 #topic wrapping up 17:39:57 #info currnetly this works with real topology and real data, as long as everything augments the topology model 17:40:14 #info longer-term goals multi-layer multi-topology support 17:40:39 #info scripting support for programmable rules in filtering, equality and unification 17:41:10 #info LuisGomez asks, you showed nodes, what about links and termination points 17:41:26 #info Michal says links and TPs are aren’t supported, but they’re hoping to do that in Be 17:42:31 colindixon: Good question. 17:43:03 #info colindixon asks what they used to make the slides, the answer is impress.js (the slides were cool) 17:43:15 #info they will post the slides to the wiki 17:49:22 #info colindixon says that this is really cool and is important for anyone writing an app that wants be support multiple different southbound protoocols and deal with toptology in a protocol-independent way, because you will have to build your own version of this or use this stuff 17:49:45 #info hideyuki asks what colindixon meant above about the inventory model vs. topology model 17:50:12 colindixon: Thanks for answering question. 17:50:26 this is super cool 17:51:06 #info colindixon says that for historical reasons, we have two top-level models with nodes: inventory (which is ODL-specific) and topology (which is from an IETF RFC) 17:52:27 dbainbri needs learn to keep quiet ;) 17:53:56 i think most people (ODL users) don't care how it is sourced, as long as it can be accessed via a public web site 17:54:37 #info for historical reasons the OF plugin uses the inventory model, while pretty much everyone else uses topology and we should really be moved to the topology model 18:01:46 #topic asciidoc stuff 18:03:51 #info tony shows how to do some automated translation of wiki to asciidoc 18:04:23 OK - colindixon that was the point I was going to ask tony 18:04:59 #info tony will send an e-mail to the mailing list describing what he’s done 18:05:11 #Info there was a lot of discussion around how to improve docs going forward 18:05:46 #info dbainbri asks if we want to have a model which is AsciiDoc as the primary and that’s where people edit it or if we want to move to a mode where the wiki is the primary and we simply use AsciiDoc to archive things at a release 18:05:59 #info several people say that having HTML would be much better than PDFs 18:06:52 #info colindixon says that we have HTML, it’s just way too segmented (one document per subsection or subsubsection) to be useful 18:07:16 #info tony shows that on github, we can use some of their asciidoc renderer to get HTML views of the live docs in the repo 18:08:41 #link https://github.com/opendaylight/docs/blob/master/manuals/getting-started-guide/src/main/asciidoc/general_installation.adoc this is a good example 18:10:08 #info odlcasey asks about how the documentation effort is staffed, colindixon says it’s staffed by people who mostly have day jobs as well and thus we just don’t have the raw documentation horsepower except from the projects themselves 18:10:35 #info colindixon invites anyone who wants to help to come to the docs project meetings and plan Be features if they are interested 18:11:09 #link https://wiki.opendaylight.org/view/Documentation this page has information on documentation meetings and plans 18:11:14 #endmeeting