ZStack Cloud Platform
Single Server, Free Trial for One Year
-
Documentation&Tools
Comprehensive product documentation and tools
-
Support & Services
Upholding the value of Customer First and the mission of Serving Customer, ZStack is dedicated to providing secure and stable services for customers.
-
Training & Certification
To educate ZStack partners and interested individuals about cloud computing and to cultivate cloud computing talent.
-
Content
ZStack provides innovative cloud infrastructure for ten major industries
VMware-to-ZStack Case Collection
The report provides three major
solutions and customer case studies for transitioning from VMware to ZStack.
ZStack ZSphere 4.10.10>ZStack ZSphere Documentation>ZStack ZSphere User Guide>Install ZStack ZSphere
Install ZStack ZSphere
This chapter mainly describes how to install and deploy the ZStack ZSphere virtualization platform.
Deployment Scenarios
ZStack ZSphere provides three installation modes: management node mode, compute node mode, and expert mode.
The installation content, applicable scenarios, and installation steps vary for different installation modes.
| Modes | Description | Applicable Scenarios |
|---|---|---|
| Management Node Mode |
| Suitable for installing the management node. |
| Compute Node Mode |
| Suitable for installing other nodes in the virtualization platform excluding the management node, such as:
|
| Expert Node Mode |
|
Planning and Prerequisites
Hardware Requirements
The configuration of server CPU, memory, storage size, and NIC performance determines the business capacity of the ZStack ZSphere.
- Minimum Environment (All In One): Requires at least 4 CPU cores and at least 8 GB of memory. This is only suitable for basic demonstration environments and not recommended for production use.
- Production Environment:
- Management Node Configuration: Determined by deployment scale and user environment, please consult official technical support for details. For small-scale scenarios, the recommended configuration for the management node is: 8 CPU cores, 16 GB of memory, and 240 GB of storage.
- Compute Node Configuration: Determined by business scale, please consult official technical support for details.
Recommended Configurations for Server Hardware
Whether for minimum environment deployment or production environment deployment, it is recommended that hardware devices such as servers be configured according to the recommended configurations in the table below:
| Device | Component | Configuration Requirements |
|---|---|---|
| Server | CPU | x86 Environment: 64-bit x86 architecture, supporting Intel VT or AMD-V hardware virtualization features (for example, Intel's VMX or AMD/Hygon's SVM). ARM Environment: 64-bit ARM architecture, supporting hardware virtualization features. |
| Memory | No special requirements. Recommends DDR4 or higher performance memory. | |
| Motherboard | Standard dual-socket server motherboard. | |
| RAID Card | Supports SAS/SATA RAID 0/1/10 and supports passthrough mode. | |
| Hard Disk | No special requirements. You can choose between HDD or SSD based on storage planning. | |
| Network Port |
| |
| Network Switch | - |
|
When preparing your server hardware, make sure to configure the following:
- Enable CPU virtualization support in the server BIOS.
- Complete your storage planning in advance:
- If you use local storage, it is recommended to adopt a storage redundancy backup solution (for example, configure 4 hard disks in RAID 10) to improve the reliability of data storage and image storage. If your virtual machines require very high I/O read/write performance, consider using a RAID configuration with all SSDs. If the I/O access of your virtual machines leans more towards read performance, a mixed configuration of SSDs and HDDs can also work well.
- If you use NFS or distributed storage, configure the corresponding storage or file system in advance. If your image storage uses a distributed image storage, ensure that your data storage also uses distributed storage.
- Plan your network in advance: It is recommended that you consistently name all physical host NICs and use NICs with the same name to carry the same type of communication traffic. For example, management traffic should all use the em1 NICs.
- Complete the necessary configurations on your network switch in advance:
- If you need to use a VLAN network environment, configure the corresponding VLAN network communication on the switch in advance.
- ZStack ZSphere will actively allocate IP addresses to your virtual machines, so reserve a range of IP addresses that do not conflict with your system, and avoid conflicts with existing DHCP services in your network environment.
Next Chapter: Getting Started Through Wizard