Registering a Linux ISO File as a Private Image

Scenarios

Register an external ISO file on the cloud platform as a private image (ISO image). Before registering an image, upload the ISO file to the OBS bucket.

An ISO image cannot be replicated or exported.

Prerequisites

• The file to be registered must be in ISO format.
• The ISO image file has been uploaded to the OBS bucket. For details, see Upload an Image File.
  

  The ISO image file name can contain only letters, digits, hyphens (-), and underscores (_). If the image file name does not meet the requirements, change the name before uploading the image file to the OBS bucket.

Procedure

1. Log in to the IMS console.
2. Register an ISO file as an ISO image.
   1. Click Create Image in the upper right corner.
   2. Set image parameters as required.

      Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.

      Figure 1 Image type and source
      

      Table 1 Parameters for configuring the image type and source

      Parameter	Description	Example Value
      Region	Resources in different regions cannot communicate with each other over an intranet. For low latency and fast access, select a region close to where your services will be provided.	-
      Type	Private images can be created or imported.	Import Image
      Image Type	A private image contains an OS or service data, preinstalled public applications, and a user's personal applications. Private images are only available to the users who created them. A private image can be a system disk image, data disk image, ISO image, or full-ECS image. A system disk image contains an OS and preinstalled software for various services. You can use a system disk image to create ECSs and migrate your services to the cloud. A data disk image contains only service data. You can use a data disk image to create EVS disks and use them to migrate your service data to the cloud. An ISO image is created from an external ISO image file. It is a special image that is not available on the ECS console. It can only be used to provision temporary cloud servers. A full-ECS image contains an OS, preinstalled software, and service data. A full-ECS image is created using differential backups and the creation takes less time than creating a system or data disk image that has the same disk capacity.	ISO image
      Select Image File	Select the bucket storing the image file from the bucket list and then select the image file. NOTE: Only image files that have been uploaded to a Standard OBS bucket can be used to create private images, and each image file cannot exceed 128 GiB. The format and size of the new image may be different from the source image file. Before creating an image, ensure that VirtIO drivers have been integrated into the Windows ISO file. For details, see Integrating VirtIO Drivers into an ISO File.	-

      Figure 2 Image information
      

      Table 2 Parameters for configuring image information

      Parameter	Description	Example Value
      Architecture	The value can be x86 or ARM. NOTE: If the system identifies that the architecture in the image file is different from what you set here, the identified architecture will be used. If the system fails to identify an architecture, the architecture you set will be used.	x86
      Boot Mode	This parameter is optional. Select the same boot mode as that in the image file, or the ECS created using this image cannot be booted. After you select the boot mode, the cloud platform will configure the corresponding boot settings for the image. The boot mode can be BIOS or UEFI. For details about the differences between them, see How Is BIOS Different from UEFI? For details about which OSs support UEFI boot, see OSs supporting UEFI Boot Mode. NOTE: If the image file uses the Arm architecture, only the UEFI mode is available.	BIOS
      OS	To ensure that the image can be created and used properly, select an OS consistent with that in the image file. If you do not select an OS, the system attempts to automatically identify the OS in the image file. NOTE: If the system identifies that the OS in the image file is different from the one you select here, the identified OS will be used. If the system fails to identify an OS, the OS you select will be used. If the OS you selected or the OS identified by the system is different from the actual OS, the performance of the ECSs created using the image file may be affected.	-
      System Disk	Set the system disk capacity (value range: 40 GiB to 1,024 GiB). This value must be no less than the size of the system disk in the image file. NOTE: If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity by referring to Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger Than What I Specified on the Management Console?	-
      Name	Set an image name that is easy to identify.	-
      Encryption	This parameter is optional. If you want to encrypt the image, select KMS encryption and select the key to be used from the key list. After you select KMS encryption, the system will create a default key ims/default. You can also select a key from the key list. For details about how to encrypt an image, see Introduction.	-
      Enterprise Project	This parameter is for enterprise users. To use this function, contact customer service to enable it. An enterprise project groups cloud resources, so you can manage resources and users by project. The default project is default. Select an enterprise project from the drop-down list. For more information, see Accessing the Enterprise Center.	default
      Tag	This parameter is optional. Set tag keys and values for the image to make identification and management easier. You are advised to create predefined tags in TMS. For details, see Creating Predefined Tags. NOTE: If your organization has configured tag policies for images, you need to add tags to your images based on the policies. Otherwise, tags may fail to be added. For details about image tag format, see Image Tag Format.	-
      Description	This parameter is optional. Enter a description for the image.	-
      Agreement	Read and agree to the Image Disclaimer	-

   3. Click Next. Confirm the settings and click Submit.

3. Switch back to the Image Management Service page to check the image status.

   When the image status changes to Normal, the image is registered successfully.