Versions Compared

Old Version 36

changes.mady.by.user Manoj Nair

Saved on

compared with

New Version 37

changes.mady.by.user Manoj Nair

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleDerived Ext-API Interlude Requirements

External API Requirements for supporting Inter-Provider API

Roles / Actors

    • SP A (ONAP deployment)
      • Administrator: Manages lifecycle of Services
      • Operation Engineer: Manages operational tasks like distribution of packages, manage/process work orders
      • Designer: Onboard VNF packages and designs Service Package
      • Tester: Verifies the Service package and approves the package for distribution
    • SP B (assuming a non-ONAP deployment)
      • Administrator: Manages the lifecycle of services
      • Operation Engineer : Manages operational tasks
    • Partner A (assuming an ONAP deployment)
      • same as for ONAP SP
    • Partner B (assuming a non ONAP deployment)
      • Administrator: Manages lifecycle of Services
      • Operation Engineer : Manages Operational

Types of Interactions

Image Added

General Requirements

Expand
titleONAP Dublin Requirements

Requirements

Study how we can control modification requested at Interlude level – they are at least 2 subtopics there:

    • Identify where the information could be managed within ONAP (in SDC ? have attribute change value and state change authorized at SOF-SOF interaction level ?)
    • Explore if External API can be used by internal ONAP Components as a proxy to talk to external Partner ( e.g. ONAP 1 SO call ONAP 1 ExtAPI, then ONAP 1 ExtAPI call ONAP 2 ExtAPI ) i.e. ONAP internal components can communicate securely internally, External API act as proxy to forward request ( e.g. Service Order ) to Partner ( maybe a Partners ONAP External API Framework ). 
    • Define the API (resource model) that allow the system to request ‘authorized’ service modification (Policy API ?)

Dependency on other projects

...