#opendaylight-meeting: MD-SAL interest call

Meeting summary

1. Discussing 4 meetings related to the logical "core" of the controller (devinavery, 16:12:43)
   1. there are 4 meetings - MD-SAL hackers call, TWS call, MD-SAL clustering calls, MD-SAL weekly call (devinavery, 16:13:08)
   2. What do we want to cover in the public meetings? (devinavery, 16:13:34)
   3. bug scrub, deisgn and implementation, general tipics Q&A, presentations of features and functionality (devinavery, 16:22:18)
   
   
2. Switch to Event Manager (needs better name) demo / discussion (devinavery, 16:26:26)
   1. Andrew is showing diagram showing demo set up (devinavery, 16:26:44)
   2. 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 (colindixon, 16:31:03)
   3. you can subscribe to topics (thus across devices) (colindixon, 16:32:15)
   4. the user-agent which is sending the XMPP messages is just listening for normal MD-SAL notifications and then fowarding them over ejabber (colindixon, 16:33:44)
   5. it listens for notifications around who’s subscribed to what as well as for notifications that pertain to the subscription (colindixon, 16:34:48)
   6. 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 (colindixon, 16:39:46)
   7. 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 (colindixon, 16:41:36)
   8. the event source relies on the notifications and RPCs and the node in the topology YANG model (colindixon, 16:44:47)
   9. 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 (colindixon, 16:59:36)
   10. see the meeting recording from ~25 minutes to ~57 minutes for more information (colindixon, 17:00:23)
   11. andrew says the name is either event topic broker or topic event broker (colindixon, 17:01:05)
   12. ACTION: andrew to send mail proposing (or really just stating) the new name to the list (colindixon, 17:03:19)
   13. ACTION: colindixon to send mail asking about how we might generalize some of this and maybe push it into our core MD-SAL abstractions (colindixon, 17:03:55)

Action items

1. andrew to send mail proposing (or really just stating) the new name to the list
2. colindixon to send mail asking about how we might generalize some of this and maybe push it into our core MD-SAL abstractions

Action items, by person

1. colindixon
   1. colindixon to send mail asking about how we might generalize some of this and maybe push it into our core MD-SAL abstractions

People present (lines said)

1. colindixon (14)
2. devinavery (10)
3. odl_meetbot (4)