Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-505

Get and Store SchemaSets of node(s) in initial Inventory (new modules only)

XMLWordPrintable

      Description

      1. Process described in DMI NCMP Model Sync.pptx
      2. This user story combines/uses the implementation of CPS-483,CPS-485 and CPS-506
      3. 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

      1. Call dmi–plugin rest endpoint to retrieve all modules on new node (depends CPS-483 and CPS-531)
      2. Call CPS-Core rest endpoint to get all existing modules in cps-core (depends CPS-506)
      3. Calculate difference (delta) 
      4. Call dmi–plugin rest endpoint to retrieve missing modules CPS-483
      5. Add missing modules to cps-core to anchor (cm handle) (depends CPS-508)

      A/C

      1. SchemaSet is created in CPS-Core DB for the given anchor (cmHandle) 
      2. SchemaSet has reference to al the yang resources (source files)
      3. When same cmHandle is (re-)registered NO new yang-resources should be requested/stored
      4. Team demo of above

      Out-of-scope

      1. This user story covers only model sync. Data-Sync wil be handled in future user story CPS-507
      2. No handling of A&AI DMaap events, only initial inventory cm handles covered

        1. DMI NCMP Model Sync.pptx
          147 kB

            josephkeenan josephkeenan
            ToineSiebelink Toine Siebelink
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: