[CONTROLLER-1181] Define and implement EventSource SPI Created: 02/Mar/15  Updated: 12/May/15  Resolved: 12/May/15

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: Post-Helium
Fix Version/s: None

Type: Bug
Reporter: Tony Tkacik Assignee: Marian Adamjak
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
blocks CONTROLLER-1188 Milestone: add support for network-wi... Resolved
External issue ID: 2775

 Description   

Current process of registration of EventSource requires several steps
for application to become event source.

These steps are: exporting node to event source topology and providing (registering) an RPC implementation of EventSourceService RPCs to MD-SAL.

These steps are currently manually implemented in NetconfEventSource / NetconfEventSourceManaget

In order to ease development of EventSources, convenience SPI and implementation
should be provided, which will expose method such
as

interface EventSourceRegistry

{ EventSourceRegistration registerEventSource(EventSourceService impl); }

which will return EventSourceRegistration (subclass of abstract object registration) with following:

InstanceIdentifier - path assigned to event source in event source topology.
close() - when invoked event source will be removed and registration of event source topology.

Proposed SPI contract is not definite, and should be iterated upon, to provide
best APIs. Available.

Instance of EventSourceRegistry should be available via Config Subsystem and
name of EventSource topology should be configurable.



 Comments   
Comment by Tony Tkacik [ 12/May/15 ]

https://git.opendaylight.org/gerrit/#/c/16401/

Generated at Wed Feb 07 19:54:53 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.