...
Using the 8 LFN project, an end user (e.g., a carrier) can realize the above as follows:
Phase 0 - Building the network infrastructure and preparing the network functions
Following the CNTT Reference model, the operator decides which CNTT Openstack based Reference Architecture Reference Architecture (Proposed by Hiroshi Dempo) may best suit its needs. This is followed by picking a set of infrastructure components that fits a CNTT Reference Implementation of choice. The infrastructure is built using the deployment tolls and CI/CD provided by OPNFV. Next, the infrastructure is certified using the CNTT RC and OPNFV CVC.
...
- An NFV vendor pre-validates and certifies a couple of VNFs (i.e., VNF1 and VNF2) through the OPNFV Verification Program (OVP). (Bin Hudo you think we should/could expand?)
- The NFV vendor ensures that the VNF complies with the ONAP VNF requirements. This will enable ONAP to properly control the lifecycle of the VNF as part of a network service.
Phase 1 - Network service design and deployment
At design time, ONAP is used to onboard the VNFs that are compliant with the ONAP requirements and pre-certified using the OPNFV CVC . Those compliant resources can later be used to design any E2E service using ONAP Service Design and Creation (ONAP SDC).
...
The predefined policies that will control the lifecycle of the network service are designed using the ONAP design-time components such as CLAMP.
Phase 2 - Network service operation
Naturally, being a Network Automation Platform, ONAP plays a central role in the delivery and assurance of the service. The VNFs report their performance and fault data to the ONAP DCAE using the VNF Event Streaming (VES) interface. This information is constantly analyzed and may trigger predefined policies that were created at design-time. The policies are used to invoke closed loop automation actions such as scaling and healing of service components in order to assure the required SLA and respond to changing demands and network conditions.
...