ONAP Architecture Slides Current Plan of Record

Slides:

Advertisements

Similar presentations

Open Network Automation Platform (ONAP) Use Case Driven Architecture Proposal DRAFT.

Advertisements

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.

Microservice Powered Orchestration

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) & Opendaylight Controllers

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

ONAP layering/MEF alignment

Data Collection Framework

ONAP Architecture Meeting 8/8

Intel HF2 ONAP Community POD 01 (AKA: POD-25)

ONAP Project Proposal Training

Existing Applications Applications built on SDK

Multi-VIM/Cloud High Level Architecture

ONAP SDC VoLTE Model Support

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,

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

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

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.

ONAP Integration to External Domain Management Systems (DMS)

Multi-VIM/Cloud High Level Architecture

VoLTE Use Case Proposal

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

Alex Vul and Ramesh Nagarajan DMS Task Force

ONAP Run-time Catalog Project

ONAP Reference Architecture for R2 and Beyond Tiger Team Presentation Parviz Yegani – Futurewei Technologies Contributors: Vimal Begwani (AT&T), Jamil.

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

ONAP Reference Architecture for R2 and Beyond Tiger Team Presentation Parviz Yegani – Futurewei Technologies Contributors: Vimal Begwani (AT&T), Jamil.

ONAP Amsterdam Architecture

PNF and Mixed Infrastructure Support for EtE Network Slicing --Cloud Infrastructure Controller Vivien Yang.

VF-C R2 Feature Planning & Implementation Yan Yang

Agenda Where we are (Amsterdam Architecture)

ONAP APIs Andrew Mayer, AT&T

Open Source Access Manager™ ONAP Proposal

ONAP Amsterdam Architecture

ONAP Integration Through Information and Data Modeling

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

Documenting ONAP components (functional)

Multi-VIM/Cloud High Level Architecture

Management and Orchestration in Complex and Dynamic Environment

FUNCTIONAL Architecture for R2+

ONAP Beijing Architecture Chris Donley 1/9/18

Defining ONAP VNF Package Model

ONAP Architecture for Rel 1

ONAP 5G USE CASE ENHANCEMENTS FOR PNF DEPLOYMENTS

TOSCA Native Service Orchestration SO State of the Union

Draft for the detailed SO Flows for R1

SOL003 Adapter Architecture, Technical Debt and Roadmap

GNFC Architecture and Interfaces

ONAP Architecture Overview Template

Presentation transcript:

ONAP Architecture Slides Current Plan of Record Chris Donley

VFC/APPC Architecture Baseline for R1 Portal OPEN-O UI (GUI/CLI) Run-time Modeling (specs & Utilities) Integration Certification & Lab Security High Availability Dashboard OA&M (VID) External Data Movement & APIs Design-time A&AI Service Orchestration SDC UI Server VNF Design Service Design Workflow Design Common Service DMaaP ESR Auth. Microservice Bus Policy Creation SDN-C APP-C VF-C (NFV-O) DCAE Policy Analytic Application Creation Alarm Correlation App (Holmes) Recipie/ Engineering Rules & Policy Distribution (G/S)-VNFM Catalog NFV-O NFV Collector (Monitor) Multi-VIM/MultiCloud VNF SDK Cloud & WAN OpenStack VMware RackSpace Azure ...... Architecture Baseline for R1. SO and VFC PTLs to talk and see if they can make additional progress towards longer-term architecture in R1 timeframe

VFC/APPC FUNCTIONAL Architecture for R2+ Portal OPEN-O UI (GUI/CLI) Run-time Modeling (specs & Utilities) Integration Certification & Lab Security High Availability Dashboard OA&M (VID) External Data Movement & APIs Design-time A&AI Service Orchestration SDC UI Server VNF Design Service Design Interface Workflow Design Common Service DMaaP ESR Auth. Microservice Bus Policy Creation Resource Orchestration (using ETSI terminology – will refine label) Analytic Application Creation Interface DCAE Alarm Correlation (Holmes) Policy SDN-C APP-C gvnfm Other? Recipie/ Engineering Rules & Policy Distribution Catalog NFV-O NFV Collector (Monitor) Multi-VIM/MultiCloud VNF SDK Cloud & WAN OpenStack VMware RackSpace Azure ...... Consensus on layered architecture. This picture does not imply project structure.

Steps towards R2+ architecture SO and VFC meeting to identify R1 ‘baby steps’ (if any) Seshu took action item to set up meetings before we open R2 planning to address: Map projects into functional architecture Define interfaces between layers Map existing code into (1) and (2) (project-level discussion, not ARC committee)