• You can obtain the usage of physical resources, such as processors, memories, storages, and networks in the Cloud in real time. You only need to create VM instances and the Cloud will immediately send alarms if resources are insufficient.
• The Cloud allows you to copy templates before you create VM instances.
• After you create a VM instance, the Cloud allows you to set or change the relevant IP address.
• The Cloud supports flat networks, vRouter networks, and VPC networks. You can quickly set up flexible and diverse network scenarios as needed with simple clicks in the UI.
• The Cloud can take over vCenter. Specifically, the Cloud can manage both KVM and VMware clusters at the same time. In addition, the Cloud supports the V2V migration of VM instances from vCenter to ZStack.
• The Cloud allows different accounts to see different VM instances.
• The Cloud supports advanced features such as billing.
• You can directly add firewalls to VM instances on the Cloud and set various security policies, which is simple and convenient.
• The Cloud supports advanced features, such as enterprise management, bare metal management, V2V migration, and backup service.

• Release Notes:

  The release notes briefly describe the new features provided by ZStack during each release and detail the changes or enhancements made to the Cloud.

• Product Manuals:

  The product manuals include the User Guide, Maintenance Manual, Technical Whitepaper, CLI Command Manual, and CTL Command Manual. These manuals describe the functional architecture, functional advantages, installation and deployment, how to use the Cloud, and solutions to common problems during the O&M of ZStack. You will find a new world if you explore ZStack by using CLI.

• Tutorials:

  We provide you with many tutorials that cover various application scenarios, for example, Quick Start Installation Tutorial, Upgrade Tutorial, Multi-MN HA Tutorial, and V2V Migration Tutorial. With these tutorials, you can get started quickly and easily.

• API Reference:

  The API Reference, as the core of ZStack, helps you gain in-depth insight of ZStack from the API level.

• FAQ:

  The FAQ provides answers to a list of frequently asked questions during the use of the Cloud.

• Blogs:

  The blogs provide a place where you can voice your ideas and share your thoughts on ZStack as well as the cloud computing industry. Here, you can expand your horizon and have a more thorough understanding of IaaS.

1. ZStack Enterprise Management Node

   Install the ZStack Custom ISO that is deeply customized based on CentOS 7.4 or CentOS 7.6 as well as the ZStack Enterprise management node.

2. ZStack Community Management Node

   Install the ZStack Custom ISO that is deeply customized based on CentOS 7.4 or CentOS 7.6 as well as the ZStack Community management node.

3. ZStack Compute Node

   Install the ZStack Custom ISO that is deeply customized based on CentOS 7.4 or CentOS 7.6 as well as the essential software package of ZStack compute node.

4. ZStack Expert Node

   Install the ZStack Custom ISO that is deeply customized based on CentOS 7.4 or CentOS 7.6 and configure the local repo. You can customize the system usage as needed.

• Incremental upgrade:
  1. Obtain the latest bin installation package from ZStack Official Website: ZStack-installer-3.10.0.bin.
  2. If the root password of the database is the default password, run the following command to upgrade the Cloud:

     [root@localhost ~]# bash ZStack-installer-3.10.0.bin -u

     If the root password of the database is a custom non-blank password, run the following command to upgrade the Cloud:

     [root@localhost ~]# bash ZStack-installer-3.10.0.bin -u -P MYSQL_ROOT_PASSWORD

• Offline upgrade:
  1. Obtain the latest ISO installation package from ZStack Official Website: ZStack-x86_64-DVD-3.10.0-c76.iso.
  2. Obtain the latest upgrade script: Upgrade script.
  3. Run the following command to upgrade the Cloud:

     [root@localhost ~]# bash zstack-upgrade ZStack-x86_64-DVD-3.10.0-c76.iso

Note: The method to upgrade the c74 version is the same as that of the c76 version. Please obtain the installation package corresponding to the c74 version to upgrade.

[root@localhost ~]# yum --disablerepo=* --enablerepo=zstack-local install zstack-manager [root@localhost ~]# bash ZStack-installer-3.10.0.bin -E

[root@localhost ~]# yum --disablerepo=* --enablerepo=zstack-local,qemu-kvm-ev groupinstall zstack-host

[root@localhost ~]# rpm -e zstack-host [root@localhost ~]# yum --disablerepo=* --enablerepo=zstack-local install zstack-manager [root@localhost ~]# bash ZStack-installer-3.10.0.bin -E

1. Run the following command to delete the original database:

   [root@localhost ~]# rm -rf /usr/local/zstack

   Note: This command will delete all the data under this directory. You can use this command only when you want to completely reinstall ZStack.
2. Then, run the following command to reinstall the management node:

   [root@localhost ~]# bash ZStack-installer-3.10.0.bin -D #Install ZStack Enterprise.

• Symptom:
  When you install ZStack, you use root for login. However, when you start the service, the system reports that you are not a root user and sudo is required.

  ERROR: please use sudo or root user FAIL  Reason: failed to start zstack

  When you run the following command in a Python CLI environment, you find that Python determined that you are not a root user.

  import getpass  user = getpass.getuser()  print user 

• Cause:

  When you switch from a regular user to a root user, you used su instead of sudo su. In this case, only the root user is switched but relevant environment variables are not switched.

• Description:
  • The sudo command can be used by the current user with the root super permission.
  • The su command can be used to switch to a root user. However, the relevant environment variables are not switched to the root directory.
  • The sudo su command is used to switch to a root user with the root permission.

• Cause:

  The startup time of the management node is related to the configuration resources of the node. The startup takes a long time only when you install ZStack on a VM instance.

• Solution:
  We recommend that you use more than 4 CPUs and 16 GB memory in a virtualization environment.

  Note:

  The startup takes a long time does not indicate that the installation or startup fails. If a time out error is reported, use zstack-ctl status to check the status. If the status is stopped, use zstack-ctl start to start the service. If the status is unknown, use zstack-ctl stop to stop the service, and then use zstack-ctl start to start the service.

[root@localhost ~]# bash zstack-installer.bin -r /home/zstack

• Symptom:
  If the new version of ZStack Custom ISO does not match the old one during the upgrade, the following error message will be reported:

  mount: /dev/loop0 is write-protected, mounting read-only /root Current release c76 not matched the new ISO c74, Use zstack-upgrade -r xxx.iso to update current repo, Use zstack-upgrade -a/--add_repo xxx.iso to add a new repo

• Cause:

  The current ISO version used by the system is not suitable for upgrading the installation package. You need to upgrade the corresponding ISO and then upgrade ZStack.

• Solution:
  Follow these steps to perform the deployment. Here, we take c76 as an example.

  1. Run the following command to download the latest upgrade script:

     wget http://cdn.zstack.io/product_downloads/scripts/zstack-upgrade

  2. Run the following command to download the latest ISO in the management node:

     wget http://cdn.zstack.io/product_downloads/iso/ZStack-x86_64-DVD-3.10.0-c76.iso

  3. Perform the upgrade. That is, upgrade the yum repo in the ISO and synchronize it to your local server. Then, directly upgrade the management node.

     bash zstack-upgrade ZStack-x86_64-DVD-3.10.0-c76.iso

• Prerequisite:

  During the upgrade of ZStack, the core files and database of the current ZStack are backed up to the corresponding directory by default.

• Procedure:
  1. Back up the core files in ZStack of the previous version.

     cp /usr/local/zstack/upgrade/2017-11-09-15-41-52 /root -r

  2. Back up the database of the previous version.

     cp /usr/local/zstack/db_backup/2017-11-09-15-42-43/backup.sql /root

  3. Back up the database again.

     zstack-ctl dump_mysql

  4. Delete the current ZStack environment.

     zstack-ctl stop rm -rf /usr/local/zstack

  5. Use the previous installation package to directly install ZStack.

     bash ZStack-installer-3.10.0.bin -D

  6. Perform recovery by using the core files backed up in Step 1.

     zstack-ctl stop mv /usr/local/zstack/apache-tomcat/webapps/zstack /usr/local/zstack/apache-tomcat/webapps/zstack-bk cp /root/2017-11-09-15-41-52/zstack /usr/local/zstack/apache-tomcat/webapps  -r chown zstack:zstack /usr/local/zstack/apache-tomcat/webapps/zstack -R

  7. Restore the database backed up in Step 2.

     cat /root/backup.sql |mysql -u root -p zstack.mysql.password zstack

  8. Start the ZStack management node service. Then, ZStack is successfully restored to the previous version.

     zstack-ctl start

• Cause: The versions earlier than ZStack 3.5.0 use Prometheus 1.8.2, which might cause the monitoring data to occupy the root space.
  Note: ZStack 3.5.0 and later versions use Prometheus 2.9.2, which allow you to set the retention policy. (By default, 50 GB monitoring data can be saved.)
• Solution: If the monitoring data is no longer needed, permanently delete the Prometheus monitoring data to release the space.
  • In a single management node environment, run the following commands in sequence to delete the Prometheus monitoring data:

    [root@hostname ~]# du -sh /var/lib/zstack/prometheus/data/    //View the monitoring data size. [root@hostname ~]# zstack-ctl stop  [root@hostname ~]# kill -9 `ps -ef |grep prometheus|awk '{print $2}'`  [root@hostname ~]# rm -rf /var/lib/zstack/prometheus/data [root@hostname ~]# zstack-ctl start

  • In a dual-MN environment, run the following commands in each management node to delete the Prometheus monitoring data:

    [root@mn-1 ~]# du -sh /var/lib/zstack/prometheus/data/    //View the monitoring data size. [root@mn-1 ~]# zsha2 stop-node [root@mn-1 ~]# kill -9 `ps -ef |grep prometheus|awk '{print $2}' [root@mn-1 ~]# rm -rf /var/lib/zstack/prometheus/data [root@mn-1 ~]# zsha2 start-node

1. If the system reports that the user name or password is incorrect, enter the correct user name and password.
2. If the system reports that you could not connect to the management node, run the zstack-ctl status command to check whether the management node service is running properly.
3. If you still could not connect to the management node, perform login via cli.

   [root@localhost ~]# zstack-cli  #Go to the CLI mode. admin>>> LogInByAccount accountName=admin password=password #Log in to the CLI. Default user name/password: admin/password.

4. Check whether the related Java process cannot run due to zombies in the process. If yes, restart the management node service.

• UI method:

  On the Homepage of ZStack, click the admin icon, and then click Change Password.

• CTL method:
  Run the following command:

  [root@localhost ~]# zstack-ctl reset_password --password NEW_PASSWORD #Change the password. (NEW_PASSWORD is the new password.)

• CLI method:
  Run the following commands in sequence:

  [root@localhost ~]# zstack-cli  #Go to the CLI mode. admin>>> LogInByAccount accountName=admin password=password #Log in to the CLI. Default user name/password: admin/password. admin>>> UpdateAccount uuid=36c27e8ff05c4780bf6d2fa65700f22e password=NEW_PASSWORD #Change the password. (NEW_PASSWORD is the new password.)

[root@localhost ~]# zstack-ctl config_ui --server-port 8888  #Change the UI port to 8888. [root@localhost ~]# zstack-ctl config_ui --webhook-port 8888  #Change the webhook host port to 8888. [root@localhost ~]# zstack-ctl stop_ui  #Stop the UI service. [root@localhost ~]# zstack-ctl start_ui  #Start the UI service.

• UI method:

  Go to Settings > Global Settings > Basic Settings, locate Session.timeout, and set a value as needed.

• CLI method:
  Run the following commands in sequence:

  [root@localhost ~]# zstack-cli  #Go to the CLI mode. admin>>> LogInByAccount accountName=admin password=password #Log in to the CLI. Default user name/password: admin/password. admin>>> UpdateGlobalConfig name=session.timeout category=identity value=720000 #Change the session timeout to 200 hours.

• UI method:

  Go to Settings > Global Settings > Advanced, locate Session.maxConcurrent, and set a value as needed.

• CLI method:
  1. Run the QueryGlobalConfig name~=session command. Then, you will find that the maximum number of allowed concurrent sessions is 500.

     {             "category": "identity",             "defaultValue": "500",             "description": "Max number of sessions management server accepts. \ When this limit met, new session will be rejected",             "name": "session.maxConcurrent",             "value": "500"  }

  2. If you want to change the value to 1000, run the following command:

     UpdateGlobalConfig category=identity name="session.maxConcurrent" value=1000

[root@localhost ~]# zstack-ctl configure locale=en_US   #Switch the language. Note that en_US indicates English, and zh_CN indicates Chinese. [root@localhost ~]# zstack-ctl restart_node   #Restart the management node for the configuration to take effect.