Professional Documents
Culture Documents
HCIA Cloud Computing V4.0 Lab Guide
HCIA Cloud Computing V4.0 Lab Guide
HCIA-Cloud Computing
Lab Guide
Version: 4.0
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their
respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between
Huawei and the customer. All or part of the products, services and features described in this
document may not be within the purchase scope or the usage scope. Unless otherwise specified in
the contract, all statements, information, and recommendations in this document are provided "AS
IS" without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made
in the preparation of this document to ensure accuracy of the contents, but all statements,
information, and recommendations in this document do not constitute a warranty of any kind,
express or implied.
Website: http://e.huawei.com
HCIA-Cloud Computing V4.0 Lab Guide
HCIA-Cloud Computing V4.0 Lab Guide
Contents
2.2 Manually Installing the CNA Nodes and Installing the VRM Node Using a Tool ................................. 10
5.3 Procedure........................................................................................................................................................................ 91
Overview
This document is intended for trainees taking the HCIA-Cloud Computing certification
training courses. It provides cloud computing and virtualization basics, and also
introduces you to the architecture and features of Huawei's virtualization product.
HCIA-Cloud Computing V4.0 Lab Guide
Server RH1288V5 1
Switch S5700 1
FusionCompute 6.3
CentOS 7.3
PuTTY
VNC-viewer
HCIA-Cloud Computing V4.0 Lab Guide
WinSCP
2 Installing FusionCompute
2.1 Objectives
This chapter describes how to install FusionCompute R6.3.1.
Method 2: Use an image to install the CNA node and use a tool to install the VRM
node. (This document uses this method.)
Method 3: Use an image to install both the CNA and VRM nodes.
If the time out, please sent Ctrl+Alt+Del to the VM and let it reboot, in the process of
rebooting, Please ESC for boot menu, and select DVD/CD as a boot device.
HCIA-Cloud Computing V4.0 Lab Guide
Press the up or down arrow key to select Hard Drive, and then press Enter.
Press the up or down arrow key to select the disk where the operating system is to be
installed.
HCIA-Cloud Computing V4.0 Lab Guide
Press the up or down arrow key to select Network, and then press Enter.
HCIA-Cloud Computing V4.0 Lab Guide
Configure the host network information (set the management plane VLAN).
Press the up or down arrow key to move to Manual address configuration and press
the space bar.
HCIA-Cloud Computing V4.0 Lab Guide
IP Address: 192.168.17.10
Netmask: 255.255.255.0
Set the gateway of the management plane to 192.168.17.254, and then select OK.
HCIA-Cloud Computing V4.0 Lab Guide
Press the up or down arrow key to select Hostname, and then press Enter.
Change HostName to CNA01. (Set the hostname of the other server to CNA02 based
on the planning.)
HCIA-Cloud Computing V4.0 Lab Guide
Press the up or down arrow key to select Timezone, and then press Enter. Change the
time zone to Asia/Beijing and press Tab to select OK.
Set the password. It is the root password for logging in to the operating system of the
CNA node.
Press the up or down arrow key to select Password, and press Enter. Change the
password to Cloud12#$ and press Tab to select OK.
HCIA-Cloud Computing V4.0 Lab Guide
Step 5 Repeat the preceding steps to install the other host CNA02. The network
address information is as follows:
IP Address: 192.168.17.20
Netmask: 255.255.255.0
To ensure system security, you are not allowed to log in to the host using Secure Shell
(SSH) as the root user after host installation. Instead, you can log in to the host using
SSH as user gandalf. You can then switch to the root user when necessary. The default
password of the gandalf user is IaaS@OS-CLOUD9!.
HCIA-Cloud Computing V4.0 Lab Guide
----End
Step 2 The installation preparation page is displayed. Set Language and select
FusionCompute and then VRM under Components, as shown in the
following figure.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 Select Installation package path. (The path cannot contain Chinese
characters or special characters.)
HCIA-Cloud Computing V4.0 Lab Guide
Step 7 Click Next. The Configure VRM page is displayed. Configure the VRM node.
(Obtain IP address planning from administrator or trainer.)
Step 8 Click Next. The Choose Host page is displayed. Click Install VRM. Wait until
the VRM installation is complete. The estimated time is 45 minutes.
HCIA-Cloud Computing V4.0 Lab Guide
Click Finish.
----End
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 Use the default user name admin and password IaaS@PORTAL-CLOUD8! to
log in to FusionCompute.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 Change the initial password to HCIA@123 upon the first login.
Click OK.
HCIA-Cloud Computing V4.0 Lab Guide
----End
3 FusionCompute Resource
Configuration
Step 1 In the left navigation tree on FusionCompute, click . The Resource Pools
page is displayed. Right-click the cluster name ManagementCluster
(automatically created by the system) to which you want to add a host, and
choose Add Host.
Step 2 The Add Host page is displayed. Add the host information and BMC
information as follows, and click Next.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 Wait until the CNA02 host icon changes from red to blue, indicating that
the CNA02 host is added successfully.
HCIA-Cloud Computing V4.0 Lab Guide
----End
Step 2 On the displayed page, click the Configuration tab. Choose Network >
Aggregate Port, and select Mgnt_Aggr (automatically created by the
HCIA-Cloud Computing V4.0 Lab Guide
system) from the Aggregate Port list. The physical NIC that has been added
to the aggregate port is displayed in the Physical NIC list, which is the
default physical NIC added when the host is added.
Step 3 Click Add Network Port. On the Add Network Port page that is displayed,
select other physical NICs to be added and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 The Aggregate Port configuration page is displayed. Refresh and view the
Physical NIC list of the aggregate port Mgnt_Aggr.
Step 5 Click Bind Network Port in the upper part of the page. The Bind Network
Port page is displayed.
Step 6 On the Bind Network Port page, set Binding Mode to Active-backup, select
the physical NIC to be added to the aggregate port Storage, and click
Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 7 The Aggregate Port configuration page is displayed. Refresh and view the
Physical NIC list of the aggregate port Storage.
Step 8 Refresh and view the aggregate ports added to the Aggregate Port list on
the upper part of the page.
Step 1 In the left navigation tree on FusionCompute, click . The Resource Pools
page is displayed. Click Network. On the displayed page, click Create DVS.
Step 2 On the Create DVS page, configure the following information and click Next.
(You can select Add Uplinks and Add VLAN Pool if necessary. In this
example, they are not selected.)
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 On the confirmation page, verify the information and then click Confirm.
Step 4 The Network page is displayed. View the newly created DVS in the DVS list.
HCIA-Cloud Computing V4.0 Lab Guide
----End
Step 2 On the Add Uplinks page, expand CNA02, select the port to be added as an
uplink, and click Confirm.
Step 3 The Uplink Group list is displayed. View the added uplink.
----End
HCIA-Cloud Computing V4.0 Lab Guide
Step 2 On the Add VLAN Pool page, enter Start VLAN ID and End VLAN ID and
click Confirm.
Step 3 The VLAN Pool list of ManagementDVS is displayed. View the added VLAN
pool.
----End
Step 2 On the Add Port Group page, set the basic information about the port
group, set Port Type to Access, and click Next.
Step 4 On the confirmation page, verify the information and click Confirm.
Step 5 Open the Add Port Group page again, and then add another port group
whose Port Type is Trunk.
HCIA-Cloud Computing V4.0 Lab Guide
Step 7 On the confirmation page, verify the information and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 8 The Port Group list of ManagementDVS is displayed. View the newly added
port groups.
----End
Step 2 On the Port Binding page, associate the storage port with an aggregate
port, and click Next.
Step 3 On the Connection Settings page, set connection parameters and click
Next.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 On the confirmation page, verify the information and click Confirm.
Step 5 Switch back to the Logical Interface page and check information about the
logical interface.
HCIA-Cloud Computing V4.0 Lab Guide
Step 6 Repeat the preceding steps to add a storage port for host CNA02.
----End
Step 2 Click Add Storage Resource. On the Add Storage Resource page, set the
storage resource parameters, set Type to NAS, select Associate Host, and
click Next.
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 On the Associate Host page, select hosts to be associated with the NAS
storage resource and click Next.
Step 4 On the confirmation page, verify the information, select Scan Storage
Device, and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 5 Switch back to the Storage Resources tab page. Refresh the page and view
the added NAS storage resource.
Step 6 Click Add Storage Resource to add an IP SAN storage resource. On the Add
Storage Resource page, set Type of IPSAN, configure the required
parameters, select Associate Host, and click Next.
HCIA-Cloud Computing V4.0 Lab Guide
Obtain the management IP address and storage IP address from the administrator or
trainer.
Step 7 Select the hosts to be associated with the IP SAN storage resource and click
Next.
HCIA-Cloud Computing V4.0 Lab Guide
Step 8 On the confirmation page, verify the information, select Scan Storage
Device, and click Confirm.
Step 9 Switch back to the Storage Resources tab page. Refresh the page and view
the added IP SAN storage resource.
----End
Step 1 On the storage configuration page, click the Storage Device tab. The
Storage Device page is displayed.
HCIA-Cloud Computing V4.0 Lab Guide
Step 2 Click Scan. On the Scan Storage Device page, select the hosts to be scanned.
The scanning takes about 1 minute. After the scanning is complete, refresh the page
and check whether available storage devices are detected. The following figure shows
the scanning result.
----End
Step 2 Click Add Data Store. On the Select Storage Device page, select the NAS
storage where the data store resides and click Next.
Step 3 On the Add Data Store page, set Name to DataStore_01, select the two
hosts to be associated with the data store, and click Next.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 On the confirmation page, verify the information and click Confirm.
Step 5 Switch to the Data Store tab page, click Add Data Store. On the Select
Storage Device page, select the IP SAN storage where the data store resides
and click Next.
HCIA-Cloud Computing V4.0 Lab Guide
Step 6 On the Add Data Store page, set Name to DataStore_02 and Storage Mode
to Virtualization, select the two hosts to be associated with the data store,
and click Next.
Step 8 On the confirmation page, verify the information and click Confirm.
Step 9 Switch back to the Data Store tab page, click Refresh Data Store, and check
the data stores added to the data store list.
----End
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 On the Select Creation Mode page, click Create VM and click Next to create
a bare VM.
HCIA-Cloud Computing V4.0 Lab Guide
Step 5 On the Select Data Store page, select the data store to be run and click Next.
Expand Disk 1, set Configuration Mode to Thin provisioning, retain the default settings
for other parameters, and click Next.
Step 7 On the confirmation page, verify the information and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 8 Switch back to the Resource Pools page. In the navigation pane, choose
Resource Pools > ManagementCluster and click the name of the newly
created bare VM. On the Summary page, the VM status changes to
Running.
----End
Step 2 On the Configuration tab page, choose Hardware > CD/DVD-ROM Drive
Unmounted. On the displayed page, set Mount CD/DVD-ROM Drive Type to
Mount Local CD/DVD-ROM Drive and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Do not close this page while using the image. Otherwise, the VM OS will fail to be
installed.
Step 4 Switch back to the Summary page. Click Log In Using VNC. In the displayed
window, install the OS as instructed. (You only need to know the overall
software installation process, instead of all detailed steps.)
----End
4.3.1 Importing a VM
Step 1 On the Resource Pools page, right-click Resource Pools and choose
Import > Import VM.
Step 2 On the Import Template page, select Import from Local PC, click Select next
to Template Path to select the path of the template VM, and click Next.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 On the confirmation page, verify the information and click Confirm.
Step 6 In the left navigation tree on FusionCompute, view the imported VM in the
VM list.
HCIA-Cloud Computing V4.0 Lab Guide
----End
Step 3 Log in to the VNC window of the VM as user root and install Tools.
Open the CLI and run the following commands to mount the virtual DVD-ROM drive
to a folder:
mkdir /etc/Tools
mount /dev/sr0 /etc/Tools
cd /etc/Tools
Run the following commands to copy the vmtools-2xxx.tar.bz2 file to the created
folder and decompress it:
cp vmtools-2xxx.tar.bz2 /root
cd /root
tar –xjvf vmtools-2xxx.tar.bz2
HCIA-Cloud Computing V4.0 Lab Guide
Run the following commands to access the Tools installation directory and install
Tools:
cd vmtools
./install
reboot
Step 4 After the VM is restarted, switch back to the Summary page. The status of
Tools is Running
Step 5 In the left navigation tree on FusionCompute, click . The Resource Pools
page is displayed. Right-click the VM name, choose Tools > Unmount Tools,
and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
----End
vi /etc/sysconfig/network-scripts/ifcfg-eth0
HCIA-Cloud Computing V4.0 Lab Guide
Step 2 Modify the following parameters in the configuration file and enter :wq to
save the change and exit.
Run the ip addr command to check whether the network configuration takes effect.
Run the ping 192.168.17.254 command to check whether the network configuration is
correct.
HCIA-Cloud Computing V4.0 Lab Guide
Step 5 On the Resource Pools page, choose Resource Pools > ManagementCluster.
Right-click the VM name, choose Power > Stop, and click Confirm to stop
the VM.
Step 6 On the Summary tab page, wait for the VM status to change to Stopped.
Then, in the navigation pane, right-click the VM name, choose Template >
Convert to Template, and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 7 In the navigation pane, expand VM Template to view the newly converted
VM template.
----End
Expand NIC Settings and configure NIC information for the VM. (IP Address/Subnet
Mask: 192.168.17.31/24, Default Gateway: 192.168.17.254)
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 Click Next. On the confirmation page, verify the information and click
Confirm. The VM Linux_01 is deployed.
Step 5 Repeat the preceding steps to deploy VM Linux_02 on host CNA02. The IP
Address/Subnet Mask: 192.168.17.32/24, Default Gateway: 192.168.17.254.
Step 6 After the VMs are deployed, view the newly deployed VMs in the navigation
pane.
HCIA-Cloud Computing V4.0 Lab Guide
Step 7 Right-click the name of the target VM, choose Power > Start, and click
Confirm to start the VM.
Step 2 Click + next to Number of Cores to change Number of Cores to 2, and click
Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 Log in to the VM as user root using VNC and run the following command to
check the number of CPUs on the VM:
----End
Step 2 Click + next to Memory to change Memory to 2 GB, and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 Log in to the VM as user root using VNC and run the following command to
check the VM memory size.
cat /proc/meminfo
---End
Step 2
Step 3 In the disk list, locate the row that contains the target disk, click More, and
choose Adjust Capacity.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 On the Adjust Capacity page, set Capacity (GB) to 6 and click Save.
Step 5 Refresh the disk list and view the disk capacity.
----End
Step 2 On the Add NIC page, retain the default NIC settings, set DVS to
ManagementDVS, select VLAN 16 created in section 3.2.4 "Creating Port
Groups", and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 Refresh the page and view the newly added NIC in the VM NIC list.
After the modification, press Esc, enter :wq, and press Enter.
HCIA-Cloud Computing V4.0 Lab Guide
Run the required command to restart the network service, as shown in the following
figure.
Use the NIC to ping the gateway and check whether the network is normal.
Step 5 Change the port group used by the new NIC to VLAN16-2.
Switch back to the VM NIC configuration page, click More of the new NIC, and choose
Modify Port Group.
In the Modify Port Group dialog box, select a new port group and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Ping the IP address of the NIC again. It is found that the network connection is
abnormal.
The cause for the abnormal network connection is that the port group type changes
from Access to Trunk. Differences between Access and Trunk need to be illustrated
based on the content in the training materials.
Step 6 (Optional) Add a new configuration to restore the network to the normal
state in trunk mode.
Modify the configuration file of the new NIC and delete the IP address.
Run the ip link add link eth1 name eth0.16 type vlan id 16 command to add NIC
eth0.16 tagged with VLAN 16.
Run the ip addr add 192.168.16.31/24 brd 192.168.16.255 dev eth0.16 command to
configure an IP address for the NIC.
Run the p link set dev eth0.16 up command to start the new NIC.
After the configuration is complete, run the service network restart command to
restart the network service.
----End
Step 2 On the Configure Object Rights page, select the permission to be disabled,
for example, Delete VM, and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 In the left navigation tree on FusionCompute, click . The Resource Pools
page is displayed. Right-click the VM name and choose Delete to see if the
VM can be deleted. If Delete is dimmed, the corresponding function is
unavailable.
HCIA-Cloud Computing V4.0 Lab Guide
This section describes the service scenarios of VM disks of different types and modes.
5.2 Process
1. Create disks of different types and modes.
2. Mount the created disks to Linux_01 and Linux_02.
3. Perform functional tests.
5.3 Procedure
Step 2 On the Create Disk page, configure the basic disk information, set Type to
Shared, and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 Create Disk_02 and Disk_03 by referring to Step 1 and Step 2 while
configuring the disk information as follows:
HCIA-Cloud Computing V4.0 Lab Guide
Switch back to the Disk List tab page and view the newly created disks.
Question: Compare the occupied spaces of Disk_01 (or Disk_02) and Disk_03. What
are the differences between common and thin provisioned disks?
----End
Step 2 Click Attach Disk. On the displayed page, select the Disk_01 disk and click
Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 Repeat Step 2 to attach Disk_02. On the Attach Disk tab page, check the
disks attached to the VM.
Step 4 Repeat Step 1 and Step 3 to attach Disk_01 and Disk_03 to Linux_02.
The VM disk list is as follows:
Question: Compare Disk_01 and Disk_02 (Disk_03). What are the differences between
common and shared disks?
----End
fdisk /dev/vdb
n
p
Press Enter three times.
w
cd /tmp
mkdir Test1
Run the mount command to mount the /dev/vdb1 disk partition to the /tmp/Test1
directory.
Run the following command to check the mounted disk partition /dev/vdb1.
df –Th
Step 3 Go to the mount directory, create a test file, and check whether the file can
be read and written.
cd /tmp/Test1
touch test1.txt
ll
Echo this is test file > test1.file
cat test1.file
If the information above is displayed, the disk can be read and written after being
formatted.
Step 4 Repeat the preceding steps to format Disk_02 and Disk_03, mount them to
/tmp/Test2 and /tmp/Test3 of the VM, and create test files test2.file and
test3.file. (Disk_02 and Disk_03 are the third disks of Linux_01 and Linux_02,
and the device names are /dev/vdc.)
Step 2 On the Migration Mode page, select Change Host for Select Migration
Mode and click Next.
Step 3 On the Change Host page, click Select, click + in front of site, select the
destination host, and click Confirm twice.
HCIA-Cloud Computing V4.0 Lab Guide
Step 4 Wait until the live migration is complete, switch back to the Summary page,
and check the host to which the VM belongs.
The preceding information indicates that VM Linux_01 has been migrated from host
CNA01 to host CNA02.
Step 5 Change the data store of the Linux_01 VM. On the Migration Mode page,
select Change Data Store for Select Migration Mode and click Next.
HCIA-Cloud Computing V4.0 Lab Guide
Step 6 On the Change Data Store page, select Migrate all storage, click Select. On
the displayed page, select the target data store and click Confirm.
Step 8 Switch back to the Change Data Store page. In the list on the lower part of
the page, view the disks that do not support migration and the reason.
Modify the destination configuration mode of the disks that support
migration and click Confirm.
Step 10 Choose Configuration > Disk and view the data store in the VM disk list.
The preceding information indicates that the VM disk is migrated from DataStore_01
to DataStore_02.
Step 11 Repeat the preceding steps to live migrate Linux_02 by switching its data
store.
Questions:
1. Does a VM with a shared disk support live migration in the Change Host mode?
2. Does a VM with a shared disk support live migration in the Change Data Store mode?
3. Does a VM with an independent & persistent disk support live migration in the Change
Data Store mode?
4. Does a VM with an independent & nonpersistent disk support live migration in the
Change Data Store mode or cold migration in the Change Data Store mode?
HCIA-Cloud Computing V4.0 Lab Guide
----End
Step 2 Click Create Snapshot. On the Create Snapshot page, enter the snapshot
name, deselect Create memory snapshot, and click Confirm.
Question: If you select Create memory snapshot, can the snapshot be successfully
created? Why?
Step 5 Choose Configuration > Disk. In the VM disk list, locate the row where the
disk resides, click More, and select Manage Snapshot. In the Manage
Snapshot page, check whether any snapshot can be detected.
HCIA-Cloud Computing V4.0 Lab Guide
Step 6 Repeat Step 1 to Step 5 to create a snapshot for the Linux_02 VM and check
whether a snapshot exists in the Manage Snapshot page.
Question: Does a snapshot exist for Disk_01 (shared disk)? Does a snapshot exist for
the Disk_02 disk (slave disk)? Does a snapshot exist for the Disk_03 disk (independent
nonpersistent disk)?
Step 7 Log in to the VM as the root user, and run the following command to create
the test.file file in the /root directory:
cd /root
touch test.file
ll
Step 9 Create a snapshot for the VM again and click the plus sign (+) in front of the
first snapshot Snap_01 to view the second snapshot Snap_02.
Step 10 Select the first snapshot Snap_01 in the snapshot list and click Resume VM.
In the dialog box that is displayed, click Confirm to restore the VM.
Step 11 Check whether the new test.file file exists in the /root directory of the VM.
If preceding information is displayed, the new test.file file does not exist. The VM has
been restored to the state when the first snapshot Snap_01 was created.
Return to the VM snapshot list and check the status of the second snapshot Snap_02.
HCIA-Cloud Computing V4.0 Lab Guide
Question: After a VM is restored using a snapshot, will a snapshot created after the
snapshot be affected?
Step 12 After the VM is restored using the snapshot, run the df –Th command to
check the disk attachment status on the Linux_01 VM.
The preceding information indicates that /dev/vdb1 and /dev/vdc1 are detached
after the restoration.
Step 13 Log in to the Linux_02 VM as the root user by referring to Step 8. Run the
following command to change the content of the test file test3.file under
/tmp/Test3 from this is test file to this is new file:
Step 14 Restore the Linux_02 VM using snapshot Snap_01. For details, see Step 10.
Step 15 After the restoration, check the disk attachment status of the Linux_02 VM.
HCIA-Cloud Computing V4.0 Lab Guide
Conclusion: After restoration, the disk Disk_02 (slave), disk Disk_01 (independent &
persistent), and disk Disk_02 (independent & nonpersistent) are detached.
Step 16 Run the mount command to attach the Disk_01 disk to the Linux_01 VM and
check whether the modified file exists in the /tmp/Test1 directory.
If the preceding information is displayed, the modified file still exists in Disk_01
(independent & persistent) after the restoration. Data changes are immediately
written to the disk.
The system displays a message indicating that /dev/vdc1 does not exist and cannot
be attached again.
After the restoration, the disk Disk_03 (independent & nonpersistent) needs to be
attached and formatted again, and the data in the disk will be lost.
Summary: When a VM snapshot is created, snapshots are not created for Disk_01
(independent & persistent) or Disk_03 (independent & nonpersistent), and disk data
cannot be restored. After the VM restoration, Disk_01 is detached, and after the VM is
HCIA-Cloud Computing V4.0 Lab Guide
attached again, its data is not lost. Disk_03 (independent & nonpersistent) is detached
and cannot be attached again. In addition, the disk needs to be attached and
formatted again, and data in the disk will be lost.
Step 18 After the preceding steps are performed, migrate Linux_01 to the original
host CNA01 and detach the shared disk Disk_01 from Linux_01 and
Linux_02. In the VM disk list, locate the row that contains the target disk,
and click Detach. In the dialog box that is displayed, click Confirm.
----End
This section provides guidance on how to ensure service availability where Huawei
virtualization layer is deployed.
In this lab, DRS rule groups are configured to meet the preceding requirements.
6.2 Procedure
Step 1 In the left navigation tree on FusionCompute, click . The Resource Pools
page is displayed. Click VM Linux_01 and VM Linux_02 to view their host
names under Basic Information on the Summary tab page.
Step 3 Click Control Cluster Resource at the upper-right corner of the page.
Step 5 When the compute resource scheduling configuration data shown in the
following figure is displayed, click Confirm.
Step 6 On the Configure Resource Scheduling page, choose DRS Rule > Rule Group
and click Add.
HCIA-Cloud Computing V4.0 Lab Guide
Step 7 On the displayed Add Rule Group page, set the rule group name to Rule_01,
set its type to Keep VMs together, select Linux_01 and Linux_02 in the VM
list, and click Confirm.
Step 8 On the Rule Group page, view the added rule group.
Step 9 Click Recent Tasks in the lower part of the page to view the task list.
HCIA-Cloud Computing V4.0 Lab Guide
The task shows that the system automatically migrates Linux_02 from host CNA02 to
host CNA01. That is, Linux_01 and Linux_02 run on the same host (Type = Keep VMs
together).
Step 10 Click Delete in the Operation column for Rule_01 to delete the rule group.
Step 11 Repeat steps 6 through 9 to add rule group Rule_02, set Type to Keep VMs
mutually exclusive, select Linux_01 and Linux_02 from the VM list, and view
the host to which the VMs have been migrated.
HCIA-Cloud Computing V4.0 Lab Guide
The task shows that the system automatically migrates Linux_02 from host CNA01 to
host CNA02. That is, Linux_01 and Linux_02 run on different hosts (Type = Keep VMs
mutually exclusive).
Step 14 Set the host group name to HostGroup, select the host on which the VM
will run from the host list. In this example, select CNA02 and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 15 Return to the Configuration page, choose DRS Rule > VM Group, and click
Add. The Add VM Group page is displayed.
Step 16 Set the VM group name to VMGroup, select Linux_01 and Linux_02 from the
VM list, and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Step 17 Repeat Step 6 through Step 9 to add rule group Rule_03, set Type to VM to
Host, set Rule to Must run on hosts in group, and select the newly added
VM group and host group. After the operations are complete, check the VM
migration result.
HCIA-Cloud Computing V4.0 Lab Guide
The task shows that the system automatically migrates Linux_01 from host CNA01 to
host CNA02. That is, Linux_01 and Linux_02 run on the specified host.
7.2 Procedure
Step 1 In the left navigation tree on FusionCompute, click . The Resource Pools
page is displayed. Choose ManagementCluster. On the Configuration tab
page, choose Configuration > Configure HA, and click Control Cluster
Resource at the upper-right corner.
Step 3 When the HA configuration data shown in the following figure is displayed,
select HA for Host Fault Policy, and click Confirm.
Use PuTTY to log in to CNA02 and run the following commands to power off CNA02.
(Use username gandalf and password IaaS@OS-CLOUD9! for login. Then, switch to
user root. The password is the one set when the CNA is installed. In this example, the
password is Cloud12#$.)
su – root
poweroff
Step 5 On FusionCompute, click Recent Tasks in the lower part of the page.
The tasks show that the system has automatically migrated Linux_01 and Linux_02
from CNA02 to CNA01.
Step 6 In the left navigation tree on FusionCompute, click . The Resource Pools
page is displayed. Right-click the host name, choose Power > Power On. On
the displayed page, click Confirm to power on CNA02.
HCIA-Cloud Computing V4.0 Lab Guide
Tip: this is the best way to power on CNA, however, in this lab, you can’t power on the
CNA with this way, please connect with manager or lecturer.
----End
8.2 Procedure
Step 1 Ping Linux_01 and Linux_02 to verify network connectivity.
On the displayed page, set the name and description and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
If you configure the NIC for the first time, power off Linux_01.
HCIA-Cloud Computing V4.0 Lab Guide
On the Configure Security Group page, click Select and select the security group
created in the previous step.
----End
9.2 Procedure
Question: How do I filter out all the alarms whose severity is Warning and Object
Type is Host?
Step 2 Find the target alarm, and click Clear in the Operation column to clear it.
Step 3 Under Monitoring, choose Alarm > Alarm Masking. On the Alarm Making
page, click Add. The Add Alarm Masking Rule page is displayed.
HCIA-Cloud Computing V4.0 Lab Guide
Remarks: On the Add Alarm Masking Rule page, use three methods to mask the
alarm "Data store I/O response delay exceeds the threshold".
----End
Step 2 On the Add Role page, specify Role Name, select permissions, and click
Confirm.
Remarks: Add the role Role_test that has the permissions to manage sites, clusters,
hosts, and VMs.
Step 3 Choose Rights Management > User Management and click Add User.
Step 4 On the Add User page, select a User Type, set User Name and Password,
select roles, specify other basic information, and click Confirm.
HCIA-Cloud Computing V4.0 Lab Guide
Remarks: Add a Local User. Set User Type to Local User and select the role added in
step 2.
----End
Remarks: Configure a password policy. If you enter incorrect passwords for two
consecutive times, the system automatically locks the account for 10 minutes.
----End
Step 2 Click Load License File. On the Load License File page, click Obtain ESN,
import the license file as prompted, and click Confirm.
----End
Step 1 Choose System Configuration > Services and Management. On the Services
and Management page, click More and choose Configure Management
Data Backup.
HCIA-Cloud Computing V4.0 Lab Guide
Step 3 Return to the Configure Management Data Backup page, choose Back Up
Management Data, and click Confirm.
Step 4 Go to the FTPD backup upload path and check the backup file.
----End