© ETSI 2017

TSC PerspectivesZERO TOUCH AUTOMATION CONGRESS - Madrid

March 26, 2019

Vanessa Little (VMware)OSM TSC Chair

© ETSI 2017

<image here>

2

Introduction to OSM

© ETSI 2017

OSM provides a production-quality MANO stack…

• Capable of consuming openly published IM/DM

• Available for everyone, to minimize uncertainties

• Suitable for all VNFs, capturing real production complexity

• Operationally significant: including Service Orchestration too!

• VIM-independent

ALIGNED TO NFV ISG INFORMATION MODELS

• … but capable of providing prompt and constructive feedback whenever needed

ENABLING AN ECO-SYSTEM OF IM-COMPLIANT VNF VENDORS

• Ready to be offered to cloud and service providers

• No need of integration per- customer & MANO vendor basis

3

© ETSI 2017

OSM Architectural Principles

4

Layering Abstraction

Modularity Simplicity

Architectural Principles

© ETSI 2017

The Open Source MANO Project

5

Open Source MANO is an ETSI-hosted project to develop an Open Source NFV Management and Orchestration (MANO) software stack aligned with ETSI NFV.

© ETSI 2017

Layered Model

A multilayered model, where each layer provides a “service object”, composed by service objects provided by lower layers.

6

© ETSI 2017

OSM’s approach aims to minimize integration efforts

1. A well-known Information Model (IM), aligned with ETSI NFV, that is capable of modelling and automating the full lifecycle of Network Functions:• VNFD (VNF Descriptor),

VNFR (VNF Record), • NSD (Network Service Descriptor),

NSR (Network Service Record), • NST (Network Slice Template),

NSI (Network Slice Instance)

7

© ETSI 2017

OSM’s approach aims to minimize integration efforts

2. A unified northbound interface (NBI), based on NFV SOL005

8

© ETSI 2017

OSM’s approach aims to minimize integration efforts

3. The extended concept of “Network Service” in OSM, so that an NS can span across the different domains identified and therefore control the full lifecycle of an NS interacting with VNFs, PNFs and HNFs.

9

© ETSI 2017

Service Platform view

10

OSM as a Network Service Orchestrator (NSO)

© ETSI 2017

Service Platform view

11

VIM manages the virtual network to support VNF’s connectivity

In advanced cases, the VIM might (transparently) control al external SDN Controller, to fulfill the connectivity requirements

© ETSI 2017

Integration with SDN Controller

12

SDN AssistAllows OSM to control SDN connectivity, even when not possible by the VIM (eg: PCI

Passthrough, SR-IOV)

© ETSI 2017

OSM Release FIVE, reaching PRODUCTION READINESS…

Release FIVE

(Dec 2018)

© ETSI 2017

OSM Release 5

...and launched Release FIVE in December 2018, with key features for 5G and production environments!

14

The most ambitious release so far!

• Support for hybrid Network Services! VNFs and PNFs

• Network Slicing for 5G

• Multi-site Inter-DC extensions

• Monitoring & Policy improvements (VNF + VIM metrics, autoscaling)

• Improved modelling of VNF networking (SFC, multi-VDU relations)

• Better user experience (GUI package composer, faster installation, events/logs GUI)

Release FIVE

© ETSI 2017 15

Release 5 Deep Dive and Components

© ETSI 2017

Release FIVE Highlights

16

NETWORK SLICING FOR 5G

• Integrated Slice Manager

• IM extended to support NST and NSI

MULTI-SITE EXTENSIONS

• Dynamic inter-DC connections

• WIM plugin model

• Multi-VIM Enhancements

MONITORING IMPROVEMENTS

• Extended interop capabilities

• Policy support

• VNF + VIM Metrics Collection

Release FIVEAvailable at: osm.etsi.org

USER EXPERIENCE & OPTIMIZATION

• GUI based NS composer

• Faster startup and responsiveness

• Better event and log visualization

• Docker, Vagrant and VM image install

IMPROVED MODELLING & NETWORKING

• Service Function Chaining (SFC)

• Physical Deployment Units

• Multi-VDU relations in VNF

© ETSI 2017

Release FIVE+ architectural view

Object Storage

TSDB(Metrics)

Kafka bus

Common Services

ROVCA

OSM IM

OSM IM

CommonDatabase(NoSQL)

OSM IM

NBIOSM IM

osmclient

SOL 005 compliant

MON

LCM

light-ui / composer

N2VC

POL

Integrated components for policy, fault and performance management

Lightweight Life Cycle Manager (LCM)

Unified Northbound Interface (SOL005-based), decoupled from LCM

Complete control through CLI and stand-alone new UI

Common DB, time-series DB and object storage

5

3

2

1

OSM IM Message bus for async communications

4

6

© ETSI 2017

Release FIVE+ architecture

Microservice architecture to enable extensibility

18

© ETSI 2017

A single OSM NS/Slice can now span across different VIM+NFVI, Transports, and Physical Functions…

E2E Service Orchestration

OSS/BSS

ETSI SOL005 + NS LCM calls

VIRTUAL DOMAINTRANSPORT

DOMAIN

PNFs

&

HNFs

Or-ViT-SDN (TAPI, MEF-Legato…)

IM integrated

RelFOUR

RelFIVE Rel

FIVE

© ETSI 2017

… with a unique and non-ambiguous IM, independent of the technologies southbound…

NFVI VIM

NS#1VNF 1

VNF 2

VNF 3

VIM’s NBI

VCACharms

ROVIM/SDN Connectors

LCM

OSM’s NBI

MgmtProcedures

Resource Description

VNF Packages

MgmtProcedures

Topology

NS Package

Deployment

INFORMATION MODEL

© ETSI 2017

SFC Status in OSM

● Available since OSM Release 3● SFC only available using:

Openstack Queens (or higher) with Networking-SFC● Only supports Asymmetrical Chains● SFC Encapsulation using Network Service Headers (NSH)

VNF #1 VNF #2 VNF #3

© ETSI 2017

OPNFV XCI Integration

22

• OPNFV has integrated OSM installation into their pipeline.

https://wiki.opnfv.org/display/sfc/OSM+guide• The first advanced use case

they want to implement is Service Function Chaining (previously done with Tacker)

→ Basic SFC has been integrated as of 31/Oct/2018

• Next step is to evolve OSM SFC features to achieve more use cases.

© ETSI 2017

Separate ingress and egress ports

Modifying the Information Model and Resource Orchestrator

23

VNF VNF

Status: Complete.

© ETSI 2017

Symmetrical/Asymmetrical Chains

Currently only Asymmetrical Chains are supported.Status: In development.

24

VNF #1 VNF #2 VNF #3

© ETSI 2017

Non-Transparent Service Functions

25

VNF# 1(SFC Aware)

VNF #2(SFC Unaware)

SFC Proxy

Currently not supported.Status: Future Release

© ETSI 2017

Branching and Joining

26

VNF #1 VNF #2 VNF #3

VNF #4

Currently not supported.Status: Future Release

© ETSI 2017

Service Function Tap

27

VNF #1 VNF #2 VNF #3

VNF #4(ex. IDS)

Currently not supported. Status: Future Release

© ETSI 2017

SFC Management API

28

«The current service function deployment models are relativelystatic, coupled to network topology and physical resources,greatly reducing or eliminating the ability of an operator tointroduce new services or dynamically create service functionchains.»

IETF - RFC 7665 - Service Function Chaining (SFC) Architecture

© ETSI 2017

SFC Management API

29

© ETSI 2017

Network Slicing Overview

30

• Different network slices addressing different types of usage requiring different levels of functionality, performance and reliability.

• For each type of usage there can be different:• The radio access technologies (RAT)

• The list of activated core network features in the control plane and the user plane

• Resource dimensioning and the location where they are deployed

eMBB

MIoT

URLLC

Source: NGMN

© ETSI 2017

ETSI NFV Framework for Network Slicing

31

Analysis of 3GPP and alignment of NFV architecture with itETSI GR NFV-EVE 012

Considerations:- Network Slice Subnet can be

considered as an NFV Network Service.

- Network Functions can be described as VNF and PNF.

3GPP ETSI NFV

© ETSI 2017

Network Slicing in OSM

32

• Major development under 5G• Two key attributes• Composition of NSs

• ‘Normal’ NS in NS• Sharing of a single NS instance

between slices• Quite different to normal NS in NS

and is not normal containmentrelationship

• Dynamic behaviour in NSs and networkslices• An instance can easily evolve well

away from its original creationtemplate

3GPPP ETSI

© ETSI 2017

Network slicing in OSM

• Network slice instance: a set of network functions and the resources for these network functions which are arranged and configured, forming a complete logical network to meet certain network characteristics.

• The NSI contains:• NFs (e.g. belonging to AN and CN)

• Information relevant to the interconnections between these NFs like topology of connections

• Individual link requirements (e.g. QOS attributes),

• The NSI is defined by a Network Slice Template.

33

PreparationInstantiation, Configuration, and

Activation

Pre-provision

Network environment

preparation

Instantiation/

ConfigurationActivation

Run-time Decommisioning

Termination

Lifecycle of a Network Slice Instance

De-

activation

Supervision

Reporting

Upgrade/

Reconfiguration/

Scaling

Design

© ETSI 2017

NST diagram

34

© ETSI 2017

Network Slicing Assumptions in OSM

35

• Slice subnet (NSS) is supported by a NS (shared or not)• Reference to NSD

• Network Functions can be virtual or physical (we do not care)

• Include 5QI as constraint

• There are 2 new types of IM resource for supporting slices: • NST (Network Slice Template)

• NSI (Network Slice Instance)

• NST will have connection points, in a similar way as Network Service external connection points.

• NSS can be interconnected with virtual links which are described in a NSSFG• netslice-vld: information at NST to declare how we plan to interconnect their NSS

• netslicefgd: includes list of Rendered Service Paths and list of classifier rules.

© ETSI 2017

OSM Components Impacted

36

Introducing an API to:● Manage Rendered Service Paths (RSPs)● Manage Flow Classifiers

Main problems:● Loop detection and avoidance● Scaling operations

Status: In development.

Aligned with SOL005

© ETSI 2017

6th OSM Hackfest – Santa Clara (CA, USA)

Hosted by

13th to 17th May 2019

Co-located with OSM#7

Registration is OPEN:

OSM-Hackfest#06 Santa Clara

First Ever OSM VNF DAY!