view orchestration from model driven engineering prospective

View Orchestration from Model Driven

Engineering Prospective

Study Notes

CC 4.0 SA, NC 2

Intent• To understand orchestration;• What is orchestration? • What is the purpose of orchestration?• Why do I need it? Can I automate the orchestration?• Are there different types of orchestration? • Is there a general concept/design pattern I can follow?• …

using “Model Driven Engineering” as a tool to view orchestration.

• General guiding principle• To allow the learning continue to evolve.

20170126

CC 4.0 SA, NC 3

Outline• Resource-Event-Agent (REA)• Business Process

• TMN, Value Chain, and eTOM • BPMN

• Orchestration• Roles and responsibilities

• Use Cases• 1 - Deliver a pizza order• 2 - Deploy a telecom service to cloud

• Open Source• ETSI-MANO and NFV-IFO model• …

20170126

CC 4.0 SA, NC 4

What is model?Simpler version of the real thing.

There are many modeling tools for various domains, e.g.

F18 airplane in AMES wind tunnel, software development; …

UML is only one model language for software development.

20170126

CC 4.0 SA, NC 5

Why Modeling?• Not necessary

• Real Men Don't Eat Quiche;• Real Women Don't Pump Gas;• Real Kids Don't Say Please;• …• Real Architects Don't Write Code!!!

• Real Programmers Don't Model Software Design!!!

• Good thing to do• Communicate/sync among team members.• Design documentation and Code generation.• Reverse engineering.• Model transformation and Data mapping.• Manage complexity.• …

20170126

CC 4.0 SA, NC 6

Resource, Event, Agent (REA) ModelResources, Events, Agents (REA) • is a model of how an accounting

system can be re-engineered for the computer age.

• proposed in 1982 by William E. McCarthy as a generalized accounting model, and contained the concepts of resources, events and agents (McCarthy 1982).

• ISO 15944-4

20170126Ref: https://en.wikipedia.org/wiki/Resources,_events,_agents_(accounting_model)

CC 4.0 SA, NC 7

REA in a Nutshell• Agent has Custody of a Resource. • An Resource has economic value.• An economic exchange is an Event between Agents; which results an economic

Commitment.

• Commitment needs to be fulfilled by the responsible Agent to complete the economic exchange.

• A Process changes the Custody of a Resource or state of a Resource.• Service groups a set of Resources and deliver the utility to the Agent. Service Level

is established in the exchange. • Policy governs the behavior of economic exchange.

20170126

CC 4.0 SA, NC 8

UML Class Diagram for Extended REA (working in progress)

20170126

CC 4.0 SA, NC 9

Value Chain• A value chain is a set of activities that a

firm operating in a specific industry performs in order to deliver a valuable product or service for the market. The concept comes from business management and was first described and popularized by Michael Porter in his 1985 best-seller, Competitive Advantage: Creating and Sustaining Superior Performance.[1]

20170126Ref: https://en.wikipedia.org/wiki/Value_chain

CC 4.0 SA, NC 10

Business Process Model and Notation (BPMN2) • A standard Business Process Model and Notation (BPMN)• will provide businesses with the capability of understanding their internal

business procedures in a graphical notation and • will give organizations the ability to communicate these procedures in a standard

manner. Furthermore, • the graphical notation will facilitate the understanding of the performance

collaborations and business transactions between the organizations.

• Large ecosystem: BPMN design tools, executable platforms, flow simulation, code generation,…

20170126ref: http://www.bpmn.org/

CC 4.0 SA, NC 11

Simple BPMN Model for REA

20170126

CC 4.0 SA, NC 12

Use Case 1 – Deliver Ordered Pizza

20170126

Decide type of pizza to eat

Find pizza store

Like the pizza and its price, call & order it

Pizza StoreRegister

Accept order

Send order to kitchen

If there is no pre-made pizza, get dough

and other ingredientsUpdate menu

Receipt

Make pizza Deliver pizza

Payment bounced

Wrong size pizza

Eat pizza

Finished this order Or no one is happy

this exchange

Payment bounced

New pizza or refund,Different payment method

CC 4.0 SA, NC 13

Use Case 2 – Simple BPMN Model for Network Services

20170126

Decide the network service requirements

Find service provider

Order service

Service ProviderWeb Shipping Site

Accept order

Send order to production OSS

Assemble:- Create vm or container- Identify network links- Configure …- Fetch network apps

Update service menu

Receipt

Build service:- Load app- Link, - Test

Deliver network service

Payment bounced

Network is too slow

Use connectivity

Keep using the network Or service cancelled

Trouble shooting

CC 4.0 SA, NC 14

Telecommunication Management Network

20170126Ref: http://www.snmpcenter.com/what-is-the-tmn-model/

CC 4.0 SA, NC 15

Enhanced Telecom Operation Mapping (eTOM)

20yymmddRef: http://www.slideshare.net/cangkolen/e-tom6-8

CC 4.0 SA, NC 16

eTOM in Production

20yymmddRef: https://processarchitecture.files.wordpress.com/2014/03/030314_1558_staticanddy3.jpg

CC 4.0 SA, NC 17

Primary Mapping Between the Management Domain Concept and the eTOM

20yymmddRef: https://processarchitecture.wordpress.com/

CC 4.0 SA, NC 18

What is Orchestration? (my interpretation)

A system canDynamically select and deploy processes • To allocate and to assemble resources to fulfill service order, • To trigger quality assurance to meet desired SLA,• To provide billing information.

In telecom context:• It monitors the state of resources and logs the changes, can dynamically allocate and adjust the

network resources components to meet new requirements in real-time, provides feedback to BSS and self-aware and self-healing in OSS/NMS/NME/NEL layers.

Leverage:• BPMN2 Provides a standard notations, practices for design various processes, and TOSCA for

topology and automation. • MicroServices provides granular software components (eTOM) for reuse and flexibility.• VMs and containers provide execution environment.

20170126

CC 4.0 SA, NC 19

Challenges• Virtualization• Real-time, any time, anywhere.• Elastic.• Agility.• Dynamic and speed.

• Software Defined Everything (SDx)• New paradigms, control strategies.• Service mixing and complexity.

• Microservices• Flexibility and complexity. • Development management.

• Open Source and Open Platform• More software options.• Nature of competitiveness.

• Containers• New software design, and

development and deployment practice (CI/CD).

• Networking • IoT, M2M, eHealth, …• 5G, Mobile Edge Computing• Autonomous driving.

• …

20170126

CC 4.0 SA, NC 20

Open Source MANOs• ETSI-MANO

• Reference design (NFVO, VNFM, VIM, …)

• Open Source MANO (OSM)• ETSI OSM leverages OpenMANO for Resource

Orchestration (RO), and • Juju for VNF configuration and management (CM),• OSM also introduces a component for Service

Orchestration (SO), provided by Rift.io Riftware (NSO) which is beyond the ETSI NFV current scope.

• Open Baton • Open Baton is an open source project led by

Fraunhofer Focus and TU Berlin. It uses use message bus + driver. It is now being used by a few European projects and is available under GitHub and Apache 2.0 license.

• Open Baton is also based on ETSI NFV phase 1 reference architectural framework and MANO specifications. It is not aligned yet with the IFA interface specifications.

• Open-O • Linux Foundation (NFV-O + SDN-O)

• Cloudify, Project ARIA • GigaSpaces

• Tacker • OpenStack

• T-NOVA• EU project

• …

• Related:• Open Source TOSCA Orchestration.• OpenStack Heat.• Kubernetes, Fleet, Swarm.• …

20170126

CC 4.0 SA, NC 2120170126

MANO Architecture Framework

CC 4.0 SA, NC 22

MANO Basic Components

20170126

CC 4.0 SA, NC 23

Use MANO Architecture to FitPizza Ordering Example

20170126

CC 4.0 SA, NC 24

Use MANO Architecture Framework to Fit NFV-Orchestration

20170126

CC 4.0 SA, NC 25

MANO Components’ Roles and Functions

20170126Ref: http://www.telecomlighthouse.com/a-beginners-guide-to-nfv-management-orchestration-mano/

CC 4.0 SA, NC 26

MANO Reference Points

20170126

CC 4.0 SA, NC 27

Demo - ETSI-MANO Information Model (NFV-IFA)

20170126

CC 4.0 SA, NC 28

Thank You for ListeningRichard Kuo

20170126

CC 4.0 SA, NC 29

Supplement Information

20170126

CC 4.0 SA, NC 3020170126Out of date, reference only

CC 4.0 SA, NC 3120170126

CC 4.0 SA, NC 3220170126

CC 4.0 SA, NC 3320170126

NS, SLA, Billing

NS offers

ConfigurationLog, metering

Log, monitoring, user configurable data

Virtualization

Service composition & chaining

create execution environment

SLA/KPI, Billing

Load NS app

Service -> Service Components ->VNF Management ->Resource Components ->Resource Composition/Chaining (+FCAPS + policy) ->CI/CD

Manage VNF group

MANO Reference Architecture

CC 4.0 SA, NC 34

MANO Reference Points

20170126Ref: https://wiki.opnfv.org/display/mano/ETSI-MANO

CC 4.0 SA, NC 3520170126

CC 4.0 SA, NC 36

VNF Instantiation Flow

20yymmddRef: http://www.etsi.org/deliver/etsi_gs/NFV-MAN/001_099/001/01.01.01_60/gs_NFV-MAN001v010101p.pdf B3.1.2