TABLE OF CONTENTS

• 1 Intro
  • 1.1 Background
  • 1.2 Purpose
  • 1.3 Testers
•  2 Planning
  • 2.1 Topology
  • 2.2 IP Planning
  • 2.3 Server Configuration
  • 2.4 Switch Configuration
  • 2.5 SAN Storage Configuration
  • 2.6 Software Version
  • 2.7 Preparation
• 3 Installation
  • 3.1 Install system
  • 3.2 Configure host network
  • 3.3 Setup management HA
  • 3.4 Mount backup storage (SAN)
  • 3.5 Setup NFS as primary storage (Optional)
  • 3.6 Initialise ZStack Cloud
• 4 Test Checklist

1 Intro

1.1 Background

Cloud computing is an important opportunity in XX's development and digital transformation. The traditional business mainly works on network infrastructure, while the future business will focus on building infrastructure for applications, which can be realised precisely with cloud computing. XX Company needs to combine computing and information storage capacity to provide effective services.

1.2 Purpose

ZStack is one of the best cloud computing solutions, based on open-source KVM virtualisation technology and integrated distributed storage and network management, providing a lightweight, highly concurrent, full API cloud computing solution. To validate ZStack's logical architecture and assess its technical maturity and its ability to integrate cloud resources with CPU, motherboard, 10GbE networks and storage.

1.3 Testers

 
2 Planning

2.1 Topology

This test uses ZStack Hybrid Cloud Edition, which provides server, storage and network virtualisation capabilities, abstracting information system hardware facilities into a unified resource pool and providing cloud resources on-demand services. 

In this test project, two networks were built, 10GbE for the management and service network, another 10GbE for the storage network. The logic diagram of this solution is as follows.

2.2 IP Planning

2.3 Server Configuration

2.4 Switch Configuration

The management network, service network, and storage network should be configured with LACP on the switch for the high availability of network hardware. The physical machine NIC use ZStack CLI to configure as Linux bond 4 LACP mode, which can realise the high availability of the corresponding network.

The management network, storage network, service network need to be specified as a VLAN. Also needs to configure trunk mode on the switch side. Otherwise, configure switch port as access mode. The administrator needs to plan and configures VLANs according to the actual network environment and makes network connections. The corresponding ports of the switch need to be configured for link aggregation and use the LACP protocol.

2.5 SAN Storage Configuration

2.6 Software Version

2.7 Preparation

3 Installation

3.1 Install system

Install Host A and Host B as management nodes. Install Host C as compute node. Please refer to the system installation section of the user manual for the installation process.

3.2 Configure host network

1. Create a bond

All hosts：

zs-bond-ab -c bond0

zs-bond-ab -c bond1

2. Add NIC to bond

All hosts：

zs-nic-to-bond -a bond0 em1

zs-nic-to-bond -a bond0 em1

zs-nic-to-bond -a bond1 enps0

zs-nic-to-bond -a bond1 enps1

3. Set the management IP address

Host A:

zs-network-setting -b bond0 192.168.1.11 255.255.255.0 192.168.1.1

Host B:

zs-network-setting -b bond0 192.168.1.12 255.255.255.0 192.168.1.1

Host C:

zs-network-setting -b bond0 192.168.1.13 255.255.255.0 192.168.1.1

4. Set the storage IP address

Host A:

zs-network-setting -b bond1 192.168.100.11 255.255.255.0

Host B:

zs-network-setting -b bond1 192.168.100.12 255.255.255.0

Host C:

zs-network-setting -b bond1 192.168.100.13 255.255.255.0

5. Check the network configuration

All hosts:

zs-show-network

3.3 Setup management HA

1. Upload licenses

Download the request key from Host A, and Host B. Apply two trail licenses for two nodes with the same features. Then upload the licenses to Host A and Host B separately.

2. Download HA Suite

Download ZStack HA Suite (ZStack-Enterprise-Multinode-HASuite.tar.gz) to Host A, then unzip it.

Host A:

tar zxvf ZStack-Enterprise-Multinode-HA-Suite.tar.gz

3. Install HA Suite

Host A：

./zsha2 install-ha -nic br_bond0 -gateway 192.168.1.1 -slave "root:password

@192.168.1.12" -vip 192.168.1.254 -db-root-pw zstack.mysql.password -yes -time-server server 0.au.pool.ntp.org

4. Add timeserver

Host A：

vim /etc/chrony.conf

local stratum 10  

allow 0.0.0.0/0    

server 0.au.pool.ntp.org iburst    

systemctl restart chronyd.service

Host B, C:

vim /etc/chrony.conf

server 192.168.1.11 iburst    

systemctl restart chronyd.service

5. Setup database backup

Host A：

crontab -e 

30 */4 * * * zstack-ctl dump_mysql --host root@192.168.1.12 --d --keep-amount 42

Host B：

crontab -e 

30 */4 * * * zstack-ctl dump_mysql --host root@192.168.1.11 --d --keep-amount 42

3.4 Mount backup storage (SAN)

1. Scan LUN

Host C

/usr/bin/rescan-scsi-bus.sh

multipath -ll

2. Format and mount LUN

parted /dev/mapper/mpathb mklabel gpt 

mkfs.xfs -f -i size=512 -l size=128m,lazy-count=1 -d agcount=16 /dev/mapper/mpathb

chmod +x /etc/rc.local

mkdir /zstack_bs –p

mount /dev/mapper/mpathb /zstack_bs

echo sleep 5 >>/etc/rc.local

echo mount /dev/mapper/mpathb /zstack_bs >>/etc/rc.local

3. Check mount point

df –h

ls -l /etc/rc.local

3.5 Setup NFS as primary storage (Optional)

1. Install NFS

HOST C:

yum install nfs-utils

mkdir /zstack_ps

chmod -R 755 /zstack_ps

chown root /zstack_ps

vim /etc/exports

/zstack_ps        192.168.100.0(rw,sync,no_root_squash,no_all_squash)

systemctl enable rpcbind

systemctl enable nfs-server

systemctl enable nfs-lock

systemctl enable nfs-idmap

systemctl start rpcbind

systemctl start nfs-lock

systemctl start nfs-idmap

systemctl restart nfs-server

HOST A, B, C:

iptables -F

systemctl stop iptables

systemctl disable iptables

2. Check NFS

rpcinfo -p

exportfs -r

showmount -e localhost

3.6 Initialise ZStack Cloud

Login to http://192.168.1.254:5000 and follow the wizard.

4 Test Checklist

The POC is divided into the following test sections: 

• ZStack interface;
• Dashboard; 
• Global setting; 
• VM instance management; 
• Network management; 
• Image management; 
• Storage management; 
• Platform O&M; 
• vCenter management; 
• Enterprise management; 
• Backup management; 
• Bare metal management.

• Concurrency performance test; 
• VM instance disk I/O performance test.

• Compute node power failure; 
• Management node power failure.

• Adding AccessKey; 
• Region Management; 
• Zone Management; 
• ECS instance management; 
• Image management; 
• Volume management; 
• Network management