OPEN-O integrate both SDN-O and NFV-O to provide the end to end network service orchestration, in the case of vCPE/vBRAS, Enterprise, VPN et al, it need to configure broadband and enterprise access by SDN-O(orchestrator), virtual network function like vCPE/vPE router via NFV-O, and VPN tenant connection through DC-O. And one global "O" is proposed to coordinate two "O"s. OOP (OPEN-O Project) has designed a hierarchical "O" to facilitate the deployment. Since two "O"s could share some common modules, two data models Yang and Tosca will be translated between or within each "O", so one open source project would be considered to be proposed.Starting from NFVO which could work with multiple generic VNF Managers(Tacker, et al.) in Openstack, SDN controller (ODL, et al.), and Virtual Resrouce Manager (Openstack, Vmware et al.) to deploy virtual network function. From now on, we are looking into the possbility to implement the SDNO based on the common platform.
The Telecom/NFV track is brought to you by OpenStack and OPNFV.
The architecture of OPEN-O, how NFV-O is implemented, and how VNFM like tacker works with NFV-O, the process of NFV orchestration. This presentation will demonstrate how both fixed and mobile network VNFs will be configured by OPEN-O, how network service is orchestrated.Some VNFs are in one Telecom Integrated Cloud(TIC), other VNFs are deployed in a different TICs, the location of VNFs will be based on the location of end to end network infrastructure.