FusionSphere

V100R005C00
Quick User Guide
Issue: 01
Date: 2014-01-10

Introduction to FusionSphere
The FusionSphere solution consists of the FusionManager
cloud OS software FusionCompute and VM VM VM
cloud management software FusionManager. APP APP APP APP APP APP
FusionCompute is deployed on physical Guest OS Guest OS Guest OS
servers to virtualize the server hardware
CPU CPU CPU
resources, including CPUs, memory, and
network interface cards (NICs).
FusionManager schedules and manages Resource pool
computing, network, and storage resources
CPU CPU CPU
in the underlying resource pools in a
centralized manner. On FusionManager,
users can create VMs for tenants, allocate
resources for the VMs, and manage the FusionCompute
VMs based on the service requirements.
Virtualized Virtualized Virtualized
FusionSphere improves hardware resource Server Server Server
utilization, shortens the service launch period, 1 2 3
simplifies maintenance, and reduces the
maintenance costs.

Document Overview
This document illustrates how to quickly install and configure FusionSphere and provision services using
FusionSphere. For more details about FusionSphere, see the FusionSphere V100R005C00 Product
Documentation.

Contact Information
Official website: http://support.huawei.com/enterprise/
Documentation: http://support.huawei.com/enterprise/productsupport
Technical Forum: http://support.huawei.com/ecommunity/
Support Local offices: http://enterprise.huawei.com/cn/about/contact/all/index.htm
Service hotline: 400-822-9999
Email: [email protected]

Send us your thoughts, suggestions, or any other feedback using the technical
Feedback
support contact information listed above.

Copyright Huawei Technologies Co., Ltd. 2014.

All rights reserved.
1 Background
Resource utilization of traditional servers is mostly 5% to 25%, which swells a company's operating
expenditure with the increase of servers required by the growing services of the company. This is a
common problem challenging most companies nowadays.
Using virtualization technologies, FusionSphere enables one physical server to function as multiple or even
hundreds of isolated virtual servers providing the same functions as a traditional server. Besides,
FusionSphere is able to pool and dynamically manage the CPU, memory, disk, and NIC resources of these
virtual servers in a centralized manner, thereby improving resource utilization and helping companies
reduce hardware investment costs as well as operating expenditures.
Example Scenario
Company A has three departments: Business, Development, and Maintenance. Business Department is
responsible for product sales; Development Department is responsible for product development; and
Maintenance Department is responsible for after-sales services.
The company has an X6000 server and an IP SAN storage device deployed in the equipment room to
support services of all these three departments.

Business Dept

X6000 server Maintenance Dept

IP SAN

Development Dept

With the growth of services, the three departments apply for new servers to handle new services. The
server requirements of the three departments are as follows.

Department Server Requirements

One server to deploy a website system for showcasing products and handling
Business Dept
online orders. The server is required to be accessible to public network users.
One server to deploy databases
Development Dept
One server to serve as the file server
Maintenance Dept One server to serve as the file server

The Company A is facing the following problems:

Resource utilization of the existing servers is low, while purchasing new servers requires additional
capital investment.
Servers, storage devices, and switches cannot be managed in a centralized manner, resulting in slow
service response and low maintenance efficiency.
Therefore, Company A expects to optimize service deployment of its three departments by improving the
resource utilization of its existing servers.
FusionSphere is able to virtualize physical resources to enable a physical server to run multiple VMs that
carry different servers. This solution improves the server utilization and reduces the hardware investment
cost. Moreover, FusionSphere is able to manage both physical and virtual resources to improve the
company's maintenance efficiency and service response capability.
Next, we are going to show how to deploy FusionSphere on Company A's existing servers and use
FusionSphere to allocate resources and provision service VMs to the company's three core departments.

2
2 Preparations
2.1 Deployment Plan
1. Physical Device Networking

Company A's network devices include an aggregation switch and an access switch. Servers and the IP
SAN storage device are connected to the access switch over their network ports to allow data access to
the switch from the management, storage, and service planes of the devices.

Aggregation switch
192.168.210.132 Internet
VLAN 2000 VLAN 2004
Administrator

Access switch
eth0 (Management NIC 1) Controller A Storage links (4)
eth1 (Management NIC 2)
eth2 (Storage NIC 1)
Management
eth3 (Storage NIC 2)
eth4 (Service NIC 1) link
eth5 (Service NIC 2)
BMC
Management
link

Controller B Storage links (4)

IP SAN

Management BMC
Blade 1 Blade 2 plane
Service
Storage plane
X6000 server plane

Network
Configuration Information Remarks
Plane
The company's management plane network.
Management VLAN 2000 You can set the host IP addresses and management
plane Subnet: 192.168.210.0/24 node IP addresses in the FusionSphere system in the
management plane.
Server BMC plane, which communicates with the
VLAN 13 management plane.
BMC
Subnet: 192.168.13.0/24 X6000 blade 1 BMC IP address: 192.168.13.105
X6000 blade 2 BMC IP address: 192.168.13.106
Network segments, VLANs, and
The storage IP addresses on the four storage planes
subnet masks applicable to the
are:
storage planes:
Storage 172.20.100.100
172.20.0.0 VLAN 4 255.255.0.0
planes 172.30.100.100
172.30.0.0 VLAN 5 255.255.0.0
172.40.100.100
172.40.0.0 VLAN 6 255.255.0.0
172.50.100.100
172.50.0.0 VLAN 7 255.255.0.0
Subnet 192.168.214.0/24 under VLAN 2004 can
Service directly connect to the Internet.
2004~2019
planes VLANs 2011 to 2019 can be used for service
provisioning.

3
2. Installation Plan Description
Install FusionCompute virtualization software on the servers in the system so the servers become hosts
providing virtual resources in the FusionCompute hypervisor. Then, install the FusionSphere
management components, including Virtualization Resource Management (VRM), Virtual Service
Appliance Management (VSAM), and FusionManager on Host 1, as shown in the following figure.
VSAM management
VRM management IP address:
IP address: 192.168.210.50 FusionManager
192.168.210.30 management IP address:
192.168.210.60

Virtualization
software
FusionCompute

Host 1 Host 2

Management IP address
Management IP address (eth0): 192.168.210.22
(eth0): 192.168.210.21
Access switch

IP SAN
Aggregation switch

192.168.210.132

Component Description Data Plan

Host 1
Name: Host01
Management IP address:
192.168.210.21
Two blades in the X6000 server function as two hosts in
root user password: Admin@1234
Host the FusionCompute hypervisor after having the
Host 2
FusionCompute software installed.
Name: Host02
Management IP address:
192.168.210.22
root user password: Admin@1234
Management component in the FusionCompute
hypervisor.
VRM can be deployed in either standalone or
active/standby mode. In this example task, VRM is
deployed on only one host (Host01) in standalone mode,
and the VRM management IP address is configured to Management IP address:
the management plane IP address. 192.168.210.30
VRM
Notes: In active/standby mode, the management Subnet mask: 255.255.255.0
node is deployed on two physical servers or VMs. If Gateway: 192.168.210.1
the active node is faulty, the system rapidly switches
services to the standby node to ensure service
continuity. Therefore, the active/standby mode
provides high service reliability.

Cloud management component, which can be deployed

in either standalone or active/standby mode to manage
VM name: FM01
and maintain physical resources, virtual resources, and
Node name: FMN
services in a centralized manner.
Management IP address:
FusionManager In this example task, less than 200 VMs are required.
192.168.210.50
Therefore, only one FusionManager node is needed. It is
Subnet mask: 255.255.255.0
deployed on a VM on Host01, and its management IP
Gateway: 192.168.210.1
address is configured to the management plane IP
address.

4
Component Description Data Plan
The Virtual Service Appliance (VSA) management
component, which is deployed on a VM to
automatically configure and manage system service
VMs that provide software router, virtual load
VM name: VSAM01
balancer (VLB), and Dynamic Host Configuration
Node name: VSAM
Protocol (DHCP) functions.
VSAM Management IP address:
After VSAM is deployed in the system, users can
192.168.210.60
apply for software routers, bind a public IP address to
Subnet mask: 255.255.255.0
a VM, and configure access control list (ACL) rules to
Gateway: 192.168.210
improve network access security.
In this example task, VSAM is deployed on a single
VM on Host01, and its management IP address is
configured to a management plane IP address.
The host storage port names and
IP addresses for communicating
The storage device is connected to hosts through the with the storage devices:
Storage
switch storage plane network to provide virtualized StoragePort1 172.20.123.123
device
storage resources for the VMs running on the hosts. StoragePort2 172.30.123.123
StoragePort3 172.40.123.123
StoragePort4 172.50.123.123
Connect servers to the storage device to enable
Switch intercommunication among different planes in the N/A
FusionSphere system.

5
2.2 Service Deployment Plan
1. Add resources to FusionManager.
After installing FusionSphere, add the FusionCompute hypervisor to FusionManager, so that
FusionManager can manage clusters and hosts resources in the FusionCompute hypervisor and provide
virtualized resources for users.
The following figure shows the process of adding virtualized resources to FusionManager.

FusionManager

FusionManager
FusionCompute
Resource Resource
zone 1 zone 2
(zone)
Cluster 1 Cluster 2 Cluster 3

Create resource zones. Add Add the hypervisor.

resources.

zone FusionManager
AZ 1 AZ 2 zone
(az)

Resource Resource
cluster 1 cluster 2

Create AZs. Associate resource clusters

with resource zones.
1. Create resource zones in FusionManager.
A resource zone in the FusionManager system is a logical zone to manage all resources in an
independent layer 2 network in the system. All resources in the system must belong to one or multiple
resource zones.
2. Add the FusionCompute hypervisor to FusionManager.
Add the FusionCompute hypervisor to FusionManager to provide virtualized resources in the
FusionManager system. A hypervisor contains all the cluster resources managed by a set of VRM
system in FusionCompute.
3. Associate resource clusters with resource zones in FusionManager.
After adding the hypervisor to FusionManager, associate resource clusters in the hypervisor with the
resource zones in FusionManager, then the resources in the clusters can be automatically added to the
resource pools in the zones.
4. Create availability zones (AZs) in FusionManager.
An AZ is a collection of resources available to users in a resource zone. If a resource zone contains
multiple resource clusters, you can create multiple AZs to accommodate different resource clusters. An
AZ can contain one or multiple resource clusters. By selecting an AZ for a user, you can specify the
source of resources available to the user.
In this step, you need to plan data for the following objects.

Object Description Data Plan

Plan the following information for each resource zone:
Resource Name: identifies a resource zone. Name: zone
zone Location: identifies the location of the physical resources in Location: HT2
the resource zone.

Plan the names of the FusionCompute hypervisor and the Hypervisor name: FC
Hypervisor
VSAM node. VSAM name: VSAM

AZ Plan the names of the AZs to be created. AZ name: az

6
2. Configure resource pools and divide resources into VDCs.
After adding resources to FusionManager, resource pools in each resource zone have available virtual
resources. Then, the administrator can include resources in the resource pools into different virtual data
centers (VDCs) and allocate the resources to organizations by VDC.

Zone
AZ VDC01
Resource pools

VDC02
Computing Storage Network
resource pool resource pool resource pool

Resource VDC03
cluster

1. Configure resource pools.

Resource pools are classified into computing resource pools, storage resource pools, and network
resource pools. Resources in the resource pools are from the resource clusters virtualized by the
hypervisor.
Computing resource pool: contains virtual CPU and memory resources on the hosts in the resource
clusters.
Storage resource pool: contains data store resources in the resource clusters.
Network resource pool: contains distributed virtual switches created in the hypervisor. The virtual local
area networks (VLANs) used for creating service networks on FusionManager must also be added to
the network resource pool for creating external networks and the VSA management network.
2. Create VDCs.
VDC is the unit for using virtual resources in the resource pools. For example, to provide virtual
resources for three departments of a company, you can create a VDC for each department, with each
VDC containing isolated computing, storage, and network resources required for the VMs used by each
department.
In this step, you need to plan data for the following objects.
Object Description Data Plan
Plan the start VLAN ID and end VLAN ID for the service
VLAN pool name: VLAN_pool
networks.
VLAN pool Start VLAN ID: 2004
All VLANs must be allowed to pass through the service
End VLAN ID: 2019
plane ports on the switch.
Plan Company A's existing network that can connect to External network name:
the Internet as the external network, and add the external_network01
External external network to the company's network resource VLAN: 2004
network pool to provide IP addresses for the VMs to access Subnet IP address: 192.168.214.0
public networks. Subnet mask: 255.255.255.0
Gateway: 192.168. 214.1
The VSA management network assigns management
IP addresses for software routers. The configuration
VSA management network name: VSAnet
requirements are as follows:
VLAN: 2001
The VSA management network must be configured
VSA Subnet IP address: 192.168.214.0
on the aggregation switch to communicate with the
management Subnet mask: 255.255.255.0
network (VLAN 2000) of the management
network Available IP addresses:
components at layer 3.
192.168.211.101-192.168.211.150
The VLAN planned for the VSA management
Gateway: 192.168. 214.1
network cannot be added to FusionManager VLAN
pools.
VDC names:
Business Dept: VDC01
Plan an independent VDC each for the Business
Development Dept: VDC02
Department, Development Department, and
Maintenance Dept: VDC03
VDC Maintenance Department.
VDC quotas: 12 CPUs, 12 GB memory, and
Resources in each VDC are managed by the
300 GB storage for each department
administrator of the VDC respectively.
VDC administrator names: VDC01_admin;
VDC02_admin; VDC03_admin

7
3. Deploy services.
After creating VDCs, create a network in each VDC and provision VMs for users in the VDC. The following
figure uses the VDC (VDC01) for the Business Department as an example.
VDC01
VPC01
Routed
Router
VM01 network
External
VLAN 2016 network

Business Dept VlAN 2004

192.168.214.0/24
CPU

The VDC administrator can create a network and required VMs in the VDC based on the CPU, memory,
storage, and network resources allocated to the VDC.
In this step, you need to plan data for the following objects.

Object Description Data Plan

Plan a virtual private cloud (VPC) for creating secure service
VPC01 VPC name: VPC01
networks for the VDC.
Apply for a software router in VPC01.
A software router can be used to bind an elastic IP address to
Router a VM so the VM can connect to the public network. The router N/A
also supports the ACL function, which allows the system to use
ACL rules to control data packets to be sent to the VMs.
Routed network name:
Route_network01
Create a routed service network in VPC01. VLAN 2016
Routed Select a VLAN, for example, VLAN 2016, for the routed Subnet IP address:
network network from the service plane VLAN pool. The subnet IP 192.168.16.0
address can be specified by the VDC administrator as desired. Subnet mask: 255.255.255.0
Gateway: 192.168.16.1

Create a VM for deploying the website system in the routed

network.
VM VM name: VM001
The VM can be created using a VM template that has been
published on FusionManager.

8
2.3 Process Overview
Use FusionSphere to deploy services for the Business Department involves three phases: install
FusionSphere, add and configure resources, and create the network and VMs. The entire process is as
follows.

Install FusionSphere.
Install Install Configure the alarm
FusionCompute. Install VSAM.
FusionManager. reporting function.
Install the Install FusionManager Configure the function
FusionCompute software to manage physical Install VSAM to that allows
on hosts, deploy the VRM and virtual resources configure and manage FusionCompute and
component, and as well as services in software routers VSAM nodes to report
configure virtual storage a centralized manner. requested by tenants. alarms to
resoruces. FusionManager.

Add and configure resources.

Add resources to Configure Prepare template
Create a VDC.
FusionManager resource pools. resources.
Create resource zones Configure resource Create a VDC for
Import the VSA template
in FusionMananger pools containing tenants, configure the
required by the software
and add the required computing, allowed resource
router and the
hypervisor to it to storage, and network quota, and add VDC
application VM template
provide virtualized resources in the users.
to FusionManager.
resoruces. resource zone.

Create the required service network and VMs.

Create a VPC and
Provision VMs.
required network.
Create an isolated Use the imported VM
network for the VDC template to create VMs
and create the service and configure elastic IP
network required for addresses and ACL
provisioning rules for the VMs.
applications. System VDC
administrator administrator

9
2.4 Software Preparation
Obtain the following software files for installing FusionSphere.

Software Type Software Package How to Obtain

FusionCompute FusionCompute
host OS V100R005C00SPC100_CNA.iso Visit http://support.huawei.com and choose
Enterprise > Software > IT > FusionCloud
FusionCompute FusionCompute
> FusionSphere > FusionCompute >
installation wizard V100R005C00SPC100_Tools.zip
V100R005C00SPC100.
VRM VM template FusionCompute
file V100R005C00SPC100_VRM.zip

Visit http://support.huawei.com and choose

FusionManager FusionManager Enterprise > Software > IT > FusionCloud
installation file V100R005C00SPC200_SV.zip > FusionSphere > FusionManager >
V100R005C00SPC200.

Visit http://support.huawei.com and choose

VSAM VM template FusionCompute Enterprise > Software > IT > FusionCloud
file V100R005C00SPC100_VSAM.zip > FusionSphere > FusionCompute >
V100R005C00SPC100.

Obtain the following software files for provisioning services using FusionSphere.

Software Type Description How to Obtain

Used to install an OS on a VM.
This task uses the SUSE Linux
OS image file Provided by the customer.
Enterprise Server 11 OS as an
example.
Application software to be installed
on VMs, for example:
Application software MySQL Provided by the customer.
WinRAR
Apache
Visit http://support.huawei.com/enterprise,
choose Software > IT > FusionCloud >
FusionCompute
FusionSphere > FusionCompute >
Tools V100R005C00SPC100_GuestOS
V100R005C00SPC100 and download
Drivers.zip
FusionCompute
V100R005C00SPC100_GuestOSDrivers.zip.

Visit http://support.huawei.com/enterprise,
choose Software > IT > FusionCloud >
FusionCompute
VSA VM template FusionSphere > FusionCompute >
V100R005C00SPC100_VSA.zip
V100R005C00SPC100 and download
FusionCompute V100R005C00_VSA.zip.

10
Obtain the following tools before installing FusionSphere:

Tool Type Tool Name How to Obtain

Cross-platform remote access tool PuTTY http://www.putty.org

File decompression tool 7-Zip http://sparanoid.com/lab/7z/

Ensure that the local PC used for installing FusionSphere software meets the following requirements:

Item Requirement
Uses 32-bit CPUs with a minimum of 2 GB memory.
Hardware The system disk has a minimum of 1 GB free space, and one another service disk has a
minimum of 30 GB free space.
32-bit Windows XP or Windows 7
OS
Windows firewall is disabled.
The PC can communicate with the planned management plane and the host BMC plane
Network
properly.

In the following operation instruction slides, the left column provides the procedure, and the right
column provides the operation background, principle, and other related information. The following
table explains the icons used in the provisioning process. It is recommended that you familiarize yourself
with the icon descriptions before proceeding.

Icon Description

1 2 3 Operation sequence

Transition between different sections of

the web interface

Skip to step

Example:

Step 1: Click Resource.

Step 2: Click Resource Zones.

11
 NOTE: The screenshots in the steps below include sample parameter values, which may vary
from the actual parameter values onsite.

3 Install FusionCompute

3.1 Install an OS on the Host

Step 1: Mount an ISO file to the host.
1. Set the local PC to ensure that the PC can ping the host where
FusionCompute is to be installed.
Connect the PC and the host to the
Ensure that the IP address of the PC is in the same network
same switch.
segment as the host management IP address, and the PC IP
address can ping the host BMC system.
2. Open a web browser on the PC, then enter the BMC IP address First configure the first blade of the
into the address bar to access the host BMC system. X6000 server.
3. Log in to the BMC system using an administrator account.

Administrator root is used as an

example in this task.

4. Open the Remote Control window.

You may need to click Remote
Virtual Console (requiring JRE) on
the Remote Control page of some
Huawei server BMCs.

5. Mount an ISO image to the host. 3 Select FusionCompute

1 V100R005C00SPC100_CNA.iso.

4 4 When Connect turns to

2 Disconnect, the ISO file is mounted
3 to the host successfully,

Step 2: Upload the OS installation file.

1. Restart the host after the ISO file is mounted to it. Note
The host BIOS password may be
required during the restart. Obtain
1 the password in advance.
When the host begins to The default BIOS password for
restart, press F11 repeatedly Huawei RH-series rack servers, X-
3 2
until the screen for selecting series high-density servers, and
boot device is displayed. E6000 blade server is uniBIOS123.
The default BIOS password for
Huawei Tecal E9000 blade server is
Huawei12#$ or uniBIOS123.

12
Step 2: Start to install the OS on the host.
2. Set DVD-ROM as the boot device.
Note
The DVD-ROM name and the
configuration screen may vary
depending on the server used.

3. Select Install. The system begins automatic

data loading, which takes
about 2 minutes.

Step 3: Configure host information.

1. Select Network, then select a management plane port, for example, Tip
When configuring host data on
eth0. the configuration screen:
Press Tab or the up and
2 down arrow keys to move
1 the cursor.
Press Enter to expand or
execute the highlighted item.
Press the space bar to
toggle between options.

2. On the IP Configuration for eth0 screen, configure the IP address

and subnet mask for the management plane network port.
Note: The management
plane VLAN must be set to
the tagged type on the
switch port to which the
1 management network port is
connected.
2

Use the
number pad
3
on the
keyboard to
enter numbers.

3. On the Network Configuration screen, configure the management N/A

plane gateway.

13
Step 3: Configure host information.
4. Select Hostname, then set the host name. N/A

2
1
3

5. Select Timezone, then set the local time zone and time. N/A

1
3

6. Select Password, then set the password for user root. NOTE
Note: Exercise caution when entering the password to avoid incorrect intput. The password must contain
at least:
Eight characters
One space or one of the
following special characters:
2 `~!@#$%^&*()-_=
+\|[{}];:'",<.>/?
1 At least two of the following:
3 lowercase letters,
uppercase letters, and
numbers.

Step 4: Install the host OS.

1. Select OK in the bottom right corner of the screen, then select Yes in the displayed 2 Ensure that the OS is
dialog box to install the OS on the host. installed on the default disk
1 partition.
3 Confirm the configuration,
then select Yes to install the
OS.
The installation takes about
10 minutes.
2 After the installation is
3 complete, the host
automatically restarts.

2. Repeat the above procedure to install OSs on additional hosts. N/A

When the OS installation progress bar for a host is displayed, you can begin installing
an OS on the other host.

3. If the host running the VRM node is also planned to carry service VMs and the TIP
service VMs need to use Huawei storage area network (SAN) devices, use After installing the OS on
commands to switch the multipathing mode of the VRM host to Huawei multipathing Host01, you can immediately
start to install the VRM node
mode after installing the OS on the two hosts. on Host01. During VRM
You can also switch the multipathing mode for the non-VRM host on the installation, you can install
FusionCompute web client. the OS on the other host at
the same time.

14
3.2 Install VRM
Step 1: Decompress the software packages.
1. Decompress FusionCompute V100R005C00SPC100_Tools.zip onto
the PC to obtain the Installer, ModCNABFileTool, PlugIn, ToDPS, N/A
and HostInstaller folders.

2. Decompress FusionCompute_V100R005C00SPC100_VRM.zip into a

new folder to obtain two VRM VM template files whose file name N/A
extensions are .ovf and .vhd, respectively.

Step 2: Initialize the installation wizard.

The installation wizard is
opened.
Note
If an error is displayed
indicating that the .net
1. Run FusionComputeInstaller.exe in the Installer folder.
Framework program is not
installed, run
dotNetFx40_Full_x86_x64.e
xe in the PlugIn folder. Then
manually restart the local PC.
2. Select a language. N/A
3. Select an installation mode.

The system begins to install

1 system components, which
takes about 30 seconds.

The Configure Host page is

4. Click Next after the components are installed.
displayed.

Step 3: Configure the host.

1. Configure the host where the VRM VM is deployed, then click Next. 1 Enter the management IP
address you set during host
installation.
2 Enter the password (not
1 the host BMC password) you
set during host installation.
Note
If a message is displayed
2 indicating that the host is
unreachable, ensure that the
IP address set in 1 is
3
correct and can be pinged
from the local PC.

15
Step 4: Configure a data store.

1. Select Local disk/FC SAN, then click Next.

You are advised to use local
2. The storage devices are automatically refreshed, and the system disks to install VRM.
adds the storage device in the first row as the data store by default. A VRM node requires 80 GB
space on the local disk.
If local disks are used, the active
and standby VRM nodes use
different disks, which provide
higher reliability.
You are advised to select disks
that constitute RAID 1 to
enhance reliability.
The length of a RAID 1 disk is
generally twice as that of
common disks.
For details about VM storage
working principles, see
Appendix 2.

Step 5: Configure VRM VM information.

1. Configure VRM VM template information.

1 Select
FusionCompute_V100R005C0
1 0SPC100_VRM.ovf.

2. Set the VRM VM management IP address.

N/A

3. Set VRM VM specifications.

You can set the specifications
based on the deployment scale
or customize the specifications.
VM to the right of By
deployment scale indicates the
number of VMs required. PM
refers to the number of hosts
deployed.

4. Click Verify Configuration and click Next after the verification

N/A
succeeds.

16
Step 6: Configure the rights management mode.

1. Select a rights management mode as instructed.

N/A

Step 10: Install the VRM VM.

The installation takes about 50
1. Click Next to start installing the VRM VM.
minutes.
2. After the installation is complete, click the link on the displayed page
and log in to FusionCompute.
Common mode Enter http://VRM
1 management IP address in
the address bar of the browser,
and enter the username and
password to log in to
2 FusionCompute.
The default username and
Enter the username and password to log in to password are shown in the
FusionCompute.
figure on the left.

3. Click Finish to finish the VRM VM installation.

17
3.3 Configure FusionCompute
3.3.1 Log in to the FusionCompute Web Client.

To use Internet Explorer Step 1: Configure the Internet Explorer browser.

To use Mozilla Firefox Step 2: Configure the Mozilla Firefox browser.

Step 1: Configure the Internet Explorer browser.

1. Enter http://VRM floating IP address, for example, http://188.100.4.30/, in

Internet Explorer 9 is
the address bar of the browser, press Enter, and select Continue to this
recommended.
website (not recommended).

2. In the upper right corner of the browser, click Certificate Error, and click
View certificates in the dialog box displayed.
1
After the certificate is
installed, FusionCompute
will be recognized as a
secure site so users do not
need to install this
certificate again for
subsequent logins.

3. Click Install Certificate and click Next in the dialog box displayed.

4. Import the certificate to the system as the following figures instruct.

1
N/A
2

18
5. Click Finish, then click Yes in the dialog box displayed. A message is
displayed indicating that the import is successful. N/A

6. Click OK to close the certificate dialog box.

7. Hold down and press Shift+Ctrl+Delete.

8. Select the following options and click Delete to delete historical records. After the historical records
Preserve Favorites website data are deleted, restarting the
Temporary Internet files browser will make the
Cookies previous settings take
History effect.
9. Click Close to close Internet Explorer and open it again.
10. Go to Step 3: Log in to the FusionCompute Web Client. N/A

Step 2: Configure the Mozilla Firefox browser.

1. Enter http://VRM floating IP address, for example, http://188.100.4.30/ , in

With this setting
the address bar of the browser, press Enter, and select Continue to this configured, the
website (not recommended). FusionCompute Web
Client login page can
2. Expand I Understand the Risks and click Add Exception. directly display when you
intent to log in to the client
3. Click Permanently store this exception in the dialog box displayed and the next time.
click Confirm Security Exception.

Step 3: Log in to the FusionCompute Web Client.

1.Enter http://VRM floating IP address in the address bar of the browser and
press Enter.
N/A
2. Enter the admin username and its password to log in to the Web Client.
The system asks you to change the initial password upon your first log in to
the system.

19
3.3.2 Add Hosts to the Cluster of Host01

Step 1: Add hosts.

Add all hosts other than the
1. On the FusionCompute web client, select Computing Pool. host running the VRM VM
to clusters.

2. Go to the Add Host page.

1 Right-click the cluster.

2
3 N/A

3. Set the host parameters, then click OK to complete the adding.

1
After you set the host BMC
information, you can power
on or off the host on
FusionCompute.
2

Step 2: Bind host management ports.

1. Go to the Bind Network Port page.

If ports eth0 and eth1 are
1 both common ports on the
2 4 management plane of the
host, bind them in
3
active/standby mode to
5 improve network reliability.
6

20
2. Locate the row that contains Mgnt_Aggr, then open the Add Network Mgnt_Aggr is a bound
Port dialog box. port automatically created
during host OS installation
that contains the
1 management port eth0
you configured. Select
2 another management port
eth1 and bind it to eth0 as
Mgnt-Aggr to improve
network reliability.
3. Select the port name for eth1 to bind it to the management plane network
port PORTX in the displayed port list represents the network port ethx on
the host.

N/A

4. Click OK on the Bind Network Port page.

5. Bind eth0 and eth1 on the other host. For details, see 1 to 4.

21
3.3.3 Add Storage Resources to a Site (SAN Storage)

1. Open the Add Storage Resource dialog box.

For details about network

communication between
2
hosts and storage devices,
see Appendix 3.

2. Set the storage resource type to IP SAN, then click Next.

3 The management IP
3. Set the storage device parameters, then click Add. address specifies the
storage device.
1
2 4 5 An IP storage
3 area network (SAN) device
4
connects to a host through
multiple storage links.
5
Enter the information for all
links at one time.

4. Click Next. N/A

5. Select the host to be connected to, then click Next.

6. Obtain the generated world wide name (WWN), then click Finish.

22
3.3.4 Add a Data Store to the Host (SAN Storage)
Step 1: Change the host multipathing mode.

1. Go to the Getting Started page of the host.

The default multipathing
mode for FusionCompute is
1 Universal. If a Huawei IP
SAN device is deployed,
change the mode to Huawei
to improve storage
2 performance. If non-Huawei
3 storage devices are
deployed, skip this step.
4

2. Open the Configure Storage Multipathing dialog box. N/A

3. Select Huawei.

Restart the host for the

settings to take effect. The
restart process takes about
1 3 minutes.
You can ping the IP address
of the host to check whether
the host has restarted. If the
host can be pinged, the host
has successfully restarted.
2

Step 2: Add storage ports to the host.

1. Go to the Add Storage Port page of the host.

If you changed the multipathing mode of the host, perform this step after the
host restarts.

After storage ports are

added to the host, the host
can communicate with the
1 IP SAN device.

23
2. Select the host storage plane network , then click Next. The page for connection
PORTX indicates the network port ethX on the host. configuration is displayed.
3. Set the storage port parameters, then click Next.

The page for information

conformation is displayed.
The IP address is used to
communicate with the
storage device. Set it to an
2 idle IP address on the
storage plane.
3

The Finish page is displayed,

4. Confirm the information, then click Add. indicating that the port has
been added to the host.
5. If multipathing mode is selected, click Continue and repeat 2 to 4 to add
multiple storage ports to the host. Click Close on the Finish page after all N/A
ports are added.

Step 3: Associate storage resources with the host.

1. Go to the Associate Storage Resource page of the host.

1 After a storage device is

associated with a host, the
host can discover all storage
2 resources on the device.

The storage resource is

associated with the host.
2. Select the added storage resources, click Association, then click OK on After association, all
the displayed dialog box. associated storage
resources are displayed on
the Storage Resource page.

Step 4: Configure the initiator.

1. Choose Configuration > Storage Resource and record the host WWN
displayed in the bottom right corner of the page.
Storage devices identify a
host using the WWN of the
host.

24
2. Enter the storage device management IP address in the address bar of the
browser, then press Enter to load the storage device management software.
NOTE
The initiator can be
configured only on the
management interface of
the storage device.

The storage device

3. Select a language, then click OK. management software is
open.
4. Click Discover Device. N /A
5. Enter the administrator username and password to scan the storage
device.

2 Enter the management

IP address of the storage
device.
2

6. Enter logical host view, then click Initiator Configuration.

1
2 6
5 Select the logical host
that matches the logical
unit number (LUN). The
selected host in the figure
3 is only an example.
5
4

25
7. Add the host WWN to the initiator.
1

2 Select the host WWN

you have recorded.

Step 5: Add a data store.

1. Switch to FusionCompute and scan storage devices available to the host.
A data store is used to
1 create user disks on VMs.
You can view the task
2 progress on the Task
Tracing page.

2. After the scan is complete, go to the Add Data Store page of the host.

2 N/A

3. Select a SAN device and add it to the host as a data store. 2 A virtualized SAN
storage device supports
advanced storage features,
such as thin provisioning,
1 snapshots, and live
storage migration, and
provides high resource
utilization. However, disk
creation on it is slow.
If you set this parameter to
Virtualization, you can
select whether to format
2 the data store. When a
data store is added to the
host the first time, the data
3 store must be formatted.

26
3.3.5 Add Virtual Network Resources to the Site
ISO
NOTE: If the service plane and the management plane are deployed on the same network plane, no service plane
distributed virtual switch (DVS) is required. Instead, you only need to add a service plane VLAN pool to the
management plane DVS.

Step 1: Create a DVS.

1. Go to the Create DVS page. Create a DVS that connects to
the service plane to provide
network resources for user VMs.
1
A DVS named
ManagementDVS for the
management plane has been
automatically created during
VRM installation, the bound
network port Mgnt_Aggr has
been added to the uplink group
on the DVS, and a
management plane port group
2 managePortgroup has been
created.
For details about VM network
access, see Appendix 1.

2. Set the DVS name, then check the boxes next to Add uplink and
Add VLAN pool.

1
2

N/A
3
4

3. Select a service port for each host on the Add uplink page.

An uplink is a physical port on a

1 host that connects to a DVS.
VMs connect to the network
through the physical ports on
the host.
Add all the hosts in a cluster to
the same uplink group on a
2 DVS. This allows VMs in the
cluster to have the most
migration options if a fault
occurs.

4. Click Next.
N/A
5. Click Add.

27
6. Set a VLAN pool on the DVS.
A VLAN pool defines the allowed
VLAN range for a DVS.
During service provisioning,
create port groups on the DVS for
1 each service. This allows each
port group to use VLANs from
2 different VLAN pools.
The VLAN pool set on the DVS
must be the same as the VLANs
set on the physical switch to which
3 the host connects.

7. Click Next.
N/A
8. Click Create.

28
3.3.6 Configure the NTP Clock Source and Time Zone

Step 1: Configure the Network Time Protocol (NTP) clock source.

1. On FusionCompute, click System. After an NTP clock source is
set, the time on all nodes in
2. Choose System Configuration > Time Management. the system is the same.
If multiple NTP servers are to
3. Set the NTP server information. be deployed, ensure that all
the NTP servers use the
same upper-layer clock
1 source to ensure time
consistency.
This configuration requires a
restart of the FusionCompute
service process, which
2 interrupts services for about 2
minutes. After the restart, log
in to FusionCompute and
continue to the next step.
For details about time
3
synchronization, see
Appendix 4.

Step 2: Configure the time zone.

1. On the System page, choose System Configuration > Time Zone.

2. Configure the time zone settings.

1 2 N/A

29
4 Install FusionManager

4.1 Install FusionManager Using a Template

Step 1: Decompress the FusionManager installation package.

Ensure that the folder
1. Create a folder named share on the local PC.
space is greater than 10 GB.

2.Use 7-Zip to decompress the FusionManager

V100R005C00SPC200_SV.zip file.
The FusionManager V100R005C00SPC200_SV.7z file is obtained.
N/A
3. Use 7-Zip to decompress the FusionManager V100R005C00_SV.7z file.
The following files are obtained:
FusionManager V100R005C00SPC200_SV.ovf

FusionManager V100R005C00SPC200_SV-xvda.vhd

The shared folder path

4.Move the two files to the share folder, and share the folder with the
cannot contain Chinese
current login user of the local PC.
characters.

Step 2: Create a FusionManager VM on FusionCompute.

1. On FusionCompute, click VM and Template.

2. Click Import VM. N/A

3. Select Shared directory, then click Next.

4. Configure template information.

2 The path format is

\\Local PC IP
2
address\Name of the
folder containing the
template file.

3 If the user account is

registered in multiple
domains, enter the
3 username with the
specified domain name,
for example,
CHINA\w00123456.

5. Set the creation location to Host.

30
Step 2: Create a FusionManager VM on FusionCompute.

6. Click Bind to the selected host and select Permanently reserve

resources for the VM.

7. Bind the FusionManager NIC to the DVS port group of the

management plane.

8. Configure the data store and configuration mode (Common or

Thick provisioning lazy zeroed) for the disk, and select N/A
Persistency.
The options Persistent and Nonpersistent are available for a VM
disk only when the disk type is set to Common and the data store type
is set to Local Pome, LUN Pome, or NAS. For such disks, set
Persistency to Persistent. For disks using other types of storage
resources, the Persistency attribute can only be Persistent, which is
the default setting and not available for selection.

9. Configure VM information.

3 This parameter is available if

1 the cluster has the GuestNUMA
function enabled. The CPUs of a
VM can be divided into multiple
groups. The one or multiple CPU
cores in each group are provided
by one or multiple cores of a
2 physical CPU. The number of
CPU cores in each group
3
determines the number of CPU
4 cores allowed in a socket. The
5 number of sockets and the
number of CPU cores allowed in
a socket vary depending on the
OS capabilities. Set this
parameter based on the actual
capability of the in-use OS. The
VM CPUs are recommended to
be evenly provided by the
physical CPU.

5 In the CPU Resource

Control area, move the
Reserved (MHz) slider to the
maximum value. In the Memory
Resource Control area, move
the Reserved (MB) slider to the
required value.

10. Keep the default values of other parameters, then click Next.

N/A
11. Click Create.
The creation process takes about 40 minutes.

31
4.2 Configure FusionManager

1: Configure the FusionManager VM.

1. On FusionCompute, log in to the FusionManager VM using VNC.

The login username is galaxmanager, and the default password is
Huawei@CLOUD8.

2. Run the following command to disable user logout upon system timeout:
TMOUT=0 N/A

3. Run the following command to start the configuration wizard:

fmconfig

4. Select OK to enter the configuration wizard.

5. Select Next to enter the page for selecting the deployment mode.

6. Select Single mode.

N/A

7. Select Next.

8. Configure FusionManager VM information.

1
2
3
4 N/A

If the entered
configuration information
9. Confirm that the configuration information is correct, then select Next. is incorrect, run stopALL
The system begins to configure the FusionManager VM. The configuration is to stop the process and
successful when the progress reaches 100% and the system displays a perform the configuration
success message. procedure again from
running the fmconfig
command.

32
4.3 Configure Time Synchronization and Time Zone

Step 1: Log in to the FusionManager web client.

1. Enter the FusionManager management IP address in the address box,
then press Enter.
The address format is http://FusionManager management node IP address, Internet Explorer 9 is
for example, http://192.168.210.60. recommended.
2. If no security certificate has been installed, click Continue to this website
(not recommended).
3. Enter the username and password.
Default username: admin
4. Enter the displayed verification code.
Default password:
5. Click Login. Huawei@CLOUD8!
If the system displays a message indicating that the login password must be
changed upon the first login or be reset, change the password as prompted.

Step 2: Configure the time zone.

1. On FusionManager, select System.

2. Choose System Configuration > Time Management.

3. In the Time Zone area in the lower part of the page, check whether the
current time zone is the same as the local time zone. If different, change the
system time zone to the local time zone.
N/A

Step 3: Configure the time server.

1. Configure the time synchronization function.

33
5 Install the VSAM VM

Step 1: Decompress the VSAM installation package.

1. Decompress the FusionCompute V100R005C00SPC100_VSAM.zip file.
The following files are obtained:
FusionCompute_V100R005C00SPC100_VSAM.ovf

FusionCompute_V100R005C00SPC100_VSAM-1.vhd N/A

2. Create a folder named share, move the two files into the folder, and share
the folder with the current login user of the local PC.

Step 2: Create the VSAM VM on FusionCompute.

1. On FusionCompute, select VM and Template.

2. Click Import VM. N/A

3. Select Shared directory, then click Next.

4. Configure template information.

1
2 The path format is
\\Local PC IP
address\Name of the
2 folder containing the
template file.

3 If the user account is

registered in multiple
domains, enter the
username with the
3
specified domain name,
for example,
CHINA\w00123456.

5. Set the creation location to Host.

6. Click Bind to the selected host and select Permanently reserve resources for the
VM.

7. Configure the FusionManager NIC information on the management plane

DVS and port group.

8. Configure the data store and configuration mode (Common or Thick N/A
provisioning lazy zeroed) for the disk, and select Persistency.
The options Persistent and Nonpersistent are available for a VM disk only
when the disk type is set to Common and the data store type is set to Local
Pome, LUN Pome, or NAS. For such disks, set Persistency to Persistent.
For disks using other types of storage resources, the Persistency attribute
can only be Persistent, which is the default setting and not available for
selection.

34
9. Configure VM information.

3 In the CPU Resource

Control area, move the
2 Reserved (MHz) slider to
the maximum value.

4 In the Memory
Resource Control area,
3 move the Reserved (MB)
slider to the required value.

10. Keep the default values of other parameters, select Customize using
the Customization Wizard, then click Next.
N/A
11. Enter the VSAM VM name, leave Save as computer attributes
unchecked, and click Next.

12. Configure VSAM VM NIC information.

N/A

13. Click Next.

14. Confirm that the entered information is correct, then click Create. N/A

The creation process takes about 20 minutes.

35
Step 3: Configure the NTP server and time zone.
1. On FusionCompute, log in to the VSAM VM as user root using VNC.
The default root user password is Huawei@CLOUD8!.
2. Run the following command to disable user logout upon system timeout:
TMOUT=0
3. Run the following command to enter the configuration interface: N/A
python /opt/galax/vsam/tomcat/script/configvsam/ConfigVSAM.py
The following information is displayed:
START TO CONFIG VSAM !
please input the user gesysman's password[q/Q]:
Password:

4. Enter the gesysman user password, which is GeEnginE@123 by default.

The following information is displayed:
**************************************
* please choose your operation: *
* SET HA : 0 *
* SET NTP : 1 *
* SET FTP : 2 *
* SET Time Zone : 3 *
* SHOW ALL : 4 *
* SHOW HA : 5 *
N/A
* SHOW NTP : 6 *
* SHOW FTP : 7 *
* SHOW Time Zone : 8 *
* EXIT : 9 *
**************************************

please input your choice[0~9]:

5. Enter 1, then press Enter.

6. Enter the NTP server IP address, then press Enter.

start to config ntp ! Configure the NTP clock
please input the ntp ip address: source preferentially to the
same external clock
7. Press Enter, set the synchronization interval (default: 64s), then press source used by both
Enter. FusionCompute and
8. Enable forcible clock synchronization (which is disabled by default), then FusionManager. If no
press Enter. external NTP clock source
is available, configure the
9. Configure the NTP network bridge address (which is not configured by clock source to the host
default), then press Enter. running the active VSAM
VM.
10. Confirm that the entered information is correct, then press Enter.
The system begins to configure the NTP server.
11. Enter 3 and press Enter to configure the time zone.

start to config time zone info !

please input the time zone info [example:Asia/Hong_Kong]:
For more information about time zone, please refer to the following
directory :/usr/share/zoneinfo N/A

12. Enter the time zone, then press Enter.

13. Confirm that the entered information is correct, then press Enter.

36
6 Configure the Alarm Reporting Function
After installing FusionCompute, FusionManager, and VSAM, configure the function that allows
FusionCompute and VSAM to report alarms to FusionManager.
Step 1: Log in to FusionCompute.
1. Enter http://VRM IP address, for example, http://192.168.210.30, in the address box,
then press Enter. Internet Explorer
9 is
2. Enter the username and password and set the user type and login type. recommended.
3. Click Login.

Step 2: Configure the FusionCompute alarm reporting function.

1. On FusionManager, select System.

N/A
2. Choose Connect To > FusionManager.

3. Configure the alarm reporting function.

1
2 Set it to the
2 FusionManager
management IP
address if only
one
FusionManager
VM is deployed.
3

Note: Before configure the alarm reporting function, enable port 18080 to allow VSAM to report alarms
to FusionManager. However, port 18080 is based on the insecure protocol HTTP. Therefore exercise
caution when deciding to enable this port.

Step 3: Configure the VSAM alarm reporting function.

1. On FusionCompute, log in to the VSAM VM as user root using VNC.
The default root user password is Huawei@CLOUD8!.

2. Run the following command to disable user logout upon system timeout:
TMOUT=0
3. Run the following command to query whether port 18080 is disabled. N/A
iptables -S|grep 18080
If the following command output is displayed, the port is enabled. Go to Step 5.
-A VSAM_INPUT_CONTROL -p tcp -m multiport --dports 18080 -j ACCEPT

If no command output is displayed, the port is disabled. Go to Step 4.

4. Run the following command to enable port 18080:
sh /opt/galax/vsam/tomcat/script/setVsamHttpPort.sh open
If the following command output is displayed, the port is successfully enabled: N/A
modify config file success

5. Run the following command to configure the function that allows VSAM to report
alarms to FusionManager in real time:
sh /opt/galax/vrm/om/fms/bin/modGMIp.sh FusionManager management IP address
N/A
The configuration is successful if the following information is displayed:
modify GM IP Success.........

37
7 Add Resources to FusionManager

7.1 Create resource zones.

A resource zone is a logical container of resources virtualized in the hypervisor. Resources in a resource
zone belong to an independent layer 2 network and are managed as resource pools, including computing
resource pool, storage resource pool, and storage resource pools.

Step 1: Log in to the FusionManager .Web Client.

1. In the address bar of Internet Explorer, enter http://FusionManager
management IP address, press Enter, then select Continue to this This task uses Internet
website (not recommended) to switch to the FusionManager Web Client Explorer 9.0 as an
login page. example.
For example, enter http://192.168.210.60.
2. Log in to FusionManager as user admin.
The default password of user admin is Huawei@CLOUD8!.
N/A
After logging in to FusionManager for the first time, you need to change
the login password as requested.

Step 2: Create a resource zone.

1. On FusionManager, go to the Resource Zones page.

N/A
2

2. Click Create on the displayed page.

3. Configure zone information.

1
3 In this task, a
2 software VSA node
functions as the gateway
3 of the service network,
and no physical
networking is required.
Therefore, use the default
physical networking mode.

38
7.2 Add the Hypervisor to FusionManager
Add FusionCompute and VSAM to FusionManager so FusionManager can manage resources in the
hypervisor.

Step 1: Add the hypervisor to FusionManager.

1. Switch to the Hypervisor page.

2 -

2. Click Add on the hypervisor page.

3. Configure the hypervisor access information.

1
5 If only one VRM node
2 is deployed, enter the
VRM management IP
3 address and the default
port number 7443.
4
6 Enter the name for
connecting the hypervisor
to FusionManager. The
5 default username for
connecting the
FusionCompute
hypervisor is gmsysman,
and the default password
6 is GMEnginE@123.

8 If Update data
immediately after data
saving is not checked, the
system automatically
7 updates the hypervisor
data periodically (every six
hours) to ensure data
consistency between
FusionManager and the
8
hypervisor.

4. Click Next.

39
Step 2: Add VSAM to FusionManager.
1. Configure VSAM access information.

3 5 If only one VSAM node

is deployed, enter the VSAM
4 management IP address and
the default port number
18443.
5
6 The default username
for connecting VSAM to
FusionManager is gmsysman,
and the default password is
GMEnginE@123.
6

6. Click Next.
N/A
7. Confirm that the entered information is correct, then click Add.

40
 7.3 Associate the Resource Cluster with a Resource Zone
Associate the resource cluster in the added hypervisor with a resource zone in FusionManager, so the
computing, storage, and DVS resources virtualized in the hypervisor are added to the computing, storage, and
network resource pools in FusionManager, respectively.

Step 1: Associate the resource cluster with a resource zone in FusionManager.

1. Go to the Resource Clusters page.

N/A

2. Click Associate.

3. Associate the added resource cluster with a resource zone.

2
N/A

4. Click OK.

41
 7.4 Create AZs.
An availability zone (AZ) is a collection of logical resources that can be allocated to users.

Step 1: Create an AZ.

1. Go to the Resource Zones page.

N/A

2. Click the name of the target resource zone.

The Summary page for the resource zone is displayed.

3. Select Availability Zones.

4. Click Create.

5. Configure basic information for the AZ.

N/A

6. Add resource clusters to the AZ.

1
The resource clusters
contained in an AZ must
2 be provided by the same
hypervisor.
4
3

7. Confirm that the entered information is correct, then click Add.

42
 8 Configure Resource Pools

8.1 Add a VLAN Pool

To create service networks (external networks, internal networks, and routed networks) on FusionManager,
the VLANs used by these networks must be first added to the VLAN pools in FusionManager. Then
FusionManager can manage and allocate VLAN resources to the requested service networks in a unified
manner. VLAN pools in FusionManager are available only after being associated with the DVSs.

Step 1: Add a VLAN pool.

1. On FusionManager, choose Resource > Resource Zones, select a

resource zone, then choose Network Resource Pools > VLAN Pools.
N/A

2. Click Create.

3. Configure the VLAN pool information.

4 4 Enter the service

plane VLAN range
configured on the switch.

4. Click Create.

43
 8.2 Create an External Network
Add an existing network of the customer that is connected to the Internet as the external network. After the
external network is added to FusionManager, FusionManager can manage the public IP addresses in the
network and provide public IP addresses for VMs to connect to the Internet through the software router.
Step 1: Create an external network.

1. On FusionManager, choose Resource > Resource Zones, select a

resource zone, and choose Network Resource Pools > External Networks.

2. Click Create. N/A

3. Set Connection Mode to Subnet (common VLAN) and Connect to

Internet to Yes.

4. Enter the external network name.

N/A

5. Select the required DVS, then click Next. Select the DVS with which
the external network
6. Enter the external network VLAN, then click Next. VLAN is associated.

7. External subnet information for the external network.

N/A

8. Click Next.

9. Use the default QoS settings, then click Next.

N/A
10.Confirm that the entered information is correct, then click Create.

44
8.3 Create a VSA Management Network
The VSA management network communicates with the system management plane and assigns IP addresses
for system service VMs, such as the software router VM and internal DHCP server VM, so the system service
VMs can communicate with the VSAM and FusionManager nodes.
Step 1: Add a VSA management network.

1.On FusionManager, choose Resource > Resource Zones, select a

resource zone, and choose Network Resource Pools > VSA Network. N/A

2. Click Create VSA Management Network.

4. Enter the external network name.

N/A

5. Configure the VSA management network.

1
6 Ensure that the VLAN
of the VSA management
network has been added
2 to the DVS in the
hypervisor
3
4 (FusionCompute) and the
4 VLAN is not contained in
the FusionManager VLAN
5 pool.
6

9. Remain the default settings for network port rate limit, then click Next.
N/A
10. Confirm that the entered information is correct, then click Create.

45
9 Prepare a VM Template

9.1 Import a VSA VM Template

The VSAM template is a system service VM template. When a tenant applies for a software router, the system
uses the imported VSA VM template to automatically create a system service VM functioning as a software
router for the tenant.

Step 1: Import a VSA VM template to FusionCompute.

1.Decompress FusionCompute V100R005C00SPC100_VSA.zip on the
local PC.
The following files are obtained:
FusionCompute_V100R005C00SPC100_VSA.ovf
FusionCompute_V100R005C00SPC100_VSA-1.vhd
2.Create a new folder, move the two files to the folder, and share the folder
with the current user of the local PC. N/A

3. Log in to FusionCompute.
4. On FusionCompute, choose VM and Template.
5. Click Import Template.
6. Select Shared directory, then click Next.
7.Configure the template information.

2
3 Enter the username
and password for logging
in to the local PC.

4
8.Select the creation location, then click Next.
9.Configure the data store and configuration mode for the VM disks, then
select Persistent.
N/A
You are advised to deploy the VSA VM using a shared storage resource.
Otherwise, deploying the VSA VM concurrently in multiple clusters may fail.
10.Remain the default values of other parameters, then click Next.
11.Enter the name of the VSA VM template.
12.Remain the default values of other parameters, then click Next.
N/A
13.Confirm that the entered information is correct, then click Finish.
The creation process takes about 10 minutes.

46
Step 2: Discover the VSA template on FusionManager.

1. Log in to FusionManager.

2. Choose Resource > VM Templates.

3. Click Discover.

4. Discover the VM template available in the hypervisor.

2
5. Click OK.

Step 3: Change the VM template type.

1. Locate the row that contains the discovered VSA template, then choose
More > Modify VM Template Information.

2. Change the template type.

47
9.2 Create a VM Template
Create a VM template based on the OS type and VM specification requirements of the needed VMs. The
template can then be used to create new VMs with the same specifications as the template, which
significantly shortens the time for configuring new VMs and installing OSs on them.

Step 1: Create a VM template.

1. On FusionManager, choose Resources > VM Templates.
Note: FusionManager
does not support VM
2. Click Create. template creation if it
uses local disks as
3. Configure basic information for the VM. storage resources.
1

4. Configure the VM template specifications.

4
5

5. After the VM is created, click Next.

The Install Software page is displayed. On this page, you can log in to the
VM using VNC and install an OS and Tools and configure NICs and disks for
the VM.

48
Step 2: Install an OS for the VM.

1. Click on top of the VNC window and mount the OS CD/DVD-ROM

drive or ISO image file to the VM.

SUSE Linux Enterprise

Server 11 is used as an
2 example in this task.

3
4

2. After the VM restarts, install the OS on the VM as prompted. Note: Do not close the
The OS installation method for a VM is similar to that for a physical computer. VNC login window before
OS installation is
complete. Otherwise, the
3. After the OS is installed, click on the top of the VNC window, then CD/DVD-ROM drive is
select Unmount CD/DVD-ROM Drive. automatically unmounted
from the VM

4. Install the OS patch. The patch file must be mounted to the VM as an ISO
N/A
file.

Step 4: Disable the firewall on the VM.

1. Log in to the VM as user root.

2. On the VM desktop, choose Computer > YaST.

The YaST2 Control Center window is displayed.

3. Select Security and Users from Groups and click Firewall in the right
pane. The YaST2 window is displayed.

4. Select Disable Firewall Automatic Starting from Start-Up and click Stop
Firewall Now.

5. Click Save Settings and Restart Firewall Now.

6. Click Next.
A confirmation dialog box is displayed.

7. Click Yes.
A confirmation dialog box is displayed.

8. Click Finish.
The YaST2 window is closed.
9. Right-click the VM desktop and choose Open in terminal from the
shortcut menu.
The system switches to the CLI.

10. Run the reboot command to restart the VM.

49
Step 5: Install Tools.
1.Decompress the FusionCompute
V100R005C00SPC100_GuestOSDrivers.zip software package on the local
PC.
The FusionCompute V100R005C00_GuestOS.iso file is obtained.
2.Use VNC to log in to the VM as user root and mount the ISO image
FusionCompute V100R005C00SPC100_GuestOS.iso to the VM.
3.Right-click on the VM desktop and select Open in terminal from the
shortcut menu.
The system switches to the CLI.
4.Run the following command to create the xvdd directory:
mkdir xvdd
5.Run the following command to mount the ISO image to the VM:
mount Target directory xvdd
For example, run mount /dev/sr0 xvdd to mount the ISO file to the /dev
directory on the VM running SUSE Linux Enterprise Server 11.
6.Run the following command to switch to the xvdd/pvDriver/linux directory:
cd xvdd/pvDriver/linux
7.Run the following command to view the required Tools installation package: Tools improve I/O
ls processing, hardware
The following information is displayed: monitoring, and other
... advanced functions on a
uvp-tools-linux-xxx.tar.bz2 VM.
uvp-tools-linux-xxx.tar.bz2.sha256

8.Run the following commands to copy the Tools installation package to the
root directory:
cp uvp-tools-linux-xxx.tar.bz2 /root
cd /root
9.Run the following command to decompress the Tools software package:
tar -xjvf uvp-tools-linux-xxx.tar.bz2
10.Run the following command to switch to the Tools installation directory:
cd uvp-tools-linux-xxx
11.Run the following command to install Tools:
./install
Tools installation is complete if the following command output is displayed:
The PV driver is installed successfully. Reboot
the system for the installation to take effect.

12. Run the following command to restart the VM for Tools to take effect:
reboot

13.Use VNC to log in to the VM as user root again.

14.Right-click the VM desktop and choose Open in terminal from the

shortcut menu.
15.Run the following command to check whether Tools installation is
successful: N/A
ps -ef | grep uvp-monitor
Tools installation is successful if the command output contains the bold
characters as follows:
root 4561 1 0 Jun29 ? 00:00:00 /usr/bin/uvp-monitor
root 4567 4561 0 Jun29 ? 00:00:00 /usr/bin/uvp-monitor
root 6185 6085 0 03:04 pts/2 00:00:00 grep uvp-monitor

50
Step 7: Configure the VM NIC.
1. Run the following command on the VM to view the files in the network rule
directory:
ls l /etc/udev/rules.d
2. Run the following commands to delete the rule files whose file names contain
persistent and net in the network rule directory:
For example:
rm -r /etc/udev/rules.d/30-net_persistent-names.rules
rm -r /etc/udev/rules.d/70-persistent-net.rules
The italicized content in the command varies depending on the actual service
environment
N/A
3. Decompress the software package FusionCompute
V100R005C00SPC100_GuestOSDrivers.zip on the local PC.
The FusionCompute V100R005C00SPC100_Customization.iso file is obtained.

4. Mount the FusionCompute V100R005C00SPC100_Customization.iso file to

the VM.
This file is used to configure the VM to automatically obtain an IP address using
the DHCP service.
5. Copy the linux folder in the ISO file to the /home directory on the VM.
6. Run the following command to back up the original NIC configuration file and
create a new configuration file for the NIC:
sh /home/linux/autoConfigLinuxNetwork.sh /etc/sysconfig/network
The command is executed successfully if the following information is displayed N/A
backup old config files ...
create new config files ...
done !!!

7. Run the following command on the VM to switch to the control center:

yast

8. Choose Network Devices > Network Settings.

9. Hold down Alt and press G on the Network Settings page. N/A
The Global Options page is displayed.

10. Hold down Alt and press T, and select Traditional Method with ifup.

11. Press F10 to save the configurations and exit the control center.

51
Step 6: Configure the VM template.
1. Run the following command on the VM to open the rc file using the visual
interface (vi) editor: Note:
vi /etc/init.d/rc Back up the rc file before
editing it.
2. Press i to enter editing mode.

3. Add a command statement based on the following requirements:

If exit 0 is displayed at the end of the file, add sh
/etc/init.d/setpasswd.sh in the line before exit 0.
If exit 0 is not displayed at the end of the file, add sh
/etc/init.d/setpasswd.sh at the end of the file.

4. Press Esc, enter :wq, and press Enter.

The system saves the configurations and exits the vi editor.

Step 7: Initialize the user disk.

1. Run the following command on the VM to query user disk information:
ll /dev/xvd*
brw-rw---- 1 root disk 202, 0 08-15 16:13 /dev/xvda
brw-rw---- 1 root disk 202, 1 08-15 16:13 /dev/xvda1 xvda indicates a system
brw-rw---- 1 root disk 202, 2 08-15 16:13 /dev/xvda2 disk, xvdd indicates the
brw-rw---- 1 root disk 202, 48 08-15 16:13 /dev/xvdd CD/DVD-ROM drive, and
brw-rw---- 1 root disk 202, 64 08-15 16:13 /dev/xvde xvde indicates a user disk.
brw-rw---- 1 root disk 202, 65 08-15 16:13 /dev/xvde1
brw-rw---- 1 root disk 202, 66 08-15 16:13 /dev/xvde2

2. Run the following command to format the user disk:

mkfs.ext3 -F /dev/xvde

3. Run the following commands to attach the user disk to the VM:
mkdir /usr/xvde
mount /dev/xvde /usr/xvde/

4. Run the following command to query the information about the user disk:
df h N/A
The user disk is successfully attached to the VM if a capacity value is displayed for
the xvde disk.
File System Capacity Used Available Usage Mounting Point
/dev/xvda2 19G 3.1G 15G 18% /
devtmpfs 465M 108K 465M 1% /dev
tmpfs 465M 100K 465M 1% /dev/shm
/dev/xvde 20G 173M 19G 1% /usr/xvde

5. Run the following command to open the fstab file using the vi editor and
enable automatic disk attaching:
vi /etc/fstab

6. Move the cursor to the end of the file, press Enter, and enter the following
N/A
line:
/dev/xvde /usr/xvde/ ext3 defaults 0 0

7. Press Esc, enter :wq, and press Enter.

The system saves the configurations and exits the vi editor.

52
Step 10: Complete VM template creation.

1. FusionManager, choose Resource > Templates and Specs .

2. Locate the row that contains the VM template, then choose More > Install
Software.
N/A
The Install Software page is displayed.

3. Click Complete.
The VM Templates page is displayed., on which the VM template status is
Complete. After the VM is created, the CD/DVD-ROM mounted to the VM is
automatically unmounted.

53
 10 Create a VDC
A virtual data center (VDC) is the unit of using virtual resources on FusionManager. Create a VDC for a
service department and create a VDC administrator. Then the VDC administrator can manage resources in
the VDC and allocate the resources to user VMs in the VDC.
Step 1: Create a VDC.
1. On FusionManager, choose VDC > VDCs.
The VDC management page is displayed.

2. Click Create VDC.

3. Configure the VDC information.

3 Configure the
maximum amount of
resources allowed for the
3 VDC. These settings can
also be modified after the
VDC is created.

4. Click Next.
5. Select an AZ, then click Next.
6. Select an external network, then click Next.
7. Select VDC members, then click Next.
8. Confirm that the entered information is correct, then click Create.

9. Repeat step 2 to step 8 to create VDC02 and VDC03.

Step 2: Create the VDC administrator.

1.Locate the row that contains the created VDC, then choose More >
Member Management. The created VDC
administrator can manage
2. Click Create User.
the resources available in
3. Set the username, password, and role, then click Create. the VDC.
To create a VDC administrator, select the vdcmanager role.

54
11 Create a VPC and Networks

11.1 Create a VPC

Create a VPC to provide VDC tenants with a secure and isolated network environment. The VDC
administrator can create virtual networks in a VPC to provide VDC tenant VMs with the same network
functions as those provided by a traditional network.

Step 1: Log in to FusionManager.

After logging in to
FusionManager for the
1. Log in to FusionManager as the VDC administrator. first time, you need to
change the default login
password as requested.

Step 2: Create a VPC.

1. Choose VPC > My VPC.

2. Click Create VPC.

3. Configure the VPC information.

5. choose Custom, then click Next.

N/A
6. Click Create.

55
11.2 Apply for a Router
Apply for a router for the VPC so that the router can serve as a gateway for the routed networks created in the
VPC. The router also supports the elastic IP address function, which allows an elastic IP address to be bound
to the VM so the VM can connect to public networks.

Step 1: Go to the VPC configuration page.

ISO
1. Click the name of the created VPC (VPC01).

2. On the displayed VPC01 configuration page, choose Routers.

3. Click Apply for Router.

4. Apply for a router.

1 A software router is
deployed on a VSA VM to
provide firewall functions.
The administrator can
1 apply for a software router
only after creating the
VSA management
network and importing the
VSA template to the
system. For details about
the software router
2 functions, see Appendix 6.

56
11.3 Create a Routed Network
VMs deployed in a routed network can have their private IP addresses bind to an elastic IP address through
a router, so the VMs can use the elastic IP address to provide public network access services.

Step 1: Create a routed network.

1. On the VPC01 page, choose Network> Network.

A routed network can
provide VMs with elastic
2. Click Create.
IP address and destination
network address
3. Enter the routed network name and set the network type to Routed
translation (DNAT)
Network. functions through the
router. The router also
supports configuration of
access control list (ACL)
rules to control the data
4. Click Next. traffic inbound to or
outbound from the routed
network to improve
network security.

4. Configure VLAN information for the routed network.

1

2
2
Enter a VLAN ID
planned for routed
networks.

5. Configure subnet information.

2
The VDC
administrator can
2 customize the subnet IP
address for the routed
network.

6. Click Next.

7. Confirm that the entered information is correct, then click Create.

57
12 Provision VM

12.1 Create the VM

The VDC administrator can select a created VM template and specify the specifications and network to
create a VM with the same configuration as the template.

Step 1: Create the required VM.

1.On the web client page in tenant view, choose Resources > Computing > N/A
VMs.

2.Click Create.

3.Select a VM template, then click Next.

4. Configure the VM specifications.

5. Select a network. 1

2
Add the VM NIC to
3 3 routed network
the
created in 11.3.

6. Enter the VM name, then click Next.

7. Confirm that the entered information is correct, then click Complete.

The system begins to create the VM.

Step 2: Install the application software.

1. Mount the ISO file of the application software to the VM to install the
application software on the VM.
You can use any ISO image creation tool, such as UltraISO and ISOMaker, to create
an ISO file for the desired application software.

58
 12.2 Bind an Elastic IP Address to a VM
Elastic IP address is a public IP address that can be bound to a VM or a private IP address to enable the VM
to provide external services using the public IP address. Apply for an elastic IP address before binding the
elastic IP address to a VM.

Step 1: Apply for an elastic IP address.

1. On the VPC01 configuration page, choose Network > Elastic IP

Addresses.
2. Click Apply For.
A message is displayed indicating that elastic IP address application is
successful.
3. Click OK.
The requested elastic IP address is displayed. The requested elastic IP
address is obtained from a
subnet from the created
external network.

Step 2: Bind the elastic IP address to the VM.

1. Locate the row that contains the obtained elastic IP address, then click
N/A
Bind.

2. Bind the elastic IP address to the VM.

Verify the Elastic IP Address Bound to the VM

Ping an IP address in the external network using the elastic IP address
bound to the VM to check whether the VM can communicate with the external
network using the bound elastic IP address.

59
12.3 Add ACL Rules
Add ACL rules in the VPC to allow users to access the web services deployed on a specific VM using only
the TCP protocol and port 80. This configuration prevents unauthorized users from accessing the web
services and thereby improves network access security.
Note: The system allows services access using any supported port and protocol by default. To allow VMs to
access services using only the specified protocol and port number, you need to first add an ACL rule that
prohibits service access using any protocol or port, and then add another higher-priority ACL rule that
specifies the protocol and port number allowed for service access.

Step 1: Prohibit access to the web-service-deployed VM using any protocol and port.
IN indicates the control for
1. On the VPC01 configuration page, choose Security > ACLs.
network packets inbound to
the VM. OUT indicates the
2. On the IN page, click Add Rule. control for network packets
outbound from the VM.

3. Configure ACL rules. 1 Set the ACL rule ID

representing the rule priority.
If multiple ACL rules contain
1 the same rule configuration,
the rule with the smaller rule
ID takes effect preferentially.
2 You are advised to number
two adjacent rules with a
3
step of 10 numbers to
4 facilitate adding more sub-
rules in future.
5
5 Set the elastic IP
6 address bound to the VM on
which the configured ACL
rule takes effect.
7
6 Set the IP address of the
VMs to access the services.
8 0.0.0.0 indicates all IP
addresses.

Step 2: Specify the protocol and port number allowed for VM access.
1. On the IN page, click Add Rule.
2. Configure the ACL rules.
1 The ACL rule configured
in the preceding step
1 prohibits the access to the
web service VM. The ACL
2 rule to be configured in this
step allows access to the
3
VM using the TCP protocol
4 and port number 80. This
5 ACL rule (10) has the higher
priority than the ACL rule 20
6 configured in the preceding
step.
7
8

60
Appendix

Appendix 1 Principles of VM Network Access

A virtual NIC of a VM communicates with an external network by connecting to the DVS through the
port group, then by connecting to the physical NIC of a host through the DVS uplink. These connections
are shown in the following figure.

Host1 Host2

VM1 VM2
VPC

Routed network1 Routed network2

Router VLAN 11 VLAN 12
192.168.11.0/24 192.168.12.0/24

Gateway 192.168.11.1; 192.168.12.1

External network
VLAN 2 192.168.2.0/24

Port Group VLAN 2 VLAN 11 VLAN 12

Virtual
resources
DVS
Uplink

Physical
resources

Physical network

Network
Description
Element
A software router functions as a gateway that enables VMs in a VPC to communicate
Software with VMs in other routed networks. The software router connects to the public network
router through the external network and therefore provides IP addresses for VMs to access
external networks.
A port group is a virtual logical port similar to a template with network attributes. A port
Port group group is used to define VM NIC attributes and uses a DVS to connect to the network:
Each service network (internal, routed, and external networks) created on
FusionManager maps a port group on the DVS.
A DVS provides the same functions as a physical layer 2 switch. A DVS links port groups
DVS
to VMs and connects to the physical network through uplink channels.
An uplink connects the DVS to the physical network NIC and therefore can transmit the
Uplink
data from the VMs connected to the DVS to the physical network.

61
Appendix 2 Principles of VM Storage Access
A data store is a logical storage unit on FusionCompute. A data store is used to universally define all
types of storage resources.
You can create a virtual disk on a data store for use by a VM.

Host local disk

VM
LUN
Virtual disk

IP SAN storage
Data store

Host Shared storage

Appendix 3 Network Communication Between Hosts and IP SAN Devices

Logical layer:
After a storage device is
associated with a host, the host
bus adapter (HBA) generates a Host IP SAN device
WWN for the host.
After an initiator is added to the LUN01
logical host on the storage device
using the host WWN, the host can
WWN

LUN02
access the storage resources
Initiator

(LUNs) that match the logical host

on the storage device and add the

LUNs as data stores.
Controller
HBA

Logical host

Logical association

Physical association
Physical layer:
A host connects to an IP
SAN device through
multipathing.
Switch

Storage NICs on the host

connect to the storage
NICs on the storage device
controller.

62
Appendix 4 Principle of Clock Synchronization

After the NTP clock source is

NTP clock
configured, all hosts, VRM source
VMs, and FusionManager
VMs synchronize time from FusionManager
the NTP clock source to
ensure system time accuracy. VRM

Hosts in the management cluster Other hosts

Appendix 5 Setting Multipathing Mode for a Host Using Commands

1. After the OS is installed on the host and the host restarts, log in to the host as user
root in the remote control window, and run TMOUT=0 to disable logout on timeout.
The password of user root
is the password you set
during host OS installation.

2. Run the following command to set the multipathing mode to Huawei mode:
sh /opt/uvp/multipath/change_multipath_mode.sh 1

N/A

The command is executed successfully if the message "Enable ultrapath

successfully" is displayed.

3. Run reboot to restart the host for the mode to take effect:

N/A

63
Appendix 6 VSAM and VSA

The VSAM node is deployed on the FusionManager management plane to manage VMs that provide VSA
system services, including software router and DHCP.

Management VSA management

network network

VSA VSA

DHCP VSA

VPC1
VPC2 VPCn
FusionManager
node VSAM node

VM VM VM
Service networks

VM VM VM

Network Network Network

1 2 n

The VSA management network connects to the management networks of the FusionManager node and the
VSAM node to enable communication between VSA VMs and the VSAM node. When a tenant applies for a
software router or the DHCP service for a VPC, FusionManager creates a VSA VM using the VSAM node
and automatically deploys the virtual firewall or DHCP service on t he VSA VM. A software router functions
as a firewall that connects to the Internet-accessible external network to provide public IP addresses for
VMs in the VPC to access public networks.

64