16:11:59 <devinavery> #startmeeting MD-SAL interest call
16:11:59 <odl_meetbot> Meeting started Tue Apr 14 16:11:59 2015 UTC.  The chair is devinavery. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:11:59 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:11:59 <odl_meetbot> The meeting name has been set to 'md_sal_interest_call'
16:12:43 <devinavery> #topic Discussing 4 meetings related to the logical "core" of the controller
16:13:08 <devinavery> #info there are 4 meetings - MD-SAL hackers call, TWS call, MD-SAL clustering calls, MD-SAL weekly call
16:13:34 <devinavery> #info What do we want to cover in the public meetings?
16:22:18 <devinavery> #info bug scrub, deisgn and implementation, general tipics Q&A, presentations of features and functionality
16:26:02 <devinavery> # info the notes taken in the meeting will be posted to MD-SAL weekly call site. We will also send to mailing list to continue conversation.
16:26:26 <devinavery> #topic Switch to Event Manager (needs better name) demo / discussion
16:26:44 <devinavery> #info Andrew is showing diagram showing demo set up
16:29:08 <devinavery> #chair colindixon
16:29:08 <odl_meetbot> Current chairs: colindixon devinavery
16:29:29 <colindixon> thanks :-)
16:30:35 <devinavery> I am being called away - colindixon will be covering the remaining of the meeting. Thank you colin!
16:31:03 <colindixon> #info andrew shows a demo using an XMPP connector (for events) and two NETCONF routers so that you can show events pushing from NETCONF to OpenDaylight to Adium
16:32:15 <colindixon> #info you can subscribe to topics (thus across devices)
16:33:44 <colindixon> #info the user-agent which is sending the XMPP messages is just listening for normal MD-SAL notifications and then fowarding them over ejabber
16:34:48 <colindixon> #info it listens for notifications around who’s subscribed to what as well as for notifications that pertain to the subscription
16:39:46 <colindixon> #info colindixon asks how this fits into what we currently have in terms of RPCs and notifications, also how it fits into dbainbri (and others) asks for the ability to filter notifications
16:41:36 <colindixon> #info the answer is that these filters are really based on the additional information added in the event source to figure out capabilities instead of filtering based on the notification contents
16:44:47 <colindixon> #info the event source relies on the notifications and RPCs and the node in the topology YANG model
16:59:36 <colindixon> #info there was a lot of discussion largely surrounding whether this microservice/application can be generalized in order to be pushed down into the current abstractions we have
17:00:23 <colindixon> #info see the meeting recording from ~25 minutes to ~57 minutes for more information
17:01:05 <colindixon> #info andrew says the name is either event topic broker or topic event broker
17:03:19 <colindixon> #action andrew to send mail proposing (or really just stating) the new name to the list
17:03:55 <colindixon> #action colindixon to send mail asking about how we might generalize some of this and maybe push it into our core MD-SAL abstractions
17:04:42 <colindixon> #endmeeting