...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
- SOL003 Adapter continues to be an SO microservice component, and exposes its NBI to any SOL003 Adapter client in ONAP
- SOL003 Adapter is registered to MSB.
- Operator registers VNFM and VIM to ESR in AAI.
- SOL003 Adapter exposes its NBI to any SOL003 Adapter client in ONAP (not for Frankfurt)
- Interfaces will be refactored to be generic to allow access by other ONAP components.
- The NBI will be enhanced for additional SOL003 operation support
- SDC distributes SDC packages including the vendor original SOL004 (VNF and PNF) and SOL007 (NS) packages – SOL007 is not for Frankfurts
- SO (SDC Controller) passes the SDC CSAR ID to ETSI Catalog Manager to invoke storage
- ETSI Catalog Manager queries for SDC CSAR with the SDC CSAR id & store SOL004/SOL007 package.
- SO (BPMN) and the SOL003 Adapter client locates SOL003 Adapter.
- SO (BPMN) and the SOL003 Adapter client invokes SOL003 Adapter.
- SOL003 Adapter retrieves VNF package from Catalog Manager.
- SOL003 Adapter gets available VNFM locations (endpoints) and gets VIM and VNF Info.
- SOL003 Adapter selects a VNFM, based on a VNFM locating mechanism.
- SOL003 Adapter and SVNFM supports SOL003 VNF LCM, granting and package management operations.
- SOL003 Adapter supports HPA-based Granting, leveraging OOF.
- SOL003 Adapter updates vServer, status and VNF association in AAI
- SOL003 Adapter and SVNFM support authentication and authorization (AAF, and vendor AA mechanism) – partially for Frankfurt.
- For integration testing, the VNFM Simulator is used.
...