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

Remove CmHandle in DMI-Registry for a DMI-Plugin Instance

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: High High
    • Istanbul Release
    • Istanbul Release
    • None

      CmHandles could change their additional properties.

      NCMP can be informed of this using the existing (registration) API call on NCMP (#1 in https://wiki.onap.org/display/DW/CPS-390+Spike%3A+Define+and+Agree+DMI+Plugin+REST+Interface#CPS390Spike:DefineandAgreeDMIPluginRESTInterface-DMIInventory,Model&DataSyncAPI

       For this user story the payload labeled "removedcmhandles" needs to be implemented. ie. any entries in this need to be updated in the registry

      If an entry in "removedcmhandles"  does not exist we can probably silently ignore this

      A/C
      Update the schema in the yaml file to include an operation to indicate it is a remove operation
      Accept an array of cm handles "removedCmHandles" : [ "node-1", "node-2" , ... ]
      Add a new method to ncmp service Interface
      Call method in the cps java API deleteListNode
      Remove cm handle changes in the db

            dylanb95est dylanb95est
            ToineSiebelink Toine Siebelink
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: