Content Comparison

A&AI

Move to Active OS Graph Project (e.g.Janus)

Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.

A&AI

A&AI

Scalable, HA A&AI

Back end needs to be HA. Need to confirm, explore.

• Testing vs performance, throughput
• Scaling A&AI

Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.

A&AI

A&AI

A&AI Reconciliation from Network/Cloud.

• Need to refresh from VIM
• Different VIMs have different levels of detail.
• MSO has this UC also.
• Variety of different options here (SO, COntroller, VIM).

Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.

A&AI

A&AI

Extend Model-driven A&AI Usecases

Move forward the A&I model-driven story, driven initially by requirements of 3 release 1 use-cases

• For Resource, service and schema change.
• Includes definition of (model-driven) API
• Model evolution

Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.

If anything is out of scope, not it down

A&AI

A&AI

track Change through Time

Tracking the Service, Resource changes across time

• Support for point in time service/resource detail, e.g. for assurance

Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.

A&AI

SDN-C/APP-C/SDN-agent

APP-C

APP-C

DCAE

DCAE Closed Loop Using CLAMP

Realizing Open/Closed Loop using CLAMP

Realizing Open/Closed Loop using CLAMP

CLAMP

Common services

End to End flow decomposition across ONAP

Closed loop, Change management, orchestration, design time

CMO

Use Case VNFs

ONAP Deployment Management

Common serv1

Common services

ONAP platform OAM and a platform manager/controller

The ONAP Platform Manager/Controller will automate deploy/un-deploy of ONAP instance(s) and individual components, monitor its health and perform all platform lifecycle management functions.

embeds resiliency and such that can be used

CommServ 1

Common services

Common Controller Framework

Software framework that contains reusable code that can be used across multiple components. The code could be used in other components but would not be an end solution for use cases by itself and would not be deployed on its own

CommServ 2

SDN-C/APP-C/SDN-agent

Controller framework

A controller framework that is the platform infrastructure for the controllers

controller framework.

• functional evolution
• non functional
• testing

CommServ 2

DCAE

DCAE Release 1 Basic

Normalization   ECOMP/OPEN-O, .TOSCA   Alignment (Service Modeling), Role of   PNF in DCAE, Building   Catalogue, Micro-Services, VES, DCAE   Controller: Federation -  Edge/Central

DCAE

DCAE

DCAE Release 2 Project

Role of   Infrastructure Events (AIC, Other Cloud), Event   Trigger Scenarios Related to Life Cycle Management, Improve   DCAE/Controller Environment, Evolution, New User   Case Support, Improve   DCAE/Controller Environment, Evolution, Predictive   Analytics, Artificial   Intelligence/Machine Learning

DCAE

Common services

Messaging Bus

DMAAP

Extra

Documentation

Documentation

Common services

External API Integration

External API Integration so that external systems can do things like get called and be called. You have to have security considerations around this.

Ext API FW

Certification/ onboarding guidelines

Certification and VNF op with ONAP

Note: Use “validation”

ICE

Use Case VNFs

VNF Certification

Note: Use “validation”

ICE

Common services

Platform Level Testing

Platform Level Testing and characterization

Integration

Integration

System Integration and Testing

Responsible for ONAP cross-projects system integration and all related testing, such as VNF compliant & verification testing, necessary for the successful delivery and industry adaption of the ONAP project as a whole.   Provide integration tools and processes for CI/CD of source master and release branches.  Consolidation of common test suites.

• Provides all the cross-project infrastructure framework and DevOp toolchain, code and scripts, best practice guidance and benchmark, testing reports and white paper related to:•Cross projects Continuous System Integration Testing (CSIT)
• VNF compliant and verification testing leveraging ONAP projects
• Release delivering of the ONAP project
• PoC: building and maintenance community integration labs
• Continuous Distribution (CD) to ONAP community integration labs

Integration

SDN-C/APP-C/SDN-agent

Integration testing

Integration

Use Case VNFs

E2E tests

integration

Use Case VNFs

ONAP Platform Use Case Definitions

Integration

Common services

Common platform for modeling

Modelling

Modelling

Information and Data Modeling

Creation of Information models

• Creation of Data models

How do we split information and data models?

Infrastructure layer and service layer modeling

Northbound/Southbound API models

Modelling

Modelling

Declarative and Imperative Processing (BPMN - TOSCA interworking)

Workflow (BPMN) and TOSCA interworking

Modelling

Modelling

Tooling: Parser

Identify the tools needed for modeling

Tosca Parsers.

• YANG VNF Parsers.

Modelling

Modelling

Tooling: Model Translators

There are some translator tools which translate among tosca, YANG, HOT

Translator between Heat and Tosca

• Translator between Tosca and Yang for some subset

Modelling

Common services

Mircoservice Service Discovery, Load Balancer and Registry

MSPMSB

Multi med/multi-vim

Multi-VIM framework

Multi-VIM

Multi med/multi-vim

Multi-VIM Homing Locator

Multi-VIM

Multi med/multi-vim

Multi-VIM  plugin OpenStack

Multi-VIM  plugin for OpenStack

Multi-VIM

Multi med/multi-vim

Multi-VIM  plugin VMWare VIO

Multi-VIM  plugin for VMware VIO

Multi-VIM

SO

Multi-vim

Support for multiple VIMs

• Common interface for multiple VIMs
• testing

Multi-VIM

SDN-C/APP-C/SDN-agent

network controllers

Evolution of SDN-agent and transport controller

SDN-agent

• transport controller
• Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.
• testing.
• non functoinal, functional evolution

Network Controller

SDN-C

Use Case VNFs

ONAP Community Hardware Integration Lab

OpenLab

Policy

Infrastructure Policy

Policy aspects related to a VNF/service needs, e.g. for lifecycle management of VNF/service, e.g. scaling, placement, security, fault response, telemetry, SLA, ... including how policies are designed/packaged/onboarded.

Policy repository for storage and lifecycle management of policy

• Conflict Detection

Policy Framework

Policy

Policy Distribution

Ingestion and distribution to elements where policy will be applied.

Policy Decision Engines

• Policy Enforcement Points
• Policy repository

Policy Framework

Policy

Generic Policies

Platform-level policies, i.e. independent of specific VNF/service.

Where can they be expressed

Policy Framework

Policy

Policy Enforcement Point Onboarding

Ensuring elements that enforce policy conform to standards and are able to enforce policy

Required API's for enforcement

• Requirements and security surrounding enforcement points
• If anything is out of scope, not it down

Policy Framework

Portal/VID

ONAP Portal Enhancements

This provides the basis for the portal framework and onboarding of portal applications

Portal SDK

• User management
• Security / Authentication / Authorization
• UI Application Onboarding / Management

Portal

Portal/VID

Portal's new UI Applications

Separate applications provided by other projects as needed based on Portal SDK

Examples include VID, SDC

• GUI for vCPE, VoLTE
• Model driven user interface for vCPE , VoLTE use cases
• UI for ONAP Controller, change management

Portal

Portal/VID

ONAP CLI (ECOMP + OPEN-O merger scope)

CLI is used to allow command line access to ONAP functionality

Automation of portal functions

• No visual component
• Commands for orchestration of ONAP functionality
• Merger between Open-O and OpenECOMP

Portal

Use Case VNFs

Reference VNFs

RefVNF

SDC

Service Design and creation

Enhance the existing platform for ONAP release 1 Architecture

Integrate with  projects like Modeling, VNF SDK, VF-C

Convergence with OPEN-O and OpenEcomp

Service function chaining Design

Design deployment flavors (GeoR, HA).

SD&C

SDC

image management platform

Provide an image management platform, for multiple VIM, with multiple versions

Onboard image

Image distribution

Versioning

Quarantine area

SD&C

SDC

VNF onboarding Northbound API

API for onboarding VNFs and Service definitions onto SDC from external systems.

API for on-boarding and updating VNF into the SDC catalog

SD&C

Portal/VID

Service Design & Creation (SD&C)

Provide a platform for onboard a VNF, and design a service

Provide a platform for modeling a VNF, and a service

• Provide NBI for VNF & service design
• Provide an image management platform, for multiple VIM, with multiple versions
• Integrate with new projects like VNF SDK, workflow designer, and more
• Support different VNF deployment flavors

SDC

Common services

Optimizer Framework for resources used during vnf deployment

Optimizer Framework takes the low level work out of optimizing letting them focus on high level orchestration

SNIRO

SO

Service Orchestrator

Take and evolve the service orchestration module to support various controllers

Service orchestration

• interface to "multi-VIM"
• dependencies to SDC and modeling
• non-functional impacts
• support for YANG, Heat, TOSCA

SO

Extra

Training

Training

VF-C

VF-C

  NFVO/VNFM.

• Interfaces.
• Testing
• documentation (alignment)

Virtual Function Controller

Use Case VNFs

VNF SDK

Note: Use “validation”

VNF SDK

VNF/SDK guidelines

VNF Guidelines & SDK

VNF SDK

Use Case VNFs

VNF Guidelines

Note: Use “validation”

VNF-SDK