...
Use Cases
- TBD
SOL001/SOL004 Support
x
- SO SDC Controller gets a SOL004 VNF package with an SOL001 VNFD
- SO SDC Controller stores a VNF CSAR file reference to the SO Catalog DB (e.g., TOSCA_CSAR database table)
- VNFM Adapter gets a CSAR package URL from the SO TOSCA_CSAR database table
- VNFM Adapter gets an original CSAR package file from the SDC repository
Note: SO future release could consider SOL001/SOL004 internal representation in its Catalog DB, or using the Run-time Catalog DB
SO VNFM Adapter SOL003 API Support Design
...
- SO VNFM Adapter component (a sub component of SO; docker image and container manged)
- North Bound Interface (NBI)
- RESTful APIs that support createVnf, instantiateVnf, queryVnf
- Business Logic layer
- It is invoked by the NBI and provides business logic for createVnf, instantiateVnf, queryVnf
- SDNC and A&AI access to collect assignment and VimConnectionInfo
- Access SdcPackageProvider for getting SOL003 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
- SOL003Lcn APIs
- Support VnfIdentifierCreationNotification, VnfIdentifierDeletionNotification, VnfLcmOperationOccurrenceNotification
VNFM Adapter - SVNFM SOL003 Interfaces
Create VNF
-HTTP Method Type: POST
-VNFM Endpoint: /vnf_instances/
-Request Payload: CreateVnfRequest
-Response Header: 201 success
-Response Body: VnfInstanceInstantiate VNF
-HTTP Method Type: POST
-VNFM Endpoint: /vnf_instances/{vnfInstanceId}/instantiate
-Request Payload: InstantiateVNFRequest
-Response Header: 202 success
-Response Body: not applicableGrant VNF Request
-HTTP Method Type: POST
-VNFM Endpoint: /grants
-Request Payload: GrantRequest
-Response Header: 201 success
-Response Body: not applicableScale VNF
HTTP Method Type: POST
VNFM Endpoint: /vnf_instances/{vnfInstanceId}/scale
Request Payload: ScaleRequest
Response Header: 202 accepted
Response Body: not applicable
- Dublin Requirements
- Build SO VNFM Adapter
- Use SOL003 APIs for VNFM communication
- Support operations such as create, instantiate, scale, etc.
- Support SOL001 VNFD and SOL004 Package
- Enhance SO BPMN workflows & recipes
- Pass VNF LCM requests to VNFM using Adapter
- Modeling and A&AI Updates maybe required
- Some of this work may already be implemented
- Build SO VNFM Adapter
- SO VNFM Adapter Requirements for Dublin
- New SO subcomponent, following ONAP Microservice Architecture
- Generic VNFM Adapter, supporting SOL003-compliant SVNFMs
- Support SOL003 APIs
- Design
- ...
- Impacted ONAP components
- SO
- SO Catalog DB for SOL001/SOL004 support
- BPMN Workflows and Recipes
- VNFM Adapter
- SDC
- Support SOL001/SOL004
- SDNC
- VNF-level Network Assignment, instead of VF-Module
- A&AI
- VNF-level Inventory Update
- VNFM location
- Policy
- Scale-Out support for ETSI-based scaling
- Modeling
- Support SOL001/SOL004
- SO
- Open Items
- VNF vs. VF-Modules Modeling