Command Line Tool

# Create a link aggregation virtual interface in LACP mode
zs-bond-lacp -c [bond-name]
zs-bond-lacp -c bond0

# Create another link aggregation virtual interface in active-backup mode
zs-bond-ab -c [bond-name]
zs-bond-ab -c bond0

# Bind the physical interface to the link aggregation interface
zs-nic-to-bond -a [bond-name] [nic-name]
zs-nic-to-bond -a bond0 ens3

# Create a VLAN interface
zs-vlan -c [nic-name] [vlan]
zs-vlan -c bond0 10

# Create a network bridge, and configure the network IP address for the network bridge
zs-network-setting -b [interface] [ipaddress] [netmask] [gateway]
zs-network-setting -b bond0.10 192.168.1.10 255.255.255.0 192.168.1.1

GUI

1. Add a bond device.

   On the INSTALLATION SUMMARY page, choose NETWORK & HOST NAME > Ethernet (ens3) > Configure.... Then the ens3 configuration page is displayed. Click the plus sign (+) at the lower left, select Bond from the prompted Add device drop-down list, and click Add.

   
   
   

2. Add a bond slave.
   1. On the bond configuration page, click Add to add a bond slave.

      
      
      

   2. On the displayed Choose a Connection Type page, choose a bond slave connection type from the drop-down list, for example, Ethernet and then click Create...

      
      
      

   3. On the Ethernet tab of the Editing bond0 slave1 page, select a bond slave device from the Device drop-down list, for example, ens3 (MAC address). Then, configure settings or use the default settings for the other parameters. After you complete the settings, click Save.

      
      
      

3. Select a bond mode.

   From the Mode drop-down list of the Bond tab, select the bond mode as need, such as Active backup. Then, configure settings or use the default settings for the other parameters. After you complete the settings, click Save.

   
   
   

4. Disable the IPv4 settings of the original NIC.
   • On the Ethernet (ens3) page, choose Configure... > IPv4 Settings. On the tab, set Method to Disabled and then click Save.

   • 
     
     

5. Complete the network bonding configurations.
   Note:

   Make sure that you turn on the On switch on the bond configuration tab and configure the IP address. In addition, make sure that you turn on the On switch for the bond slave, for example, ens3. Otherwise, you might fail to install ZStack Cloud properly.

   
   
   

6. Configure a static IP address for bond device.
   1. On the INSTALLATION SUMMARY page, choose NETWORK & HOST NAME > Bond (bond0) > Configure.... Then the Bond (bond0) page is displayed. On the page, choose IPv4 Settings > Method > Manual. Then you can manually assign an IP address.
      Note: You can also use DHCP to automatically obtain an IP address.
   2. Click Add to add an IP entry, configure the IP address, subnet, and gateway, and then click save to save the configurations.
7. Configure NIC auto-activation.
   On the Bond (bond0) page, choose General > Connect automatically with priority (0) > Save. Then the auto-activation is enabled.

   
   
   

ZStack Cloud Custom ISO Installation Mode

Auto-Install ZStack Cloud on Management Node

If you select Enterprise or Community Management Node Mode, the system automatically restarts and installs ZStack Cloud on the management node.

Considerations

Technically, a management node can manage unlimited compute nodes. Note that the number of compute nodes that you can use is limited by the quota authorized in the license.

Considerations

The expert mode supports simplified installation. After you select ZStack Expert Mode on the left pane, you can select No ZStack Local Repo on the right pane to implement simplified installation.

Note: In simplified expert mode, the ISO file in the /opt/zstack-dvd/ directory is not copied and configuration files such as zstack-local.repo are not generated in the /etc/yum.repos.d/ directory.

Considerations before Upgrade

Offline Upgrading

1. Before you implement ZStack Cloud offline upgrading as the admin, you need to prepare the following installation package. We recommend that you save the installation package or script in the /root/ directory.
   • ZStack Cloud ISO:
     • h84r: ZStack-Cloud-x86_64-DVD-4.8.38-h84r.iso
     • Download address: Click here
   • Installation Package
   • ZStack Cloud installation package:
     • Software: ZStack-Cloud-installer-4.8.38.bin
     • Download address: Click here
   Note: After the software packages are downloaded, you need to use an MD5 checker to check whether the MD5 hashes of the packages are consistent with the ones listed on the official website.
2. Before you upgrade as the admin, you need to back up the database.
   • Run the following command to back up the database:

     [root@zstack-1 ~]# zstack-ctl dump_mysql --file-name zstack-mysql-before-upgrade

     Note:

     • After you run the command, a database backup is created in the /var/lib/zstack/mysql-backup/ directory.
     • During the upgrading, ZStack Cloud proxy server is upgraded. Data stored on the primary storage and backup storage is not affected.
   • You can also use Backup Service of ZStack Cloud to implement scheduled backup of the database.
     Note:

     • Backup Service is provided in an independent module. You need to purchase the Backup Service Plus License, in addition to the Base License.
3. Run the following command as the admin to upgrade the management service of ZStack Cloud:

   # Two offline upgrading methods are supported. The first one is recommended:
   # First method: Upgrade the local repo and management service simultaneously:
   [root@zstack-1 opt]# zstack-upgrade ZStack-Cloud-x86_64-DVD-4.8.38-h84r.iso
   # Second method: Upgrade the local repo first and then the management service:
   [root@localhost ~]# zstack-upgrade -r ZStack-Cloud-x86_64-DVD-4.8.38-h84r.iso
   [root@localhost ~]# bash ZStack-Cloud-installer-4.8.38.bin -u -P MYSQL_ROOT_PASSWORD

   Note:

   • If the root password of the database is the default password, you do not need to specify -P MYSQL_ROOT_PASSWORD.
   • Before you run the zstack-upgrade command, make sure that you use ISO of the h84r version instead of other versions.
   • While upgrading the local repo, the upgrade script is auto-updated. When the update is completed, rerun the preceding command.