Fusion Compute

FusionCompute
V100R003C10
Product Description
www.huawei.com
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Understand the functions of FusionCompute in

FusionSphere
 Learn the architecture of FusionCompute
 Learn the key features of FusionCompute
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 2
Contents
1. FusionCompute Functions in FusionSphere
2. Customer Benefits
3. System Architecture
4. Features
5. Specifications
FusionCompute Functions in FusionSphere
As a virtualization component in the FusionSphere solution,
FusionCompute can virtualize resources and manage virtual resource
pools.
Contents
4. Features
5. Specifications
Improving Resource Utilization
Resource Sharing
Before After
 Before virtualization
virtualization virtualization 3%
 The server utilization is only 5% to
3% 10% 5% 60%
5% 10%.
VM 1
…  After virtualization
VM N  The consolidation rate of virtual
10%
servers is 1:5 to 1:10.
…
Server 1 Server 2 Server N Server
 The server utilization increases to
VM 2
more than 60%.
Time-Division
Sharing
Before After
virtualization virtualization 60% 10% Peak Trough
70% Time Time

60% 10% 10% 60% 70%
VM 1 VM 1
10% Wap gateway
60% 22:00 4:00
server
Server 1 Server 1 Server VM 2 Server VM 2
Server 2 Server 2 Multimedia
8:00 20:00
message server
Daytime Night Daytime Night
Promoting Reliability
1 2 3 4 5 1 2 3 4 5
X Planned
maintenance
Working domain (CPU: 25%) Working domain (CPU: 25%)
VM HA VM migration
1 2 3 4 5 1 2 3 4 5
X X
Working domain (CPU: 30%) Repair Working domain (CPU: 30%) Maintenance
If a node is faulty, its VM will be started on other nodes by In the planned maintenance for a node, its VMs are
the HA function. migrated to other nodes without affecting VM services.
App Real-time data App

App
synchronization
FusionCompute FusionCompute
X
Fault tolerance (Services
Server A are not interrupted.) Server A’
Supporting Dynamic Power Management
App App App App App App
FusionCompute FusionCompute FusionCompute FusionCompute
Application Scenarios
In the evening, when the service loads are light,
Features
resources on physical servers are not fully utilized so that
The system automatically powers on or off physical servers,
the VMs can be automatically merged and idle physical
thereby reducing the number of migrated VMs and ensuring
machines can be powered off.
that some physical servers are hibernated and can quickly
In the daytime, when service loads are heavy,
provide resources for new services.
resources on running physical servers become
insufficient so that power-off physical servers can
automatically power on to take over VMs on heavy-load
physical servers, which ensures QoS.
Contents
4. Features
5. Specifications
System Architecture
VRM: The Virtualization Resource Management (VRM) node is the management node of FusionCompute. It allocates and
schedules resources for FusionCompute and supports centralized operation and maintenance (O&M), resource monitoring,
and resource management.
VNA: The virtual node agent (VNA), deployed on the Computing Node Agent (CNA) node, virtualizes computing, storage,
and network resources.
VRM High Level Architecture

Presentation
WebUI
Service
Business API Binding

SOAP BPMBPM DRM REST API
Process Framework
Enterprise Service Bus (Mule)
Business
CRM BRM NRM NM PMS FMS LOG PMM
Service
Data
Data Access
Service
Connectivity Adapter for CNA

Adapter
Brokerfor
forCNA
VNA JDBC
Service
CNA Database
VNA
Computing Storage
DVS
Virtualization Virtualization
Module Functions
Acronym and Full Name Functions
Abbreviation
BPM Business Process Management Manages complex resource processing, such as VM creation.
Conducts distributed resource management based on specific
DRM Dynamic Resource Management
policies (energy saving or load balancing).
Computer Resource
CRM Manages virtual computing resources.
Management
Manages storage resources, such as IP SAN storage and local
BRM Block Resource Management
storage.
NRM Network Resource Management Manages network resources.
NM Node Management Manages virtual nodes, for example, powering on or off them.
Manages performance by collecting performance data and
Performance Management
PMS performing real-time performance analysis and after-the-event
Service
analysis.
FMS Fault Management Service Collects alarm and fault information and manages faults.
PMM Package Management Module Manages patches of computing nodes.

Controls the computing, storage, and network resources on
VNA Virtual Node Agent
virtual nodes.
DVS Distributed Virtual Switch N/A
WebUI Web User Interface Allows users to manage the system using APIs.
Application Programming
API Provides an interface for external communication.
Interface
JDBC Java Data Base Connectivity Connects to Java databases.
Contents
4. Features
5. Specifications
VM Live Migration
App App Features

App
 Based on the memory compression
technology, VM live migration efficiency is
doubled.
VM disks can be live migrated between
shared storage devices and local disks.
 VM live migration applies to the
services that can tolerate short
interruptions but must be recovered
quickly, for example, lightweight database
Server A Server B services and desktop cloud services.
VM live migration does not interrupt VM services and is transparent to users.
Flexible VM Configuration Adjustment
Features
vRAM can be added to a running or stopped VM,
VM Virtual resources pool and deleted from a stopped VM.
vCPUs can be added to a running or stopped VM,
APP and deleted from a stopped VM.

vNICs can be added to a running or stopped VM,
and deleted from a stopped VM.
Note: Not all OSs support hot add of vRAM and
vCPUs.
For those OSs that do not support hot add,
FusionCompute restarts the VM to make the added
resources take effect.
Benefits
FusionCompute
FusionCompute can flexibly adjust VM configuration based
on VM requirements.
Resources scale-up ensures the QoS of a single VM.
Resources scale-out ensures the QoS of a cluster.
CPUs, memory, and NICs can be flexibly adjusted for a VM based on service
requirements.
Dynamic Resource Scheduler
App App App App App App App App
Features Benefits
 Improves service performance.

 In a cluster, FusionCompute automatically migrates
 Prevents traffic congestion at peak hours.
VMs based on specified load balancing policies.
 Optimized load balancing algorithms prevent invalid VM
migration.
Dynamic Power Management
App App App App App App
Features Benefits
The system automatically powers on or off physical servers, In the evening, when the service loads are light, resources
thereby reducing the number of migrated VMs and ensuring on physical servers are not fully utilized so that the VMs
that some physical servers are hibernated and can quickly can be automatically merged and idle physical machines
provide resources for new services. can be powered off.
In the daytime, when service loads are heavy, resources
on running physical servers become insufficient so that
power-off physical servers can automatically power on to
take over VMs on heavy-load physical servers, which
ensures QoS.
VIMS File System
Features
Virtual Image Management System (VIMS),
a high-performance cluster file system, is the
Guest OS Guest OS Guest OS Guest OS
basic technology of advanced features, such
as thin provisioning, snapshots, and storage
migration.
FusionCompute The VIMS is compatible with

FusionCompute SAN devices, IP SAN devices,
NAS devices, and local disks.
The VIMS supports fixed, dynamic, and delta
VHDs.
VIMS
It is used for VMs that require advanced
storage features, such as the storage live
migration, snapshot, and linked cloning.
Constraints
Local disk If the VIMS is used, a computing cluster can
SAN device NAS device
contain a maximum of 32 hosts.
Provides better support for deploying cluster software on the

virtualization platform.
Storage Live Migration
Features
The migration bandwidth is controllable,
thereby preventing service interruptions.
Volumes can be migrated from one cluster
to another.
Maintenance of power-off storage systems
VM storage I/O performance optimization
 Efficient storage capacity management,
such as storage fragment reclamation
Storage live migration
Facilitates service deployment and ensures service continuity in

the event of storage system maintenance.
Thin Provisioning
Features
Only the configured capacity is visible to VM users.
However, the real disk capacity is dynamically
adjustment based on disk usage.
Thin provisioning supports storage space
reclamation.
Thin provisioning reduces the storage costs by
40%, depending on the application modules.
FusionCompute
Compared with traditional storage modes, thin
provisioning lowers the IOPS of a single VM.
Common type Thin provisioning applies to the scenarios that
Common disk Thin-provisioned
20 GB disk 80 GB provide large storage capacity and pose low
40 GB
requirements for IOPS.
40 GB
20 GB 20 GB
Physical Virtually allocated: 120 GB

storage Actually allocated: 80 GB
20GB
Physical space: 100 GB
100 GB
Significantly improves storage utilization and reduces storage

costs.
Linked Cloning
 Features
 Multiple linked clones share the same base
image and operating system (OS).
Upgrades and maintenance can be
VM VM VM VM
performed on these linked clones in a
unified manner by upgrading and
maintaining the base image.
 Each VM stores the delta data of the image.
 Linked cloning reduces the storage costs
by 60%.
 It takes only 12 seconds to create a single
linked clone.
 Application Scenarios
 Linked cloning applies to task-based
desktops, such as the cloud call center.
Delta
disk
Base image
Sufficiently increases management efficiency and reduces storage cost.
Distributed Virtual Switches
VM 1 VM 2 VM 3 VM 11 VM 12 VM 13
DVS 1 (Web)
DVS 2 (App)
Server A Server B
Features Benefits
Provides a portal for centralized management. Supports flexible network policy control.
Supports VLAN, layer 2 security policies, and bandwidth
control.
VXLAN
Decoupling logical networks Supporting a maximum of 16 million Supporting VM migration across layer 3
from physical networks. virtual networks. networks and capacity expansion.
LN 1 LN 2 LN 3
Logical
network
Network hypervisor
Physical
network
Benefits
1. Virtual networks do need to be configured on physical switches are therefore decoupled from physical networks.
2. The backbone network does not need to be reconstructed for supporting TRILL or due to MAC address insufficiency.
Existing devices in the backbone network can be reused.
3. A maximum of 16 million virtual networks are supported to meet multi-tenant requirements. (The current VLAN
technology supports only 4000 virtual networks.)
4. VMs can be migrated across layer 3 networks, which facilitates remote DR and backup that requires the VIS remote
active-active DR storage device.
Contents
4. Features
5. Specifications
Capacity Specifications
Category Specification Baseline Specifications Value
Maximum number of computing nodes supported by a

256
VRM
Maximum number of sites supported by a VRM 16
Maximum number of VMs supported by a single VRM 5120
Maximum number of running VMs supported by a server
117
System capacity (OA heavy load)
specifications GE network card:
512 (SAN storage/virtual
Maximum number of VMs supported by a single server storage)
256 (XVE/FusionStorage)
iNIC: 250
Virtual storage: 1024
Maximum number of volumes supported by a host
SAN storage: 2048
Maximum number of VCPUs on a VM 64
Maximum number of NICs on a VM 12
Maximum number of disks on a VM 60
VM specifications
Maximum capacity of memory on a VM 1 TB
Maximum capacity of user volumes on a VM (virtual
64 TB
storage)
Server Requirements
Item Requirement
Intel or AMD 64-bit CPUs
The CPU supports hardware virtualization technology, such as Intel VT-x or AMD-V, and the CPU virtualization
function is enabled.
CPU
It is recommended to use same type of CPU within one cluster of hosts. To add a host that uses different CPUs to the
cluster, enable the IMC mode.
≥8 GB
Memory For a host where the management VM is deployed, 3 GB of memory must be added to its existing memory.
The recommended memory size is greater than or equal to 48 GB.

≥16 GB
Hard disk
If local storage resources are used to create VRM VMs, the disk space should be greater than or equal to 96 GB.
The number of network ports is greater than or equal to 1.

Network
port The recommended number of network cards is 6. The recommended network card transmission rate is greater than
1000 Mbit/s.
Use RAID 1 that consists of hard disks 1 and 2 to install the OS and software on the host and create VRM VMs,
thereby enhancing host reliability.
The BIOS startup mode is set to startup from a hard disk in RAID1.
RAID
If a host contains multiple hard disks, it is recommended to combine all the other hard disks except hard disks 1 and 2
to form RAID 5.
The RAID configuration can be adjusted based on customer requirements.
Thank you
www.huawei.com

Fusion Compute

Uploaded by

Document Information

Original Title

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

Fusion Compute

Uploaded by

Copyright:

Available Formats

FusionCompute

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

 Understand the functions of FusionCompute in

 Learn the architecture of FusionCompute

 Learn the key features of FusionCompute

70% Time Time

App Real-time data App

App App App App App App

FusionCompute FusionCompute FusionCompute FusionCompute

VRM High Level Architecture

Business API Binding

Enterprise Service Bus (Mule)

Connectivity Adapter for CNA

PMM Package Management Module Manages patches of computing nodes.

App App Features

VM live migration does not interrupt VM services and is transparent to users.

APP and deleted from a stopped VM.

App App App App App App App App

FusionCompute FusionCompute FusionCompute FusionCompute

 Improves service performance.

 Optimized load balancing algorithms prevent invalid VM

App App App App App App

FusionCompute FusionCompute FusionCompute FusionCompute

FusionCompute The VIMS is compatible with

Provides better support for deploying cluster software on the

Storage live migration

Facilitates service deployment and ensures service continuity in

Physical Virtually allocated: 120 GB

Significantly improves storage utilization and reduces storage

Sufficiently increases management efficiency and reduces storage cost.

Maximum number of computing nodes supported by a

Intel or AMD 64-bit CPUs

The recommended memory size is greater than or equal to 48 GB.

The number of network ports is greater than or equal to 1.

The RAID configuration can be adjusted based on customer requirements.

You might also like