...
- Vendor SVNFM must be "SOL003-compliant"
- Providing SOL003 APIs for VNFM LCM, based on ETSI VNFLifecycleManagement
- Use https://forge.etsi.org/gitlab/nfv/SOL002-SOL003/2.5.1/master/src/SOL003/VNFLifecycleManagement swagger for providing services
- Create
- Instantiate
- Grant request to SO VNFM Adapter, as a client
- Life cycle notification
- Terminate/Delete
- Registration itself to ONAP (thru A&AI ESR) - Name, Type, Vendor, Version, URL, VIM, Username and Password
- Providing Subscription Services for Life-cycle Management Notifications
- Due to SDC SOL004 package support issues in Dublin, manual onboarding VNF Packages are needed for SVNFM.
- Support of the "Direct Mode" of Resource Management only
- After receiving a grant permission, the VNFM sends requests for resources directly to VIM
- Invoking MultiCloud from VNFM is under discussion, but not for Dublin
- The "Indirect Mode" of Resource Management is being discussed, but not for Dublin
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
- SO VNFM Adapter component is a sub component of SO; utilizing docker image and container managed.
- North Bound Interface (NBI)
- RESTful APIs that support createVnf (invokes both createVnf and instantiateVnf), grantVnf, TerminateVnf/DeleteVnf
- Its APIs are SO specific; i.e., not SOL003-based ones; for the NB API details, see the SO VNFM Adapter APIs page.
- Business Logic layer
- It is invoked by the NBI and provides business logic for createVnf, instantiateVnf, terminateVnf/DeleteVnf
- SDNC and A&AI access to collect assignment and VimConnectionInfo
- Accesses SdcPackageProvider for getting SOL004 package(s) and parameters
- SdcPackageProvider
- Supports SOL001/SOL004 package management
- Provides getPackage, getVnfdId, getFlavorId, getVnfNodeProperty
- Provides getPackage(s), getVnfd, getArtifactFile for SVNFM
- Uses SDC Tosca Parser
- GrantManager
- Provides requestGrantForInstantiate REST API for SVNFM
- Invokes OOF for homing decision; HPA support, and/or non-OOF decision
- SOL003Lcn APIs
- Supports VnfIdentifierCreationNotification, VnfIdentifierDeletionNotification, VnfLcmOperationOccurrenceNotification
- SOL003 Communication Layer
- It is a thin REST client layer, which sends SOL003-compliant requests to SVNFMs and receives responses/notifications from SVNFM.
- For Grant, it provides the Grant REST endpoint for SVNFM
- For the SOL003 Southbound API details, see the SO VNFM Adapter APIs page.
- North Bound Interface (NBI)
- SO VNFM Adapter component is a sub component of SO; utilizing docker image and container managed.
...
CSAR Import, Store and Retrieve Sequences
- SDC stores the original vendor VNF package along with the transformed ONAP-compliant package.
- Note: this will not supported SDC Dublin.
- SO uses SDC-transformed CSAR packages and VNFM Adapter uses the original Vendor CSAR package.
- Note: since SDC Dublin does not support the original vendor CSAR package, SO VNFM Adapter will retrieve VNFDs from SDC.
- For that reason, the following steps 1, 2, 3 and 4 have been simplified and adjusted.
- In Dublin, SVNFM needs to onboard its VNF packages.
- SDC stores the original vendor VNF package along with the transformed ONAP-compliant package.
Design
...
VNF Application Configuration thru VNFM Adapter and VNFM is under discussion (out of scope from Dublin)
Architecture subcommittee is defining orchestration scenarios for application configuration
Better mechanism for VNFM Adapter to locate VNFMs (two methods are suggested)
How do we identify which VNFM to use?
Modelling for VNF and VF Modules; mapping between VF Modules and VNF (out of scope from Dublin)
Assigning Network resources to SDNC; do we use preload data?
Continue to support existing non-ETSI SO workflows along with ETSI-based workflows
SOL001/SOL004 SO Representation (for Dublin, the second option was chosen)
Option #1: Enhance SO Catalog Database?
VNF_Package (vnfdid, vnfm_info, version, vnf_provider, product, vendor, etc.)
VNF_Package_Artifact (child database for VNF_Package, VNFD_URL, SoftwareImage_URL, Additional Files etc)
Option #2: Store minimum reference in TOSCA_CSAR database table? This was chosen for Dublin
MultiCloud use (not for Dublin)
SO VNFM Adapter High Availability and error handling are not fully covered.