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

Spike: Analyse E2E API GET methods

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • None

      Analyse all API GET calls listed on this page: https://wiki.onap.org/display/DW/CPS+APIs

      (#2 and #21 have already been analyzed and required queries been identified)

      • Ensure use case is clear using given model and data example
      • Find out required (new) query functionality in CPS (several API call might need same CPS functionality)to 'find' the required data given the provided parameters (request payload) and model.
      • One (Slicing) 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 NW Slicing specific data.

      A/C

      1. Wiki Page with conclusion for each API call
      2. Add new query functionality if needed to  https://wiki.onap.org/display/DW/CPS-235%3A+Overview+of+%28early%29+CPS+Query+and+Update+Scenarios
      3. Review with full team

       

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

              Created:
              Updated:
              Resolved: