Skip to content

Management Component Image Preparation Guide

Before officially creating the xSpace management component (AS6) virtual machines, a compliant operating system image needs to be prepared. The management component's operating environment is strictly limited to openEuler 22.03.

1. Image Acquisition Methods

It is strongly recommended to use the openEuler images provided in the version release directory.

  • Advantages: System kernel parameters, disk partitioning, and necessary dependency packages have been pre-optimized and pre-installed, which significantly increases deployment success rates.
  • Account Information: The default login account is root. Please refer to the documentation in the image download path or consult vendor technical support for the initial password.

1.2 Manual Image Creation (Alternative)

If you need to create an image from an official openEuler ISO, please note the following requirements:

  • ISO Download: Please download the openEuler Offline Standard ISO from official channels.
  • Architecture Matching:
    • x86_64: Applicable to servers based on Intel or Hygon processors.
    • aarch64: Applicable to ARM servers based on Kunpeng or Phytium processors.

2. Image Customization and Dependency Package Installation

If you choose to create images manually, please complete the following standardized configurations in the image template:

2.1 Storage Partitioning Plan

  • Total System Disk: Recommended 200G.
  • Root Partition (/): Size must not be less than 150G.
  • Management Specifications: It is recommended to use LVM (Logical Volume Management) structure for online expansion later as the business grows. Do not use a "system disk + data disk" combination to meet the root partition space requirements.

2.2 Install Core Tools

Based on the openEuler 22.03 minimal system, the tar tool package must be installed, otherwise the installer will not be able to decompress the bin package.

  • Online Installation:
  yum install -y tar
  • Offline Installation: If in an environment without external network access, please download the corresponding RPM package from the version release directory in advance and install it manually:
    • x86 Architecture: tar-1.34-5.oe2203sp4.x86_64.rpm
    • ARM Architecture: tar-1.34-5.oe2203.aarch64.rpm

3. Key Operating Mode Considerations

When you upload the prepared image to the underlying cloud platform and configure the image properties, please pay attention to the following settings:

3.1 Boot Mode (BIOS Mode)

  • Images Included in Release Directory: Use the Legacy boot mode. When creating virtual machines on the cloud platform, it is strictly forbidden to select UEFI boot, otherwise the system will not be able to boot.

On the OpenStack platform, when uploading images, keep the hw_firmware_type and hw_machine_type attributes as default, i.e.:

hw_firmware_type = bios
hw_machine_type = pc
  • Manually Created Images: Please ensure that the cloud platform's boot mode (Legacy/UEFI) is consistent with the mode you selected when creating the image.

3.2 Disk I/O Type

  • Bus Protocol: Given that the management component includes high-performance components such as databases, it is recommended to set the disk bus to VirtIO in the cloud platform image properties to obtain optimal I/O performance.
  • Physical Medium: Ensure that the physical storage layer where the image resides uses SSD, to avoid installation failures due to insufficient HDD performance. ```