[CONTROLLER-1967] Devise a mechanism for discovering magement information at runtime Created: 23/Oct/20 Updated: 23/Oct/20 |
|
| Status: | Confirmed |
| Project: | controller |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | CDS management API |
| Description |
|
Our downstreams interested in critical management information for they operation, even when they should not rely on it, should have a better way to get at the information than going through JMX. Devise mechanics how this information can be acquired. If we need some extra classes, these should live in cds-mgmt-impl. OVSDB wants the information it gets from org.opendaylight.ovsdb.utils.mdsal.utils.ShardStatusMonitor |