1. State of OPNFV MANO OPNFV MANO WG Report
Prakash Ramchandran, Futurewei Technologies Inc.
Bryan Sullivan – AT&T
16/11/2018

2. Agenda MANO in OPNFV: Guiding Perspectives and Goals
History and Roadmap of MANO in OPNFV
Moving up the MANO Stack from OPNFV VIM is Multi-modal
Project Mapping for Danube
View of Working Groups and Projects in MANO Scope
Comparing Colorado OPNFV Framework & evolving MANO
16/11/2018
State of MANO in OPNFV

3. MANO in OPNFV: Guiding Perspectives and Goals
Given resources, OPNFV has proven to be open to integrating diverse/competing/pre-converged solutions for NFV
MANO in OPNFV should follow that model for any project that wants to collaborate with OPNFV as a framework or component
Open-O, OSM, OpenBaton, Aria, Cloudify, Tacker, JuJu, OpenECOMP
As we are gaining initial experience integrating lower-layer MANO stack components (e.g. VNFMs in the Models project), we are collecting perspectives and seeking consensus on
key aspects of MANO, e.g. VNF Onboarding
OPNFV priorities, e.g. VNF portability, and consistent user experience
embracing implementation diversity / deviation from ETSI MANO model
Upper MANO stack hot-swappability / plug and play interop with VIMs
16/11/2018
State of MANO in OPNFV

4. History and Roadmap of MANO in OPNFV
Arno/Brahmaputra focused on the NFVI exclusively. As of Colorado, we began integrating upper MANO functions mainly as test tools (e.g. the Tacker VNFM for the SFC project). As of Danube we will integrate VNFMs etc as components of the OPNFV platform. As we proceed up the MANO stack, the complexity of integrating these components in a consistent/interoperable way may increase, so we are taking a step-wise approach to integrating them.
E/F
Complexity
NFVO
Service Lifecycle
Reference Network Services
VNFM
VNF Lifecycle
Reference VNFs
VIM
OpenStack
SDN Controllers
C/D
A/B
Release
16/11/2018
State of MANO in OPNFV

5. Moving up the MANO Stack from OPNFV VIM is Multi-modal
The process of assessing/integrating MANO in OPNFV will involve multiple parallel efforts with different focuses. The MANO WG links below will document progress on those efforts.
Define
Predictable Targets
VNF on boarding, VNF Formats, VNF Life Cycle Management
Try
Exploratory Targets
Integrating MANO Components in OPNFV
Evolve
Evolving Targets
Top-Down-Architecture
16/11/2018
State of MANO in OPNFV

6. Project Mapping for Danube
For Danube, these projects will add VNF Onboarding and Management to OPNFV
Opera (Open-O integration)
Open-O Upstream project implements the main parts of onboarding process
Orchestra (Open-Baton integration)
Open-Baton Upstream project implements the main parts of onboarding process
Other projects will contribute MANO-related components which can be integrated into the Opera / Orchestra deployment scenarios
Parser: Translation of templates
Domino: Policy based template mapping and distribution
Copper: Policy artifacts and management
Models: Role of Service/VNF modeling in development, onboarding, production
VES: Analytics modeling and collection
16/11/2018
State of MANO in OPNFV

7. View of Working Groups and Projects in MANO Scope
Summary of projects identified so far as having some specific relation to the scope of MANO
Project/WG
Focus and Approach
MANO WG
Collaboration: provide a common discussion forum for MANO related projects, to optimize interaction (e.g. reduce number of discrete meetings, enable global participation).
Models
Assess and advise: for the various MANO solutions, assess how they approach the goals through their documentation and experience integrating their components (e.g. VNFM) into OPNFV and Functest. Based upon the assessment, provide feedback and advice on opportunities for convergence, and initiate related work upstream per consensus on priorities. In the process, document the degree of convergence, e.g. in data models for services/VNFs and components that leverage/fulfill them.
Domino
Develop: support service/VNF blueprint distribution across diverse NFVI environments, to provide flexibility in how services/VNFs are distributed and adapted to those environments
Parser
Develop: tools for translation between various information and data model formats
Copper
Develop: configuration policy modeling and management
VES
Develop: common data model for telemetry collection from VNFs and NFVI
16/11/2018
State of MANO in OPNFV

8. Comparing Colorado OPNFV Framework & evolving MANO
OPNFV has been focused on NFVI so far, which is more easily mapped to the ETSI NFV architecture. As upper MANO stack components are integrated, we can expect the diversity of those components to blur boundaries/roles of the ETSI-referenced elements e.g. NFVO, VNFM, EMS, OSS/BSS, ...
Some convergence toward the ETSI architectural model may occur over time, but that is not an explicit or first-order goal of more fully integrating MANO functions into OPNFV.
16/11/2018
State of MANO in OPNFV

9. For more information
MANO WG site :
16/11/2018
State of MANO in OPNFV