7 NFV Solution Overview

NFV Solution Overview
www.huawei.com
Copyright © Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:

 Understand NFV solutions and key capabilities.
 Understand computing, storage, and network virtualization technologies.
 Master principles of OpenStack.
 Know basic knowledge of containers and microservices.
 Know basics about NFV O&M.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 2

Contents
1. NFV Background
2. NFV Architecture and Characteristics
3. NFV O&M Solution
4. Automatic O&M

Development of Telecom Networks
NFV Network Structure
Unified IP-based bearer network
IT Service
vMSE
vEPC
vHSS
vIMS
Various network protocols
PON/NG-PON
ADSL / VDSL
GSM/UMTS
LTE/LTE-A
40G/100G
400G/IT
IMS
CS
...
...
...
...
UMTS
PSTN
GSM
Unified virtualization layer
LTE
RAN FAN IP+ Core
platform platform Optical platform Unified hardware platform
platform
FR ATM IP All-IP
E1/T1 Optical Ethernet

• Unified hardware platform
• IP-based bearer • Unified bearer network
• Multiple bearer network protocol
protocols • Separated control plane
• Single service type and service plane
• Complex network • Complex device
maintenance maintenance

Structural Challenges Faced by CT
Subscriber growth is saturated. Service innovation

2002
5/year
Telco
vs.
160,000/year
App store
> 32,000 times

Traditional services are declining. Service TTM
2013
6/month
Telco
vs.
12/hour
Individual
developers
> 360 times

To increase revenue To reduce OPEX To innovate
and CAPEX

Challenge from High Efficiency of Internet Service Providers (OTTs)
Business portal Service portal

Management
Promise theory portal Service & Business orchestration (automatic combination of service
packages and service processes)
(Autonomic System)
Big data
analytics
3 4 app app based on
and management
Product
Statistics management applications
deployment
report
Function
Function
Function
Function
Configuration
Configuration
management
management
App
policies
Service
policies
Service
Marketing
5
Parallel
2
Service Parallel management
framework framework User data
system
monitoring
and alarms Cloud infrastructure
Pricing and Service data
charging
Resource Scheduling 1
Configuration
Source data
management
Cloud OS
model policies
Infrastructure
monitoring ...
and alarms Compute Network Storage ...
Maintenance Service system Operation

System System
1. Automatic scheduling of hardware system 4. SLA- and QoS-based automatic quality assurance,
resources (cloud OS) fault isolation, and fault self-healing
2. Automatic service expansion based on parallel and 5. Big-data-driven system self-optimization and
distributed applications automatic optimization
3. Automatic service provisioning and deployment
based on initial configurations

What Is NFV?
 NFV is short for Network Functions Virtualization.

 NFV uses IT virtualization technologies to consolidate many network equipment types onto industrial standards,
such as servers, switches, and storage, which could be located in data centers, network nodes, or end user
premises. It involves the implementation of network functions in software that can run on standard servers.
 The network functions can be migrated, deployed on instances in any location on networks without adding new
physical devices.

ETSI MANO Architecture
 Virtualized infrastructure manager (VIM)
 Virtualized network function manager (VNFM)
 VNF orchestrator (NFVO)

Huawei 5GC Architecture (Non-container-based VNFs)
NFVO
(Manages NS
life cycle)
VNF VNFM
Virtualized Network (Manages VNF
Function life cycle)
(e.g. UNC/UDG)
NFVI Cloud OS
(Hypervisor + Management VIM
Module) (Provisions
virtualized
Hardware resources)
(Server /Storage/Network)
MANO

Huawei 5GC Architecture (Container-based VNFs)
NFVO
(Manages
NS life
cycle)
Virtualized Network Function VNFM

VNF (e.g. UNC/UDG) (Manages
VNF
life cycle)
CaaS
Cloud OS
VIM
(Hypervisor + Management
NFVI (Provisions
Module)
virtualized
Hardware resources)
MANO

Automatic VNF Deployment
VNF deployment
Telecom operation system
1. The NFVO receives the VNF deployment requirements.
1
1 MANO
Network
2. The NFVO instructs the VIM to provide virtual resources.
OSS/BSS Service
NFVO Template 3. The NFVO instructs the VNFM to deploy the VNF.
8
3 2 4. The VIM creates a VM.
EMS VNFM VNF
Packages 5. The VIM notifies the VNFM of the VM creation success.
6 5 VIM 6. The VNFM deploys the VNF.

VNF
Templates
7 7. The VNF is on-boarded on the EMS, and initial
4
vCPE ... vBNG
configurations are performed on the EMS.
VM VM 8. The service system provisions services.
Traditional NFVI
network
DC1 DC ...
SNMP/CLI RESTful APIs

Contents
1. NFV Background
3. NFV O&M Solution
4. Automatic O&M

Contents

2.1. NFV Architecture and Characteristics
2.2. Virtualization Basics
2.3. OpenStack Principles
2.4. Basics of Containers and Microservices

Open Architecture and Compatibility
Extensive compatibility Co-deployment of multi-vendor devices Stable performance
MANO Live-network Open Lab

OSS/BSS
vPCRF
vEPC
vMSE
vIMS
...
...
...
Vendor A: NFVO
OSS
RESTful
Mainstream cloud OS
Ecosystem alliance
pre-evaluation
Vendor B: VNFM CORBA
Benchmark Benchmark
Mainstream Hypervisor VM design for the CSCF service
EMS processing module: Two VMs, each with four
SOAP REST
(EXSI) cores, 2.49 GHz
interpreter interpreter (C7000)
dominant frequency, and
8 GB memory
COTS (Huawei supports 200+ vendors.) TAS service module design:

Service module VM: 8-
core, 16 GB memory
VIM VIM Forwarding module VM:
2-core, 4 GB memory

Virtualization Architecture VS. Cloud-based Architecture
Traditional devices Virtualization Cloud-based architecture
VNF view (such as CSCF)

VNF (such as Service data layer (distributed
CSCF) memory database)
Service logic layer

Service logic and
Service logic and data are bound.
data are bound. VM Session forwarding layer
Software-hardware
Software-hardware decoupling Software-hardware
coupling
decoupling
Key capability differences
• Supports separation between programs and data, and between

forwarding layer and data layer.
• Supports horizontal expansion and distributed memory database.

Elastic Scaling
Elastic scale-out Elastic scale-in
Active DB Standby DB Active DB Standby DB

A A A A
B B B B
Dynamic data includes
subscription data, link office
C C direction configuration data, C C
and stable call session data.
... ... ... ...
• Stateless Obtain dynamic data.
• Distributed • Stateless Stable traffic can be reestablished
• Service • Distributed in other modules immediately.
processing Real-time • Service
... Real-time New processing
module with
traffic traffic module module with ...
N+M Real-time Real-time Real-time
redundancy N+M
traffic traffic traffic
redundancy
Based on CPU Based on

Service Service Service Service
load CPU load
distribution distribution distribution distribution
Active Standby Active Standby

High Availability
Redundancy mechanism 1: active/standby redundancy
Application layer
Service Service
module module
Redundancy mechanism 2: stateless N+M redundancy

Service Service Service
module module module
Ensures zero interruption of
application layer sessions.
Redundancy mechanism: rapid VM rebuilding

Cloud OS
99.999%
availability
VM New VM
Ensures that resources

are always available.
Hardware layer
Redundancy mechanism: cluster and material redundancy
Hardware, VM, and service-layer reliability are implemented

independently, ensuring availability of the entire system.

New Mode Helps Cost Reduction and Revenue Growth
Top 3 Benefits of NFV Traditional network NFV network
Shortens TTM, reduces TCO, and Service deployment Simplified

Flexible and fast
Shorter
promotes innovation deployment
is complex deployment TTM
and time-consuming
Infrastructure Automatic
Complex O&M OAM
Unified management
Reduced
TCO
Co-deployment of Infrastructure Unified
multiple devices Share hardware
A platform for third-

Open
Accelerated
Closed party developers
Source: Infonetics (2014.3) innovation
SDN and NFV Strategies: Global Service Provider
Survey

Contents


Definition of Hypervisor
 A hypervisor is a software layer between physical servers and OSs. It allows multiple OSs and applications to
share the same set of physical hardware.
 It coordinates access to all physical devices and VMs on the server. It is also called a virtual machine
monitor (VMM).
 The basic function of Hypervisor is to support multi-workload migration without interruption.
 When the server starts and runs the Hypervisor, the Hypervisor allocates appropriate memory, CPU,
network, and disk resources to each VM and loads the guest OSs of all VMs.

Hypervisor Working Principle
 x86 OSs are designed to run directly on bare hardware devices. Computer hardware is totally designed.
 In the x86 architecture, four privilege levels (Rings) are provided for operating systems and applications to
access hardware. There are four privilege levels, numbered 0 (most privileged) to 3 (least privileged).
 The OS (kernel) requires direct access to hardware and memory, and its code runs on Ring 0.
 The OS can use privileged instructions to control interrupts, modify page tables, access devices, and more.
 The code of applications runs at Ring 3 (least privileged), and controlled operations are not allowed.
 If you want to perform controlled operations, for example, access disks or write files, you need to execute
system calls (functions). During system calls, the CPU running level is switched from Ring 3 to Ring 0, and
the system calls the corresponding kernel code. This way, the kernel completes device access and then
switches from Ring 0 to Ring 3.
 This process is also called switching between the user mode and the kernel mode.

Background of Compute Virtualization
 Compute virtualization adds a virtualization layer between the hardware and the applications to
simplify the representation, access, and management of computer resources, such as CPUs and
memory, and provide standard I/O interfaces for these resources.
 The virtualization technology is used to virtualize and run multiple VMs on a physical machine,
improving the utilization of computer hardware resources.
 Applications highly benefit from compute virtualization technologies but also encounter a slump in
performance when compared to hardware on legacy networks.
 What compute virtualization technologies has Huawei used to improve application performance?
 Huawei CloudCore solution uses key compute performance optimization technologies, such as
resource isolation, NUMA affinity, and CPU pinning, to ensure the performance of service VMs.

Background of Compute Virtualization (Cont.)
 Compute virtualization can be simply understood as allocating pCPUs to VMs in the form of virtual CPUs
(vCPUs). How pCPUs are allocated and occupied determines the compute resource usage and performance
of VMs. The following technologies are used during CPU allocation:
 Resource isolation: On each server, physical CPU cores for the NFVI and service VMs are isolated from
each other, avoiding CPU resource scrambles. For example, four physical cores on each blade are isolated
and dedicated for virtualization-layer services.
 Non Uniform Memory Access (NUMA) affinity: VM performance deteriorates if it spans multiple NUMA
nodes. The Huawei NUMA affinity feature enables the system to automatically deploy VMs on the same
NUMA node (with vCPU and memory allocated) and balance loads over different NUMA nodes, which helps
decrease the memory access delay and improve VM performance.
 CPU pinning: CPU pinning enables the system to pin, or establish a mapping between a vCPU and a
pCPU core so that the vCPU can always run on the same pCPU core, which means VMs can use their
dedicated pCPUs.

Core Technologies of Compute Virtualization
 Compute virtualization can be simply understood as allocating pCPUs to VMs in the form of vCPUs.
 Resource isolation: On each server, physical CPU cores for the NFVI and service VMs are isolated from each
other, avoiding CPU resource scrambles.
 vCPU pinning: vCPUs of each VM are pinned with and exclusive to pCPUs.

NUMA Concept
 Commercial servers can be classified into the following types based on the server
CPU architecture:
 Symmetric multi-processor (SMP)
 Massively parallel processing (MPP)
 Non-uniform memory access (NUMA)
 In the NUMA architecture, a CPU can access the entire system memory and the CPU accesses the memory on its NUMA node much
faster than that on a remote NUMA node.
NUMA NODE 0 NUMA NODE 1
MEM MEM
CORE CORE CORE CORE
CPU Memory CPU Memory

Controller Controller
CORE CORE CORE CORE

I/O I/O
SYSTEM BUS
Compute node
NUMA architecture

NUMA Deployment Policy
VM 1 VM 2
vCPU vCPU vMEM vNIC vCPU vCPU vMEM vNIC
NUMA NODE 0 NUMA NODE 1
MEM MEM
CORE CORE CORE CORE
CPU Memory CPU Memory

Controller Controller
CORE CORE CORE CORE
I/O I/O
SYSTEM BUS
COMPUTING NODE
NUMA affinity IO-NUMA

 For a VM created using NUMA affinity rules, its  When IO-NUMA is used, virtual NICs of a VM
vCPU and memory resources come from the same come from the physical NIC of the same NUMA
NUMA node of a compute node. This improves node to avoid using virtual NICs across NUMA
memory access performance. The performance nodes, thereby improving network I/O
gain is especially significant for applications performance.
entailing frequent memory accesses.

Background of Storage Virtualization
 Storage virtualization is the pooling of physical storage resources from multiple network
storage devices into what appears to be a single storage device that is managed from a
central console.
 Huawei 5GC solution uses distributed block storage.

Distributed Storage
 Distributed storage is characterized by software-defined storage.

 In distributed storage mode, local storage resources provide storage services for applications
through a storage resource pool, which is centrally managed using the storage software.
 Distributed storage is classified into distributed block storage, file storage, and object storage based
on data types. Multiple open-source projects (such as Ceph, GlusterFS, Sheepdog, and Swift) are
dedicated to the research on distributed storage. Google, AWS, Microsoft, Kingsoft, Qiniu, Youpai,
Alibaba Cloud, and QingCloud has issued commercial distributed storage products. Huawei
developed FusionStorage to provide distributed block storage.

Huawei FusionStorage
 FusionStorage Block is a piece of distributed block storage software specifically designed for the storage
infrastructure of cloud computing DCs. Similar to a virtual distributed SAN storage system, it can employ
distributed technologies to organize HDDs and SSDs of x86 servers into large-scale storage resource pools and
provide standard SCSI and iSCSI interfaces for upper-layer applications and VMs.
 FusionStorage Block applies to:
 Large-scale cloud computing data centers.
FusionStorage Block organizes disks of x86 servers into large-scale storage resource pools, provides standard block storage data access
interfaces SCSI and iSCSI, and supports a wide range of hypervisors and applications, such as SQL, web, and industry applications. In addition,
it can integrate with a variety of cloud platforms, such as Huawei FusionSphere, VMware, and OpenStack, enabling on-demand resource
allocation.
 Critical enterprise IT infrastructure.

FusionStorage Block employs InfiniBand (IB) for server interconnection and supports SSD cache and SSD main storage, which significantly
improves the performance and reliability of storage systems while retaining the high scalability of distributed storage systems. For this reason, it
supports critical enterprise databases, Enterprise Resource Planning (ERP), and Customer Relationship Management (CRM) and provides
sufficient storage space for large amounts of data generated by these applications.

Software Architecture
Module Function
FusionStorage A management process. Provides O&M functions, such as alarm reporting, monitoring, logging, and
Manager (FSM) configuration. It is best practice to deploy two FSM nodes working in active/standby mode.
FusionStorage
A management agent process. It is deployed on each node (server) to communicate with the FSM node.
Agent (FSA)
A service control process. Controls status of distributed clusters and data distribution and reconstruction rules.
MDC
MDC is deployed on three, five, or seven nodes to form a control cluster.
A service input and output (I/O) process. Manages metadata and provides an access service that enables
VBS computing resources to connect to distributed storage resources. A VBS process is deployed on each server to
form a VBS cluster.
A service I/O process. Performs specific I/O operations. Multiple OSD processes can be deployed on each
OSD
server and one disk requires an OSD process.

Network Virtualization
 Network virtualization provides layer 2 network interconnection for VMs.

 VMs are connected to external networks through virtual switches that are bound to
physical NICs.
 Telecom services require high forwarding performance and little to no delays, which is
assured by purpose-built hardware on the traditional ATCA platform. COTS hardware is
used on an NFV network. How does Huawei ensure the forwarding performance on
such a network?

Overview of Key Network Virtualization Technologies
Name Concept
Open Virtual Switch (OVS) is an open-source virtual switching solution, and is integrated
OVS
into the KVM.
Hardware passthrough allows a VM to directly access a PCIe device (for example, a NIC is
a PCIe device). That is, a VM has direct access to hardware registers and message queues.
Hardware
It is also called PCI pass-through. A NIC can be assigned for one VM or be virtualized to
passthrough
multiple virtual NICs (SR-IOV) for use of one or more VMs. SR-IOV is supported only by
certain NICs.
SR-IOV is an extension of the PCI Express (PCIe) specification. It enables a PCIe adapter
SR-IOV (such as a NIC) to function as multiple independent components (NICs) through a shared
PCIe interface.
An elastic virtual switch (EVS) provides virtual network switching functions, including VLAN,
EVS DHCP isolation, bandwidth limiting, and priority setting. This is a user-mode-based virtual
switching solution developed by Huawei based on DPDK.

Open vSwitch (OVS)
 Open vSwitch (OVS) is a software-based open-source virtual Ethernet switch (Ethernet bridge) licensed under the Apache
2.0 license.
 The OVS supports multiple standard management interfaces and protocols, such as NetFlow, sFlow, SPAN, Remote
Switched Port Analyzer (RSPAN), Command Line Interface (CLI), LACP, and 802.1ag. It also supports distribution across
multiple physical servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
 The OVS supports the OpenFlow protocol and can be integrated with multiple open-source virtualization platforms.
 An OVS is used to transmit traffic between VMs and implement communication between VMs and external networks.

Elastic Virtual Switch (EVS)
 Huawei EVS uses the following technologies:

 NIC: Physical NICs use Intel DPDK to boost the packet processing performance.
 EVS: The EVS runs in user space on the host OS and leverages user-space packet
transmission and huge-page memory of DPDK to improve network performance. Data is
received and sent in the kernel mode on an OVS but is in the user mode on an EVS. An EVS
starts threads in user mode (bypassed the kernel mode) and takes over the packet sending and
receiving of the kernel to improve performance. However, the OVS does not have dedicated
threads.
 Dedicated CPU cores are allocated to EVS for data transmission to improve performance.

Differences Between OVS and EVS

SR-IOV High-Speed Forwarding Technology
 To enable multiple VMs to directly access and share a physical device, PCI-SIG has released the
single-root I/O virtualization (SR-IOV) specification, which defines a standard mechanism to allow
multiple clients to share a device.
 Currently, SR-IOV is most widely used on NICs.

SR-IOV High-Speed Forwarding Technology (Cont.)
 SR-IOV enables a single functional unit (for example, an Ethernet port) to appear to be multiple
independent physical devices. A physical device with the SR-IOV function can be configured as
multiple functional units. SR-IOV provides the following functions:
 Physical functions (PFs): Full-featured PCIe devices that can be discovered, managed, and
configured as common PCI devices.
 Virtual functions (VFs): A simple PCIe function that can process only I/Os. Each VF is derived
from a PF. The number of VFs on a device is limited. A PF can be virtualized into multiple VFs
for different VMs.

Advantages and Disadvantages of SR-IOV
Advantages Disadvantages
Device sharing (multiple VMs share the physical This function depends on devices. Currently, only some
port of an SR-IOV device) devices support SR-IOV.
VMs cannot be dynamically migrated because VMs
Close to native performance directly use physical host devices. VM migration and
saving are not supported.
Compared with VT-d, SR-IOV uses fewer devices to
support more VMs, improving space utilization of
the data center.

Contents


What Is OpenStack?
 Literally, many open-source component services are combined into a cloud computing management platform.
 OpenStack began as a joint project of Rackspace Hosting and NASA and is released under the terms of the
Apache license. OpenStack is a free and open-source project.
 The participants of the open-source project include IBM, Intel, Red Hat, Cisco, AT&T, Ubuntu, HP, IBM, Intel,
Rackspace, SUSE, and Huawei. Huawei is the first vendor in China to become a platinum member of the
OpenStack Foundation.
 URL of OpenStack open-source community: https://www.openstack.org/

Why OpenStack Is Used?
Huawei 3rd DC MANO/ 3rd Guest OS

OpenStack Management BOSS &
OM Applications
Open architecture
• Northbound standard OpenStack APIs and various
ecosystems
• No technical lock-in
• Apache license used, allowing on-demand commercial
integration of applications
High scalability
• Easy to add new custom modules and services (such as a
new hypervisor)
Heat • Can be cascaded to build a large-scale cloud platform
Powerful compatibility with cross-vendor devices

Nova Neutron Cinder • Strong southbound access capability, co-deployable with
multiple hypervisors (such as KVM, Xen, and VMware),
storage devices, networks, and physical devices
FusionCompute
Hypervisor
FusionStorage
SDS
FusionNetwork
SDN
3rd Huawei &3rd Huawei &3rd Most popular, fast-growing cloud platform with numerous
Hypervisor Storage Network
members
• Rapid response to fix bugs with a new version released every
six months
• 300+ participated enterprises and 20,000+ developers

Logical Architecture of OpenStack
Service Function
Portal: Horizon provides an easy-to-use web portal for managing OpenStack services. Note: In FusionSphere
Horizon
OpenStack, FusionManager provides this service.
Compute service: manages the life cycle of VM instances. OpenStack does not provide virtualization capabilities.
Nova
Instead, it interacts with the hypervisor (such as KVM and Xen) to manage the virtual resources.
Network service: Neutron provides network virtualization technologies for cloud computing, network connection
Neutron
services for VMs, and other services, such as VPN and firewall.
Swift Object-based storage: Swift mainly stores unstructured data of a large data volume, for example, image files.
Block storage: Cinder provides running VM instances with stable data block storage services, for example,
Cinder
creating a volume, deleting a volume, and attaching or detaching a volume to or from an instance.
Authentication: Keystone provides identity verification, service rules, and service token functions for other
Keystone
OpenStack services.
Image service: The image server discovers, registers, and retrieves VM images, but it does not store image files.
Glance
Generally, images are stored in object-storage systems like the OpenStack Swift project.
Monitoring: Ceilometer collects almost all events that occur inside the OpenStack system as a data basis for
Ceilometer
other related services, such as monitoring and billing.
Service orchestration: Heat provides a template-defined mode for automatically deploying a cloud-based
Heat
infrastructure and software environment running computing, storage, and network resources.
Ironic Bare metal server (BMS) provisioning

What Is OpenStack (Cont.)

VM Creation Procedure

Contents


Microservice
 What is a microservice?
 Microservices are a type of software structure that arranges an application as a collection of
small and independent services.
 These services communicate with each other through APIs that are irrelevant to languages.
 These services are fine-grained and loosely coupled.
 Microservice-based modular structure facilitates system construction.
 These services are autonomous and complete, controlling all components, including UI,
middleware, access, and transactions.

Microservice Architecture vs. Monolithic Application
Monolithic applications Microservice applications (1) Microservice-specific
Appropriate design in a instantiation and scaling
specific environment can maximize resource
UI maximize efficiency. If efficiency.
UI Resource
the environment (2) Excessively fine
efficiency
changes, huge granularities will increase
Catalog resources may be basic overhead and
Service wasted. cross-service
Business Logic
communication overhead.
Recommendation Customer
Data Access Layer Account Service
Service Service (1) A full-function team
Development and
maintains microservices,
maintenance complexity
improving development
Maintenance increases rapidly with
and O&M efficiency.
efficiency software volume.
2) Too many details will
Appropriate design can
DB DB DB DB increase management
simplify subscriber
and maintenance costs.
operations.
Characteristics of the microservice Core of the microservice Principles for defining

architecture architecture microservices
• Services are self-governed, self- • Decoupling software logic • Independent life cycle
Weak. Agile release is Excellent. Good decoupling
Agility
contained, and self-managed. into microservices. An • Independent resource not supported. significantly improves agility.
• Services are independently developed application is broken down scaling
and platforms and languages can be into its core functions • Independent optional
selected separately. independent of each other. components Excellent. Good Medium. Excessive splitting
• Services are running and upgraded Performance performance is usually increases the delay and
independently. degrades the performance.
provided.
• Inter-service interfaces are
contractual.

Relationship Between Microservices and Containers
 Essentially, microservices are not directly related to containers.
 The concept of microservices was proposed in the 1970s.
 Container technology was proposed in 2013, much later than microservices.
 Microservices are an architectural approach to building applications. It is characterized by single
responsibility, service autonomy, lightweight communication, and interface clarification. Based on
this, the container can be used to facilitate the development, maintenance, and on-demand scaling
of microservices.
 (1) According to the concept of microservices, deploying services in containers implements rapid
deployment and fast iteration.
 (2) In the cloud computing era, containers gains more attention since they can be used to replace VMs.
 (3) k8s is a default containerization platform standard. It integrates the configuration center and registration
center.

What Is a Container? Lightweight OS Virtualization
VM vs. Container Docker container engine

Apps Apps
Build Ship Run
Bins/Libs Base Image(Bins/Libs)
Homogeneous OS with container Engine

Guest OS (kernel)
Namespaces, Control
groups
• The image layering technology facilitates quick software
Host OS with Hypervisor Engine
development and deployment.
• Centralized warehouse facilitates software sharing and release.
COTS Hardware COTS Hardware
Container is an OS kernel-based lightweight virtualization technology.

Unified container engines and images make software deployment
Containers provide higher resource utilization and faster startup speed
and sharing simple and efficient.
than VMs, but lower security isolation.

Comparison Between Containers and VMs
Item Container VM
Design Concept Application-oriented lightweight Resource-oriented system-level isolation
OS-level virtualization, providing an application Device-level virtualization, providing a system
Implementation Technology
running environment running environment
Virtualized hardware resources, affecting the
Using the hardware resource (I/O) directly
performance
Relying on hardware to facilitate high-performance
Adapting to any CPU architecture, such as x86,
Resource Dependency virtualization. (KVM has a complete ecosystem
ARM, and PPC with high performance
only on x86 servers.)
Resource miniaturization for improving the
N/A
resource efficiency
Image Release MB-level layered mirroring About 10 GB-level layered mirroring
Microservice bearers for Build-Ship-Run N/A
Microservice ecosystem Abundant microservice ecosystems (such as
third-party middleware, distributed framework, N/A
tool system, and Docker Hub)
Development Mode DevOps CI/CD N/A
Deployment in milliseconds About 5 minutes for deployment
Performance Slightly better in compute, network, and I/O
—
virtualization
Shared kernel space. Security isolation needs to
Security Complete system isolation
be improved.

Huawei Container Cluster Scheduling and Application
Orchestration Solution – FusionStage (PaaS)
Application scheduling and resource management framework: Sets up Kubernetes-based enhanced automatic lifecycle management, including application modeling,
orchestration deployment, resource scheduling, auto scaling, monitoring, and self-healing.
Microservice operation and management framework: provides applications with a series of distributed microservice management capabilities, such as automated
application registration, discovery, governance, isolation, invoking, and analysis, to simplify the complexity of distributed systems.
Application development pipeline framework: streamlines the automated CI/CD process from encoding and code submission to automated compilation, packaging,
continuous integration, as well as automated deployment and rollout.
Cloud middleware services: provide middleware services required by cloud-based applications and integrate traditional non-cloud middleware capabilities through service
integration management.
Management zone Data zone
PaaS cloud management system Legacy applications Virtualization applications Cloud-based applications
Combined ERP e-Banking... CRM E-commerce... Web Email...
orchestration/de
ployment
Service
Monitoring & integration
self-healing Application
control Microservice running and governance framework Cloud middleware services
scheduling &
resource mgmt. Application
framework resource Distributed cache service
Auto scaling Service route Service discovery Elastic load balance (ELB)
scheduling (DCS)
Cross-cloud
adaptation
Service governance Distributed message service Cloud Service Catalog

Service registration
Code version (isolation and fallbreak) (DMS) (CSC)
management
Continuous Application
development IDE Service monitoring (call Service definition
integration
pipeline framework chain) management
Compilation and
packaging
IaaS
The development pipeline is open source, which is included in Huawei products Some microservice components are open source.
and provided for customers free of charge. Huawei can recommend qualified The FST 2.0 microservice framework provides POC capabilities,
suppliers for customization, but Huawei does not provide customized services. and was commercially used in Q1 of 2018.

How NFV Introduces Containers?
Container-based VNF Container-based VNF Container-based VNF
Existing Existing
VNF VNF
Container platform Container platform Container platform
VM Bare metal VM Pure Bare metal

IaaS IaaS
VM-based Container NFVI Extended Bare-Metal Container Pure Bare-Metal Container

Sharing infrastructure with
Yes Yes No
existing VNFs
No. The container platform is integrated
Container platform decoupled No. The container platform
Yes. The NFVI shields hardware. with the NFVI, and the NFVI is coupled
from infrastructure manages hardware infrastructure.
with hardware.
Yes. The NFVI provides multi-vendor
No. Container platforms are still under quick development. Multi-vendor
Multiple-vendor integration integration capabilities, and different vendors
integration is difficult before container platforms are standardized.
can use their own container platforms.
VMs are used to isolate containers. This Physical machines are used to isolate containers, implementing isolation
Isolation of containers from
enables security isolation between tenants between tenants. This method is not as flexible as container isolation using
multiple vendors
more flexibly. VMs.
performance Similar to VM performance Similar to physical machines
Container OS faults are within VMs, so other
Reliability Container OS faults are within bare-metal devices.
VMs are not affected.
VMs can be used to implement advanced
Resource management
functions, such as live migration of Advanced functions, such as live migration of containers, are unavailable.
flexibility
containers.
Use VM-based containers because bare-metal containers do not support multi-vendor integration before they are standardized.

Impact of VMs and Containers on the NFV Model
Network functions virtualization
orchestrator (NFVO):
 Orchestrates NSs and VNF software
NFVO packages.
(Manages NS  Manages NS life cycles.
life cycle)  Globally manages, authenticates, and
The CaaS layer is added to authorizes NFVI resource requests.
 Manages policies on NS instances.
the original NFV model and
interfaces are added between Virtualized network function manager (VNFM):
 Manages life cycles of VNF instances.
the CaaS layer and VNFM.  Provides coordination between the NFVI and
• Orchestrates, deploys, and EMS.
VNF Virtualized Network Function
schedules containers. (e.g. CloudIMS/CloudEPC) VNFM  Functions as a VNF container resource
• Provides CT enhancement (Manages VNF
management portal.
capabilities for containers,  Manages life cycles of container-based
life cycle)
such as hugepage memory, VNFs, including instantiation, uninstallation,
CaaS auto scaling, and transparent transmission of
shared memory, DPDK, CPU
upgrade requests.
pinning, and isolation.  Monitors container alarms and KPIs.
• Supports container network
capabilities, SR-IOV+DPDK, Cloud OS VIM Virtualized infrastructure manager
NFVI (VIM):
and multiple network planes. (Hypervisor + Management Module)
(Provisions
• Supports the IP SAN storage  Controls and manages compute,
virtualized storage, and network resources.
capability of VM-based resources)
Hardware  Collects and reports infrastructure
containers. performance counters and events.
MANO
Management and
Orchestration

Basic Concepts Introduced to 5GC Deployment
VM Micro Service
POD POD VM
Container1 Container1
POD for Controller
VM
POD for Executor
VM: Container: Relationships between VMs, containers, Relationships between microservices,

1. Each VM has an independent 1. Containers act as lightweight and pods: pods, and VMs:
guest OS, ensuring security VMs. They share the OS 1. Pod is a resource management 1. Microservice is a concept of logical
isolation. kernel. Containers are less concept defined in K8s and is not a functions.
2. Hardware resources are isolated than VMs. running entity. 2. The logical functions of
virtualized, affecting the 2. No performance penalty for 2. Containers with a group of functions microservices need to be carried by
performance. bare metal containers. form a pod, and are deployed by pod. the VM or pod entities.
3. Second-level instantiation, 3. A pod is deployed on a VM.
and agile deployment. 4. Containers within a pod cannot be
4. Multiple containers can run deployed on different VMs.
in a VM.

LCM Information Model for VNFs Running on VM-based Containers
Service Model The items highlighted in yellow are the main objects
managed by the container-based VNF LCM.
NFVO
Software Model
NS
Resource Model
1:N
1:N
N:1 1:1 VNFM
VNF VDU
N:1
1:N
N:1
1:1 1:N N:1
VNFC (Micro)Services Pod VM Host
1:N
CaaS
EMS Container

Section Summary
 This part describes the following key NFV technologies:

 Basic concepts of Hypervisor
 Knowledge about compute, storage, and network virtualization
 OpenStack concepts and functions
 Basics of containers and microservices

Contents
1. NFV Background
3. NFV O&M Solution
4. Automatic O&M

NFV Routine Monitoring Solution
NFV O&M Solution
IES
OSS Auto-
Monitoring Analysis
Healing
2
EMS
Monito Auto-
Analysis VNFM
ring Healing
CloudIMS CloudEPC CloudVAS 1
vCPU vStorage vSwitch OpenSta

Server Storage Switch ck VIM
NFVI AC
1 Small closed-loop (single-vendor) 2 Large closed-loop (multi-vendor)

Concept of Large and Small Closed Loops
Type Definition Characteristics
Carriers divide NFVI resources and isolate different resource pools for
In the layered delivery scenario of Telco different vendors.
Cloud, the IES is used to build unified A vendor's EMS is used to manage its VNFs, instead of monitoring
O&M capabilities, which is called a large NFVI resources and the vendor's EMS can provide association
Large
closed-loop. The large closed-loop analysis between VNF and NFVI virtual resources (small closed loop,
closed-loop
solution provides cross-vendor cross- within the vendor).
layer O&M capabilities and uses IES as The IES provides cross-vendor, cross-layer, and comprehensive O&M
the main O&M entry. for NFVI (large closed-loop, implementing cross-vendor, vertical, cross-
layer, and cross-service domain O&M actions).
In the telecom cloud vertical delivery

scenario, U2020 is used to build unified Carriers require that the EMS of the cloud core network be responsible
O&M capabilities, which is called the for O&M of both the cloud core VNFs and the NFVI.
Small
small closed-loop. U2020 implements Carriers' BOSS can be integrated based on the existing EMS
closed-loop
unified O&M of the NFVI and VNFs. The interconnection interfaces and the NFVI O&M information is carried
EMS is used as the unified O&M center over these interfaces.
of the cloud core network.

NFV Large Closed-Loop Scenario
IES 1. eSight is as the local O&M center of
Service O&M telecom cloud to manage networks,
Carrier's OSS physical devices, virtual resources,
(Traditional ICT-O ICT-A and nodes, and provides correlation
Centralized O&M at the
O&M) 4 analysis capabilities, a unified NFVI
infrastructure layer
O&M GUI and O&M service
interfaces (the interfaces allow
access of third-party hardware).
2. EMS is the O&M center for vendor
Vendor O&M VNF alarms/performance/resources REST: managed VNF alarms/performance/resources devices, providing O&M services to
alarms/performance/ managed VNFs, including
resources
Huawei U2020 or other EMS S- S-
correlation analysis, monitoring, and
3rd EMS (multiple instances)
2 (Supporting multiple instances) VNFM VNFM assurance of VNFs and
infrastructure-layer resources.
Proprietary interface: alarms/performance/resources 3 3. VNFM only obtains NFVI monitoring
Fast fault reporting
Managed data of its managed VNFs.
VNF 1 VNF 2 VNF 3 VNF 4 alarms/performance/resources VNF 1 VNF 2 VNF 3 VNF 4 4. IES provides service monitoring, log
management, unified device O&M,
VIM
and NFVI O&M, implements cross-
Virtual compute Virtual storage
1 Virtual storage Virtual network
vendor, cross-layer correlation
FS VIM with analysis, fault demarcation, and
O&M fault locating.
Server Storage enhancement Storage Third-party hardware
(eSight)
Network DeviceAC(O) NFVI n
VDC A
NFVI 1 VDC B
REST: alarms/performance/resources
Portal Local O&M at the NFVI

NFV Small Closed-Loop Scenario
Carrier's OSS
Implements SSO between U2020

and eSight to realize centralized
VNF and NFVI alarms/performance/resources monitoring.
5
Vendor O&M REST: managed
alarms/performance/re
sources
Huawei U2020-CN
2 (single-instance) LCM
Proprietary interface: alarms/performance/resources

3 Managed
Fast fault 4 alarms/performance/resources
reporting
VNF 1 VNF 2 VNF 3 VNF 4 NFVI alarms/performance/
resources
VIM
Virtual compute Virtual storage

1 Virtual storage Virtual network
VMware
Enhanced O&M
service (eSight)
Server Storage Storage
Network AC Device
NFVI
REST: alarms/performance/resources

Information Collection in the Large Closed-Loop Solution

U2020-CN Cross-Layer Monitoring Information Collection in the
Small Closed-Loop Solution

Self-Healing in the NFV Large Closed-Loop Solution

Self-Healing in the NFV Small Closed-Loop Solution

Section Summary
 This part describes the concepts related to large closed-loop and small closed-loop O&M.

Contents
1. NFV Background
3. NFV O&M Solution
4. Automatic O&M

Understanding of O&M
 O&M: routine O&M interaction between professional technical personnel and various software and hardware
objects.
 O&M differences between traditional and Internet enterprises:
 Traditional enterprises: Management prior to O&M. Commercial O&M software and human-based O&M are recommended.
 Internet enterprises: O&M is prior to management. Open-source O&M software and tools are recommended.
 Future O&M work: 50% of O&M and 50% of development.

 Objective of O&M: Use tools to gradually transform O&M into operation, and reduce cost and increase profits.
 O&M values: Is O&M fire-fighting or fire prevention? If it is fire prevention, how should we prevent it?
Specifically, it includes three parts: supervision, management, and control. Monitoring is the "eyes", which
enables you to view the business status more clearly and control the business more carefully. Management is to
develop rules and standards to enable services to run in a standardized manner. Control refers to batch
execution. Instructions can be delivered and the controlled end can proactively provide feedback.

Service O&M Model
Service roles:
1. Professional technical positions, production management
positions, and service support positions.
2. O&M, development, outsourcing, and management
positions.
Service scenario:
1. Monitoring and emergency operations
2. Monitoring + application operation + event ticket creation +
SMS notification.
Service operation:
1. Deployment and monitoring
2. Operation and analysis
Service objects:
1. Physical facilities: equipment room, air conditioner, and power
supply
2. Infrastructure: hardware, network, and software
Application system:
Various service systems

Service O&M Model - Service Activities (DMOA)
 Deploy: Installs and configures objects, updates patches, adds or deletes objects, and maintains
object life cycles.
 Monitor: Traces, compares, and determines the status, performance, and rule compliance of O&M
objects, and generates alarms and real-time views based on the monitoring results.
 Operate: Execute routine operations, commands, scheduled tasks, periodic inspection, batch
operations, technical change, backup and restoration, and switchover in an HA or DR scenario. The
operation result is status, attribute, or mode change.
 Analyze: Analyzes the status, performance, process, changes, and data of various O&M objects. It
also includes problem diagnosis based on certain rules, and generates analysis reports, trend
predictions, or decision-making suggestions.

Functional Layers of O&M Automation
 (1) Resource-oriented automation (ROA)
 Resource-oriented O&M automation implements automatic DMOA for each type of resources
(software and hardware resources) and combines various O&M automation scenarios to free
professional technical personnel from manual labor.
 (2) Application-oriented automation (AOA)
 AOA integrates O&M automation functions for various resources in an application. (such as OA
capacity expansion and e-commerce platform capacity expansion, and gaming zone expansion)
 AOA helps construct the comprehensive O&M automation function based on the correlations
between resources of the application.
 (3) Business-oriented automation (BOA)
 The biggest challenge of BOA is to systematically sort out business processes, business
objects, and business transactions and establish mapping and association between them and IT
O&M objects.

Automatic O&M Implementation
 1. Use commercial software, such as that provided by IBM, BMC, and HP.
 2. Use open-source automatic O&M software, such as Ansible, SaltStack, Puppet, and Chef.
 3. Use automatic O&M software: Top Internet companies' technologies + O&M-focused
vendors + professional project delivery, realizing independent and controllable O&M with
secondary development.

Disadvantages of Traditional O&M Compared with Automatic O&M
 Business service automation  Traditional IT O&M:
 Automatic standard integration, correlation mapping,  O&M personnel rectify problems
user management, problem isolation and diagnosis, passively and manually.
and business transaction management
 Standard service process
 There is a lack of an efficient IT
O&M mechanism.
 A standard enterprise service process is built based on
the ITIL process and enterprise practices.  There is a lack of efficient IT
 Automatic O&M management O&M tools.
 Standardization, visualization, automation, intelligence,  O&M personnel have to do some
and digitization repetitive work.
 Unified configuration
 The key of IT O&M management is to obtain higher
value through the CMS system.
 Collects, stores, manages, updates, and presents data
related to IT service configuration projects (including
software and infrastructure) and their relationships.

Logical Architecture of Automatic O&M

Section Summary
 This part describes concepts related to automatic O&M.

Summary
 This course covers the following contents:

 NFV Infrastructure and Technical Features
 Key NFV Technologies
 Compute virtualization
 Storage virtualization
 Network virtualization
 OpenStack Principles
 Basics of Containers and Microservices
 Concepts Related to NFV O&M Basics and Automatic O&M

Thank you
www.huawei.com

7 NFV Solution Overview

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7 NFV Solution Overview

Uploaded by

Copyright:

Available Formats

NFV Solution Overview

Copyright © Huawei Technologies Co., Ltd. All rights reserved.

 Upon completion of this course, you will be able to:

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 2

2. NFV Architecture and Characteristics

3. NFV O&M Solution

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

NFV Network Structure

Unified IP-based bearer network

Unified virtualization layer

E1/T1 Optical Ethernet

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 4

Subscriber growth is saturated. Service innovation

> 32,000 times

> 360 times

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 5

Business portal Service portal

Maintenance Service system Operation

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 6

 NFV is short for Network Functions Virtualization.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 7

 Virtualized infrastructure manager (VIM)

 Virtualized network function manager (VNFM)

 VNF orchestrator (NFVO)

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 8

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 9

Virtualized Network Function VNFM

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 11

6 5 VIM 6. The VNFM deploys the VNF.

SNMP/CLI RESTful APIs

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 12

2. NFV Architecture and Characteristics

3. NFV O&M Solution

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 13

2. NFV Architecture and Characteristics

2.2. Virtualization Basics

2.3. OpenStack Principles

2.4. Basics of Containers and Microservices

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 14

Extensive compatibility Co-deployment of multi-vendor devices Stable performance

MANO Live-network Open Lab

COTS (Huawei supports 200+ vendors.) TAS service module design:

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 15

Traditional devices Virtualization Cloud-based architecture

VNF view (such as CSCF)

Service logic layer

Key capability differences

• Supports separation between programs and data, and between

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 16

Elastic scale-out Elastic scale-in

Active DB Standby DB Active DB Standby DB

Based on CPU Based on

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 17

Redundancy mechanism 1: active/standby redundancy

Redundancy mechanism 2: stateless N+M redundancy

Redundancy mechanism: rapid VM rebuilding

Ensures that resources

Redundancy mechanism: cluster and material redundancy

Hardware, VM, and service-layer reliability are implemented

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 18

Top 3 Benefits of NFV Traditional network NFV network

Shortens TTM, reduces TCO, and Service deployment Simplified

A platform for third-

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 19