This section aims to present an end-to-end use case where the 8 LFN projects work in harmony to deliver a "service" that includes VNFs, connectivity and analytics-powered assurance as shown in the following picture:
In this example, 2 VNFs (for the sake of simplicity, provided by the same vendor) must be deployed on top of an NFVI (e.g., OpenStack), be interconnected and provided with external connectivity to the Internet. Moreover, the VNFs require network acceleration and the whole service must be assured using Analytics driven closed loop operations.
...
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.
Several LFN projects may be used as infrastrucutre building blocks for addressing the needs of network functions, such as high throughput/low latency networking:
- OpenDaylight and Tungsten Fabric can be used as 3rd party SDN solutions. As described in the OPNFV Documentation, OpenDaylight uses the standard ML-2 plugin whereas Tungsten Fabric is integrated by means of Tungsten Fabric plugin for OpenStack which implements Neutron API. (Proposed by Hiroshi Dempo)
- Open Switch (OPX) can be used to configure the physical (underlay) network that connects the physical hosts used to deploy OpenStack (Mike Lazar is this correct? can OPX being instructed by ONAP? Should it?) Leaf and spine topology as a physical infrastructure is recommended in the requirements of physical infrastructure . (Hiroshi Dempo )
- FD.io provides data plane network acceleration through its Vector Packet Processor (VPP). (it would be great to have ONAP instructing FD.io.Or perhaps ODL can do it? Abhijit Kumbhare)
...
ONAP deploys the VNFs in the available NFVi and the overlay network connecting them using ONAP SDN-C. SDN-C uses its OpenDaylight based architecture to model and deploy the L1-L3 network. Next the ONAP APP-C is used to configure the network functions and their L4-L7 functionality. This is also done leveraging the OpenDaylight architecture.
In a case where OpenDaylight manages leaf and spine switch fabric (SDN-based network infrastructure), OpenStack Neutron is a client application of the OpenDaylight SDN controller. OpenStack Neutron interacts with the OpenDaylight SDN controller to manage virtualised networks via OpenDaylight plugin. The OpenDaylight SDN controller interacts with agents running on the host servers (e.g. OpenStack compute, controller). OpenStack Neutron does not have any features to manage underlay network infrastructure resources. Therefore, ONAP-SDNC works as another client application of the OpenDaylight SDN controller to complement the OpenStack weakness. Through the OpenDaylight-NBI, ONAP-SDNC is able to instruct the OpenDaylight SDN controller for underlay network management. The southbound interfaces (e.g. NETCONF, etc) support interactions with OpenSwitch running on the leaf and spine switches in the NFVI. (Hiroshi Dempo )
By leveraging its SDN-C southbound interface, ONAP instructs Tungsten Fabric to create the external connectivity that will enable customers to "consume" the services offered by the VNFs. (Prabhjot Singh Sethido you think we should/could expand?)
...