Image Management Service

Service Overview

Issue 14 Date 2021-08-17

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Contents

1 What Is Image Management Service?...... 1 2 Product Advantages...... 5 3 Application Scenarios...... 7 4 Features...... 8 5 Constraints...... 13 6 Supported OSs...... 17 6.1 OSs Supported by Different Types of ECSs...... 17 6.2 Formats and OSs Supported for External Image Files...... 24 6.3 OSs Supporting UEFI Boot Mode...... 29 7 Billing...... 31 8 Permissions Management...... 33 9 Basic Concepts...... 36 9.1 Region and AZ...... 36 9.2 Common Image Formats...... 37 10 Related Services...... 40 11 Change History...... 43

1 What Is Image Management Service?

Overview An image is a server or disk template that contains an operating system (OS) or service data and necessary software, such as database software. IMS provides public, private, Marketplace, and shared images. Image Management Service (IMS) allows you to manage the entire lifecycle of your images. You can create ECSs or BMSs from public, private, or shared images. You can also create a private image from a cloud server or an external image file to make it easier to migrate workloads to the cloud or on the cloud.

Image Types Images are classified as public, private, Marketplace, and shared. Public images are provided by the cloud platform, private images are those you created yourself, and shared images are private images that other tenants have shared with you. Figure 1-1 illustrates the relationships among different types of images.

Figure 1-1 Image types

Image Type Description

Public image A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. Public images are very stable and their OS and any included software have been officially authorized for use. If a public image does not contain the application environments or software you need, you can use a public image to create an ECS and then deploy required software as needed. Public images support the following OSs: Windows, CentOS, Debian, openSUSE, Fedora, Ubuntu, EulerOS, and CoreOS. For more information about public images, see Managing Public Images.

Image Type Description

Private A private image contains an OS or service data, preinstalled image 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, or full-ECS image. ● A system disk image contains an OS and pre-installed 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. ● A full-ECS image contains an OS, pre-installed 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 of the same size.

Shared A shared image is a private image another user has shared with image you. For more information about shared images, see Sharing Images.

Marketplace The Marketplace is an online store where you can purchase image third-party images that have the OS, application environments, and software preinstalled. You can use these images to deploy websites and application development environments in just a few clicks. No additional configuration is required. Marketplace images are provided by service providers who have extensive experience in configuring and maintaining cloud servers. All the images are thoroughly tested and have been approved by HUAWEI CLOUD before being published.

IMS Functions IMS provides: ● Public images that contain common OSs ● Creation of a private image from an ECS or external image file ● Public image management, such as searching for images by OS type, name, or ID, and viewing the image ID, system disk size, and image features such as user data injection and disk hot swap ● Private image management, such as modifying image attributes, sharing images, and replicating images ● Creation of ECSs using an image

Access Methods The public cloud provides a web-based service management platform (a management console). You can access the IMS service through HTTPS APIs or from the management console. ● API If you need to integrate IMS into a third-party system for secondary development, use APIs to access the IMS service. For details, see Image Management Service API Reference. ● Management console If no integration with a third-party system is needed, use the management console. Log in to the management console and choose Computing > Image Management Service on the homepage. If you do not have an account, sign up for one before logging in to the management console. For details about how to register an account, see Account Registration Process.

2 Product Advantages

IMS provides convenient, secure, flexible, and efficient image management. Images allow you to deploy services faster, more easily and more securely.

Saving Time and Effort ● Deploying services on cloud servers is much faster and easier when you use images. ● A private image can be created from an ECS, an external image file, or the system disk or data disks of an ECS or BMS. ● Private images can be transferred between accounts, regions, or cloud platforms through image sharing, replication, and export.

Secure ● Public images use Huawei EulerOS and mainstream OSs such as Windows Server, Ubuntu, and CentOS. These OSs have been thoroughly tested to provide secure and stable services. ● Multiple copies of image files are stored on Object Storage Service (OBS), which provides excellent data reliability and durability. ● Private images can be encrypted for data security by using envelope encryption provided by Key Management Service (KMS).

Flexible ● You can manage images through the management console or using APIs. ● You can use a public image to deploy a general-purpose environment, or use a private image or Marketplace image to deploy a custom environment. ● You can use IMS to migrate servers to the cloud or on the cloud, and back up server running environments.

Unified ● IMS provides a self-service platform to simplify image management and maintenance. ● IMS allows you to batch deploy and upgrade application systems, improving O&M efficiency and ensuring consistency.

● Public images comply with industry standards. Pre-installed components only include clean installs, and only kernels from well-known third-party vendors are used to make it easier to transfer images from or to other cloud platforms.

Comparison Between Image-based Deployment and Manual Deployment

Table 2-1 Image-based deployment and manual deployment Item Image-based Deployment Manual Deployment

Time required 2 to 5 minutes 1 to 2 days

Complexity Quickly create ECSs by using Select an appropriate OS, public images, Marketplace database, and various software images, or private images. packages based on your service requirements. Then, install and commission them.

Security You only need to identify The security depends on the sources of shared images. skills of the R&D or O&M Public, private, and personnel. Marketplace images have been strictly tested to ensure security and stability.

3 Application Scenarios

● Migrating servers to the cloud or on the cloud You can import local images to the cloud platform and use the images to quickly create cloud servers for service migration to the cloud. A variety of image types can be imported, including VHD, VMDK, QCOW2, and RAW. You can also share or replicate images across regions to migrate ECSs between accounts and regions. ● Deploying a specific software environment Use shared or Marketplace images to quickly build custom software environments without having to manually configure environments or install any software. This is especially useful for Internet startups. ● Batch deploying software environments Prepare an ECS with an OS, the partition arrangement you prefer, and software installed to create a private image. You can use the image to create batch clones of your custom ECS. ● Backing up server environments Create an image from an ECS to back up the ECS. If the ECS breaks down due to software faults, you can use the image to restore the ECS.

4 Features

Private Image Lifecycle After you create a private image, you can use the image to create ECSs or EVS disks. You can also share the image with other tenants or replicate the image to other regions. Figure 4-1 shows the lifecycle of a private image.

Figure 4-1 Private image lifecycle

Features

Table 4-1 Creating a private image Feature Description Helpful Link

Creating a After creating a cloud server, you ● Creating a System system disk can set it up, installing whatever Disk Image from a image from an software or application Windows ECS ECS or BMS environment you need and then ● Creating a System use the preconfigured server to Disk Image from a create a system disk image. You Linux ECS can create new cloud servers with the custom configurations from ● Creating a Private the image, which frees you from Image from a BMS a lot of repetitive work.

Creating a You can import a system disk ● Creating a Windows system disk from your local PC or other cloud System Disk Image image from an platforms, and use the imported from an External external image image to create new cloud Image File file servers or reinstall or change the ● Creating a Linux OSs of existing cloud servers. System Disk Image from an External Image File ● Creating a BMS Private Image from an External Image File ● Quickly Importing an Image File

Creating a In contrast with other image ● Creating a Windows system disk formats, an ISO file can be used System Disk Image image from an only after it is decompressed from an ISO File ISO file using a tool, such as UltraISO or ● Creating a Linux VirtualBox. For details about the System Disk Image image creation process, see the from an ISO File Related Operations column in the table. ● Creating a Windows Image Using VirtualBox and an ISO File ● Creating a Linux Image Using VirtualBox and an ISO File

Feature Description Helpful Link

Creating a Packer is an open-source tool Creating a Private system disk that can be used to create Image Using Packer image using custom images. It simplifies Packer private image creation by changing the image creation process to a form in which management code can be configured. In this way, users can flexibly customize images as needed.

Creating a data A data disk image only contains Creating a Data Disk disk image user data. You can create a data Image from an ECS from an ECS disk image from an ECS and then use the image to create new EVS disks. This is a convenient way to migrate data from an ECS to EVS disks.

Creating a data You can import the data disk Creating a Data Disk disk image image of a local server or a server Image from an External from an on another cloud platform to Image File external image HUAWEI CLOUD and then the file image can be used to create EVS disks.

Creating a full- You can use an ECS with data ● Creating a Full-ECS ECS image disks to create a full-ECS image, Image from an ECS from an ECS, complete with an OS, various ● Creating a Full-ECS CSBS backup, applications, and your service Image from a CSBS or CBR backup data. The full-ECS image then can Backup be used to quickly provision identical ECSs for data migration. ● Creating a Full-ECS Image from a CBR A full-ECS image can be created Backup by using an ECS, CSBS backup, or CBR backup.

Creating an After a system disk image or full- Creating an ECS from an ECS from a ECS image is created, you can Image private image click Apply for Server in the row that contains the image to create an ECS.

Table 4-2 Managing private images Feature Description Helpful Link

Modifying an To facilitate private image Modifying an Image image management, you can modify the following attributes of an image: name, description, minimum memory, maximum memory, and advanced functions such as NIC multi-queue and SR-IOV driver.

Sharing images You can share an image with other ● Sharing Images HUAWEI CLOUD accounts. These ● Image Sharing accounts can use your shared private FAQs image to quickly create ECSs or EVS disks.

Exporting You can export private images to Exporting an Image images your OBS bucket and download them to your local PC for backup.

Encrypting You can create encrypted images to ● Encryption images improve data security. The encryption Method mode is KMS envelope encryption. ● Creating Encrypted images can be created Encrypted Images from external image files or encrypted ECSs.

Replicating By replicating images within a Replicating Images images within region, you can convert encrypted Within a Region a region and unencrypted images into each other or enable some advanced features, for example, quick ECS provisioning.

Replicating You can replicate private images Replicating Images images across created in one region to another Across Regions regions region. Cross-region image replication is supported within a single account. Shared images can be replicated across regions between different accounts.

Tagging an You can tag your private images for Tagging an Image image easy management and search.

Exporting You can export the public or private Exporting Image List image list image list in a given region in CSV format, facilitating local maintenance and query.

Feature Description Helpful Link

Deleting You can delete images that will be Deleting Images images no longer used. Deleting an image does not affect the ECSs created from that image.

5 Constraints

This section describes the constraints on using IMS.

Table 5-1 Constraints Scenario Item Constraint

Creating a Maximum number 50 private of private images If you need to create more than 50 private image that can be created images, submit a service ticket to increase in a region your quota. For details, see How Do I Increase the Image Quota?

Maximum number 40 of concurrent tasks for creating private images

Creating a system ● The ECS must be in the Stopped or disk image from an Running state. ECS or BMS ● The BMS must be in the Stopped state and must be booted from an EVS disk rather than a local disk.

Creating a system For details about constraints on external disk image from an image files, see Preparing an Image File external image file (Windows) or Preparing an Image File (Linux).

Creating a system ● Register the ISO file as an ISO image, disk image from an use the ISO image to create a ISO file temporary ECS, install an OS and related drivers on the ECS, and use the ECS to create a system disk image. ● The ISO image cannot be replicated, exported, or encrypted.

Scenario Item Constraint

Creating a data disk ● The ECS must be in the Stopped or image from an ECS Running state. ● A data disk image can be used to create a data disk for an ECS only once. ● The data disk capacity of the ECS must be less than 2 TB and the data that has been stored on the disk must be less than 1 TB.

Creating a data disk The destination data disk can be 40–2048 image from an GB, and it must also be at least as big as external image file the data disk in the image file.

Creating a full-ECS ● The ECS must be in the Stopped or image from an ECS Running state. or a CSBS or CBR ● A CSBS or CBR backup can be used to backup create only one full-ECS image at a time. ● A full-ECS image cannot be published in the Marketplace or be exported. ● A full-ECS image can only be replicated across regions. ● A full-ECS image is shareable with other tenants only when it is created from a CBR backup or from an ECS that has never had a CSBS backup.

Creating an ● An encrypted image cannot be shared encrypted image with other tenants, published in the from an encrypted Marketplace, or replicated across ECS or an external regions. image file ● The key used for encrypting an image cannot be changed.

Sharing an Maximum number System disk image or data disk image: 128 image of tenants an image Full-ECS image: 10 can be shared with

Maximum number No limit of shared images that a tenant can receive

Private image status Normal

Scenario Item Constraint

Image sharing ● The images published in the Marketplace and the full-ECS images created from a CSBS backup cannot be shared with others. ● You can share images only within the region where they reside. To make an image available in a different region, replicate the image to the region and then share it. ● A shared image can be used to create an ECS only in the same region.

Replicating Maximum size of an 128 GB an image image

Maximum number 5 of concurrent replication tasks per tenant

Private image status Normal

Replicating images Neither the private images created from within a region ISO files nor the full-ECS images support in-region replication.

Replicating images ● A new replication task can be created across regions only after the previous replication task is complete. ● Encrypted images do not support cross- region replication.

Exporting Maximum size of an 1 TB images exported image Images larger than 128 GB only support fast export. For details about fast export, see Comparison Between Import and Fast Import, and Between Export and Fast Export.

Formats of exported VMDK, VHD, QCOW2, ZVHD, and ZVHD2 image files

Private image status Normal

Scenario Item Constraint

Exporting images ● Windows and SUSE public images as well as private images created from these public images cannot be exported. ● If a Marketplace image is used to create an ECS and then the ECS is used to create a private image, this private image cannot be exported. ● Both private images created from ISO files and full-ECS images cannot be exported. ● Encrypted images cannot be exported through fast export.

Deleting Private image status A released private image cannot be images deleted.

Creating Number of ECSs Recommended value: ≤ 100 ECSs that can be concurrently created using a system disk image

Tagging an Maximum number 10 image of tags that can be added to a private image

Other Constraints ● If an ECS is frozen due to overdue payment, it cannot be used to create a private image. You must renew the ECS before using it to create a private image. ● A private image created from an x86 ECS cannot be used to create a Kunpeng ECS or change the OS of a Kunpeng ECS. ● When you use an external image file to create a private image and select x86 for Architecture, the private image cannot be used to create a Kunpeng ECS or change the OS of a Kunpeng ECS. ● A private image containing a 32-bit OS cannot be used to create an ECS with 4 GB of memory because the total available address space for a 32-bit OS is 4 GB.

6 Supported OSs

6.1 OSs Supported by Different Types of ECSs This section describes the OSs supported by different types of ECSs. ● x86 ECSs ● Kunpeng ECSs x86 ECSs ● Table 6-1 lists the OSs supported by the following ECSs: General-purpose T6 General computing S2, S3, S6, and SN3 General computing-plus C3 Memory-optimized M2, M3, and M6 High-performance computing HC2 and H3 Disk-intensive D2 and D3 ● Table 6-2 lists the OSs supported by the following ECSs: General computing-plus C3ne, C6, and C6s Memory-optimized M3ne ● Table 6-3 lists the OSs supported by the following ECSs: Large-memory E3 ● Table 6-4 lists the OSs supported by the following ECSs: Ultra-high I/O I3 and IR3 ● For other GPU-accelerated ECSs, see the GPU product description. NO TE

It is recommended that you use the official OS release versions. Do not tailor or customize the release versions, or problems may occur. OS vendors do not always update OS release versions regularly. Some versions are no longer maintained, and these deprecated versions no longer receive security patches. Ensure that you read the update notifications from OS vendors and update your OS so that it runs properly.

Table 6-1 Supported OS versions-01 OS OS Version

Windows Windows Server 2008 R2 Standard/Enterprise/Datacenter/Web Windows Server 2012 Standard/Datacenter Windows Server 2012 R2 Standard/Datacenter Windows Server 2016 Standard/Datacenter Windows Server 2019 Standard/Datacenter Windows Server Core Version 1709

CentOS 64-bit: CentOS 6.10, 6.9, 6.8, 6.7, 6.6, 6.5, 6.4, and 6.3 64-bit: CentOS 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, and 7.0 64-bit: CentOS 8.0

Ubuntu 64-bit: Ubuntu 20.04, 18.04, 16.04, 14.04, and 12.04 Server

EulerOS 64-bit: EulerOS 2.5, 2.3, and 2.2

Red Hat 64-bit: Red Hat 6.10, 6.9, 6.8, 6.7, 6.6, 6.5, and 6.4 64-bit: Red Hat 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, and 7.0 64-bit: Red Hat 8.0

SUSE Linux Enterprise 64-bit: SLES 11 SP4 and 11 SP3 64-bit: SLES 12 SP4, 12 SP3, 12 SP2, 12 SP1, and 12 64-bit: SLES 15

Debian 64-bit: Debian 8.0.0–8.10.0 64-bit: Debian 9.8.0, 9.7.0, 9.6.0, 9.5.0, 9.4.0, 9.3.0, and 9.0.0

openSUSE 64-bit: openSUSE 13.2 64-bit: openSUSE Leap 15.1 and 15.0 64-bit: openSUSE Leap 42.3, 42.2, and 42.1

Fedora 64-bit: Fedora 22–29

CoreOS 64-bit: CoreOS 2079.4.0

FreeBSD 64-bit: FreeBSD 11.0

openEuler 64-bit: openEuler 20.03

Table 6-2 Supported OS versions-02 OS OS Version Kernel Version

Windows Windows Server 2008 R2 10.0.14393 Enterprise/Datacenter/Web/ 6.1.7600 Standard 6.0.6002 Windows Server 2012 R2 Standard/Datacenter 6.1.7600 Windows Server 2016 6.3.9600 Standard/Datacenter Windows Server 2019 Datacenter Windows Server Version 1709 Datacenter

CentOS 64-bit: 2.6.32-754.10.1.e16.x86_64 CentOS 6 2.6.32-696.16.1.el6.x86_64 CentOS 7 2.6.32-754.10.1.el6.x86_64 CentOS 8 2.6.32-754.11.1.e16.x86_64 3.10.0-514.10.2.el7.x86_64 3.10.0-693.11.1.el7.x86_64 3.10.0-862.9.1.el7.x86_64 3.10.0-957.5.1.e17.x86_64 3.10.0-957.10.1.e17.x86_64

Ubuntu 64-bit: 4.15.0-52-56 Ubuntu 14.04 Server 4.4.0-151-178 Ubuntu 16.04 Server 4.4.0-104-generic Ubuntu 18.04 Server 4.4.0-141-generic Ubuntu 20.04 Server 4.4.0-142-generic 4.4.0-145-generic 4.15.0-34-generic 4.15.0-45-generic 4.15.0-47-generic

EulerOS 64-bit: 3.10.0-327.62.59.83.h162.x86_64 EulerOS 2.2 3.10.0-514.44.5.10.h198.x86_64 EulerOS 2.3 3.10.0-327.59.59.46.h38.x86_64 EulerOS 2.5 3.10.0-327.62.59.83.h96.x86_64 3.10.0-327.62.59.83.h128.x86_64 3.10.0-514.44.5.10.h121.x86_64 3.10.0-514.44.5.10.h142.x86_64

OS OS Version Kernel Version

Red Hat 64-bit: 2.6.32-358.6.2.el6.x86_64 Red Hat 6 2.6.32-431.20.3.el6 Red Hat 7 2.6.32-504.12.2.el6 2.6.32-573.el6.x86_64 2.6.32-696.1.1.el6.x86_64 2.6.32-696.10.2.el6.x86_64 2.6.32-754.el6.x86_64 3.10.0-229.1.2.el7.x86_64 3.10.0-327.36.1.el7.x86_64 3.10.0-514.36.1.el7 3.10.0-514.6.1.el7.x86_64 3.10.0-693.11.6.el7.x86_64 3.10.0-862.3.2.el7.x86_64

SUSE Linux 64-bit: 3.0.101-108.18-default Enterprise SLES 11 3.12.74-60.64.40-default SLES 12 4.4.103-92.53-default 4.4.120-92.70-default 4.4.121-92.92

Debian 64-bit: 4.9.168-1+deb9u3 Debian 8 3.2.0-4-686-pae Debian 9 3.2.0-4-amd64 3.16.0-4-amd64 4.9.0-3-amd64 4.9.0-4-amd64 4.9.0-8-amd64 4.9.0-9-amd64 4.19.0-5-amd64

openSUSE 64-bit: 4.4.103-18.41-default openSUSE 15.0 3.0.101-108.18-default openSUSE 15.1

Fedora 64-bit: 5.1.11-200.fc29.x86_64 Fedora 2x 4.5.5-300.fc24.x86_64 4.20.8-200.fc29.x86_64 5.2.8-200.fc30.x86_64 4.8.6-300.fc25.x86_64

openEuler 64-bit: 4.19.90-2003.4.0.0036.oel.x86_64 openEuler 20.03

Table 6-3 Supported OS versions-03 OS OS Version Kernel Version

CentOS 64-bit: 2.6.32-754.15.3.e16.x86_64 CentOS 6 2.6.32-696.16.1.el6.x86_64 CentOS 7 2.6.32-754.10.1.el6.x86_64 CentOS 8 2.6.32-754.11.1.e16.x86_64 3.10.0-514.10.2.el7.x86_64 3.10.0-693.11.1.el7.x86_64 3.10.0-862.9.1.el7.x86_64 3.10.0-957.21.3.e17.x86_64 3.10.0-957.5.1.e17.x86_64 3.10.0-957.10.1.e17.x86_64

Ubuntu 64-bit: 4.15.0-52-56 Ubuntu 14.04 Server 4.4.0-151-178 Ubuntu 16.04 Server 4.4.0-104-generic Ubuntu 18.04 Server 4.4.0-141-generic 4.4.0-142-generic 4.4.0-145-generic 4.15.0-34-generic 4.15.0-45-generic 4.15.0-47-generic

OS OS Version Kernel Version

SUSE Linux 64-bit: 3.0.101-108.18-default Enterprise SLES 11 3.12.74-60.64.40-default SLES 12 4.4.103-92.53-default 4.4.120-92.70-default 4.4.121-92.92

Debian 64-bit: 4.9.168-1+deb9u3 Debian 8 3.2.0-4-686-pae Debian 9 3.2.0-4-amd64 3.16.0-4-amd64 4.9.0-3-amd64 4.9.0-4-amd64 4.9.0-8-amd64 4.9.0-9-amd64 4.19.0-5-amd64

openSUSE 64-bit: 4.4.103-18.41-default openSUSE 15.0 3.0.101-108.18-default openSUSE 15.1

Fedora 64-bit: 5.1.11-200.fc29.x86_64 Fedora 2x 4.5.5-300.fc24.x86_64 4.20.8-200.fc29.x86_64 5.2.8-200.fc30.x86_64 4.8.6-300.fc25.x86_64

openEuler 64-bit: 4.19.90-2003.4.0.0036.oel.x86_64 openEuler 20.03

Table 6-4 Supported OS versions-04

OS OS Version Kernel Version

CentOS 64-bit: 2.6.32-754.15.3.e16.x86_64 CentOS 6 2.6.32-696.16.1.el6.x86_64 CentOS 7 2.6.32-754.10.1.el6.x86_64 2.6.32-754.11.1.e16.x86_64 3.10.0-514.10.2.el7.x86_64 3.10.0-693.11.1.el7.x86_64 3.10.0-862.9.1.el7.x86_64 3.10.0-957.21.3.e17.x86_64 3.10.0-957.5.1.e17.x86_64 3.10.0-957.10.1.e17.x86_64

Ubuntu 64-bit: 4.4.0-31-generic Ubuntu 14.04 Server 4.4.0-131-generic Ubuntu 16.04 Server 4.4.0-141-generic Ubuntu 18.04 Server 4.4.0-142-generic 4.15.0-29-generic 4.15.0-45-generic

SUSE Linux 64-bit: 4.4.103-92.53-default Enterprise SLES 12 4.4.120-92.70-default

Debian 64-bit: 3.16.0-7-amd64 Debian 8 3.16.0-4-amd64 Debian 9 4.9.0-3-amd64

Kunpeng ECSs

Table 6-5 lists the OSs supported by the following ECSs:

● Kunpeng general computing-plus KC1 ● Kunpeng memory-optimized KM1

Table 6-5 Supported OS versions-05

OS OS Version

CentOS 64-bit: CentOS 7.6, 7.5, and 7.4 64-bit: CentOS 8.0

Ubuntu 64-bit: Ubuntu 18.04 Server

OS OS Version

EulerOS 64-bit: EulerOS 2.8

Red Hat 64-bit: Red Hat 7.6 and 7.5

SUSE Linux Enterprise 64-bit: SLES 12 SP5 and SP4 64-bit: SLES 15

openSUSE 64-bit: openSUSE Leap 15.0

Fedora 64-bit: Fedora 29

Debian 64-bit: Debian 10.2.0

openEuler 64-bit: openEuler 20.03

6.2 Formats and OSs Supported for External Image Files

Supported File Formats Image files in VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ISO, ZVHD2, or ZVHD format can be used to create private images. Select whichever format best meeting your requirements.

Supported OSs When you upload an external image file to an OBS bucket on the management console, the OS contained in the image file will be checked. Table 6-6 lists the OSs supported for external image files. If the OS cannot be identified or is not supported: ● For Windows, Other_Windows (64_bit) or Other_Windows (32_bit) will be selected during image registration. ● For Linux, Other_Linux (64_bit) or Other_Linux (32_bit) will be selected during image registration.

NO TE

Uploading image files containing OSs not listed in Table 6-6 and Table 6-7 may fail. You are advised to contact the customer service before attempting to upload these image files.

Table 6-6 Supported OSs (x86) OS OS Version

Windows Windows 10 64bit Windows Server 2019 Standard 64bit Windows Server 2019 Datacenter 64bit Windows Server 2016 Standard 64bit Windows Server 2016 Datacenter 64bit Windows Server 2012 R2 Standard 64bit Windows Server 2012 R2 Essentials 64bit Windows Server 2012 R2 Datacenter 64bit Windows Server 2012 Datacenter 64bit Windows Server 2012 Standard 64bit Windows Server 2008 WEB R2 64bit Windows Server 2008 R2 Standard 64bit Windows Server 2008 R2 Enterprise 64bit Windows Server 2008 R2 Datacenter 64bit

SUSE SUSE Linux Enterprise Server 15 SP1 64bit SUSE Linux Enterprise Server 15 64bit SUSE Linux Enterprise Server 12 SP5 64bit SUSE Linux Enterprise Server 12 SP4 64bit SUSE Linux Enterprise Server 12 SP3 64bit SUSE Linux Enterprise Server 12 SP2 64bit SUSE Linux Enterprise Server 12 SP1 64bit SUSE Linux Enterprise Server 11 SP4 64bit SUSE Linux Enterprise Server 11 SP3 64bit SUSE Linux Enterprise Server 11 SP3 32bit

Oracle Linux Oracle Linux Server release 7.6 64bit Oracle Linux Server release 7.5 64bit Oracle Linux Server release 7.4 64bit Oracle Linux Server release 7.3 64bit Oracle Linux Server release 7.2 64bit Oracle Linux Server release 7.1 64bit Oracle Linux Server release 7.0 64bit Oracle Linux Server release 6.10 64bit Oracle Linux Server release 6.9 64bit Oracle Linux Server release 6.8 64bit Oracle Linux Server release 6.7 64bit Oracle Linux Server release 6.5 64bit

OS OS Version

Red Hat Red Hat Linux Enterprise 8.0 64bit Red Hat Linux Enterprise 7.6 64bit Red Hat Linux Enterprise 7.5 64bit Red Hat Linux Enterprise 7.4 64bit Red Hat Linux Enterprise 7.3 64bit Red Hat Linux Enterprise 7.2 64bit Red Hat Linux Enterprise 7.1 64bit Red Hat Linux Enterprise 7.0 64bit Red Hat Linux Enterprise 6.10 64bit Red Hat Linux Enterprise 6.9 64bit Red Hat Linux Enterprise 6.8 64bit Red Hat Linux Enterprise 6.7 64bit Red Hat Linux Enterprise 6.6 64bit Red Hat Linux Enterprise 6.6 32bit Red Hat Linux Enterprise 6.5 64bit Red Hat Linux Enterprise 6.4 64bit Red Hat Linux Enterprise 6.4 32bit

Ubuntu Ubuntu 20.04 Server 64bit Ubuntu 19.04 Server 64bit Ubuntu 18.04.2 Server 64bit Ubuntu 18.04.1 Server 64bit Ubuntu 18.04 Server 64bit Ubuntu 16.04.6 Server 64bit Ubuntu 16.04.5 Server 64bit Ubuntu 16.04.4 Server 64bit Ubuntu 16.04.3 Server 64bit Ubuntu 16.04.2 Server 64bit Ubuntu 16.04 Server 64bit Ubuntu 14.04.5 Server 64bit Ubuntu 14.04.4 Server 64bit Ubuntu 14.04.4 Server 32bit Ubuntu 14.04.3 Server 64bit Ubuntu 14.04.3 Server 32bit Ubuntu 14.04.1 Server 64bit Ubuntu 14.04.1 Server 32bit Ubuntu 14.04 Server 64bit Ubuntu 14.04 Server 32bit

OS OS Version

openSUSE openSUSE 42.3 64bit openSUSE 42.2 64bit openSUSE 42.1 64bit openSUSE 15.1 64bit openSUSE 15.0 64bit openSUSE 13.2 64bit openSUSE 11.3 64bit

CentOS CentOS 8.0 64bit CentOS 7.9 64bit CentOS 7.8 64bit CentOS 7.7 64bit CentOS 7.6 64bit CentOS 7.5 64bit CentOS 7.4 64bit CentOS 7.3 64bit CentOS 7.2 64bit CentOS 7.1 64bit CentOS 7.0 64bit CentOS 7.0 32bit CentOS 6.10 64bit CentOS 6.10 32bit CentOS 6.9 64bit CentOS 6.8 64bit CentOS 6.7 64bit CentOS 6.7 32bit CentOS 6.6 64bit CentOS 6.6 32bit CentOS 6.5 64bit CentOS 6.5 32bit CentOS 6.4 64bit CentOS 6.4 32bit CentOS 6.3 64bit CentOS 6.3 32bit

OS OS Version

Debian Debian GNU/Linux 10.0.0 64bit Debian GNU/Linux 9.3.0 64bit Debian GNU/Linux 9.0.0 64bit Debian GNU/Linux 8.10.0 64bit Debian GNU/Linux 8.8.0 64bit Debian GNU/Linux 8.7.0 64bit Debian GNU/Linux 8.6.0 64bit Debian GNU/Linux 8.5.0 64bit Debian GNU/Linux 8.4.0 64bit Debian GNU/Linux 8.2.0 64bit Debian GNU/Linux 8.1.0 64bit

Fedora Fedora 30 64bit Fedora 29 64bit Fedora 28 64bit Fedora 27 64bit Fedora 26 64bit Fedora 25 64bit Fedora 24 64bit Fedora 23 64bit Fedora 22 64bit

EulerOS EulerOS 2.9 64bit EulerOS 2.5 64bit EulerOS 2.3 64bit EulerOS 2.2 64bit EulerOS 2.1 64bit

openEuler openEuler 20.03 64bit

NeoKylin NeoKylin 7.4 64bit NeoKylin Server release 5.0 U2 64bit NeoKylin Linux Advanced Server release 7.0 U5 64bit

Table 6-7 Supported OSs (ARM)

OS OS Version

CentOS CentOS 7.6 64bit CentOS 7.5 64bit CentOS 7.4 64bit

OS OS Version

EulerOS EulerOS 2.8 64bit

Fedora Fedora 29 64bit

Ubuntu Ubuntu 19.04 Server 64bit Ubuntu 18.04 Server 64bit

SUSE SUSE Linux Enterprise Server 12 SP5 64bit

openEuler openEuler 20.03 64bit

NeoKylin NeoKylin V7 64bit

UnionTech UOS 20 64bit

6.3 OSs Supporting UEFI Boot Mode The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI? Table 6-8 lists the OSs that support the UEFI boot mode.

Table 6-8 OSs supporting UEFI boot mode OS OS Version

Windows Windows Server 2019 Datacenter 64bit

Windows Server 2019 Standard 64bit

Windows Server 2016 Standard 64bit

Windows Server 2016 Datacenter 64bit

Windows Server 2012 R2 Standard 64bit

Windows Server 2012 R2 Datacenter 64bit

Windows Server 2012 Essentials R2 64bit

Windows Server 2012 Standard 64bit

Windows Server 2012 Datacenter 64bit

Windows 10 64bit

Ubuntu Ubuntu 19.04 Server 64bit

Ubuntu 18.04 Server 64bit

Ubuntu 16.04 Server 64bit

Ubuntu 14.04 Server 64bit

OS OS Version

Red Hat Red Hat Linux Enterprise 7.4 64bit

Red Hat Linux Enterprise 7.3 64bit

Red Hat Linux Enterprise 7.1 64bit

Red Hat Linux Enterprise 7.0 64bit

Red Hat Linux Enterprise 6.9 64bit

Red Hat Linux Enterprise 6.6 32bit

Red Hat Linux Enterprise 6.5 64bit

Oracle Linux Oracle Linux Server release 7.4 64bit

Oracle Linux Server release 6.9 64bit

openSUSE openSUSE 42.1 64bit

SUSE SUSE Linux Enterprise Server 12 SP5 64bit

SUSE Linux Enterprise Server 12 SP1 64bit

SUSE Linux Enterprise Server 11 SP3 64bit

Fedora Fedora 29 64bit

Fedora 24 64bit

Debian Debian GNU/Linux 8.8.0 64bit

CentOS CentOS 7.6 64bit

CentOS 7.5 64bit

CentOS 7.4 64bit

CentOS 7.0 64bit

CentOS 6.9 64bit

CentOS 6.6 64bit

EulerOS EulerOS 2.8 64bit

EulerOS 2.5 64bit

EulerOS 2.3 64bit

EulerOS 2.2 64bit

openEuler openEuler 20.03 64bit

NeoKylin NeoKylin V7 64bit

UnionTech UOS 20 64bit

7 Billing

Billing of Different Image Types Image Type Billing

Public Only Windows Server public images are billed. Other public images are free.

Private When you create a private image, you will be billed for the storage on CSBS or CBR. ● System disk image or data disk image: OBS buckets invisible to users are provided for free to store the images. ● Full-ECS image: If the image is created from a CSBS or CBR backup, you will be billed for the space used to store the CSBS or CBR backup.

Shared ● If it is a system or data disk image, the OBS storage is free. ● If it is a full-ECS image, you will be billed for the space used to store the CBR backup. NOTE Full-ECS images created from a CBR backup can be shared but those created from a CSBS backup cannot.

Marketplace Determined by the image provider.

Billing of Private Image Operations Operation Billing Item

Uploading an external OBS storage (You are advised to delete unneeded image file to an OBS image files.) bucket

Operation Billing Item

Creating an ECS from a EVS disks attached to the created ECS (The system system disk image or full- disk image and full-ECS image are free of charge.) ECS image For example, when you use a full-ECS image (with a 40 GB system disk and 100 GB data disk) to create an ECS, you will be charged based on the total size of the system disk and data disk.

In-region replication of a None. OBS buckets are available for free to store system or data disk image the image copies.

Cross-region replication of Traffic generated by OBS cross-region replication a system or data disk image

Cross-region replication of ● Traffic of CSBS or CBR cross-region replication a full-ECS image ● Space used for storing the CSBS or CBR backup associated with the newly replicated image

Exporting images OBS space for storing the exported images

Reference ● For OBS pricing details, see OBS Pricing Details. ● For CSBS pricing details, see CSBS Pricing Details. ● For CBR pricing details, see CBR Pricing Details. ● For EVS pricing details, see EVS Pricing Details.

8 Permissions Management

If you need to grant different permissions to employees in your enterprise to access your IMS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your resources.

With IAM, you can use your account to create IAM users for your employees, and grant permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use IMS resources but must not delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using IMS resources.

If your account does not require individual IAM users for permissions management, skip this section.

IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.

IMS Permissions

By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign policies or roles to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on cloud services based on the permissions.

IMS is a project-level service deployed and accessed in specific physical regions. When you grant IMS permissions to a user group, set Scope to Region-specific projects and then select projects (for example, ap-southeast-2) for the permissions to take effect. If you select All projects, the permissions will take effect for the user group in all region-specific projects. Before you access IMS, switch to a region where you have been authorized to use IMS.

You can grant user permissions by using roles and policies.

● Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the

permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.

Table 8-1 System-defined IMS roles

Role Description Dependency

IMS Administrator permissions This role depends on the Administrator for IMS Tenant Administrator role.

Server Permissions for creating, This role depends on the Administrator deleting, querying, IMS Administrator role modifying, and uploading in the same project. images

● Policies (recommended): A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy- based authorization, meeting requirements for secure access control. For example, you can grant IMS users only the permissions for managing a certain type of image resources. Most policies define permissions based on APIs. For the API actions supported by IMS, see Permission Policies and Supported Actions.

Table 8-2 System-defined IMS policies

Policy Description Dependency

IMS FullAccess All permissions of IMS None

IMS Read-only permissions for IMS. None ReadOnlyAccess Users granted these permissions can only view IMS data.

Table 8-3 lists common operations and their required system-defined IMS permissions.

Table 8-3 Common operations and required system-defined permissions

Action IMS FullAccess IMS IMS Administrator ReadOnlyAccess (Depending on Tenant Administrator)

Creating an √ x √ image

Deleting an √ x √ image

Action IMS FullAccess IMS IMS Administrator ReadOnlyAccess (Depending on Tenant Administrator)

Querying an √ √ √ image

Updating image √ x √ information

Helpful Links ● What Is IAM?

9 Basic Concepts

9.1 Region and AZ

Concept

A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

● Regions are divided based on geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region. Regions are classified into universal regions and dedicated regions. A universal region provides universal cloud services for common tenants. A dedicated region provides specific services for specific tenants. ● An AZ contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected using high- speed optical fibers to support cross-AZ high-availability systems.

Figure 9-1 shows the relationship between regions and AZs.

Figure 9-1 Regions and AZs

HUAWEI CLOUD provides services in many regions around the world. Select a region and AZ based on requirements. For more information, see HUAWEI CLOUD Global Regions.

Selecting a Region

When selecting a region, consider the following factors:

● Location It is recommended that you select the closest region for lower network latency and quick access. Regions within the Chinese mainland provide the same infrastructure, BGP network quality, as well as resource operations and configurations. Therefore, if your target users are on the Chinese mainland, you do not need to consider the network latency differences when selecting a region. – If your target users are in Asia Pacific (excluding the Chinese mainland), select the CN-Hong Kong, AP-Bangkok, or AP-Singapore region. – If your target users are in Africa, select the AF-Johannesburg region. – If your target users are in Europe, select the EU-Paris region. – If your target users are in Latin America, select the LA-Santiago region.

NO TE

The LA-Santiago region is located in Chile. ● Resource price Resource prices may vary in different regions. For details, see Product Pricing Details.

Selecting an AZ

When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.

● For high DR capability, deploy resources in different AZs within the same region. ● For lower network latency, deploy resources in the same AZ.

Regions and Endpoints

Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.

9.2 Common Image Formats

IMS supports multiple image formats, but the system uses ZVHD or ZVHD2 by default.

Table 9-1 lists the common image formats.

Table 9-1 Common image formats Image Description Remarks Format

ZVHD ZVHD is a format developed by A universal format HUAWEI CLOUD. This format uses supported by IaaS the ZLIB compression algorithm and OpenStack; a format supports sequential read and write. supported for imported and exported images

ZVHD2 ZVHD2 is a format developed by A format for the lazy HUAWEI CLOUD. This format uses loading feature; a format the ZSTD algorithm and supports supported for imported lazy loading. images

QCOW2 This is a disk image supported by A format supported for the QEMU simulator. It is a file that imported and exported indicates a block device disk of a images fixed size. Compared with the RAW format, the QCOW2 format has the following features: ● Supports a lower disk usage. ● Supports Copy-On-Write (CoW). The image file only reflects disk changes. ● Supports snapshots. ● Supports zlib compression and encryption by following Advanced Encryption Standard (AES).

VMDK VMDK is a virtual disk format from A format supported for VMware. A VMDK file represents a imported and exported physical disk drive of the virtual images machine file system (VMFS) on an ECS.

VHD VHD is a virtual disk file format A format supported for from Microsoft. A VHD file is a imported and exported compressed file stored in the file images system of the host machine. It mainly contains a file system required for starting ECSs.

Image Description Remarks Format

VHDX VHDX is a new VHD format A format supported for introduced into Hyper-V of Windows imported images Server 2012 by Microsoft. Compared with the VHD format, VHDX has a larger storage capacity. It provides protection against data damage during power supply failures, and the disk structure alignment has been optimized to prevent performance degradation of new physical disks in a large sector.

RAW A RAW file can be directly read and A format supported for written by ECSs. This format does imported images not support dynamic space expansion and has the best I/O performance.

QCOW QCOW manages the space A format supported for allocation of an image through the imported images secondary index table. The secondary index uses the memory cache technology and needs the query operation, which results in performance loss. The performance of QCOW is inferior to that of QCOW2, and the read and write performance is inferior to that of RAW.

VDI VDI is the disk image file format A format supported for used by the VirtualBOX imported images virtualization software from Oracle. It supports snapshots.

QED The QED format is an evolved A format supported for version of the QCOW2 format. Its imported images storage location query mode and data block size are the same as those of the QCOW2 format. However, QED implements Copy- On-Write (CoW) in a different way as it uses a dirty flag to replace the reference count table of QCOW2.

10 Related Services

Figure 10-1 shows the relationships between IMS and other services.

Figure 10-1 IMS relationships with other services

Table 10-1 Related services Service Relationship with Related Operation IMS

Elastic Cloud Server You can use an ● Creating an ECS from an (ECS) image to create Image ECSs or use an ECS ● Creating a System Disk to create an image. Image from a Windows ECS ● Creating a System Disk Image from a Linux ECS ● Creating a Full-ECS Image from an ECS

Bare Metal Server (BMS) You can use an ● Creating a BMS from a image to create Private Image BMSs or use a BMS ● Creating a Private Image to create an image. from a BMS ● Creating a Private Image from an External Image File

Object Storage Service Images are stored in ● Uploading an External (OBS) OBS buckets. Image File (Windows) External image files ● Exporting an Image to be uploaded to the system are stored in OBS buckets, and private images are exported to OBS buckets.

Data Encryption Images can be Encrypting Images Workshop (DEW) encrypted through envelope encryption of DEW to ensure data security. The keys used for encrypting images are stored in DEW.

Elastic Volume Service You can create a Creating a Data Disk Image (EVS) data disk image from an ECS using a data disk of an ECS. The created data disk image can be used to create other EVS disks.

Cloud Server Backup You can use a CSBS Creating a Full-ECS Image Service (CSBS) backup to create a from a CSBS Backup full-ECS image.

Service Relationship with Related Operation IMS

Cloud Backup and You can use a CBR Creating a Full-ECS Image Recovery (CBR) backup to create a from a CBR Backup full-ECS image.

Tag Management Service You can add tags to Tagging an Image (TMS) images for convenient classification and search.

Cloud Trace Service CTS records IMS IMS Operations Recorded by (CTS) operations for CTS query, auditing, or backtracking.

11 Change History

Released On Description

2021-08-17 This issue is the fourteenth official release. Modified the following content: ● In Constraints, added the following constraints: – The system disk capacity of the ECS or BMS used to create a system disk image must be no greater than 1 TB. – The data disk capacity of the ECS used to create a data disk image must be no greater than 1 TB.

2021-06-15 This issue is the thirteenth official release. Added the following content: ● Permissions Management Modified the following content: ● Added CentOS 8, openEular, and EulerOS 2.5 to the OSs supported by E3 ECSs in OSs Supported by Different Types of ECSs.

2021-03-08 This issue is the twelfth official release. Modified the following content: ● Added a constraint on creating a data disk image from an ECS in Constraints.

2020-08-18 This issue is the eleventh official release. Added EulerOS 2.9 64bit in Formats and OSs Supported for External Image Files.

2020-06-16 This issue is the tenth official release. Added openEuler 20.03 64bit in Formats and OSs Supported for External Image Files.

Released On Description

2020-04-30 This issue is the ninth official release. Added the following supported OSs in Formats and OSs Supported for External Image Files: SUSE Linux Enterprise Server 12 SP5 64bit and SUSE Linux Enterprise Server 15 SP1 64bit.

2020-02-29 This issue is the eighth official release. Added the following supported OSs in Formats and OSs Supported for External Image Files: Ubuntu 19.04 Server 64bit, Oracle Linux Server release 6.10 64bit, CentOS 6.10 32bit, and CentOS 8.0 64bit.

2019-10-30 This issue is the seventh official release. Added the following content: ● Product Advantages ● Application Scenarios ● Features ● Constraints Modified the following content: Added the relationship diagram in Related Services.

2019-08-31 This issue is the sixth official release. Added the description of the LA-Santiago region in Region and AZ.

2019-08-10 This issue is the fifth official release. ● Added the OSs supported for Kunpeng ECSs in OSs Supported by Different Types of ECSs. ● Optimized the description for regions and AZs in Region and AZ.

2019-06-15 This issue is the fourth official release. Added the following content: ● OSs Supporting UEFI Boot Mode ● Region and AZ Modified the following content: Rectified the OS versions supported by all ECS types in OSs Supported by Different Types of ECSs.

2019-04-30 This issue is the third official release. Added supported OSs in Formats and OSs Supported for External Image Files, including Ubuntu 18.04.2 Server 64bit, Ubuntu 18.04.1 Server 64bit, Ubuntu 16.04.6 Server 64bit, Ubuntu 16.04.5 Server 64bit, Ubuntu 16.04.4 Server 64bit, Windows Server 2019 Standard 64bit, Windows Server 2019 Datacenter 64bit, and NeoKylin 7.4 64bit.

Released On Description

2019-02-25 This issue is the second official release. Modified the following content: ● Related Services ● OSs Supported by Different Types of ECSs ● Billing

2018-11-20 This issue is the first official release.