Management Component Installation Environment Requirements
Before installing the xSpace management component, please ensure that the infrastructure resource pool is ready. You can use your existing IaaS environment and create a dedicated project within it (some platforms refer to this as a "virtual machine group") to deploy the management component virtual machines.
1. Supported Cloud Platform Requirements
Please confirm that the underlying cloud platform (IaaS) version meets the following requirements before installation:
| Cloud Platform Type | Version Requirement |
|---|---|
| InCloud | >= 6.5.2 |
| OpenStack | >= Train |
| SmartX | >= 4.4.0 |
| UCloud | >= 2.12 |
| WxStack | >= 8.0.1 |
| WxVDI Cloud | >= 4.5 |
| ZStack | >= 4.8.10 |
| nDeskHCI | >= 4.5 |
| nSSV/nCSSV | >= 4.8.10 |
2. Virtual Machine Configuration Specifications
The management component defaults to a clustered deployment architecture, requiring 3 virtual machines to be created in the aforementioned project. Specific configuration requirements are as follows:
2.1 Hardware Specifications and Performance
- Operating System: Must be openEuler 22.03.
- Image Recommendation: It is strongly recommended to use the image provided in the version release directory. The default login account for this image is
root. Please consult the vendor's technical support for the password. If a third-party image is used, compatibility issues such as missingtarpackages orsysctl -pfailures may occur, requiring additional installation and adjustments. - Processor and Memory: Virtual machine configuration should be no less than 8 cores and 16GB RAM. Please avoid severe CPU over-subscription to prevent insufficient actual computing power.
- Disk Space: The root partition size of the system disk must be at least 150G (total system disk size recommended to be 200G).
- Disk Structure Requirements: It must be ensured that the independent space of the root partition is no less than 150G, and it cannot be assembled by mounting multiple small-capacity disks (e.g., 100G system disk + 100G data disk). For third-party images, it is recommended to use LVM for root partition management for future expansion. If space is insufficient, please refer to online resources to expand the system disk, logical volume, and filesystem size yourself.
- Disk I/O Performance: The management component includes middleware with high IOPS requirements, such as databases. It is recommended to deploy on SSD physical drives, and strictly forbidden to use HDD drives. If deployment is slow, please monitor the
waindicator (I/O wait) using thetopcommand.
2.2 Network and Clock Configuration
- Static IP: The IP address of the virtual machine is not allowed to be changed after installation. If it is a dynamically assigned address, it must be manually configured as a static IP within the system.
- DNS Configuration: Please configure a valid DNS server in each virtual machine.
- Clock Synchronization: If a clock server is available in the environment, please configure and enable synchronization in the Master virtual machine.