Embed Size (px)
Citation preview
© ETSI 2019
8th OSM Hackfest
© ETSI 2019
Hackfest Week Plan
2
Slides
© ETSI 2019
Agenda
• Quick overview of NFV
• Introduction to the latest OSM Release
4
© ETSI 2019
<image here>
5
Quick review of NFV
© ETSI 2019
What is NFV trying to address?
•Network Function Virtualization (NFV) proposes to virtualize network functions that typically run in dedicated appliances
•The main goal is to support virtualized functions over COTS servers.
•Virtual Network Functions (VNFs) acquire all the advantages of Cloud Applications!
6
CLOUD
© ETSI 2019
The original idea…. triggered an industry movement
• Initial white paper was written in 2012 by the world's leading telecom network operators (Europe, América & Asia).
• This group evolved to the ETSI NFV ISG (Industry Specification Group), formed by 300+ companies.
• Their main motivation had to do with reducing TCO of building a network by using open solutions.
7https://portal.etsi.org/nfv/nfv_white_paper.pdf
© ETSI 2019
ETSI Publications
• Based on member’s feedback, field experiences and proof of concepts, standard documents have evolved.
• 60+ publications exist today, including the following three main documents:
• NFV Architectural Framework http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_NFV002v010201p.pdf
• NFV Infrastructure Overview http://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/gs_NFV-INF001v010101p.pdf
• NFV Management and Orchestration http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_NFV002v010201p.pdf
8
http://www.etsi.org/standards-search
© ETSI 2019
Benefits of a standard NFV architecture
We are looking for a unified and generic virtualization infrastructure, compatible with any vendor’s Virtual Networking Function (VNF), so standardization is a must.
9
Hardware Infrastructure for Virtualization + Managera.k.a “Telco Cloud”
Management /Orchestrationvnf
em
vnf
em
vnf
em
Vendor #1
vnf
em
vnf
em
vnf
em
vnf
em
vnf
em
vnf
em
Vendor #2 Vendor #3
CommonOperator’sInfrastructure
© ETSI 2019
The ETSI NFV Architectural Framework
The standard architecture can be better understood in three blocks:
10
MANOManagement & Orchestration
(focus on VNF/NS lifecycle)
NFVI NFV Infrastructure
VNFsVirtual Network Functions
VIMOfficially part of MANO, but usually bundled with NFVI
(focus on VM lifecycle)
© ETSI 2019
NFVI: NFV Infrastructure
NFVI goal is to provide a virtualization environment for VNFs, including virtual compute, storage and networking resources.
11
•But!
Networking applications may have more strict performance requirements, we will discuss that later.
© ETSI 2019
NFVI: NFV Infrastructure
VNF Special Requirements
VNFs, especially data-plane ones, usually have additional requirements than common cloud applications, including:
•Minor latency (disk I/O & network) → Faster hardware (More cores, SSD disks, faster buses)→ Dataplane acceleration
•Higher throughput or PPS → Dataplane acceleration→ EPA: Enhanced Platform Awareness
•Geographical distribution→ multi-site cloud
•Horizontal auto-scaling → automated operations (orchestration)
12
© ETSI 2019
NFVI: NFV Infrastructure
VNF Special Requirements
EPA covers the different approaches that can be taken at the NFVI layer to increase performance while maintaining a generic (COTS) infrastructure. VIM and MANO should be able to request them.
13
Huge Pages NUMA Topology Awareness
Data Plane assignmentCPU Pinning
© ETSI 2019
VIM:Virtualised Infrastructure Manager
•The Virtualised Infrastructure Manager is part of the ‘MANO Stack’ and provides lifecycle management for virtualized resources (VMs, volumes, networking paths and connectivity, etc.)
14
© ETSI 2019
VNFM:VNF Manager
•The VNF Manager, also part of the ‘MANO Stack’, covers lifecycle management for Virtual Network Functions (VNFs), either directly or through their own Element Management System (EMS).
• VNF Managers can be generic (current trend), or vendor-specific ones.
15
© ETSI 2019
MANO: NFV Orchestrator (NFVO)
•The NFV Orchestrator, the higher entity in the ‘MANO Stack’, covers general resource orchestration and services lifecycle, which comprise multiple VNFs and define their roles (traffic paths, scaling decisions, and other service-related requirements)
• It can interact with a generic VNF Manager, or vendor-specific ones.
16
LCM & RO
© ETSI 2019
Virtual Network Functions (VNF)
•Finally, the VNFs, which are supported by the underlying NFVI, and managed by their own EM (internal, element manager) and the VNF Manager (external, ‘context-aware’ manager)
•They should be able to provide any networking function and interact with other VNFs.
17
© ETSI 2019
VNF Descriptor files (VNFD)
One of the most important aspects of achieving a unified VNF catalogue, is having a standard way of describing VNFs.
18
•MANO solutions should give the possibility to describe VNFs through ‘descriptor files’
•The industry’s goal is a unified and standard descriptor file format across different platforms.
•Both NS (comprised of VNFs) and VNFs should be described in a simple way.
© ETSI 2019
Multi-vendor NFV Showcase
With the support of leading NFV-enablers, putting together a number of leading VNF vendors, on top of commoditized x86 infrastructure, managed by OpenStack and Open Source MANO.
Goal: to demonstrate publicly that multi-vendor networks are possible
19
whitecloud
Security
whitenfv
Intel Servers Featuring Scalable Processors, 10/25G NICs, SSD, QAT
Whitebox Switches High-performance Broadcom chipset (10 / 40 / 100G)
Performance
DRAEPC
© ETSI 2019
Multi-vendor NFV Showcase
• ng4t VRAN: Emulates the vRAN• OpenAir Interface: Implement the vEPC (MME, SGW, PGW)• Fortinet: implement security• Mobileum: implement DRA and NTR (Roaming Steering)
© ETSI 2019
Multi-vendor NFV Showcase
Day-0, Day-1 and Day-2
Day 0:Instantiate
Isolated VNFs
Day 1:Build Service(automated)
Evolved Packet Core
Day 2:Operate(on demand)
Evolved Packet Core
© ETSI 2019
Multi-vendor NFV Showcase
22
The final results, including configurations used for
deploying this vEPC, are published, following the
guidelines from ETSI Plugtests Programme.
https://www.whitestack.com/posts/results-multivendor-nfv-showcase/
© ETSI 2019
<image here>
23
Introduction to OSM Release SIX
© ETSI 2019
The NFV MANO Landscape
•Given that the VIM is already well covered by OpenStack distributions and proprietary
solutions (e.g. vCD), in practice, the “NFV MANO” part focuses on the VNF Manager and NFV Orchestrator.
•Among the most popular open source platforms for NFV MANO, we have:
24
tacker
© ETSI 2019
The Open Source MANO Project
25
We are here!Open Source MANO is an ETSI-hosted project developing an Open Source NFV Management and Orchestration (MANO) software stack aligned with ETSI NFV.
© ETSI 2019
OSM Architectural Principles
26
Layering Abstraction
Modularity Simplicity
Architectural Principles
© ETSI 2019
Layered Model
A multilayered model, where each layer provides a “service object”, composed by service objects provided by lower layers.
27
© ETSI 2019
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)
28
© ETSI 2019
OSM’s approach aims to minimize integration efforts
2. A unified northbound interface (NBI), based on NFV SOL005
29
© ETSI 2019
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.
30
© ETSI 2019
OSM’s approach aims to minimize integration efforts
4. In addition, OSM can also manage the lifecycle of Network Slices, assuming if required the role of Slice Manager, or integrating with an external Slice Manager
31
Full E2E Management (Integrated Modelling)
Standalone Management (Vanilla NFV/3GPP)
© ETSI 2019
Service Platform view
32
OSM as a Network Service Orchestrator (NSO)
© ETSI 2019
Service Platform view
33
VIM manages the virtual network to support VNF’s connectivity
In advanced cases, the VIM might (transparently) control al external SDN Controller, to fulfil the connectivity requirements
© ETSI 2019
Integration with SDN Controller
34
SDN AssistAllows OSM to control SDN
connectivity, even when not possible by the VIM (eg: PCI Passthrough,
SR-IOV)
© ETSI 2019
Release FOUR+ architectural view
Kafka bus
TSDB(Metrics)
Auth
Object Storage
Common Services
ROVCA
OSM IM
OSM IM
CommonDatabase(NoSQL)
OSM IM
NBIOSM IM
osmclient
OSM’s NBI
MON
LCM
light-ui
N2VC
POLIntegrated components for policy, fault and performance management(auto-scaling, monitoring, etc)
Complete orchestrator: LifeCycle Management (LCM) component
Unified Northbound Interface
Complete control through CLI and stand-alone new UI
unified message bus for async communications
common DB, storage, authentication and TSDB systems 1
2
4
5
6
7
N2VC-VCA Juju controller for VNF configuration & indicator management
3
35
new
new
© ETSI 2019
Release FOUR+ architecture
Microservice architecture to enable extensibility
36
© ETSI 2019
Why is OSM Awesome?
It has a rich and open information model
• Agnostic to VIM, SDN platform, VNF and OSS connectors/specifics.
• It allows for a uniform NFV orchestration, abstracted from the environment
• Aligned with ETSI-NFV Information Model
37
Visit:https://osm.etsi.org/wikipub/index.php/OSM_Information_Model
© ETSI 2019
Why is OSM Awesome?
It has a large and diverse community! More than members!
38(*) Names & brands may be claimed as the property of others
• 12 Global Service Providers• Leading IT/Cloud players • VNF providers
130
© ETSI 2019
Why is OSM Awesome?
It is well organized for producing production-ready upstream code
39
MARCOM TASK FORCE
VNF ONBOARDING TASK FORCE
© ETSI 2019
Why is OSM Awesome?
It is well organized for producing production-ready upstream code
40
MARCOM TASK FORCE
VNF ONBOARDING TASK FORCE
LEADERSHIP GROUP
Francisco Javier Ramón Andy Reid Pål Grønsund
© ETSI 2019
Why is OSM Awesome?
It is well organized for producing production-ready upstream code
41
MARCOM TASK FORCE
VNF ONBOARDING TASK FORCETECHNICAL STEERING COMMITTEE
Vanessa Little José Miguel GuzmánGerardo García Mark Shuttleworth Felipe Vicens
© ETSI 2019
Why is OSM Awesome?
It is well organized for producing production-ready upstream code
42
MARCOM TASK FORCE
VNF ONBOARDING TASK FORCE
END USER ADVISORY GROUP
Andy Reid
VNF ONBOARDING TASKFORCE
MARCOM TASKFORCE
Mona Hrapkowicz
Gianpietro Lavado
© ETSI 2019
Why is OSM Awesome?
It is well organized for producing production-ready upstream code
43
MARCOM TASK FORCE
VNF ONBOARDING TASK FORCE
DEVOPS MDL
Jayant Madhavi
RO MDL
Alfonso Tierno
SA MDL
Gianpietro Lavado (interim)
N2VC MDL
Adam Israel
UI TFL
Francesco Lombardo
ETSI TE
Silvia Almagia
© ETSI 2019
Why is OSM Awesome?
It prioritizes features for production readiness...
Multi-VIMOpenStack, AWS, VMWare
Multi-SDNODL, ONOS, Floodlight
One-click installer
Network Service Scaling
Multi-Site, and more!
Multi-tenancy & RBAC
Monitoring Module
Enhanced VIM support & emulation
NB API Consolidation
Affinity/Anti-Affinity Rules
MAY 2016
OCT 2016
APRIL 2017 OCTOBER 2017
CI/CD Workflow
Information Model Consolidation
44
Model-driven NBI
Monitoring Improvements
Cloud-native deployment
Improved modeling
Service Chaining
MAY2018
Native Charms
Enhanced usability
Network Slicing
Monitoring Improvements
Multi-site Extensions
Improved modeling
Hybrid Network Services
Auto-Scaling
Enhanced usability
DECEMBER 2018
© ETSI 2019
Why is OSM Awesome?
...and launched Release SIX in June 2019, with more key features for 5G and production environments!
45
• Role-based authentication control (RBAC)
• Support for full/native charms for enhanced VNF management
• Network Slicing extensions
• Network-Service-level primitives
• Improved monitoring of infrastructure components and VNFs
• Enhanced support for instantiation parameters
© ETSI 2019
Why is OSM Awesome?
46
And because other people say that OSM Rocks!
Scan & Download
© ETSI 2019
<image here>
47
Contributing to the Community
© ETSI 2019
Joining the OSM Community
• Join here as a company or individual contributor!https://osm.etsi.org/about/how-to-join
48
© ETSI 2019
OSM Community Activities
• Weekly Conference Calls• Technical, MARCOM, DevOps, SA, and more!
• Face to Face Meetings• Plenaries and Mid-Release meetings (every 3 months)
• Next location: Madrid (March 2020)
• OSM Hackfests• Co-located with OSM Face-to-Face meetings.
49
© ETSI 2019
Ways to contribute to OSM
• Try OSM and give feedback to the community.
• Join as a developer to make contributions to the code.
• Join the community to contribute to design discussions.
• Start building your own distribution of OSM as an integrator.
• Host an OSM meeting to contribute to the community’s growth in your area.
50
![[e-Book] Network Functions Virtualization (NFV) pour les nuls](https://img.dokumen.tips/doc/110x75/58ecb0b21a28abc8428b471d/e-book-network-functions-virtualization-nfv-pour-les-nuls.jpg)
