White Papers

Understanding OPNFV

Issue link: https://read.uberflip.com/i/1344850

Contents of this Issue

Navigation

Page 57 of 144

Understanding OPNFV 57 ECOMP ECOMP adds several capabilities over and above the ETSI MANO architecture. It addresses the entire service delivery lifecycle using model driven architectures. For example, it has a rich service design environment for service creators to build services using a collaborative, catalog- driven self-service design studio. The design studio also creates service, VNF, and infrastructure descriptions that are richer in scope than what's required by the ETSI architecture by adding numerous pieces of metadata. NFVO and VNFM functionalities are enhanced for greater control over NFVI, VIM, and SDN controllers, and for faster on-boarding of new VNF types. ECOMP supports YANG, TOSCA, OpenStack Heat and other modeling languages. Finally, the project includes FCAPS (Fault, Configuration, Accounting, Performance, Security) functionality to provide greater control over closed loop automation (in the ETSI architecture this functionality resides in the EMS – Element Management System). While OpenStack is the primary VIM (Virtual Infrastructure Manager) supported, Open Source ECOMP can be extended to other VIMs too. OPEN-O is a Linux Foundation open orchestration project that combines NFV MANO and connectivity services orchestration over both SDN and legacy networks. OPEN-O employs a model-driven automation approach, and has adopted standard modeling languages YANG (for networking devices) and TOSCA (for services). The OPEN-O architecture is partitioned into three main orchestration functions: global services orchestrator (GSO), SDN orchestrator (SDN-O), and NFV orchestrator (NFV-O), along with a

Articles in this issue

Links on this page

view archives of White Papers - Understanding OPNFV