Scenarios
When optimizing a Linux private image, you need to install native KVM drivers on the ECS. If the drivers have been installed, skip this section.
-
If you do not install KVM drivers, NICs of the ECS may not be detected and the ECS cannot communicate with other resources.
+ If you do not install KVM drivers, NICs of the ECS may not be detected and the ECS cannot communicate with other resources.
Prerequisites
- The ECS needs to be optimized. For details, see Checking Whether a Private Image Needs to be Optimized.
- If the ECS uses native Linux KVM drivers, its kernel must be later than 2.6.24.
- Disable your antivirus and intrusion detection software. You can enable the software after KVM drivers are installed.
Prerequisites
- The ECS needs to be optimized. For details, see Checking Whether a Private Image Needs to be Optimized.
- The ECS kernel must be later than 2.6.24.
- Disable your antivirus and intrusion detection software. You can enable the software after KVM drivers are installed.
Procedure
Modify the configuration file based on the OS version.
@@ -22,7 +22,7 @@Take CentOS 7.0 as an example.
- In the /etc/dracut.conf file, add VirtIO drivers to add_drivers, including virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces.
- Save and exit the /etc/dracut.conf file and run the dracut -f command to generate initrd again.
Ubuntu/Debian
@@ -56,15 +56,15 @@ -CentOS, EulerOS
- Run the following command to open the /etc/dracut.conf file:
vi /etc/dracut.conf
- - Press i to enter the editing mode and add VirtIO drivers to add_drivers (the format depends on the OS requirements).
[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +
CentOS and EulerOS
- Run the following command to open the /etc/dracut.conf file:
vi /etc/dracut.conf
+ - Press i to enter the editing mode and add VirtIO drivers to add_drivers (the format varies depending on the OS).
[root@CTU10000xxxxx ~]# vi /etc/dracut.conf # additional kernel modules to the default add_drivers+="virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio" ....
- Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
- Run the following command to regenerate initrd:
dracut -f /boot/initramfs-2.6.32-573.8.1.el6.x86_64.img
If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
- - If the virtual file system is initramfs, run the following command to check whether native KVM drivers have been loaded:
lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
-If the virtual file system is initrd, run the following command to check whether native KVM drivers have been loaded:
+ - If the virtual file system is initramfs, run the following command to check whether native KVM drivers have been installed:
lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following command to check whether native KVM drivers have been installed:
lsinitrd /boot/initrd-`uname -r` | grep virtio
Assume that the virtual file system is initramfs. The following command output will be displayed:
[root@CTU10000xxxxx home]# lsinitrd /boot/initramfs-`uname -r`.img | grep virtio @@ -81,7 +81,7 @@ drwxr-xr-x 2 root root 0 Jul 16 17:53 lib/modules/2.6.32-573.8.
Ubuntu and Debian
- Run the following command to open the modules file:
vi /etc/initramfs-tools/modules
- - Press i to enter the editing mode and add VirtIO drivers to the /etc/initramfs-tools/modules file (the format depends on the OS requirements).
[root@CTU10000xxxxx ~]#vi /etc/initramfs-tools/modules +
- Press i to enter the editing mode and add VirtIO drivers to the /etc/initramfs-tools/modules file (the format varies depending on the OS).
[root@CTU10000xxxxx ~]#vi /etc/initramfs-tools/modules ... # Examples: # @@ -128,7 +128,7 @@ root (hd0,0) kernel /boot/linux.vmx vga=0x314 splash=silent ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processsor.max+cstate=1 nomodeset x11failsafe console=ttyS0,115200n8 console=tty0 net.ifnames=0 NON_PERSISTENT_DEVICE_NAMES=1 showopts initrd /boot/initrd.vmx
/boot/initrd.vmx in the initrd line is the initrd file actually used. Run the dracut -f /boot/initrd.vmx command. If the initrd file does not contain the /boot directory, such as /initramfs-xxx, run the dracut -f /boot/initramfs-xxx command.
- - Run the following command to check whether the VirtIO module for KVM is loaded:lsinitrd /boot/initrd-`uname -r` | grep virtio-
SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio +
- Run the following command to check whether KVM VirtIO drivers have been installed:
lsinitrd /boot/initrd-`uname -r` | grep virtioSIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio -rwxr--r-- 1 root root 19248 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/scsi/virtio_scsi.ko -rwxr--r-- 1 root root 23856 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/virtio_blk.ko drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio @@ -152,27 +152,27 @@ drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/d
SUSE and openSUSE (SUSE 12 SP1)
Modify the /etc/dracut.conf file.- Run the following command to open the /etc/dracut.conf file:
vi /etc/dracut.conf
- - Press i to enter the editing mode and add VirtIO drivers to add-drivers (the format depends on the OS requirements).
[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +
SUSE and openSUSE (SUSE 12 SP1)
Modify the /etc/dracut.conf file.- Run the following command to open the /etc/dracut.conf file:
vi /etc/dracut.conf
+ - Press i to enter the editing mode and add VirtIO drivers to add-drivers (the format varies depending on the OS).
[root@CTU10000xxxxx ~]# vi /etc/dracut.conf # additional kernel modules to the default add_drivers+="ata_piix ata_generic virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
- - Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
- Run the following command to regenerate initrd: +
- Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
- Run the following command to regenerate initrd:
dracut -f /boot/initramfs-File name
If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
- - If the virtual file system is initramfs, run the following command to check whether native KVM drivers have been loaded:
lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
-If the virtual file system is initrd, run the following command to check whether native KVM drivers have been loaded:
+ - If the virtual file system is initramfs, run the following command to check whether native KVM drivers have been installed:
lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following command to check whether native KVM drivers have been installed:
lsinitrd /boot/initrd-`uname -r` | grep virtio
SUSE and openSUSE (Later than SUSE 12 SP1 or openSUSE 13)
Modify the /etc/dracut.conf file.
Take SUSE Linux Enterprise Server 12 SP2 (x86_64) as an example.- Run the following command to open the /etc/dracut.conf file:
vi /etc/dracut.conf
- - Press i to enter the editing mode and add VirtIO drivers to add_drivers (the format depends on the OS requirements).
[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +
- Press i to enter the editing mode and add VirtIO drivers to add_drivers (the format varies depending on the OS).
[root@CTU10000xxxxx ~]# vi /etc/dracut.conf # additional kernel modules to the default add_drivers+="ata_piix ata_generic virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
- - Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
- Run the following command to regenerate initrd:
dracut -f /boot/initramfs-File name
-If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
- - If the virtual file system is initramfs, run the following command to check whether native KVM drivers have been loaded:
lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
-If the virtual file system is initrd, run the following command to check whether native KVM drivers have been loaded:
+ - Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
- Run the following command to regenerate initrd:
dracut -f /boot/initramfs-File name
+If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
+ - If the virtual file system is initramfs, run the following command to check whether native KVM drivers have been installed:
lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following command to check whether native KVM drivers have been installed:
lsinitrd /boot/initrd-`uname -r` | grep virtio
Assume that the virtual file system is initrd. The following command output will be displayed:
sluo-ecs-30dc:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio diff --git a/docs/ims/umn/en-us_topic_0000001328477720.html b/docs/ims/umn/en-us_topic_0000001328477720.html index f3ab65ea..1bf74a5d 100644 --- a/docs/ims/umn/en-us_topic_0000001328477720.html +++ b/docs/ims/umn/en-us_topic_0000001328477720.html @@ -9,22 +9,22 @@
- Run the following command to open the /etc/dracut.conf file:
- Run the following command to check whether KVM VirtIO drivers have been installed:
- Run the following command to open the /etc/dracut.conf file:
Public image
+Public
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 environments or software you need, you can use a public image to create an ECS and then deploy the required environments or software on it.
Private image
+Private
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, 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.
- 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 of the same size.
- 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.
- 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.
Shared image
+Shared
A shared image is a private image another user has shared with you.
-For more information about shared images, see "Sharing Images" in Image Management Service User Guide.
+For more information about shared images, see "Sharing Images" in Image Management Service User Guide.
Must I Install Guest OS Drivers on an ECS?
Installing Guest OS drivers on an ECS improves your experience in using the ECS. In addition, it also ensures high reliability and stability of ECSs.
-- Windows ECSs: Install UVP VMTools on ECSs.
- Linux ECSs: Install VirtIO drivers and load them in initrd.
- Windows ECSs: Install UVP VMTools on ECSs.
- Linux ECSs: Install VirtIO drivers and add them to initrd.
How Do I Add, Delete, and Modify Image Tags?
- When adding predefined tags to an image or searching for an image using predefined tags, you must have permission to access the Tag Management Service (TMS).
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab and click the image name to display the image details.
- Click the Tags tab, locate the target tag, and click Edit in the Operation column. In the displayed dialog box, modify the tag.
- Click the Tags tab, locate the target tag, and click Delete in the Operation column. In the displayed dialog box, click Yes.
- Click the Tags tab and then Add Tag. In the displayed dialog box, add a tag.
How Do I Search for Private Images by Tag?
- - When adding predefined tags to an image or searching for an image using predefined tags, you must have permission to access the Tag Management Service (TMS).
Search for Private Images by Tag
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Search for Private Images by Tag
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab and then Search by Tag.Figure 1 Searching for images by tag
- Enter the tag key and value.
Neither the tag key nor tag value can be empty. When the tag key and tag value are matched, the system automatically shows your desired private images.
diff --git a/docs/ims/umn/en-us_topic_0013901609.html b/docs/ims/umn/en-us_topic_0013901609.html index cd850016..02e489a2 100644 --- a/docs/ims/umn/en-us_topic_0013901609.html +++ b/docs/ims/umn/en-us_topic_0013901609.html @@ -12,22 +12,22 @@ -Public image
+Public
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 environments or software you need, you can use a public image to create an ECS and then deploy the required environments or software on it.
Private image
+Private
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, 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.
- 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 of the same size.
- 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.
- 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.
Shared image
+Shared
A shared image is a private image another user has shared with you.
-For more information about shared images, see "Sharing Images" in Image Management Service User Guide.
+For more information about shared images, see "Sharing Images" in Image Management Service User Guide.
- Access the IMS console.
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
- 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 capacity, 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.
diff --git a/docs/ims/umn/en-us_topic_0030713141.html b/docs/ims/umn/en-us_topic_0030713141.html index b4b199fc..fa517c19 100644 --- a/docs/ims/umn/en-us_topic_0030713141.html +++ b/docs/ims/umn/en-us_topic_0030713141.html @@ -2,7 +2,7 @@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 or an external image file. It can be a system, disk, or full-ECS image that suites your different needs.
- Private images can be transferred between accounts, regions, or cloud platforms through image sharing, replication, and export.
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 or an external image file. It can be a system disk, data disk, or full-ECS image that suites your different needs.
- Private images can be transferred between accounts, regions, or cloud platforms through image sharing, replication, and export.
diff --git a/docs/ims/umn/en-us_topic_0030713142.html b/docs/ims/umn/en-us_topic_0030713142.html index f82a76fd..d4d4c8ac 100644 --- a/docs/ims/umn/en-us_topic_0030713142.html +++ b/docs/ims/umn/en-us_topic_0030713142.html @@ -2,12 +2,12 @@Secure
- Public images use mainstream OSs such as 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).
OSs Supported by Different Types of ECSs
This section describes the OSs supported by different types of ECSs.
--x86 ECSs
- Table 1 lists the OSs supported by the following ECSs:
General-purpose S2, S3
+-x86 ECSs
- Table 1 lists the OSs supported by the following ECSs:
General-purpose S2, S3
Dedicated general-purpose C3, C4
-Memory-optimized M2, M3, M4
+Memory-optimized M3, M4
Disk-intensive D2
Ultra-high I/O I3
- - Table 2 lists the OSs supported by large-memory ECSs (E3).
- Table 3 lists the OSs supported by high-performance ECSs (HL1, H2).
- Table 4 lists the OSs supported by GPU-accelerated ECSs (G6, P2s, P2v, P2, PI2).
- Table 5 lists the OSs supported by GPU-accelerated ECSs (P1).
- FPGA-accelerated FP1c and FP1cne ECSs support only CentOS 7.3 64bit.
- AI-accelerated AI1 ECSs support the following OSs:
- Ubuntu Server 16.04 64bit
- CentOS 7.4 64bit
- Table 2 lists the OSs supported by large-memory ECSs (E3).
- Table 3 lists the OSs supported by GPU-accelerated ECSs (G6, P2s, P2v, PI2).
- AI-accelerated AI1 ECSs support the following OSs:
- Ubuntu Server 16.04 64bit
- CentOS 7.4 64bit
@@ -143,102 +143,42 @@ - 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 3 Supported OS versions OS
+- -
-Table 3 Supported OS versions OS
Version
+OS Version
CentOS
+Rocky
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Rocky 8 64 bit
Oracle Linux
+CentOS
- Oracle Linux Server release 8.4 64bit
- Oracle Linux Server release 7.6 64bit
CentOS 7.9 64bit
Red Hat
+EulerOS
Red Hat Enterprise Linux 7.9 64bit
-SUSE
-- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- -
-Table 4 Supported OS versions OS
-OS Version
-Rocky
-Rocky 8 64 bit
-CentOS
-CentOS 7.9 64bit
-EulerOS
-EulerOS 2.5 64bit
+EulerOS 2.5 64bit
NOTE:PI2 ECSs do not support this OS version.
Oracle Linux
+Oracle Linux
Oracle Linux Server release 7.6 64bit
+Oracle Linux Server release 7.6 64bit
Ubuntu
+Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
+Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
-Table 5 Supported OS versions OS
-OS Version
-CentOS
-CentOS 7.9 64bit
-Debian
-- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
Oracle Linux
-Oracle Linux Server release 7.6 64bit
-Ubuntu
-- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
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 1 lists the OSs supported by 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.
- 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.
diff --git a/docs/ims/umn/en-us_topic_0030713148.html b/docs/ims/umn/en-us_topic_0030713148.html index 5c8706f6..35565783 100644 --- a/docs/ims/umn/en-us_topic_0030713148.html +++ b/docs/ims/umn/en-us_topic_0030713148.html @@ -54,9 +54,9 @@ - Uploading image files containing OSs not listed in Table 1 may fail. You are advised to contact the customer service before uploading these image files.
- For details about the formats and OSs supported for BMS images, see Bare Metal Server Private Image Creation Guide.
- When uploading a CoreOS image file, set the OS type to CoreOS. Otherwise, the OS type will be set to Other (64bit). In addition, ensure that coreos-cloudinit has been installed and configured for CoreOS. Automatic system upgrades must be disabled. Otherwise, they may make ECSs created using this image unavailable.
- You can only use external image files containing Windows 10 64bit or Windows 7 Enterprise 64bit to create ECSs on a Dedicated Host (DeH).
Cloud Backup and Recovery (CBR)
+Cloud Backup and Recovery (CBR)
You can use a CBR backup to create a full-ECS image.
+You can use a CBR backup to create a full-ECS image.
Creating a System Disk Image from a Windows ECS
-Scenarios
If you have created and configured a Windows ECS based on your service requirements (for example, by installing software and setting up an application environment), you can create a system disk image based on this configured ECS. Then, all new ECSs created from this image will have the same software and environment preinstalled.
+Scenarios
If you have created and configured a Windows ECS based on your service requirements (for example, by installing software and setting up an application environment), you can create a system disk image based on this configured ECS. Then, all new ECSs created from this image will have the same software and environment preinstalled.
Creating a system disk image does not affect the running of services on the ECS or cause data loss.
-Background
The following figure shows the process of creating a system disk image from an ECS.
@@ -19,7 +19,7 @@ If an ECS is created from a public image, Cloudbase-Init has been installed by default. You can follow the guide in the prerequisites to verify the installation.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Create a system disk image.
- Access the IMS console.
- Click Create Now.
- Confirm the settings and click Submit.
+- Click Create Now.
- Confirm the settings and click Submit.
- Go back to the Private Images page and view the new system disk image.
-The time required for creating an image depends on the ECS system disk size, network quality, and the number of concurrent tasks. When the image status changes to Normal, the image creation is complete.
- Do not perform any operations on the selected ECS or its associated resources during image creation.
- An ECS created from an encrypted image is also encrypted. The key used for encrypting the ECS is the same as that used for encrypting the image.
- An image created from an encrypted ECS is also encrypted. The key used for encrypting the image is the same as that used for encrypting the ECS.
diff --git a/docs/ims/umn/en-us_topic_0030713152.html b/docs/ims/umn/en-us_topic_0030713152.html index bee73a8b..1e2a8701 100644 --- a/docs/ims/umn/en-us_topic_0030713152.html +++ b/docs/ims/umn/en-us_topic_0030713152.html @@ -7,11 +7,11 @@Follow-up Procedure
After a system disk image is created, you can use either of the following methods to migrate data between two servers:
+Follow-up Procedure
After a system disk image is created, you can:
- Use the image to create new ECSs. For details, see Creating an ECS from an Image.
- Use the image to change the OSs of existing ECSs.
Prerequisites
You have logged in to the ECS used to create a Windows private image.
-For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
Procedure
- On the ECS, choose .
- Click Network and Internet Connections.
- Click Network and Sharing Center.Figure 1 Network and Sharing Center
- Select the connection configured with the static IP address. For example, click Local Area Connection 2.Figure 2 Local Area Connection 2 Status-
- Click Properties and select the configured Internet protocol version.
- On the General tab, select Obtain an IP address automatically and Obtain DNS server address automatically and click OK. Figure 3 shows the dialog box for configuring the IP address obtaining mode.
You are advised to record the original network information so that you can restore the network if necessary.
+- Click Properties and select the configured Internet protocol version.
- On the General tab, select Obtain an IP address automatically and Obtain DNS server address automatically and click OK. Figure 3 shows the dialog box for configuring the IP address obtaining mode.
diff --git a/docs/ims/umn/en-us_topic_0030713155.html b/docs/ims/umn/en-us_topic_0030713155.html index 7df8cab0..92d865b2 100644 --- a/docs/ims/umn/en-us_topic_0030713155.html +++ b/docs/ims/umn/en-us_topic_0030713155.html @@ -6,7 +6,7 @@ You are advised to record the original network information so that you can restore the network if necessary.
Prerequisites
You have logged in to the ECS used to create a Windows private image.
-For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
Procedure
- Before enabling this function, you are advised to set the resolution of the ECS to 1920×1080.
On the ECS, choose Start > Control Panel. Under Appearance and Personalization, click Adjust screen resolution. Then select a proper value from the Resolution drop-down list box.
- Choose Start, right-click Computer, and choose Properties from the shortcut menu.
- Click Remote settings.
- In the Remote tab, select Allow connections from computers running any version of Remote Desktop (less secure).
- Click OK.
- Choose Start > Control Panel and navigate to Windows Firewall.
- Choose Allow a program or feature through Windows Firewall in the left pane.
- Select programs and features that are allowed by the Windows firewall for Remote Desktop based on your network requirements and click OK in the lower part.Figure 1 Configuring remote desktopdiff --git a/docs/ims/umn/en-us_topic_0030713176.html b/docs/ims/umn/en-us_topic_0030713176.html index 35acb110..c312b192 100644 --- a/docs/ims/umn/en-us_topic_0030713176.html +++ b/docs/ims/umn/en-us_topic_0030713176.html @@ -7,7 +7,7 @@
Prerequisites
You have logged in to the ECS used to create a Windows private image.
-For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
Ubuntu 18 or Later
- Run vi /etc/netplan/01-netcfg.yaml on the ECS to open the /etc/netplan/01-netcfg.yaml file, and check whether the value of dhcp4 is true.
- If dhcp4 is set to true, enter :q to exit the editor. No further action will be required.
network: version:2 diff --git a/docs/ims/umn/en-us_topic_0030713178.html b/docs/ims/umn/en-us_topic_0030713178.html index a8e91875..71ec7281 100644 --- a/docs/ims/umn/en-us_topic_0030713178.html +++ b/docs/ims/umn/en-us_topic_0030713178.html @@ -2,7 +2,7 @@Is There Any Difference Between the Image Created from a CSBS/CBR Backup and That Created from an ECS?
No.
-You can create a full-ECS image from an ECS, a CSBS backup, or a CBR backup.
+You can create a full-ECS image from an ECS, a CSBS backup, or a CBR backup.
When you create a full-ECS image from an ECS, the system first creates a backup for the ECS and then uses the backup to create an image. Therefore, the image is essentially created from an ECS backup no matter you use an ECS or a CSBS/CBR backup.
diff --git a/docs/ims/umn/en-us_topic_0030713180.html b/docs/ims/umn/en-us_topic_0030713180.html index f1e44035..89155815 100644 --- a/docs/ims/umn/en-us_topic_0030713180.html +++ b/docs/ims/umn/en-us_topic_0030713180.html @@ -1,7 +1,7 @@Creating a System Disk Image from a Linux ECS
-Scenarios
If you have created and configured a Linux ECS based on your service requirements (for example, by installing software and setting up an application environment), you can create a system disk image based on this configured ECS. Then, all new ECSs created from this image will have the same software and environment preinstalled.
+Scenarios
If you have created and configured a Linux ECS based on your service requirements (for example, by installing software and setting up an application environment), you can create a system disk image based on this configured ECS. Then, all new ECSs created from this image will have the same software and environment preinstalled.
Creating a system disk image does not affect the running of services on the ECS or cause data loss.
Background
The following figure shows the process of creating a system disk image from an ECS.
@@ -16,12 +16,12 @@- The time required for creating an image depends on the ECS system disk size, network quality, and the number of concurrent tasks.
- A system disk image will be created in the same region as the ECS that was used to create it.
- If an ECS has expired or been released, you can use the system disk image created from the ECS to restore it.
-Prerequisites
Before creating a private image from an ECS:
-- Delete any sensitive data the ECS may contain.
- Ensure that the ECS is in the Running or Stopped state.
- Check network configuration of the ECS and ensure that DHCP is configured for the NICs. For details, see Setting the NIC to DHCP.
- Install special drivers. The normal running and advanced functions of some ECSs depend on certain drivers. For example, P1 ECSs depend on the NVIDIA driver. For details, see Installing Special Linux Drivers.
- Check whether Cloud-Init has been installed on the ECS. The user data injection function on the management console is only available for new ECSs that have this tool installed. You can use data injection, for example, to set the login password for a new ECS. For details, see Installing Cloud-Init and Configuring Cloud-Init.
- Delete any network rules to prevent NIC name drift on the ECSs created from the image. For details, see Deleting Files from the Network Rule Directory.
- To ensure that the ECSs created from the image support KVM virtualization, the Linux ECS used to create the image has to be modified. For instance, the disk IDs in the GRUB and fstab files need to be UUID and native KVM drivers need to be installed.
For details, see Optimization Process.
+- Delete any sensitive data the ECS may contain.
- Ensure that the ECS is in the Running or Stopped state.
- Check network configuration of the ECS and ensure that DHCP is configured for the NICs. For details, see Setting the NIC to DHCP.
- Install special drivers. The normal running and advanced functions of some ECSs depend on certain drivers. For example, P1 ECSs depend on the NVIDIA driver. For details, see Installing Special Linux Drivers.
- Check whether Cloud-Init has been installed on the ECS. The user data injection function on the management console is only available for new ECSs that have this tool installed. You can use data injection, for example, to set the login password for a new ECS. For details, see Installing Cloud-Init and Configuring Cloud-Init.
- Delete any network rules to prevent NIC name drift on the ECSs created from the image. For details, see Deleting Files from the Network Rule Directory.
- To ensure that the ECSs created from the image support KVM virtualization, the Linux ECS used to create the image has to be modified. For instance, the disk IDs in the GRUB and fstab files need to be UUID and native KVM drivers need to be installed.
For details, see Optimization Process.
- If multiple data disks are attached to an ECS used to create a private image, the ECSs created from the image may be unavailable. You need to detach all data disks from the ECS before using it to create an image. For details, see Detaching Data Disks from an ECS.
- If data disks have been attached to the ECS and automatic partition mounting has been configured in the fstab file for the ECS, delete these configurations from the file before using the ECS to create a system disk image.
- To ensure that Console Log is available for the newly created ECSs on the console, set related parameters in the ECS that is used to create the image. For details, see Configuring Console Logging.
If an ECS is created from a public image, Cloud-Init has been installed by default. You can follow the guide to verify the installation.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Create a system disk image.
- Access the IMS console.
- If dhcp4 is set to true, enter :q to exit the editor. No further action will be required.
- Table 1 lists the OSs supported by the following ECSs:
- Click Create Now.
- Confirm the settings and click Submit. +
- Click Create Now.
- Confirm the settings and click Submit.
- Go back to the Private Images page and view the new system disk image.
The time required for creating an image depends on the ECS system disk size, network quality, and the number of concurrent tasks. When the image status changes to Normal, the image creation is complete.
- Do not perform any operations on the selected ECS or its associated resources during image creation.
- An ECS created from an encrypted image is also encrypted. The key used for encrypting the ECS is the same as that used for encrypting the image.
- An image created from an encrypted ECS is also encrypted. The key used for encrypting the image is the same as that used for encrypting the ECS.
diff --git a/docs/ims/umn/en-us_topic_0030713183.html b/docs/ims/umn/en-us_topic_0030713183.html index 1612e474..28d89495 100644 --- a/docs/ims/umn/en-us_topic_0030713183.html +++ b/docs/ims/umn/en-us_topic_0030713183.html @@ -1,7 +1,7 @@Follow-up Procedure
After a system disk image is created, you can use either of the following methods to migrate data between two servers:
+Follow-up Procedure
After a system disk image is created, you can:
- Use the image to create new ECSs. For details, see Creating an ECS from an Image.
- Use the image to change the OSs of existing ECSs.
Uploading an External Image File
-You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.
+diff --git a/docs/ims/umn/en-us_topic_0030713184.html b/docs/ims/umn/en-us_topic_0030713184.html index 45514094..32b4db57 100644 --- a/docs/ims/umn/en-us_topic_0030713184.html +++ b/docs/ims/umn/en-us_topic_0030713184.html @@ -3,7 +3,7 @@You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.
- The bucket file and the image to be registered must belong to the same region.
- Only unencrypted external image files or those encrypted using SSE-KMS can be uploaded to the OBS bucket.
- The storage class of the OBS bucket must be Standard.
- If you want to create a data disk image along with the system disk image, you also need to upload an image file containing data disks to the OBS bucket. You can create one system disk image and no more than three data disk images.
Registering an External Image File as a Private Image
-Scenarios
Register an image file uploaded to the OBS bucket as a private image.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Register an external image file as a private image.
- Click Create Image in the upper right corner.
- Set image parameters.
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
@@ -63,8 +63,8 @@Boot Mode
This parameter is optional. The value can be BIOS or UEFI. For details about the differences between the two, see How Is BIOS Different from UEFI?
-For details about which OSs support UEFI boot, see OSs Supporting UEFI Boot Mode
+This parameter is optional. The value can be BIOS or UEFI. For details about the differences between the two, see How Is BIOS Different from UEFI?
+For details about which OSs support UEFI boot, see OSs Supporting UEFI Boot Mode.
The boot mode must be the same as that in the image file. You need to confirm which boot mode is used in the image file. After you select the correct boot mode, the boot mode will be configured for the image at the background. Select the right boot mode, or ECSs created using the image will not be able to boot up.
System Disk (GB)
The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is at least equal to the system disk size in the image file.
-NOTE:If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk size based on What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
+The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is at least equal to the system disk capacity in the image file.
+NOTE:If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity based on What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
Data Disk (GB)
You can also add data disks to the image. You need to obtain an image file containing data disks in advance. This function is used to migrate VMs and data disks from other platforms to the current platform.
-To add data disks, click
+
, set the data disk size, and click Select Image File. In the displayed dialog box, select the target bucket and then the target image file containing the data disk.To add data disks, click
, set the data disk capacity, and click Select Image File. In the displayed dialog box, select the target bucket and then the target image file containing the data disk.A maximum of three data disks can be added.
What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?
If an image file is not configured as instructed in Table 1 before it is exported from the original platform, configure it by referring to Figure 1.
- The proper running of ECSs depends on the KVM Guest OS driver (UVP VMTools), without which the performance of ECSs will be affected and some functions will be unavailable. Ensure that the driver installation has been completed for the image file before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.
+@@ -11,16 +11,16 @@ The proper running of ECSs depends on the KVM Guest OS driver (UVP VMTools), without which the performance of ECSs will be affected and some functions will be unavailable. Ensure that the driver installation has been completed for the image file before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.
For details about how to install UVP VMTools, see Installing UVP VMTools.
-Step 2 Register the Image File as a Private Image
On the management console, select the uploaded image file and register it as a private image. For details, see Registering an External Image File as a Private Image.
Step 3: Create an ECS
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Step 3: Create an ECS
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab.
- Locate the row that contains the private image and click Apply for Server in the Operation column.
- Set parameters as promoted to create an ECS. Pay attention to the following:
- Bind an EIP to the ECS so that you can upload installation packages to the ECS or download installation packages from the ECS.
- You must add inbound rules for security groups of the ECS to ensure that the ECS can be accessed.
- If the image file has Cloudbase-Init installed, set a password and log in to the ECS using the password as prompted. If Cloudbase-Init is not installed, use the password or certificate contained in the image file to log in the ECS.
For details, see Elastic Cloud Server User Guide.
- - Perform the following steps to check whether the private image has been pre-configured:
- Check whether the ECS can be successfully started. If the start succeeds, a Guest OS driver has been installed for the image file on the original platform or the driver has been automatically installed for the private image on the cloud platform. If the start failed, install a Guest OS driver for the image file on the original platform and start from Step 1: Upload the Image File again.
- Check whether you can log in to the ECS using your configured password or key. If you can, Cloudbase-Init has been installed. If you cannot, use the password or key contained in the image file to log in to the ECS and install Cloudbase-Init as instructed in Installing and Configuring Cloudbase-Init.
- Check whether NICs are set to DHCP by referring to 2 in Step 4: Configure the ECS.
- Use MSTSC to log in to the ECS. If the login is successful, remote desktop connection is enabled on the ECS. If the login fails, enable remote desktop connection by referring to 3 in Step 4: Configure the ECS.
- Click the Private Images tab.
- Locate the row that contains the private image and click Apply for Server in the Operation column.
- Set parameters as promoted to create an ECS. Pay attention to the following:
- Bind an EIP to the ECS so that you can upload installation packages to the ECS or download installation packages from the ECS.
- You must add inbound rules for security groups of the ECS to ensure that the ECS can be accessed.
- If the image file has Cloudbase-Init installed, set a password and log in to the ECS using the password as prompted. If Cloudbase-Init is not installed, use the password or certificate contained in the image file to log in the ECS.
For details, see Elastic Cloud Server User Guide.
+ - Perform the following steps to check whether the private image has been pre-configured:
- Check whether the ECS can be successfully started. If the start succeeds, a Guest OS driver has been installed for the image file on the original platform or the driver has been automatically installed for the private image on the cloud platform. If the start failed, install a Guest OS driver for the image file on the original platform and start from Step 1: Upload the Image File again.
- Check whether you can log in to the ECS using your configured password or key. If you can, Cloudbase-Init has been installed. If you cannot, use the password or key contained in the image file to log in to the ECS and install Cloudbase-Init as instructed in Installing and Configuring Cloudbase-Init.
- Check whether NICs are set to DHCP by referring to 2 in Step 4: Configure the ECS.
- Use MSTSC to log in to the ECS. If the login is successful, remote desktop connection is enabled on the ECS. If the login fails, enable remote desktop connection by referring to 3 in Step 4: Configure the ECS.
If the ECS meets the preceding requirements, the private image has been pre-configured. Skip Step 4: Configure the ECS and Step 5: Create a Private Image from the ECS.
Step 4: Configure the ECS
Remotely log in to the ECS created in Step 3: Create an ECS to configure it.
-- Log in to the ECS.
- Check whether NICs are set to DHCP. If the ECS is configured with a static IP address, change its IP address assignment mode to DHCP as instructed in Setting the NIC to DHCP.
- Enable remote desktop connection for the ECS as needed. For details about how to enable this function, see Enabling Remote Desktop Connection.
- (Optional) Configure value-added functions.
- Install and configure Cloudbase-Init. For details, see Installing and Configuring Cloudbase-Init.
- Enable NIC multi-queue. For details, see How Do I Enable NIC Multi-Queue for an Image?
- Log in to the ECS.
- Check whether NICs are set to DHCP. If the ECS is configured with a static IP address, change its IP address assignment mode to DHCP as instructed in Setting the NIC to DHCP.
- Enable remote desktop connection for the ECS as needed. For details about how to enable this function, see Enabling Remote Desktop Connection.
- (Optional) Configure value-added functions.
- Install and configure Cloudbase-Init. For details, see Installing and Configuring Cloudbase-Init.
- Enable NIC multi-queue. For details, see How Do I Enable NIC Multi-Queue for an Image?
Step 5: Create a Private Image from the ECS
For details, see Creating a System Disk Image from a Windows ECS.
diff --git a/docs/ims/umn/en-us_topic_0030713188.html b/docs/ims/umn/en-us_topic_0030713188.html index 6ffe19dd..dc45876e 100644 --- a/docs/ims/umn/en-us_topic_0030713188.html +++ b/docs/ims/umn/en-us_topic_0030713188.html @@ -4,9 +4,9 @@-Scenarios
After registering an external image file as a private image on the cloud platform, you can use the image to create ECSs or change the OSs of existing ECSs.
This section describes how to create an ECS from an image.
Procedure
Create an ECS by referring to Creating an ECS from an Image.
+Procedure
Create an ECS by referring to Creating an ECS from an Image.
Note the following when setting the parameters:
-- Region: Select the region where the private image is located.
- Specifications: Select a flavor based on the OS type in the image and the OS versions described in OSs Supported by Different Types of ECSs.
- Image: Select Private image and then the created image from the drop-down list.
- (Optional) Data Disk: Add data disks. These data disks are created from a data disk image generated together with a system disk image. In this way, you can migrate the data of data disks together with system disk data from the VM on the original platform to the current cloud platform.
- Region: Select the region where the private image is located.
- Specifications: Select a flavor based on the OS type in the image and the OS versions described in OSs Supported by Different Types of ECSs.
- Image: Select Private image and then the created image from the drop-down list.
- (Optional) Data Disk: Add data disks. These data disks are created from a data disk image generated together with a system disk image. In this way, you can migrate the data of data disks together with system disk data from the VM on the original platform to the current cloud platform.
diff --git a/docs/ims/umn/en-us_topic_0030713189.html b/docs/ims/umn/en-us_topic_0030713189.html index b1cacdfc..43610dca 100644 --- a/docs/ims/umn/en-us_topic_0030713189.html +++ b/docs/ims/umn/en-us_topic_0030713189.html @@ -2,7 +2,7 @@Follow-up Procedure
After a system disk image is created, you can use it to change the OS of an ECS.
Preparing an Image File
You need to prepare an image file that meets the platform requirements.
- - You are advised to complete the network, tool, and driver configurations in Table 1 on the source VM and then export the image file. You can also complete the configurations on the created ECSs. For details, see What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?
- Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In addition to the requirements described in Table 1, a bitmap file needs to be generated for each RAW image file. The bitmap file is uploaded together with the image file. For details, see Quickly Importing an Image File.
- You are advised to complete the network, tool, and driver configurations in Table 1 on the source VM and then export the image file. You can also complete the configurations on the created ECSs. For details, see What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?
- Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In addition to the requirements described in Table 1, a bitmap file needs to be generated for each RAW image file. The bitmap file is uploaded together with the image file. For details, see Quickly Importing an Image File.
Table 1 Windows image file requirements Image File Property
@@ -53,7 +53,7 @@Other requirements
- Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk size must be between 1 GB and 1 TB.
- The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
- The boot partition and system partition must be on the same disk.
- For an external image file, you need a tenant administrator account and password combination.
- Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see OSs Supporting UEFI Boot Mode.
- The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
- Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk capacity must be between 1 GB and 1 TB.
- The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
- The boot partition and system partition must be on the same disk.
- For an external image file, you need a tenant administrator account and password combination.
- Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see OSs Supporting UEFI Boot Mode.
- The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
Uploading an External Image File
-You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.
+diff --git a/docs/ims/umn/en-us_topic_0030713193.html b/docs/ims/umn/en-us_topic_0030713193.html index ee096c89..341ce4ac 100644 --- a/docs/ims/umn/en-us_topic_0030713193.html +++ b/docs/ims/umn/en-us_topic_0030713193.html @@ -3,7 +3,7 @@You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.
- The bucket file and the image to be registered must belong to the same region.
- Only unencrypted external image files or those encrypted using SSE-KMS can be uploaded to the OBS bucket.
- The storage class of the OBS bucket must be Standard.
- If you want to create a data disk image along with the system disk image, you also need to upload an image file containing data disks to the OBS bucket. You can create one system disk image and no more than three data disk images.
Registering an External Image File as a Private Image
-Scenarios
Register an image file uploaded to the OBS bucket as a private image.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Register an external image file as a private image.
- Click Create Image in the upper right corner.
- Set image parameters.
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
@@ -63,8 +63,8 @@Boot Mode
This parameter is optional. The value can be BIOS or UEFI. For details about the differences between the two, see How Is BIOS Different from UEFI?
-For details about which OSs support UEFI boot, see OSs Supporting UEFI Boot Mode
+This parameter is optional. The value can be BIOS or UEFI. For details about the differences between the two, see How Is BIOS Different from UEFI?
+For details about which OSs support UEFI boot, see OSs Supporting UEFI Boot Mode.
The boot mode must be the same as that in the image file. You need to confirm which boot mode is used in the image file. After you select the correct boot mode, the boot mode will be configured for the image at the background. Select the right boot mode, or ECSs created using the image will not be able to boot up.
System Disk (GB)
The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is at least equal to the system disk size in the image file.
-NOTE:If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk size based on What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
+The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is at least equal to the system disk capacity in the image file.
+NOTE:If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity based on What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
Data Disk (GB)
You can also add data disks to the image. You need to obtain an image file containing data disks in advance. This function is used to migrate VMs and data disks from other platforms to the current platform.
-To add data disks, click
+, set the data disk size, and click Select Image File. In the displayed dialog box, select the target bucket and then the target image file containing the data disk.To add data disks, click
, set the data disk capacity, and click Select Image File. In the displayed dialog box, select the target bucket and then the target image file containing the data disk.A maximum of three data disks can be added.
- How Do I Import an OVF or OVA File to the Cloud Platform?
- - What Do I Do If I Configured an Incorrect OS or System Disk Size During Private Image Registration Using an Image File?
+ - What Do I Do If I Configured an Incorrect OS or System Disk Capacity During Private Image Registration Using an Image File?
- - What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
+ - What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
diff --git a/docs/ims/umn/en-us_topic_0030713197.html b/docs/ims/umn/en-us_topic_0030713197.html
index cdabcace..45c9d4d4 100644
--- a/docs/ims/umn/en-us_topic_0030713197.html
+++ b/docs/ims/umn/en-us_topic_0030713197.html
@@ -4,9 +4,9 @@
- Region: Select the region where the private image is located.
- Specifications: Select a flavor based on the OS type in the image and the OS versions described in OSs Supported by Different Types of ECSs.
- Image: Select Private image and then the created image from the drop-down list.
- (Optional) Data Disk: Add data disks. These data disks are created from a data disk image generated together with a system disk image. In this way, you can migrate the data of data disks together with system disk data from the VM on the original platform to the current cloud platform.
- Region: Select the region where the private image is located.
- Specifications: Select a flavor based on the OS type in the image and the OS versions described in OSs Supported by Different Types of ECSs.
- Image: Select Private image and then the created image from the drop-down list.
- (Optional) Data Disk: Add data disks. These data disks are created from a data disk image generated together with a system disk image. In this way, you can migrate the data of data disks together with system disk data from the VM on the original platform to the current cloud platform.
- You are advised to complete the file system, network, and driver configurations in Table 1 on the source VM and then export the image file. You can also complete the configurations on the created ECSs. For details, see What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?
- Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In addition to the requirements described in Table 1, a bitmap file needs to be generated for each RAW image file. The bitmap file is uploaded together with the image file. For details, see Quickly Importing an Image File.
- You are advised to complete the file system, network, and driver configurations in Table 1 on the source VM and then export the image file. You can also complete the configurations on the created ECSs. For details, see What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?
- Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In addition to the requirements described in Table 1, a bitmap file needs to be generated for each RAW image file. The bitmap file is uploaded together with the image file. For details, see Quickly Importing an Image File.
- SUSE, Oracle Linux, Red Hat, Ubuntu, openSUSE, CentOS, Debian, Fedora, EulerOS, and NeoKylin
- 32-bit or 64-bit
- The OS cannot be bound to specific hardware.
- The OS must support full virtualization.
- Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk size must be between 1 GB and 1 TB.
- The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
- The boot partition and system partition must be on the same disk.
- Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see "OSs Supporting UEFI Boot Mode" in Image Service Management User Guide.
- The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
- The /etc/fstab file cannot contain automatic mounting information of non-system disks. Otherwise, the login to the created ECS may fail.
- If the external image file uses LVM as the system disk, ECSs created from the private image do not support file injection.
- If the VM where the external image file is located has been shut down, it must be a graceful shutdown. Otherwise, a blue screen may occur when the ECS created from the private image is started.
- Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk capacity must be between 1 GB and 1 TB.
- The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
- The boot partition and system partition must be on the same disk.
- Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see "OSs Supporting UEFI Boot Mode" in Image Service Management User Guide.
- The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
- The /etc/fstab file cannot contain automatic mounting information of non-system disks. Otherwise, the login to the created ECS may fail.
- If the external image file uses LVM as the system disk, ECSs created from the private image do not support file injection.
- If the VM where the external image file is located has been shut down, it must be a graceful shutdown. Otherwise, a blue screen may occur when the ECS created from the private image is started.
- You can only modify a private image in the Normal state.
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Method 1:-- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab to display the image list.
- Locate the row that contains the image and click Modify in the Operation column.
- In the Modify Image dialog box, modify the image.Figure 1 Modifying an image
Method 2:- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Method 2:diff --git a/docs/ims/umn/en-us_topic_0030713200.html b/docs/ims/umn/en-us_topic_0030713200.html index 9931c787..c2c63b0e 100644 --- a/docs/ims/umn/en-us_topic_0030713200.html +++ b/docs/ims/umn/en-us_topic_0030713200.html @@ -4,9 +4,9 @@- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab to display the image list.
- On the image list, click the name of the target image.
- On the image details page, click Modify in the upper right corner. In the Modify Image dialog box, modify image attributes.
-Scenarios
You can use a public, private, or shared image to create an ECS.
- If you use a public image, the created ECS contains an OS and preinstalled public applications. You need to install applications as needed.
- If you use a private or shared image, the created ECS contains an OS, preinstalled public applications, and a user's personal applications.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Public Images, Private Images, or Images Shared with Me tab to display the image list.
- Locate the row that contains your desired image and click Apply for Server in the Operation column.
- For details about how to create an ECS, see Elastic Cloud Server User Guide.
When you use a system disk image to create an ECS, you can set the ECS specifications and system disk type without considering those in the image, but the system disk size can only be larger than that in the image.
+ - Click the Public Images, Private Images, or Images Shared with Me tab to display the image list.
- Locate the row that contains your desired image and click Apply for Server in the Operation column.
- For details about how to create an ECS, see Elastic Cloud Server User Guide.
When you use a system disk image to create an ECS, you can set the ECS specifications and system disk type without considering those in the image, but the system disk capacity can only be larger than that in the image.
When you use a full-ECS image to create an ECS, the system and data disk information defaulted by the image will be automatically displayed. You can increase the capacity of a system disk or data disks, but cannot decrease it.
diff --git a/docs/ims/umn/en-us_topic_0030713201.html b/docs/ims/umn/en-us_topic_0030713201.html index 550529ea..a62f37e1 100644 --- a/docs/ims/umn/en-us_topic_0030713201.html +++ b/docs/ims/umn/en-us_topic_0030713201.html @@ -4,12 +4,12 @@ If a full-ECS image contains multiple data disks, it takes some time to load and display the disk information.
-Scenarios
You can delete private images that will no longer be used.
- Deleted private images cannot be retrieved. Perform this operation only when absolutely necessary.
- After a private image is deleted, it cannot be used to create ECSs or EVS disks.
- After a private image is deleted, ECSs created from the image can still be used and are still billed. However, the OS cannot be reinstalled for the ECSs and ECSs with the same configuration cannot be created.
- Deleting the source image of a replicated image has no effect on the replicated image. Similarly, deleting a replicated image has no effect on its source.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab to display the image list.
- Locate the row that contains the image, choose More > Delete in the Operation column.-
To delete multiple images:
- Select the images you want to delete in the image list.
- Click Delete above the image list.
- (Optional) Select Delete CSBS backups or cloud server backups of the full-ECS images.
This parameter is available only when you have selected full-ECS images from the image list.
+ - (Optional) Select Delete CSBS backups or cloud server backups of the full-ECS images.
This parameter is available only when you have selected full-ECS images from the image list.
If you select this option, the system will delete CSBS or CBR backups of the full-ECS images.
diff --git a/docs/ims/umn/en-us_topic_0030713208.html b/docs/ims/umn/en-us_topic_0030713208.html index cabb279c..959b70ff 100644 --- a/docs/ims/umn/en-us_topic_0030713208.html +++ b/docs/ims/umn/en-us_topic_0030713208.html @@ -3,7 +3,7 @@ If CSBS or CBR backups failed to be deleted, the cause may be that these backups are being created and cannot be deleted. In this case, manually delete them as prompted.
Can I Change the Image of a Purchased ECS?
Yes.
If you have selected an incorrect image or your service requirements have changed, you can change the image of your ECS.
-You can change the image type (public, private, and shared images) and OS. For details, see "Changing the OS" in Elastic Cloud Server User Guide.
+You can change the image type (public, private, and shared images) and OS. For details, see "Changing the OS" in Elastic Cloud Server User Guide.
diff --git a/docs/ims/umn/en-us_topic_0030713209.html b/docs/ims/umn/en-us_topic_0030713209.html index a6bd23e5..a7d4c6ca 100644 --- a/docs/ims/umn/en-us_topic_0030713209.html +++ b/docs/ims/umn/en-us_topic_0030713209.html @@ -1,7 +1,7 @@Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to Create the Private Image?
-Yes. You can specify the CPU, memory, bandwidth, data disks of the new ECSs if necessary. You can also specify their system disk size. The value must be smaller than 1024 GB but no less than the system disk size in the image.
+Yes. You can specify the CPU, memory, bandwidth, data disks of the new ECSs if necessary. You can also specify their system disk capacity. The value must be smaller than 1024 GB but no less than the system disk capacity in the image.
diff --git a/docs/ims/umn/en-us_topic_0030713211.html b/docs/ims/umn/en-us_topic_0030713211.html index 6acc5e66..5ead5e20 100644 --- a/docs/ims/umn/en-us_topic_0030713211.html +++ b/docs/ims/umn/en-us_topic_0030713211.html @@ -2,7 +2,7 @@What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?
If an image file is not configured as instructed in Table 1 before it is exported from the original platform, configure it by referring to Figure 1.
- The proper running of ECSs depends on the KVM driver. If no such a driver is installed, the performance of ECSs will be affected and some functions will be unavailable. Ensure that the KVM driver has been installed for the image file before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.
+@@ -11,21 +11,21 @@ The proper running of ECSs depends on the KVM driver. If no such a driver is installed, the performance of ECSs will be affected and some functions will be unavailable. Ensure that the KVM driver has been installed for the image file before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.
For details, see Installing Native KVM Drivers.
Step 2 Register the Image File as a Private Image
On the management console, select the uploaded image file and register it as a private image. For details, see Registering an External Image File as a Private Image.
Step 3: Create an ECS
Create an ECS from the private image.
-- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab.
- Locate the row that contains the private image and click Apply for Server in the Operation column.
- Set parameters as promoted to create an ECS. Pay attention to the following:
- You must add inbound rules for security groups of the ECS to ensure that the ECS can be accessed.
- If Cloud-Init has been installed in the image file, set a login password as prompted. If Cloud-Init is not installed, use the password or certificate contained in the image file to log in.
For details, see Elastic Cloud Server User Guide.
- - Perform the following steps to check whether the private image has been pre-configured:
- Check whether the ECS can be successfully started. If the start succeeds, the KVM driver has been installed for the external image file on the original platform or the driver has been automatically installed for the private image on the cloud platform. If the start failed, install the KVM driver as needed for the image file and start from Step 1: Upload the Image File again.
- Check whether you can log in to the ECS using your configured password or key. If you can, Cloud-Init has been installed. If you cannot, use the password or key contained in the image file to log in to the ECS and install Cloud-Init as instructed in Installing Cloud-Init.
- Check the network configuration by referring to Step 4: Configure the ECS.
- Click the Private Images tab.
- Locate the row that contains the private image and click Apply for Server in the Operation column.
- Set parameters as promoted to create an ECS. Pay attention to the following:
- You must add inbound rules for security groups of the ECS to ensure that the ECS can be accessed.
- If Cloud-Init has been installed in the image file, set a login password as prompted. If Cloud-Init is not installed, use the password or certificate contained in the image file to log in.
For details, see Elastic Cloud Server User Guide.
+ - Perform the following steps to check whether the private image has been pre-configured:
- Check whether the ECS can be successfully started. If the start succeeds, the KVM driver has been installed for the external image file on the original platform or the driver has been automatically installed for the private image on the cloud platform. If the start failed, install the KVM driver as needed for the image file and start from Step 1: Upload the Image File again.
- Check whether you can log in to the ECS using your configured password or key. If you can, Cloud-Init has been installed. If you cannot, use the password or key contained in the image file to log in to the ECS and install Cloud-Init as instructed in Installing Cloud-Init.
- Check the network configuration by referring to Step 4: Configure the ECS.
If the ECS meets the preceding requirements, the private image has been pre-configured. Skip Step 4: Configure the ECS and Step 5: Create a Private Image from the ECS.
- Access the IMS console.
-Step 4: Configure the ECS
Remotely log in to the ECS created in Step 3: Create an ECS to configure it.
-- Log in to the ECS.
- Configure the network.
- Run the ifconfig command to check whether the private IP address of the ECS is the same as that displayed on the console. If they are inconsistent, delete files from the network rule directory as instructed in Deleting Files from the Network Rule Directory.
- Check whether NICs are set to DHCP. If the ECS is configured with a static IP address, change its IP address assignment mode to DHCP as instructed in Setting the NIC to DHCP.
- Run the service sshd status command to check whether SSH is enabled. If it is disabled, run the service sshd start command to enable it. Ensure that your firewall (for example, Linux iptables) allows SSH access.
- Log in to the ECS.
- Configure the network.
- Run the ifconfig command to check whether the private IP address of the ECS is the same as that displayed on the console. If they are inconsistent, delete files from the network rule directory as instructed in Deleting Files from the Network Rule Directory.
- Check whether NICs are set to DHCP. If the ECS is configured with a static IP address, change its IP address assignment mode to DHCP as instructed in Setting the NIC to DHCP.
- Run the service sshd status command to check whether SSH is enabled. If it is disabled, run the service sshd start command to enable it. Ensure that your firewall (for example, Linux iptables) allows SSH access.
- Configure a file system.
- Change the disk identifier in the GRUB configuration file to UUID. For details, see Changing the Disk Identifier in the GRUB Configuration File to UUID.
- Change the disk identifier in the fstab file to UUID. For details, see Changing the Disk Identifier in the fstab File to UUID.
- Clear the automatic attachment information of non-system disks in the /etc/fstab file to prevent impacts on subsequent data disk attachment. For details, see Detaching Data Disks from an ECS.
- (Optional) Configure value-added functions.
- Install and configure Cloud-Init. For details, see Installing Cloud-Init and Configuring Cloud-Init.
- Enable NIC multi-queue. For details, see How Do I Enable NIC Multi-Queue for an Image?
Step 5: Create a Private Image from the ECS
Create a private image from the ECS. For details, see Creating a System Disk Image from a Linux ECS.
+Step 5: Create a Private Image from the ECS
Create a private image from the ECS. For details, see Creating a System Disk Image from a Linux ECS.
(Optional) Clear the Environment
After the image registration is complete, delete the image file as well as the intermediate private image and ECS to prevent them from occupying storage and compute resources.
- Delete the image registered in Step 2 Register the Image File as a Private Image.
- Delete the ECS created in Step 3: Create an ECS.
- Delete the image file from the OBS bucket.
What Do I Do If I Configured an Incorrect OS or System Disk Size During Private Image Registration Using an Image File?
-If you selected an incorrect OS, ECSs may fail to be created from the private image. If the configured system disk size is less than the one in the image file, image registration will fail.
+What Do I Do If I Configured an Incorrect OS or System Disk Capacity During Private Image Registration Using an Image File?
+If you selected an incorrect OS, ECSs may fail to be created from the private image. If the configured system disk capacity is less than the one in the image file, image registration will fail.
In such cases, delete the incorrect image and create a new one using correct parameter settings.
diff --git a/docs/ims/umn/en-us_topic_0030713214.html b/docs/ims/umn/en-us_topic_0030713214.html index e68dff98..6a811e27 100644 --- a/docs/ims/umn/en-us_topic_0030713214.html +++ b/docs/ims/umn/en-us_topic_0030713214.html @@ -2,7 +2,7 @@Must I Install Guest OS Drivers on an ECS?
Installing Guest OS drivers on an ECS improves your experience in using the ECS. In addition, it also ensures high reliability and stability of ECSs.
-- Windows ECSs: Install UVP VMTools on ECSs.
- Linux ECSs: Install VirtIO drivers and load them in initrd.
- Windows ECSs: Install UVP VMTools on ECSs.
- Linux ECSs: Install VirtIO drivers and add them to initrd.
diff --git a/docs/ims/umn/en-us_topic_0030713220.html b/docs/ims/umn/en-us_topic_0030713220.html index 53969005..b0941797 100644 --- a/docs/ims/umn/en-us_topic_0030713220.html +++ b/docs/ims/umn/en-us_topic_0030713220.html @@ -8,7 +8,7 @@- Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to Create the Private Image?
-
- Can I Specify the System Disk Size When I Create an ECS Using an Image?
+- Can I Specify the System Disk Capacity When I Create an ECS Using an Image?
- What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private Image?
diff --git a/docs/ims/umn/en-us_topic_0030713221.html b/docs/ims/umn/en-us_topic_0030713221.html index 92ea9eb6..24057452 100644 --- a/docs/ims/umn/en-us_topic_0030713221.html +++ b/docs/ims/umn/en-us_topic_0030713221.html @@ -1,8 +1,8 @@ -
Can I Specify the System Disk Size When I Create an ECS Using an Image?
-Yes. However, the value must be smaller than 30,768 GB but no less than the system disk size in the image.
- Ensure that your ECS OS supports the system disk size you specified.
+Can I Specify the System Disk Capacity When I Create an ECS Using an Image?
+Yes. However, the value must be smaller than 30,768 GB but no less than the system disk capacity in the image.
+ Ensure that your ECS OS supports the system disk capacity you specified.
diff --git a/docs/ims/umn/en-us_topic_0030730602.html b/docs/ims/umn/en-us_topic_0030730602.html index d1d9ecaa..f455d548 100644 --- a/docs/ims/umn/en-us_topic_0030730602.html +++ b/docs/ims/umn/en-us_topic_0030730602.html @@ -4,6 +4,8 @@+Scenarios
To ensure that you can use the user data injection function to inject initial custom information into ECSs created from a private image (such as setting the ECS login password), install Cloudbase-Init on the ECS used to create the image.
- If Cloudbase-Init is not installed, you cannot configure an ECS. As a result, you can only use the password in the image file to log in to the ECS.
- By default, ECSs created from a public image have Cloudbase-Init installed. You do not need to install or configure Cloudbase-Init on such ECSs.
- For ECSs created from external image files, install and configure Cloudbase-Init by performing the operations in this section.
Cloudbase-Init is open-source software. If the installed version has security vulnerabilities, you are advised to upgrade it to the latest version.
+Prerequisites
- An EIP has been bound to the ECS.
- You have logged in to the ECS.
- The IP address obtaining mode of the ECS is DHCP.
Install Cloudbase-Init
- On the Windows Start menu, choose Control Panel > Programs > Programs and Features and check whether Cloudbase-Init 1.1.2 is installed.
- If Cloudbase-Init 1.1.2 is installed, skip the subsequent steps and go to Configure Cloudbase-Init.
- If Cloudbase-Init is installed but the version is not 1.1.2, uninstall Cloudbase-Init and go to the next step.
- If Cloudbase-Init is not installed, go to the next step.
- Double-click the Cloudbase-Init installation package.
- Click Next.
- Select I accept the terms in the License Agreement and click Next.
- Retain the default path and click Next.
- In the Configuration options window, enter Administrator for Username, select COM1 for Serial port for logging, and ensure that Run Cloudbase-Init service as LocalSystem is not selected.
The version number shown in the figure is for reference only.
Figure 1 Configuring parameters-
- Click Next.
- Click Install.
- In the Files in Use dialog box, select Close the application and attempt to restart them and click OK.
- Check whether the version of the OS is Windows desktop. +
- Click Next.
- Click Install.
- In the Files in Use dialog box, select Close the application and attempt to restart them and click OK.
- Check whether the version of the OS is Windows desktop.
- In the Completed the Cloudbase-Init Setup Wizard window, ensure that neither option is selected.Figure 2 Completing the Cloudbase-Init installation
@@ -49,25 +51,25 @@ add_metadata_private_ip_route=False The version number shown in the figure is for reference only.
- When creating an image using a Windows ECS, you need to change the SAN policy of the ECS to OnlineAll. Otherwise, EVS disks attached to the ECSs created from the image may be offline.
Windows has three types of SAN policies: OnlineAll, OfflineShared, and OfflineInternal.
-Table 1 SAN policies Type
+Table 1 SAN policies Type
Description
+Description
OnlineAll
+OnlineAll
All newly detected disks are automatically brought online.
+All newly detected disks are automatically brought online.
OfflineShared
+OfflineShared
All disks on sharable buses, such as iSCSI and FC, are left offline by default, while disks on non-sharable buses are kept online.
+All disks on sharable buses, such as iSCSI and FC, are left offline by default, while disks on non-sharable buses are kept online.
OfflineInternal
+OfflineInternal
All newly detected disks are left offline.
+All newly detected disks are left offline.
-+Scenarios
To ensure that you can use the user data injection function to inject initial custom information into ECSs created from a private image (such as setting the ECS login password), install Cloud-Init on the ECS used to create the image.
- You need to download Cloud-Init from its official website. Therefore, you must bind an EIP to the ECS.
- If Cloud-Init is not installed, you cannot configure an ECS. As a result, you can only use the password in the image file to log in to the created ECSs.
- By default, ECSs created from a public image have Cloud-Init installed. You do not need to install or configure Cloud-Init on such ECSs.
- For ECSs created using an external image file, install and configure Cloud-Init by performing the operations in this section. For how to configure Cloud-Init, see Configuring Cloud-Init.
Cloud-Init is open-source software. If the installed version has security vulnerabilities, you are advised to upgrade it to the latest version.
+Prerequisites
- An EIP has been bound to the ECS.
- You have logged in to the ECS.
- The IP address obtaining mode of the ECS is DHCP.
Procedure
- Check whether Cloud-Init has been installed.
For details, see Check Whether Cloud-Init Has Been Installed.
@@ -21,7 +23,7 @@
If Cloud-Init has been installed, perform the following operations:- Check whether to use the certificate in the ECS OS. If the certificate is no longer used, delete it.
- If the certificate is stored in a directory of user root, for example, /$path/$to/$root/.ssh/authorized_keys, run the following commands:
cd /root/.ssh
+If Cloud-Init has been installed, perform the following operations:- Check whether to use the SSH certificate in the ECS OS. If the certificate is no longer used, delete it.
- If the certificate is stored in a directory of user root, for example, /$path/$to/$root/.ssh/authorized_keys, run the following commands:
cd /root/.ssh
rm authorized_keys
- If the certificate is not stored in a directory of user root, for example, /$path/$to/$none-root/.ssh/authorized_keys, run the following commands:
cd /home/centos/.ssh
rm authorized_keys
@@ -54,29 +56,29 @@
- If the certificate is stored in a directory of user root, for example, /$path/$to/$root/.ssh/authorized_keys, run the following commands:
- Check whether to use the SSH certificate in the ECS OS. If the certificate is no longer used, delete it.
- If the certificate is stored in a directory of user root, for example, /$path/$to/$root/.ssh/authorized_keys, run the following commands:
- CentOS
Table 1 lists the Cloud-Init installation paths for CentOS. Select the required installation package from the following addresses. -Table 1 Cloud-Init installation package addresses OS Type
+Table 1 Cloud-Init installation package addresses OS Type
Version
+Version
How to Obtain
+How to Obtain
CentOS
+CentOS
6 32-bit
+6 32-bit
+ 6 64-bit
+6 64-bit
https://archives.fedoraproject.org/pub/archive/epel/6/x86_64/
+https://archives.fedoraproject.org/pub/archive/epel/6/x86_64/
7 64-bit
+7 64-bit
https://archives.fedoraproject.org/pub/epel/7/x86_64/Packages/e/
+https://archives.fedoraproject.org/pub/epel/7/x86_64/Packages/e/
- Run the following commands to enable Cloud-Init to automatically start upon system boot:
-systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service
systemctl status cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service
- Debian and Ubuntu
Before installing Cloud-Init, ensure that the network installation source address has been configured for the OS by checking whether the /etc/apt/sources.list file contains the installation source address of the software package. If the file does not contain the address, configure the address by following the instructions on the Debian or Ubuntu official website.
+- Debian and Ubuntu
Before installing Cloud-Init, ensure that the network installation source address has been configured for the OS by checking whether the /etc/apt/sources.list file contains the installation source address of the software package. If the file does not contain the address, configure the address by following the instructions on the Debian or Ubuntu official website.
- Run the following commands to install Cloud-Init:
apt-get install cloud-init
- Run the following commands to enable Cloud-Init to automatically start upon system boot:
systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service
diff --git a/docs/ims/umn/en-us_topic_0032042418.html b/docs/ims/umn/en-us_topic_0032042418.html index 61557a70..dfbfd1bd 100644 --- a/docs/ims/umn/en-us_topic_0032042418.html +++ b/docs/ims/umn/en-us_topic_0032042418.html @@ -1,11 +1,11 @@Obtaining the Project ID
-Scenarios
Before a tenant shares an image with you, you need to provide your project ID.
+-Scenarios
Before a tenant shares an image with you, you need to provide your project ID.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the username in the upper right corner and select My Credentials from the drop-down list.
On the My Credentials page, view the project ID in the project list.
+ - Click the username in the upper right corner and select My Credentials from the drop-down list.
On the My Credentials page, view the project ID.
Images can be shared only within the region where they reside. So, obtain the project ID in the same region.
Figure 1 Viewing the project ID
-Prerequisites
- If the image to be shared is an encrypted image, authorize the key (it must be a custom key) used for encrypting the image. For details, see How Do I Authorize a Key?
- You have obtained the project ID from the target tenant.
- Before sharing an image, ensure that any sensitive data has been deleted from the image.
Procedure
- Share multiple images.
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Share multiple images.
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab.
- Select the private images to share and click Share above the image list.
- In the Share Image dialog box, enter the project ID of the target tenant.
To share images with more than one tenant, separate their project IDs with commas (,).
- You can enter a maximum of 100 project IDs at a time.
- You can share images only within the region where they reside.
- If the target tenant is a multi-project user, you can share images to any project of the tenant.
- Click OK.
- Access the IMS console.
- Share a single image.
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+ - Share a single image.
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab.
- Locate the row that contains the private image you are to share, click More in the Operation column, and select Share from the drop-down list.
- In the Share Image dialog box, enter the project ID of the target tenant.
To share an image with more than one tenant, separate their project IDs with commas (,).
-- You can enter a maximum of 100 project IDs at a time.
- You can share images only within the region where they reside.
- If the target tenant is a multi-project user, you can share images to any project of the tenant.
- Click OK.
Related Operations
- After you share images with a tenant, the tenant can accept the shared images on the Images Shared with Me page on the IMS console. For detailed operations, see Accepting or Rejecting Shared Images.
- If the shared image is an encrypted image and is accepted by a tenant, the tenant can use this image to apply for ECSs or replace the key of this image with its own by replicating the shared image. If the tenant has accepted the shared image but have not performed any other operations, do not cancel the authorization of the key. Otherwise, the shared image will be unavailable to the tenant.
Related Operations
- After you share images with a tenant, the tenant can accept the shared images on the Images Shared with Me page on the IMS console. For detailed operations, see Accepting or Rejecting Shared Images.
- If the shared image is an encrypted image and is accepted by a tenant, the tenant can use this image to apply for ECSs or replace the key of this image with its own by replicating the shared image. If the tenant has accepted the shared image but have not performed any other operations, do not cancel the authorization of the key. Otherwise, the shared image will be unavailable to the tenant.
diff --git a/docs/ims/umn/en-us_topic_0032042420.html b/docs/ims/umn/en-us_topic_0032042420.html index 7f7132c7..6324a84d 100644 --- a/docs/ims/umn/en-us_topic_0032042420.html +++ b/docs/ims/umn/en-us_topic_0032042420.html @@ -7,15 +7,15 @@-Prerequisites
- Another tenant has shared images with you.
- If the shared image is a full-ECS image, you need to create a server backup vault to store the full-ECS image and the backups of the full-ECS image before accepting the shared image. When creating a server backup vault, set Protection Type to Backup.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- In the upper left corner, switch to the region where the target project resides and then select the project.
- Click the Images Shared with Me tab.
A message is displayed above the image list asking you whether to accept the shared images.
- To accept all the shared images, click Accept All in the upper right corner.
- To accept some images, select the images and click Accept.
- To reject some images, select the images and click Reject.
If no message is displayed, check whether you have selected a correct region.
- (Optional) In the Accept Full-ECS Image dialog box, select a server backup vault with the Backup protection type and click OK.
This dialog box is displayed when the shared image is a full-ECS image.
-When accepting a full-ECS image, you must specify a vault for storing the CBR backups associated with the full-ECS image. The vault capacity must be no less than the total capacities of the system disk and data disk backups.
- @@ -23,7 +23,7 @@For more information about server backup vaults, see Cloud Backup and Recovery User Guide.
+When accepting a full-ECS image, you must specify a vault for storing the CBR backups associated with the full-ECS image. The vault capacity must be no less than the total capacities of the system disk and data disk backups.
+ For more information about server backup vaults, see Cloud Backup and Recovery User Guide.
- Accepted: After an image is accepted, it is displayed in the shared image list. You can use the image to create ECSs.
- Rejected: After an image is rejected, it is not displayed in the shared image list. You can click Rejected Images to view the images you have rejected and you can still choose to accept them.
diff --git a/docs/ims/umn/en-us_topic_0032042421.html b/docs/ims/umn/en-us_topic_0032042421.html index 856f2d40..53980ea4 100644 --- a/docs/ims/umn/en-us_topic_0032042421.html +++ b/docs/ims/umn/en-us_topic_0032042421.html @@ -6,9 +6,9 @@Follow-up Procedure
After accepting a system disk image or full-ECS image shared by another tenant, you can:
-- Use the image to create one or more ECSs (select Shared Image during ECS creation).
- Use the image to change the OS of existing ECSs. For details, see "Changing the OS" in Elastic Cloud Server User Guide.
- Use the image to create one or more ECSs (select Shared Image during ECS creation).
- Use the image to change the OS of existing ECSs. For details, see "Changing the OS" in Elastic Cloud Server User Guide.
After accepting a data disk image shared by another tenant, you can use the image to create EVS disks (locate the row that contains the image and click Create Data Disk in the Operation column).
After accepting the encrypted image shared by another tenant, you can use the image to apply for ECSs or EVS disks or replace the key of the image with your own key by replicating the shared image. The replacement prevents the shared image from being unavailable when the tenant who shares the image cancels the key authorization.
-Prerequisites
You have accepted images shared by other users.
diff --git a/docs/ims/umn/en-us_topic_0032042422.html b/docs/ims/umn/en-us_topic_0032042422.html index 39e62d12..878b6c7c 100644 --- a/docs/ims/umn/en-us_topic_0032042422.html +++ b/docs/ims/umn/en-us_topic_0032042422.html @@ -6,9 +6,9 @@Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Images Shared with Me tab.
- Determine the next step based on how many images you are to reject.
- To reject multiple images: select the images to be rejected and click Reject above the image list. In the displayed dialog box, click Yes.
- To reject a specific image: locate the image to be rejected and click Reject in the Operation column. In the displayed dialog box, click Yes.
- Click the Images Shared with Me tab.
- Determine the next step based on how many images you are to reject.
- To reject multiple images: select the images to be rejected and click Reject above the image list. In the displayed dialog box, click Yes.
- To reject a specific image: locate the image to be rejected and click Reject in the Operation column. In the displayed dialog box, click Yes.
- Access the IMS console.
- Access the IMS console.
-Prerequisites
You have shared private images with others.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab.
- Locate the row that contains the private image that you no longer want to share, and choose More > Share in the Operation column.
- In the Share Image dialog box, click the Stop Sharing tab.
- Select the project ID for which you want to stop image sharing and click OK.
- Click the Private Images tab.
- Locate the row that contains the private image that you no longer want to share, and choose More > Share in the Operation column.
- In the Share Image dialog box, click the Stop Sharing tab.
- Select the project for which you want to stop the image sharing and click OK.
- Access the IMS console.
diff --git a/docs/ims/umn/en-us_topic_0032042423.html b/docs/ims/umn/en-us_topic_0032042423.html index 85a799cc..890e9a3e 100644 --- a/docs/ims/umn/en-us_topic_0032042423.html +++ b/docs/ims/umn/en-us_topic_0032042423.html @@ -5,9 +5,9 @@-Prerequisites
- You have shared private images.
- You have obtained the project IDs of the tenants to be added.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab.
- Click the image name to view image details.
- Click Add Tenant.
- In the Add Tenant dialog box, enter the project ID of the tenant to be added and click OK.
To add multiple tenants, enter their project IDs and separate them with commas. Click OK.
+ - Click the Private Images tab.
- Click the image name to view image details.
- Click Add Tenant.
- In the Add Tenant dialog box, enter the project ID of the tenant to be added, and click OK.
To add multiple tenants, enter their project IDs and separate them with commas (,). Click OK.
- You can share images only within the region where they reside.
- A project ID uniquely identifies a tenant in a specific region. If you enter a project ID that belongs to a different region from the images, a message will display indicating that the tenant cannot be found.
Deleting Image Recipients Who Can Use Shared Images
-Scenarios
This section describes how to delete image recipients who can use shared images.
Prerequisites
- You have shared private images.
- You have obtained project IDs of the image recipients.
-Prerequisites
- You have shared private images.
- You have obtained the project IDs of the image recipients.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab.
- Click the image name to view image details.
- View the tenants who can use shared image.
- Delete one or all of the recipients:
- To delete a single image recipient, locate the target recipient and click Delete.
- To delete all image recipients, click Delete All above the image recipient list.
- Click Yes.
What Will the System Do to an Image File When I Use the File to Register a Private Image?
You are advised to enable automatic configuration when registering a private image using an image file. Then, the system will perform the following operations:
-Linux
- Check whether any PV drivers exist. If yes, the system deletes them.
- Modify the grub and syslinux configuration files to add the OS kernel boot parameters and change the disk partition name (UUID=UUID of the disk partition).
- Change the names of the disk partitions in the /etc/fstab file (UUID=UUID of the disk partition).
- Check whether the initrd file has the IDE driver. If no, the system will load the IDE driver.
- Modify the X Window configuration file /etc/X11/xorg.conf to prevent display failures.
- Delete services of VMware tools.
- Record the latest automatic modification made to the image into /var/log/rainbow_modification_record.log.
- Copy the built-in VirtIO driver to initrd or initramfs. For details, see External Image File Formats and Supported OSs.
-Linux
- Check whether any PV drivers exist. If yes, the system deletes them.
- Modify the grub and syslinux configuration files to add the OS kernel boot parameters and change the disk partition name (UUID=UUID of the disk partition).
- Change the names of the disk partitions in the /etc/fstab file (UUID=UUID of the disk partition).
- Check whether the initrd file has the IDE driver. If no, the system will load the IDE driver.
- Modify the X Window configuration file /etc/X11/xorg.conf to prevent display failures.
- Delete services of VMware tools.
- Record the latest automatic modification made to the image into /var/log/rainbow_modification_record.log.
- Copy built-in VirtIO drivers to initrd or initramfs. For details, see External Image File Formats and Supported OSs.
For the following image files, the system does not copy this driver after Enable automatic configuration is selected:
- Image files whose /usr directory is an independent partition
- Fedora 29 64bit, Fedora 30 64bit, and CentOS 8.0 64bit image files that use the XFS file system
- SUSE 12 SP4 64bit image files that use the ext4 file system
Windows
- Restore the IDE driver to enable the OS to use this driver for its initial start.
- Delete the registry keys of the mouse and keyboard and generate the registry keys on the new platform to ensure that the mouse and keyboard are available.
- Inject the VirtIO driver offline so that the system can start without UVP VMTools installed.
- Restore DHCP. The system will dynamically obtain information such as the IP address based on the DHCP protocol.
Windows
- Restore the IDE driver so that the OS can use this driver for its initial start.
- Delete the registry keys of the mouse and keyboard and generate the registry keys again to ensure that the mouse and keyboard are available on the new cloud platform.
- Inject VirtIO drivers offline so that the OS can start without UVP VMTools installed.
- Restore DHCP. The OS will dynamically obtain information such as the IP address based on the DHCP protocol.
diff --git a/docs/ims/umn/en-us_topic_0032326546.html b/docs/ims/umn/en-us_topic_0032326546.html index c61698aa..9fcbf0cb 100644 --- a/docs/ims/umn/en-us_topic_0032326546.html +++ b/docs/ims/umn/en-us_topic_0032326546.html @@ -1,7 +1,7 @@Image Deletion
-Will a Private Image Be Automatically Deleted If I Delete the ECS Used to Create the Image?
No. Private images created using ECSs are stored in OBS buckets. Deleting the ECS used to create a private image does not affect the image.
+Will a Private Image Be Automatically Deleted If I Delete the ECS Used to Create the Image?
No. Private images created using ECSs are stored in OBS buckets. Deleting the ECS used to create a private image does not affect the image.
diff --git a/docs/ims/umn/en-us_topic_0034011241.html b/docs/ims/umn/en-us_topic_0034011241.html index 60697f28..08c748ac 100644 --- a/docs/ims/umn/en-us_topic_0034011241.html +++ b/docs/ims/umn/en-us_topic_0034011241.html @@ -11,12 +11,13 @@Can I Delete an Image I Shared with Others If My Image Quota Becomes Insufficient?
Yes. You can delete a shared image without requiring any operation by image recipients. After you delete the image, the image recipients cannot use it any longer. Inform the image recipients to back up their data before you delete the image.
-Constraints
- An image can only be exported to a Standard bucket that is in the same region as the image.
- The following private images cannot be exported:
- Full-ECS images
- ISO images
- Private images created from a Windows, SUSE, Red Hat, Ubuntu, or Oracle Linux public image
- The image size must be less than 1 TB. Images larger than 128 GB support only fast export.
Prerequisites
An OBS bucket is available in the region where the private image is located.
-If no OBS bucket is available, create one by referring to Object Storage Service User Guide. Select Standard for Storage Class.
+-Prerequisites
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Locate the row that contains the image to be exported, click More in the Operation column and select Export.
- In the displayed Export Image dialog box, set the following parameters:
- Fast Export: To export an image larger than 128 GB, you must enable fast export, and you cannot specify the format of the exported image (which can only be ZVHD2). After exporting the image, you can use qemu-img-hw to convert it to your desired format. For details, see Converting the Image Format Using qemu-img-hw.
For details about differences between export and fast export, see What Are the Differences Between Import/Export and Fast Import/Export?
+- Locate the row that contains the image to be exported, click More in the Operation column and select Export.
- In the displayed Export Image dialog box, set the following parameters:
- Fast Export: To export an image larger than 128 GB, you must enable fast export, and you cannot specify the format of the exported image (which can only be ZVHD2). After exporting the image, you can use qemu-img-hw to convert it to your desired format. For details, see Converting the Image Format Using qemu-img-hw.
For details about differences between export and fast export, see What Are the Differences Between Import/Export and Fast Import/Export?
- Format: Select one from qcow2, vmdk, vhd, and zvhd as you need.
- Name: Enter a name that is easy to identify.
- Storage Path: Click
to expand the bucket list and select an OBS bucket for storing the exported image.diff --git a/docs/ims/umn/en-us_topic_0037352059.html b/docs/ims/umn/en-us_topic_0037352059.html index a6b9670e..41dd39de 100644 --- a/docs/ims/umn/en-us_topic_0037352059.html +++ b/docs/ims/umn/en-us_topic_0037352059.html @@ -1,11 +1,11 @@ An image can only be exported to a Standard bucket that is in the same region as the image. So, only such buckets are available in the list.
Obtaining Required Software Packages
-UVP VMTools
Table 1 lists the UVP VMTools software packages required for optimizing Windows private images.
+UVP VMTools
Table 1 lists the UVP VMTools software packages required for optimizing Windows private images.
-Table 1 UVP VMTools software packages Software Package
+Table 1 UVP VMTools software packages Software Package
OS
+OS
How to Obtain
Installing UVP VMTools
The following operations describe how to install UVP VMTools. vmtools-WIN2016-x64.exe extracted from vmtools-WIN2016-x64.zip is used as an example.
-- Log in to the Windows ECS using VNC.
For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+- Log in to the Windows ECS using VNC.
For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
You must log in to the ECS using VNC. Remote desktop connection is not allowed because the NIC driver needs to be updated during the installation but the NIC is in use for the remote desktop connection. As a result, the installation will fail.
- Download the required UVP VMTools based on the ECS OS and Obtaining Required Software Packages.
- Decompress the UVP Tools software package vmtools-WIN2016-x64.zip.
- Right-click vmtools-WIN2016-x64.exe, and select Run as administrator from the shortcut menu.
- In the displayed dialog box, select I agree to the license terms and conditions and click Install.Figure 1 Installing UVP VMToolsdiff --git a/docs/ims/umn/en-us_topic_0037352185.html b/docs/ims/umn/en-us_topic_0037352185.html index eea0ecb9..dd94d5b6 100644 --- a/docs/ims/umn/en-us_topic_0037352185.html +++ b/docs/ims/umn/en-us_topic_0037352185.html @@ -1,10 +1,23 @@
Checking Whether a Private Image Needs to be Optimized
-- If the ECS virtualization is KVM and VirtIO drivers are not installed, optimization is required.
- If the ECS virtualization is KVM and VirtIO drivers are installed, optimization is not required.
Procedure
- Run the following command to check whether the ECS has VirtIO drivers installed:
lsinitrd /boot/initramfs-$(uname -r).img | grep virtio
-- If virtio is displayed, VirtIO drivers have been installed. For more information, see Creating a Linux System Disk Image from an External Image File.
-
- Otherwise, VirtIO drivers have not been installed. Optimize the private image as instructed in Process.
diff --git a/docs/ims/umn/en-us_topic_0040740508.html b/docs/ims/umn/en-us_topic_0040740508.html index 133c4630..f301e3b7 100644 --- a/docs/ims/umn/en-us_topic_0040740508.html +++ b/docs/ims/umn/en-us_topic_0040740508.html @@ -67,7 +67,7 @@- If the virtualization type is KVM and VirtIO drivers are not installed, optimization is required.
- If the virtualization type is KVM and VirtIO drivers are installed, optimization is not required.
Procedure
- Check whether VirtIO drivers have been installed.
- CentOS/EulerOS
For initramfs, run the following command:
+lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+For initrd, run the following command:
+lsinitrd /boot/initrd-`uname -r` | grep virtio
+ - Ubuntu/Debian +
- SUSE/openSUSE + +
If virtio is displayed, VirtIO drivers have been installed. For more information, see Creating a Linux System Disk Image from an External Image File.
+
+Otherwise, VirtIO drivers have not been installed. Optimize the private image as instructed in Process.
- CentOS/EulerOS
- If virtio is displayed, VirtIO drivers have been installed. For more information, see Creating a Linux System Disk Image from an External Image File.
- Log in to the Windows ECS using VNC.
Windows
- Install software in the bms-network-config package.
- Install Cloudbase-Init.
- Delete residual files from the OS.
- Install the bms-network-config package.
- Install Cloudbase-Init.
- Delete residual files from the OS.
"Creating a Private Image from a BMS" in Bare Metal Server User Guide
2024-01-15
+2024-05-11
+Modified the following content:
+Deleted ECSs from OSs Supported by Different Types of ECSs that have been taken offline, including M2, P1, P2, HL1, H2, FP1c, and FP1cne.
+2024-01-15
Added the following content:
@@ -20,7 +26,7 @@2023-10-30
Added the following content:
-- Product Advantages
- Application Scenarios
- Features
- Constraints
- Basic Concepts
- What Do I Do If I Cannot Find a Desired Image?
- What Are the Differences Between Images and Backups?
- Can I Tailor an Image?
- How Can I Back Up the Current Status of an ECS for Restoration in the Case of a System Fault?
- How Can I Apply a Private Image to an Existing ECS?
- Can I Import Data from a Data Disk Image to a Data Disk?
- Full-ECS Image FAQs
- How Can I Use a Backup to Create an EVS Disk or ECS?
- Is There Any Difference Between the Image Created from a CSBS/CBR Backup and That Created from an ECS?
- What Do I Do If an ECS Created from a Windows Image Failed to Start After Running Sysprep?
- What Are the Differences Between Sharing Images and Replicating Images?
- How Do I Select an OS?
- Why Can't I Find My Private Image When I Want to Use It to Create an ECS or Change the OS of an ECS?
- Image Replication
- Image Deletion
- Cloud-Init
- Can I Change the Image of a Purchased ECS?
- Driver Installation
- Must I Install Guest OS Drivers on an ECS?
- Why Do I Need to Install and Update VMTools for Windows?
- What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?
- How Do I Install UVP VMTools in Windows?
- How Do I Install Native KVM Drivers in Linux?
- Image Tags
- How Many Tags Can I Add to an Image?
- How Do I Add, Delete, and Modify Image Tags?
- How Do I Search for Private Images by Tag?
- Product Advantages
- Application Scenarios
- Features
- Constraints
- Basic Concepts
- What Do I Do If I Cannot Find a Desired Image?
- What Are the Differences Between Images and Backups?
- Can I Tailor an Image?
- How Can I Back Up the Current Status of an ECS for Restoration in the Case of a System Fault?
- How Can I Apply a Private Image to an Existing ECS?
- Can I Import Data from a Data Disk Image to a Data Disk?
- Full-ECS Image FAQs
- How Can I Use a Backup to Create an EVS Disk or ECS?
- Is There Any Difference Between the Image Created from a CSBS/CBR Backup and That Created from an ECS?
- What Do I Do If an ECS Created from a Windows Image Failed to Start After Running Sysprep?
- What Are the Differences Between Sharing Images and Replicating Images?
- How Do I Select an OS?
- Why Can't I Find My Private Image When I Want to Use It to Create an ECS or Change the OS of an ECS?
- Image Replication
- Image Deletion
- Cloud-Init Installation FAQ
- Can I Change the Image of a Purchased ECS?
- Driver Installation
- Must I Install Guest OS Drivers on an ECS?
- Why Do I Need to Install and Update VMTools for Windows?
- What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?
- How Do I Install UVP VMTools in Windows?
- How Do I Install Native KVM Drivers in Linux?
- Image Tags
- How Many Tags Can I Add to an Image?
- How Do I Add, Delete, and Modify Image Tags?
- How Do I Search for Private Images by Tag?
Modified the following content:
- Added the figure showing relationships between IMS and other services in Related Services.
- Added figures in Introduction.
- Updated the description that system disk images cannot be exported in Introduction.
- Added restrictions on VMDK image files in Preparing an Image File.
- Added that the bucket file and the image to be registered must be in the same region in Uploading an External Image File and Uploading an External Image File.
- Added more information about sharing full-ECS images and updated the console operation screenshot in Creating a Full-ECS Image from an ECS.
- Added a screenshot of the console operations in Creating a Full-ECS Image from a CBR Backup.
- Added a screenshot of the console operations in Quickly Importing an Image File (Linux).
- Added a screenshot of the console operations in Quickly Importing an Image File (Windows).
- Added the Boot Mode attribute and updated the console operation screenshot accordingly in Modifying an Image.
- Added a screenshot of the console operations in Checking the Disk Capacity of an Image.
- Added the description of using a full-ECS private image to create an ECS in Creating an ECS from an Image.
- Added new scenarios in Deleting Images.
- Clarified that the cloud platform does not ensure the integrity or security of shared images and advised users to use images from a trusted sharer in Overview.
- Added notes for a step in Sharing Specified Images.
- Added follow-up operations in Accepting or Rejecting Shared Images.
- Added new questions and answers in Image Creation FAQs.
- Added new questions and answers in Image Sharing FAQs.
- Updated the console operation screenshot in How Do I Make a System Disk Image Support Fast ECS Creation?.
- Added Ubuntu 18 and later in Setting the NIC to DHCP.
- Added a Cloudbase-Init configuration item in Installing and Configuring Cloudbase-Init.
- Updated steps in Configuring Cloud-Init.
- Optimized operations in Rejecting Accepted Images.
- Added a screenshot of the console operations in Tagging an Image.
2017-10-30
Modified the following content:- Added the OSs supported by external image files, including Oracle Linux Server release 7.4 64bit, Red Hat Linux Enterprise 7.4 64bit, and CentOS 7.4 64bit in External Image File Formats and Supported OSs.
- Changed the upper limit of the system disk size of the ECS used to create a private image to 1024 GB.
Modified the following content:- Added the OSs supported by external image files, including Oracle Linux Server release 7.4 64bit, Red Hat Linux Enterprise 7.4 64bit, and CentOS 7.4 64bit in External Image File Formats and Supported OSs.
- Changed the upper limit of the system disk capacity to 1024 GB when creating a private image.
2017-04-28
Added the following content:- Configuring Console Logging
- What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
Added the following content:Modified the following content:
Added support for external image files containing CoreOS 1298.6.0 in External Image File Formats and Supported OSs.
diff --git a/docs/ims/umn/en-us_topic_0047501112.html b/docs/ims/umn/en-us_topic_0047501112.html index 1daa4e94..dd220bad 100644 --- a/docs/ims/umn/en-us_topic_0047501112.html +++ b/docs/ims/umn/en-us_topic_0047501112.html @@ -1,10 +1,10 @@Optimization Process
-The proper running of ECS depends on KVM Guest OS driver (UVP VMTools). To ensure that ECSs support KVM and to improve network performance, the UVP VMTools must be installed for the image.
-- Create an ECS using the Windows private image to be optimized and log in to the ECS.
- Install the UVP VMTools required for creating ECSs in the KVM virtual resource pool.
For details, see Installing UVP VMTools.
- - On the ECS, choose Control Panel > Power Options. Click Choose when to turn off the display, select Never for Turn off the display, and save the changes.
- Clear system logs and then stop the ECS.
For details, see Clearing System Logs.
- - Create a Windows private image using the ECS.
The proper running of ECSs depends on KVM Guest OS driver (UVP VMTools). To ensure that ECSs support KVM and to improve network performance, the UVP VMTools must be installed for the image.
+- Create an ECS using the Windows private image to be optimized and log in to the ECS.
- Install the UVP VMTools which is required to create ECSs using KVM virtual resources.
For details, see Installing UVP VMTools.
+ - On the ECS, choose Control Panel > Power Options. Click Choose when to turn off the display, select Never for Turn off the display, and save the changes.
- Clear system logs and then stop the ECS.
For details, see Clearing System Logs.
+ - Create a Windows private image from the ECS.
diff --git a/docs/ims/umn/en-us_topic_0047501133.html b/docs/ims/umn/en-us_topic_0047501133.html index 9059dd80..c9e90af9 100644 --- a/docs/ims/umn/en-us_topic_0047501133.html +++ b/docs/ims/umn/en-us_topic_0047501133.html @@ -1,15 +1,15 @@Optimization Process
-A Linux ECS can run properly only when VirtIO drivers have been installed on it and the disk ID in its GRUB configuration file and fstab file has been changed to UUID.
-Preparations
- Use the Linux image to be optimized to create an ECS, and start and log in to the ECS.
- Check whether the private image needs to be optimized.
For details, see Checking Whether a Private Image Needs to be Optimized.
+A Linux ECS can run properly only when native KVM (VirtIO) drivers have been installed on it and the disk ID in its GRUB configuration file and fstab file has been changed to UUID.
+Preparations
- Use the Linux image to be optimized to create an ECS, and start and log in to the ECS.
- Check whether the private image needs to be optimized.
For details, see Checking Whether a Private Image Needs to be Optimized.
Process
- Change the disk ID in the GRUB configuration file to UUID.
For details, see Changing the Disk Identifier in the GRUB Configuration File to UUID.
- Change the disk ID in the fstab file to UUID.
For details, see Changing the Disk Identifier in the fstab File to UUID.
- Install native KVM drivers.
For details, see Installing Native KVM Drivers.
- - Delete log files and historical records, and stop the ECS.
For details, see Clearing System Logs.
- - Create a Linux private image using the ECS.
- Delete log files and historical records, and stop the ECS.
For details, see Clearing System Logs.
+- Create a Linux private image from the ECS.
diff --git a/docs/ims/umn/en-us_topic_0049177180.html b/docs/ims/umn/en-us_topic_0049177180.html index 9cbcb10f..00e3f031 100644 --- a/docs/ims/umn/en-us_topic_0049177180.html +++ b/docs/ims/umn/en-us_topic_0049177180.html @@ -1,19 +1,20 @@Replicating Images
-Scenarios
You can convert encrypted and unencrypted images into each other or enable some advanced features (such as fast ECS creation from an image) using the image replication function. You may need to replicate an image in the following scenarios:
+Scenarios
You can convert encrypted and unencrypted images into each other or enable some advanced features (such as fast ECS creation from an image) using the image replication function. You may need to replicate an image to:
- Replicate an encrypted image to an unencrypted one.
- Replicate an encrypted image to an encrypted one.
Keys for encrypting the images cannot be changed. If you want to change the key of an encrypted image, you can replicate this image to a new one and encrypt the new image using an encryption key.
- Replicate an unencrypted image to an encrypted one.
If you want to store an unencrypted image in an encrypted way, you can replicate this image as a new one and encrypt the new image using a key.
- - Optimize a system disk image so that it can be used to quickly create ECSs.
Fast Create greatly reduces the time required for creating ECSs from a system disk image. Currently, this feature is supported by all newly created system disk images by default. Existing system disk images may not support this function. You can optimize the images using the image replication function. For example, if image A does not support fast ECS creation, you can replicate it to generate image copy_A that supports fast ECS creation.
+ - Optimize a system disk image so that it can be used to quickly create ECSs.
Fast Create greatly reduces the time required for creating ECSs from a system disk image. Currently, this feature is supported by all newly created system disk images by default. Existing system disk images may not support this function. You can optimize the images using the image replication function. For example, if image A does not support fast ECS creation, you can replicate it to generate image copy_A that supports fast ECS creation.
Constraints
- Full-ECS images cannot be replicated.
- Private images created using ISO files do not support in-region replication.
-Prerequisites
The images to be replicated are in the Normal state.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+diff --git a/docs/ims/umn/en-us_topic_0049196766.html b/docs/ims/umn/en-us_topic_0049196766.html index da043af9..ab2fd1c7 100644 --- a/docs/ims/umn/en-us_topic_0049196766.html +++ b/docs/ims/umn/en-us_topic_0049196766.html @@ -2,7 +2,7 @@Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Locate the row that contains the image to be replicated, click More in the Operation column, and select Replicate.
- In the displayed Replicate Image dialog box, set the following parameters:
- Name: Enter a name that is easy to identify.
- Description: This parameter is optional. Enter description of the replication.
- Encryption: If you want to encrypt the image or change a key, select KMS encryption and select the key you want to use from the drop-down list.
- Locate the row that contains the image to be replicated, click More in the Operation column, and select Replicate.
- In the displayed Replicate Image dialog box, set the following parameters:
- Name: Enter a name that is easy to identify.
- Description: This parameter is optional. Enter description of the replication.
- Encryption: If you want to encrypt the image or change a key, select KMS encryption and select the key you want to use from the drop-down list.
- Click OK.
On the Private Images page, view the replication progress. If the status of the new image becomes Normal, the image replication is successful.
How Can I Back Up the Current Status of an ECS for Restoration in the Case of a System Fault?
You can back up the ECS in any of the following ways:
-- (Recommended) Use CBR to create a scheduled backup task for the ECS. If the ECS fails, select a backup corresponding to the time you want the ECS to restore to, create a full-ECS image from the backup, and use the image to apply for a new ECS or to reinstall the OS.
- Create a system disk image from the ECS. If the ECS fails, use the system disk image to apply for a new ECS or to reinstall the OS.
- Create a snapshot for the system disk of the ECS. If the ECS fails, you can roll it back from the snapshot.
- (Recommended) Use CBR to create a scheduled backup task for the ECS. If the ECS fails, select a backup corresponding to the time you want the ECS to restore to, create a full-ECS image from the backup, and use the image to apply for a new ECS or to reinstall the OS.
- Create a system disk image from the ECS. If the ECS fails, use the system disk image to apply for a new ECS or to reinstall the OS.
- Create a snapshot for the system disk of the ECS. If the ECS fails, you can roll it back from the snapshot.
diff --git a/docs/ims/umn/en-us_topic_0058841396.html b/docs/ims/umn/en-us_topic_0058841396.html index 2eeb3650..aaa404a2 100644 --- a/docs/ims/umn/en-us_topic_0058841396.html +++ b/docs/ims/umn/en-us_topic_0058841396.html @@ -1,15 +1,15 @@ -What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
-The possible causes may be:- You have specified a small value.
Check the system disk size in the VHD image file. Specify a value no less than this size when you use the VHD image file to register an image.
- - The actual size of the VHD image file is larger than its virtual size, if this VHD image file is generated using qemu-img or a similar tool. For details, see https://bugs.launchpad.net/qemu/+bug/1490611.
Run the following command to check the VHD image file information:
+What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?
+diff --git a/docs/ims/umn/en-us_topic_0068002265.html b/docs/ims/umn/en-us_topic_0068002265.html index 5e70c74f..a3aa7d9f 100644 --- a/docs/ims/umn/en-us_topic_0068002265.html +++ b/docs/ims/umn/en-us_topic_0068002265.html @@ -7,12 +7,12 @@The possible causes may be:- You have specified a small value.
Check the system disk capacity in the VHD image file. Specify a value no less than this value when you use the VHD image file to register an image.
+ - After being converted using qemu-img or a similar tool, the VHD's virtual disk size becomes smaller than the actual system disk size. For details, see https://bugs.launchpad.net/qemu/+bug/1490611.
Run the following command to check the VHD image file information:
[xxxx@xxxxx test]$ qemu-img info 2g.vhd image: 2g.vhd file format: vpc virtual size: 2.0G (2147991552 bytes) disk size: 8.0K cluster_size: 2097152
-The virtual size is converted from the actual size (unit: byte) to an integer in GB. As a result, the actual file size 2147991552 bytes (2.0004 GB) is larger than the virtual size 2 GB. Therefore, you need to specify a value larger than the actual size 2.0004 GB. (The system disk size value on the management can only be an integer, so you only need to enter a value larger than 2.)
+The virtual size is converted from the actual size (unit: byte) to an integer in GB. After the conversion, the output virtual size 2 GB is smaller than the input actual size 2.0004 GB (2147991552 bytes). You need to specify an integer larger than the actual size 2.0004 GB on the management console.
- You have specified a small value.
-Constraints
An image can have a maximum of 10 tags.
Add, Delete, and Modify Image Tags
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+-Add, Delete, and Modify Image Tags
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab and click the image name to display the image details.
- Click the Tags tab, locate the target tag, and click Edit in the Operation column. In the displayed dialog box, modify the tag.
- Click the Tags tab, locate the target tag, and click Delete in the Operation column. In the displayed dialog box, click Yes.
- Click the Tags tab and then Add Tag. In the displayed dialog box, add a tag.
Search for Private Images by Tag
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+Search for Private Images by Tag
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab and then Search by Tag.Figure 1 Searching for images by tag
- Enter the tag key and value.
Neither the tag key nor tag value can be empty. When the tag key and tag value are matched, the system automatically shows your desired private images.
@@ -25,7 +25,7 @@After you accept private image image_test with tag (Enterprise=A) which is shared by another tenant, you can search for the image by tag.
- You cannot add tags to a shared image. The tags of a shared image are added by the tenant who shares the image with you.
- Log in to the management console.
- Under Computing, click Image Management Service.
The Private Images page is displayed.
+- Log in to the management console.
- Under Computing, click Image Management Service.
The Private Images page is displayed.
- Click the Images Shared with Me tab and then Search by Tag.
- Enter the tag key and value.
Neither the tag key nor tag value can be empty. When the tag key and tag value are matched, the system automatically shows your desired shared images.
- Click
to add a tag.You can add multiple tags to search for shared images. The system will display private images that match all tags.
- Click Search.
The system searches for shared images based on tag keys or tag values.
diff --git a/docs/ims/umn/en-us_topic_0069896389.html b/docs/ims/umn/en-us_topic_0069896389.html index abd0de85..06fc85a0 100644 --- a/docs/ims/umn/en-us_topic_0069896389.html +++ b/docs/ims/umn/en-us_topic_0069896389.html @@ -1,7 +1,7 @@How Can I Apply a Private Image to an Existing ECS?
-- You can change the OS of the ECS later. When you change the OS, select the created private image. For details about how to change the OS, see "Changing the OS" in Elastic Cloud Server User Guide.
- You can change the OS of the ECS later. When you change the OS, select the created private image. For details about how to change the OS, see "Changing the OS" in Elastic Cloud Server User Guide.
diff --git a/docs/ims/umn/en-us_topic_0075730699.html b/docs/ims/umn/en-us_topic_0075730699.html index ed6c664f..6aef42b7 100644 --- a/docs/ims/umn/en-us_topic_0075730699.html +++ b/docs/ims/umn/en-us_topic_0075730699.html @@ -5,7 +5,7 @@-Prerequisites
- You have rejected the images shared by others.
- The image owners have not stopped sharing the images.
Procedure
- Access the IMS console.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
+
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Log in to the Windows ECS using VNC.
- Fast Export: To export an image larger than 128 GB, you must enable fast export, and you cannot specify the format of the exported image (which can only be ZVHD2). After exporting the image, you can use qemu-img-hw to convert it to your desired format. For details, see Converting the Image Format Using qemu-img-hw.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Share multiple images.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
-Scenarios
After registering an external image file as a private image on the cloud platform, you can use the image to create ECSs or change the OSs of existing ECSs.
This section describes how to create an ECS from an image.
Procedure
Create an ECS by referring to Creating an ECS from an Image.
+Procedure
Create an ECS by referring to Creating an ECS from an Image.
Note the following when setting the parameters:
-diff --git a/docs/ims/umn/en-us_topic_0030713198.html b/docs/ims/umn/en-us_topic_0030713198.html index 1b1a7e16..c9af356c 100644 --- a/docs/ims/umn/en-us_topic_0030713198.html +++ b/docs/ims/umn/en-us_topic_0030713198.html @@ -2,7 +2,7 @@Follow-up Procedure
After a system disk image is created, you can use it to change the OS of an ECS.
Preparing an Image File
You need to prepare an image file that meets the platform requirements.
- Table 1 Linux image file requirements Image File Property
@@ -14,7 +14,7 @@OS
For details about the supported OS versions, see External Image File Formats and Supported OSs. These OSs support automatic configuration. For details, see What Will the System Do to an Image File When I Use the File to Register a Private Image? For other OSs, check and install the VirtIO driver (see Installing Native KVM Drivers). On the image registration page, select Other Linux. After the image is imported, whether the system is started depends on the driver integrity.
+For details about the supported OS versions, see External Image File Formats and Supported OSs. These OSs support automatic configuration. For details, see What Will the System Do to an Image File When I Use the File to Register a Private Image? For other OSs, check and install VirtIO drivers (see Installing Native KVM Drivers). On the image registration page, select Other Linux. After the image is imported, whether the system is started depends on the driver integrity.
Image format
@@ -57,7 +57,7 @@Other requirements
Constraints
Procedure
Use any of the following methods to modify an image:
-Method 1:
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
- Access the IMS console.
