State of OPNFV MANO OPNFV MANO WG Report

Slides:



Advertisements
Similar presentations
Virtualized Infrastructure Deployment Policies (Copper) 19 February 2015 Bryan Sullivan, AT&T.
Advertisements

Introducing Open Platform for NFV Please direct any questions or comments to 1.
Please direct any questions or comments to
Introducing Open Platform for NFV Please direct any questions or comments to 1.
© 2015 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual.
OSCAR Project Proposed Project for OPNFV
Copyright © 2014 Juniper Networks, Inc. 1 OSCAR Project Proposed Project for OPNFV Stuart Mackie NFV/SDN Architect.
IETF 91: Open Platform for NFV Collaboration with I2NSF Chris Donley 1.
OpenContrail for OPNFV
BoF: Open NFV Orchestration using Tacker
DOCUMENT #:GSC15-PLEN-82r2 FOR:Presentation SOURCE:ATIS AGENDA ITEM: PLEN 6.14 CONTACT(S): Andrew White ATIS’
1 Adopting and Embracing Open Source for NFV Guy Shemesh Senior Director for Cloud Solutions, CloudBand October 2015.
Open Source and Info Models 17 Dec 2015 Bryan Sullivan, AT&T.
OPEN-O for MODM Unified NFV/SDN Open Source Orchestrator
14 March 2016 Bryan Sullivan, AT&T Artur Tyloch, Canonical
© 2016 TM Forum | 1 NFV Ecosystem Enabler: A well-enabled VNF package Catalyst Theater Presentation, May 10, 2016.
Model-Driven NFV (Models) Project 22 March 2016 Bryan Sullivan, AT&T.
Benoit Claise Mehmet Ersue
OSM - Open Source MANO An open-source project hosted by ETSI
What is OPNFV? Frank Brockners, Cisco. June 20–23, 2016 | Berlin, Germany.
June 20–23, 2016 | Berlin, Germany. Copper: Configuration Policy Management in OPNFV Colorado Bryan Sullivan, AT&T.
June 20–23, 2016 | Berlin, Germany. MANO Modeling: Service, Infrastructure and VNF On-Boarding and Interoperability Uri Elzur, Intel Bryan Sullivan, AT&T.
Project Tacker Open Platform for NFV Orchestration OPNFV Design Summit.
Contributors: Vimal Begwani (AT&T) Dean Bragg (AT&T) Lingi Deng (CMCC)
Learnings from the first Plugfest
Open Source Summit May 8, 2017.
SDN-O LCM for Mercury Release Key Points and Overview
Open-O SFC.Mgr Proposal
OPEN-O VNF Supplier APIs & SDK Project Proposal
ARC: Definitions and requirements for SO/APP-C/VF-C discussion including call notes Chris Donley July 5, 2017.
Bryan Sullivan, AT&T June 13, 2017
OPEN-O Architecture Comments
Orchestration and Controller Architecture Alignment Vimal Begwani AT&T
Rationalizing ONAP Architecture for R2 and Beyond Vimal Begwani – AT&T
14 April 2016 Bryan Sullivan, AT&T
Orchestration and Controller Alignment for ONAP Release 1
Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.
OPEN-O Modeling Directions (DRAFT 0.6)
Defining ONAP VNF Package Model
Tina Tsou, Bryan Sullivan,
Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.
TSC Update at December Board Meeting
ETSI NFV: IFA & SOL specifications list
Alla Goldner (outcomes from brainstorming meetings) Sept, 2017
ARC: Definitions and requirements for SO/APP-C/VF-C discussion Chris Donley Date , 2017.
ONAP Architecture Meeting 8/8
OPEN-O Modeling Directions (DRAFT 0)
Escalator: Refreshing Your OPNFV Environment With Less Troubles
OPNFV Doctor - How OPNFV project works -
ARC 5: Deployment Options Chris Donley
Zongbiao OPEN-O VNF SDK Design Zongbiao
Introduction to OPNFV CVP
Dovetail project update
SDN World Congress, The Hague, October 10-13, /10/2016.
17 Dec 2015 Bryan Sullivan, AT&T
EOB Methodology Overview
ONAP – Centralised Parser Distribution Atul Purohit - Vodafone
OASIS TOSCA Report for December ONAP Modeling Workshop
Agenda Where we are (Amsterdam Architecture)
ONAP Amsterdam Architecture
Christopher Donley Prakash Ramchandran Ulas Kozat
OSM Workshop SDN World Congress Oct’16
ONAP Beijing Architecture Chris Donley 1/9/18
Casablanca Platform Enhancements to Support 5G Use Case (Network Deployment, Slicing, Network Optimization and Automation Framework) 5G Use Case Team.
ONAP & ETSI NFV converged architecture
5G RAN Deployment – Casablanca PNF software and configuration management Huawei,
Open Source MANO (OSM) develop an Open Source MANO software stack aligned with ETSI NFV ISG
For Community and TSC Discussion Bin Hu
ONAP Architecture Principle Review
Title: Robust ONAP Platform Controller for LCM in a Distributed Edge Environment (In Progress) Source: ONAP Architecture Task Force on Edge Automation.
Presentation transcript:

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

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

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

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

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

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

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

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

For more information MANO WG site : https://wiki.opnfv.org/display/mano 16/11/2018 State of MANO in OPNFV