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

Analyse SON Use case PUT,PATCH & DELETE endpoints

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Low Low
    • Jakarta Release
    • None
    • None
    • None

      Analyse API PUT calls listed on this page for SON use case

      • Ensure use case is clear using model and data example
      • Find out required (new) update functionality in CPS (several API call might need same CPS functionality.
      • One API call might require more then one CPS-Core call, indicate in report if this is the case
      • One API call might need to access more then one model (report!)
      • Distinguish between NCMP (ran network data) and CPS-Core access for slicing specific data.

      A/C

      1. Wiki Page with a conclusion for each API call (see toines example for API call no.2 https://wiki.onap.org/display/DW/CPS+APIs)
      2. Add new update functionality if needed to https://wiki.onap.org/display/DW/CPS-235%3A+Overview+of+%28early%29+CPS+Update+Scenarios
        https://wiki.onap.org/display/DW/CPS-235%3A+Overview+of+%28early%29+CPS+Query+and+Update+Scenarios
      3. Review with the full team
      4. Review with SON team

            mohak mohak
            niamhcore niamhcore
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: