Installation and Deployment
Environment Preparations
Before you install ZStack ZStone, prepare the following software
packages:
- ZStack Cloud ISO of the latest version (H76C, at least in
expert mode).
Note: You can use Rufus (recommended) or UltraISO to burn the
prepared ISO file to a U disk. For instructions on how to use Rufus, refer
to the first chapter in Quick Installation and Usage
Tutorial. - ZStack Cloud Enterprise toolkit: Contact official technical support to obtain it.
- ZStack Cloud Management Node HA Suite: Contact official technical support to obtain it.
- ZStack ZStone software package: Contact official technical support to obtain it.
Install ZStack ZStone
This topic describes the deployment mode of ZStack ZStone
5.5.6. ZStack ZStone provides the
following deployment modes:
- Default Deployment
- Hyper-Converged Infrastructure Deployment
Different deployment modes apply to different installation scenarios.
| Mode | Scenario |
|---|---|
| Default Deployment | We recommend using this mode in environments where ZStack Cloud is already deployed. |
| Hyper-Converged Infrastructure Deployment | When deploying a hyper-converged infrastructure (HCI) on ZStack Cube, skip deploying storage resources because they are provided by default. |
Default Deployment
As mentioned above, we recommend using this mode in environments where ZStack Cloud is already deployed.
ZStack ZStone management services depend on ZStack Cloud management node services. Therefore, you must first deploy
management nodes on ZStack Cloud before configuring management node
services on ZStack ZStone. Follow these steps:
- Deploy two management nodes in ZStack Cloud and configure
the HA policy.
Note: These two management nodes can serve as ZStack ZStone management nodes, providing you with
management services. - Deploy a compute node or a node in expert node on ZStack Cloud.
Note: This node, together with the two management
nodes mentioned above, can serve as a storage server node on ZStack ZStone, providing you with storage
services. - On any management node, download ZStack ZStone installation package.
- Decompress the installation
package.
# Check the obtained installation package [root@localhost ~]# ls ZStone-x86_64-installer-5.5.6.tar.gz # Decompress the installation package [root@localhost ~]# tar xf ZStone-x86_64-installer-5.5.6.tar.gz - After decompression, navigate to the zstone-installer
directory.
[root@localhost ~]# cd zstone-installer - Modify and edit the install.conf
file.
[root@localhost zstone-installer]# vim install.conf # Leave the management node IP if only one manager is deployed; enter the VIP for dual management nodes. zstone_vip= # ZStone Manager hosts list. Separate the IP addresses of dual management nodes with commas. zstone_managerment_host_ip= # Management node SSH port. The default is 22. zstone_managerment_host_port=22 # Management node root passwords. Format: ["password1","password2"] zstone_managerment_host_rootpw=["password"] # MySQL info zstone_db=zstone zstone_db_user=root zstone_db_port=3306 zstone_db_password=zstack.mysql.password # Indicates whether to perform a custom database installation. # If set to false, the default cloud database will be used. zstone_master_db_customed_use=false # Required. Specifies the database type: mariadb or greatsql. # Only effective when zstone_master_db_customed_use is set to true. zstone_master_customed_db=mariadb # virtual_router_id for keepalived, must be unique in the network, and must be the same for all hosts. # Range: 1-255 zstone_master_keepalived_virtual_router_id=230 # Required. Specifies the host management network interface. # Only effective when zstone_master_db_customed_use is set to true. zstone_master_vrrp_interface=ens3 # Log level: trace, debug, info, warning, error, fatal, panic log_level=info # Language used for alarms. The default is zh_CN. Options: en_US, zh_CN default_language=zh_CN # PostgreSQL info zstone_temporal_db_port=5432 # ZStone account zstone_account_name=admin zstone_account_password=password # Cloud VIP zstone_identify_server_ip= # The default is /zstack/v1. Change it if necessary. zstone_identify_url_prefix= # ZCF License Server info # zstone_license_server_type can be set to zs or ls. Empty is reserved for upgrade compatibility; new installations default to ls. zstone_license_server_type=ls # An empty host defaults to zstone_vip; an empty port defaults to 18201. zstone_license_server_host= zstone_license_server_port= # An empty protocol is auto-detected by type: ls uses https, and zs uses http. zstone_license_server_protocol= # LS quota type: Auto, Host, or Capacity. Auto first uses Host and falls back to Capacity. # An empty value is treated as Auto by ZStone for upgrade compatibility. zstone_license_server_quota_type= # LS offline protection max days. The range is 0-15, and the default is 7. zstone_license_server_max_offline_days=7 # LS HTTPS CA file path zstone_license_server_ca_path=/opt/zstone/license/ls_ca.pem # Built-in LS certificate SAN zstone_license_server_tls_server_name=license.server.zstack.org # Global site access key zstone_license_server_site_access_key=zstack-license-site-global-access-key # ZBS # Set this to true to install high-performance block storage. zbs_install=false # ZBS ChunkServer storage engine: fs (filesystem, for testing) or block (raw block device, recommended for production). chunkserver_backend=block - After saving the configuration information, return to the current directory and
run the following command to install the software
package.
[root@localhost zstone-installer]# ./install.sh - Upon successful installation, you will receive the ZStack ZStone UI URL.
Hyper-Converged Infrastructure Deployment
When deploying a hyper-converged infrastructure (HCI) on ZStack Cube, skip deploying storage resources on ZStack ZStone because the distributed storage service is provided by default.
