U2020 virtualization solution overview (eular os, taishan)

1. U2020
Virtualization
Increasing
equipment usage
and reducing costs
Simplifying
engineering
deployment and
capacity expansion
Extending the
flexibility of service
deployment
Facilitating load
balancing
VMs
Physical hosts
Hardware: physical hosts, storage devices, and
switching devices
Virtualization software
Infrastructure layer
Virtualization layer
Virtualization software defines and divides IT resources, including
CPUs, memories, disks, network adapters, and application programs. It
dynamically allocates and schedules IT resources for VMs, increasing
the resource usage.
Server virtualization refers to the creation of multiple logical computers
(virtual machines or VMs) on a single computer (physical host). Multiple
VMs can run simultaneously on a physical host and run different
operating systems. Application programs on each VM run independently.
Server virtualization improves the working efficiency of the physical host.
App
OS
App
OS+DB
App
OS+DB
App
OS
Virtual resources: CPUs, memories, network
adapters, and disks
Product Version: V300R019C10
Issue: 01
Virtualization Solution Overview (EulerOS, TaiShan)
Virtualization Overview1

2. Virtualization software centrally manages storage
volumes, snapshots, and volume mirrors.
EMC IBM HP HW
Storage pool and LUN sharing
SAN
Storage virtualization refers to the addition of a virtualization layer between the
physical storage systems and the servers. All storage systems are managed at this layer.
Storage virtualization isolates the servers from storage hardware. Adding, deleting,
replacing, splitting, or combining storage hardware is imperceptible to the server side.
Virtual disk
Virtual disk
Virtual disk Virtual disk
Virtual disk
Network virtualization refers to the integration of various physical networks into a
virtual network based on server virtualization. Services are able to run on the virtual
network. The physical networks integrated include Ethernet, FC SAN, and IP SAN. The
virtual network detects and automatically adapts to VM changes, for example, migrating
or copying a VM.
Physical storage
Virtual storage
Physical host
VMs
Virtualservice
network1
Virtualservice
network2
Virtualmaintenance
network1
Virtualmaintenance
network2
Virtualdatanetwork
1
Virtualdatanetwork
2
Physical NICs
Network switching center
(Ethernet, FC SAN, and IP
SAN)
Virtual Network
Active Plane
Virtual Network
Standby Plane
Virtualservice
network1
Virtualservice
network2
Virtualmaintenance
network1
Virtualmaintenance
network2
Virtualdatanetwork
1
Virtualdatanetwork
2
Virtual NICs Virtual NICs
Network
virtualization
Physical networks
Customer's
network
SANVirtual Disk
Virtual Disk
Virtual Disk
Virtual Disk
Virtual Disk
Virtual storage
EMC IBM HP HW
Storage Pool LUN Sharing
Physical storage
Virtualization software centrally manages storage
volumes, snapshots, and volume mirrors.
If the storage device
changes, applications
on the physical host
are not interrupted.

3. Hot Migration of VMs
Enables:
System capacity expansion
without VM power-off
Load balancing between physical
hosts in a distributed system
Hardware maintenance without
VM power-off
Lossless upgrades
X
Encapsulation: Each VM is saved in
files. Users can move or copy VMs by
moving or copying the corresponding
files.
Independence: VMs are independent
from hardware and can run on servers
with required resources, without any
modification.
Subarea: Different subareas are
allocated to VMs so that these VMs can
run simultaneously on a physical host.
Isolation: The VMs running on a
physical host are isolated from
each other.
Physical hosts can function as standby hosts for one another. A physical host does not need
to be exclusively configured as a standby host.
Compared with traditional deployment solutions, the virtualization solution allows for an
increased usage of existing resources, as well as enabling the physical host to handle an
increased load.
When faulty hosts are recovered, the system migrates the VMs back in seconds using the
hot migration technology. This does not interrupt services because the client and NEs do not
detect the migration.
Compared with traditional HA technologies, the operating system (OS) needs to be restarted
in the HA. The HA increases the time needed for VM startup and switchover. The increased
time does not exceed 5 minutes.
Service failures on VMs cannot be rectified by using HA.
High Availability (HA)
If the system detects faults in one or
multiple physical hosts, it migrates
the VMs from faulty physical hosts to
normal physical hosts and restarts
the VMs.
Hot Migration of Storage
Eliminates the need of VM power-off
Supports optical fiber channels
Key Virtualization Technologies2
App
X
App
OS
App
OS
App
OS
App
OS
App
OS
App
OS
Normal running during hot migration

4. U2020 Virtualization Solution3
 FusionSphere: is a Huawei cloud OS.
 OSMU: is short for Virtual OSS Self-maintenance Unit. It centrally manages IP addresses,
routes, time, time zones, data backup, the life cycle of OSS VMs, and data restoration.
 U2020: is an NE management system.
 ES: refers to the virtual emergency system. It can be interconnected to only one U2020
virtual system. For details on the service solution, see U2020 Virtual Emergency System
User Guide (EulerOS, TaiShan).
 TS: refers to the virtual Trace Server system. It can be interconnected to only one U2020
virtual system. For details on the service solution, see U2020 Trace Server Virtual System
User Guide (EulerOS, TaiShan).
Architecture and Application Scenarios
Notes
Centralized VM O&M
The OSMU facilitates centralized VM operation and maintenance (O&M). Use the OSMU to
operate and maintain those VMs connected to the OSMU, as shown in the following figure.
Data center
including servers,
storage devices,
network devices,
and virtualization
software.
Hardware: physical hosts, storage devices, and switching
devices
Virtualization software: FusionSphere
Virtual resources: CPUs, memories, network adapters,
and disks
OSMU
OS
U2020
OS+DB
Pre-integration: is an end-to-end OSS virtualization solution in which the OSS or NE solutions
provides hardware, virtualization software, VMs, and service software.
ES
OS+DB
TS
OS
Network
Level-1
Scenario
Level-2 Scenario
Virtualization
Software
Hardware
VM Deployment
Mode
OSS Product
Wireless
network
Pre-
integration
Integration by
OSS's
FusionSphere Data
Center
FusionSphere
OpenStack
TaiShan Pre-installation
OSMU/U2020/
ES/TS/mAOS
Core
network
Pre-
installation
CloudCore pre-
installation
FusionSphere
OpenStack
TaiShan
Use the Swift
Deploy tool to
create the OSMU.
And then use the
OSMU to create
the other OSS
products VMs.
OSMU/U2020
CloudEdge pre-
installation
FusionSphere
OpenStack
TaiShan OSMU/U2020
Full
installation
CloudCore full
installation
FusionSphere
OpenStack
TaiShan
OSMU/U2020/
ES
CloudEdge full
installation
FusionSphere
OpenStack
TaiShan
OSMU/U2020/
ES

5. Data Type Data Description Backup Policy
OS data Data of the VM operating
system
A maximum of 3 backup files containing operating system data
can be saved by default.
Static data Binary codes of the
OSMU software, OSS
applications, database
software, and third-party
software
•A maximum of 5 backup files containing database applications
can be saved by default.
•A maximum of 5 backup files containing OSS applications can
be saved by default.
•A maximum of 3 backup files containing the OSMU management
system can be saved by default.
Dynamic data Dynamic configuration
files and data generated
when the OSS is running
A maximum of 7 backup files containing dynamic data can be
saved by default.
When the number of backup files stored in the system exceeds
the configured threshold, the oldest backup files will be deleted
automatically.
1 Network HA
HA Overview
2 VM HA
3 Data HA
Switches, NICs, virtual switches, and vNICs can be configured in 1+1 redundancy mode to achieve network full
redundancy, improving network reliability.
RAID and multi-path technologies can be used to improve storage reliability.
Backup and Restoration on the OSMU
OSMU
OS
U2020
OS+DB
ES
OS+DB
TS
OS
Network switching center (Ethernet, FC SAN, and IP SAN)
OS data
Static data
Dynamic data
OSMU
TS
ES
U2020
OSMU
TS
ES
U2020
OSMU
TS
ES
U2020
Backup of dynamic data is not required for the ES. The
ES temporarily takes over U2020 services. When the
U2020 is recovered, dynamic data can be obtained in
the automatic supplementary collection procedure.
Use backup
files to restore
the system to
any status it
was in when it
was backed up.
TS U2020
U2020
U2020
OSMU
OSMU
OSMU
TS U2020
U2020
U2020
OSMU
OSMU
OSMU
TS U2020
U2020
U2020
OSMU
OSMU
OSMU
Pre-integration:
backup in NFS
mode
By-integration:
backup in SFTP
mode
Data transmission
layer
Backup and restoration
instruction layer
TS
TS
TS
TS
TS
TS
Backup Storage
A. HA of key service unit deployment policies
Multiple FusionSphere control nodes are deployed to balance load. In normal cases, all nodes provide services
simultaneously. If a node is faulty, the services on this node are automatically shared by other nodes that are
running properly, and therefore services are not affected.
Two FusionSphere OpenStack OM VMs are deployed on different control nodes.
One standby service VM and one standby database VM are deployed in a U2020 system. If a service or database
VM becomes faulty, services on the faulty service or database VM can be automatically switched to the standby
service or database VM, respectively. After the switchover, the standby VM uses the IP address of the faulty VM.
The emergency system and primary system are deployed on different hardware in anti-affinity mode. The two
systems are completely isolated from each other to prevent their concurrent faults caused by a single-point
hardware failure. The emergency system data is stored on a local hard disk, and the primary system data is stored
on disk arrays.
The emergency system, standby for the primary one, does not implement HA. If emergency system hardware is
faulty, the emergency system cannot be migrated to other devices.
NOTE: The Core Network does not support the standby VM solution.
B. For details about HA and hot migration technologies, see Key Virtualization Technologies.
Copyright © Huawei Technologies Co., Ltd.