34
OPEN-O Common-TOSCA Project Proposal Version 0.9 Draft – For Review Arthur Berezin

OPEN-O Common-TOSCA

Embed Size (px)

Citation preview

Page 1: OPEN-O Common-TOSCA

OPEN-O Common-TOSCA

Project Proposal

Version 0.9

Draft – For Review

Arthur Berezin

Page 2: OPEN-O Common-TOSCA

Overview⬜ Project Name “Common-TOSCA”

⬜ Repository name [‘common-tosca’]

⬜ Project Description:

Common-TOSCA provides frameworks and services for GS-O, NFV-O

and SDN-O to support “TOSCA Simple Profile for NFV” orchestration of VNFs, NSs and NFCs. Including services for modeling, storing, onboarding, installation and interaction with VNFs, NS, and SFCs.

⬜ Participants: GigaSpaces, ZTE, Huawei, China Mobile, Others ?

Page 3: OPEN-O Common-TOSCA

Project Description

⬜ Release 1 includes several sub projects:◼ Architecture is micro-services style.◼ RESTful APIs between components.

◼ TOSCA Framework for on-boarding and orchestration of TOSCA

Simple Profile descriptors consumed by GS-O and NFV-O.

◼ Catalog and Inventory for VNFs, Network Services(NS) descriptors,

images, and all related resources needed by GS-O, NFV-O (and possibly by SDN-O in future releases).

◼ Graphical Modeling Designer for creation of TOSCA descriptors

Page 4: OPEN-O Common-TOSCA

4

Orchestrator ServiceCommonTOSCA

OPEN-O Architecture Overview (until now)

Driver VNFM Drivers

VIM Drivers

ACCESS/WAN SDN Controller Drivers

NFV SDN Controller Drivers

Common Service

Micro-ServiceBus

Auth.

Log Driver Mgr.

Workflow

Catalog

SDN-O

SDN Res.Mgr.

Abstract NBI

Abstract SBI

NFV-O

NFV Res. Mgr.

NFV Monitor

Model Designer

NS Lifecycle Mgr.

Abstract NBI

Abstract SBI

Portal GUI Portal …TOOLs

Foreman

AnsibleGS-O

Service Decomposer

Service Lifecycle Mgr.

ServiceFormation

Abstract NBI

VPN

SDN Lifecycle Mgr.

Traffic Optimize

VAS Mgr.

SDNMonitor

Lifecycle Mgr.Framework

Template Mgr.

Model DrivenFramework

Policy DrivenFramework

CommonRes. Mgr

Compass

Controller Mgr.

Protocol Stack

HA

EMS/NMS Drivers

Driver

Page 5: OPEN-O Common-TOSCA

5

Common (TOSCA)

Common Service

Micro-ServiceBus

Auth.

Log

TOSCA Workflow

Catalog

SDN-O

SDN Res.Mgr.

Abstract NBI

Abstract SBI

NFV-O

NFV Res. Mgr.

NFV MonitorModel Designer

NS Lifecycle Mgr.

Abstract NBI

Abstract SBI

GUI Portal

TOOLs

Foreman

Ansible

GS-O

Service Decomposer

Service Lifecycle Mgr.

Abstract NBI

VPN

SDN Lifecycle Mgr.

Traffic Optimize

SDNMonitor

Runtime engine

TOSCA Parser

Compass

Protocol Stack

HA

Driver ACCESS/WAN SDN Controller Drivers

EMS/NMS Drivers

DriverVNFM Drivers

VIM Drivers

NFV SDN Controller Drivers

GUI Portal

GUI Portal

Service layer

Inventory

Common-TOSCA Architecture Release 1

Page 7: OPEN-O Common-TOSCA

Modules for Release 1

◼ TOSCA Parser and Validator

◼ Workflow Execution Engine◼ Model Designer ◼ Catalog◼ Inventory

Page 8: OPEN-O Common-TOSCA

TOSCA Parser and Validator

Problem being solved

◼ Common-TOSCA provides Parser for TOSCA Validation

services for the major Open-O orchestrations components

GS-O, NFV-O and SDN-O

◼ TOSCA is object oriented modeling language:

▫ Normative, Extendable, Abstractable, and Composable

▫ TOSCA natively allows modeling and integrating nested

models like YANG.

Page 9: OPEN-O Common-TOSCA

TOSCA Parser and Validator

Project Scope :

◼ TOSCA YAML CSAR Parser and validation of TOSCA CSAR

YAML Templates.

◼ RESTful API Endpoint Microservice for CSAR validation.

◼ TOSCA extensions framework for extension of base node

types and creation of SBI Drivers/Plugins to support

gNFVM, sNFVM, and VIM.

Page 10: OPEN-O Common-TOSCA

Common-TOSCA Internal Architecture Release 1

TOSCA Orchestration Libraries

DSL Parser Workflow Engine

Built-in (Optional)WorkflowsInstall, Uninstall

WorkflowMechanism Python WorkflowsWith Graph Context

Drivers/Plugins are Subject To Implementationby GS-O, NFV-O

TOSCAYAML DSL

REST API Framework (REST API Services in GS-O/NFV-O/SDN-O?)

CSARVNF/NS

DescriptorOptionally:

Images, Scripts,

Workflows, etc’

ARIA Plugins Engine

TOSCA SBIVal

idat

ion

Exe

cutio

n

Page 11: OPEN-O Common-TOSCA

Workflow Execution

GS-OBrendan Hassett

Workflows

RESTful API (NBI)

SDN-OOlga Havel

NFV-OLingli Deng

NFV-O DriverSDN-O Driver

Catalog

Inventory

LifecycleManager

ARIA TOSCA Workflows

RESTful API (NBI)RESTful API (NBI)

NBI

NS LifecycleManager

SBI

Designer

Common-TOSCA Architecture Alignment Release 1

....

..

DriverDriver

ARIA ParserAPI

DecomposeAPI

ARIA ParserAPI

HuaweisVNFM

RESTful API

ZTEsVNFM

JujugVNFM

WSO2/BPEL

RESTFul APIInventory

Page 12: OPEN-O Common-TOSCA

Gaps and Roadmap

⬜ Release 1:◼ CSAR Support (currently standard archive file)◼ Framework for RESTful TOSCA Services

▫ In collaboration with GS-O and NFV-O◼ Work with GS-O and NFV-O to support framework

consumption and interaction with REST API and SBI

⬜ Stretch: ◼ The TOSCA SPEC is a moving target:

▫ Align to latest TOSCA Simple Profile▫ Align to latest TOSCA Simple Profile for NFV

Page 13: OPEN-O Common-TOSCA

Modules for Release 1

◼ TOSCA Parser and validator

◼ Workflow Execution Engine ◼ Model Designer ◼ Catalog◼ Inventory ◼

Page 14: OPEN-O Common-TOSCA

Workflow Execution Engine

⬜ Problem Being Solved:

◼ It is needed to describe the flow of the automation by determining which task, operation, action, or arbitrary code will be executed and when depending on the orchestration graph.

◼ Orchestrators needs the ability to execute onboarding workflows in order to register and initiate Network Services or VNFs

◼ After onboarding process the orchestrator needs the ability to interact with running NSs and VNFs.

Page 15: OPEN-O Common-TOSCA

Workflow Execution Engine

⬜ Project Scope:

◼ A framework with dedicated API for creating context aware workflows

◼ Workflows are automated process algorithms.

◼ Execute onboarding workflows based on topology

graph(Install, Uninstall)

◼ Context is passed between nodes on workflow execution

Page 16: OPEN-O Common-TOSCA

Workflow Execution Engine

⬜ Project Scope:

◼ Workflows are written in Python

◼ Workflows describe the flow of the automation by determining which task, operation, action, or arbitrary code will be executed and when depending on the orchestration graph.

Page 17: OPEN-O Common-TOSCA

Modules for Release 1

◼ TOSCA Parser and Validator

◼ Workflow Execution Engine ◼ Model Designer ◼ Catalog◼ Inventory ◼

Page 18: OPEN-O Common-TOSCA

Problem being Solved

⬜ The Model Designer is a Web-based GUI environment to

design service templates and plans for lifecycle management of

the services.

Page 19: OPEN-O Common-TOSCA

Model Designer Scope

⬜ Create service template◼ NS/VL/VNF◼ SFC(VNFFG)

⬜ Create Plan(lcm workflow)⬜ Support layered/nested Service template-to be discussed

◼ A (nested) NS can be referenced in other NS ◼ A abstract NS model expose standard capabilities to high layer, and the

implementation can be any vendors

⬜ Import CSAR package into designer⬜ Export template as CSAR package⬜ Deploy template to Catalog

Page 20: OPEN-O Common-TOSCA

Layered and Nested NS ModelNS1

VNF1 NS 2

NS2 is referenced by NS1 as a nested NS.The Nested Ns in the example can also be a nested VNF

VNF2

NS2

VNF3 VNF4 VNF5

reference

NS1

VNF1 VNF2 VNF3

VNF2(Abstract Type)

reference

VNF2 (Vendor1) VNF2(Vendor1) VNF2(…..)

Could VNF2 be an abstract type and have multiple implementation by different vendors? –need to work with modeling project/architecture committee

Choose appreciate concrete VNF according to policy(location, availability , cost, latency, etc.) when deployment

Page 21: OPEN-O Common-TOSCA

Model Designer Architecture

Page 22: OPEN-O Common-TOSCA

External Interface of Model Designer

Model Designer

Catalog Common Parser

②rest①rest

Interface Description:⬜ ① Save CSAR Package to Catalog⬜ ② Parser Tosca YAML File

Page 23: OPEN-O Common-TOSCA

Modules for Release 1

◼ TOSCA Parser and Validator

◼ Workflow Engine ◼ Model Designer ◼ Catalog◼ Inventory ◼

Page 24: OPEN-O Common-TOSCA

Problem being Solved⬜ The Catalog includes NFV Service Catalog and VNF Catalog.

⬜ The NFV Service Catalog is the repository of all of the on-boarded Network Services, supporting the management of the NS deployment templates (NSD, VLD, and VNFFGD).

⬜ The VNF Catalog is the repository of all of the on-boarded VNF Packages, supporting the management of the VNF deployment templates (VNFD and Artifacts). Both NFVO and VNFM can query the VNF Catalog for finding and retrieving a VNFD, to support different operations (e.g. validation, checking instantiation feasibility).

⬜ The Catalog also provide artifacts download function.

Page 25: OPEN-O Common-TOSCA

Catalog Scope

⬜ CSAR upload, download, delete, query, status management.

⬜ Provide REST API interface to query information model.

⬜ Provide artifacts download(software pkg. , image, scripts, policy, plan, etc.).

Page 26: OPEN-O Common-TOSCA

Catalog Architecture

Process Model

TOSCA XML Parser

TOSCA YAML Parser

ETSI-NFVYANG Parser

TOSCA-NFV YAML Parser

TOSCA/ETSIModel Catalog

APIs

File Catalog

APIs

NFV Service Package VNF Package

Common Parser

APIs

APIs

Process Files

Package Download URL Image URL

Package

Process Plan

Parser

Upload

Http Server

Database

StorageStorage

Support

NFV Service Descriptor Restful Interface

VNF Descriptor Restful Interface

Support

Page 27: OPEN-O Common-TOSCA

External Interfaces of Catalog

Catalog

Model Designer

Common Parser

GS-O/SDN-O/NFV-O

1

4

2

REST API

Common Service3

Page 28: OPEN-O Common-TOSCA

Interfaces Description

⬜ 1 Deploy CSAR package.

⬜ 2 Parse information model.

⬜ 3 Service registration, Auth, logs.

⬜ 4 Query NFV descriptor or download artifacts(scripts, plan, policy, etc).

Page 29: OPEN-O Common-TOSCA

Upload CSAR Sequence Diagram

Page 30: OPEN-O Common-TOSCA

Onboarding Sequence Diagram

Page 31: OPEN-O Common-TOSCA

Tosca/ETSI Model

Page 32: OPEN-O Common-TOSCA

Modules for Release 1

◼ TOSCA Parser and Execution Engine

◼ Workflow Engine ◼ Model Designer ◼ Catalog◼ Inventory ◼

Page 33: OPEN-O Common-TOSCA

Problem being Solved

⬜ The requirement of centralized management and maintenance

resources, services and their relationships.

⬜ Provide a global resource view for GS-O, NFV-O, SDN-O.

⬜ Dynamic extension resource properties

Page 34: OPEN-O Common-TOSCA

Inventory Scope

⬜ Provide resources centralized storage function

⬜ Support schemaless data stores for easily model evolution

⬜ Provide CURD(create, update, read, delete) REST interface for GS-O/SDN-O/NFV-O to manage the resource instance. Like NS,

VNF, VL, VDU etc.

⬜ Maintain the relationship of resource instance

⬜ Support subscription the resources change notification