-
Story
-
Resolution: Done
-
High
-
None
Description
- Process described in DMI NCMP Model Sync.pptx
- This user story combines/uses the implementation of
CPS-483,CPS-485andCPS-506 - The model-sync wil be triggered after the initial-dmi registration (hidden temporary rest endpoint, see
CPS-442
See presentation attached, steps for this user story
- Call dmi–plugin rest endpoint to retrieve all modules on new node (depends
CPS-483andCPS-531) - Call CPS-Core rest endpoint to get all existing modules in cps-core (depends
CPS-506) - Calculate difference (delta)
- Call dmi–plugin rest endpoint to retrieve missing modules
CPS-483 - Add missing modules to cps-core to anchor (cm handle) (depends
CPS-508)
A/C
- SchemaSet is created in CPS-Core DB for the given anchor (cmHandle)
- SchemaSet has reference to al the yang resources (source files)
- When same cmHandle is (re-)registered NO new yang-resources should be requested/stored
- Team demo of above
Out-of-scope
- This user story covers only model sync. Data-Sync wil be handled in future user story
CPS-507 - No handling of A&AI DMaap events, only initial inventory cm handles covered
- is blocked by
-
CPS-442 Implement DMI Registration (NCMP-Side)
- Closed
-
CPS-483 Retrieve list of Yang Modules for an cm-Handle (DMI-Plugin impl)
- Closed
-
CPS-484 Retrieve yang-resources for one or more modules for a cmHandle (DMI Plugin impl)
- Closed
-
CPS-506 List all known modules and revisions (java API only)
- Closed
-
CPS-508 Create anchor/schemaset from new modules and existing modules
- Closed
- relates to
-
CPS-615 Demo & CSIT Test for Model-Sync
- Closed
(1 relates to, 2 mentioned in)