[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 |
||
| Issue Links: |
|
||||||||
| External issue ID: | 2775 | ||||||||
| Description |
|
Current process of registration of EventSource requires several steps 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 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. Proposed SPI contract is not definite, and should be iterated upon, to provide Instance of EventSourceRegistry should be available via Config Subsystem and |
| Comments |
| Comment by Tony Tkacik [ 12/May/15 ] |