ONAP Architecture for Rel 1

Slides:

Advertisements

Similar presentations

OSCAR Project Proposed Project for OPNFV

Advertisements

BoF: Open NFV Orchestration using Tacker

Specific SDK Specific SDK NFVO Specific VNFM Specific VNFM VNF Message Queue JSON REST API.

Service Design & Onboarding

ONAP E2E Flow `.

ONAP Management Requirements

ARC: Definitions and requirements for SO/APP-C/VF-C discussion including call notes Chris Donley July 5, 2017.

Master Service Orchestrator (MSO)

Orchestration and Controller Architecture Alignment Vimal Begwani AT&T

Rationalizing ONAP Architecture for R2 and Beyond Vimal Begwani – AT&T

Open Network Automation Platform (ONAP) Controller Architecture Proposal DRAFT.

Data Collection Framework

ONAP Architecture Meeting 8/8

Enterprise vCPE September 27, 2017.

Existing Applications Applications built on SDK

Multi-VIM/Cloud High Level Architecture

Orchestration and Controller Alignment for ONAP Release 1

ONAP Architecture Slides Current Plan of Record

Example Services Managed by OpenECOMP Demo

ONAP Multi-VIM/Cloud Long Term Architecture and Use Cases (Under Community Discussion across Use Case, Optimization Framework, OOM,

5G Network Deployment, Slicing, Network Optimization and Automation Framework – Use Case Deep Dive 5G Use Case Team.

CLAMP Flows for vCPE Use Case in ONAP R1 Ron Shacham AT&T

Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.

Defining ONAP VNF Package Model

Multi-VIM/Cloud High Level Architecture

Multi-VIM/Cloud High Level Architecture

Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.

Rationalizing ONAP Architecture for R2 and Beyond

Interface to External Controllers and SD-WAN Use Case

ONAP and SD-WAN Integration Proposal

Alla Goldner (outcomes from brainstorming meetings) Sept, 2017

ONAP Interface to External Controllers

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)

Agenda Overview High Level Architecture Design time Architecture

ARC 5: Deployment Options Chris Donley

ONAP Architecture Slides Current Plan of Record

MEF LSO Legato SDK 24 October 2017 Andy Mayer, Ph.D. Tara Cummings.

Target ONAP End-to-End Architecture Vimal Begwani – AT&T Parviz Yegani – Futurewei Technologies Jamil Chawki – Orange.

Multi-VIM/Cloud High Level Architecture

ONAP Optimization Framework - HAS Shankar Narayanan - AT&T Labs Research 08/15/2017.

Enterprise vCPE use case requirement

ONAP Run-time Catalog Project

Target ONAP End-to-End Architecture Tiger Team Presentation Parviz Yegani – Futurewei Technologies Contributors: Vimal Begwani (AT&T), Jamil Chawki.

ONAP Amsterdam Architecture

ONAP – Centralised Parser Distribution Atul Purohit - Vodafone

Enhanced Platform Awareness (EPA) Alex Vul Intel Corporation

VF-C R2 Feature Planning & Implementation Yan Yang

Agenda Where we are (Amsterdam Architecture)

ONAP APIs Andrew Mayer, AT&T

SDNC Roadmap Dan Timoney – AT&T Marcus Williams - Intel

Open Source Access Manager™ ONAP Proposal

ONAP Amsterdam Architecture

Casablanca Platform Enhancements to Support 5G Use Case Architecture Review 5G Use Case Team June 26, 2018.

Isasku, Srini, Alex, Ramki, Seshu, Bin Hu, Munish, Gil, Victor

Documenting ONAP components (functional)

Multi-VIM/Cloud High Level Architecture

Management and Orchestration in Complex and Dynamic Environment

FUNCTIONAL Architecture for R2+

Defining ONAP VNF Package Model

ONAP 5G USE CASE ENHANCEMENTS FOR PNF DEPLOYMENTS

TOSCA Native Service Orchestration SO State of the Union

ONAP & ETSI NFV converged architecture

Draft for the detailed SO Flows for R1

SOL003 Adapter Architecture, Technical Debt and Roadmap

GNFC Architecture and Interfaces

ONAP Architecture Overview Template

Proposed Approach for ONAP Runtime Support of Network Service Onboarding Gil Bullard, AT&T.

Title: Robust ONAP Platform Controller for LCM in a Distributed Edge Environment (In Progress) Source: ONAP Architecture Task Force on Edge Automation.

Presentation transcript:

ONAP Architecture for Rel 1 should be aligned with VNF Guidelines and Artefacts … ? ONAP User ONAP Portal Admin OSS/BSS VNF SDK Onboarding SDC Portal Design Studio Distribution Service Service Order Requests Service & Resource Artifacts VNF & Network Requests Modelling AAI Service Orchestrator Policy ? Inventory SDN-O NFV-O Create/Update Cloud Virtual Resources Assign/Configure Network Resources DCAE Assign/Configure VNF/Application Resources MSO metrics collection and fault monitoring SDN Controller OpenDaylight APP Controller OpenDaylight Data Collector Fault Collector Infra Controller OpenStack 3rd Party SDN-C vRouter SO Tosca Based NFVO: Tosca Recipe execution Cloud Infra Instantiation VNF VM Switch App vSwitch VM VM VM VM Cloud Network Application/VNF

Service Logic Interpreter & Adaptors SO SO NFVO VF C App C App C Service Logic Interpreter & Adaptors NFVO VNFM Infra Infra VNF VNF VNF VNF DCAE DCAE Pro: Simpler integration of Open-O Con: difficulties to keep 2 Controllers functionally aligned (SDC, VNF Guidelines, artefacts …) Overlapping functionalities between the controllers (APIs, adapters, workflow engine, languages…) Pro: Integrated architecture with minimal overlap Best of breed components Single VNF Guidelines and reduce VNFM/EM dependency Con: More work on initial integration & APIs