16:06:27 <colindixon> #startmeeting MD-SAL interest call
16:06:27 <odl_meetbot> Meeting started Tue Sep  2 16:06:27 2014 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:06:27 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:06:27 <odl_meetbot> The meeting name has been set to 'md_sal_interest_call'
16:06:32 <colindixon> #topic agenda bashing
16:07:14 <colindixon> #link https://wiki.opendaylight.org/view/MD-SAL_Weekly_Call#Agenda the details of the agenda and call (as always)
16:07:20 <colindixon> edwarnicke: tahnks!
16:09:46 <colindixon> #topic new functionality
16:10:14 <colindixon> #info tony says that the enew write out codec to restconf is ready and waiting on verify before it getst merged
16:10:21 <colindixon> #topic questions
16:10:39 <colindixon> #link https://lists.opendaylight.org/pipermail/controller-dev/2014-August/006371.html this mailing list item hasn’t gotten the response we’d like
16:22:48 <colindixon> #info the question is how to get the parent of a node in the MD-SAL tree
16:23:47 <colindixon> #info the answer is to use InstanceIdenfier.firstIdentifierOf() and pass the class of the expected parent to get an instance identifier of the parent, which you can then use to read the parent
16:25:09 <colindixon> #info ramkumar asks if the same data change listener be used for multiple change registrations?
16:26:17 <colindixon> #info answer is that, yes, you can register twice, but there’s no promise about the ordering of events between the two registrations
16:28:57 <colindixon> #topic topics for the design forum
16:29:36 <colindixon> #info jan medved wants to hear things about clustering (both how it’s built and how it can be used)
16:30:57 <colindixon> #info brainstorming about binding specification
16:31:06 <colindixon> #link https://wiki.opendaylight.org/view/YANG_Tools:Design:Binding_Specification_v2_Analysis this page has been aggregating some ideas
16:32:19 <colindixon> #link https://bugs.opendaylight.org/show_bug.cgi?id=1411 this bug is the v2 spec which has all other bugs that require v2 spec to solve
16:33:59 <colindixon> #info colindixon suggests the config subsytem: (i) introductuion to basic use, (ii) how to extend with own classes, (iii) how to find what already exists vs. what I need to register again, (iv) how to make it easier to use [others adding the sub bullets]
16:36:08 <colindixon> #info how to model and represent hetergeous network topology (layers, etc.)
16:39:15 <colindixon> #info there’s a lot of discussion from ramkumar, rovarga, colindixon, and others about how we currrently do things
16:40:10 <colindixon> #info devinavery says that modeling best practices in general probably needs to be a topic either here or at the design forum
16:43:16 <colindixon> #info around modeling Uyen points out that there’s a lot of modeling silos right now, figuring out how to drag (at least some) models out to application-independent ways
16:43:45 <colindixon> #topic JMX stats for MD-SAL
16:44:53 <colindixon> #info see recording for the demo
16:48:01 <colindixon> #info tom pantelis shows getting status out of JMX, including things about data-store-executor, notification-executor, e.g., the active number of threads, completed tasks, etc.
16:51:35 <colindixon> #info jan medved asks about commit stats, TomP shows commit stats including average, longest, and shortest commit times, as well as total number of commits
16:58:23 <colindixon> #info TomP notes that the clustering stuff has more info too, but that would have to wait until later for a demo
17:01:21 <colindixon> #endmeeting