Updated on 2025-03-31 GMT+08:00

Overview

Introduction

To ensure an iMetal server can work properly on the management console, you need to install an OS for it. You can use an image for OS installation. Before that, you need to register an image file as an IMS private image on Huawei Cloud.

This section describes how to create a private image. You can create one based on your OS type.

You can also install software as needed to customize your private image.

Constraints

  • Only Linux servers can be used to create images.
  • Only x86 images are supported.
  • You can create a private image for an iMetal server by importing an image file.

    The image file format can be VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, or ZVHD.

  • The image file size cannot exceed 128 GB.
    If an image file is between 128 GB and 1 TB, convert it into RAW or ZVHD2 format and import it using fast import.
  • For details about the supported OSs, see External Image File Formats and Supported OSs.

Procedure

You can create an image in either of the following ways:

  • Scenario 1: If no image file has been exported from the original server or VM, install and configure Cloud-Init and network-related services on the original server or VM, export an image file, and upload the image file to an OBS bucket. Then register the image file as a private image for iMetal servers.

    Figure 1 shows the process of creating a private image.

    Figure 1 Creating a system disk image (scenario 1)

    For details, see Scenario 1: No Image File Exported from the Original Server or VM.

  • Scenario 2: An image file (in VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, or ZVHD format) has been exported from the original server or VM. You need to use the image file to create an ECS on Huawei Cloud. After installing and configuring tools such as Cloud-Init and network-related services on the ECS, use the ECS to create a private image for iMetal servers.
    Figure 2 shows the process of creating a private image.
    Figure 2 Creating a system disk image (scenario 2)

    For details, see Scenario 2: External Image File Exported from the Original Server or VM.