[CONTROLLER-519] Provide information on MD-SAL's "Ready" status Created: 28/May/14 Updated: 19/Oct/17 Resolved: 04/Jul/17 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | karaf |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Devin Avery | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Northbound and southbound clients need to know when MD-SAL is "ready" to be utilized. In this case, ready means, all OOB models have been loaded, and services have been published to the OSGi container. WE should provide some type of status identifier to help northbound / southbound clients track the "status" of the controller (specific to MD-SAL to start?) |
| Comments |
| Comment by Devin Avery [ 28/May/14 ] |
|
Note from initial comments: This problem is solved for RESTConf by making it register for YANG convergence events and have it reload its cache based on these events. However, from the controller, it is impossible to say when the controller is really ready. |
| Comment by Robert Varga [ 04/Feb/15 ] |
|
Unfortunately MD-SAL itself does not know this. We need the 'installation done' stimulus, which must come from Karaf (or whatever container we are in). I think part of this is already achieved via the config-loopback, where we can wee what services are already initialized and ready, but the problem is we do not see what the operator's intent is (or what Karaf has in store for us). |
| Comment by Robert Varga [ 13/Nov/15 ] |
|
We need this feedback from karaf. |
| Comment by Michael Vorburger [ 10/May/17 ] |
|
Robert, FYI I'm building something related (dupe?) in |