...
Study is required to clearly define the scope and impacts of updating YANG model schema sets for cmhandles.
| Table of Contents |
|---|
Requirements
Functional
| # | Interface | Requirement | Additional Information |
|---|---|---|---|
| 1 | TBD |
Error Handling
| # | Error Scenario | Expected behavior |
|---|---|---|
| 1 |
Capabilities
| Excerpt | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Characteristics : ++
***
|
Out-of-scope
- Upgrade of models for cached data (only pass-trough ie. non-cached data upgrade will be supported
Solution Proposals
Two options to trigger a module set upgrade. One based on kafka events and one based on REST. Preference is alternative 1 - the Kafka based solution.
...
If the moduleSetId json property is set to "" (empty string) or then it should also indicate that the moduelSet for a cmhandle has been updated but there is no associated moduleSetId available for that cmhandle. This approach will always result is a full request to the dmi plugin for the module set for the cmhandle.
Characteristics : ++
- It shall be possible to upgrade moduleSets for cmhandles at a rate of 5 / second when the moduleSetIds are unknown to NCMP. ***
- It Shall be possible to upgrade moduleSets for cmhandles at a rate of 10 / second when the provided moudleSetIds are already known to NCMP.
***The assumption is there are 100 modules in each moduleSet and a moduleSet is available from a dmi plugin within 0.5 seconds. Also assume there is a 90% overlap in modules across all CM Handles.
++ Assumes 2 NCMP instances running.