7 NFV Solution Overview
April 8, 2023 | Author: Anonymous | Category: N/A
Short Description
Download 7 NFV Solution Overview...
Description
NF NFV V Solut Solutio ion n Overview Overvi ew
www.huawei.com
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All ri ghts r eserved.
Objectives
Upo pon n com ompl ple etion of thi his s cou ours rse, e, you will be abl ble e to:
Unde Un ders rsta tand nd NFV NFV solut solutio ions ns an and d key key capa capabi bili liti ties es..
Unders Und erstan tand d comput computing ing,, storag storage, e, and netwo network rk virtua virtualiz lizati ation on techno technolog logies ies..
Mast Ma ster er princ princip iple les s of Open OpenSt Stack ack..
Know Kn ow ba basi sic c know knowle ledg dge e of cont contai aine ners rs and and mi micr cros oser ervi vice ces. s.
Know Kn ow basi basics cs abou aboutt NFV NFV O&M. O&M.
Page 2
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Contents 1.
NFV B ac k g r o u n d
2. NF NFV V Ar Arch chit itec ectu ture re an and d Ch Char arac acte terris isti tics cs 3.
NFV O&M Solution
4.
Automatic O&M
Page 3
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Development of Telecom Networks NFV Network Structure e c i v r e S T I
Unified IP-based bearer network Various network protocols L S D V / L S
M S G
N T S P
S T M U
E T L
FR
ATM
IP
E1/T1
Optical
Ethernet
D A
...
N O P G N / N
S T M . U .. / M S O G P
A E T L / E T L
RAN FAN platform platform
G 0 0 .. 1 . / G 0 4
T I / G 0 0 4
S C
...
S M I
S M I v
C P E v
S S H v
E S M v
Unified virtualization layer IP+ Core Optical platform platform
Unified hardware platform
All -IP
•
• •
• •
Multiple bearer protocols Single service type Complex network maintenance
•
•
IP-based bearer network Separated control plane and service plane Complex device
•
Unified hardware platform Unified bearer network protocol
maintenance Page 4
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 4
Structural Challenges Faced by CT
Subscriber growth is saturated saturated..
2002
Service innovation 5/year Telco
vs. 160,000/year
App store
> 32,000 times Traditional services are declining declining..
Service TTM 2013 6/month Telco
vs. 12/hour Individual developers
> 360 times
To increase revenue
To reduce OPEX and CAPEX
To innovate
Page 5
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Challenge from High Efficiency of Internet Service Providers (OTTs) Business portal Management portal
Promise theory (Autonomic System)
Statistics report
Service system monitoring and alarms
Infrastructure monitoring and alarms
Maintenance System
Service portal
Service & Business orchestration (automatic combination of service packages and service processes)
t 3 n t e n m e e g p m a p y n o A l p a e m d d n a
4 n t o n i e t
a m r e u g g a i f n n o a C m
e s c e i v c r i l e o S p
app
app n o i t c n u F
n o i t c n u F
Parallel framework
2
n t o n i t e a m r e u g g i f a n n o a C m
e s c e i v c r i l e o S p
n o i t c n u F
n o i t c n u F
Parallel framework
Cloud infrastructure n t o n i t e a r m u e g g i a f n n o a C m
Resource model
Scheduling policies
Cloud OS
1
Product management
Marketing management
Network
Storage
Pricing and charging
Operation System
1. Automatic scheduling of hardware system resources (cloud OS)
4. SLA- and QoS-based automatic quality assurance, fault isolation, and fault self-healing
2. Automatic service expansion based on parallel and distributed applications
5. Big-data-driven system self-optimization and automatic optimization
3. based Automatic service provisioning and deployment on initial configurations
Service data Source data
...
Service system
5 User data
... Compute
Big data analytics based on applications
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 6
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, switches, and storage, which could be located located in data centers, network nodes, or 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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
ETSI MANO Architecture
Virtua Virtualiz lized ed inf infras rastru tructu cture re manage managerr (VIM) (VIM)
Virtua Virtualiz lized ed net networ work k functi function on manage managerr (VNFM) (VNFM)
VNF orches orchestra trator tor (NFVO) (NFVO)
Page 7
Page 8
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Huawei 5GC Architecture (Non-container-based VNFs)
NFVO (Manages NS (Manages life cycle)
VNF
NFVI
Virtualized Network Function (e.g. UNC/UDG)
Clou Cl oud d OS (Hypervisor + Management Module)
Hardware (Server (Serv er /Stor /Storage/N age/Networ etwork k)
VNFM (Manages (Man ages VNF life cycle)
VIM (Provisions virtualized resources)
MANO
Page 9
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Huawei 5GC Architecture (Container-based VNFs)
NFVO (Manages NS li life fe cycle)
VNF
Virtualized Network Function (e.g. UNC/UDG)
VNFM (Manages VNF life cycle)
CaaS Clou Cl oud d OS NFVI
(Hypervisor + Management Module)
Hardware (Server (Serv er /Stor /Storage/N age/Networ etwork k)
VIM (Provisions virtualized resources)
MANO
Page 11
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Automatic VNF Deployment VNF deploym ent Telecom operation system
1
1. The NFVO receives the VNF deployment requirements. 1
MANO
Network Service Template
OSS/BSS NFVO
2. The NFVO instructs the VIM to provide virtual resources. resources. VNF. 3. The NFVO instructs the VNFM to deploy the VNF.
8 3
2
4. The VIM creates a VM. VM. VNF Packages
VNFM
EMS
6
5
VIM
7 4 vCPE ... vBNG
VM
VM
DC1 SNMP/CLI
RESTful APIs
6. The VNFM deploys the VNF. VNF. 7. The VNF is on-boarded on the EMS, and initial configurations are performed on the EMS. 8. The service system provisions services. services.
NFVI
Traditional network
VNF Templates
5. The VIM notifies the VNFM of the VM creation success.
DC ...
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Contents 1.
NFV Background
2.
NFV Ar Arch chit ite ectu cture re and Cha hara ract cte eri rist stic ics s
3.
NFV O&M Solution
4.
Automatic O&M
Page 12
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Contents 2.
NFV Ar Arch chit ite ectu cture re and Cha hara ract cte eri rist stic ics s 2. 2.1. 1. NFV NFV Archit ecture and and Characteristics Characteristics 2.2. Virtualization Basics 2.3. OpenStack Principles 2.4. Basics of Containers and Microservices
Page 13
Page 14
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Open Architecture and Compatibility
Co-deployment of multi -vendor devices
Extensive compatibility
S M I v
C P E v
E S M v
. . .
. . .
. . .
Open Lab
Live-network OSS/BSS
MANO F R C P v
Stable performance
Vendor A: NFVO
OSS
RESTful
Mainstream cloud OS Vendor B: VNFM
Ecosystem alliance pre-evaluation CORBA
Mainstream Hypervisor (EXSI)
EMS SOAP REST interpreter interpreter
Benchmark Benchmark VM design for the CSCF service processing module: Two VMs, each with four (C7000)
cores, 2.49 GHz dominant frequency, and 8 GB memory
TAS service module design:
COTS (Huawei supports 200+ vendors.)
VIM
VIM
Service module VM: 8core, 16 GB memory Forwarding module VM: 2-core, 4 GB memory
Page 15
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Virtualization Architecture VS. Cloud-based Architecture
Traditional devices
Virtualization
Cloud-based architecture
VNF (such as CSCF)
VNF view (such as CSCF) Service data layer (distributed memory database)
Service logic layer
Service logic and data are bound.
Service logic and data are bound.
VM
Session forwarding layer
Software-hardware decoupling
Software-hardware coupling
Software-hardware decoupling
Key capability differences •
•
Supports separation between between programs and data, and between forwarding layer and data layer. Supports horizontal expansion and distributed memory database.
Page 16
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Elastic Scaling
Elastic scale-out
Active DB
Standby DB
A
B
• •
Dynamic data includes subscription data, link office direction configuration data, and stable call session data.
C
... Stateless Distributed Service processing Real -time module with traffic N+M redundancy
Based on CPU load
Active DB
A
B
C
•
Elastic scale-in
Obtain dynamic data.
• •
Service distribution
Active
Real -time traffic
A
B
B
C
C ...
...
...
Standby DB
A
•
New module
Stateless Distributed Service processing module with N+M redundancy
Service distribution
Standby
Based on CPU load
...
Stable traffic can be reestablished in other modules immediately.
Real-time traffic
...
Real -time traffic
Real -time traffic
Service distribution
Service distribution
Active
Standby
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 17
High Availability r e y a l n o i t a c i l p p A
Redundancy mechanism 1: active/standby redundancy Service module
Service module
Redundancy mechanism 2: stateless N+M redundancy Service Service Service module module module
Ensures zero interruption of application layer sessions.
S O d u o l C
Redundancy mechanism: rapid VM rebuilding VM
99.999% availability
New VM
Ensures that resources are always available. r e y a l e r a w d r a H
Redundancy mechanism: cluster and material redundancy
Hardware, VM, and service-layer service-layer reliability are implemented implemented independently, ensuring availability of the entire system.
Page 18
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
New Mode Helps Cost Reduction and Revenue Growth
Top 3 Benefits of NFV Shortens TTM, reduces TCO, and promotes innovation
NFV network
Traditional network Service deployment is complex and time-consuming
Simplified deployment
Infrastructure Complex O&M
Co-deployment of multiple devices
Source: Infonetics (2014.3) SDN and NFV Strategies: Global Service Provider Survey
Closed
Unified management
Infrastructure Share
A platform for thirdparty developers
Flexible and fast deployment
Shorter TTM
Automatic OAM
Reduced TCO Unified hardware
Open
Accelerated innovation
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Contents 2. NFV Arc Archit hite ectur cture e and Cha hara racte cterist ristics ics 2.1. NFV Architecture and Characteristics 2.2. Virtualization Basics 2.3. OpenStack Principles 2.4. Basics of Containers and Microservices
Page 19
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 20
Definition of Hypervisor
A hypervisor is a sof softwa tware re la laye yer r be betw twee een n ph phys ysic ical al se serv rver ers s an and d OSs. OSs. It al allo lows ws mult multip iple le OSs OSs an and d ap appl plic icat atio ions ns to sh ha are th the e s ame ame s e ett of ph phy y si si ca cal ha hard rdw w are are..
It coordinates access to all physical devices and VMs on the server. It is also called a virtual machine monitor (VMM).
Th The e ba basi sic c func functi tion on of Hy Hype perv rvis isor or is to supp suppor ortt mult multii-wo work rklo load ad mi migr grat atio ion n wi with thou outt in inte terr rrup upti tion on..
When the server starts and runs the Hypervisor, the Hypervisor H ypervisor allocates appropriate memory, CPU, network, and disk resources to each VM and loads the guest OSs of all VMs.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 21
Hypervisor Working Principle
x8 x86 6 OSs OSs ar are e de desi sign gned ed to ru run n di dire rect ctly ly on bare bare hard hardwa ware re de devi vice ces. s. Comp Comput uter er ha hard rdwa ware re is to tota tall lly y de desi sign gned ed..
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).
Th The e OS (k (ker erne nel) l) re requ quir ires es di dire rect ct ac acce cess ss to ha hard rdwa ware re an and d memo memory ry,, an and d it its s co code de ru runs ns on Ring Ring 0.
The OS can use privileged instructions to control interrupts, modify page tables, access devices, and more.
Th The e code code of ap appl plic icat atio ions ns ru runs ns at Ri Ring ng 3 (l (lea east st priv privil ileg eged ed), ), an and d co cont ntro roll lled ed op oper erat atio ions ns ar are e not not al allo lowe wed. d.
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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 22
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 virtualization technologies has Huawei used to improve improve application performance?
Huawei CloudCore solution uses key compute compute performance optimization optimization technologies, such as resource iso lation, NUMA NUMA affinity, and CPU CPU pinnin g , to ensure the performance of service VMs.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 23
Background of Compute Virtualization (Cont.)
Compute virtualization can can be simply understoo understood d as allocating pCPUs to VMs in the form of virtual CPUs (vCPUs). How pCPUs are allocated and occu occupied pied determines the compute compute resource usage and perform performance ance of VMs. The following technologies are used during CPU allocation:
Resource Re source i solation: solation : 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: 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: 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 always run on the same same pCPU core, which means means VMs can use their dedicated pCPUs.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 24
Core Technologies of Compute Virtualization
Comp Co mput ute e virt virtua uali liza zati tion on ca can n be si simp mply ly un unde ders rsto tood od as al allo loca cati ting ng pC pCPU PUs s to VMs VMs in th the e fo form rm of vC vCPU PUs. s.
Resource Re source isolation: isolation: On eac each se serv rver er,, physi hysic cal CPU CPU co core res s fo forr the NFVI NFVI an and d ser erv vic ice e VMs VMs ar are e iso sollat ate ed fr fro om each ach other, oth er, avoidi avoiding ng CPU resour resource ce scr scramb ambles les..
vC vCPU PU pinning pinning:: vC vCPU PUs s of ea each ch VM are pin inne ned d wit ith h an and d excl exclu usi sive ve to pCPU pCPUs. s.
Page 25
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
NUMA Concept
Commercial servers can be classified into the following types based on the server CPU arch archite itectur cture: e:
Symmetric Symmetri c 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 CORE
CORE
CPU
CORE
MEM CORE
CORE
CPU
Memory Controller CORE
CORE
Memory Controller CORE
I/O
I/O
SYSTEM BUS Compute node
NUMA architecture
Page 26
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
NUMA Deployment Policy VM 2
VM 1 vCPU
vCPU
vMEM
vNIC
vCPU
vCPU
NUMA NODE 0
CORE
CPU CORE
vNIC
NUMA NODE 1 MEM
CORE
vMEM
CORE
Memory Controller
Memory Controller
CPU
CORE
MEM
CORE
CORE
CORE
I/O
I/O
SYSTEM BUS COMPUTING NODE
NUMA affinity
For a VM created using NUMA affinity rules, its vCPU and memory resources come from the same NUMA node of a compute node. This improves memory access performance. The performance gain is especially significant for applications entailing frequent memory accesses.
IO-NUMA
When IO-NUMA is used, virtual NICs of a VM come from the physical NIC of the same NUMA node to avoid using virtual NICs across NUMA nodes, thereby improving network I/O performance.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 27
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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 28
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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 29
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.
FusionStor Fusio nStorage age Block applies applies to:
Large-scale cloud computing data centers. FusionStorage FusionStora ge 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 infrastructure.. FusionStorage FusionStora ge Block employs InfiniBand (IB) for server interconnection interconnection and supports SSD cache and SSD main storage, which significant significantly ly improves the performance performance and reliability of storage systems while retaining the high scalabil scalability ity 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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 30
Software Architecture
Mo d u l e
Fu n c t i o n
FusionStorage Manager (FSM)
A management management process. Provides O&M O&M functions, functions, such as alarm reporting, monitoring monitoring,, loggin logging, g, and configuration. It is best practice to deploy two FSM nodes working in active/standby mode.
FusionStorage Agent (FSA)
A management management agent proc process. ess. It is deployed on each node (server) (server) to com communicate municate with the FS FSM M node.
MDC
A service service contr control ol process. process. Controls status of d distributed istributed clusters a and nd data d distribution istribution and recon reconstruction struction rules. MDC is deployed on three, five, or seven nodes to form a control cluster.
VBS
A service service input and output (I/O) process. Manages metadata and prov provides ides an a access ccess s service ervice that enables computing resources to connect to distributed storage resources. A VBS process is deployed on each server to form a VBS cluster.
OSD
A service service I/O pro process. cess. Perfo Performs rms spec specific ific I/O operations. operations. Multiple OSD proces processes ses can be deploye deployed d on ea each ch server and one disk requires an OSD process.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 31
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?
Page 32
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Overview of Key Network Virtualization Technologies Nam e OVS
Hardware passthrough
Co n c ep t Open Virtual Switch (OVS) is an open-source virtual switching solution, and is integrated into the KVM. Hardware passthroug Hardware passthrough h allow allows s a VM to directly directly access access a PCIe devic device e (for example, example, a NIC is a PCIe device). That is, a VM has direct access access to hardware registers registers and message queues. It is also called PCI pass-through. A NIC can be assigned for one VM or be virtualized to multiple virtual virtual NICs (SR-IOV) for use of one or more VMs. SR-IOV is supported only by certain NICs.
SR-IOV
SR-IOV is an extension of the PCI Express (PCIe) specification. It enables a PCIe adapter (such as a NIC) to function as multiple independent components (NICs) through a shared PCIe interface.
EVS
An elastic virtual switch switch (EVS) provides virtual networ network k switching functions, includi including ng VLAN, DHCP isolation, bandwidth limiting, and priority setting. This is a user-mode-based virtual switching solution developed by Huawei based on DPDK.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 33
Open vSwitch (OVS)
Op Open en vS vSwi witc tch h (OVS (OVS)) is a so soft ftwa ware re-b -bas ased ed open open-s -sou ourc rce e virt virtua uall Et Ethe hern rnet et sw swit itch ch (Eth (Ether erne nett br brid idge ge)) li lice cens nsed ed unde underr th the e Apac Apache he 2.0 lic licens ense. e.
The OV OVS S su sup pport ports s mul ulti tipl ple e st sta andard ard manage nagem ment int interfa erface ces s and pro rottoc oco ols, su such ch as Net NetFlo low w, sFlo sFlow w, SPAN, Re Rem mot ote e Sw Swit itch ched ed Po Port rt An Anal alyz yzer er (RSP (RSPAN AN), ), Co Comm mman and d Line Line Inte Interf rfac ace e (CLI (CLI), ), LACP LACP,, and and 802. 802.1a 1ag. g. It al also so su supp ppor orts ts di dist stri ribu buti tion on acro across ss multi multiple ple phy physic sical al ser server vers s sim simila ilarr to VM VMwa ware' re's s vN vNetw etwork ork distri distribut buted ed vsw vswitc itch h or Cisco' Cisco's s Nexus Nexus 1000V 1000V..
Th The e OVS sup suppor ports ts the Ope OpenFl nFlow ow pro protoc tocol ol and can be integr integrate ated d with with mu multi ltiple ple ope open-s n-sour ource ce vir virtua tualiz lizati ation on pla platfo tforms rms..
An OVS is used to transmit traffic between VMs and implement communication between VMs and external networks.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 34
Elastic Virtual Switch (EVS)
Huaw Hu awei ei EV EVS S us uses es th the e fo foll llow owin ing g te tech chno nolo logi gies es::
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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Differences Between OVS and EVS
Page 35
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 36
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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 37
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 simple PCIe function that can process only I/Os. Each 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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 38
Advantages and Disadvantages of SR-IOV
Advan Ad vantag tag es
Dis advant adv ant ages
Device sharing (multiple VMs share the physical port of an SR-IOV device)
This function depends on devices. Currently Currently,, only some devices support SR-IOV.
Close to native performance
VMs cannot be dynamically migrated because VMs 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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Contents 2. NFV Arc Archit hite ectur cture e and Cha hara racte cterist ristics ics 2.1. NFV Architecture and Characteristics 2.2. Virtualization Basics 2.3.. OpenStack Princ ipl es 2.3 2.4. Basics of Containers and Microservices
Page 39
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 40
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 OpenStack is a free and open-source proje project. ct.
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/
Page 41
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Why OpenStack Is Used? Huawei OpenStack OM
3rd DC Management
MANO/ BOSS
3rd Guest OS & Applications Applic ations
Open architecture •
• •
Northbound standard OpenStack APIs and various ecosystems No technical lock-in Apache license license us used, ed, allow allowing ing on-dem on-demand and com commercial mercial integration of applications
High scalability •
Heat Nova
FusionCompute Hypervisor
FusionStorage SDS
•
Neutron
FusionNetwork SDN
Cinder
3rd Huawei &3rd Huawei &3rd Hypervisor Network Storage
Easy to add new custom modules and services (such as a new hypervisor) Can be cascaded to build a large-scal large-scale e cloud platform
Powerful compatibility with cross-vendor devices •
Strong southbound access capability, co-deployable with multiple hypervisors (such as KVM, Xen, and VMware), storage devices, networks, and physical devices
Most popular, fast-growing cloud platform with numerous members •
•
Rapid response to fix bugs with a new version released every six months 300+ participated enterprises and 20,000+ developers
Page 42
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Logical Architecture of OpenStack Ser v i c e
Fu n c t i o n
Horizon
Portal : Horizon provides an easy-to-use web portal for managing OpenSta OpenStack ck services. Note: In FusionSphere OpenStack, FusionManager FusionManager provides this service.
Nova
Compute service: manages the life cycle of VM instances. OpenStack does not provide virtualization capabilities. Instead, it interacts with the hypervisor (such as KVM and Xen) to manage the virtual resources.
Neutron
Ne Network twork service: Neutron provides network virtualization technologies for cloud computing, network connection services for VMs, and other services, such as VPN and firewall.
Swift
Object-based Object-base d sto rage rage:: Swift mainly stores unstructured data of a large data volume, for example, image files.
Cinder
Block storage: Cinder provides running VM instances with stable data block storage services, for example, creating a volume, deleting a volume, and attaching or detaching a volume to or from an instance.
Keystone
Aut hent ic ati on : Keystone provides identity verification, service rules, and service token functions for other OpenStack services.
Glance
Image service: service: The image server discovers, registers, and retrieves VM images, but it does not store image files. Generally, images are stored in object-storage systems like the OpenStack Swift project. Generally,
Ceilometer
Monitoring : Ceilometer collects almost all events that occur inside the OpenStack system as a data basis for other related services, such as monitoring and billing.
Heat
Service orchestration : Heat provides a template-def template-defined ined mode for automatically deploying a cloud-based infrastructure and software environment running computing, storage, and network resources.
Ironic
Bare metal server (BMS) provisioning
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
What Is OpenStack (Cont.)
Page 43
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
VM Creation Procedure
Page 44
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Contents 2. NFV Arc Archit hite ectur cture e and Cha hara racte cterist ristics ics 2.1. NFV Architecture and Characteristics 2.2. Virtualization Basics 2.3. OpenStack Principles 2. 2.4. 4. Basics of Containers and Microservices
Page 45
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 47
Microservice
What Wh at is a mi micr cros oser ervi vice ce? ?
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.
Page 48
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Microservice Architecture vs. Monolithic Application Monolithic applications
Microservice a ap pplications
UI
Resource efficiency
UI Catalog Service
Business Logic
Data Access Layer
Account Service
DB
DB
Characteristics of the microservice architecture
•
Services are self-governed, selfcontained, and self-managed. Services are independently developed and platforms and languages can be selected separately. Services are running and upgraded
•
independently. Inter-service interfaces are
•
•
Recommendation Service
Customer Service
DB
DB
Core of the microservice architecture •
Decoupling software logic into microservices. An application is broken down into its core functions independent of each other.
Appropriate design design in a specific environment can maximize efficiency. If the environment changes, huge resources may be wasted.
Development and maintenance complexity Maintenance increases rapidly with software volume. efficiency Appropriate design design can simplify subscriber operations.
(1) Microservice-sp Microservice-specific ecific instantiation and scaling maximize resource efficiency. (2) Excessively fine granularities will increase basic overhead and cross-service communication overhead.
(1) A full-function team maintains microservices, improving development and O&M efficiency. 2) Too many details will increase management and maintenance costs.
Principles for defining microservices •
•
•
Independent life cycle Independent resource scaling Independent optional components
Agility
Weak. Agile release is not supported.
Excellent. Good decoupling significantly improves agility.
Performance
Excellent. Good performance is usually provided.
Medium. Excessive splitting increases the delay and degrades the performance.
contractual.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 49
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. 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.
Page 50
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
What Is a Container? Lightweight OS Virtualization VM
vs.
Container
Apps
Apps
Bins/Libs
Base Image(Bins/Libs)
Docker container engine Build
Ship
Run
Homogeneous OS with container Engine Guest OS (kernel)
Namespaces, Control groups •
Host OS with Hypervisor Engine
•
COTS Hardware
COTS Hard Hardwar ware e
Container is an OS kernel-based lightweight virtualization technology. technology. Containers provide higher resource utilization and faster startup speed
The image layering technology facilitates quick software development and deployment. Centralized warehouse facilitates software sharing and release.
Unified container engines and images make software deployment and sharing simple and efficient.
than VMs, but lower security isolation. Page 51
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Comparison Between Containers and VMs It em Design Concept
Co n t ai n er Application-oriented lightweight OS-level virtualization, providing an application Implementation Technology running environment
Using the hardware resource (I/O) directly
VM Resource-oriented system-level isolation Device-level virtualization, providing a system running environment Virtualized hardware resources, affecting the performance
Relying on hardware to facilitate high-performance Resource Dependency
Image Release
Microservice ecosystem Development Mode Performance Security
Adapting any with CP CPU Uhigh architecture, such as x8 x86, 6, ARM, andtoPPC perform performance ance Resource miniaturization for improving the resource efficiency MB-level layered mirroring Microservice bearers for Build-Ship-Run Abundant eco ecosystems systemsframework, (such as third-partymicroservice middleware, distributed tool system, and Docker Hub) DevOps CI/CD Deployment in milliseconds Slightly better in compute, network, and I/O virtualization
Shared kernel space. Security isolation needs to
virtualization. (KVM has a complete ecosystem only on x86 servers.) N/A About 10 GB-level layered mirroring N/A N/A N/A About 5 minutes for deployment —
Complete system isolation
be improved. Page 52
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Huawei Container Cluster Scheduling and Application Orchestration Solution Fus FusionS ionStag tage e (Pa (PaaS) aS) –
Application scheduling and resource management framework: Sets up Kubernetes-based enhanced automatic lifecycle management, including application modeling, modeling, orchestration deployment, resource scheduling, auto scaling, monitoring, and self -healing. Microservice operation and management framework: provides provides applications with a series of distribu distributed ted microservice management capabilities, such as automated application registration, discovery, governance, isolation, isolation, invoking, and analysis, to simplify the complexity of distributed systems. Application development pipeline pipeline framework: streamlines the automated C CI/CD I/CD process from encoding and code submission 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 Combined orchestration/de ployment Monitoring & self-healing
Auto scaling
Application scheduling & resource mgmt. framework Cross-cloud adaptation
ERP Service integration control Application resource scheduling
Code version management Continuous integration
Application development pipeline framework Compilation and packaging
Legacy applications
IDE
Virtualization applications
e-Banking...
CRM
Microservice running and governance governance framework
Cloud-based applications
E-commerce...
W eb
Email...
Cloud middleware services
Service route
Service discovery
Elastic load balance (ELB)
Distributed cache service (DCS)
Service registration
Service governance (isolation and fallbreak)
Distributed message service (DMS)
Cloud Service Catalog (CSC)
Service monitoring (call chain)
Service definition management
IaaS The development pipeline is open source, which is included in Huawei products
Some microservice components are open source.
and provided for customers fr ee of charge. Huawei can recommend qualified suppliers for customization, but Huawei does not provide customized services.
The FST 2.0 microservice framework provides POC capabilities, and was commercially used in Q1 of 2018.
Page 53
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
How NFV Introduces Containers? Container-based VNF Container platform
Container-based VNF Existing VNF
Container platform
VM
Existing VNF
Bare metal
IaaS VM-b as as e ed d Co nt nt a aii ne ner
Container-based VNF Container platform Pure Bare metal
VM
IaaS NFVI Ex tte en de ded B ar ee-Met al al Co nt nt ai ai ne ner
Pu re re B ar ar ee-Met a all Co nt nt ai ai ne ner
Sharing infrastructure with Sharing existing VNFs VNFs
Yes
Yes
No
Container platform decoupled from infrastructure
Yes. The NFVI shields hardware.
No. The container platform is integrated with the NFVI, and the NFVI is coupled with hardware.
No. The container platform manages hardware infrastructure.
Multiple-vendor integration
Yes. The NFVI provides multi-vendor integration capabilities, and different vendors can use their own container platforms.
No. Container platforms are still under quick development. Multi-vendor integration is difficult before container platforms are standardized.
Isolation of containe Isolation containers rs from multiple vendors
VMs are used to isolate containers. This enables security isolation between tenants more flexibly.
Physical machines are used to isolate containers, implementing isolation between tenants. This method is not as flexible as container isolation using VMs.
performance
Similar to VM perform ance
Similar to physical machines
Reliability
Container OS faults are within VMs, so other VMs are not affected.
Container OS faults are within bare-metal devices.
Resource management flexibility
VMs can be used to implement advanced functions, such as live migration of containers.
Advanced functions, such as live migration of containers, are unavailable.
integration before they are standardized. Use VM-based containers because bare-metal containers do not support multi-vendor integration Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 54
Impact of VMs and Containers on the NFV Model NFVO (Manages NS (Manages life cycle)
The CaaS laye layerr is added to the original NFV model and interfaces are added between the CaaS layer and VNFM. •
•
•
•
Orchestrates, deploys, and schedules containers. Provides CT enhancement capabilities capabiliti es for containers containers,, such as hugepage memory memory,, shared memory, DPDK, CPU pinning, and isolation. Supports container network capabilities, capabiliti es, SR-IOV+DPDK, and multiple network planes. Supports the IP SAN storage capability of VM-based containers.
Network functions virtualization orchestrator (NFVO): Orchestrates NSs and VNF software packages. Manages NS life cycles. Globally manages, authenticates, and authorizes NFVI resource requests. Manages policies on NS instances. Virtualized network function manager (VNFM):
VNF
Virtualized Network Function (e.g. CloudIMS/CloudEP CloudIMS/CloudEPC) C)
VNFM (Manages VNF (Manages life cycle)
CaaS
NFVI
Cloud OS (Hypervisor + Management Module)
Hardware
VIM (Provisions virtualized resources)
(Server /Storage/Networ /Storage/Network) k) MANO
Management and
Manages life cycles of between VNF instances. Provides coordination the NFVI and EMS. Functions as a VNF container resource management portal. Manages life cycles of container-based VNFs, including instantiation, uninstallation, auto scaling, and transparent transmission of upgrade requests. Monitors container alarms and KPIs.
Virtualized infrastructure manager (VIM): Controls and manages compute, storage, and network resources. Collects and reports infrastructure performance counters and events.
Orchestration Page 55
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Basic Concepts Introduced to 5GC Deployment VM
Micro Service
POD
POD
Container1
Container1
Container2
Container2
Container3
Container3
VM POD for Controller
VM POD for Executor
VM:
Container:
Relationships between VMs, containers,
Relationships between microservices,
1. guest Each VM an independent OS,has ensuring security
1. VMs. Containers act asthe lightweight They share OS
isolation. 2. Hardware resources are virtualized, affecting the performance.
kernel. Containers are less isolated than VMs. 2. No performance penalty penalty for bare metal containers. 3. Second-level Second-level instantiation, instantiation, and agile deployment. 4. Multiple containers can run in a VM.
and pods: 1. Pod is a resource management concept defined in K8s and is not a running entity. 2. Containers with a group of functions form a pod, and are deployed by pod. 3. A pod is deployed on a VM. 4. Containers within a pod cannot be deployed on different VMs.
pods, and VMs: 1. Microserv Microservice ice is a concept of logica logicall functions. 2. The logical functions of microservices microserv ices need to be carried by the VM or pod entities.
Page 56
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
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
VNF
N:1
VNFM
1:1
VDU
N:1 1:N N:1 VNFC
1:1
(Micro)Services
1:N
Pod 1:N
EMS
Container
VM
N:1
Host
CaaS
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Section Summary
This Th is pa part rt de desc scri ribe bes s the the fo foll llow owin ing g ke key y NF NFV V te tech chno nolo logi gies es::
Basic concepts of Hypervisor
Knowledge about compute, storage, and network virtualization
OpenStack concepts and functions
Basics of containers and microservices
Page 57
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Contents 1.
NFV Background
2. NF NFV V Ar Arch chit itec ectu ture re an and d Ch Char arac acte terris isti tics cs 3.
NFV O& M So l u t i o n
4.
Automatic O&M
Page 58
Page 59
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
NFV Routine Monitoring Solution NFV O&M Soluti on IES OSS
Monitoring
AutoHealing
Analysis 2
EMS Monito ring
CloudIMS
Analysis
AutoHealing
CloudEPC
CloudVAS
vCPU
vStorage
vSwitch
Server
Storage
Switch
VNFM
1 OpenSta ck AC
NFVI 1
Small closed-loop (single-vendor)
2
Large closed-loop (multi-vendor)
VIM
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 60
Concept of Large and Small Closed Loops Ty p e
Def i n i t i o n
In the layered delivery scenario of Telco Cloud, the IES is used to build unified Large closed-loop
Small closed-loop
O&M capabilities, which is called a large closed-loop. The large closed-loop solution provides cross-vendor crosslayer O&M capabilities and uses IES as the main O&M entry.
In the telecom cloud vertical delivery scenario, U2020 is used to build unified O&M capabilities, which is called the small closed-loop. U2020 implements implements unified O&M of the NFVI and VNFs. The EMS is used as the unified O&M center of the cloud core network.
Ch ar ac t er i s t i c s
Carriers divide NFVI resources and isolate different resource pools for different vendors. A vendor's vendor's EM EMS S is used to manage its VNFs, instead of monitoring NFVI resources and the vendor's EMS can provide association analysis between VNF and NFVI virtual resources (small closed loop, within the vendor). The IES provides cross-vendor cross-vendor,, cross-layer, and comprehensive O&M for NFVI (large closed-loop, implementing cross-vendor cross-vendor,, vertical, crosslayer, and cross-service domain O&M actions).
Carriers require that the EMS of the cloud core c ore network be responsible for O&M of both the cloud core VNFs and the NFVI. Carriers' BOSS can be integrated based on the existing EMS interconnection interfaces interfaces and the NFVI O&M information is carried over these interfaces.
of the cloud core network.
Page 61
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
NFV Large Closed-Loop Scenario IES
Service O&M
Carrier's OSS (Traditional O&M)
Vendor O&M
2
ICT-O
VNF alarms/performance/resources
Huawei Huaw ei U2020 or other EMS (Supporting multiple instances)
REST: managed alarms/performance/ resources SVNFM
Proprietary interface: alarms/performance/resources Fast fault reporting
VNF 1
VNF 2
ICT-A
Centralized O&M at the infrastructure layer
4
VNF 3
VNF 4
VNF alarms/performance/resources
SVNFM
3rd EMS (multiple instances)
3
Managed alarms/performance/resources
VNF 1
VNF 2
VNF 3
VNF 4
VIM
Virtual compute
Virtual storage
Server
Storage
Network VDC A
1 FS
AC(O) Device
VIM with O&M enhancement (eSight)
Virtual storage
Virtual network
Storage
Third-party hardware
1. eSig eSight ht is as tthe he lo local cal O& O&M M cent center er of telecom cloud to manage networks, physical devices, virtual resources, and nodes, and provides correlation analysis capabilities, capabilities, a unified NFVI O&M GUI and O&M service interfaces (the interfaces allow access of third-party hardware). 2. EMS is the O O&M &M cen center ter fo forr ven vendor dor devices, providing O&M services to managed VNFs, including correlation analysis, monitoring, and assurance of VNFs and infrastructure-layer infrastructure -layer resources. 3. VNFM on only ly obt obtains ains N NFVI FVI mon monitor itoring ing data of its managed VNFs. 4. IES prov provides ides s servi ervice ce moni monitori toring, ng, log management, unified device O&M, and NFVI O&M, implements crossvendor, cross-layer correlation analysis, fault demarcation, and fault locating.
NFVI n
NFVI 1
VDC B
REST: alarms/performance/resources
Local O&M at the NFVI
Portal
Page 62
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
NFV Small Closed-Loop Scenario Carrier's OSS
5
Implements SSO between U2020 and eSight to realize centraliz centralized ed monitoring.
VNF and NFVI alarms/performance/resources
Vendor O&M REST: managed alarms/performance/re sources
2
Huawei U2020-CN (single-instance)
LCM
Proprietary interface: alarms/performance/resource alarms/performance/resources s Fast fault reporting
VNF 1
VNF 2
VNF 3
VNF 4
3 Managed
4
alarms/performance/resources
NFVI alarms/performa alarms/performance/ nce/ resources
VIM Vi r t u al c o m p u t e
1
Vi r t u al s t o r ag e
Virtual storage
VMware
Ser v er Network
NFVI
Enhanced O&M service (eSight)
St o r ag e AC
Device
Storage
Vi r t u al n et w o r k
REST: alarms/performa alarms/performance/resources nce/resources
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 63
Information Collection in the Large Closed-Loop Solution
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 64
U2020-CN Cross-Layer Monitoring Information Collection in the Small Closed-Loop Solution
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 66
Self-Healing in the NFV Large Closed-Loop Solution
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 67
Self-Healing in the NFV Small Closed-Loop Solution
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 68
Section Summary
This Th is pa part rt de desc scri ribe bes s the the co conc ncep epts ts re rela late ted d to la larg rge e clos closed ed-l -loo oop p an and d sm smal alll clos closed ed-l -loo oop p O& O&M. M.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Contents 1.
NFV Background
2. NF NFV V Ar Arch chit itec ectu ture re an and d Ch Char arac acte terris isti tics cs 3.
NFV O&M Solution
4.
A u t o m at i c O& M
Page 69
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 70
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 Management prior to O&M. Commercial O&M software and human-based O&M are recommended. recommended.
Internet enterprises: O&M is prior to management 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 rules you toand view the business statusservices more clearly the business more carefully. is to develop standards to enable to runand in acontrol standardized manner. Control refersManagement to batch execution. Instructions can be delivered and the controlled end can proactively provide feedback.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 71
Service O&M Model Service roles: technical positions, production management 1. Professional 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 Service objects: 1. Physical facilities: equipment room, air conditioner, and power supply 2. Infrastructure: hardware, network, and software App li cat io ion n sys tem: Various service systems
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 72
Servi Service ce O&M Model Model - Servic Service e Activities Activities (DMOA) (DMOA)
Deploy:: Installs and configures objects, updates patches, adds or deletes objects, and maintains Deploy 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 Operate operations, technical change, backup and restoration, and switchover in an HA or DR scenario. The operation result is status, attribute, or mode change.
Analy An alyze ze:: 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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 73
Functional Layers of O&M Automation
(1) Res Resourc ource-or e-orient iented ed aut automat omation ion (RO (ROA) A)
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) App Applic licatio ation-or n-orien iented ted auto automat mation ion (AO (AOA) A)
AOA integrates O&M automation automation functions for various resources in an appl application. ication. (such as OA capacity expansion and e-commerce platform capacity expansion, and gaming zone expansion)
AOA helps construct the comprehensive comprehensive O&M automation function based on the correlations between resources of the application.
(3) Bus Busines iness-or s-orien iented ted auto automat mation ion (BO (BOA) A)
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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Page 74
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.
Page 75
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Disadvantages of Traditional O&M Compared with Automatic O&M
Business Busin ess service service automation automation
Standa Sta ndard rd ser servic vice e proces process s
A standard enterprise service process is built based on the ITIL process and enterprise practices.
Traditional IT O&M:
O&M personnel rectify problems passively and manually.
There is a lack of an efficient IT O&M mechanism.
There is a lack of efficient IT O&M tools.
O&M personnel have to do some repetitive work.
Automatic O&M management
Automatic standard integration, integration, correlation mapping, user management, problem isolation and diagnosis, and business transaction management
Standardization, visualization, automation, intelligence, and digitization
Unified confi Unified configurat guration ion 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.
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Logical Architecture of Automatic O&M
Page 76
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Section Summary
This Th is pa part rt de desc scri ribe bes s co conc ncep epts ts re rela late ted d to au auto toma mati tic c O& O&M. M.
Page 77
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Summary
This Th is co cour urse se co cove vers rs th the e fo foll llow owin ing g co cont nten ents ts::
NFV NF V Infr Infrast astruc ructu ture re and Te Techn chnic ical al Fe Featu atures res
Key Ke y NFV NFV Tech Techno nolo logi gies es
Compute Compu te virtualizat virtualization ion
Storage Stora ge virtualizat virtualization ion
Network Netw ork virtualizat virtualization ion
OpenStack OpenS tack Principles Principles
Basi Ba sics cs of Cont Contai aine ners rs an and d Mi Micr cros oser ervi vice ces s
Conc Co ncep epts ts Re Rela late ted d to NF NFV V O& O&M M Ba Basi sics cs an and d Au Auto toma mati tic c O&M
Page 78
Copyright © Hua Huawei wei T Technolog echnolog ies Co., Ltd. All r ight s reserved.
Thank you www.huawei.com
Page 79
View more...
Comments
