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

Implement DMI Registration (NCMP-Side)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Istanbul Release
    • None
    • NCMP

      implement API method #1 from https://wiki.onap.org/display/DW/CPS-390+Spike%3A+Define+and+Agree+DMI+Plugin+REST+Interface#CPS390Spike:DefineandAgreeDMIPluginRESTInterface-DMIInventory,Model&DataSyncAPI

      including REST and Service Layer

      A/C

      Update yaml to create an endpoint for registration in NCMP

      Deprecate 'old' (defined in H) methods in Open API 
      accept properties in json format
      Agree and implement error scenarios
      Keep track of error scenarios in a separate table https://wiki.onap.org/display/DW/CPS+Exceptions+and+REST+API+HTTP+Response+Codes
      An error will tell the DMI Plugin that this datasource has already been processed - no need to recover the cmhandles again.
      Store cmhandle name and cmhandle id and additional properties within the db from the ri module
      Use java service api in cps
      Write groovy tests
      Verify registration is successful by showing the data in the db
      Demo to team using a deployment that has cps core and ncmp

      Naming Suggestions

      • REST endpoint data object : dmiPluginRestration { dmiPlugin, createdCmHandles[ {cmHandle, additonalProperties[]] }

        (as per body on 390 study)

      • Java API can use similar object;  updateDmuiPluginRegsitration(dmiPLuginRegistration)

       

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

              Created:
              Updated:
              Resolved: