diff --git a/docs/ims/umn/ALL_META.TXT.json b/docs/ims/umn/ALL_META.TXT.json index 2751a0792..dfa942d8b 100644 --- a/docs/ims/umn/ALL_META.TXT.json +++ b/docs/ims/umn/ALL_META.TXT.json @@ -13,7 +13,7 @@ "uri":"en-us_topic_0013901609.html", "product_code":"ims", "code":"2", - "des":"An image is a server or disk template that contains an operating system (OS) or service data and necessary software, such as database software. IMS provides public, priva", + "des":"An image is a cloud server or disk template that contains an operating system (OS), service data, or necessary software.Image Management Service (IMS) allows you to manag", "doc_type":"usermanual", "kw":"Supported OSs,OS compatibility,Supported images,Public image,Private image,Shared image,What Is Imag", "title":"What Is Image Management Service?", @@ -33,7 +33,7 @@ "uri":"en-us_topic_0030713142.html", "product_code":"ims", "code":"4", - "des":"This section describes the OSs supported by different types of ECSs.Table 1 lists the OSs supported by the following ECSs:General-purpose T6General computing S2, S3, S6, ", + "des":"This section describes the OSs supported by different types of ECSs.Table 1 lists the OSs supported by the following ECSs:General-purpose S2, S3Dedicated general-purpose ", "doc_type":"usermanual", "kw":"Supported OSs,OS compatibility,Supported images,OSs Supported by Different Types of ECSs,Supported O", "title":"OSs Supported by Different Types of ECSs", @@ -53,7 +53,7 @@ "uri":"en-us_topic_0170853315.html", "product_code":"ims", "code":"6", - "des":"The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?Table 1 lists the OSs that support the", + "des":"The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?.Table 1 lists the OSs that support th", "doc_type":"usermanual", "kw":"Supported OSs,OS compatibility,Supported images,OSs Supporting UEFI Boot Mode,Supported OSs,User Gui", "title":"OSs Supporting UEFI Boot Mode", @@ -305,7 +305,7 @@ "code":"31", "des":"Create a full-ECS image from a CSBS backup. This image can then be used to create ECSs.When creating a full-ECS image from a CSBS backup, ensure that the source ECS of th", "doc_type":"usermanual", - "kw":"CSBS backup,Creating a Full-ECS Image from a CSBS Backup,Creating a Private Image,User Guide", + "kw":"full-ECS image,CSBS backup,Creating a Full-ECS Image from a CSBS Backup,Creating a Private Image,Use", "title":"Creating a Full-ECS Image from a CSBS Backup", "githuburl":"" }, @@ -403,7 +403,7 @@ "uri":"en-us_topic_0030713200.html", "product_code":"ims", "code":"41", - "des":"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 pre-installed public applications. You need ", + "des":"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 t", "doc_type":"usermanual", "kw":"Creating an ECS from an Image,Managing Private Images,User Guide", "title":"Creating an ECS from an Image", @@ -520,10 +520,20 @@ "githuburl":"" }, { - "uri":"en-us_topic_0000001175697174.html", + "uri":"en-us_topic_0172473649.html", "product_code":"ims", "code":"53", - "des":"IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size.To import a data disk image file, follow the ins", + "des":"Replicate a private image that was shared with you. The image is displayed in the private image list. You can export, share, and replicate this image, or use it to create", + "doc_type":"usermanual", + "kw":"Replicating a Shared Image,Sharing Images,User Guide", + "title":"Replicating a Shared Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0000001175697174.html", + "product_code":"ims", + "code":"54", + "des":"IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size.Importing an imageFormatFile SizeReferenceVMDK, ", "doc_type":"usermanual", "kw":"Importing an Image,Managing Private Images,User Guide", "title":"Importing an Image", @@ -532,7 +542,7 @@ { "uri":"en-us_topic_0034011241.html", "product_code":"ims", - "code":"54", + "code":"55", "des":"You can export a private image to a standard OBS bucket and then download it to your local PC.You can reproduce cloud servers and their running environments in on-promise", "doc_type":"usermanual", "kw":"Exporting an Image,Managing Private Images,User Guide", @@ -542,7 +552,7 @@ { "uri":"en-us_topic_0130878748.html", "product_code":"ims", - "code":"55", + "code":"56", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Optimizing a Windows Private Image", @@ -552,8 +562,8 @@ { "uri":"en-us_topic_0047501112.html", "product_code":"ims", - "code":"56", - "des":"ECSs require Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools) for proper running. To ensure that ECSs support both Xen and KVM and to improve network", + "code":"57", + "des":"The proper running of ECSs depends on Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools). To ensure that ECSs support both Xen and KVM and to improve n", "doc_type":"usermanual", "kw":"Optimization Process,Optimizing a Windows Private Image,User Guide", "title":"Optimization Process", @@ -562,7 +572,7 @@ { "uri":"en-us_topic_0125075471.html", "product_code":"ims", - "code":"57", + "code":"58", "des":"Open the cmd window and run the following command to query the virtualization type of the ECS:systeminfoIf the values of System Manufacturer and BIOS Version are Xen, the", "doc_type":"usermanual", "kw":"virtualization type,Viewing the Virtualization Type of a Windows ECS,Optimizing a Windows Private Im", @@ -572,7 +582,7 @@ { "uri":"en-us_topic_0037352059.html", "product_code":"ims", - "code":"58", + "code":"59", "des":"Table 1 lists the PV driver software packages required for optimizing Windows private images.Table 2 lists the UVP VMTools software packages required for optimizing Windo", "doc_type":"usermanual", "kw":"PV driver,UVP VMTools,Obtaining Required Software Packages,Optimizing a Windows Private Image,User G", @@ -582,8 +592,8 @@ { "uri":"en-us_topic_0037352182.html", "product_code":"ims", - "code":"59", - "des":"When using an ECS or external image file to create a private image, ensure that the PV driver has been installed in the OS to enable Xen virtualization for subsequently c", + "code":"60", + "des":"This section only applies to Xen ECSs, which have been discontinued and no longer been available for new users. If you are a new user or you are an existing user that wil", "doc_type":"usermanual", "kw":"PV driver,Installing the PV Driver,Optimizing a Windows Private Image,User Guide", "title":"Installing the PV Driver", @@ -592,8 +602,8 @@ { "uri":"en-us_topic_0037352061.html", "product_code":"ims", - "code":"60", - "des":"Before using an ECS or external image file to create a private image, ensure that UVP VMTools has been installed in the OS to enable subsequently created ECSs to support ", + "code":"61", + "des":"This section only applies to KVM ECSs, which will replace Xen ECSs gradually. Before using an ECS or external image file to create a private image, ensure that UVP VMTool", "doc_type":"usermanual", "kw":"UVP VMTools,KVM virtualization,UVP VMTools,Installing UVP VMTools,Optimizing a Windows Private Image", "title":"Installing UVP VMTools", @@ -602,7 +612,7 @@ { "uri":"en-us_topic_0125075472.html", "product_code":"ims", - "code":"61", + "code":"62", "des":"After installing the PV driver and UVP VMTools, perform the following operations to clear system logs:For Windows Server 2008 and Windows Server 2012, right-click Compute", "doc_type":"usermanual", "kw":"Clearing System Logs,Optimizing a Windows Private Image,User Guide", @@ -612,7 +622,7 @@ { "uri":"en-us_topic_0130878749.html", "product_code":"ims", - "code":"62", + "code":"63", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Optimizing a Linux Private Image", @@ -622,8 +632,8 @@ { "uri":"en-us_topic_0047501133.html", "product_code":"ims", - "code":"63", - "des":"A Linux ECS can be switched from Xen to KVM if xen-pv and VirtIO drivers run on the ECS. Before changing a Xen-based ECS to a KVM-based ECS, ensure that the required driv", + "code":"64", + "des":"The virtualization of ECSs is gradually changing from Xen to KVM. Therefore, private images need to support both Xen and KVM. To ensure that ECSs created from a private i", "doc_type":"usermanual", "kw":"Optimization Process,Optimizing a Linux Private Image,User Guide", "title":"Optimization Process", @@ -632,8 +642,8 @@ { "uri":"en-us_topic_0037352185.html", "product_code":"ims", - "code":"64", - "des":"You can run the following command to query the virtualization type of an ECS:lscpuIf the value of Hypervisor vendor is Xen, the ECS uses Xen. If KVM is required, perform ", + "code":"65", + "des":"You can run the following command to query the virtualization type of an ECS:lscpuIf the value of Hypervisor vendor is Xen, the ECS uses Xen.If the value of Hypervisor ve", "doc_type":"usermanual", "kw":"Viewing the Virtualization Type of a Linux ECS,Optimizing a Linux Private Image,User Guide", "title":"Viewing the Virtualization Type of a Linux ECS", @@ -642,17 +652,17 @@ { "uri":"en-us_topic_0037352186.html", "product_code":"ims", - "code":"65", - "des":"When optimizing a Linux private image, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the ECS. To ensure", + "code":"66", + "des":"When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drive", "doc_type":"usermanual", - "kw":"uvp-monitor,Uninstalling the PV Driver from a Linux ECS,Optimizing a Linux Private Image,User Guide", - "title":"Uninstalling the PV Driver from a Linux ECS", + "kw":"uvp-monitor,Uninstalling PV Drivers from a Linux ECS,Optimizing a Linux Private Image,User Guide", + "title":"Uninstalling PV Drivers from a Linux ECS", "githuburl":"" }, { "uri":"en-us_topic_0086020895.html", "product_code":"ims", - "code":"66", + "code":"67", "des":"When optimizing a Linux private image, you need to change the disk identifier to UUID in the GRUB configuration file of the ECS.Modify the menu.lst or grub.cfg configurat", "doc_type":"usermanual", "kw":"Changing the Disk Identifier in the GRUB Configuration File to UUID,Optimizing a Linux Private Image", @@ -662,18 +672,28 @@ { "uri":"en-us_topic_0086024961.html", "product_code":"ims", - "code":"67", + "code":"68", "des":"When optimizing a Linux private image, you need to change the disk identifier to UUID in the fstab configuration file of the ECS.Take CentOS 7.0 as an example. Run blkid ", "doc_type":"usermanual", "kw":"UUIDs,Changing the Disk Identifier in the fstab File to UUID,Optimizing a Linux Private Image,User G", "title":"Changing the Disk Identifier in the fstab File to UUID", "githuburl":"" }, + { + "uri":"en-us_topic_0000001347866330.html", + "product_code":"ims", + "code":"69", + "des":"When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drive", + "doc_type":"usermanual", + "kw":"Install the Native Xen and KVM Drivers,Optimizing a Linux Private Image,User Guide", + "title":"Install the Native Xen and KVM Drivers", + "githuburl":"" + }, { "uri":"en-us_topic_0000001120952155.html", "product_code":"ims", - "code":"68", - "des":"When optimizing a Linux private image, you need to install native KVM drivers on the ECS.If you do not install KVM drivers, NICs of the ECS may not be detected and the EC", + "code":"70", + "des":"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 ", "doc_type":"usermanual", "kw":"native KVM drivers,Installing Native KVM Drivers,Optimizing a Linux Private Image,User Guide", "title":"Installing Native KVM Drivers", @@ -682,7 +702,7 @@ { "uri":"en-us_topic_0125076462.html", "product_code":"ims", - "code":"69", + "code":"71", "des":"Delete log files and historical records, and stop the ECS.Run the following commands to delete redundant key files:echo > /$path/$to/$root/.ssh/authorized_keysAn example ", "doc_type":"usermanual", "kw":"Delete log files,Clearing System Logs,Optimizing a Linux Private Image,User Guide", @@ -692,7 +712,7 @@ { "uri":"en-us_topic_0046588153.html", "product_code":"ims", - "code":"70", + "code":"72", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Encrypting Images", @@ -702,17 +722,17 @@ { "uri":"en-us_topic_0046588154.html", "product_code":"ims", - "code":"71", + "code":"73", "des":"IMS allows you to create encrypted images to ensure data security.To use the image encryption function, you must apply for KMS Administrator permissions.KMS must be enabl", "doc_type":"usermanual", - "kw":"image encryption,Encrypted images,Overview,Encrypting Images,User Guide", + "kw":"image encryption,Overview,Encrypting Images,User Guide", "title":"Overview", "githuburl":"" }, { "uri":"en-us_topic_0046588155.html", "product_code":"ims", - "code":"72", + "code":"74", "des":"You can create an encrypted image using an external image file or an encrypted ECS.Create an encrypted image using an external image file.When you register the external i", "doc_type":"usermanual", "kw":"encrypted image,Creating Encrypted Images,Encrypting Images,User Guide", @@ -722,7 +742,7 @@ { "uri":"en-us_topic_0049177180.html", "product_code":"ims", - "code":"73", + "code":"75", "des":"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 fu", "doc_type":"usermanual", "kw":"replicate an image,Replicating Images,Managing Private Images,User Guide", @@ -732,7 +752,7 @@ { "uri":"en-us_topic_0068002265.html", "product_code":"ims", - "code":"74", + "code":"76", "des":"You can use tags to classify images. You can add, modify, or delete image tags, or search for required images by tag in the image list.When adding predefined tags to an i", "doc_type":"usermanual", "kw":"image tags,Tagging an Image,Managing Private Images,User Guide", @@ -742,7 +762,7 @@ { "uri":"en-us_topic_0107462580.html", "product_code":"ims", - "code":"75", + "code":"77", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Auditing Key Operations", @@ -752,7 +772,7 @@ { "uri":"en-us_topic_0107462581.html", "product_code":"ims", - "code":"76", + "code":"78", "des":"Cloud Trace Service (CTS) is a log audit service provided by the public cloud and intended for cloud security. It allows you to collect, store, and query cloud resource o", "doc_type":"usermanual", "kw":"IMS Operations Recorded by CTS,Auditing Key Operations,User Guide", @@ -762,7 +782,7 @@ { "uri":"en-us_topic_0107462582.html", "product_code":"ims", - "code":"77", + "code":"79", "des":"Once CTS is enabled, it starts recording IMS operations. You can view operations recorded in the last seven days on the CTS management console.This section describes how ", "doc_type":"usermanual", "kw":"Viewing Traces,Auditing Key Operations,User Guide", @@ -772,7 +792,7 @@ { "uri":"en-us_topic_0117262219.html", "product_code":"ims", - "code":"78", + "code":"80", "des":"You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converte", "doc_type":"usermanual", "kw":"qemu-img,Converting the Image Format Using qemu-img,Managing Private Images,User Guide", @@ -782,7 +802,7 @@ { "uri":"en-us_topic_0171668652.html", "product_code":"ims", - "code":"79", + "code":"81", "des":"You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converte", "doc_type":"usermanual", "kw":"Converting the Image Format Using qemu-img-hw,Managing Private Images,User Guide", @@ -792,7 +812,7 @@ { "uri":"en-us_topic_0199394934.html", "product_code":"ims", - "code":"80", + "code":"82", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Windows Operations", @@ -802,7 +822,7 @@ { "uri":"en-us_topic_0030713152.html", "product_code":"ims", - "code":"81", + "code":"83", "des":"If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you ne", "doc_type":"usermanual", "kw":"NIC DHCP,Enable remote desktop connection,Setting the NIC to DHCP,Windows Operations,User Guide", @@ -812,7 +832,7 @@ { "uri":"en-us_topic_0030713155.html", "product_code":"ims", - "code":"82", + "code":"84", "des":"If you want to remotely access an ECS, enable remote desktop connection for the source ECS when creating a private image. This function must be enabled for GPU-accelerate", "doc_type":"usermanual", "kw":"Use ECS to create image,remote desktop connection,Enabling Remote Desktop Connection,Windows Operati", @@ -822,7 +842,7 @@ { "uri":"en-us_topic_0030730602.html", "product_code":"ims", - "code":"83", + "code":"85", "des":"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 pas", "doc_type":"usermanual", "kw":"Cloudbase-Init,Installing and Configuring Cloudbase-Init,Windows Operations,User Guide", @@ -832,7 +852,7 @@ { "uri":"en-us_topic_0093887081.html", "product_code":"ims", - "code":"84", + "code":"86", "des":"Running Sysprep ensures that an ECS has a unique SID after it is added to a domain.After installing Cloudbase-Init on an ECS, you need to decide whether the ECS needs to ", "doc_type":"usermanual", "kw":"Sysprep,Running Sysprep,Windows Operations,User Guide", @@ -842,7 +862,7 @@ { "uri":"en-us_topic_0081795392.html", "product_code":"ims", - "code":"85", + "code":"87", "des":"Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.If you want to use the created private image to create GPU-accel", "doc_type":"usermanual", "kw":"Installing Special Windows Drivers,Windows Operations,User Guide", @@ -852,7 +872,7 @@ { "uri":"en-us_topic_0199394935.html", "product_code":"ims", - "code":"86", + "code":"88", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Linux Operations", @@ -862,7 +882,7 @@ { "uri":"en-us_topic_0030713176.html", "product_code":"ims", - "code":"87", + "code":"89", "des":"If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you ne", "doc_type":"usermanual", "kw":"Setting the NIC to DHCP,Linux Operations,User Guide", @@ -872,7 +892,7 @@ { "uri":"en-us_topic_0069904570.html", "product_code":"ims", - "code":"88", + "code":"90", "des":"To prevent NIC name drift when you use a private image to create ECSs, you need to delete files from the network rule directory of the VM where the ECS or image file is l", "doc_type":"usermanual", "kw":"Delete network rule files,Disable NetworkManager,Deleting Files from the Network Rule Directory,Linu", @@ -882,7 +902,7 @@ { "uri":"en-us_topic_0030730603.html", "product_code":"ims", - "code":"89", + "code":"91", "des":"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 pas", "doc_type":"usermanual", "kw":"Check whether Cloud-Init is installed,Cloud-Init,Installing Cloud-Init,Linux Operations,User Guide", @@ -892,7 +912,7 @@ { "uri":"en-us_topic_0122876047.html", "product_code":"ims", - "code":"90", + "code":"92", "des":"You need to configure Cloud-Init after it is installed.Cloud-Init has been installed.An EIP has been bound to the ECS.You have logged in to the ECS.The IP address obtaini", "doc_type":"usermanual", "kw":"Cloud-Init,Configuring Cloud-Init,Linux Operations,User Guide", @@ -902,7 +922,7 @@ { "uri":"en-us_topic_0082002007.html", "product_code":"ims", - "code":"91", + "code":"93", "des":"Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.If you want to use the private image to create P1 ECSs, install ", "doc_type":"usermanual", "kw":"Installing Special Linux Drivers,Linux Operations,User Guide", @@ -912,7 +932,7 @@ { "uri":"en-us_topic_0030713179.html", "product_code":"ims", - "code":"92", + "code":"94", "des":"If multiple data disks are attached to the ECS used to create a private image, ECSs created from the image may be unavailable. Therefore, you need to detach all data disk", "doc_type":"usermanual", "kw":"Detaching Data Disks from an ECS,Linux Operations,User Guide", @@ -922,7 +942,7 @@ { "uri":"en-us_topic_0057450886.html", "product_code":"ims", - "code":"93", + "code":"95", "des":"If you want to use the ECS console logging function, you need to configure related parameters on the ECS.Currently, ECSs running the following OSs are supported: CentOS 6", "doc_type":"usermanual", "kw":"Configuring Console Logging,Linux Operations,User Guide", @@ -932,7 +952,7 @@ { "uri":"en-us_topic_0030713202.html", "product_code":"ims", - "code":"94", + "code":"96", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQs", @@ -942,7 +962,7 @@ { "uri":"en-us_topic_0138455714.html", "product_code":"ims", - "code":"95", + "code":"97", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Image Consulting", @@ -952,7 +972,7 @@ { "uri":"en-us_topic_0195253327.html", "product_code":"ims", - "code":"96", + "code":"98", "des":"When creating an ECS or BMS, you can select an image based on the following factors:Region and AZImage TypeOSAn image is a regional resource. You cannot use an image to c", "doc_type":"usermanual", "kw":"How Do I Select an Image?,Image Consulting,User Guide", @@ -962,7 +982,7 @@ { "uri":"en-us_topic_0153114116.html", "product_code":"ims", - "code":"97", + "code":"99", "des":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.If the existing resource quota ", "doc_type":"usermanual", "kw":"How Do I Increase the Image Quota?,Image Consulting,User Guide", @@ -972,7 +992,7 @@ { "uri":"en-us_topic_0173986473.html", "product_code":"ims", - "code":"98", + "code":"100", "des":"Yes.Other tenants can share a private image with you. You can use it after accepting it. For details about image sharing, see Sharing Specified Images.", "doc_type":"usermanual", "kw":"Can I Use Private Images of Other Tenants?,Image Consulting,User Guide", @@ -982,7 +1002,7 @@ { "uri":"en-us_topic_0193137621.html", "product_code":"ims", - "code":"99", + "code":"101", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Image Creation", @@ -992,7 +1012,7 @@ { "uri":"en-us_topic_0193146244.html", "product_code":"ims", - "code":"100", + "code":"102", "des":"Currently, you can create a maximum of 100 private images under an account in a region.No. You can create an image from a running ECS. However, if data is written to the ", "doc_type":"usermanual", "kw":"Image Creation FAQs,Image Creation,User Guide", @@ -1002,7 +1022,7 @@ { "uri":"en-us_topic_0106444267.html", "product_code":"ims", - "code":"101", + "code":"103", "des":"An ECS used to create a Windows full-ECS image cannot have a spanned volume. If you attempt to create an image from an ECS with a spanned volume, when the image is used t", "doc_type":"usermanual", "kw":"How Do I Create a Full-ECS Image Using an ECS That Has a Spanned Volume?,Image Creation,User Guide", @@ -1012,7 +1032,7 @@ { "uri":"en-us_topic_0030742197.html", "product_code":"ims", - "code":"102", + "code":"104", "des":"For a user that needs to be added to a domain and uses the domain account to log in to Windows, Sysprep is required before a private image is created. Otherwise, the imag", "doc_type":"usermanual", "kw":"Why Is Sysprep Required for Creating a Private Image from a Windows ECS?,Image Creation,User Guide", @@ -1022,7 +1042,7 @@ { "uri":"en-us_topic_0096558549.html", "product_code":"ims", - "code":"103", + "code":"105", "des":"When you create a ZVHD2 image using an API, the image is created in the ZVHD format.Check whether your token contains the op_gated_lld role (op_gated_lld is the OBT tag, ", "doc_type":"usermanual", "kw":"What Do I Do If I Cannot Create an Image in ZVHD2 Format Using an API?,Image Creation,User Guide", @@ -1032,7 +1052,7 @@ { "uri":"en-us_topic_0171668653.html", "product_code":"ims", - "code":"104", + "code":"106", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Image Sharing", @@ -1042,8 +1062,8 @@ { "uri":"en-us_topic_0183293890.html", "product_code":"ims", - "code":"105", - "des":"128There is no limit.No.No.Yes. After sharing an image with other tenants, you can still use the image to create an ECS and use the created ECS to create a private image.", + "code":"107", + "des":"A system disk image or data disk image can be shared with up to 256 tenants, but a full-ECS image can only be shared with up to 10 tenants.There is no limit.No.No.You can", "doc_type":"usermanual", "kw":"Image Sharing FAQs,Image Sharing,User Guide", "title":"Image Sharing FAQs", @@ -1052,7 +1072,7 @@ { "uri":"en-us_topic_0037352060.html", "product_code":"ims", - "code":"106", + "code":"108", "des":"Cause 1: Some images cannot be shared in any cases (the Share button in the Operation column for these images is unavailable), such as:Encrypted imagesFull-ECS images cre", "doc_type":"usermanual", "kw":"What Do I Do If I Cannot Share My Images?,Image Sharing,User Guide", @@ -1062,7 +1082,7 @@ { "uri":"en-us_topic_0133773782.html", "product_code":"ims", - "code":"107", + "code":"109", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"OS", @@ -1072,7 +1092,7 @@ { "uri":"en-us_topic_0113533721.html", "product_code":"ims", - "code":"108", + "code":"110", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"How Is BIOS Different from UEFI?,OS,User Guide", @@ -1082,7 +1102,7 @@ { "uri":"en-us_topic_0093842586.html", "product_code":"ims", - "code":"109", + "code":"111", "des":"The target ECS has had an EIP bound.You have obtained the driver installation package required for an OS. For details, see Table 1.The procedure for installing the NVIDIA", "doc_type":"usermanual", "kw":"How Do I Install the NVIDIA Driver on a P1 ECS?,OS,User Guide", @@ -1092,7 +1112,7 @@ { "uri":"en-us_topic_0106312064.html", "product_code":"ims", - "code":"110", + "code":"112", "des":"Press Win+R. In the displayed dialog box, enter regedit and press Enter to open the registry editor.Open the following registry key:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\", "doc_type":"usermanual", "kw":"How Do I Delete Redundant Network Connections from a Windows ECS?,OS,User Guide", @@ -1102,7 +1122,7 @@ { "uri":"en-us_topic_0117142739.html", "product_code":"ims", - "code":"111", + "code":"113", "des":"If an ECS starts slowly, you can change the default timeout duration to speed up the startup.Log in to the ECS.Run the following command to switch to user root:sudo susud", "doc_type":"usermanual", "kw":"What Do I Do If an ECS Starts Slowly?,OS,User Guide", @@ -1112,7 +1132,7 @@ { "uri":"en-us_topic_0081802526.html", "product_code":"ims", - "code":"112", + "code":"114", "des":"When the 20.4.1 driver package downloaded at Intel website https://downloadcenter.intel.com/search?keyword=Intel++Ethernet+Connections+CD was installed in a Windows 7 64b", "doc_type":"usermanual", "kw":"What Do I Do If a Windows 7 ECS Equipped with an Intel 82599 NIC Reports an Error in SR-IOV Scenario", @@ -1122,7 +1142,7 @@ { "uri":"en-us_topic_0030713195.html", "product_code":"ims", - "code":"113", + "code":"115", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Image Importing", @@ -1132,7 +1152,7 @@ { "uri":"en-us_topic_0030713217.html", "product_code":"ims", - "code":"114", + "code":"116", "des":"No. Currently, only the VMDK, VHD, RAW, QCOW2, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD formats are supported.Images of the -flat.vmdk format and image file packages contain", "doc_type":"usermanual", "kw":"Can I Use Images in Formats Other Than the Specified Ones?,Image Importing,User Guide", @@ -1142,7 +1162,7 @@ { "uri":"en-us_topic_0030713216.html", "product_code":"ims", - "code":"115", + "code":"117", "des":"Before using an ECS or external image file to create a private image, you need to pre-configure the ECS or the source VM of the image file. If you do not perform the pre-", "doc_type":"usermanual", "kw":"What Are the Impacts If I Do Not Pre-configure an ECS Used to Create a Private Image?,Image Importin", @@ -1152,7 +1172,7 @@ { "uri":"en-us_topic_0118990097.html", "product_code":"ims", - "code":"116", + "code":"118", "des":"Open Virtualization Appliance (OVA) is a single file (with the .ova extension) that archives all the files making up an Open Virtualization Format (OVF). OVF is a folder ", "doc_type":"usermanual", "kw":"How Do I Import an OVF or OVA File to the Cloud Platform?,Image Importing,User Guide", @@ -1162,7 +1182,7 @@ { "uri":"en-us_topic_0030713213.html", "product_code":"ims", - "code":"117", + "code":"119", "des":"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 regi", "doc_type":"usermanual", "kw":"What Do I Do If I Configured an Incorrect OS or System Disk Size During Private Image Registration U", @@ -1172,7 +1192,7 @@ { "uri":"en-us_topic_0058841396.html", "product_code":"ims", - "code":"118", + "code":"120", "des":"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 ", "doc_type":"usermanual", "kw":"What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Man", @@ -1182,7 +1202,7 @@ { "uri":"en-us_topic_0030713222.html", "product_code":"ims", - "code":"119", + "code":"121", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Image Exporting", @@ -1192,7 +1212,7 @@ { "uri":"en-us_topic_0249675952.html", "product_code":"ims", - "code":"120", + "code":"122", "des":"Yes. You can download private images in VMDK, VHD, QCOW2, or ZVHD format as instructed in Exporting an Image.", "doc_type":"usermanual", "kw":"Can I Download My Private Images to a Local PC?,Image Exporting,User Guide", @@ -1202,17 +1222,17 @@ { "uri":"en-us_topic_0030713153.html", "product_code":"ims", - "code":"121", + "code":"123", "des":"No. The system disk image of an ECS is a VM file that contains a system running environment and does not have an installation boot program. Therefore, it cannot be used o", "doc_type":"usermanual", - "kw":"Can I Use the System Disk Image of an ECS on a Physical Server After I Export It from the Cloud Plat", - "title":"Can I Use the System Disk Image of an ECS on a Physical Server After I Export It from the Cloud Platform?", + "kw":"Can I Use the System Disk Image of an ECS on a BMS After I Export It from the Cloud Platform?,Image ", + "title":"Can I Use the System Disk Image of an ECS on a BMS After I Export It from the Cloud Platform?", "githuburl":"" }, { "uri":"en-us_topic_0274352601.html", "product_code":"ims", - "code":"122", + "code":"124", "des":"After a private image is exported to an OBS bucket, the image size in the bucket is different from that displayed in IMS. For example, the size of a private image is 1.04", "doc_type":"usermanual", "kw":"Why Is the Image Size in an OBS Bucket Different from That Displayed in IMS?,Image Exporting,User Gu", @@ -1222,7 +1242,7 @@ { "uri":"en-us_topic_0030713186.html", "product_code":"ims", - "code":"123", + "code":"125", "des":"Currently, you cannot directly download a public image. You can use the public image to create an ECS, use the ECS to create a private image, export the private image to ", "doc_type":"usermanual", "kw":"Can I Download a Public Image to My Local PC?,Image Exporting,User Guide", @@ -1232,7 +1252,7 @@ { "uri":"en-us_topic_0199451475.html", "product_code":"ims", - "code":"124", + "code":"126", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"What Are the Differences Between Import/Export and Fast Import/Export?,Image Exporting,User Guide", @@ -1242,7 +1262,7 @@ { "uri":"en-us_topic_0199396601.html", "product_code":"ims", - "code":"125", + "code":"127", "des":"Some images cannot be exported. Therefore, the Export option is not provided for them in the Operation column. The following images cannot be exported:Public imagesFull-E", "doc_type":"usermanual", "kw":"What Do I Do If the Export Option Is Unavailable for My Image?,Image Exporting,User Guide", @@ -1252,7 +1272,7 @@ { "uri":"en-us_topic_0030713203.html", "product_code":"ims", - "code":"126", + "code":"128", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Image Optimization", @@ -1262,17 +1282,27 @@ { "uri":"en-us_topic_0030713214.html", "product_code":"ims", - "code":"127", + "code":"129", "des":"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", "doc_type":"usermanual", "kw":"Must I Install Guest OS Drivers on an ECS?,Image Optimization,User Guide", "title":"Must I Install Guest OS Drivers on an ECS?", "githuburl":"" }, + { + "uri":"en-us_topic_0165718046.html", + "product_code":"ims", + "code":"130", + "des":"VMTools is a VirtIO driver (para-virtualization driver) that provides high-performance disks and NICs for ECSs.A standard Windows OS does not have the VirtIO driver.Publi", + "doc_type":"usermanual", + "kw":"Why Do I Need to Install and Update VMTools for Windows?,Image Optimization,User Guide", + "title":"Why Do I Need to Install and Update VMTools for Windows?", + "githuburl":"" + }, { "uri":"en-us_topic_0032307025.html", "product_code":"ims", - "code":"128", + "code":"131", "des":"You are advised to enable automatic configuration when registering a private image using an image file. Then, the system will perform the following operations:Check wheth", "doc_type":"usermanual", "kw":"What Will the System Do to an Image File When I Use the File to Register a Private Image?,Image Opti", @@ -1282,7 +1312,7 @@ { "uri":"en-us_topic_0040740508.html", "product_code":"ims", - "code":"129", + "code":"132", "des":"When registering an external image file as a private image, you are advised to perform the preceding operations on the VM where the external image file is located.When re", "doc_type":"usermanual", "kw":"How Do I Configure an ECS, BMS, or Image File Before I Use It to Create an Image?,Image Optimization", @@ -1292,7 +1322,7 @@ { "uri":"en-us_topic_0030713185.html", "product_code":"ims", - "code":"130", + "code":"133", "des":"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 ", "doc_type":"usermanual", "kw":"What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image", @@ -1302,7 +1332,7 @@ { "uri":"en-us_topic_0030713211.html", "product_code":"ims", - "code":"131", + "code":"134", "des":"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 ", "doc_type":"usermanual", "kw":"What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?,", @@ -1312,7 +1342,7 @@ { "uri":"en-us_topic_0085214115.html", "product_code":"ims", - "code":"132", + "code":"135", "des":"With the increase of network I/O bandwidth, a single vCPU cannot meet the requirement of processing NIC interruptions. NIC multi-queue allows multiple vCPUs to process NI", "doc_type":"usermanual", "kw":"How Do I Enable NIC Multi-Queue for an Image?,Image Optimization,User Guide", @@ -1322,7 +1352,7 @@ { "uri":"en-us_topic_0187108863.html", "product_code":"ims", - "code":"133", + "code":"136", "des":"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 ", "doc_type":"usermanual", "kw":"How Do I Make a System Disk Image Support Fast ECS Creation?,Image Optimization,User Guide", @@ -1332,7 +1362,7 @@ { "uri":"en-us_topic_0030713215.html", "product_code":"ims", - "code":"134", + "code":"137", "des":"Possible causes:Your image file was exported from a VMware VM, and VMware Tools was not uninstalled or not completely uninstalled.You have downloaded the Guest OS driver ", "doc_type":"usermanual", "kw":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?,Image Optimization,U", @@ -1342,27 +1372,47 @@ { "uri":"en-us_topic_0086020894.html", "product_code":"ims", - "code":"135", - "des":"When optimizing a Linux private image, you need to install native Xen and KVM drivers for the image.If you do not install Xen drivers for the image, the network performan", + "code":"138", + "des":"When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drive", "doc_type":"usermanual", - "kw":"native Xen and KVM drivers,How Do I Install Native Xen and KVM Drivers?,Image Optimization,User Guid", - "title":"How Do I Install Native Xen and KVM Drivers?", + "kw":"How Do I Install the Native Xen and KVM Drivers?,Image Optimization,User Guide", + "title":"How Do I Install the Native Xen and KVM Drivers?", "githuburl":"" }, { "uri":"en-us_topic_0049196765.html", "product_code":"ims", - "code":"136", + "code":"139", "des":"If you want to store an unencrypted image in an encrypted way, you can select an encryption key when you replicate the image. Then, the system will generate an encrypted ", "doc_type":"usermanual", "kw":"Image Encryption,FAQs,User Guide", "title":"Image Encryption", "githuburl":"" }, + { + "uri":"en-us_topic_0205273057.html", + "product_code":"ims", + "code":"140", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Accounts and Permissions", + "title":"Accounts and Permissions", + "githuburl":"" + }, + { + "uri":"en-us_topic_0133773781.html", + "product_code":"ims", + "code":"141", + "des":"To share an encrypted image, you need to authorize the key used for encrypting the image. This section describes how to authorize a key.The key can only be a custom key. ", + "doc_type":"usermanual", + "kw":"How Do I Authorize a Key?,Accounts and Permissions,User Guide", + "title":"How Do I Authorize a Key?", + "githuburl":"" + }, { "uri":"en-us_topic_0138479468.html", "product_code":"ims", - "code":"137", + "code":"142", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Cloud-Init", @@ -1372,7 +1422,7 @@ { "uri":"en-us_topic_0148873774.html", "product_code":"ims", - "code":"138", + "code":"143", "des":"Cloud-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloud-Init, you can use user data injection to inject customize", "doc_type":"usermanual", "kw":"What Can I Do with a Cloud-Init ECS?,Cloud-Init,User Guide", @@ -1382,7 +1432,7 @@ { "uri":"en-us_topic_0113992021.html", "product_code":"ims", - "code":"139", + "code":"144", "des":"A major cause is that the version of Cloud-Init is incompatible with that of NetworkManager. In Debian 9.0 and later versions, NetworkManager is incompatible with Cloud-I", "doc_type":"usermanual", "kw":"What Do I Do If Injecting the Key or Password Using Cloud-Init Failed After NetworkManager Is Instal", @@ -1392,7 +1442,7 @@ { "uri":"en-us_topic_0078454810.html", "product_code":"ims", - "code":"140", + "code":"145", "des":"growpart for SUSE and openSUSE is an independent toolkit that does not start with cloud-*. Perform operations in this section to install growpart.Run the following comman", "doc_type":"usermanual", "kw":"How Do I Install growpart for SUSE 11 SP4?,Cloud-Init,User Guide", @@ -1402,7 +1452,7 @@ { "uri":"en-us_topic_0076880304.html", "product_code":"ims", - "code":"141", + "code":"146", "des":"An image whose root partition file system is xfs cannot automatically expand its partitions.An image that has the LVM partition cannot automatically expand its partitions", "doc_type":"usermanual", "kw":"How Do I Configure a Linux Private Image to Make It Automatically Expand Its Root Partition?,Cloud-I", @@ -1412,7 +1462,7 @@ { "uri":"en-us_topic_0030713220.html", "product_code":"ims", - "code":"142", + "code":"147", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"ECS Creation", @@ -1422,7 +1472,7 @@ { "uri":"en-us_topic_0030713209.html", "product_code":"ims", - "code":"143", + "code":"148", "des":"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", "doc_type":"usermanual", "kw":"Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to", @@ -1432,7 +1482,7 @@ { "uri":"en-us_topic_0030713221.html", "product_code":"ims", - "code":"144", + "code":"149", "des":"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 specif", "doc_type":"usermanual", "kw":"Can I Specify the System Disk Size When I Create an ECS Using an Image?,ECS Creation,User Guide", @@ -1442,7 +1492,7 @@ { "uri":"en-us_topic_0034220644.html", "product_code":"ims", - "code":"145", + "code":"150", "des":"This may be caused by a disk partition ID change after the cross-platform image import. As a result, no partition can be found based on the original disk partition ID in ", "doc_type":"usermanual", "kw":"What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private ", @@ -1452,7 +1502,7 @@ { "uri":"en-us_topic_0030713219.html", "product_code":"ims", - "code":"146", + "code":"151", "des":"Generally, this is because the xen-blkfront.ko module is not loaded during the startup. You need to modify OS kernel startup parameters. Figure 1 shows the startup screen", "doc_type":"usermanual", "kw":"What Do I Do If the Disks of an ECS Created from a CentOS Image Cannot Be Found?,ECS Creation,User G", @@ -1462,7 +1512,7 @@ { "uri":"en-us_topic_0113403127.html", "product_code":"ims", - "code":"147", + "code":"152", "des":"This issue is probably caused by the failure of offline VirtIO driver injection.When you inject the VirtIO driver for a Windows ECS offline, there are some restrictions:I", "doc_type":"usermanual", "kw":"What Do I Do If an ECS Created from a Windows Image Failed to Start When I Have Enabled Automatic Co", @@ -1472,7 +1522,7 @@ { "uri":"en-us_topic_0161870891.html", "product_code":"ims", - "code":"148", + "code":"153", "des":"An ECS created from a private image using the UEFI boot mode cannot start.The image OS uses the UEFI boot mode, but the uefi attribute is not added to the image.Delete th", "doc_type":"usermanual", "kw":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mo", @@ -1482,7 +1532,7 @@ { "uri":"en-us_topic_0041178787.html", "product_code":"ims", - "code":"149", + "code":"154", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", @@ -1492,7 +1542,7 @@ { "uri":"en-us_topic_0047898081.html", "product_code":"ims", - "code":"150", + "code":"155", "des":"For details about the terms involved in this document, see Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", diff --git a/docs/ims/umn/CLASS.TXT.json b/docs/ims/umn/CLASS.TXT.json index 67d3e5d5f..3c51ec54c 100644 --- a/docs/ims/umn/CLASS.TXT.json +++ b/docs/ims/umn/CLASS.TXT.json @@ -9,7 +9,7 @@ "code":"1" }, { - "desc":"An image is a server or disk template that contains an operating system (OS) or service data and necessary software, such as database software. IMS provides public, priva", + "desc":"An image is a cloud server or disk template that contains an operating system (OS), service data, or necessary software.Image Management Service (IMS) allows you to manag", "product_code":"ims", "title":"What Is Image Management Service?", "uri":"en-us_topic_0013901609.html", @@ -27,7 +27,7 @@ "code":"3" }, { - "desc":"This section describes the OSs supported by different types of ECSs.Table 1 lists the OSs supported by the following ECSs:General-purpose T6General computing S2, S3, S6, ", + "desc":"This section describes the OSs supported by different types of ECSs.Table 1 lists the OSs supported by the following ECSs:General-purpose S2, S3Dedicated general-purpose ", "product_code":"ims", "title":"OSs Supported by Different Types of ECSs", "uri":"en-us_topic_0030713142.html", @@ -45,7 +45,7 @@ "code":"5" }, { - "desc":"The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?Table 1 lists the OSs that support the", + "desc":"The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?.Table 1 lists the OSs that support th", "product_code":"ims", "title":"OSs Supporting UEFI Boot Mode", "uri":"en-us_topic_0170853315.html", @@ -360,7 +360,7 @@ "code":"40" }, { - "desc":"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 pre-installed public applications. You need ", + "desc":"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 t", "product_code":"ims", "title":"Creating an ECS from an Image", "uri":"en-us_topic_0030713200.html", @@ -468,13 +468,22 @@ "code":"52" }, { - "desc":"IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size.To import a data disk image file, follow the ins", + "desc":"Replicate a private image that was shared with you. The image is displayed in the private image list. You can export, share, and replicate this image, or use it to create", + "product_code":"ims", + "title":"Replicating a Shared Image", + "uri":"en-us_topic_0172473649.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"53" + }, + { + "desc":"IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size.Importing an imageFormatFile SizeReferenceVMDK, ", "product_code":"ims", "title":"Importing an Image", "uri":"en-us_topic_0000001175697174.html", "doc_type":"usermanual", "p_code":"37", - "code":"53" + "code":"54" }, { "desc":"You can export a private image to a standard OBS bucket and then download it to your local PC.You can reproduce cloud servers and their running environments in on-promise", @@ -483,7 +492,7 @@ "uri":"en-us_topic_0034011241.html", "doc_type":"usermanual", "p_code":"37", - "code":"54" + "code":"55" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -492,16 +501,16 @@ "uri":"en-us_topic_0130878748.html", "doc_type":"usermanual", "p_code":"37", - "code":"55" + "code":"56" }, { - "desc":"ECSs require Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools) for proper running. To ensure that ECSs support both Xen and KVM and to improve network", + "desc":"The proper running of ECSs depends on Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools). To ensure that ECSs support both Xen and KVM and to improve n", "product_code":"ims", "title":"Optimization Process", "uri":"en-us_topic_0047501112.html", "doc_type":"usermanual", - "p_code":"55", - "code":"56" + "p_code":"56", + "code":"57" }, { "desc":"Open the cmd window and run the following command to query the virtualization type of the ECS:systeminfoIf the values of System Manufacturer and BIOS Version are Xen, the", @@ -509,8 +518,8 @@ "title":"Viewing the Virtualization Type of a Windows ECS", "uri":"en-us_topic_0125075471.html", "doc_type":"usermanual", - "p_code":"55", - "code":"57" + "p_code":"56", + "code":"58" }, { "desc":"Table 1 lists the PV driver software packages required for optimizing Windows private images.Table 2 lists the UVP VMTools software packages required for optimizing Windo", @@ -518,26 +527,26 @@ "title":"Obtaining Required Software Packages", "uri":"en-us_topic_0037352059.html", "doc_type":"usermanual", - "p_code":"55", - "code":"58" + "p_code":"56", + "code":"59" }, { - "desc":"When using an ECS or external image file to create a private image, ensure that the PV driver has been installed in the OS to enable Xen virtualization for subsequently c", + "desc":"This section only applies to Xen ECSs, which have been discontinued and no longer been available for new users. If you are a new user or you are an existing user that wil", "product_code":"ims", "title":"Installing the PV Driver", "uri":"en-us_topic_0037352182.html", "doc_type":"usermanual", - "p_code":"55", - "code":"59" + "p_code":"56", + "code":"60" }, { - "desc":"Before using an ECS or external image file to create a private image, ensure that UVP VMTools has been installed in the OS to enable subsequently created ECSs to support ", + "desc":"This section only applies to KVM ECSs, which will replace Xen ECSs gradually. Before using an ECS or external image file to create a private image, ensure that UVP VMTool", "product_code":"ims", "title":"Installing UVP VMTools", "uri":"en-us_topic_0037352061.html", "doc_type":"usermanual", - "p_code":"55", - "code":"60" + "p_code":"56", + "code":"61" }, { "desc":"After installing the PV driver and UVP VMTools, perform the following operations to clear system logs:For Windows Server 2008 and Windows Server 2012, right-click Compute", @@ -545,8 +554,8 @@ "title":"Clearing System Logs", "uri":"en-us_topic_0125075472.html", "doc_type":"usermanual", - "p_code":"55", - "code":"61" + "p_code":"56", + "code":"62" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -555,34 +564,34 @@ "uri":"en-us_topic_0130878749.html", "doc_type":"usermanual", "p_code":"37", - "code":"62" + "code":"63" }, { - "desc":"A Linux ECS can be switched from Xen to KVM if xen-pv and VirtIO drivers run on the ECS. Before changing a Xen-based ECS to a KVM-based ECS, ensure that the required driv", + "desc":"The virtualization of ECSs is gradually changing from Xen to KVM. Therefore, private images need to support both Xen and KVM. To ensure that ECSs created from a private i", "product_code":"ims", "title":"Optimization Process", "uri":"en-us_topic_0047501133.html", "doc_type":"usermanual", - "p_code":"62", - "code":"63" + "p_code":"63", + "code":"64" }, { - "desc":"You can run the following command to query the virtualization type of an ECS:lscpuIf the value of Hypervisor vendor is Xen, the ECS uses Xen. If KVM is required, perform ", + "desc":"You can run the following command to query the virtualization type of an ECS:lscpuIf the value of Hypervisor vendor is Xen, the ECS uses Xen.If the value of Hypervisor ve", "product_code":"ims", "title":"Viewing the Virtualization Type of a Linux ECS", "uri":"en-us_topic_0037352185.html", "doc_type":"usermanual", - "p_code":"62", - "code":"64" + "p_code":"63", + "code":"65" }, { - "desc":"When optimizing a Linux private image, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the ECS. To ensure", + "desc":"When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drive", "product_code":"ims", - "title":"Uninstalling the PV Driver from a Linux ECS", + "title":"Uninstalling PV Drivers from a Linux ECS", "uri":"en-us_topic_0037352186.html", "doc_type":"usermanual", - "p_code":"62", - "code":"65" + "p_code":"63", + "code":"66" }, { "desc":"When optimizing a Linux private image, you need to change the disk identifier to UUID in the GRUB configuration file of the ECS.Modify the menu.lst or grub.cfg configurat", @@ -590,8 +599,8 @@ "title":"Changing the Disk Identifier in the GRUB Configuration File to UUID", "uri":"en-us_topic_0086020895.html", "doc_type":"usermanual", - "p_code":"62", - "code":"66" + "p_code":"63", + "code":"67" }, { "desc":"When optimizing a Linux private image, you need to change the disk identifier to UUID in the fstab configuration file of the ECS.Take CentOS 7.0 as an example. Run blkid ", @@ -599,17 +608,26 @@ "title":"Changing the Disk Identifier in the fstab File to UUID", "uri":"en-us_topic_0086024961.html", "doc_type":"usermanual", - "p_code":"62", - "code":"67" + "p_code":"63", + "code":"68" }, { - "desc":"When optimizing a Linux private image, you need to install native KVM drivers on the ECS.If you do not install KVM drivers, NICs of the ECS may not be detected and the EC", + "desc":"When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drive", + "product_code":"ims", + "title":"Install the Native Xen and KVM Drivers", + "uri":"en-us_topic_0000001347866330.html", + "doc_type":"usermanual", + "p_code":"63", + "code":"69" + }, + { + "desc":"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 ", "product_code":"ims", "title":"Installing Native KVM Drivers", "uri":"en-us_topic_0000001120952155.html", "doc_type":"usermanual", - "p_code":"62", - "code":"68" + "p_code":"63", + "code":"70" }, { "desc":"Delete log files and historical records, and stop the ECS.Run the following commands to delete redundant key files:echo > /$path/$to/$root/.ssh/authorized_keysAn example ", @@ -617,8 +635,8 @@ "title":"Clearing System Logs", "uri":"en-us_topic_0125076462.html", "doc_type":"usermanual", - "p_code":"62", - "code":"69" + "p_code":"63", + "code":"71" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -627,7 +645,7 @@ "uri":"en-us_topic_0046588153.html", "doc_type":"usermanual", "p_code":"37", - "code":"70" + "code":"72" }, { "desc":"IMS allows you to create encrypted images to ensure data security.To use the image encryption function, you must apply for KMS Administrator permissions.KMS must be enabl", @@ -635,8 +653,8 @@ "title":"Overview", "uri":"en-us_topic_0046588154.html", "doc_type":"usermanual", - "p_code":"70", - "code":"71" + "p_code":"72", + "code":"73" }, { "desc":"You can create an encrypted image using an external image file or an encrypted ECS.Create an encrypted image using an external image file.When you register the external i", @@ -644,8 +662,8 @@ "title":"Creating Encrypted Images", "uri":"en-us_topic_0046588155.html", "doc_type":"usermanual", - "p_code":"70", - "code":"72" + "p_code":"72", + "code":"74" }, { "desc":"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 fu", @@ -654,7 +672,7 @@ "uri":"en-us_topic_0049177180.html", "doc_type":"usermanual", "p_code":"37", - "code":"73" + "code":"75" }, { "desc":"You can use tags to classify images. You can add, modify, or delete image tags, or search for required images by tag in the image list.When adding predefined tags to an i", @@ -663,7 +681,7 @@ "uri":"en-us_topic_0068002265.html", "doc_type":"usermanual", "p_code":"37", - "code":"74" + "code":"76" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -672,7 +690,7 @@ "uri":"en-us_topic_0107462580.html", "doc_type":"usermanual", "p_code":"37", - "code":"75" + "code":"77" }, { "desc":"Cloud Trace Service (CTS) is a log audit service provided by the public cloud and intended for cloud security. It allows you to collect, store, and query cloud resource o", @@ -680,8 +698,8 @@ "title":"IMS Operations Recorded by CTS", "uri":"en-us_topic_0107462581.html", "doc_type":"usermanual", - "p_code":"75", - "code":"76" + "p_code":"77", + "code":"78" }, { "desc":"Once CTS is enabled, it starts recording IMS operations. You can view operations recorded in the last seven days on the CTS management console.This section describes how ", @@ -689,8 +707,8 @@ "title":"Viewing Traces", "uri":"en-us_topic_0107462582.html", "doc_type":"usermanual", - "p_code":"75", - "code":"77" + "p_code":"77", + "code":"79" }, { "desc":"You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converte", @@ -699,7 +717,7 @@ "uri":"en-us_topic_0117262219.html", "doc_type":"usermanual", "p_code":"37", - "code":"78" + "code":"80" }, { "desc":"You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converte", @@ -708,7 +726,7 @@ "uri":"en-us_topic_0171668652.html", "doc_type":"usermanual", "p_code":"37", - "code":"79" + "code":"81" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -717,7 +735,7 @@ "uri":"en-us_topic_0199394934.html", "doc_type":"usermanual", "p_code":"", - "code":"80" + "code":"82" }, { "desc":"If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you ne", @@ -725,8 +743,8 @@ "title":"Setting the NIC to DHCP", "uri":"en-us_topic_0030713152.html", "doc_type":"usermanual", - "p_code":"80", - "code":"81" + "p_code":"82", + "code":"83" }, { "desc":"If you want to remotely access an ECS, enable remote desktop connection for the source ECS when creating a private image. This function must be enabled for GPU-accelerate", @@ -734,8 +752,8 @@ "title":"Enabling Remote Desktop Connection", "uri":"en-us_topic_0030713155.html", "doc_type":"usermanual", - "p_code":"80", - "code":"82" + "p_code":"82", + "code":"84" }, { "desc":"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 pas", @@ -743,8 +761,8 @@ "title":"Installing and Configuring Cloudbase-Init", "uri":"en-us_topic_0030730602.html", "doc_type":"usermanual", - "p_code":"80", - "code":"83" + "p_code":"82", + "code":"85" }, { "desc":"Running Sysprep ensures that an ECS has a unique SID after it is added to a domain.After installing Cloudbase-Init on an ECS, you need to decide whether the ECS needs to ", @@ -752,8 +770,8 @@ "title":"Running Sysprep", "uri":"en-us_topic_0093887081.html", "doc_type":"usermanual", - "p_code":"80", - "code":"84" + "p_code":"82", + "code":"86" }, { "desc":"Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.If you want to use the created private image to create GPU-accel", @@ -761,8 +779,8 @@ "title":"Installing Special Windows Drivers", "uri":"en-us_topic_0081795392.html", "doc_type":"usermanual", - "p_code":"80", - "code":"85" + "p_code":"82", + "code":"87" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -771,7 +789,7 @@ "uri":"en-us_topic_0199394935.html", "doc_type":"usermanual", "p_code":"", - "code":"86" + "code":"88" }, { "desc":"If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you ne", @@ -779,8 +797,8 @@ "title":"Setting the NIC to DHCP", "uri":"en-us_topic_0030713176.html", "doc_type":"usermanual", - "p_code":"86", - "code":"87" + "p_code":"88", + "code":"89" }, { "desc":"To prevent NIC name drift when you use a private image to create ECSs, you need to delete files from the network rule directory of the VM where the ECS or image file is l", @@ -788,8 +806,8 @@ "title":"Deleting Files from the Network Rule Directory", "uri":"en-us_topic_0069904570.html", "doc_type":"usermanual", - "p_code":"86", - "code":"88" + "p_code":"88", + "code":"90" }, { "desc":"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 pas", @@ -797,8 +815,8 @@ "title":"Installing Cloud-Init", "uri":"en-us_topic_0030730603.html", "doc_type":"usermanual", - "p_code":"86", - "code":"89" + "p_code":"88", + "code":"91" }, { "desc":"You need to configure Cloud-Init after it is installed.Cloud-Init has been installed.An EIP has been bound to the ECS.You have logged in to the ECS.The IP address obtaini", @@ -806,8 +824,8 @@ "title":"Configuring Cloud-Init", "uri":"en-us_topic_0122876047.html", "doc_type":"usermanual", - "p_code":"86", - "code":"90" + "p_code":"88", + "code":"92" }, { "desc":"Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.If you want to use the private image to create P1 ECSs, install ", @@ -815,8 +833,8 @@ "title":"Installing Special Linux Drivers", "uri":"en-us_topic_0082002007.html", "doc_type":"usermanual", - "p_code":"86", - "code":"91" + "p_code":"88", + "code":"93" }, { "desc":"If multiple data disks are attached to the ECS used to create a private image, ECSs created from the image may be unavailable. Therefore, you need to detach all data disk", @@ -824,8 +842,8 @@ "title":"Detaching Data Disks from an ECS", "uri":"en-us_topic_0030713179.html", "doc_type":"usermanual", - "p_code":"86", - "code":"92" + "p_code":"88", + "code":"94" }, { "desc":"If you want to use the ECS console logging function, you need to configure related parameters on the ECS.Currently, ECSs running the following OSs are supported: CentOS 6", @@ -833,8 +851,8 @@ "title":"Configuring Console Logging", "uri":"en-us_topic_0057450886.html", "doc_type":"usermanual", - "p_code":"86", - "code":"93" + "p_code":"88", + "code":"95" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -843,7 +861,7 @@ "uri":"en-us_topic_0030713202.html", "doc_type":"usermanual", "p_code":"", - "code":"94" + "code":"96" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -851,8 +869,8 @@ "title":"Image Consulting", "uri":"en-us_topic_0138455714.html", "doc_type":"usermanual", - "p_code":"94", - "code":"95" + "p_code":"96", + "code":"97" }, { "desc":"When creating an ECS or BMS, you can select an image based on the following factors:Region and AZImage TypeOSAn image is a regional resource. You cannot use an image to c", @@ -860,8 +878,8 @@ "title":"How Do I Select an Image?", "uri":"en-us_topic_0195253327.html", "doc_type":"usermanual", - "p_code":"95", - "code":"96" + "p_code":"97", + "code":"98" }, { "desc":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.If the existing resource quota ", @@ -869,8 +887,8 @@ "title":"How Do I Increase the Image Quota?", "uri":"en-us_topic_0153114116.html", "doc_type":"usermanual", - "p_code":"95", - "code":"97" + "p_code":"97", + "code":"99" }, { "desc":"Yes.Other tenants can share a private image with you. You can use it after accepting it. For details about image sharing, see Sharing Specified Images.", @@ -878,8 +896,8 @@ "title":"Can I Use Private Images of Other Tenants?", "uri":"en-us_topic_0173986473.html", "doc_type":"usermanual", - "p_code":"95", - "code":"98" + "p_code":"97", + "code":"100" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -887,8 +905,8 @@ "title":"Image Creation", "uri":"en-us_topic_0193137621.html", "doc_type":"usermanual", - "p_code":"94", - "code":"99" + "p_code":"96", + "code":"101" }, { "desc":"Currently, you can create a maximum of 100 private images under an account in a region.No. You can create an image from a running ECS. However, if data is written to the ", @@ -896,8 +914,8 @@ "title":"Image Creation FAQs", "uri":"en-us_topic_0193146244.html", "doc_type":"usermanual", - "p_code":"99", - "code":"100" + "p_code":"101", + "code":"102" }, { "desc":"An ECS used to create a Windows full-ECS image cannot have a spanned volume. If you attempt to create an image from an ECS with a spanned volume, when the image is used t", @@ -905,8 +923,8 @@ "title":"How Do I Create a Full-ECS Image Using an ECS That Has a Spanned Volume?", "uri":"en-us_topic_0106444267.html", "doc_type":"usermanual", - "p_code":"99", - "code":"101" + "p_code":"101", + "code":"103" }, { "desc":"For a user that needs to be added to a domain and uses the domain account to log in to Windows, Sysprep is required before a private image is created. Otherwise, the imag", @@ -914,8 +932,8 @@ "title":"Why Is Sysprep Required for Creating a Private Image from a Windows ECS?", "uri":"en-us_topic_0030742197.html", "doc_type":"usermanual", - "p_code":"99", - "code":"102" + "p_code":"101", + "code":"104" }, { "desc":"When you create a ZVHD2 image using an API, the image is created in the ZVHD format.Check whether your token contains the op_gated_lld role (op_gated_lld is the OBT tag, ", @@ -923,8 +941,8 @@ "title":"What Do I Do If I Cannot Create an Image in ZVHD2 Format Using an API?", "uri":"en-us_topic_0096558549.html", "doc_type":"usermanual", - "p_code":"99", - "code":"103" + "p_code":"101", + "code":"105" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -932,17 +950,17 @@ "title":"Image Sharing", "uri":"en-us_topic_0171668653.html", "doc_type":"usermanual", - "p_code":"94", - "code":"104" + "p_code":"96", + "code":"106" }, { - "desc":"128There is no limit.No.No.Yes. After sharing an image with other tenants, you can still use the image to create an ECS and use the created ECS to create a private image.", + "desc":"A system disk image or data disk image can be shared with up to 256 tenants, but a full-ECS image can only be shared with up to 10 tenants.There is no limit.No.No.You can", "product_code":"ims", "title":"Image Sharing FAQs", "uri":"en-us_topic_0183293890.html", "doc_type":"usermanual", - "p_code":"104", - "code":"105" + "p_code":"106", + "code":"107" }, { "desc":"Cause 1: Some images cannot be shared in any cases (the Share button in the Operation column for these images is unavailable), such as:Encrypted imagesFull-ECS images cre", @@ -950,8 +968,8 @@ "title":"What Do I Do If I Cannot Share My Images?", "uri":"en-us_topic_0037352060.html", "doc_type":"usermanual", - "p_code":"104", - "code":"106" + "p_code":"106", + "code":"108" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -959,8 +977,8 @@ "title":"OS", "uri":"en-us_topic_0133773782.html", "doc_type":"usermanual", - "p_code":"94", - "code":"107" + "p_code":"96", + "code":"109" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -968,8 +986,8 @@ "title":"How Is BIOS Different from UEFI?", "uri":"en-us_topic_0113533721.html", "doc_type":"usermanual", - "p_code":"107", - "code":"108" + "p_code":"109", + "code":"110" }, { "desc":"The target ECS has had an EIP bound.You have obtained the driver installation package required for an OS. For details, see Table 1.The procedure for installing the NVIDIA", @@ -977,8 +995,8 @@ "title":"How Do I Install the NVIDIA Driver on a P1 ECS?", "uri":"en-us_topic_0093842586.html", "doc_type":"usermanual", - "p_code":"107", - "code":"109" + "p_code":"109", + "code":"111" }, { "desc":"Press Win+R. In the displayed dialog box, enter regedit and press Enter to open the registry editor.Open the following registry key:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\", @@ -986,8 +1004,8 @@ "title":"How Do I Delete Redundant Network Connections from a Windows ECS?", "uri":"en-us_topic_0106312064.html", "doc_type":"usermanual", - "p_code":"107", - "code":"110" + "p_code":"109", + "code":"112" }, { "desc":"If an ECS starts slowly, you can change the default timeout duration to speed up the startup.Log in to the ECS.Run the following command to switch to user root:sudo susud", @@ -995,8 +1013,8 @@ "title":"What Do I Do If an ECS Starts Slowly?", "uri":"en-us_topic_0117142739.html", "doc_type":"usermanual", - "p_code":"107", - "code":"111" + "p_code":"109", + "code":"113" }, { "desc":"When the 20.4.1 driver package downloaded at Intel website https://downloadcenter.intel.com/search?keyword=Intel++Ethernet+Connections+CD was installed in a Windows 7 64b", @@ -1004,8 +1022,8 @@ "title":"What Do I Do If a Windows 7 ECS Equipped with an Intel 82599 NIC Reports an Error in SR-IOV Scenarios?", "uri":"en-us_topic_0081802526.html", "doc_type":"usermanual", - "p_code":"107", - "code":"112" + "p_code":"109", + "code":"114" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1013,8 +1031,8 @@ "title":"Image Importing", "uri":"en-us_topic_0030713195.html", "doc_type":"usermanual", - "p_code":"94", - "code":"113" + "p_code":"96", + "code":"115" }, { "desc":"No. Currently, only the VMDK, VHD, RAW, QCOW2, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD formats are supported.Images of the -flat.vmdk format and image file packages contain", @@ -1022,8 +1040,8 @@ "title":"Can I Use Images in Formats Other Than the Specified Ones?", "uri":"en-us_topic_0030713217.html", "doc_type":"usermanual", - "p_code":"113", - "code":"114" + "p_code":"115", + "code":"116" }, { "desc":"Before using an ECS or external image file to create a private image, you need to pre-configure the ECS or the source VM of the image file. If you do not perform the pre-", @@ -1031,8 +1049,8 @@ "title":"What Are the Impacts If I Do Not Pre-configure an ECS Used to Create a Private Image?", "uri":"en-us_topic_0030713216.html", "doc_type":"usermanual", - "p_code":"113", - "code":"115" + "p_code":"115", + "code":"117" }, { "desc":"Open Virtualization Appliance (OVA) is a single file (with the .ova extension) that archives all the files making up an Open Virtualization Format (OVF). OVF is a folder ", @@ -1040,8 +1058,8 @@ "title":"How Do I Import an OVF or OVA File to the Cloud Platform?", "uri":"en-us_topic_0118990097.html", "doc_type":"usermanual", - "p_code":"113", - "code":"116" + "p_code":"115", + "code":"118" }, { "desc":"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 regi", @@ -1049,8 +1067,8 @@ "title":"What Do I Do If I Configured an Incorrect OS or System Disk Size During Private Image Registration Using an Image File?", "uri":"en-us_topic_0030713213.html", "doc_type":"usermanual", - "p_code":"113", - "code":"117" + "p_code":"115", + "code":"119" }, { "desc":"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 ", @@ -1058,8 +1076,8 @@ "title":"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?", "uri":"en-us_topic_0058841396.html", "doc_type":"usermanual", - "p_code":"113", - "code":"118" + "p_code":"115", + "code":"120" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1067,8 +1085,8 @@ "title":"Image Exporting", "uri":"en-us_topic_0030713222.html", "doc_type":"usermanual", - "p_code":"94", - "code":"119" + "p_code":"96", + "code":"121" }, { "desc":"Yes. You can download private images in VMDK, VHD, QCOW2, or ZVHD format as instructed in Exporting an Image.", @@ -1076,17 +1094,17 @@ "title":"Can I Download My Private Images to a Local PC?", "uri":"en-us_topic_0249675952.html", "doc_type":"usermanual", - "p_code":"119", - "code":"120" + "p_code":"121", + "code":"122" }, { "desc":"No. The system disk image of an ECS is a VM file that contains a system running environment and does not have an installation boot program. Therefore, it cannot be used o", "product_code":"ims", - "title":"Can I Use the System Disk Image of an ECS on a Physical Server After I Export It from the Cloud Platform?", + "title":"Can I Use the System Disk Image of an ECS on a BMS After I Export It from the Cloud Platform?", "uri":"en-us_topic_0030713153.html", "doc_type":"usermanual", - "p_code":"119", - "code":"121" + "p_code":"121", + "code":"123" }, { "desc":"After a private image is exported to an OBS bucket, the image size in the bucket is different from that displayed in IMS. For example, the size of a private image is 1.04", @@ -1094,8 +1112,8 @@ "title":"Why Is the Image Size in an OBS Bucket Different from That Displayed in IMS?", "uri":"en-us_topic_0274352601.html", "doc_type":"usermanual", - "p_code":"119", - "code":"122" + "p_code":"121", + "code":"124" }, { "desc":"Currently, you cannot directly download a public image. You can use the public image to create an ECS, use the ECS to create a private image, export the private image to ", @@ -1103,8 +1121,8 @@ "title":"Can I Download a Public Image to My Local PC?", "uri":"en-us_topic_0030713186.html", "doc_type":"usermanual", - "p_code":"119", - "code":"123" + "p_code":"121", + "code":"125" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1112,8 +1130,8 @@ "title":"What Are the Differences Between Import/Export and Fast Import/Export?", "uri":"en-us_topic_0199451475.html", "doc_type":"usermanual", - "p_code":"119", - "code":"124" + "p_code":"121", + "code":"126" }, { "desc":"Some images cannot be exported. Therefore, the Export option is not provided for them in the Operation column. The following images cannot be exported:Public imagesFull-E", @@ -1121,8 +1139,8 @@ "title":"What Do I Do If the Export Option Is Unavailable for My Image?", "uri":"en-us_topic_0199396601.html", "doc_type":"usermanual", - "p_code":"119", - "code":"125" + "p_code":"121", + "code":"127" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1130,8 +1148,8 @@ "title":"Image Optimization", "uri":"en-us_topic_0030713203.html", "doc_type":"usermanual", - "p_code":"94", - "code":"126" + "p_code":"96", + "code":"128" }, { "desc":"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", @@ -1139,8 +1157,17 @@ "title":"Must I Install Guest OS Drivers on an ECS?", "uri":"en-us_topic_0030713214.html", "doc_type":"usermanual", - "p_code":"126", - "code":"127" + "p_code":"128", + "code":"129" + }, + { + "desc":"VMTools is a VirtIO driver (para-virtualization driver) that provides high-performance disks and NICs for ECSs.A standard Windows OS does not have the VirtIO driver.Publi", + "product_code":"ims", + "title":"Why Do I Need to Install and Update VMTools for Windows?", + "uri":"en-us_topic_0165718046.html", + "doc_type":"usermanual", + "p_code":"128", + "code":"130" }, { "desc":"You are advised to enable automatic configuration when registering a private image using an image file. Then, the system will perform the following operations:Check wheth", @@ -1148,8 +1175,8 @@ "title":"What Will the System Do to an Image File When I Use the File to Register a Private Image?", "uri":"en-us_topic_0032307025.html", "doc_type":"usermanual", - "p_code":"126", - "code":"128" + "p_code":"128", + "code":"131" }, { "desc":"When registering an external image file as a private image, you are advised to perform the preceding operations on the VM where the external image file is located.When re", @@ -1157,8 +1184,8 @@ "title":"How Do I Configure an ECS, BMS, or Image File Before I Use It to Create an Image?", "uri":"en-us_topic_0040740508.html", "doc_type":"usermanual", - "p_code":"126", - "code":"129" + "p_code":"128", + "code":"132" }, { "desc":"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 ", @@ -1166,8 +1193,8 @@ "title":"What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?", "uri":"en-us_topic_0030713185.html", "doc_type":"usermanual", - "p_code":"126", - "code":"130" + "p_code":"128", + "code":"133" }, { "desc":"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 ", @@ -1175,8 +1202,8 @@ "title":"What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?", "uri":"en-us_topic_0030713211.html", "doc_type":"usermanual", - "p_code":"126", - "code":"131" + "p_code":"128", + "code":"134" }, { "desc":"With the increase of network I/O bandwidth, a single vCPU cannot meet the requirement of processing NIC interruptions. NIC multi-queue allows multiple vCPUs to process NI", @@ -1184,8 +1211,8 @@ "title":"How Do I Enable NIC Multi-Queue for an Image?", "uri":"en-us_topic_0085214115.html", "doc_type":"usermanual", - "p_code":"126", - "code":"132" + "p_code":"128", + "code":"135" }, { "desc":"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 ", @@ -1193,8 +1220,8 @@ "title":"How Do I Make a System Disk Image Support Fast ECS Creation?", "uri":"en-us_topic_0187108863.html", "doc_type":"usermanual", - "p_code":"126", - "code":"133" + "p_code":"128", + "code":"136" }, { "desc":"Possible causes:Your image file was exported from a VMware VM, and VMware Tools was not uninstalled or not completely uninstalled.You have downloaded the Guest OS driver ", @@ -1202,17 +1229,17 @@ "title":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?", "uri":"en-us_topic_0030713215.html", "doc_type":"usermanual", - "p_code":"126", - "code":"134" + "p_code":"128", + "code":"137" }, { - "desc":"When optimizing a Linux private image, you need to install native Xen and KVM drivers for the image.If you do not install Xen drivers for the image, the network performan", + "desc":"When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drive", "product_code":"ims", - "title":"How Do I Install Native Xen and KVM Drivers?", + "title":"How Do I Install the Native Xen and KVM Drivers?", "uri":"en-us_topic_0086020894.html", "doc_type":"usermanual", - "p_code":"126", - "code":"135" + "p_code":"128", + "code":"138" }, { "desc":"If you want to store an unencrypted image in an encrypted way, you can select an encryption key when you replicate the image. Then, the system will generate an encrypted ", @@ -1220,8 +1247,26 @@ "title":"Image Encryption", "uri":"en-us_topic_0049196765.html", "doc_type":"usermanual", - "p_code":"94", - "code":"136" + "p_code":"96", + "code":"139" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Accounts and Permissions", + "uri":"en-us_topic_0205273057.html", + "doc_type":"usermanual", + "p_code":"96", + "code":"140" + }, + { + "desc":"To share an encrypted image, you need to authorize the key used for encrypting the image. This section describes how to authorize a key.The key can only be a custom key. ", + "product_code":"ims", + "title":"How Do I Authorize a Key?", + "uri":"en-us_topic_0133773781.html", + "doc_type":"usermanual", + "p_code":"140", + "code":"141" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1229,8 +1274,8 @@ "title":"Cloud-Init", "uri":"en-us_topic_0138479468.html", "doc_type":"usermanual", - "p_code":"94", - "code":"137" + "p_code":"96", + "code":"142" }, { "desc":"Cloud-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloud-Init, you can use user data injection to inject customize", @@ -1238,8 +1283,8 @@ "title":"What Can I Do with a Cloud-Init ECS?", "uri":"en-us_topic_0148873774.html", "doc_type":"usermanual", - "p_code":"137", - "code":"138" + "p_code":"142", + "code":"143" }, { "desc":"A major cause is that the version of Cloud-Init is incompatible with that of NetworkManager. In Debian 9.0 and later versions, NetworkManager is incompatible with Cloud-I", @@ -1247,8 +1292,8 @@ "title":"What Do I Do If Injecting the Key or Password Using Cloud-Init Failed After NetworkManager Is Installed?", "uri":"en-us_topic_0113992021.html", "doc_type":"usermanual", - "p_code":"137", - "code":"139" + "p_code":"142", + "code":"144" }, { "desc":"growpart for SUSE and openSUSE is an independent toolkit that does not start with cloud-*. Perform operations in this section to install growpart.Run the following comman", @@ -1256,8 +1301,8 @@ "title":"How Do I Install growpart for SUSE 11 SP4?", "uri":"en-us_topic_0078454810.html", "doc_type":"usermanual", - "p_code":"137", - "code":"140" + "p_code":"142", + "code":"145" }, { "desc":"An image whose root partition file system is xfs cannot automatically expand its partitions.An image that has the LVM partition cannot automatically expand its partitions", @@ -1265,8 +1310,8 @@ "title":"How Do I Configure a Linux Private Image to Make It Automatically Expand Its Root Partition?", "uri":"en-us_topic_0076880304.html", "doc_type":"usermanual", - "p_code":"137", - "code":"141" + "p_code":"142", + "code":"146" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1274,8 +1319,8 @@ "title":"ECS Creation", "uri":"en-us_topic_0030713220.html", "doc_type":"usermanual", - "p_code":"94", - "code":"142" + "p_code":"96", + "code":"147" }, { "desc":"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", @@ -1283,8 +1328,8 @@ "title":"Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to Create the Private Image?", "uri":"en-us_topic_0030713209.html", "doc_type":"usermanual", - "p_code":"142", - "code":"143" + "p_code":"147", + "code":"148" }, { "desc":"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 specif", @@ -1292,8 +1337,8 @@ "title":"Can I Specify the System Disk Size When I Create an ECS Using an Image?", "uri":"en-us_topic_0030713221.html", "doc_type":"usermanual", - "p_code":"142", - "code":"144" + "p_code":"147", + "code":"149" }, { "desc":"This may be caused by a disk partition ID change after the cross-platform image import. As a result, no partition can be found based on the original disk partition ID in ", @@ -1301,8 +1346,8 @@ "title":"What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private Image?", "uri":"en-us_topic_0034220644.html", "doc_type":"usermanual", - "p_code":"142", - "code":"145" + "p_code":"147", + "code":"150" }, { "desc":"Generally, this is because the xen-blkfront.ko module is not loaded during the startup. You need to modify OS kernel startup parameters. Figure 1 shows the startup screen", @@ -1310,8 +1355,8 @@ "title":"What Do I Do If the Disks of an ECS Created from a CentOS Image Cannot Be Found?", "uri":"en-us_topic_0030713219.html", "doc_type":"usermanual", - "p_code":"142", - "code":"146" + "p_code":"147", + "code":"151" }, { "desc":"This issue is probably caused by the failure of offline VirtIO driver injection.When you inject the VirtIO driver for a Windows ECS offline, there are some restrictions:I", @@ -1319,8 +1364,8 @@ "title":"What Do I Do If an ECS Created from a Windows Image Failed to Start When I Have Enabled Automatic Configuration During Image Registration?", "uri":"en-us_topic_0113403127.html", "doc_type":"usermanual", - "p_code":"142", - "code":"147" + "p_code":"147", + "code":"152" }, { "desc":"An ECS created from a private image using the UEFI boot mode cannot start.The image OS uses the UEFI boot mode, but the uefi attribute is not added to the image.Delete th", @@ -1328,8 +1373,8 @@ "title":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mode?", "uri":"en-us_topic_0161870891.html", "doc_type":"usermanual", - "p_code":"142", - "code":"148" + "p_code":"147", + "code":"153" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1338,7 +1383,7 @@ "uri":"en-us_topic_0041178787.html", "doc_type":"usermanual", "p_code":"", - "code":"149" + "code":"154" }, { "desc":"For details about the terms involved in this document, see Glossary.", @@ -1347,6 +1392,6 @@ "uri":"en-us_topic_0047898081.html", "doc_type":"usermanual", "p_code":"", - "code":"150" + "code":"155" } ] \ No newline at end of file diff --git a/docs/ims/umn/en-us_image_0000001455418292.png b/docs/ims/umn/en-us_image_0000001455418292.png new file mode 100644 index 000000000..784858155 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001455418292.png differ diff --git a/docs/ims/umn/en-us_image_0000001505495049.png b/docs/ims/umn/en-us_image_0000001505495049.png new file mode 100644 index 000000000..9a61c964d Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001505495049.png differ diff --git a/docs/ims/umn/en-us_image_0030714279.png b/docs/ims/umn/en-us_image_0030714279.png deleted file mode 100644 index 67c1f65b6..000000000 Binary files a/docs/ims/umn/en-us_image_0030714279.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0030714282.png b/docs/ims/umn/en-us_image_0030714282.png deleted file mode 100644 index 8b0dfdfa8..000000000 Binary files a/docs/ims/umn/en-us_image_0030714282.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0030714285.png b/docs/ims/umn/en-us_image_0030714285.png deleted file mode 100644 index 97123d4e5..000000000 Binary files a/docs/ims/umn/en-us_image_0030714285.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0030714288.png b/docs/ims/umn/en-us_image_0030714288.png deleted file mode 100644 index a67640d2e..000000000 Binary files a/docs/ims/umn/en-us_image_0030714288.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0118549088.png b/docs/ims/umn/en-us_image_0118549088.png deleted file mode 100644 index 1e9d829cf..000000000 Binary files a/docs/ims/umn/en-us_image_0118549088.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0120595879.png b/docs/ims/umn/en-us_image_0120595879.png deleted file mode 100644 index d1f94c13c..000000000 Binary files a/docs/ims/umn/en-us_image_0120595879.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0120595887.png b/docs/ims/umn/en-us_image_0120595887.png deleted file mode 100644 index d1f94c13c..000000000 Binary files a/docs/ims/umn/en-us_image_0120595887.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0120595964.png b/docs/ims/umn/en-us_image_0120595964.png deleted file mode 100644 index 96d747aab..000000000 Binary files a/docs/ims/umn/en-us_image_0120595964.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0162743998.png b/docs/ims/umn/en-us_image_0162743998.png new file mode 100644 index 000000000..c8aab8471 Binary files /dev/null and b/docs/ims/umn/en-us_image_0162743998.png differ diff --git a/docs/ims/umn/en-us_image_0162744031.png b/docs/ims/umn/en-us_image_0162744031.png new file mode 100644 index 000000000..c8aab8471 Binary files /dev/null and b/docs/ims/umn/en-us_image_0162744031.png differ diff --git a/docs/ims/umn/en-us_image_0162744204.png b/docs/ims/umn/en-us_image_0162744204.png new file mode 100644 index 000000000..7cc72f323 Binary files /dev/null and b/docs/ims/umn/en-us_image_0162744204.png differ diff --git a/docs/ims/umn/en-us_image_0162745871.png b/docs/ims/umn/en-us_image_0162745871.png new file mode 100644 index 000000000..e2f628267 Binary files /dev/null and b/docs/ims/umn/en-us_image_0162745871.png differ diff --git a/docs/ims/umn/en-us_image_0172485503.png b/docs/ims/umn/en-us_image_0172485503.png new file mode 100644 index 000000000..b8bab1d8c Binary files /dev/null and b/docs/ims/umn/en-us_image_0172485503.png differ diff --git a/docs/ims/umn/en-us_image_0180992673.png b/docs/ims/umn/en-us_image_0180992673.png new file mode 100644 index 000000000..14c093006 Binary files /dev/null and b/docs/ims/umn/en-us_image_0180992673.png differ diff --git a/docs/ims/umn/en-us_image_0180992674.png b/docs/ims/umn/en-us_image_0180992674.png deleted file mode 100644 index d48cc79b4..000000000 Binary files a/docs/ims/umn/en-us_image_0180992674.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0187518440.png b/docs/ims/umn/en-us_image_0187518440.png new file mode 100644 index 000000000..484e614b7 Binary files /dev/null and b/docs/ims/umn/en-us_image_0187518440.png differ diff --git a/docs/ims/umn/en-us_topic_0000001120952155.html b/docs/ims/umn/en-us_topic_0000001120952155.html index ac2855280..92bf5f9c5 100644 --- a/docs/ims/umn/en-us_topic_0000001120952155.html +++ b/docs/ims/umn/en-us_topic_0000001120952155.html @@ -1,56 +1,55 @@

Installing Native KVM Drivers

-

Scenarios

When optimizing a Linux private image, you need to install native KVM drivers on the ECS.

+

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.

-

This section describes how to install native KVM drivers.

-

Prerequisites

  • ECSs that use native Linux KVM drivers must have a kernel later than the 2.6.24 version.
  • Disable your antivirus and intrusion detection software. You can enable the software after KVM drivers are installed.
+

Prerequisites

  • The ECS is using KVM virtualization and needs to be optimized. For details, see
  • 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.

Procedure

Modify the configuration file based on the OS version.

-
Table 1 Modifying configuration files for different OSs

OS

+
- - - - - - - - - - - - - - - @@ -63,7 +62,7 @@ add_drivers+="virtio_blkvirtio_scsivirtio_netvirtio_pcivirtio_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 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:

    lsinitrd /boot/initrd-`uname -r` | grep virtio

    @@ -153,11 +152,11 @@ 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.
    1. Run the following command to open the /etc/dracut.conf file:

      vi /etc/dracut.conf

      +

      SUSE and openSUSE (SUSE 12 SP1)

      Modify the /etc/dracut.conf file.
      1. Run the following command to open the /etc/dracut.conf file:

        vi /etc/dracut.conf

      2. 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 
 # additional kernel modules to the default
 add_drivers+="ata_piix ata_generic virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
        -
      3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
      4. Run the following command to regenerate initrd:

        dracut -f /boot/initramfs-File name

        +
      5. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
      6. 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.

      7. 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:

        @@ -167,11 +166,11 @@ add_drivers+="ata_piix

      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.
      1. Run the following command to open the /etc/dracut.conf file:

        vi /etc/dracut.conf

        -
      2. 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 
+
      3. 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 
 # additional kernel modules to the default
 add_drivers+="ata_piix ata_generic virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
        -
      4. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
      5. 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.

        +
      6. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
      7. 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.

      8. 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:

        lsinitrd /boot/initrd-`uname -r` | grep virtio

        diff --git a/docs/ims/umn/en-us_topic_0000001175697174.html b/docs/ims/umn/en-us_topic_0000001175697174.html index 38b1b5f6d..ceffe039b 100644 --- a/docs/ims/umn/en-us_topic_0000001175697174.html +++ b/docs/ims/umn/en-us_topic_0000001175697174.html @@ -1,34 +1,33 @@

        Importing an Image

        -

        IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size.

        -
    Table 1 Modifying configuration files for different OSs

    OS

    Configuration

    +

    Configuration

    Reference

    +

    Reference

    CentOS/EulerOS

    +

    CentOS/EulerOS

    Take CentOS 7.0 as an example.

    +

    Take CentOS 7.0 as an example.

    1. 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.
    2. Save and exit the /etc/dracut.conf file and run the dracut -f command to generate initrd again.

    CentOS, EulerOS

    +

    CentOS, EulerOS

    Ubuntu/Debian

    +

    Ubuntu/Debian

    1. In the /etc/initramfs-tools/modules file, add VirtIO drivers, including virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces.
    2. Save and exit the /etc/initramfs-tools/modules file and run the update-initramfs -u command to generate initrd again.
    +
    1. In the /etc/initramfs-tools/modules file, add VirtIO drivers, including virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces.
    2. Save and exit the /etc/initramfs-tools/modules file and run the update-initramfs -u command to generate initrd again.

    Ubuntu and Debian

    +

    Ubuntu and Debian

    SUSE and openSUSE

    +

    SUSE and openSUSE

    If the OS version is earlier than SUSE 12 SP1 or openSUSE 13:

    +

    If the OS version is earlier than SUSE 12 SP1 or openSUSE 13:

    1. In the /etc/sysconfig/kernel file, add VirtIO drivers to INITRD_MODULES="". VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces.
    2. Run the mkinitrd command to generate initrd again.

    SUSE and openSUSE (Earlier than SUSE 12 SP1 or openSUSE 13)

    +

    SUSE and openSUSE (Earlier than SUSE 12 SP1 or openSUSE 13)

    If the OS version is SUSE 12 SP1:

    +

    If the OS version is SUSE 12 SP1:

    1. In the /etc/dracut.conf file, add VirtIO drivers to add_drivers. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces.
    2. Run the dracut -f command to generate initrd again.

    SUSE and openSUSE (SUSE 12 SP1)

    +

    SUSE and openSUSE (SUSE 12 SP1)

    If the OS version is later than SUSE 12 SP1 or openSUSE 13:

    -
    1. In the /etc/dracut.conf file, add VirtIO drivers to add_drivers. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces.
    2. Save and exit the /etc/dracut.conf file and run the dracut -f command to generate initrd again.
    +

    If the OS version is later than SUSE 12 SP1 or openSUSE 13:

    +
    1. 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.
    2. Save and exit the /etc/dracut.conf file and run the dracut -f command to generate initrd again.

    SUSE and openSUSE (Later than SUSE 12 SP1 or openSUSE 13)

    +

    SUSE and openSUSE (Later than SUSE 12 SP1 or openSUSE 13)
    Table 1 Importing a system disk image file

    File Format

    +
    IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size. +
    - - - - - - - -
    Table 1 Importing an image

    Format

    File Size

    +

    File Size

    Reference

    +

    Reference

    VMDK, VHD, QCOW2, VHDX, QED, VDI, QCOW, or ZVHD

    +

    VMDK, VHD, QCOW2, VHDX, QED, VDI, QCOW, or ZVHD

    Not larger than 128 GB

    +

    Not larger than 128 GB

    		 +

    RAW or ZVHD2

    +

    RAW or ZVHD2

    No larger than 1 TB

    +

    No larger than 1 TB

    		 +
    - +
    diff --git a/docs/ims/umn/en-us_topic_0000001347866330.html b/docs/ims/umn/en-us_topic_0000001347866330.html new file mode 100644 index 000000000..7e4596f43 --- /dev/null +++ b/docs/ims/umn/en-us_topic_0000001347866330.html @@ -0,0 +1,229 @@ + + +

    Install the Native Xen and KVM Drivers

    +

    Scenarios

    When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the source ECS of the image.

    +

    This section describes how to install the native Xen and KVM drivers.

    +

    Xen: If you do not install the Xen driver for the image, the network performance of the ECSs created from this image will be poor, and the security groups and firewall configured for the ECSs will not take effect.

    +

    KVM: If you do not install the KVM driver for the image, the NICs of the ECSs may not be detected and the ECSs will be unable to communicate with other resources.

    +
    +
    +

    Prerequisites

    • The virtualization type of the ECS is Xen. For details, see .
    • The kernel version must be later than 2.6.24.
    • Disable your antivirus and intrusion detection software. You can enable them after installation of the Xen and KVM drivers.
    +
    +

    Procedure

    Modify the configuration file depending on the OS.
    • CentOS, EulerOS

      Take CentOS 7.0 as an example. Modify the /etc/dracut.conf file. Add the xen-pv and VirtIO drivers to add_drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include 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. Run the dracut -f command to regenerate initrd.

      +

      For details, see CentOS and EulerOS.

      +
    • Ubuntu and Debian

      Modify the /etc/initramfs-tools/modules file. Add the xen-pv and VirtIO drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Save and exit the /etc/initramfs-tools/modules file. Run the update-initramfs -u command to regenerate initrd.

      +

      For details, see Ubuntu and Debian.

      +
    • SUSE and openSUSE
      • If the OS version is earlier than SUSE 12 SP1 or openSUSE 13, modify the /etc/sysconfig/kernel file and add xen-pv and VirtIO drivers to INITRD_MODULES="". xen-pv drivers include xen_vnif, xen_vbd, and xen_platform_pci. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Run the mkinitrd command to regenerate initrd.
      • If the OS version is SUSE 12 SP1, modify the /etc/dracut.conf file and add xen-pv and VirtIO drivers to add_drivers. xen-pv drivers include xen_vnif, xen_vbd, and xen_platform_pci. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Run the dracut -f command to regenerate initrd.
      • If the OS version is later than SUSE 12 SP1 or openSUSE 13, modify the /etc/dracut.conf file and add xen-pv and VirtIO drivers to add_drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include 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. Run the dracut -f command to regenerate initrd.
      +
      For details, see SUSE and openSUSE.

      For SUSE, run the following command to check whether xen-kmp (driver package for xen-pv) is installed:

      +

      rpm -qa |grep xen-kmp

      +

      If information similar to the following is displayed, xen-kmp is installed in the OS:

      +
      xen-kmp-default-4.2.2_04_3.0.76_0.11-0.7.5
      +

      If xen-kmp is not installed, obtain it from the ISO file and install it.

      +

      If you add built-in drivers to the initrd or initramfs file by mistake, the ECS will not be affected.

      +
      +
      +
    +
    +
    +

    CentOS and EulerOS

    1. Run the following command to open the /etc/dracut.conf file:

      vi /etc/dracut.conf

      +
    2. Press i to enter editing mode and add the xen-pv and 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+="xen-blkfront xen-netfront virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio" 
+......
      +
    3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
    4. 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.

      +
    5. If the virtual file system is initramfs, run the following commands to check whether native Xen and KVM drivers have been loaded:

      lsinitrd /boot/initramfs-`uname -r`.img | grep xen

      +

      lsinitrd /boot/initramfs-`uname -r`.img | grep virtio

      +

      If the virtual file system is initrd, run the following commands to check whether native Xen and KVM drivers have been loaded:

      +

      lsinitrd /boot/initrd-`uname -r` | grep xen

      +

      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 xen 
+-rwxr--r--   1 root     root        54888 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/block/xen-blkfront.ko 
+-rwxr--r--   1 root     root        45664 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/net/xen-netfront.ko 
+ 
+[root@CTU10000xxxxx home]# lsinitrd /boot/initramfs-`uname -r`.img | grep virtio 
+-rwxr--r--   1 root     root        23448 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/block/virtio_blk.ko 
+-rwxr--r--   1 root     root        50704 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/net/virtio_net.ko 
+-rwxr--r--   1 root     root        28424 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/scsi/virtio_scsi.ko 
+drwxr-xr-x   2 root     root            0 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio 
+-rwxr--r--   1 root     root        14544 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio.ko 
+-rwxr--r--   1 root     root        21040 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko 
+-rwxr--r--   1 root     root        18016 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko
      +

      If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following commands to check whether built-in drivers are in the kernel:

      +

      cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y

      +

      cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y

      +
      +
    +
    +

    Ubuntu and Debian

    1. Run the following command to open the modules file:

      vi /etc/initramfs-tools/modules

      +
    2. Press i to enter editing mode and add the xen-pv and VirtIO drivers to the /etc/initramfs-tools/modules file (the format varies depending on the OS).
      [root@CTU10000xxxxx ~]#vi /etc/initramfs-tools/modules 
+......
+# Examples: 
+# 
+# raid1 
+# sd_mOd 
+xen-blkfront
+xen-netfront
+virtio_blk
+virtio_scsi
+virtio_net
+virtio_pci
+virtio_ring
+virtio
      +
    3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/initramfs-tools/modules file.
    4. Run the following command to regenerate initrd:

      update-initramfs -u

      +
    5. Run the following commands to check whether native Xen and KVM drivers have been installed:

      lsinitramfs /boot/initrd.img-`uname -r` |grep xen

      +

      lsinitramfs /boot/initrd.img-`uname -r` |grep virtio

      +
      [root@ CTU10000xxxxx home]# lsinitramfs /boot/initrd.img-`uname -r` |grep xen 
+lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/qlogic/netxen 
+lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/qlogic/netxen/netxen_nic.ko 
+lib/modules/3.5.0-23-generic/kernel/drivers/net/xen-netback 
+lib/modules/3.5.0-23-generic/kernel/drivers/net/xen-netback/xen-netback.ko 
+lib/modules/3.5.0-23-generic/kernel/drivers/block/xen-blkback 
+lib/modules/3.5.0-23-generic/kernel/drivers/block/xen-blkback/xen-blkback.ko 
+ 
+[root@ CTU10000xxxxx home]# lsinitramfs /boot/initrd.img-`uname -r` |grep virtio 
+lib/modules/3.5.0-23-generic/kernel/drivers/scsi/virtio_scsi.ko
      +

      If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following commands to check whether built-in drivers are in the kernel:

      +
      [root@ CTU10000xxxxx home]# cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y
+CONFIG_VIRTIO_BLK=y
+CONFIG_VIRTIO_NET=y
+CONFIG_VIRTIO=y
+CONFIG_VIRTIO_RING=y
+CONFIG_VIRTIO_PCI=y
+CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
+[root@ CTU10000xxxxx home]# cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y
+CONFIG_XEN_BLKDEV_FRONTEND=y
+CONFIG_XEN_NETDEV_FRONTEND=y
      +
      +
    +
    +

    SUSE and openSUSE

    If the OS version is earlier than SUSE 12 SP1 or openSUSE 13, modify the /etc/sysconfig/kernel file. For details, see scenario 1.

    +

    If the OS version is SUSE 12 SP1, modify the /etc/dracut.conf file and add xen-pv and VirtIO drivers. For details, see scenario 2.

    +
    If the OS version is later than SUSE 12 SP1 or openSUSE 13, modify the /etc/dracut.conf file and add xen-pv and VirtIO drivers to add_drivers. For details, see scenario 3.
    • If the OS version is earlier than SUSE 12 SP1 or openSUSE 13, perform the following steps:

      For SUSE, run the following command to check whether xen-kmp (driver package for xen-pv) is installed in the OS:

      +

      rpm -qa |grep xen-kmp

      +

      If information similar to the following is displayed, xen-kmp is installed:

      +
      xen-kmp-default-4.2.2_04_3.0.76_0.11-0.7.5
      +

      If xen-kmp is not installed, obtain it from the installation ISO and install it first.

      +
      +
      1. Run the following command to open the /etc/sysconfig/kernel file:

        vi etc/sysconfig/kernel

        +
      2. Add the xen-pv and VirtIO drivers after INITRD_MODULES= (the format of drivers depends on the OS).
        SIA10000xxxxx:~ # vi /etc/sysconfig/kernel 
+# (like drivers for scsi-controllers, for lvm or reiserfs)
+#
+INITRD_MODULES="ata_piix ata_generic xen_vnif xen_vbd xen_platform_pci virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
        +
      3. Run the mkinitrd command to regenerate initrd:

        If the virtual file system is not the default initramfs or initrd, 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 menu.lst or grub.cfg file (/boot/grub/menu.lst, /boot/grub/grub.cfg, or /boot/grub2/grub.cfg).

        +
        +

        The following is an example initrd file of SUSE 11 SP4:

        +
        default 0
+timeout 10
+gfxmenu (hd0,0)/boot/message
+title sles11sp4_001_[_VMX_]
+root (hd0,0)
+kernel /boot/linux.vmx vga=0x314 splash=silent console=ttyS0,115200n8 console=tty0 net.ifnames=0 NON_PERSISTENT_DEVICE_NAMES=1 showopts
+initrd /boot/initrd.vmx
+title Failsafe_sles11sp4_001_[_VMX_]
+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.

        +
      4. Run the following commands to check whether the PVOPS module for Xen or VirtIO module for KVM is loaded:

        lsinitrd /boot/initrd-`uname -r` | grep xen

        +
        lsinitrd /boot/initrd-`uname -r` | grep virtio
        SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep xen
+-rwxr--r-- 1 root root 42400 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/xen-blkfront.ko
+-rwxr--r-- 1 root root 44200 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/xen-netfront.ko
+
+SIA10000xxxxx:~ # 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
+-rwxr--r-- 1 root root 15848 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko
+-rwxr--r-- 1 root root 20008 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko
+-rwxr--r-- 1 root root 12272 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio.ko
+-rwxr--r-- 1 root root 38208 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/virtio_net.ko
        +
        +
      5. Restart the ECS.
      6. Modify the /boot/grub/menu.lst file. Add xen_platform_pci.dev_unplug=all and modify the root configuration.

        Before the modification:

        +
        ###Don't change this comment -YaST2 identifier: Original name: linux###
+title SUSE Linux Enterprise Server 11SP4 - 3.0.76-0.11 (default) 
+root (hd0,0) 
+kernel /boot/vmlinuz-3.0.76-0.11-default root=UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130 splash=silentcrashkernel=256M-:128M showopts vga=0x314
+initrd /boot/initrd-3.0.76-0.11-default
        +

        After the modification:

        +
        ###Don't change this comment -YaST2 identifier: Original name: linux###
+title SUSE Linux Enterprise Server 11SP4 - 3.0.76-0.11 (default) 
+root (hd0,0) 
+kernel /boot/vmlinuz-3.0.76-0.11-default root=UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130 splash=silentcrashkernel=256M-:128M showopts vga=0x314 xen_platform_pci.dev_unplug=all 
+initrd /boot/initrd-3.0.76-0.11-default
        +
        • Ensure that the root partition is in the UUID format.
        • xen_platform_pci.dev_unplug=all is added to shield QEMU devices.
        • For SUSE 11 SP1 64bit to SUSE 11 SP4 64bit, add xen_platform_pci.dev_unplug=all to the menu.lst file. For SUSE 12 or later, this function is enabled by default, and you do not need to configure it.
        +
        +
      7. Run the following commands to check whether the Xen drivers exist in initrd:

        lsinitrd /boot/initrd-`uname -r` | grep xen

        +

        lsinitrd /boot/initrd-`uname -r` | grep virtio

        +
        SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep xen
+-rwxr--r-- 1 root root 42400 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/xen-blkfront.ko
+-rwxr--r-- 1 root root 44200 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/xen-netfront.ko
+
+SIA10000xxxxx:~ # 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
+-rwxr--r-- 1 root root 15848 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko
+-rwxr--r-- 1 root root 20008 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko
+-rwxr--r-- 1 root root 12272 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio.ko
+-rwxr--r-- 1 root root 38208 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/virtio_net.ko
        +

        If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following commands to check whether built-in drivers are in the kernel:

        +

        cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y

        +

        cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y

        +
        +
      +
    • If the OS version is SUSE 12 SP1, perform the following steps:
      1. Run the following command to open the /etc/dracut.conf file:

        vi /etc/dracut.conf

        +
      2. Press i to enter editing mode and add the xen-pv and 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 xen_vnif xen_vbd xen_platform_pci virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
        +
      3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
      4. 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.

        +
      5. If the virtual file system is initramfs, run the following commands to check whether native Xen and KVM drivers have been loaded:

        lsinitrd /boot/initramfs-`uname -r`.img | grep xen

        +

        lsinitrd /boot/initramfs-`uname -r`.img | grep virtio

        +

        If the virtual file system is initrd, run the following commands to check whether native Xen and KVM drivers have been loaded:

        +

        lsinitrd /boot/initrd-`uname -r` | grep xen

        +

        lsinitrd /boot/initrd-`uname -r` | grep virtio

        +
      +
    • If the OS version is later than SUSE 12 SP1 or openSUSE 13, perform the following steps:
      Take SUSE Linux Enterprise Server 12 SP2 (x86_64) as an example.
      1. Run the following command to open the /etc/dracut.conf file:

        vi /etc/dracut.conf

        +
      2. Press i to enter editing mode and add the xen-pv and 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 xen-blkfront xen-netfront virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
        +
      3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
      4. 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.

        +
      5. If the virtual file system is initramfs, run the following commands to check whether native Xen and KVM drivers have been loaded:

        lsinitrd /boot/initramfs-`uname -r`.img | grep xen

        +

        lsinitrd /boot/initramfs-`uname -r`.img | grep virtio

        +

        If the virtual file system is initrd, run the following commands to check whether the native Xen and KVM driver modules are successfully loaded:

        +

        lsinitrd /boot/initrd-`uname -r` | grep xen

        +

        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 xen
+-rw-r--r-- 1 root root 69575 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/block/xen-blkfront.ko
+-rw-r--r-- 1 root root 53415 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/net/xen-netfront.ko
+drwxr-xr-x 2 root root 0 Sep 28 10:21 lib/modules/4.4.21-69-default/updates/pvdriver/xen-hcall
+-rwxr-xr-x 1 root root 8320 Sep 28 10:21 lib/modules/4.4.21-69-default/updates/pvdriver/xen-hcall/xen-hcall.ko
+
+sluo-ecs-30dc:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio
+-rw-r--r-- 1 root root 29335 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/block/virtio_blk.ko
+-rw-r--r-- 1 root root 57007 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/net/virtio_net.ko
+-rw-r--r-- 1 root root 32415 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/scsi/virtio_scsi.ko
+drwxr-xr-x 2 root root 0 Sep 28 10:21 lib/modules/4.4.21-69-default/kernel/drivers/virtio
+-rw-r--r-- 1 root root 19623 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio.ko
+-rw-r--r-- 1 root root 38943 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio_pci.ko
+-rw-r--r-- 1 root root 24431 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio_ring.ko
        +

        If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following commands to check whether built-in drivers are in the kernel:

        +

        cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y

        +

        cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y

        +
        +
      +
      +
    +
    +
    +
    +
    +
    +
    Parent topic: Optimizing a Linux Private Image
    +
    +
    + diff --git a/docs/ims/umn/en-us_topic_0013901609.html b/docs/ims/umn/en-us_topic_0013901609.html index b946a30f9..ffef22192 100644 --- a/docs/ims/umn/en-us_topic_0013901609.html +++ b/docs/ims/umn/en-us_topic_0013901609.html @@ -1,10 +1,10 @@

    What Is Image Management Service?

    -

    Overview

    An image is a server or disk template that contains an operating system (OS) or service data and necessary software, such as database software. IMS provides public, private, and shared images.

    +

    Overview

    An image is a cloud server or disk template that contains an operating system (OS), service data, or necessary software.

    Image Management Service (IMS) allows you to manage the entire lifecycle of your images. You can create ECSs or BMSs from public, private, or shared images. You can also create a private image from a cloud server or an external image file to make it easier to migrate workloads to the cloud or on the cloud.

    -

    Image Types

    Images are classified as public, private, and shared. Public images are provided by the cloud platform, private images are those you created yourself, and shared images are private images that other tenants have shared with you.

    +

    Image Types

    IMS provides public, private, and shared images. Public images are provided by the cloud platform, private images are created by users, and shared images are private images that other users shared with you.

    @@ -14,14 +14,14 @@ -

    Image Type

    Public image

    A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. Public images are very stable and their OS and any included software have been officially authorized for use. If a public image does not contain the application environments or software you need, you can use a public image to create an ECS and then deploy required software as needed.

    +

    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

    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 pre-installed software for various services. You can use a system disk image to create ECSs and migrate your services to the cloud.
    • A data disk image contains only service data. You can use a data disk image to create EVS disks and use them to migrate your service data to the cloud.
    • A full-ECS image contains an OS, pre-installed software, and service data. A full-ECS image is created using differential backups and the creation takes less time than creating a system or data disk image of the same size.
    +
    • 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.

    Shared image

    diff --git a/docs/ims/umn/en-us_topic_0013901628.html b/docs/ims/umn/en-us_topic_0013901628.html index c41f85e9b..04b17afe4 100644 --- a/docs/ims/umn/en-us_topic_0013901628.html +++ b/docs/ims/umn/en-us_topic_0013901628.html @@ -5,6 +5,7 @@

    Creating a private image does not affect the running of services on the cloud server or cause data loss.

    This section describes how to create a private image using any of the following methods:
    +

    After a system disk image is created, you can use it to change the OS of an ECS.

    diff --git a/docs/ims/umn/en-us_topic_0030713142.html b/docs/ims/umn/en-us_topic_0030713142.html index a92dd03b2..5115c266b 100644 --- a/docs/ims/umn/en-us_topic_0030713142.html +++ b/docs/ims/umn/en-us_topic_0030713142.html @@ -1,539 +1,260 @@

    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 T6

      -

      General computing S2, S3, S6, and SN3

      -

      General computing-plus C3 and C6

      -

      Memory-optimized M2, M3, and M6

      -

      High-performance computing HC2 and H3

      -

      Disk-intensive D2 and D3

      -
    • Table 2 lists the OSs supported by the following ECSs:

      General computing-plus C3ne, C6, and C6s

      -

      Memory-optimized M3ne

      -
    • Table 3 lists the OSs supported by the following ECSs:

      Large-memory E3

      -
    • Table 4 lists the OSs supported by the following ECSs:

      Ultra-high I/O I3 and IR3

      -
    • For other GPU-accelerated ECSs, see the GPU product description.
      • 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.
      -
      +

      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

        +

        Dedicated general-purpose C3, C4

        +

        Memory-optimized M2, 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
      +
      • 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 1 Supported OS versions-01

      OS

      +
      - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + +
      Table 1 Supported OS versions

      OS

      OS Version

      +

      Version

      Windows

      +

      Alma

      Windows Server 2008 R2 Standard/Enterprise/Datacenter/Web

      -

      Windows Server 2012 Standard/Datacenter

      -

      Windows Server 2012 R2 Standard/Datacenter

      -

      Windows Server 2016 Standard/Datacenter

      -

      Windows Server 2019 Standard/Datacenter

      -

      Windows Server Core Version 1709

      +

      Alma 8 64bit

      CentOS

      +

      CentOS

      64-bit: CentOS 6.10, 6.9, 6.8, 6.7, 6.6, 6.5, 6.4, and 6.3

      -

      64-bit: CentOS 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, and 7.0

      -

      64-bit: CentOS 8.3, 8.2, 8.1, and 8.0

      +
      • CentOS Stream 8.6 64bit
      • CentOS 7.9 64bit
      • CentOS 7.7 64bit

      Ubuntu

      +

      Debian

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

      +
      • Debian GNU/Linux 11 64bit
      • Debian GNU/Linux 10 64bit

      EulerOS

      +

      EulerOS

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

      +

      EulerOS 2.5 64bit

      Red Hat

      +

      Fedora

      64-bit: Red Hat 6.10, 6.9, 6.8, 6.7, 6.6, 6.5, and 6.4

      -

      64-bit: Red Hat 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, and 7.0

      -

      64-bit: Red Hat 8.0

      +
      • Fedora 35 64bit
      • Fedora 34 64bit
      • Fedora 33 64bit

      SUSE Linux Enterprise

      +

      OpenSUSE

      64-bit: SLES 11 SP4 and 11 SP3

      -

      64-bit: SLES 12 SP4, 12 SP3, 12 SP2, 12 SP1, and 12

      -

      64-bit: SLES 15, 15 SP1, and 15 SP2

      +

      OpenSUSE 15.3 64bit

      Debian

      +

      Oracle Linux

      64-bit: Debian 8.0.0–8.10.0

      -

      64-bit: Debian 9.13.0, 9.12.0, 9.11.0, 9.9.0, 9.8.0, 9.7.0, 9.6.0, 9.5.0, 9.4.0, 9.3.0, and 9.0.0

      -

      64-bit: Debian 10.0.0–10.5.0, 10.7.0

      +
      • Oracle Linux Server release 8.4 64bit
      • Oracle Linux Server release 7.6 64bit

      openSUSE

      +

      Red Hat

      64-bit: openSUSE 13.2

      -

      64-bit: openSUSE Leap 15.1 and 15.0

      -

      64-bit: openSUSE Leap 42.3, 42.2, and 42.1

      +
      • Red Hat Enterprise Linux 7.9 64bit
      • Red Hat Enterprise Linux 6.10 64bit

      Fedora

      +

      Rocky

      64-bit: Fedora 22–32

      +

      Rocky 8 64bit

      CoreOS

      +

      SUSE

      64-bit: CoreOS 2079.4.0

      +
      • Novell SUSE Linux Enterprise Server 15 SP3 64bit
      • Novell SUSE Linux Enterprise Server 15 SP2 64bit
      • Novell SUSE Linux Enterprise Server 15 SP1 64bit
      • Novell SUSE Linux Enterprise Server 15 64bit
      • Novell SUSE Linux Enterprise Server 12 SP5 64bit
      • Novell SUSE Linux Enterprise Server 12 SP4 64bit
      • Novell SUSE Linux Enterprise Server 12 SP3 64bit

      FreeBSD

      +

      SUSE-SAP

      64bit: FreeBSD 11.0,10.3, and 12.1

      +
      • Novell SUSE Linux Enterprise Server 15 SP3 64bit
      • Novell SUSE Linux Enterprise Server 15 SP2 64bit
      • Novell SUSE Linux Enterprise Server 15 SP1 64bit
      • Novell SUSE Linux Enterprise Server 15 64bit
      • Novell SUSE Linux Enterprise Server 12 SP5 64bit
      • Novell SUSE Linux Enterprise Server 12 SP4 64bit
      • Novell SUSE Linux Enterprise Server 12 SP3 64bit

      openEuler

      +

      Ubuntu

      64-bit: openEuler 20.03

      +
      • Ubuntu 20.04 server 64bit
      • Ubuntu 18.04 server 64bit
      +

      Windows

      +
      • Windows Server 2019 Standard 64bit
      • Windows Server 2016 Standard 64bit
      • Windows Server 2012 R2 Standard 64bit
      +

      openEuler

      +

      openEuler 20.03 64bit
      -
      Table 2 Supported OS versions-02

      OS

      +
      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      Table 2 Supported OS versions

      OS

      OS Version

      -

      Kernel Version

      +

      Version

      Windows

      +

      CentOS

      Windows Server 2008 R2 Enterprise/Datacenter/Web/Standard

      -

      Windows Server 2012 R2 Standard/Datacenter

      -

      Windows Server 2016 Standard/Datacenter

      -

      Windows Server 2019 Datacenter

      -

      Windows Server Version 1709 Datacenter

      -

      10.0.14393

      -

      6.1.7600

      -

      6.0.6002

      -

      6.1.7600

      -

      6.3.9600

      +
      • CentOS 7.9 64bit
      • CentOS 7.7 64bit

      CentOS

      +

      EulerOS

      64-bit:

      -

      CentOS 6

      -

      CentOS 7

      -

      CentOS 8

      -

      2.6.32-754.10.1.e16.x86_64

      -

      2.6.32-696.16.1.el6.x86_64

      -

      2.6.32-754.10.1.el6.x86_64

      -

      2.6.32-754.11.1.e16.x86_64

      -

      3.10.0-514.10.2.el7.x86_64

      -

      3.10.0-693.11.1.el7.x86_64

      -

      3.10.0-862.9.1.el7.x86_64

      -

      3.10.0-957.5.1.e17.x86_64

      -

      3.10.0-957.10.1.e17.x86_64

      +

      EulerOS 2.5 64bit

      Ubuntu

      +

      Fedora

      64-bit:

      -

      Ubuntu 14.04 Server

      -

      Ubuntu 16.04 Server

      -

      Ubuntu 18.04 Server

      -

      Ubuntu 20.04 Server

      -

      4.15.0-52-56

      -

      4.4.0-151-178

      -

      4.4.0-104-generic

      -

      4.4.0-141-generic

      -

      4.4.0-142-generic

      -

      4.4.0-145-generic

      -

      4.15.0-34-generic

      -

      4.15.0-45-generic

      -

      4.15.0-47-generic

      +
      • Fedora 35 64bit
      • Fedora 34 64bit
      • Fedora 33 64bit

      EulerOS

      +

      OpenSUSE

      64-bit:

      -

      EulerOS 2.2

      -

      EulerOS 2.3

      -

      EulerOS 2.5

      -

      3.10.0-327.62.59.83.h162.x86_64

      -

      3.10.0-514.44.5.10.h198.x86_64

      -

      3.10.0-327.59.59.46.h38.x86_64

      -

      3.10.0-327.62.59.83.h96.x86_64

      -

      3.10.0-327.62.59.83.h128.x86_64

      -

      3.10.0-514.44.5.10.h121.x86_64

      -

      3.10.0-514.44.5.10.h142.x86_64

      +

      OpenSUSE 15.3 64bit

      Red Hat

      +

      Oracle Linux

      64-bit:

      -

      Red Hat 6

      -

      Red Hat 7

      -

      2.6.32-358.6.2.el6.x86_64

      -

      2.6.32-431.20.3.el6

      -

      2.6.32-504.12.2.el6

      -

      2.6.32-573.el6.x86_64

      -

      2.6.32-696.1.1.el6.x86_64

      -

      2.6.32-696.10.2.el6.x86_64

      -

      2.6.32-754.el6.x86_64

      -

      3.10.0-229.1.2.el7.x86_64

      -

      3.10.0-327.36.1.el7.x86_64

      -

      3.10.0-514.36.1.el7

      -

      3.10.0-514.6.1.el7.x86_64

      -

      3.10.0-693.11.6.el7.x86_64

      -

      3.10.0-862.3.2.el7.x86_64

      +
      • Oracle Linux Server release 8.4 64bit
      • Oracle Linux Server release 7.6 64bit

      SUSE Linux Enterprise

      +

      Red Hat

      64-bit:

      -

      SLES 11

      -

      SLES 12

      -

      3.0.101-108.18-default

      -

      3.12.74-60.64.40-default

      -

      4.4.103-92.53-default

      -

      4.4.120-92.70-default

      -

      4.4.121-92.92

      +

      Red Hat Enterprise Linux 7.9 64bit

      Debian

      +

      SUSE

      64-bit:

      -

      Debian 8

      -

      Debian 9

      -

      4.9.168-1+deb9u3

      -

      3.2.0-4-686-pae

      -

      3.2.0-4-amd64

      -

      3.16.0-4-amd64

      -

      4.9.0-3-amd64

      -

      4.9.0-4-amd64

      -

      4.9.0-8-amd64

      -

      4.9.0-9-amd64

      -

      4.19.0-5-amd64

      +
      • Novell SUSE Linux Enterprise Server 15 SP3 64bit
      • Novell SUSE Linux Enterprise Server 15 SP2 64bit
      • Novell SUSE Linux Enterprise Server 15 SP1 64bit
      • Novell SUSE Linux Enterprise Server 15 64bit
      • Novell SUSE Linux Enterprise Server 12 SP5 64bit
      • Novell SUSE Linux Enterprise Server 12 SP4 64bit
      • Novell SUSE Linux Enterprise Server 12 SP3 64bit

      openSUSE

      +

      SUSE-SAP

      64-bit:

      -

      openSUSE 15.0

      -

      openSUSE 15.1

      -

      4.4.103-18.41-default

      -

      3.0.101-108.18-default

      +
      • Novell SUSE Linux Enterprise Server 15 SP3 64bit
      • Novell SUSE Linux Enterprise Server 15 SP2 64bit
      • Novell SUSE Linux Enterprise Server 15 SP1 64bit
      • Novell SUSE Linux Enterprise Server 15 64bit
      • Novell SUSE Linux Enterprise Server 12 SP5 64bit
      • Novell SUSE Linux Enterprise Server 12 SP4 64bit
      • Novell SUSE Linux Enterprise Server 12 SP3 64bit

      Fedora

      +

      Ubuntu

      64-bit:

      -

      Fedora 2x

      -

      5.1.11-200.fc29.x86_64

      -

      4.5.5-300.fc24.x86_64

      -

      4.20.8-200.fc29.x86_64

      -

      5.2.8-200.fc30.x86_64

      -

      4.8.6-300.fc25.x86_64

      +
      • Ubuntu 20.04 server 64bit
      • Ubuntu 18.04 server 64bit

      openEuler

      +

      Windows

      64-bit:

      -

      openEuler 20.03

      -

      4.19.90-2003.4.0.0036.oel.x86_64

      +
      • Windows Server 2019 Standard 64bit
      • Windows Server 2016 Standard 64bit
      • Windows Server 2012 R2 Standard 64bit
      -
      - @@ -67,7 +67,7 @@ - @@ -75,7 +75,7 @@ @@ -88,6 +88,14 @@ + + +
      Table 3 Supported OS versions-03

      OS

      +
      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      Table 3 Supported OS versions

      OS

      OS Version

      -

      Kernel Version

      +

      Version

      CentOS

      +

      CentOS

      64-bit:

      -

      CentOS 6

      -

      CentOS 7

      -

      CentOS 8

      -

      2.6.32-754.15.3.e16.x86_64

      -

      2.6.32-696.16.1.el6.x86_64

      -

      2.6.32-754.10.1.el6.x86_64

      -

      2.6.32-754.11.1.e16.x86_64

      -

      3.10.0-514.10.2.el7.x86_64

      -

      3.10.0-693.11.1.el7.x86_64

      -

      3.10.0-862.9.1.el7.x86_64

      -

      3.10.0-957.21.3.e17.x86_64

      -

      3.10.0-957.5.1.e17.x86_64

      -

      3.10.0-957.10.1.e17.x86_64

      +
      • CentOS 7.9 64bit
      • CentOS 7.7 64bit

      Ubuntu

      +

      Oracle Linux

      64-bit:

      -

      Ubuntu 14.04 Server

      -

      Ubuntu 16.04 Server

      -

      Ubuntu 18.04 Server

      -

      Ubuntu 20.04 Server

      -

      4.15.0-52-56

      -

      4.4.0-151-178

      -

      4.4.0-104-generic

      -

      4.4.0-141-generic

      -

      4.4.0-142-generic

      -

      4.4.0-145-generic

      -

      4.15.0-34-generic

      -

      4.15.0-45-generic

      -

      4.15.0-47-generic

      +
      • Oracle Linux Server release 8.4 64bit
      • Oracle Linux Server release 7.6 64bit

      EulerOS

      +

      Red Hat

      64-bit:

      -

      EulerOS 2.2

      -

      EulerOS 2.3

      -

      EulerOS 2.5

      -

      EulerOS 2.9

      -

      3.10.0-327.62.59.83.h162.x86_64

      -

      3.10.0-514.44.5.10.h198.x86_64

      -

      3.10.0-327.59.59.46.h38.x86_64

      -

      3.10.0-327.62.59.83.h96.x86_64

      -

      3.10.0-327.62.59.83.h128.x86_64

      -

      3.10.0-514.44.5.10.h121.x86_64

      -

      3.10.0-514.44.5.10.h142.x86_64

      +

      Red Hat Enterprise Linux 7.9 64bit

      Red Hat

      +

      SUSE

      64-bit:

      -

      Red Hat 6

      -

      Red Hat 7

      -

      2.6.32-358.6.2.el6.x86_64

      -

      2.6.32-431.20.3.el6

      -

      2.6.32-504.12.2.el6

      -

      2.6.32-573.el6.x86_64

      -

      2.6.32-696.1.1.el6.x86_64

      -

      2.6.32-696.10.2.el6.x86_64

      -

      2.6.32-754.el6.x86_64

      -

      3.10.0-229.1.2.el7.x86_64

      -

      3.10.0-327.36.1.el7.x86_64

      -

      3.10.0-514.36.1.el7

      -

      3.10.0-514.6.1.el7.x86_64

      -

      3.10.0-693.11.6.el7.x86_64

      -

      3.10.0-862.3.2.el7.x86_64

      -

      SUSE Linux Enterprise

      -

      64-bit:

      -

      SLES 11

      -

      SLES 12

      -

      SLES 15

      -

      3.0.101-108.18-default

      -

      3.12.74-60.64.40-default

      -

      4.4.103-92.53-default

      -

      4.4.120-92.70-default

      -

      4.4.121-92.92

      -

      Debian

      -

      64-bit:

      -

      Debian 8

      -

      Debian 9

      -

      Debian 10

      -

      4.9.168-1+deb9u3

      -

      3.2.0-4-686-pae

      -

      3.2.0-4-amd64

      -

      3.16.0-4-amd64

      -

      4.9.0-3-amd64

      -

      4.9.0-4-amd64

      -

      4.9.0-8-amd64

      -

      4.9.0-9-amd64

      -

      4.19.0-5-amd64

      -

      openSUSE

      -

      64-bit:

      -

      openSUSE 15.0

      -

      openSUSE 15.1

      -

      4.4.103-18.41-default

      -

      3.0.101-108.18-default

      -

      Fedora

      -

      64-bit:

      -

      Fedora 2x

      -

      Fedora 3x

      -

      5.1.11-200.fc29.x86_64

      -

      4.5.5-300.fc24.x86_64

      -

      4.20.8-200.fc29.x86_64

      -

      5.2.8-200.fc30.x86_64

      -

      4.8.6-300.fc25.x86_64

      -

      openEuler

      -

      64-bit:

      -

      openEuler 20.03

      -

      4.19.90-2003.4.0.0036.oel.x86_64

      +
      • 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-04

      OS

      +
      - - - - - - - - - - - - - - + + + + +
      Table 4 Supported OS versions

      OS

      OS Version

      -

      Kernel Version

      +

      OS Version

      CentOS

      +

      Rocky

      64-bit:

      -

      CentOS 7

      -

      3.10.0-514.10.2.el7.x86_64

      -

      3.10.0-693.11.1.el7.x86_64

      -

      3.10.0-862.9.1.el7.x86_64

      -

      3.10.0-957.21.3.e17.x86_64

      -

      3.10.0-957.5.1.e17.x86_64

      -

      3.10.0-957.10.1.e17.x86_64

      +

      Rocky 8 64 bit

      Ubuntu

      +

      CentOS

      64-bit:

      -

      Ubuntu 14.04 Server

      -

      Ubuntu 16.04 Server

      -

      Ubuntu 18.04 Server

      -

      4.4.0-31-generic

      -

      4.4.0-131-generic

      -

      4.4.0-141-generic

      -

      4.4.0-142-generic

      -

      4.15.0-29-generic

      -

      4.15.0-45-generic

      +

      CentOS 7.9 64bit

      SUSE Linux Enterprise

      +

      EulerOS

      64-bit:

      -

      SLES 12

      -

      4.4.103-92.53-default

      -

      4.4.120-92.70-default

      +

      EulerOS 2.5 64bit

      +
      NOTE:

      PI2 ECSs do not support this OS version.

      +

      Debian

      +

      Oracle Linux

      64-bit:

      -

      Debian 8

      -

      Debian 9

      +

      Oracle Linux Server release 7.6 64bit

      3.16.0-7-amd64

      -

      3.16.0-4-amd64

      -

      4.9.0-3-amd64

      +

      Ubuntu

      +
      • Ubuntu 20.04 server 64bit
      • Ubuntu 18.04 server 64bit
      +

      Windows

      +
      • Windows Server 2019 Standard 64bit
      • Windows Server 2016 Standard 64bit
      • Windows Server 2012 R2 Standard 64bit
      - -

      Kunpeng ECSs

      Table 5 lists the OSs supported by the following ECSs:

      -
      • Kunpeng general computing-plus KC1
      • Kunpeng memory-optimized KM1
      -
      + + +
      Table 5 Supported OS versions-05

      OS

      +
      - - - - - - - - - - - - - - - - - - - - - - - -
      Table 5 Supported OS versions

      OS

      OS Version

      +

      OS Version

      CentOS

      +

      CentOS

      64-bit: CentOS 7.6, 7.5, and 7.4

      -

      64-bit: CentOS 8.0

      +

      CentOS 7.9 64bit

      Ubuntu

      +

      Debian

      64-bit: Ubuntu 18.04 Server

      +
      • Debian GNU/Linux 11 64bit
      • Debian GNU/Linux 10 64bit

      EulerOS

      +

      Oracle Linux

      64-bit: EulerOS 2.8

      +

      Oracle Linux Server release 7.6 64bit

      Red Hat

      +

      Ubuntu

      64-bit: Red Hat 7.6 and 7.5

      -

      SUSE Linux Enterprise

      -

      64-bit: SLES 12 SP5 and SP4

      -

      64-bit: SLES 15

      -

      openSUSE

      -

      64-bit: openSUSE Leap 15.0

      -

      Fedora

      -

      64-bit: Fedora 29

      -

      Debian

      -

      64-bit: Debian 10.2.0

      -

      openEuler

      -

      64-bit: openEuler 20.03

      +
      • Ubuntu 20.04 server 64bit
      • Ubuntu 18.04 server 64bit
      -
      Parent topic: Supported OSs
      diff --git a/docs/ims/umn/en-us_topic_0030713143.html b/docs/ims/umn/en-us_topic_0030713143.html index 37961f3c1..a5d26f028 100644 --- a/docs/ims/umn/en-us_topic_0030713143.html +++ b/docs/ims/umn/en-us_topic_0030713143.html @@ -3,10 +3,10 @@

      External Image File Formats and Supported OSs

      External File Formats

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

      -

      Supported OSs

      When you upload an external image file to an OBS bucket on the management console, the OS contained in the image file will be checked. Table 1 lists the OSs supported for external image files.

      +

      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.
      • 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).
      @@ -20,14 +20,16 @@

      Windows 10 64bit

      Windows 7 Enterprise 64bit

      +

      Windows 7 Professional 64bit

      +

      Windows 7 Professional 32bit

      Windows Server 2016 Standard 64bit

      Windows Server 2016 Datacenter 64bit

      Windows Server 2012 R2 Standard 64bit

      -

      Windows Server 2012 Essentials R2 64bit

      +

      Windows Server 2012 R2 Essentials 64bit

      Windows Server 2012 R2 Datacenter 64bit

      Windows Server 2012 Datacenter 64bit

      Windows Server 2012 Standard 64bit

      -

      Windows Server 2008 R2 WEB 64bit

      +

      Windows Server 2008 WEB R2 64bit

      Windows Server 2008 R2 Standard 64bit

      Windows Server 2008 R2 Enterprise 64bit

      Windows Server 2008 R2 Datacenter 64bit

      @@ -38,6 +40,7 @@

      SUSE Linux Enterprise Server 15 SP1 64bit

      SUSE Linux Enterprise Server 15 64bit

      SUSE Linux Enterprise Server 12 SP5 64bit

      +

      SUSE Linux Enterprise Server 12 SP4 64bit

      SUSE Linux Enterprise Server 12 SP3 64bit

      SUSE Linux Enterprise Server 12 SP2 64bit

      SUSE Linux Enterprise Server 12 SP1 64bit

      @@ -150,6 +153,7 @@

      Debian GNU/Linux 10.0.0 64bit

      Debian GNU/Linux 9.3.0 64bit

      Debian GNU/Linux 9.0.0 64bit

      +

      Debian GNU/Linux 8.10.0 64bit

      Debian GNU/Linux 8.8.0 64bit

      Debian GNU/Linux 8.7.0 64bit

      Debian GNU/Linux 8.6.0 64bit

      diff --git a/docs/ims/umn/en-us_topic_0030713149.html b/docs/ims/umn/en-us_topic_0030713149.html index 665d6c4bf..505daa3c8 100644 --- a/docs/ims/umn/en-us_topic_0030713149.html +++ b/docs/ims/umn/en-us_topic_0030713149.html @@ -1,7 +1,7 @@

      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.

      @@ -14,7 +14,7 @@
    • 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. Enable remote desktop connection if needed. For details, see Setting the NIC to DHCP and Enabling Remote Desktop Connection.
      • Install special drivers. The normal running and advanced functions of some ECSs depend on certain drivers. For example, GPU-accelerated ECSs depend on the Tesla and GRID/vGPU drivers. For details, see Installing Special Windows Drivers.
      • Check whether Cloudbase-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 and Configuring Cloudbase-Init.
      • Check and install the PV driver and UVP VMTools driver to ensure that new ECSs created from the image support both KVM and XEN virtualization and to improve network performance.

        For details, see steps 2 to 5 in 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. Enable remote desktop connection if needed. For details, see Setting the NIC to DHCP and Enabling Remote Desktop Connection.
        • Install special drivers. The normal running and advanced functions of some ECSs depend on certain drivers. For example, GPU-accelerated ECSs depend on the Tesla and GRID/vGPU drivers. For details, see Installing Special Windows Drivers.
        • Check whether Cloudbase-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 and Configuring Cloudbase-Init.
        • Check and install the PV driver and UVP VMTools driver to ensure that new ECSs created from the image support both KVM and Xen virtualization and to improve network performance.

          For details, see steps 2 to 5 in Optimization Process.

        • Run Sysprep to ensure that the SIDs of the new ECSs created from the image are unique within their domain. In a cluster deployment scenario, the SIDs must be unique. For details, see Running Sysprep.

        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.

        @@ -60,6 +60,12 @@

      Set a name for the image.

      Enterprise Project

      +

      Select an enterprise project from the drop-down list. This parameter is available only if you have enabled enterprise projects or your account is an enterprise account. To enable this function, contact your customer manager.

      +

      An enterprise project provides central management of cloud resources on a project.

      +

      Tag

      (Optional) Set a tag key and a tag value for the image to make identification and management of your images easier.

      @@ -73,7 +79,7 @@
      -
    • Click Create Now.
    • Confirm the parameters 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 2b5ce0458..3de527f31 100644 --- a/docs/ims/umn/en-us_topic_0030713152.html +++ b/docs/ims/umn/en-us_topic_0030713152.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.

      Procedure

      1. On the ECS, choose Start > Control Panel.
      2. Click Network and Internet Connections.
      3. Click Network and Sharing Center.
        Figure 1 Network and Sharing Center
      4. Select the connection configured with the static IP address. For example, click Local Area Connection 2.
        Figure 2 Local Area Connection 2 Status
        diff --git a/docs/ims/umn/en-us_topic_0030713153.html b/docs/ims/umn/en-us_topic_0030713153.html index 62a8dda5b..32fa9c398 100644 --- a/docs/ims/umn/en-us_topic_0030713153.html +++ b/docs/ims/umn/en-us_topic_0030713153.html @@ -1,7 +1,7 @@ -

        Can I Use the System Disk Image of an ECS on a Physical Server After I Export It from the Cloud Platform?

        -

        No. The system disk image of an ECS is a VM file that contains a system running environment and does not have an installation boot program. Therefore, it cannot be used on a physical server.

        +

        Can I Use the System Disk Image of an ECS on a BMS After I Export It from the Cloud Platform?

        +

        No. The system disk image of an ECS is a VM file that contains a system running environment and does not have an installation boot program. Therefore, it cannot be used on a BMS.

        diff --git a/docs/ims/umn/en-us_topic_0030713155.html b/docs/ims/umn/en-us_topic_0030713155.html index 189c66ccb..39db641f8 100644 --- a/docs/ims/umn/en-us_topic_0030713155.html +++ b/docs/ims/umn/en-us_topic_0030713155.html @@ -6,7 +6,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.

        Procedure

        1. 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.

        2. Choose Start, right-click Computer, and choose Properties from the shortcut menu.
        3. Click Remote settings.
        4. In the Remote tab, select Allow connections from computers running any version of Remote Desktop (less secure).
        5. Click OK.
        6. Choose Start > Control Panel and navigate to Windows Firewall.
        7. Choose Allow a program or feature through Windows Firewall in the left pane.
        8. 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 desktop
          diff --git a/docs/ims/umn/en-us_topic_0030713176.html b/docs/ims/umn/en-us_topic_0030713176.html index d3a16fd29..5b7da33aa 100644 --- a/docs/ims/umn/en-us_topic_0030713176.html +++ b/docs/ims/umn/en-us_topic_0030713176.html @@ -7,17 +7,38 @@

      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

      This section uses Ubuntu 14.04 as an example to describe how to query and configure NIC attributes of an ECS.

      +

      Procedure

      This section uses Ubuntu 16.04 as an example to describe how to query and configure NIC attributes of an ECS.

      1. Run the following command on the ECS to open the /etc/network/interfaces file using the vi editor and query the IP address obtaining mode:

        vi /etc/network/interfaces

        -
        • If DHCP has been configured on all NICs, enter :q to exit the vi editor.
          Figure 1 DHCP IP address obtaining mode
          -
        • If static IP addresses are set on the NICs, go to 2.
          Figure 2 Static IP address obtaining mode
          +
          • If DHCP has been configured on all NICs, enter :q to exit the vi editor.
            auto lo
+iface lo inet loopback
+auto eth0
+iface eth0 inet dhcp
+
+auto eth1
+iface eth1 inet dhcp
            +
          • If static IP addresses are set on the NICs, go to 2.
            auto lo
+iface lo inet loopback
+auto eth0
+#iface eth0 inet dhcp
+iface eth0 inet static
+address 192.168.1.109
+netmask 255.255.255.0
+gateway 192.168.1.1
        • Press i to enter editing mode.
        • Delete the static IP address configuration and configure DHCP for the NICs.

          You can insert a number sign (#) in front of each line of static IP address configuration to comment it out.

          -
          Figure 3 Configuring DHCP on a NIC
          +
          auto lo
+iface lo inet loopback
+auto eth0
+iface eth0 inet dhcp

          If the ECS has multiple NICs, you must configure DHCP for all the NICs.

          -
          Figure 4 Configuring DHCP on multiple NICs
          +
          auto lo
+iface lo inet loopback
+auto eth0
+iface eth0 inet dhcp
+auto eth1
+iface eth1 inet dhcp
        • Press Esc, enter :wq, and press Enter.

          The system saves the configuration and exits the vi editor.

      diff --git a/docs/ims/umn/en-us_topic_0030713180.html b/docs/ims/umn/en-us_topic_0030713180.html index abade2c3b..16b018cd3 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.

      @@ -14,7 +14,7 @@
    • 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 both Xen and 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 Xen and KVM drivers need to be installed.

        For details, see steps 2 to 6 in 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 both Xen and 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 Xen and KVM drivers need to be installed.

          For details, see steps 2 to 6 in 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.

        @@ -60,6 +60,12 @@

      Set a name for the image.

      Enterprise Project

      +

      Select an enterprise project from the drop-down list. This parameter is available only if you have enabled enterprise projects or your account is an enterprise account. To enable this function, contact your customer manager.

      +

      An enterprise project provides central management of cloud resources on a project.

      +

      Tag

      (Optional) Set a tag key and a tag value for the image to make identification and management of your images easier.

      @@ -73,7 +79,7 @@
      -
    • Click Create Now.
    • Confirm the parameters 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 519e7bcb9..b7f0a386d 100644 --- a/docs/ims/umn/en-us_topic_0030713183.html +++ b/docs/ims/umn/en-us_topic_0030713183.html @@ -1,8 +1,8 @@

      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.

      -
      • 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.
      +

      You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.

      +
      • 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 need also 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.
      diff --git a/docs/ims/umn/en-us_topic_0030713184.html b/docs/ims/umn/en-us_topic_0030713184.html index 65199bd7a..226d2d459 100644 --- a/docs/ims/umn/en-us_topic_0030713184.html +++ b/docs/ims/umn/en-us_topic_0030713184.html @@ -53,8 +53,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. Ensure that this value is at least equal to the system disk size in the image file.

      +

      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?

      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 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.

      A maximum of three data disks can be added.

      (Optional) If you want to encrypt the image, select KMS encryption and select the key to be used from the key list. After you select KMS encryption, the system will create a default master private key ims/default for you. You can also select a private key from the private key list.

      For how to encrypt an image, see Creating Encrypted Images.

      +
      NOTE:

      If the encrypted image needs to be shared with other tenants, use a custom key to encrypt it. Otherwise, the key cannot be authorized to other tenants, causing the sharing failure.

      +
      +

      Enterprise Project

      +

      Select an enterprise project from the drop-down list. This parameter is available only if you have enabled enterprise projects or your account is an enterprise account.

      +

      An enterprise project provides central management of cloud resources on a project by project basis.

      Tag

      diff --git a/docs/ims/umn/en-us_topic_0030713185.html b/docs/ims/umn/en-us_topic_0030713185.html index a11569174..5bf3d0394 100644 --- a/docs/ims/umn/en-us_topic_0030713185.html +++ b/docs/ims/umn/en-us_topic_0030713185.html @@ -2,7 +2,7 @@

      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 XEN Guest OS driver (PV driver) or KVM Guest OS driver (UVP VMTools). If no such a driver is installed, the performance of ECSs will be affected and some functions will be unavailable. Ensure that the PV driver or UVP VMTools has been installed for the image file as needed before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.

      +

      The proper running of ECSs depends on the Xen Guest OS driver (PV driver) andKVM 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.

      Figure 1 Image creation process
      @@ -12,14 +12,14 @@

      Step 3: Create an ECS

      1. Access the IMS console.
        1. Log in to the management console.
        2. Under Compute, click Image Management Service.

          The IMS console is displayed.

        -
      2. Click the Private Images tab.
      3. Locate the row that contains the private image and click Apply for Server in the Operation column.
      4. 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.

        -
      5. Perform the following steps to check whether the private image has been pre-configured:
        1. 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.
        2. 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.
        3. Check whether NICs are set to DHCP by referring to 2 in Step 4: Configure the ECS.
        4. 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.
        +
      6. Click the Private Images tab.
      7. Locate the row that contains the private image and click Apply for Server in the Operation column.
      8. 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.

        +
      9. Perform the following steps to check whether the private image has been pre-configured:
        1. 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.
        2. 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.
        3. Check whether NICs are set to DHCP by referring to 2 in Step 4: Configure the ECS.
        4. 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.

      -
      1. Log in to the ECS.
      2. 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.
      3. Enable remote desktop connection for the ECS as needed. For details, see Enabling Remote Desktop Connection.
      4. (Optional) Configure value-added functions. +
        1. Log in to the ECS.
        2. 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.
        3. Enable remote desktop connection for the ECS as needed. For details about how to enable this function, see Enabling Remote Desktop Connection.
        4. (Optional) Configure value-added functions.

      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_0030713186.html b/docs/ims/umn/en-us_topic_0030713186.html index e2245edf0..abbd454d7 100644 --- a/docs/ims/umn/en-us_topic_0030713186.html +++ b/docs/ims/umn/en-us_topic_0030713186.html @@ -1,10 +1,10 @@

      Can I Download a Public Image to My Local PC?

      -

      Currently, you cannot directly download a public image. You can use the public image to create an ECS, use the ECS to create a private image, export the private image to your OBS bucket, and download the private image to your local PC.

      +

      Currently, you cannot directly download a public image. You can use the public image to create an ECS, use the ECS to create a private image, export the private image to your OBS bucket, and download the private image to your local PC.

      Helpful links:

      -

      Windows and SUSE Linux public images and the private images created from these public images cannot be exported.

      +
      • Windows, SUSE, Red Hat, Ubuntu, and Oracle Linux public images and the private images created from these public images cannot be exported.
      • However, if a Windows, SUSE, Red Hat, Ubuntu, or Oracle Linux private image is created from an external image file, this private image can be exported.
      diff --git a/docs/ims/umn/en-us_topic_0030713188.html b/docs/ims/umn/en-us_topic_0030713188.html index 2c7120ba9..841f933c3 100644 --- a/docs/ims/umn/en-us_topic_0030713188.html +++ b/docs/ims/umn/en-us_topic_0030713188.html @@ -4,9 +4,11 @@

      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.
      +
      • 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.
      +
      +

      Follow-up Procedure

      After a system disk image is created, you can use it to change the OS of an ECS.

      diff --git a/docs/ims/umn/en-us_topic_0030713189.html b/docs/ims/umn/en-us_topic_0030713189.html index 4c69d189f..c86fec41f 100644 --- a/docs/ims/umn/en-us_topic_0030713189.html +++ b/docs/ims/umn/en-us_topic_0030713189.html @@ -2,7 +2,7 @@

      Preparing an Image File

      You need to prepare an image file that meets the platform requirements.

      -
      +
      @@ -52,7 +52,7 @@ - diff --git a/docs/ims/umn/en-us_topic_0030713192.html b/docs/ims/umn/en-us_topic_0030713192.html index 4af7f84c6..b6997cfe4 100644 --- a/docs/ims/umn/en-us_topic_0030713192.html +++ b/docs/ims/umn/en-us_topic_0030713192.html @@ -1,8 +1,8 @@

      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.

      -
      • 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.
      +

      You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.

      +
      • 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 need also 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.
      diff --git a/docs/ims/umn/en-us_topic_0030713193.html b/docs/ims/umn/en-us_topic_0030713193.html index 6df34d291..5a799a91c 100644 --- a/docs/ims/umn/en-us_topic_0030713193.html +++ b/docs/ims/umn/en-us_topic_0030713193.html @@ -53,8 +53,8 @@
      - @@ -67,7 +67,7 @@ - @@ -75,7 +75,7 @@ @@ -88,6 +88,14 @@ + + +
      Table 1 Windows image file requirements

      Image File Property

      @@ -14,7 +14,7 @@

      OS
      • Windows Server 2008, Windows Server 2012, Windows Server 2016
      • 32-bit or 64-bit
      • The OS cannot be bound to specific hardware.
      • The OS must support full virtualization.
      -

      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 Guest OS driver. On the image registration page, select Other Windows. 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 the Guest OS driver. On the image registration page, select Other Windows. After the image is imported, whether the system is started depends on the driver integrity.

      Image format

      @@ -25,7 +25,7 @@

      Image size

      Maximum file size: 128 GB

      -
      If the image size is between 128 GB and 1 TB, convert the image file into the RAW or ZVHD2 format and import the image using fast import. +
      If the image size is between 128 GB and 1 TB, convert the image file into the RAW or ZVHD2 format and import the image using fast import.

      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 [1 GB, 1024 GB].
      • 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 an 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" in Image Service Management User Guide.
      • 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 size must be [1 GB, 1024 GB].
      • 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.

      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. Ensure that this value is at least equal to the system disk size in the image file.

      +

      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?

      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 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.

      A maximum of three data disks can be added.

      (Optional) If you want to encrypt the image, select KMS encryption and select the key to be used from the key list. After you select KMS encryption, the system will create a default master private key ims/default for you. You can also select a private key from the private key list.

      For how to encrypt an image, see Creating Encrypted Images.

      +
      NOTE:

      If the encrypted image needs to be shared with other tenants, use a custom key to encrypt it. Otherwise, the key cannot be authorized to other tenants, causing the sharing failure.

      +
      +

      Enterprise Project

      +

      Select an enterprise project from the drop-down list. This parameter is available only if you have enabled enterprise projects or your account is an enterprise account.

      +

      An enterprise project provides central management of cloud resources on a project by project basis.

      Tag

      diff --git a/docs/ims/umn/en-us_topic_0030713197.html b/docs/ims/umn/en-us_topic_0030713197.html index 04b2a14fe..48ae7f59b 100644 --- a/docs/ims/umn/en-us_topic_0030713197.html +++ b/docs/ims/umn/en-us_topic_0030713197.html @@ -4,9 +4,11 @@

      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.
      +
      • 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.
      +
      +

      Follow-up Procedure

      After a system disk image is created, you can use it to change the OS of an ECS.

      diff --git a/docs/ims/umn/en-us_topic_0030713198.html b/docs/ims/umn/en-us_topic_0030713198.html index ccf4d106e..826662f7c 100644 --- a/docs/ims/umn/en-us_topic_0030713198.html +++ b/docs/ims/umn/en-us_topic_0030713198.html @@ -2,7 +2,7 @@

      Preparing an Image File

      You need to prepare an image file that meets the platform requirements.

      -
      +
      @@ -57,7 +57,7 @@ - diff --git a/docs/ims/umn/en-us_topic_0030713199.html b/docs/ims/umn/en-us_topic_0030713199.html index 2c1fbd18d..c6d383f67 100644 --- a/docs/ims/umn/en-us_topic_0030713199.html +++ b/docs/ims/umn/en-us_topic_0030713199.html @@ -10,7 +10,8 @@

      Procedure

      Use any of the following methods to modify an image:

      Method 1:
      1. Access the IMS console.
        1. Log in to the management console.
        2. Under Compute, click Image Management Service.

          The IMS console is displayed.

        -
      2. Click the Private Images tab to display the image list.
      3. Locate the row that contains the image and click Modify in the Operation column.
      4. In the Modify Image dialog box, modify the image.
      +
    • 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.

      +
      • Method 2:
      1. Access the IMS console.
        1. Log in to the management console.
        2. Under Compute, click Image Management Service.

          The IMS console is displayed.

        diff --git a/docs/ims/umn/en-us_topic_0030713200.html b/docs/ims/umn/en-us_topic_0030713200.html index 692bb63d7..9679e2824 100644 --- a/docs/ims/umn/en-us_topic_0030713200.html +++ b/docs/ims/umn/en-us_topic_0030713200.html @@ -2,11 +2,13 @@

        Creating an ECS from an Image

        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 pre-installed public applications. You need to install applications as needed.
        • If you use a private or shared image, the created ECS contains an OS, pre-installed public applications, and a user's personal applications.
        +
        • 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

        1. Access the IMS console.
          1. Log in to the management console.
          2. Under Compute, click Image Management Service.

            The IMS console is displayed.

          -
        2. Click the Public Images, Private Images, or Images Shared with Me tab to display the image list.
        3. Locate the row that contains your desired image and click Apply for Server in the Operation column.
        4. 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.

          +
        5. Click the Public Images, Private Images, or Images Shared with Me tab to display the image list.
        6. Locate the row that contains your desired image and click Apply for Server in the Operation column.
        7. 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.

          +

          If a full-ECS image contains multiple data disks, it takes some time to load and display the disk information.

          +
        diff --git a/docs/ims/umn/en-us_topic_0030713201.html b/docs/ims/umn/en-us_topic_0030713201.html index 8c8d1b1a8..7cab28ead 100644 --- a/docs/ims/umn/en-us_topic_0030713201.html +++ b/docs/ims/umn/en-us_topic_0030713201.html @@ -8,9 +8,9 @@
      2. Click the Private Images tab to display the image list.
      3. Locate the row that contains the image, choose More > Delete in the Operation column.

        To delete multiple images:

        1. Select the images you want to delete in the image list.
        2. Click Delete above the image list.
        -
      4. (Optional) Select Delete CSBS 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 backups of the full-ECS images.

        -

        If CSBS 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.

        +
      5. (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.

        +

        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.

      6. Click Yes.
      diff --git a/docs/ims/umn/en-us_topic_0030713202.html b/docs/ims/umn/en-us_topic_0030713202.html index ff78db8f9..118f7ab5c 100644 --- a/docs/ims/umn/en-us_topic_0030713202.html +++ b/docs/ims/umn/en-us_topic_0030713202.html @@ -20,6 +20,8 @@
    • Image Encryption
      • +
    • Accounts and Permissions
      +
    • Cloud-Init
    • ECS Creation
      diff --git a/docs/ims/umn/en-us_topic_0030713203.html b/docs/ims/umn/en-us_topic_0030713203.html index 8c9ed8e7e..bbcd0072b 100644 --- a/docs/ims/umn/en-us_topic_0030713203.html +++ b/docs/ims/umn/en-us_topic_0030713203.html @@ -6,6 +6,8 @@ diff --git a/docs/ims/umn/en-us_topic_0030713211.html b/docs/ims/umn/en-us_topic_0030713211.html index 7bee12765..2342f26b1 100644 --- a/docs/ims/umn/en-us_topic_0030713211.html +++ b/docs/ims/umn/en-us_topic_0030713211.html @@ -3,7 +3,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 Xen or 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 Xen or KVM driver has been installed for the image file as needed before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.

      -

      For details, see How Do I Install Native Xen and KVM Drivers?

      +

      For details, see How Do I Install the Native Xen and KVM Drivers?

      Figure 1 Image creation process

      Step 1: Upload the Image File

      Upload the external image file to an OBS bucket. For details, see Uploading an External Image File.

      @@ -13,19 +13,19 @@

      Step 3: Create an ECS

      Create an ECS from the private image.

      1. Access the IMS console.
        1. Log in to the management console.
        2. Under Compute, click Image Management Service.

          The IMS console is displayed.

        -
      2. Click the Private Images tab.
      3. Locate the row that contains the private image and click Apply for Server in the Operation column.
      4. 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.

        -
      5. Perform the following steps to check whether the private image has been pre-configured:
        1. Check whether the ECS can be successfully started. If the start succeeds, the Xen or 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 Xen or KVM driver as needed for the image file and start from Step 1: Upload the Image File again.
        2. 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.
        3. Check the network configuration by referring to Step 4: Configure the ECS.
        +
      6. Click the Private Images tab.
      7. Locate the row that contains the private image and click Apply for Server in the Operation column.
      8. 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.

        +
      9. Perform the following steps to check whether the private image has been pre-configured:
        1. Check whether the ECS can be successfully started. If the start succeeds, the Xen or 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 Xen or KVM driver as needed for the image file and start from Step 1: Upload the Image File again.
        2. 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.
        3. 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.

      Step 4: Configure the ECS

      Remotely log in to the ECS created in Step 3: Create an ECS to configure it.

      -
      1. Log in to the ECS.
      2. 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.
        +
        1. Log in to the ECS.
        2. 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.
        3. Configure a file system.
        4. (Optional) Configure value-added functions.
      -

      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.

      diff --git a/docs/ims/umn/en-us_topic_0030713219.html b/docs/ims/umn/en-us_topic_0030713219.html index 683ae6288..eb92fea86 100644 --- a/docs/ims/umn/en-us_topic_0030713219.html +++ b/docs/ims/umn/en-us_topic_0030713219.html @@ -7,7 +7,7 @@

      Solution

      Perform the following operations to modify OS kernel boot parameters:

      These operations must be performed after the OS starts. You are advised to modify kernel boot parameters in the ECS used for creating the image.

      -
      1. Run the following command to log in to the OS:
        lsinitrd /boot/initramfs-`uname -r`.img |grep -i xen
        • If the command output contains xen-blkfront.ko, contact the customer service.
        • If no command output is displayed, go to 2.
        +
        1. Run the following command to log in to the OS:
          lsinitrd /boot/initramfs-`uname -r`.img |grep -i xen
          • If the command output contains xen-blkfront.ko, contact the customer service.
          • If no command output is displayed, go to 2.
        2. Back up the GRUB configuration file.

        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

        1. On the Windows Start menu, choose Control Panel > Programs > Programs and Features and check whether Cloudbase-Init is installed. +

          Install Cloudbase-Init

          1. 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.
          2. Check whether the version of the OS is Windows desktop.
            • If yes, go to 3.
            • If the OS is Windows Server, go to 4.
          3. Enable the administrator account (Windows 7 is used as an example).
            1. Click Start and choose Control Panel > System and Security > Administrative Tools.
            2. Double-click Computer Management.
            3. Choose System Tools > Local Users and Groups > Users.
            4. Right-click Administrator and select Properties.
            5. Deselect Account is disabled.
          4. Download the Cloudbase-Init installation package.

            Download the Cloudbase-Init installation package of the appropriate version based on the OS architecture from the Cloudbase-Init official website (http://www.cloudbase.it/cloud-init-for-windows-instances/).

            -

            Cloudbase-Init has two versions: stable and beta.

            To obtain the stable version, visit the following paths:

            -

            To obtain the beta version, visit the following paths:

            -
          5. Double-click the Cloudbase-Init installation package.
          6. Click Next.
          7. Select I accept the terms in the License Agreement and click Next.
          8. Retain the default path and click Next.
          9. 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
            -
          10. Click Next.
          11. Click Install.
          12. In the Files in Use dialog box, select Close the application and attempt to restart them and click OK.
          13. Check whether the version of the OS is Windows desktop.
            • If yes, go to 15.
            • If no, go to 14.
            -
          14. In the Completed the Cloudbase-Init Setup Wizard window, ensure that neither option is selected.
            Figure 2 Completing the Cloudbase-Init installation
            +
            Figure 1 Configuring parameters
            +
          15. Click Next.
          16. Click Install.
          17. In the Files in Use dialog box, select Close the application and attempt to restart them and click OK.
          18. Check whether the version of the OS is Windows desktop.
            • If yes, go to 15.
            • If no, go to 14.
            +
          19. In the Completed the Cloudbase-Init Setup Wizard window, ensure that neither option is selected.
            Figure 2 Completing the Cloudbase-Init installation

            The version number shown in the figure is for reference only.

          20. Click Finish.
          diff --git a/docs/ims/umn/en-us_topic_0030730603.html b/docs/ims/umn/en-us_topic_0030730603.html index 4d223ea99..7fe8916ab 100644 --- a/docs/ims/umn/en-us_topic_0030730603.html +++ b/docs/ims/umn/en-us_topic_0030730603.html @@ -12,9 +12,11 @@

          Check Whether Cloud-Init Has Been Installed

          Perform the operations provided here to check whether Cloud-Init has been installed.

          The methods of checking whether Cloud-Init is installed vary depending on the OSs. Take CentOS 6 as an example. Run the following command to check whether Cloud-Init is installed:

          -

          rpm -qa |grep cloud-init

          -

          If information similar to the following is displayed, Cloud-Init has been installed:

          -
          cloud-init-0.7.5-10.el6.centos.2.x86_64
          +

          which cloud-init

          +
          • If information similar to the following is displayed, Cloud-Init has been installed:
            cloud-init-0.7.5-10.el6.centos.2.x86_64
            +
          • If no information is returned, Cloud-Init is not installed.

            To confirm Cloud-Init is really not installed, you are advised to run rpm -qa |grep cloud-init to check again. If either of which cloud-init and rpm -qa |grep cloud-init shows that Cloud-Init has been installed, Cloud-Init is installed.

            +
            +
          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

              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

              @@ -29,12 +31,13 @@

              (Recommended) Install Cloud-Init Using the Official Installation Package

              The method of installing Cloud-Init on an ECS varies depending on the OS. Perform the installation operations as user root.

              The following describes how to install Cloud-Init on an ECS running SUSE Linux, CentOS, Fedora, Debian, and Ubuntu. For other OS types, install the required type of Cloud-Init. For example, you need to install coreos-cloudinit on ECSs running CoreOS.

              • SUSE Linux

                Paths for obtaining the Cloud-Init installation package for SUSE Linux

                -

                http://ftp5.gwdg.de/pub/opensuse/repositories/Cloud:/Tools/

                +

                http://download.opensuse.org/repositories/home:/garloff:/OTC:/cloudinit/

                +

                https://ftp5.gwdg.de/pub/opensuse/repositories/Cloud:/Tools/

                http://download.opensuse.org/repositories/Cloud:/Tools/

                Select the required repo installation package in the provided paths.

                Take SUSE Enterprise Linux Server 12 as an example. Perform the following steps to install Cloud-Init:

                -
                1. Log in to the ECS used to create a Linux private image.
                2. Run the following command to install the network installation source for SUSE Enterprise Linux Server 12:

                  zypper ar http://ftp5.gwdg.de/pub/opensuse/repositories/Cloud:/Tools/SLE_12_SP3/Cloud:Tools.repo

                  +
                  1. Log in to the ECS used to create a Linux private image.
                  2. Run the following command to install the network installation source for SUSE Enterprise Linux Server 12:

                    zypper ar https://ftp5.gwdg.de/pub/opensuse/repositories/Cloud:/Tools/SLE_12_SP3/Cloud:Tools.repo

                  3. Run the following command to update the network installation source:

                    zypper refresh

                  4. Run the following command to install Cloud-Init:

                    zypper install cloud-init

                  5. Run the following commands to enable Cloud-Init to automatically start upon system boot:
                    • SUSE 11

                      chkconfig cloud-init-local on; chkconfig cloud-init on; chkconfig cloud-config on; chkconfig cloud-final on

                      @@ -47,48 +50,57 @@
                    • Change the value of DHCLIENT_SET_HOSTNAME in the dhcp file to no.
        -
      2. CentOS

        Table 1 lists the Cloud-Init installation paths for CentOS. Select the required installation package from the following addresses.

        - -
      • Table 1 Linux image file requirements

      Image File Property

      @@ -14,7 +14,7 @@

      OS
      • 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.
      -

      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 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.

      Image format

      @@ -25,7 +25,7 @@

      Image size

      Maximum file size: 128 GB

      -
      If the image size is between 128 GB and 1 TB, convert the image file into the RAW or ZVHD2 format and import the image using fast import. +
      If the image size is between 128 GB and 1 TB, convert the image file into the RAW or ZVHD2 format and import the image using fast import.

      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 [1 GB, 1024 GB].
      • 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 size must be [1 GB, 1024 GB].
      • 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.
      Table 1 Cloud-Init installation package addresses

      OS Type

      +
    • 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

      Version

      +

      Version

      How to Obtain

      +

      How to Obtain

      CentOS

      +

      CentOS

      6 32-bit

      +

      6 32-bit

      https://archives.fedoraproject.org/pub/archive/epel/6/i386/

      +

      https://archives.fedoraproject.org/pub/archive/epel/6/i386/

      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/

      +

      https://archives.fedoraproject.org/pub/epel/7/x86_64/Packages/e/
      -

      Run the following commands to install Cloud-Init on an ECS running CentOS 6.5 64-bit (example):

      -

      yum install https://archives.fedoraproject.org/pub/archive/epel/6/x86_64/epel-release-xx-xx.noarch.rpm

      -

      yum install cloud-init

      -

      xx-xx indicates the version of Extra Packages for Enterprise Linux (EPEL) required by the current OS.

      +
      +
      1. Run the following commands to install Cloud-Init:

        yum install Cloud-Init installation package address/epel-release-x-y.noarch.rpm

        +

        yum install cloud-init

        +

        Cloud-Init installation package address indicates the address of the Cloud-Init epel-release installation package, and x-y indicates the version of the Cloud-Init epel-release required by the current OS. Replace them with the actual values according to Table 1.

        +
        • Take CentOS 6 64-bit as an example. If the version is 6.8, the command is as follows:

          yum install https://archives.fedoraproject.org/pub/archive/epel/6/x86_64/epel-release-6-8.noarch.rpm

          +
        • Take CentOS 7 64-bit as an example. If the version is 7.14, the command is as follows:

          yum install https://archives.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-release-7-14.noarch.rpm

          +
        +
      2. 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

        +
    • Fedora

      Before installing Cloud-Init, ensure that the network installation source address has been configured for the OS by checking whether the /etc/yum.repo.d/fedora.repo 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 Fedora official website.

      -

      Run the following command to install Cloud-Init:

      -

      yum install cloud-init

      -
    • 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 update

      +
      1. Run the following command to install Cloud-Init:

        yum install cloud-init

        +
      2. 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.

      +
      1. Run the following commands to install Cloud-Init:

        apt-get update

        apt-get install cloud-init

        +
      2. 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

        +

      • Install Cloud-Init Using the Official Source Code Package and pip

      The following operations use Cloud-Init 0.7.9 as an example to describe how to install Cloud-Init.

      @@ -103,6 +115,8 @@ trusted-host = <$mirror>

      Public network PyPI source: https://pypi.python.org/

    • Run the following command to install the downloaded Cloud-Init source code package (select --upgrade as needed during installation):

      pip install [--upgrade] /home/cloud-init-0.7.9.tar.gz

      +

      For details about how to install a Cloud-Init source code package, see Cloud-Init Documentation

      +
    • Run the cloud-init -v command. Cloud-Init is installed successfully if the following information is displayed:
      cloud-init 0.7.9
    • Enable Cloud-Init to automatically start upon system boot.
      • If the OS uses SysVinit to manage automatic start of services, run the following commands:

        chkconfig --add cloud-init-local; chkconfig --add cloud-init; chkconfig --add cloud-config; chkconfig --add cloud-final

        chkconfig cloud-init-local on; chkconfig cloud-init on; chkconfig cloud-config on; chkconfig cloud-final on

        diff --git a/docs/ims/umn/en-us_topic_0032042416.html b/docs/ims/umn/en-us_topic_0032042416.html index 41969a91c..2db649dc2 100644 --- a/docs/ims/umn/en-us_topic_0032042416.html +++ b/docs/ims/umn/en-us_topic_0032042416.html @@ -22,6 +22,8 @@
      • Deleting Image Recipients Who Can Use Shared Images
        • +
      • Replicating a Shared Image
        +
      diff --git a/docs/ims/umn/en-us_topic_0032042417.html b/docs/ims/umn/en-us_topic_0032042417.html index eae05838a..ada1bd02d 100644 --- a/docs/ims/umn/en-us_topic_0032042417.html +++ b/docs/ims/umn/en-us_topic_0032042417.html @@ -2,13 +2,13 @@

      Overview

      You can share your private images with other tenants. The tenants who accept the shared images can use the images to create ECSs of the same specifications.

      -

      Constraints

      • You can share images only within the region where they reside.
      • Each image can be shared with a maximum of 128 tenants.
      • Encrypted images cannot be shared.
      • Only full-ECS images created from CBR backups can be shared. Other full-ECS images cannot be shared.
      +

      Constraints

      • You can share images only within the region where they reside.
      • A system disk image or data disk image can be shared with up to 256 tenants, and a full-ECS image can be shared with no more than 10 tenants.
      • If an encrypted image needs to be shared with other tenants, the key of the image must be a custom key instead of the default key ims/default.
      • Only full-ECS images created from CBR backups can be shared. Other full-ECS images cannot be shared.

      Procedure

      If you want to share a private image with another tenant, the procedure is as follows:

      1. You obtain the project ID from the tenant.
      2. You share an image with the tenant.
      3. The tenant accepts the shared image.

        After accepting the image, the tenant can use it to create ECSs.

      -

      Related FAQs

      If you have any questions, see Image Sharing FAQs.

      +

      Related FAQs

      If you have any questions, see Image Sharing FAQs.

      diff --git a/docs/ims/umn/en-us_topic_0032042418.html b/docs/ims/umn/en-us_topic_0032042418.html index 18cf5282a..ea5cdbb41 100644 --- a/docs/ims/umn/en-us_topic_0032042418.html +++ b/docs/ims/umn/en-us_topic_0032042418.html @@ -6,7 +6,7 @@

      Procedure

      1. Access the IMS console.
        1. Log in to the management console.
        2. Under Compute, click Image Management Service.

          The IMS console is displayed.

      2. 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.

        -
        Figure 1 Viewing the project ID
        +
        Figure 1 Viewing the project ID
      diff --git a/docs/ims/umn/en-us_topic_0032042419.html b/docs/ims/umn/en-us_topic_0032042419.html index 4506083a1..6519c7997 100644 --- a/docs/ims/umn/en-us_topic_0032042419.html +++ b/docs/ims/umn/en-us_topic_0032042419.html @@ -3,23 +3,24 @@

      Sharing Specified Images

      Scenarios

      After obtaining the project ID from a tenant, you can share specified private images with the tenant. You can share a single image or multiple images as needed.

      -

      Prerequisites

      • 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.
      +

      Prerequisites

      • You have obtained the project ID from the target tenant.
      • 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?
      +
      • Before sharing an image, ensure that any sensitive data has been deleted from the image.

      Procedure

      • Share multiple images.
        1. Access the IMS console.
          1. Log in to the management console.
          2. Under Compute, click Image Management Service.

            The IMS console is displayed.

        2. Click the Private Images tab.
        3. Select the private images to share and click Share above the image list.
        4. 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 enter a maximum of 100 project IDs at a time.
          • You can share images only within the region where they reside.
        5. Click OK.
      • Share a single image.
        1. Access the IMS console.
          1. Log in to the management console.
          2. Under Compute, click Image Management Service.

            The IMS console is displayed.

        2. Click the Private Images tab.
        3. 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.
        4. 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 enter a maximum of 100 project IDs at a time.
          • You can share images only within the region where they reside.
        5. 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.

      +

      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 0af7c56b6..a640ac8e9 100644 --- a/docs/ims/umn/en-us_topic_0032042420.html +++ b/docs/ims/umn/en-us_topic_0032042420.html @@ -15,13 +15,18 @@
    • (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.

      -

      For more information about server backup vaults, see Cloud Backup and Recovery User Guide.

      +

      For more information about server backup vaults, see Cloud Backup and Recovery User Guide.

      • Results

      • Pending: If you do not immediately accept or reject a shared image, the image is in the Pending state.

        A pending shared image is not displayed in the shared image list.

      • 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.
      +

      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.
      +

      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.

      +
      diff --git a/docs/ims/umn/en-us_topic_0032042421.html b/docs/ims/umn/en-us_topic_0032042421.html index d0b2183fb..6d1a4bd26 100644 --- a/docs/ims/umn/en-us_topic_0032042421.html +++ b/docs/ims/umn/en-us_topic_0032042421.html @@ -8,7 +8,7 @@

      Procedure

      1. Access the IMS console.
        1. Log in to the management console.
        2. Under Compute, click Image Management Service.

          The IMS console is displayed.

        -
      2. Click the Images Shared with Me tab.
      3. 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.
        +
      4. Click the Images Shared with Me tab.
      5. 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 choose More > Reject in the Operation column. In the displayed dialog box, click Yes.
      diff --git a/docs/ims/umn/en-us_topic_0032042423.html b/docs/ims/umn/en-us_topic_0032042423.html index 2d7fa1c7d..cde642aeb 100644 --- a/docs/ims/umn/en-us_topic_0032042423.html +++ b/docs/ims/umn/en-us_topic_0032042423.html @@ -8,6 +8,8 @@

      Procedure

      1. Access the IMS console.
        1. Log in to the management console.
        2. Under Compute, click Image Management Service.

          The IMS console is displayed.

      2. Click the Private Images tab.
      3. Click the image name to view image details.
      4. Click Add Tenant.
      5. 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.
        +
      diff --git a/docs/ims/umn/en-us_topic_0034011241.html b/docs/ims/umn/en-us_topic_0034011241.html index 2cc27644b..b6fb5bbd9 100644 --- a/docs/ims/umn/en-us_topic_0034011241.html +++ b/docs/ims/umn/en-us_topic_0034011241.html @@ -4,19 +4,19 @@

      Scenarios

      You can export a private image to a standard OBS bucket and then download it to your local PC.

      Background

      • You can reproduce cloud servers and their running environments in on-promises clusters or private clouds by exporting their images from the cloud platform. The following figure shows the process of exporting an image.
        Figure 1 Exporting an image
        -
      • The time required for exporting an image depends on the image size and the number of concurrent export tasks.
      • You can export images in QCOW2, VMDK, VHD, or ZVHD format. Images exported in different formats may vary in size.
      • If an image is greater than 128 GB, you can select Enable for Fast Export when exporting the image to an OBS bucket. In this case, you cannot specify the format of the exported image. You can convert the image format after it is exported.

        Fast Export is unavailable for encrypted images.

        +
      • The time required for exporting an image depends on the image size and the number of concurrent export tasks.
      • You can export images in QCOW2, VMDK, VHD, or ZVHD format. Images exported in different formats may vary in size.
      • If an image is greater than 128 GB, you can select Enable for Fast Export when exporting the image to an OBS bucket. In this case, you cannot specify the format of the exported image. You can convert the image format after it is exported.

        Fast Export is unavailable for encrypted images. To export an encrypted image, decrypt it first.

      -

      Constraints

      • The following private images cannot be exported:
        • Full-ECS images
        • Private images created from a Windows or SUSE public image
        +

        Constraints

        • The following private images cannot be exported:
          • Full-ECS 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.

        +

        If no OBS bucket is available, create one by referring to Object Storage Service User Guide. Select Standard for Storage Class.

        Procedure

        1. Access the IMS console.
          1. Log in to the management console.
          2. Under Compute, click Image Management Service.

            The IMS console is displayed.

          -
        2. Locate the row that contains the image to be exported, click More in the Operation column and select Export.
        3. 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.
          • Click OK.

            You can view the image export progress above the private image list.

            diff --git a/docs/ims/umn/en-us_topic_0037352059.html b/docs/ims/umn/en-us_topic_0037352059.html index fbcc1ff82..4a70dfc07 100644 --- a/docs/ims/umn/en-us_topic_0037352059.html +++ b/docs/ims/umn/en-us_topic_0037352059.html @@ -1,9 +1,9 @@

            Obtaining Required Software Packages

            -

            PV Driver

            Table 1 lists the PV driver software packages required for optimizing Windows private images.

            +

            PV Driver

            Table 1 lists the PV driver software packages required for optimizing Windows private images.

            -
            Table 1 PV driver software packages

            Software Package

            +
            @@ -57,11 +57,11 @@
            Table 1 PV driver software packages

            Software Package

            OS

            -

            UVP VMTools

            Table 2 lists the UVP VMTools software packages required for optimizing Windows private images.

            +

            UVP VMTools

            Table 2 lists the UVP VMTools software packages required for optimizing Windows private images.

            -
            Table 2 UVP VMTools software packages

            Software Package

            +
            - diff --git a/docs/ims/umn/en-us_topic_0037352061.html b/docs/ims/umn/en-us_topic_0037352061.html index 676692703..9fa3b828d 100644 --- a/docs/ims/umn/en-us_topic_0037352061.html +++ b/docs/ims/umn/en-us_topic_0037352061.html @@ -1,7 +1,7 @@

            Installing UVP VMTools

            -

            Scenarios

            Before using an ECS or external image file to create a private image, ensure that UVP VMTools has been installed in the OS to enable subsequently created ECSs to support KVM virtualization and improve network performance.

            +

            Scenarios

            This section only applies to KVM ECSs, which will replace Xen ECSs gradually. Before using an ECS or external image file to create a private image, ensure that UVP VMTools has been installed in the OS to enable subsequently created ECSs to support KVM virtualization and improve network performance.

            If you do not install UVP VMTools, NICs of the ECS may not be detected and the ECS cannot communicate with other resources.

            UVP VMTools has been installed by default when you use a public image to create ECSs. You can perform the following operations to verify the installation:

            @@ -13,12 +13,14 @@

            Installing UVP VMTools

            The following operations describe how to install UVP VMTools. vmtools-WIN2008R2-x64.exe extracted from vmtools-WIN2008R2-x64.zip is used as an example.

            -
            1. Log in to the Windows ECS using VNC.

              For details about how to log in to an ECS, see Elastic Cloud Server User Guide.

              +
              1. 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.

                -
              2. Download the required UVP VMTools based on the ECS OS and Obtaining Required Software Packages.
              3. Decompress the UVP Tools software package. This section uses vmtools-WIN2008R2-x64.exe extracted from vmtools-WIN2008R2-x64.zip as an example to describe how to decompress the UVP Tools software package.
              4. Right-click vmtools-WIN2008R2-x64.exe, select Run as administrator from the shortcut menu, and complete the installation as prompted.
              5. In the displayed dialog box, select I accept the terms in the License Agreement and click Install.
                Figure 1 Installing UVP VMTools
                +
              6. Download the required UVP VMTools based on the ECS OS and Obtaining Required Software Packages.
              7. Decompress the UVP Tools software package. This section uses vmtools-WIN2008R2-x64.exe extracted from vmtools-WIN2008R2-x64.zip as an example to describe how to decompress the UVP Tools software package.
              8. Right-click vmtools-WIN2008R2-x64.exe, select Run as administrator from the shortcut menu, and complete the installation as prompted.
              9. In the displayed dialog box, select I accept the terms in the License Agreement and click Install.
                Figure 1 Installing UVP VMTools
              10. Install UVP VMTools as prompted.
              11. Perform the following operations to install UVP VMTools on an ECS running Windows Server 2008:
                1. The Windows Security dialog box shown in Figure 2 may be displayed during installation. In the dialog box, select Always trust... and click Install. Otherwise, the installation will fail.
                  Figure 2 Windows Security
                  -
                2. Click Finish.
                +
              12. Click Finish.

                After the installation is complete, restart the ECS so that NIC drivers can be detected.

                +
                +
            2. Perform the operations in Verifying the Installation to check whether UVP VMTools is successfully installed.

            Verifying the Installation

            Perform the following steps to verify the installation of UVP VMTools:

            diff --git a/docs/ims/umn/en-us_topic_0037352182.html b/docs/ims/umn/en-us_topic_0037352182.html index 3d651495d..ed59d8f25 100644 --- a/docs/ims/umn/en-us_topic_0037352182.html +++ b/docs/ims/umn/en-us_topic_0037352182.html @@ -1,7 +1,8 @@

            Installing the PV Driver

            -

            Scenarios

            When using an ECS or external image file to create a private image, ensure that the PV driver has been installed in the OS to enable Xen virtualization for subsequently created ECSs, improve the I/O processing performance of the ECSs, and implement advanced functions such as monitoring hardware of the ECSs.

            +

            This section only applies to Xen ECSs, which have been discontinued and no longer been available for new users. If you are a new user or you are an existing user that will use this image to create a non-Xen ECS, skip this section.

            +

            Scenarios

            When using an ECS or external image file to create a private image, ensure that the PV driver has been installed in the OS to enable Xen virtualization for subsequently created ECSs, improve the I/O processing performance of the ECSs, and implement advanced functions such as monitoring hardware of the ECSs.

            If you do not install the PV driver, the ECS network performance will be poor, and the security group and firewall configured for the ECS will not take effect.

            The PV driver has been installed by default when you use a public image to create ECSs. You can perform the following operations to verify the installation:

            @@ -9,10 +10,10 @@
            C:\Program Files (x86)\Xen PV Drivers\bin\version
            • If the PV driver version is later than 2.5, you do not need to install the PV driver.
            • If the PV driver version is not displayed or the version is 2.5 or earlier, perform operations in Installing the PV Driver.
            -

            Prerequisites

            • An OS has been installed for the ECS, and an EIP has been bound to the ECS.
            • The remaining capacity of the ECS system disk must be greater than 32 MB.
            • If the ECS uses Windows 2008, you must install the PV driver using the administrator account.
            • The PV driver software package has been downloaded on the ECS. For how to obtain the software package, see Obtaining Required Software Packages.
            • To avoid an installation failure, perform the following operations before starting the installation:
              • Uninstall third-party virtualization platform tools, such as Citrix Xen Tools and VMware Tools. For how to uninstall the tools, see the corresponding official documents of the tools.
              • Disable your antivirus and intrusion detection software. You can enable the software after the PV driver is installed.
              +

              Prerequisites

              • An OS has been installed for the ECS, and an EIP has been bound to the ECS.
              • The remaining capacity of the ECS system disk must be greater than 32 MB.
              • If the ECS uses Windows 2008, you must install the PV driver using the administrator account.
              • The PV driver software package has been downloaded on the ECS. For how to obtain the software package, see Obtaining Required Software Packages.
              • To avoid an installation failure, perform the following operations before starting the installation:
                • Uninstall third-party virtualization platform tools, such as Citrix Xen Tools and VMware Tools. For how to uninstall the tools, see the corresponding official documents of the tools.
                • Disable your anti-virus and intrusion detection software. You can enable the software after the PV driver is installed.
              -

              Installing the PV Driver

              1. Log in to the Windows ECS using VNC.

                For details about how to log in to an ECS, see Elastic Cloud Server User Guide.

                +

                Installing the PV Driver

                1. 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.

                2. On the ECS, choose Start > Control Panel.
                3. Click Uninstall a program.
                4. Uninstall GPL PV drivers for Windows x.x.x.xx as prompted.
                5. Download the required PV driver based on the ECS OS and Obtaining Required Software Packages.
                6. Decompress the PV driver software package.
                7. Right-click GPL PV Drivers for Windows x.x.x.xx, select Run as administrator, and complete the installation as prompted.
                8. Restart the ECS as prompted to make the PV driver take effect.

                  ECSs running Windows Server 2008 must be restarted twice.

                  @@ -21,7 +22,7 @@

                Verifying the Installation

                Perform the following steps to verify the installation of the PV driver:

                -
                1. Click Start. Choose Control Panel > Programs and Features.
                2. Locate the PV driver for Windows.

                  If the PV driver exists, the installation is successful, as shown in Figure 1.

                  +
                  1. Click Start. Choose Control Panel > Programs and Features.
                  2. Locate the PV driver for Windows.

                    If UVP VMTools for Windows exists, the installation is successful, as shown in Figure 1.

                    Figure 1 Verifying the installation
                diff --git a/docs/ims/umn/en-us_topic_0037352185.html b/docs/ims/umn/en-us_topic_0037352185.html index 12f760cd2..217c2a1d5 100644 --- a/docs/ims/umn/en-us_topic_0037352185.html +++ b/docs/ims/umn/en-us_topic_0037352185.html @@ -3,9 +3,8 @@

                Viewing the Virtualization Type of a Linux ECS

                You can run the following command to query the virtualization type of an ECS:

                lscpu

                -

                If the value of Hypervisor vendor is Xen, the ECS uses Xen. If KVM is required, perform the operations in this section to optimize the Linux private image.

                -

                If the ECS uses KVM, you are also advised to optimize the private image to prevent any exceptions with the ECSs created from the image.

                -
                +

                If the value of Hypervisor vendor is Xen, the ECS uses Xen.

                +

                If the value of Hypervisor vendor is KVM, the ECS uses KVM.

                Figure 1 Viewing the virtualization type of a Linux ECS
                diff --git a/docs/ims/umn/en-us_topic_0037352186.html b/docs/ims/umn/en-us_topic_0037352186.html index e5fc8123c..51c6fe6fc 100644 --- a/docs/ims/umn/en-us_topic_0037352186.html +++ b/docs/ims/umn/en-us_topic_0037352186.html @@ -1,18 +1,18 @@ -

                Uninstalling the PV Driver from a Linux ECS

                -

                Scenarios

                When optimizing a Linux private image, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the ECS. To ensure that you can successfully install native Xen and KVM drivers, you must uninstall the PV driver from the ECS.

                +

                Uninstalling PV Drivers from a Linux ECS

                +

                Scenarios

                When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the source ECS of the image.

                +

                To ensure that you can successfully install native Xen and KVM drivers, you must uninstall PV drivers from the ECS first.

                -

                Procedure

                1. Log in to the ECS as user root using VNC.
                2. Run the following command to check whether the PV driver is installed in the OS:

                  ps -ef | grep uvp-monitor

                  -

                  The PV driver is installed in the OS if the following information is displayed:

                  +

                  Procedure

                  1. Log in to the ECS as user root using VNC.
                  2. Run the following command to check whether PV drivers are installed in the OS:

                    ps -ef | grep uvp-monitor

                    +
                    • If the following information is displayed, PV drivers have been installed.
                    • Otherwise, PV drivers are not installed. No further actions will be required.
                    root     4561        1    0   Jun29 ?           00:00:00   /usr/bin/uvp-monitor
 root     4567     4561    0   Jun29 ?           00:00:00   /usr/bin/uvp-monitor
 root     6185     6085    0   03:04  pts/2      00:00:00   grep uvp-monitor
                    - -
                  3. In the VNC login window, open the CLI.

                    For how to open the CLI, see the OS manual.

                    -
                  4. Run the following command to uninstall the PV driver:

                    /etc/.uvp-monitor/uninstall

                    -
                    • The PV driver is uninstalled successfully if the following command output is displayed:
                      The PV driver is uninstalled successfully. Reboot the system for the uninstallation to take effect.
                      -
                    • If .uvp-monitor is not contained in the command output, go to 5.
                      -bash: /etc/.uvp-monitor/uninstall: No such file or directory
                      +
                    • In the VNC login window, open the CLI.

                      For how to open the CLI, see the OS manual.

                      +
                    • Run the following command to uninstall PV drivers:

                      /etc/.uvp-monitor/uninstall

                      +
                      • PV drivers are uninstalled successfully if the following command output is displayed:
                        The PV driver is uninstalled successfully. Reboot the system for the uninstallation to take effect.
                        +
                      • If the command output indicates that .uvp-monitor is not found, go to 5.
                        -bash: /etc/.uvp-monitor/uninstall: No such file or directory
                    • Perform the following operations to delete uvp-monitor that failed to take effect, preventing log overflow:
                      1. Run the following command to check whether UVP user-mode programs are installed in the OS:

                        rpm -qa | grep uvp

                        Information similar to the following is displayed:

                        diff --git a/docs/ims/umn/en-us_topic_0040740508.html b/docs/ims/umn/en-us_topic_0040740508.html index 22676330e..749c9eed7 100644 --- a/docs/ims/umn/en-us_topic_0040740508.html +++ b/docs/ims/umn/en-us_topic_0040740508.html @@ -30,7 +30,7 @@
            Table 2 UVP VMTools software packages

            Software Package

            OS

            +

            OS

            How to Obtain
            - @@ -59,7 +59,7 @@

            BMS or Image File Configurations

            Table 2 Image file configurations

            OS

            Configuration Item

            +

            Configuration

            Reference

            - @@ -69,14 +69,14 @@ - - @@ -85,7 +85,7 @@
            Table 3 BMS configurations

            OS

            Configuration Item

            +

            Configuration

            Reference
            • Install software in the bms-network-config package.
            • Install Cloudbase-Init.
            • Delete residual files from the OS.

            For details, see "Creating a Private Image from a BMS" in Bare Metal Server User Guide.

            +

            "Creating a Private Image from a BMS" in Bare Metal Server User Guide

            Linux
            • Install software in the bms-network-config package.
            • Install Cloud-Init.
            • Delete residual files from the OS.

            For details, see "Creating a Private Image from a BMS" in Bare Metal Server User Guide.

            +

            "Creating a Private Image from a BMS" in Bare Metal Server User Guide
            - @@ -93,7 +93,7 @@ - diff --git a/docs/ims/umn/en-us_topic_0041178787.html b/docs/ims/umn/en-us_topic_0041178787.html index cfeee438d..8883d73ef 100644 --- a/docs/ims/umn/en-us_topic_0041178787.html +++ b/docs/ims/umn/en-us_topic_0041178787.html @@ -8,14 +8,38 @@ - + + + + + + + + + + + + @@ -112,7 +136,7 @@ - @@ -193,7 +217,7 @@ - @@ -207,7 +231,7 @@ - @@ -215,7 +239,7 @@ @@ -229,7 +253,7 @@ diff --git a/docs/ims/umn/en-us_topic_0046588154.html b/docs/ims/umn/en-us_topic_0046588154.html index 532f6f661..95525deb4 100644 --- a/docs/ims/umn/en-us_topic_0046588154.html +++ b/docs/ims/umn/en-us_topic_0046588154.html @@ -4,7 +4,7 @@

            IMS allows you to create encrypted images to ensure data security.

            To use the image encryption function, you must apply for KMS Administrator permissions.

            -

            Constraints

            • KMS must be enabled.
            • Encrypted images cannot be shared with others.
            • The system disk of an ECS created from an encrypted image is also encrypted, and its key is the same as the image key.
            • If an ECS has an encrypted system disk, private images created from the ECS are also encrypted.
            • The key used for encrypting an image cannot be changed.
            • If the key used for encrypting an image is disabled or deleted, the image is unavailable.
            +

            Constraints

            • KMS must be enabled.
            • If an encrypted image needs to be shared with other tenants, the key of the image must be a custom key instead of the default key ims/default.
            • The system disk of an ECS created from an encrypted image is also encrypted, and its key is the same as the image key.
            • If an ECS has an encrypted system disk, private images created from the ECS are also encrypted.
            • The key used for encrypting an image cannot be changed.
            • If the key used for encrypting an image is disabled or deleted, the image is unavailable.
            diff --git a/docs/ims/umn/en-us_topic_0047501112.html b/docs/ims/umn/en-us_topic_0047501112.html index 100fc4b3a..edf636636 100644 --- a/docs/ims/umn/en-us_topic_0047501112.html +++ b/docs/ims/umn/en-us_topic_0047501112.html @@ -1,7 +1,7 @@

            Optimization Process

            -

            ECSs require Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools) for proper running. To ensure that ECSs support both Xen and KVM and to improve network performance, the PV driver and UVP VMTools must be installed for the image.

            +

            The proper running of ECSs depends on Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools). To ensure that ECSs support both Xen and KVM and to improve network performance, the PV driver and UVP VMTools must be installed for the image.

            1. Create an ECS using the Windows private image to be optimized and log in to the ECS.
            2. Install the latest version of PV driver on the ECS.

              For details, see Installing the PV Driver.

            3. Install the UVP VMTools required for creating ECSs in the KVM virtual resource pool.

              For details, see Installing UVP VMTools.

            4. 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.
            5. Clear system logs and then stop the ECS.

              For details, see Clearing System Logs.

              diff --git a/docs/ims/umn/en-us_topic_0047501133.html b/docs/ims/umn/en-us_topic_0047501133.html index 2acd4140d..93850dc35 100644 --- a/docs/ims/umn/en-us_topic_0047501133.html +++ b/docs/ims/umn/en-us_topic_0047501133.html @@ -1,13 +1,21 @@

              Optimization Process

              -

              A Linux ECS can be switched from Xen to KVM if xen-pv and VirtIO drivers run on the ECS. Before changing a Xen-based ECS to a KVM-based ECS, ensure that the required drivers have been installed and the UUID has been configured for the Linux private image. In addition, optimizing the private image can improve network performance of the ECS.

              -
              1. Use the Linux image to be optimized to create an ECS, and start and log in to the ECS.
              2. Uninstall the PV Driver installed on the ECS.

                For details, see Uninstalling the PV Driver from a Linux ECS.

                -
              3. 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.

                -
              4. Change the disk ID in the fstab file to UUID.

                For details, see Changing the Disk Identifier in the fstab File to UUID.

                -
              5. Install native KVM drivers.

                For details, see Installing Native KVM Drivers.

                -
              6. Delete log files and historical records, and stop the ECS.

                For details, see Clearing System Logs.

                -
              7. Create a Linux private image using the ECS.
              +

              The virtualization of ECSs is gradually changing from Xen to KVM. Therefore, private images need to support both Xen and KVM. To ensure that ECSs created from a private image can run properly, you are advised to optimize it no matter it is using Xen or KVM.

              +

              A Linux ECS can run properly only when xen-pv and 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

              1. Use the Linux image to be optimized to an ECS, and start and log in to the ECS.
              2. View the virtualization type of the ECS....

                For details, see Viewing the Virtualization Type of a Linux ECS.

                +

                The virtualization type may cause slice differences in an optimization process.

                +
              +
              +

              Process

              1. Uninstall PV drivers from the ECS.

                For details, see Uninstalling PV Drivers from a Linux ECS.

                +

                If the ECS is using KVM virtualization, skip this step.

                +
                +
              2. 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.

                +
              3. Change the disk ID in the fstab file to UUID.

                For details, see Changing the Disk Identifier in the fstab File to UUID.

                +
              4. Install native virtualization drivers. +
              5. Delete log files and historical records, and stop the ECS.

                For details, see Clearing System Logs.

                +
              6. Create a Linux private image using the ECS.
              +
              diff --git a/docs/ims/umn/en-us_topic_0049177180.html b/docs/ims/umn/en-us_topic_0049177180.html index 833c6fad4..eb5416fb4 100644 --- a/docs/ims/umn/en-us_topic_0049177180.html +++ b/docs/ims/umn/en-us_topic_0049177180.html @@ -4,7 +4,7 @@

              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:

              • 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.
              diff --git a/docs/ims/umn/en-us_topic_0068002265.html b/docs/ims/umn/en-us_topic_0068002265.html index 3c266f6cb..33fc9d5b1 100644 --- a/docs/ims/umn/en-us_topic_0068002265.html +++ b/docs/ims/umn/en-us_topic_0068002265.html @@ -9,8 +9,7 @@

              Add, Delete, and Modify Image Tags

              1. Access the IMS console.
                1. Log in to the management console.
                2. Under Compute, click Image Management Service.

                  The IMS console is displayed.

                -
              2. Click the Private Images tab and click the image name to display the image details.
                • To modify an image tag, go to 3.
                -
                • To delete an image tag, go to 4.
                • To add an image tag, go to 5.
                +
              3. Click the Private Images tab and click the image name to display the image details.
                • To modify an image tag, go to 3.
                • To delete an image tag, go to 4.
                • To add an image tag, go to 5.
              4. Click the Tags tab, locate the target tag, and click Edit in the Operation column. In the displayed dialog box, modify the tag.
              5. Click the Tags tab, locate the target tag, and click Delete in the Operation column. In the displayed dialog box, click Yes.
              6. Click the Tags tab and then Add Tag. In the displayed dialog box, add a tag.

              Search for Private Images by Tag

              1. Access the IMS console.
                1. Log in to the management console.
                2. Under Compute, click Image Management Service.

                  The IMS console is displayed.

                  @@ -20,6 +19,16 @@
                3. Click Search.

                  The system searches for private images based on tag keys or tag values.

              +

              Search for Shared Images by Tag

              You can search for a private image that has a tag and is shared with you by another tenant.

              +

              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.

              +
              +
              1. Log in to the management console.
              2. Under Compute, click Image Management Service.

                The Private Images page is displayed.

                +
              3. Click the Images Shared with Me tab and then Search by Tag.
              4. 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.

                +
              5. 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.

                +
              6. Click Search.

                The system searches for shared images based on tag keys or tag values.

                +
              +
              diff --git a/docs/ims/umn/en-us_topic_0084064672.html b/docs/ims/umn/en-us_topic_0084064672.html index fb9a65e08..565a7f063 100644 --- a/docs/ims/umn/en-us_topic_0084064672.html +++ b/docs/ims/umn/en-us_topic_0084064672.html @@ -5,21 +5,21 @@

              Background

              The following figure shows the process of creating a data disk image from an external image file.

              Figure 1 Creating a data disk image from an external image file
              -
              1. Prepare an external image file. The file must be in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format. If you want to use an image file in other formats, convert the file into any of the listed formats before importing it to the cloud platform.
              2. When uploading the external image file, you must select an OBS bucket with standard storage. For details, see Uploading an External Image File.
              3. Create a data disk image. For details, see Procedure.
              4. Use the data disk image to create data disks. For details, see Follow-up Procedure.
              +
              1. Prepare an external image file. The file must be in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format. If you want to use an image file in other formats, convert the file into any of the listed formats before importing it to the cloud platform.
              2. When uploading the external image file, you must select an OBS bucket with standard storage. For details, see Uploading an External Image File.
              3. Create a data disk image. For details, see Procedure.
              4. Use the data disk image to create data disks. For details, see Follow-up Procedure.

              Procedure

              1. Access the IMS console.

                1. Log in to the management console.
                2. Under Compute, click Image Management Service.

                  The IMS console is displayed.

                -

              2. Create a data disk image.

                1. Click Create Image in the upper right corner.
                2. In the Image Type and Source area, select Data disk image for Type.
                3. Select Image File for Source. Select the bucket storing the image file from the list and then select the image file.
                  Figure 2 Creating a data disk image
                  +

                4. Create a data disk image.

                  1. Click Create Image in the upper right corner.
                  2. In the Image Type and Source area, select Data disk image for Type.
                  3. Select Image File for Source. Select the bucket storing the image file from the list and then select the image file.
                    Figure 2 Creating a data disk image
                  4. To register the image file using the Fast Create function, select Enable Fast Create.
                    • Currently, this function supports only image files in ZVHD2 or RAW format.
                    • For how to convert image file formats and generate bitmap files, see Quickly Importing an Image File.

                    After you select Enable Fast Create, select the confirmation information following Image File Preparation if you have prepared the required files.

                    -
                  5. In the Image Information area, set the following parameters.
                    • OS Type: The value can be Windows or Linux.
                    • Data Disk: The value ranges from 1 GB to 2048 GB and must be no less than the data disk size in the image file.
                    • Name: Enter a name for the image.
                    • (Optional) Encryption: If you want to encrypt the image, select KMS encryption and then select the key to be used from the key list.
                    • (Optional) Tag: Set a tag key and a tag value for the image to easily identify and manage it.
                    • (Optional) Description: Enter description of the image.
                    -
                  6. Click Create Now.
                  7. Confirm the parameters and click Submit.
                  +
                5. In the Image Information area, set the following parameters.
                  • OS Type: The value is Windows or Linux.
                  • Data Disk: The value ranges from 1 GB to 2048 GB and must be no less than the data disk size in the image file.
                  • Name: Enter a name for the image.
                  • (Optional) Encryption: If you want to encrypt the image, select KMS encryption and then select the key to be used from the key list.
                  • Enterprise Project: Select an enterprise project from the drop-down list. This parameter is available only if you have enabled enterprise projects or your account is an enterprise account. To enable this function, contact your customer manager. An enterprise project provides central management of cloud resources on a project.
                  • (Optional) Tag: Set a tag key and a tag value for the image to easily identify and manage it.
                  • (Optional) Description: Enter description of the image.
                  +
                6. Click Create Now.
                7. Confirm the settings and click Submit.

              3. Go back to the Private Images page and view the new data disk image.

                When the image status changes to Normal, the image creation is complete.

              -

              Follow-up Procedure

              If you want to use the created data disk image to create an EVS disk and attach it to an ECS, you can perform either of the following operations:

              -
              • Locate the row that contains the created data disk image and click Create Data Disk to create one or multiple data disks. Then attach the data disks to an ECS.
              • On the page for creating ECSs, click Create Disk from Data Disk Image and select the data disk image.

                A data disk image can be used to create a data disk for an ECS only once.

                +

                Follow-up Procedure

                If you want to use the created data disk image to create an EVS disk and attach it to an ECS, you can perform either of the following operations:

                +
                • Locate the row that contains the created data disk image and click Create Data Disk to create one or multiple data disks. Then attach the data disks to an ECS.
                • On the page for creating ECSs, click Create Disk from Data Disk Image and select the data disk image.

                  A data disk image can be used to create a data disk for an ECS only once.

                diff --git a/docs/ims/umn/en-us_topic_0085214115.html b/docs/ims/umn/en-us_topic_0085214115.html index 31dec2b5b..39b72f8e9 100644 --- a/docs/ims/umn/en-us_topic_0085214115.html +++ b/docs/ims/umn/en-us_topic_0085214115.html @@ -83,12 +83,12 @@

                Operation Instructions

                Assume that an ECS has the required specifications and virtualization type.

                -
                -

                Register the external image file as a private image

                Register the external image file as a private image. For details, see Registering an External Image File as a Private Image.

                +

                Register the External Image File as a Private Image

                Register the external image file as a private image. For details, see Registering an External Image File as a Private Image.

                -

                Set NIC Multi-Queue for the Image

                Windows OSs have not commercially supported NIC multi-queue. If you enable NIC multi-queue in a Windows image, starting an ECS created using such an image may be slow.

                +

                Set NIC Multi-Queue for the Image

                Windows OSs have not commercially supported NIC multi-queue. If you enable NIC multi-queue for a Windows image, starting an ECS created using such an image may be slow.

                Use either of the following methods to set NIC multi-queue.

                Method 1:
                1. Access the IMS console.
                  1. Log in to the management console.
                  2. Under Compute, click Image Management Service.

                    The IMS console is displayed.

                  @@ -99,7 +99,7 @@
                2. On the displayed Private Images page, click the name of the target image.
                3. In the upper right corner of the displayed image details page, click Modify. In the displayed Modify Image dialog box, set NIC multi-queue for the image.

                Method 3: Add hw_vif_multiqueue_enabled to the image using an API.

                -
                1. Obtain a token. For details, see Token Authentication.
                2. Call an API to update image information. For details, see "Updating Image Information (Native OpenStack API)" in Image Management Service API Reference.
                3. Add X-Auth-Token to the request header.

                  The value of X-Auth-Token is the token obtained in step 1.

                  +
                  1. Obtain a token. For details, see Token Authentication.
                  2. Call an API to update image information. For details, see "Updating Image Information (Native OpenStack API)" in Image Management Service API Reference.
                  3. Add X-Auth-Token to the request header.

                    The value of X-Auth-Token is the token obtained in step 1.

                  4. Add Content-Type to the request header.

                    The value of Content-Type is application/openstack-images-v2.1-json-patch.

                    The request URI is in the following format:

                    PATCH /v2/images/{image_id}

                    @@ -115,7 +115,7 @@
                    Figure 1 Example request body
                -

                Create an ECS from the Private Image

                Use the registered private image to create an ECS. For details, see Elastic Cloud Server User Guide. Note the following when setting the parameters:
                • Region: Select the region where the private image is located.
                • Image: Select Private image and then the desired image from the drop-down list.
                +

                Create an ECS from the Private Image

                Use the registered private image to create an ECS. For details, see the Elastic Cloud Server User Guide. Note the following when setting the parameters:
                • Region: Select the region where the private image is located.
                • Image: Select Private image and then the desired image from the drop-down list.

                Enable NIC Multi-Queue

                KVM ECSs running Windows use private images to support NIC multi-queue.

                diff --git a/docs/ims/umn/en-us_topic_0086020894.html b/docs/ims/umn/en-us_topic_0086020894.html index a68d889b4..369936565 100644 --- a/docs/ims/umn/en-us_topic_0086020894.html +++ b/docs/ims/umn/en-us_topic_0086020894.html @@ -1,17 +1,17 @@ -

                How Do I Install Native Xen and KVM Drivers?

                -

                Scenarios

                When optimizing a Linux private image, you need to install native Xen and KVM drivers for the image.

                -

                If you do not install Xen drivers for the image, the network performance of the ECSs created from this image will be poor, and the security groups and firewall configured for the ECSs will not take effect.

                -

                If you do not install KVM drivers for the image, the NICs of the ECSs may not be detected and the ECSs will be unable to communicate with other resources.

                +

                How Do I Install the Native Xen and KVM Drivers?

                +

                Scenarios

                When optimizing a Linux private image with Xen virtualization, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the source ECS of the image.

                +

                This section describes how to install the native Xen and KVM drivers.

                +

                Xen: If you do not install the Xen driver for the image, the network performance of the ECSs created from this image will be poor, and the security groups and firewall configured for the ECSs will not take effect.

                +

                KVM: If you do not install the KVM driver for the image, the NICs of the ECSs may not be detected and the ECSs will be unable to communicate with other resources.

                -

                This section describes how to install native Xen and KVM drivers.

                -

                Prerequisites

                • The kernel version must be later than 2.6.24.
                • Antivirus and intrusion detection software have been disabled. You can enable them after Xen and KVM drivers are installed.
                +

                Prerequisites

                • The virtualization type of the ECS is Xen. For details, see .
                • The kernel version must be later than 2.6.24.
                • Disable your antivirus and intrusion detection software. You can enable them after installation of the Xen and KVM drivers.
                -

                Procedure

                Modify the configuration file depending on the OS.
                • CentOS, EulerOS

                  Take CentOS 7.0 as an example. Modify the /etc/dracut.conf file. Add the xen-pv and VirtIO drivers to add_drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include 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. Run the dracut -f command to regenerate initrd.

                  +

                  Procedure

                  Modify the configuration file depending on the OS.
                  • CentOS, EulerOS

                    Take CentOS 7.0 as an example. Modify the /etc/dracut.conf file. Add the xen-pv and VirtIO drivers to add_drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include 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. Run the dracut -f command to regenerate initrd.

                    For details, see CentOS and EulerOS.

                    -
                  • Ubuntu and Debian

                    Modify the /etc/initramfs-tools/modules file. Add the xen-pv and VirtIO drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Save and exit the /etc/initramfs-tools/modules file. Run the update-initramfs -u command to regenerate initrd.

                    +
                  • Ubuntu and Debian

                    Modify the /etc/initramfs-tools/modules file. Add the xen-pv and VirtIO drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Save and exit the /etc/initramfs-tools/modules file. Run the update-initramfs -u command to regenerate initrd.

                    For details, see Ubuntu and Debian.

                  • SUSE and openSUSE
                    • If the OS version is earlier than SUSE 12 SP1 or openSUSE 13, modify the /etc/sysconfig/kernel file and add xen-pv and VirtIO drivers to INITRD_MODULES="". xen-pv drivers include xen_vnif, xen_vbd, and xen_platform_pci. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Run the mkinitrd command to regenerate initrd.
                    • If the OS version is SUSE 12 SP1, modify the /etc/dracut.conf file and add xen-pv and VirtIO drivers to add_drivers. xen-pv drivers include xen_vnif, xen_vbd, and xen_platform_pci. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Run the dracut -f command to regenerate initrd.
                    • If the OS version is later than SUSE 12 SP1 or openSUSE 13, modify the /etc/dracut.conf file and add xen-pv and VirtIO drivers to add_drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include 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. Run the dracut -f command to regenerate initrd.
                    For details, see SUSE and openSUSE.

                    For SUSE, run the following command to check whether xen-kmp (driver package for xen-pv) is installed:

                    @@ -19,7 +19,7 @@

                    If information similar to the following is displayed, xen-kmp is installed in the OS:

                    xen-kmp-default-4.2.2_04_3.0.76_0.11-0.7.5

                    If xen-kmp is not installed, obtain it from the ISO file and install it.

                    -

                    If you add built-in drivers to the initrd or initramfs file by mistake, the ECS will not be affected.

                    +

                    If you add built-in drivers to the initrd or initramfs file by mistake, the ECS will not be affected.

                  @@ -71,7 +71,7 @@ drwxr-xr-x 2 root root 0 Jul 16 17:53 lib/modules/2.6.32-573.8. virtio_pci virtio_ring virtio -
                • Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/initramfs-tools/modules file.
                • Run the following command to regenerate initrd:

                  update-initramfs -u

                  +
                • Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/initramfs-tools/modules file.
                • Run the following command to regenerate initrd:

                  update-initramfs -u

                • Run the following commands to check whether native Xen and KVM drivers have been installed:

                  lsinitramfs /boot/initrd.img-`uname -r` |grep xen

                  lsinitramfs /boot/initrd.img-`uname -r` |grep virtio

                  [root@ CTU10000xxxxx home]# lsinitramfs /boot/initrd.img-`uname -r` |grep xen 
@@ -111,7 +111,7 @@ CONFIG_XEN_NETDEV_FRONTEND=y
                  # (like drivers for scsi-controllers, for lvm or reiserfs) # INITRD_MODULES="ata_piix ata_generic xen_vnif xen_vbd xen_platform_pci virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio" -
                • Run the mkinitrd command to regenerate initrd:

                  If the virtual file system is not the default initramfs or initrd, 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 menu.lst or grub.cfg file (/boot/grub/menu.lst, /boot/grub/grub.cfg, or /boot/grub2/grub.cfg).

                  +
                • Run the mkinitrd command to regenerate initrd:

                  If the virtual file system is not the default initramfs or initrd, 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 menu.lst or grub.cfg file (/boot/grub/menu.lst, /boot/grub/grub.cfg, or /boot/grub2/grub.cfg).

                  The following is an example initrd file of SUSE 11 SP4:

                  default 0
@@ -173,11 +173,11 @@ drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/d
 
                  cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y
            -
          • If the OS version is SUSE 12 SP1, perform the following steps:
            1. Run the following command to open the /etc/dracut.conf file:

              vi /etc/dracut.conf

              +
            2. If the OS version is SUSE 12 SP1, perform the following steps:
              1. Run the following command to open the /etc/dracut.conf file:

                vi /etc/dracut.conf

              2. Press i to enter editing mode and add the xen-pv and 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 xen_vnif xen_vbd xen_platform_pci virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
                -
              3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
              4. Run the following command to regenerate initrd:

                dracut -f /boot/initramfs-File name

                +
              5. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
              6. 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.

              7. If the virtual file system is initramfs, run the following commands to check whether native Xen and KVM drivers have been loaded:

                lsinitrd /boot/initramfs-`uname -r`.img | grep xen

                lsinitrd /boot/initramfs-`uname -r`.img | grep virtio

                @@ -185,7 +185,7 @@ add_drivers+="ata_piixlsinitrd /boot/initrd-`uname -r` | grep xen

                lsinitrd /boot/initrd-`uname -r` | grep virtio

              -
            3. If the OS version is later than SUSE 12 SP1 or openSUSE 13, perform the following steps:
              Take SUSE Linux Enterprise Server 12 SP2 (x86_64) as an example.
              1. Run the following command to open the /etc/dracut.conf file:

                vi /etc/dracut.conf

                +
              2. If the OS version is later than SUSE 12 SP1 or openSUSE 13, perform the following steps:
                Take SUSE Linux Enterprise Server 12 SP2 (x86_64) as an example.
                1. Run the following command to open the /etc/dracut.conf file:

                  vi /etc/dracut.conf

                2. Press i to enter editing mode and add the xen-pv and 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 xen-blkfront xen-netfront virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"
                  diff --git a/docs/ims/umn/en-us_topic_0093344231.html b/docs/ims/umn/en-us_topic_0093344231.html index f7b33f88a..ed05976a9 100644 --- a/docs/ims/umn/en-us_topic_0093344231.html +++ b/docs/ims/umn/en-us_topic_0093344231.html @@ -1,20 +1,21 @@

                  Creating a Full-ECS Image from a CSBS Backup

                  -

                  Scenarios

                  Create a full-ECS image from a CSBS backup. This image can then be used to create ECSs.

                  +

                  Scenarios

                  Create a full-ECS image from a CSBS backup. This image can then be used to create ECSs.

                  -

                  Constraints

                  • When creating a full-ECS image from a CSBS backup, ensure that the source ECS of the CSBS backup has been properly configured, or the image creation may fail.
                  • A CSBS backup used to create a full-ECS image cannot have shared disks.
                  • Only an available CSBS backup can be used to create a full-ECS image. A CSBS backup can be used to create only one full-ECS image.
                  • A full-ECS image cannot be exported or replicated.
                  +

                  Constraints

                  • When creating a full-ECS image from a CSBS backup, ensure that the source ECS of the CSBS backup has been properly configured, or the image creation may fail.
                  • If an ECS is in Stopped state, do not start it when you are using it to create a full-ECS image.
                  • A CSBS backup used to create a full-ECS image cannot have shared disks.
                  • Only an available CSBS backup can be used to create a full-ECS image. A CSBS backup can be used to create only one full-ECS image.
                  • A full-ECS image cannot be exported or replicated.

                  Procedure

                  1. Access the IMS console.

                    1. Log in to the management console.
                    2. Under Compute, click Image Management Service.

                      The IMS console is displayed.

                    -

                  2. Create a full-ECS image.

                    1. Click Create Image in the upper right corner.
                    2. In the Image Type and Source area, select Full-ECS image for Type.
                    3. Select CSBS Backup for Source and then select a backup from the list.
                      Figure 1 Creating a full-ECS image using a CSBS backup
                      -
                    4. In the Image Information area, configure basic image details, such as the image name and description.
                    5. Click Create Now.
                    6. Confirm the parameters and click Submit.
                    +

                  3. Create a full-ECS image.

                    1. Click Create Image in the upper right corner.
                    2. In the Image Type and Source area, select Full-ECS image for Type.
                    3. Select CSBS Backup for Source and then select a backup from the list.
                      Figure 1 Creating a full-ECS image using a CSBS backup
                      +
                    4. In the Image Information area, configure basic image details, such as the image name and description.
                    5. Click Create Now.
                    6. Confirm the settings and click Submit.

                  4. Switch back to the Image Management Service page to monitor the image status.

                    When the image status changes to Normal, the image creation is complete.

                  -

                  Follow-up Procedure

                  • If you want to use the full-ECS image to create ECSs, click Apply for Server in the Operation column. On the displayed page, create ECSs by following the instructions in Elastic Cloud Server User Guide.

                    If a full-ECS image contains one or more data disks, the system configures data disk parameters automatically when you use the image to create ECSs.

                    +

                    Follow-up Procedure

                    • If you want to use the full-ECS image to create ECSs, click Apply for Server in the Operation column. On the displayed page, create ECSs by following the instructions in Elastic Cloud Server User Guide.

                      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.
                      • If the full-ECS image contains multiple data disks, it takes some time to load and display the disk information.
                      -
                    • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
                    • If you want to share a full-ECS image with other tenants, you must migrate resources to the CBR service because only full-ECS images created from CBR backups can be shared.
                    +
                  • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
                  • If you want to share a full-ECS image with other tenants, you must migrate resources to the CBR service because only full-ECS images created from CBR backups can be shared.
                  diff --git a/docs/ims/umn/en-us_topic_0093887081.html b/docs/ims/umn/en-us_topic_0093887081.html index 4802663fb..bfc1f5dac 100644 --- a/docs/ims/umn/en-us_topic_0093887081.html +++ b/docs/ims/umn/en-us_topic_0093887081.html @@ -13,12 +13,12 @@

                  Procedure

                  1. Enter the Cloudbase-Init installation directory.

                    C:\Program Files\Cloudbase Solutions\ is used as an example of the Cloudbase-Init installation directory. Switch to the root directory of drive C and run the following command to enter the installation directory:

                    cd C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf

                  2. Run the following command to encapsulate Windows:

                    C:\Windows\System32\sysprep\sysprep.exe /generalize /oobe /unattend:Unattend.xml

                    -
                    • Ensure that /unattend:Unattend.xml is contained in the preceding command. Otherwise, the username, password, and other important configuration information of the ECS will be reset, and you must configure the OS manually when you use ECSs created from the Windows private image.
                    • After this command is executed, the ECS will be automatically stopped. After the ECS is stopped, use the ECS to create an image. ECSs created using the image have unique SIDs. If you restart a Windows ECS on which Sysprep has been executed, Sysprep takes effect only for the current ECS. Before creating an image using the ECS, you must run Sysprep again.
                    • For Windows Server 2012 and Windows Server 2012 R2, the administrator password of the ECS will be deleted after Sysprep is executed on the ECS. You need to log in to the ECS and reset the administrator password. In this case, the administrator password set on the management console will be invalid. Keep the password you set secure.
                    • If a domain account is required for logins, run Sysprep on the ECS before using it to create a private image. For details about the impact of running Sysprep, see Why Is Sysprep Required for Creating a Private Image from a Windows ECS?
                    • The Cloudbase-Init account of a Windows ECS is an internal account of the Cloudbase-Init agent. This account is used for obtaining metadata and completing relevant configuration when the Windows ECS starts. If you modify or delete this account, or uninstall the Cloudbase-Init agent, you will be unable to inject initial custom information into an ECS created from a Windows private image. Therefore, you are not advised to modify or delete the Cloudbase-Init account.
                    +
                    • Ensure that /unattend:Unattend.xml is contained in the preceding command. Otherwise, the username, password, and other important configuration information of the ECS will be reset, and you must configure the OS manually when you use ECSs created from the Windows private image.
                    • After this command is executed, the ECS will be automatically stopped. After the ECS is stopped, use the ECS to create an image. ECSs created using the image have unique SIDs. If you restart a Windows ECS on which Sysprep has been executed, Sysprep takes effect only for the current ECS. Before creating an image using the ECS, you must run Sysprep again.
                    • For Windows Server 2012 and Windows Server 2012 R2, the administrator password of the ECS will be deleted after Sysprep is executed on the ECS. You need to log in to the ECS and reset the administrator password. In this case, the administrator password set on the management console will be invalid. Keep the password you set secure.
                    • If a domain account is required for logins, run Sysprep on the ECS before using it to create a private image. For details about the impact of Sysprep operations, see Why Is Sysprep Required for Creating a Private Image from a Windows ECS?.
                    • The Cloudbase-Init account of a Windows ECS is an internal account of the Cloudbase-Init agent. This account is used for obtaining metadata and completing relevant configuration when the Windows ECS starts. If you modify or delete this account, or uninstall the Cloudbase-Init agent, you will be unable to inject initial custom information into an ECS created from a Windows private image. Therefore, you are not advised to modify or delete the Cloudbase-Init account.
                    Figure 2 Running Sysprep
                  -

                  Follow-up Procedure

                  1. Create a private image from the ECS on which Sysprep is executed. For details, see Creating a System Disk Image from a Windows ECS.
                  2. You can use the image to create ECSs. Each ECS has a unique SID.

                    Run the following command to query the ECS SID:

                    +

                    Follow-up Procedure

                    1. Create a private image from the ECS on which Sysprep is executed. For details, see Creating a System Disk Image from a Windows ECS.
                    2. You can use the image to create ECSs. Each ECS has a unique SID.

                      Run the following command to query the ECS SID:

                      whoami /user

                      Figure 3 ECS SID before Sysprep is executed
                      Figure 4 ECS SID after Sysprep is executed
                      diff --git a/docs/ims/umn/en-us_topic_0096558549.html b/docs/ims/umn/en-us_topic_0096558549.html index 457c51213..7e7742d11 100644 --- a/docs/ims/umn/en-us_topic_0096558549.html +++ b/docs/ims/umn/en-us_topic_0096558549.html @@ -4,7 +4,7 @@

                      Symptom

                      When you create a ZVHD2 image using an API, the image is created in the ZVHD format.

                      Solution

                      Check whether your token contains the op_gated_lld role (op_gated_lld is the OBT tag, which can be viewed in the body of the response message of the API used to obtain a user token). The ZVHD2 image has the lazy loading feature. If the current environment does not support this feature or this feature is in the OBT phase, the ZVHD2 image will fail to be created.

                      -

                      Contact the customer service to ensure that the current environment supports the lazy loading feature, obtain a new token, and use the new token to create an image.

                      +

                      Contact the customer service to ensure that the current environment supports lazy loading, obtain a new token, and use the new token to create an image.

                      diff --git a/docs/ims/umn/en-us_topic_0102644450.html b/docs/ims/umn/en-us_topic_0102644450.html index e9bf1f8b8..e9e8f114c 100644 --- a/docs/ims/umn/en-us_topic_0102644450.html +++ b/docs/ims/umn/en-us_topic_0102644450.html @@ -1,23 +1,23 @@

                      Creating a Data Disk Image from an ECS

                      -

                      Scenarios

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

                      -

                      For example, you can create a data disk image to clone the data of an ECS whose disk is about to expire.

                      +

                      Scenarios

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

                      +

                      For example, you can create a data disk image to clone the data of an ECS whose disk is about to expire.

                      Background

                      The following figure shows the process of creating a data disk image from an ECS.

                      Figure 1 Creating a data disk image and using it to create data disks
                      -

                      Prerequisites

                      • A data disk has been attached to the ECS, and the ECS is running or stopped. For details about how to attach a data disk, see Elastic Cloud Server User Guide.
                      • The data disk capacity of the ECS must be no greater than 1 TB.

                        If the capacity is greater than 1 TB, you can only use the ECS to create a full-ECS image.

                        +

                        Prerequisites

                        • A data disk has been attached to the ECS, and the ECS is running or stopped. For details about how to attach a data disk, see Elastic Cloud Server User Guide.
                        • The data disk capacity of the ECS must be no greater than 1 TB.

                          If the capacity is greater than 1 TB, you can only use the ECS to create a full-ECS image.

                        Procedure

                        1. Access the IMS console.

                          1. Log in to the management console.
                          2. Under Compute, click Image Management Service.

                            The IMS console is displayed.

                          -

                        2. Create a data disk image.

                          1. Click Create Image in the upper right corner.
                          2. In the Image Type and Source area, select Data disk image for Type.
                          3. Select ECS for Source and then select a data disk of the ECS.
                            Figure 2 Creating a data disk image
                            -
                          4. In the Image Information area, set Name, Tag, and Description.
                          5. Click Create Now.
                          6. Confirm the parameters and click Submit.
                          +

                        3. Create a data disk image.

                          1. Click Create Image in the upper right corner.
                          2. In the Image Type and Source area, select Data disk image for Type.
                          3. Select ECS for Source and then select a data disk of the ECS.
                            Figure 2 Creating a data disk image
                            +
                          4. In the Image Information area, set Name, Tag, and Description.
                          5. In the Image Information area, set Name, Tag, and Description, and select an enterprise project.
                          6. Click Create Now.
                          7. Confirm the settings and click Submit.

                        4. Go back to the Private Images page and view the new data disk image.
                        -

                        Follow-up Procedure

                        If you want to use the created data disk image to create an EVS disk and attach it to an ECS, you can perform either of the following operations:

                        -
                        • Locate the row that contains the created data disk image and click Create Data Disk to create a data disk. Then attach the data disk to an ECS.
                        • On the page for creating ECSs, click Create Disk from Data Disk Image and select the data disk image.

                          A data disk image can be used to create a data disk for an ECS only once.

                          +

                          Follow-up Procedure

                          If you want to use the created data disk image to create an EVS disk and attach it to an ECS, you can perform either of the following operations:

                          +
                          • Locate the row that contains the created data disk image and click Create Data Disk to create a data disk. Then attach the data disk to an ECS.
                          • On the page for creating ECSs, click Create Disk from Data Disk Image and select the data disk image.

                            A data disk image can be used to create a data disk for an ECS only once.

                          diff --git a/docs/ims/umn/en-us_topic_0107462581.html b/docs/ims/umn/en-us_topic_0107462581.html index 04a8c4eff..9734088f0 100644 --- a/docs/ims/umn/en-us_topic_0107462581.html +++ b/docs/ims/umn/en-us_topic_0107462581.html @@ -75,13 +75,13 @@
            • Table 4 Image file configurations

            OS

            Configuration Item

            +

            Configuration

            Reference

            Windows

            • Install drivers for x86 v5 BMSs.
            • Install Cloudbase-Init.
            • Install software in the bms-network-config package.
            • (Optional) Install the SDI iNIC driver.
            • Set the Windows time zone.
            • Set the virtual memory.
            • (Optional) Configure automatic Windows update.
            • Configure SID.
            +
            • Install drivers for x86 V5 BMSs.
            • Install Cloudbase-Init.
            • Install software in the bms-network-config package.
            • (Optional) Install the SDI iNIC driver.
            • Set the Windows time zone.
            • Set the virtual memory.
            • (Optional) Configure automatic Windows update.
            • Configure SID.

            Bare Metal Server Image Creation Guide

            2021-08-15

            +

            2023-02-07

            +

            Modified the following content:

            + +

            2023-01-16

            +

            Modified the following content:

            + +

            2022-12-01

            +

            Modified the following content:

            + +

            2022-10-31

            +

            Added the following content:

            + +

            Modified the following content:

            + +

            2021-08-15

            Added the following content:

            - +

            Modified the following content:

            -

            Deleted the following content:

            -
            • Marketplace images

            2020-08-12

            @@ -103,7 +127,7 @@

            Added the following content:

            Converting the Image Format Using qemu-img

            -
            Modified the following content:
            • Modified sections for creating and registering images due to the modification on the IMS web interface.
            • Added new OSs supported for external image files, including Ubuntu 18.04 64bit, Red Hat 7.5 64bit, Oracle 7.5 64bit, CentOS 7.5 64bit, and Fedora 28 64bit in External Image File Formats and Supported OSs.
            +
            Modified the following content:
            • Modified sections for creating and registering images due to the modification on the IMS web interface.
            • Added new OSs supported by external image files, including Ubuntu 18.04 64bit, Red Hat 7.5 64bit, Oracle 7.5 64bit, CentOS 7.5 64bit, and Fedora 28 64bit in External Image File Formats and Supported OSs.
            Added the following content:

            Modified the following content:

            -

            Changed Tools for Windows to Guest OS driver.

            +

            Changed Tools for Windows to Guest OS drivers.

            2018-04-30

            @@ -138,7 +162,7 @@

            Added the following content:

            What Do I Do If I Cannot Create an Image in ZVHD2 Format Using an API?

            Modified the following content:

            -

            Added new OSs supported for external image files, including Fedora 27 64bit and Debian 9.3 64bit in External Image File Formats and Supported OSs.

            +

            Added new OSs supported by external image files, including Fedora 27 64bit and Debian 9.3 64bit in External Image File Formats and Supported OSs.

            2017-12-30

            @@ -157,7 +181,7 @@

            2017-10-30

            Modified the following content:
            • Added the OSs supported for 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 size of the ECS used to create a private image to 1024 GB.

            2017-05-30

            Modified the following content: +
            Modified the following content:

            2017-03-30

            Modified the following content: +
            Modified the following content:

            Added the following content:

            Replicating Images

            -
            Modified the following content:
            • Added CentOS 6.5 64bit, CentOS 6.4 64bit, CentOS 6.3 64bit, and Fedora 25 64bit to the supported OSs of public images.
            • Added the OSs supported for external image files, including Windows Server 2016 Standard 64bit, Windows Server 2016 Datacenter 64bit, SUSE Linux Enterprise Server 12 SP2 64bit, Oracle Linux Server release 6.5 64bit, Oracle Linux Server release 7.3 64bit, Red Hat 6.7 64bit, openSUSE 42.2 64bit, CentOS 7.3 64bit, and Fedora 25 64bit in External Image File Formats and Supported OSs.
            +
            Modified the following content:
            • Added CentOS 6.5 64bit, CentOS 6.4 64bit, CentOS 6.3 64bit, and Fedora 25 64bit to the supported OSs of public images.
            • Added the OSs supported by external image files, including Windows Server 2016 Standard 64bit, Windows Server 2016 Datacenter 64bit, SUSE Linux Enterprise Server 12 SP2 64bit, Oracle Linux Server release 6.5 64bit, Oracle Linux Server release 7.3 64bit, Red Hat 6.7 64bit, openSUSE 42.2 64bit, CentOS 7.3 64bit, and Fedora 25 64bit in External Image File Formats and Supported OSs.

            Added the following content:

            Encrypting Images

            -
            Modified the following content:
            • Added new OSs for public images, including EulerOS 2.2 64bit, CentOS 7.3 64bit, Novell SUSE Enterprise Linux Server 12 SP2 64bit, openSUSE 42.2 64bit, Oracle Linux Server release 7.3 64bit, and Windows Server 2016 Datacenter 64bit.
            • Added new OSs supported for external image files, including SUSE Linux Enterprise Server 12 SP1 64bit, SUSE Linux Enterprise Server 11 SP4 64bit, Oracle Linux Server release 7.0 64bit, Red Hat 7.1 64bit, openSUSE 42.1 64bit, and EulerOS 2.2 64bit in External Image File Formats and Supported OSs.
            +
            Modified the following content:
            • Added new OSs for public images, including EulerOS 2.2 64bit, CentOS 7.3 64bit, Novell SUSE Enterprise Linux Server 12 SP2 64bit, openSUSE 42.2 64bit, Oracle Linux Server release 7.3 64bit, and Windows Server 2016 Datacenter 64bit.
            • Added new OSs supported by external image files, including SUSE Linux Enterprise Server 12 SP1 64bit, SUSE Linux Enterprise Server 11 SP4 64bit, Oracle Linux Server release 7.0 64bit, Red Hat 7.1 64bit, openSUSE 42.1 64bit, and EulerOS 2.2 64bit in External Image File Formats and Supported OSs.
            -
            Table 2 Relationship between IMS operations and native OpenStack APIs

            Operation

            +
            - - diff --git a/docs/ims/umn/en-us_topic_0107462582.html b/docs/ims/umn/en-us_topic_0107462582.html index 8c65f668c..6b1a60f35 100644 --- a/docs/ims/umn/en-us_topic_0107462582.html +++ b/docs/ims/umn/en-us_topic_0107462582.html @@ -4,11 +4,11 @@

            Scenarios

            Once CTS is enabled, it starts recording IMS operations. You can view operations recorded in the last seven days on the CTS management console.

            This section describes how to view the records.

            -

            Procedure

            1. Access the CTS console.
              1. Log in to the management console.
              2. Click Cloud Trace Service under Management & Governance.
              +

              Procedure

              1. Access the CTS console.
                1. Log in to the management console.
                2. Click Cloud Trace Service under Management & Deployment.
              2. In the navigation pane on the left, choose Trace List.
              3. Set the filter criteria and click Query.
                The following filters are available:
                • Trace Type, Trace Source, Resource Type, and Search By.

                  Select Management for Trace Type and IMS for Trace Source.

                  Note that:

                  • If you select Resource ID for Search By, you need to enter a resource ID. Only whole word match is supported.
                  • If you select Resource name for Search By, you need to select or enter a specific resource name.
                  -
                • Operator: Select a specific operator from the drop-down list.
                • Trace Status: Available values are All trace statuses, Normal, Warning, and Incident.
                • Time range: You can select Last 1 hour, Last 1 day, Last 1 week, or Customize.
                +
              4. Operator: Select a specific operator from the drop-down list.
              5. Trace Status: Available values are All trace statuses, Normal, Warning, and Incident.
              6. Time Range: You can select Last 1 hour, Last 1 day, Last 1 week, or Customize.
            2. Locate the target trace and click to expand the trace details.
            3. Click View Trace in the upper right corner of the trace details area.
            diff --git a/docs/ims/umn/en-us_topic_0116125142.html b/docs/ims/umn/en-us_topic_0116125142.html index a2c8fc1ea..760abec29 100644 --- a/docs/ims/umn/en-us_topic_0116125142.html +++ b/docs/ims/umn/en-us_topic_0116125142.html @@ -1,13 +1,13 @@ -

            Creating a Full-ECS Image from an ECS

            -

            Scenarios

            You can create an image of an entire ECS, including not just the OS, but also the software and all the service data. You can then use this image to migrate data by quickly provisioning exact clones of the original ECS.

            +

            Creating a Full-ECS Image from an ECS

            +

            Scenarios

            You can create an image of an entire ECS, including not just the OS, but also the software and all the service data. You can then use this image to migrate data by quickly provisioning exact clones of the original ECS.

            -

            Background

            The following figure shows the process of creating an image from an entire ECS, with both the system and data disks included.

            +

            Background

            The following figure shows the process of creating an image from an entire ECS, with both the system and data disks included.

            Figure 1 Creating a full-ECS image from an ECS
            -
            • The time required for creating a full-ECS image depends on the disk size, network quality, and the number of concurrent tasks.
            • The ECS used to create a full-ECS image must be in Running or Stopped state. To create a full-ECS image containing a database, use a stopped ECS.
            • When a full-ECS image is being created, do not detach the system disk from the ECS or stop, start, or restart the ECS, or the image creation will fail.
            • In Figure 1, if there are snapshots of the system disk and data disks but the ECS backup creation is not complete, the full-ECS image you create will only be available in the AZ where the source ECS is and can only be used to provision ECSs in this AZ. You cannot provision ECSs in other AZs in the region until the original ECS is fully backed up and the full-ECS image is in the Normal state.
            • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
            +
            • The time required for creating a full-ECS image depends on the disk size, network quality, and the number of concurrent tasks.
            • The ECS used to create a full-ECS image must be in Running or Stopped state. To create a full-ECS image containing a database, use a stopped ECS.
            • If an ECS is in Stopped state, do not start it when you are using it to create a full-ECS image.
            • When a full-ECS image is being created, do not detach the system disk from the ECS or stop, start, or restart the ECS, or the image creation will fail.
            • In Figure 1, if there are snapshots of the system disk and data disks but the ECS backup creation is not complete, the full-ECS image you create will only be available in the AZ where the source ECS is and can only be used to provision ECSs in this AZ. You cannot provision ECSs in other AZs in the region until the original ECS is fully backed up and the full-ECS image is in the Normal state.
            • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
            -

            Constraints

            • When creating a full-ECS image from an ECS, ensure that the ECS has been properly configured, or the image creation may fail.
            • A Windows ECS used to create a full-ECS image cannot have a spanned volume, or data may be lost when ECSs are created from that image.
            • A Linux ECS used to create a full-ECS image cannot have a disk group or logical disk that contains multiple physical disks, or data may be lost when ECSs are created from that image.
            • A full-ECS image cannot be exported or replicated.
            • When creating a full-ECS image from 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.

              +

              Constraints

              • When creating a full-ECS image from an ECS, ensure that the ECS has been properly configured, or the image creation may fail.
              • A Windows ECS used to create a full-ECS image cannot have a spanned volume, or data may be lost when ECSs are created from that image.
              • A Linux ECS used to create a full-ECS image cannot have a disk group or logical disk that contains multiple physical disks, or data may be lost when ECSs are created from that image.
              • A full-ECS image cannot be exported or replicated.
              • When creating a full-ECS image from 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 2 Relationship between IMS operations and native OpenStack APIs

            Operation

            Trace Name

            +

            Trace Name

            Service Type

            Resource Type

            +

            Resource Type

            OpenStack Component

            @@ -43,18 +43,19 @@

            Procedure

            1. Access the IMS console.

              1. Log in to the management console.
              2. Under Compute, click Image Management Service.

                The IMS console is displayed.

              -

            2. Create a full-ECS image.

              1. Click Create Image in the upper right corner.
              2. In the Image Type and Source area, select Full-ECS image for Type.
              3. Select ECS for Source and then select an ECS from the list.
                Figure 2 Creating a full-ECS image using an ECS
                +

              4. Create a full-ECS image.

                1. Click Create Image in the upper right corner.
                2. In the Image Type and Source area, select Full-ECS image for Type.
                3. Select ECS for Source and then select an ECS from the list.
                  Figure 2 Creating a full-ECS image using an ECS
                4. Specify Server Backup Vault to store backups.

                  The created full-ECS image and backup are stored in the server backup vault.

                  -

                  If no server backup vault is available, click Create Server Backup Vault to create one. Ensure that you select Backup for Protection Type. For more information about CBR backups and vaults, see Cloud Backup and Recovery User Guide.

                  -
                5. In the Image Information area, configure basic image details, such as the image name and description.
                6. Click Create Now.
                7. Confirm the parameters and click Submit.
                -

              5. Go back to the Private Images page and view the new full-ECS image.

                • When the image status changes to Normal, the image creation is complete.
                • If Available in AZX is displayed under Normal in the Status column for a full-ECS image, the backup for this ECS has not been created and only a disk snapshot is created. (AZX indicates the AZ where the source ECS of the image resides.)

                  In this case, the full-ECS image can be used to provision ECSs only in the specified AZ. If you want to use this image to provision ECSs in other AZs of the region, you need to wait until Available in AZX disappears from under Normal, which indicates that the ECS backup has been successfully created. This process takes about 10 minutes, depending on the data volume of the source ECS.

                  +

                  If no server backup vault is available, click Create Server Backup Vault to create one. Ensure that you select Backup for Protection Type. For more information about CBR backups and vaults, see Cloud Backup and Recovery User Guide.

                  +
                • In the Image Information area, configure basic image details, such as the image name and description.
                • Click Create Now.
                • Confirm the settings and click Submit.
              +

            3. Go back to the Private Images page and view the new full-ECS image.

              • When the image status changes to Normal, the image creation is complete.
              • If Available in AZX is displayed under Normal in the Status column for a full-ECS image, the backup for this ECS has not been created and only a disk snapshot is created. (AZX indicates the AZ where the source ECS of the image resides.)

                In this case, the full-ECS image can be used to provision ECSs only in the specified AZ. If you want to use this image to provision ECSs in other AZs of the region, you need to wait until Available in AZX disappears from under Normal, which indicates that the ECS backup has been successfully created. This process takes about 10 minutes, depending on the data volume of the source ECS.

                Figure 3 Full-ECS image status

            -

            Follow-up Procedure

            • If you want to use the full-ECS image to create ECSs, click Apply for Server in the Operation column. On the displayed page, create ECSs by following the instructions in Elastic Cloud Server User Guide.

              If a full-ECS image contains one or more data disks, the system configures data disk parameters automatically when you use the image to create ECSs.

              +

              Follow-up Procedure

              • If you want to use the full-ECS image to create ECSs, click Apply for Server in the Operation column. On the displayed page, create ECSs by following the instructions in Elastic Cloud Server User Guide.

                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.
                • If the full-ECS image contains multiple data disks, it takes some time to load and display the disk information.
                -
              • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
              +
            • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
            diff --git a/docs/ims/umn/en-us_topic_0117262219.html b/docs/ims/umn/en-us_topic_0117262219.html index 91bd1018e..b6ae5dd98 100644 --- a/docs/ims/umn/en-us_topic_0117262219.html +++ b/docs/ims/umn/en-us_topic_0117262219.html @@ -1,9 +1,33 @@

            Converting the Image Format Using qemu-img

            -

            Scenarios

            You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converted before being imported. The open-source tool qemu-img is provided for you to convert image file formats.

            +

            Scenarios

            You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converted before being imported. The open-source tool qemu-img is provided for you to convert image file formats.

            -

            Background

            • qemu-img supports the mutual conversion of image formats VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, and QED.
            • ZVHD and ZVHD2 are self-developed image file formats and cannot be identified by qemu-img. To convert image files to any of the two formats, use the qemu-img-hw tool. For details, see Converting the Image Format Using qemu-img-hw
            • When you run the command to convert the format of VHD image files, use VPC to replace VHD. Otherwise, qemu-img cannot identify the image format.

              For example, to convert a CentOS 6.9 VHD image file into a QCOW2 image file, run the following command:

              +

              Description

              This section describes how to convert an image format using a Windows or Linux local PC.

              +
              +

              Tool and Costs

              +
            Table 1 SAN policies in Windows

            Type
            + + + + + + + + + +
            Table 1 Tool and costs

            Tool

            +

            Description

            +

            Costs

            +

            qemu-img

            +

            qemu-img is an open-source tool for converting image formats.

            +

            You can obtain it from:

            +

            https://qemu.weilnetz.de/w64/

            +

            Free

            +
            +
            + +

            Constraints

            • qemu-img supports the mutual conversion of image formats VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, and QED.
            • ZVHD and ZVHD2 are self-developed image file formats and cannot be identified by qemu-img. To convert image files to any of the two formats, use the qemu-img-hw tool. For details, see Converting the Image Format Using qemu-img-hw
            • When you run the command to convert the format of VHD image files, use VPC to replace VHD. Otherwise, qemu-img cannot identify the image format.

              For example, to convert a CentOS 6.9 VHD image file into a QCOW2 image file, run the following command:

              qemu-img convert -p -f vpc -O qcow2 centos6.9.vhd centos6.9.qcow2

            @@ -53,7 +77,7 @@ Command syntax: compare [-f fmt] [-F fmt] [-T src_cach]
          • Convert the image format. For example, perform the following steps to convert a VMDK image file running CentOS 7 to a QCOW2 image file:
            1. Run the following command to convert the image file format to QCOW2:

              qemu-img convert -p -f vmdk -O qcow2 centos6.9.vmdk centos6.9.qcow2

              The parameters are described as follows:

              -
              • -p: indicates the conversion progress.
              • -f indicates the source image format.
              • The pat following -O (which must be in upper case) is the converted image format + source image file name + target image file name.
              +
              • -p: indicates the conversion progress.
              • -f indicates the source image format.
              • The pat following -O (which must be in upper case) is the converted image format + source image file name + target image file name.

              After the conversion is complete, the target image file is displayed in the directory where the source image file is located.

              The following information is displayed:

              [root@CentOS7 home]# qemu-img convert -p -f vmdk -O qcow2 centos6.9.vmdk centos6.9.qcow2
@@ -72,8 +96,9 @@ Format specific information:
            • -

            Examples

            A pre-allocated image depends on two files: xxxx.vmdk (configuration file) and xxxx-flat.vmdk (data file) and cannot be directly imported to the cloud platform. When you export a pre-allocated image file in VMDK monolithic Flat format from the VMware platform, you must convert its format to common VMDK or QCOW2 before it can be imported to the cloud platform.

            +

            Examples

            • Scenario

              A pre-allocated image depends on two files: xxxx.vmdk (configuration file) and xxxx-flat.vmdk (data file) and cannot be directly imported to the cloud platform. When you export a pre-allocated image file in VMDK monolithic Flat format from the VMware platform, you must convert its format to common VMDK or QCOW2 before it can be imported to the cloud platform.

              The following uses the image files centos6.9-64bit-flat.vmdk and centos6.9-64bit.vmdk as an example to describe how to use qemu-img to convert image formats.

              +
            • Procedure
            1. Run the following commands to query the image file details:

              ls -lh centos6.9-64bit*

              qemu-img info centos6.9-64bit.vmdk

              qemu-img info centos6.9-64bit-flat.vmdk

              diff --git a/docs/ims/umn/en-us_topic_0122876047.html b/docs/ims/umn/en-us_topic_0122876047.html index 8bf099b6b..82848cb3b 100644 --- a/docs/ims/umn/en-us_topic_0122876047.html +++ b/docs/ims/umn/en-us_topic_0122876047.html @@ -16,7 +16,7 @@
            2. Change the value of PasswordAuthentication in the sshd_config file to no.

              For SUSE and openSUSE, change the values of the following parameters in the sshd_config file to no:

              • PasswordAuthentication
              • ChallengeResponseAuthentication
              -
            3. Run the following command to open the cloud.cfg file using the vi editor:

              vi /etc/cloud/cloud.cfg

              +
            4. Run the following command to open the cloud.cfg file using the vi editor:

              vi /etc/cloud/cloud.cfg

            5. (Optional) In /etc/cloud/cloud.cfg, set apply_network_config to false.

              This step is only for Cloud-Init 18.3 or later.

              Figure 1 Example configuration
            6. Disable the SSH permissions of user root in /etc/cloud/cloud.cfg, add a common user (which is used for logging in to the ECS using VNC), and configure a password for the added user and assign sudo permissions to it.

              For Ubuntu and Debian, set the value of manage_etc_hosts in the /etc/cloud/cloud.cfg file to localhost. Otherwise, switching to user root from a user other than root may time out.

              @@ -48,13 +48,13 @@ distro: rhel # Default user name + that default users groups (if added/used) default_user: - name: linux //Username for login - lock_passwd: False //Login using a password is enabled. Note that some OSs use value 0 to enable the password login. + name: linux #Username for login + lock_passwd: False #Login using a password is enabled. Note that some OSs use value 0 to enable the password login. gecos: Cloud User - groups: users //Optional. Add users to other groups that have been configured in /etc/group. + groups: users #Optional. Add users to other groups that have been configured in /etc/group. passwd: $6$I63DBVKK$Zh4lchiJR7NuZvtJHsYBQJIg5RoQCRLS1X2Hsgj2s5JwXI7KUO1we8WYcwbzeaS2VNpRmNo28vmxxCyU6LwoD0 - sudo: ["ALL=(ALL) NOPASSWD:ALL"] // Assign the root rights to the user. - shell: /bin/bash //Execute shell in bash mode. + sudo: ["ALL=(ALL) NOPASSWD:ALL"] # Assign the root rights to the user. + shell: /bin/bash #Execute shell in bash mode. # Other config here will be given to the distro class and/or path classes paths: cloud_dir: /var/lib/cloud/ @@ -89,26 +89,26 @@ datasource:
              Figure 2 Preventing Cloud-Init from taking over the network
            7. Modify the cloud_init_modules configuration file.

              Move ssh from the bottom to the top to speed up the SSH login.

              Figure 3 Speeding up the SSH login to the ECS
              -
            8. Modify the configuration so that the hostname of the ECS created from the image does not contain the .novalocal suffix and can contain a dot (.).
              1. Run the following command to modify the __init__.py file:

                vi /usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py

                -

                Press i to enter editing mode. Search for toks. The following information is displayed:

                -
                if toks:
+
              2. Modify the configuration so that the hostname of the ECS created from the image does not contain the .novalocal suffix and can contain a dot (.).
                1. Run the following command to modify the __init__.py file:

                  vi /usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py

                  +
                  Press i to enter editing mode. Modify the file content as follows based on the keyword toks:
                  if toks:
     toks = str(toks).split('.')
 else:
-    toks = ["ip-%s" % lhost.replace(".", "-")]
-else:
-    toks = lhost.split(".novalocal")
+    #toks = ["ip-%s" % lhost.replace(".", "-")]  # Comment out this line.
+    toks = lhost.split(".novalocal")  # Add this line.
 
 if len(toks) > 1:
     hostname = toks[0]
-    #domain = '.'.join(toks[1:])
+    #domain = '.'.join(toks[1:])   # Comment out this line.
 else:
     hostname = toks[0]
 
-if fqdn and domain != defdomain:
-    return "%s.%s" % (hostname, domain)
+if fqdn and domain != defdomain:
+    #return hostname   # Comment out this line.
+    return "%s.%s" % (hostname, domain) # Add this line.
 else:
     return hostname
                  -

                  After the modification is complete, press Esc to exit the editing mode and enter :wq! to save the configuration and exit.

                  +
                  +

                  After the modification is complete, press Esc to exit the editing mode and enter :wq! to save the settings and exit.

                  Figure 4 Modifying the __init__.py file
                2. Run the following command to switch to the cloudinit/sources folder:

                  cd /usr/lib/python2.7/site-packages/cloudinit/sources/

                3. Run the following commands to delete the __init__.pyc file and the optimized __init__.pyo file:

                  rm -rf __init__.pyc

                  diff --git a/docs/ims/umn/en-us_topic_0125076462.html b/docs/ims/umn/en-us_topic_0125076462.html index dd5df58aa..09f59cff3 100644 --- a/docs/ims/umn/en-us_topic_0125076462.html +++ b/docs/ims/umn/en-us_topic_0125076462.html @@ -7,6 +7,8 @@

                  echo > /$path/$to/$none-root/.ssh/authorized_keys

                  An example command is echo > /home/linux/.ssh/authorized_keys.

                1. Run the following command to clear log files in the /var/log directory:

                  rm -rf /var/log/*

                  +

                  Before deleting log files, back up log directories and log files required by application startup. For example, if the default Nginx log directory /var/log/nginx is deleted, Nginx may fail to be started.

                  +
                2. Run the following commands to delete historical records:

                  echo > /root/.bash_history

                  history -c

                diff --git a/docs/ims/umn/en-us_topic_0130878749.html b/docs/ims/umn/en-us_topic_0130878749.html index 57e371fa6..4dbce81d4 100644 --- a/docs/ims/umn/en-us_topic_0130878749.html +++ b/docs/ims/umn/en-us_topic_0130878749.html @@ -8,12 +8,14 @@
              3. Viewing the Virtualization Type of a Linux ECS
                4. -
              4. Uninstalling the PV Driver from a Linux ECS
                +
              5. Uninstalling PV Drivers from a Linux ECS
              6. Changing the Disk Identifier in the GRUB Configuration File to UUID
              7. Changing the Disk Identifier in the fstab File to UUID
                8. +
              8. Install the Native Xen and KVM Drivers
                +
              9. Installing Native KVM Drivers
              10. Clearing System Logs
                diff --git a/docs/ims/umn/en-us_topic_0133773658.html b/docs/ims/umn/en-us_topic_0133773658.html index 1f39c973b..30f4f1d17 100644 --- a/docs/ims/umn/en-us_topic_0133773658.html +++ b/docs/ims/umn/en-us_topic_0133773658.html @@ -9,7 +9,7 @@
            -
            • The import of large files depends on lazy loading which defers loading of file data until it is needed. This reduces the initial loading time. However, RAW files do not support this feature. When you upload a RAW file, you need to upload its bitmap together.
            • For details about how to optimize an image file, see Optimization Process or Optimization Process depending on the OS type specified in the image file.
            +
            • The import of large files depends on lazy loading which defers loading of file data until it is needed. This reduces the initial loading time. However, RAW files do not support this feature. When you upload a RAW file, you need to upload its bitmap together.
            • For details about how to optimize an image file, see Optimization Process (Windows) or Optimization Process (Linux) depending on the OS type specified in the image file.

            Import Process

            The following describes how to import an external image file. Assume that you need to convert the file format to ZVHD2 or RAW.

            diff --git a/docs/ims/umn/en-us_topic_0133773660.html b/docs/ims/umn/en-us_topic_0133773660.html index 512a2853c..eb5500e57 100644 --- a/docs/ims/umn/en-us_topic_0133773660.html +++ b/docs/ims/umn/en-us_topic_0133773660.html @@ -81,8 +81,8 @@ Save settings? y (Specifies whethe

            Method 1: Register a private image on the console.

            1. Access the IMS console.
              1. Log in to the management console.
              2. Under Compute, click Image Management Service.

                The IMS console is displayed.

              -
            2. In the upper right corner, click Create Image.
            3. In the Image Type and Source area, select System disk image or Data disk image for Type.
            4. Select Image File for Source. Select the bucket storing the ZVHD2 or RAW image file and then select the image file. If the image file is in the RAW format, you also need to select its bitmap file.
            5. Select Enable Fast Create, and select the sentence following Image File Preparation.
              Figure 1 Quickly importing an image file
              -
            6. Set parameters as prompted.

              For details about the parameters, see Registering an External Image File as a Private Image and Registering an External Image File as a Private Image.

              +
            7. In the upper right corner, click Create Image.
            8. In the Image Type and Source area, select System disk image or Data disk image for Type.
            9. Select Image File for Source. Select the bucket storing the ZVHD2 or RAW image file and then select the image file. If the image file is in the RAW format, you also need to select its bitmap file.
            10. Select Enable Fast Create, and select the sentence following Image File Preparation.
              Figure 1 Quickly importing an image file
              +
            11. Set parameters as prompted.

              For details about the parameters, see Registering an External Image File as a Private Image.

              • The OS must be the same as that in the image file.
              • The system disk size must be greater than the one specified in the image file.

                Run the following command to check the system disk size in the image file:

                qemu-img-hw info test.zvhd2

              @@ -99,7 +99,7 @@ Save settings? y (Specifies whethe

              For example, run the following command to convert a QCOW2 image file to a ZVHD2 file:

              qemu-img-hw convert -p -O zvhd2 test.qcow2 test.zvhd2

            12. Querying image file information: qemu-img-hw info Source image file

              An example command is qemu-img-hw info test.zvhd2.

              -
            13. Viewing help information: qemu-img-hw –help
              14. +
            14. Viewing help information: qemu-img-hw -help

            Appendix 2: Common Errors During qemu-img-hw Running

            • Symptom:
              The following information is displayed when you run the qemu-img-hw command:
              ./qemu-img-hw: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./qemu-img-hw)
              @@ -117,7 +117,7 @@ Save settings? y (Specifies whethe

            make

            make install

            -
          • Symptom:

            The following information is displayed when you run the qemu-img-hw command:

            +
          • Symptom:

            The following information is displayed when you run the qemu-img-hw command:

            ./qemu-img-hw: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory

            Solution: Run the yum install libaio command first.

            • diff --git a/docs/ims/umn/en-us_topic_0133773781.html b/docs/ims/umn/en-us_topic_0133773781.html new file mode 100644 index 000000000..5ab7f980e --- /dev/null +++ b/docs/ims/umn/en-us_topic_0133773781.html @@ -0,0 +1,19 @@ + + +

            How Do I Authorize a Key?

            +

            Scenarios

            To share an encrypted image, you need to authorize the key used for encrypting the image. This section describes how to authorize a key.

            +

            The key can only be a custom key. The default key cannot be authorized.

            +
            +
            +

            Prerequisites

            You have confirmed the key to be authorized. (You can view KMS Key Name on the image details page).

            +
            +

            Procedure

            1. Log in to the management console and choose Security > Key Management Service.
            2. On the Custom Keys tab, click the alias of the target key to go to the key details page.
            3. On the Grants tab, click Create Grant, and set the following parameters.
              • User or Tenant: Select Tenant and enter the tenant ID. You can obtain the tenant ID from Account ID on the My Credentials page.
              • Granted Operations: Decrypt Data Key and Describe Key are mandatory. Others are optional.
              +
            4. Click OK.
            +
            +
            +
            +
            +
            Parent topic: Accounts and Permissions
            +
            +
            + diff --git a/docs/ims/umn/en-us_topic_0148873774.html b/docs/ims/umn/en-us_topic_0148873774.html index bb1158069..fa6fc4913 100644 --- a/docs/ims/umn/en-us_topic_0148873774.html +++ b/docs/ims/umn/en-us_topic_0148873774.html @@ -5,8 +5,11 @@

            Installation Methods

            You are advised to install Cloud-Init or Cloudbase-Init on the ECS to be used to create a private image so that new ECSs created from the private image support custom configurations.

            diff --git a/docs/ims/umn/en-us_topic_0153114116.html b/docs/ims/umn/en-us_topic_0153114116.html index ad69e4fd5..779cac5e7 100644 --- a/docs/ims/umn/en-us_topic_0153114116.html +++ b/docs/ims/umn/en-us_topic_0153114116.html @@ -10,7 +10,7 @@

            How Do I Apply for a Higher Quota?

            The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.

            Before dialing the hotline number or sending an email, make sure that the following information has been obtained:

            -
            • Domain name, project name, and project ID, which can be obtained by performing the following operations:

              Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.

              +
              • Domain name, project name, and project ID, which can be obtained by performing the following operations:

                Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.

              • Quota information, which includes:
                • Service name
                • Quota type
                • Required quota

              Learn how to obtain the service hotline and email address.

              diff --git a/docs/ims/umn/en-us_topic_0165718046.html b/docs/ims/umn/en-us_topic_0165718046.html new file mode 100644 index 000000000..f1633f94c --- /dev/null +++ b/docs/ims/umn/en-us_topic_0165718046.html @@ -0,0 +1,19 @@ + + +

              Why Do I Need to Install and Update VMTools for Windows?

              +

              Why Do I Need to Install VMTools?

              VMTools is a VirtIO driver (para-virtualization driver) that provides high-performance disks and NICs for ECSs.

              +
              • A standard Windows OS does not have the VirtIO driver.
              • Public images have VMTools by default.
              • You need to install VMTools for private images. For details, see Installing UVP VMTools.
              +
              +

              Why Do I Need to Update VMTools?

              The cloud platform periodically synchronizes issue-fixed versions from the VirtIO community and releases updated versions every month. This ensures that known issues identified in the community or R&D tests can be avoided on the latest driver.

              +
              +

              When Do I Need to Update VMTools?

              • If a major error is fixed, you are advised to update VMTools immediately. (Major errors have not occurred by now.) If other issues are fixed, choose whether to update VMTools based on your needs.
              • The cloud platform updates the VMTools stored in an OBS bucket on a regular basis to ensure that you can download the latest version of VMTools for private images.
              • The cloud platform updates public images on a regular basis to ensure that these images have the latest version of VMTools.
              • The document is updated on a regular basis in accordance with VMTools in an OBS bucket to ensure that the download link of VMTools provided in the document is the latest.
              +
              +

              What Do I Need to Do After VMTools Is Updated?

              • Update Windows private images or drivers in running Windows ECSs.
              • If you have any technical issue or question, contact the customer service.
              +
              +
              +
              +
              +
              Parent topic: Image Optimization
              +
              +
              + diff --git a/docs/ims/umn/en-us_topic_0170853315.html b/docs/ims/umn/en-us_topic_0170853315.html index b1a03be01..56c8515e9 100644 --- a/docs/ims/umn/en-us_topic_0170853315.html +++ b/docs/ims/umn/en-us_topic_0170853315.html @@ -1,12 +1,12 @@

              OSs Supporting UEFI Boot Mode

              -

              The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?

              +

              The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?.

              Table 1 lists the OSs that support the UEFI boot mode.

              - diff --git a/docs/ims/umn/en-us_topic_0171668652.html b/docs/ims/umn/en-us_topic_0171668652.html index f6d03be49..02914d44d 100644 --- a/docs/ims/umn/en-us_topic_0171668652.html +++ b/docs/ims/umn/en-us_topic_0171668652.html @@ -3,22 +3,44 @@

              Converting the Image Format Using qemu-img-hw

              Scenarios

              You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converted into any of these formats using the open-source tool qemu-img before being imported. However, the qemu-img tool cannot convert image files to the ZVHD or ZVHD2 format. To convert image files to any of the two formats, use the self-developed tool qemu-img-hw. This section describes how to use qemu-img-hw to convert an image file to ZVHD2.

              -

              Background

              qemu-img-hw can be used only in Linux. You can run it on a local Linux server or a Linux ECS on the cloud platform. The following procedure uses an EulerOS ECS as an example.

              +

              Tool and Costs

              +
              Table 1 OSs supporting UEFI boot mode

              OS

              OS Version

              +

              Version
              + + + + + + + + + +
              Table 1 Tool and costs

              Tool

              +

              Description

              +

              Costs

              +

              qemu-img-hw

              +

              qemu-img-hw is developed by Huawei and is used for converting image formats.

              +

              You can obtain it from:

              +

              https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip

              +

              Free

              +
              -

              Procedure

              1. Upload the image file to be converted to the ECS.
                • If the local host runs a Linux OS, run the scp command.

                  For example, to upload image01.qcow2 to the /usr/ directory on the ECS, run the following command:

                  +
              +

              Constraints

              qemu-img-hw can be used only in Linux. You can run it on a local Linux server or a Linux ECS on the cloud platform. The following procedure uses an EulerOS ECS as an example.

              +
              +

              Procedure

              1. Upload the image file to be converted to the ECS.
                • If the local host runs a Linux OS, run the scp command.

                  For example, to upload image01.qcow2 to the /usr/ directory of the ECS, run the following command:

                  scp /var/image01.qcow2 root@xxx.xxx.xx.xxx:/usr/

                  xxx.xxx.xx.xxx indicates the EIP bound to the ECS.

                • If the local host runs a Windows OS, use a file transfer tool, such as WinSCP, to upload the image file to the ECS.
              2. Obtain the qemu-img-hw software package, upload it to the ECS, and then decompress the package. -
                Table 1 qemu-img-hw package

                Tool Package

                +
                - - - diff --git a/docs/ims/umn/en-us_topic_0172473649.html b/docs/ims/umn/en-us_topic_0172473649.html new file mode 100644 index 000000000..1a4ee5713 --- /dev/null +++ b/docs/ims/umn/en-us_topic_0172473649.html @@ -0,0 +1,30 @@ + + +

                Replicating a Shared Image

                +

                Scenarios

                Replicate a private image that was shared with you. The image is displayed in the private image list. You can export, share, and replicate this image, or use it to create ECSs.

                +

                If the shared image to be replicated is an encrypted image, you can replace the key of the image with your own key when replicating the image. This prevents the shared image from being unavailable when the tenant who shares the image cancels the key authorization.

                +
                +

                Constraints

                • Only accepted shared images can be replicated.

                  To replicate a rejected shared image, you must accept the image first. For details, see Accepting Rejected Images.

                  +
                • Currently, only system and data disk images can be replicated. Full-ECS images are not supported.
                • Currently, images can only be replicated within a region.
                • An image to be replicated cannot be larger than 128 GB.
                +
                +

                Procedure

                1. Access the IMS console.
                  1. Log in to the management console.
                  2. Under Compute, click Image Management Service.

                    The IMS console is displayed.

                    +
                  +
                2. On the displayed IMS console, click the Images Shared with Me tab.

                  Shared images that are accepted are displayed.

                  +
                3. Locate a shared image, click More in the Operation column, and select Replicate from the drop-down list.
                  Figure 1 Replicating an image
                  +
                4. In the Replicate Image dialog box, specify Name, Enterprise Project, and Description.
                5. Click OK.

                  You can click the Private Images tab and view the creation progress of the image in the private image list. When the image status changes to Normal, the image creation is complete.

                  +
                +
                +
                +
                +
                +
                Parent topic: Sharing Images
                +
                +
                + + + \ No newline at end of file diff --git a/docs/ims/umn/en-us_topic_0174703579.html b/docs/ims/umn/en-us_topic_0174703579.html index dd2cd72ff..b81fe44d7 100644 --- a/docs/ims/umn/en-us_topic_0174703579.html +++ b/docs/ims/umn/en-us_topic_0174703579.html @@ -8,7 +8,7 @@
              3. An OBS bucket has been created on the management console, and OBS Browser has been ready.
                4. -

                Procedure

                1. Install the open-source tool qemu-img.
                2. Run the cmd command to go to the qemu-img installation directory and run the qemu-img command to convert the image file to the RAW format.

                  For example, run the following command to convert an image.qcow2 file to an image.raw file:

                  +

                  Procedure

                  1. Install the open-source image conversion tool qemu-img.
                  2. Run the cmd command to go to the qemu-img installation directory and run the qemu-img command to convert the image file to the RAW format.

                    For example, run the following command to convert an image.qcow2 file to an image.raw file:

                    qemu-img convert -p -O raw image.qcow2 image.raw

                  3. Use CreateMF.jar to generate a bitmap file.

                    1. Obtain the CreateMF.jar package and decompress it.
                Table 2 qemu-img-hw package

                Tool Package

                How to Obtain

                +

                How to Obtain

                quick-import-tools

                +

                quick-import-tools

                https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip

                +

                https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip
                - @@ -40,7 +41,7 @@ - diff --git a/docs/ims/umn/en-us_topic_0205273057.html b/docs/ims/umn/en-us_topic_0205273057.html new file mode 100644 index 000000000..03c78567e --- /dev/null +++ b/docs/ims/umn/en-us_topic_0205273057.html @@ -0,0 +1,15 @@ + + +

                Accounts and Permissions

                +
                +
                + + +
                +
                Parent topic: FAQs
                +
                +
                + diff --git a/docs/ims/umn/public_sys-resources/commonrtl.css b/docs/ims/umn/public_sys-resources/commonrtl.css new file mode 100644 index 000000000..f261da752 --- /dev/null +++ b/docs/ims/umn/public_sys-resources/commonrtl.css @@ -0,0 +1,2 @@ +/*! Copyright (c) Huawei Technologies Co., Ltd. 2020-2022. All rights reserved. */.msgph{font-family:Courier New}.unresolved{background-color:#87ceeb}.noTemplate{background-color:#ff0}.base{background-color:#fff}/*! Add space for top level topics */.nested0,.p{margin-top:1em}/*! div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid *//*! Default of italics to set apart figure captions */.figcap,.italic,.var{font-style:italic}.figdesc{font-style:normal}/*! Use @frame to create frames on figures */.figborder{padding-left:3px;padding-right:3px;margin-top:1em;border:2px solid Silver}.figsides{margin-top:1em;padding-left:3px;padding-right:3px;border-left:2px solid Silver;border-right:2px solid Silver}.figtop{border-top:2px solid Silver;margin-top:1em}.figbottom{border-bottom:2px solid Silver}.figtopbot{border-top:2px solid Silver;border-bottom:2px solid Silver;margin-top:1em}/*! Most link groups are created with
                . Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式 +*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre} \ No newline at end of file diff --git a/docs/ims/umn/public_sys-resources/icon-arrowdn.gif b/docs/ims/umn/public_sys-resources/icon-arrowdn.gif index 84eec9be2..379428032 100644 Binary files a/docs/ims/umn/public_sys-resources/icon-arrowdn.gif and b/docs/ims/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/ims/umn/public_sys-resources/icon-arrowrt.gif b/docs/ims/umn/public_sys-resources/icon-arrowrt.gif index 39583d168..6aaaa11c2 100644 Binary files a/docs/ims/umn/public_sys-resources/icon-arrowrt.gif and b/docs/ims/umn/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/ims/umn/public_sys-resources/imageclose.gif b/docs/ims/umn/public_sys-resources/imageclose.gif index 56818c26b..3a3344af4 100644 Binary files a/docs/ims/umn/public_sys-resources/imageclose.gif and b/docs/ims/umn/public_sys-resources/imageclose.gif differ diff --git a/docs/ims/umn/public_sys-resources/imageclosehover.gif b/docs/ims/umn/public_sys-resources/imageclosehover.gif index 3bcf231f1..8699d5e36 100644 Binary files a/docs/ims/umn/public_sys-resources/imageclosehover.gif and b/docs/ims/umn/public_sys-resources/imageclosehover.gif differ diff --git a/docs/ims/umn/public_sys-resources/imagemax.gif b/docs/ims/umn/public_sys-resources/imagemax.gif index 49fe390b1..99c07dc25 100644 Binary files a/docs/ims/umn/public_sys-resources/imagemax.gif and b/docs/ims/umn/public_sys-resources/imagemax.gif differ diff --git a/docs/ims/umn/public_sys-resources/imagemaxhover.gif b/docs/ims/umn/public_sys-resources/imagemaxhover.gif index 387b0a981..d01d77d6e 100644 Binary files a/docs/ims/umn/public_sys-resources/imagemaxhover.gif and b/docs/ims/umn/public_sys-resources/imagemaxhover.gif differ diff --git a/docs/ims/umn/public_sys-resources/macFFBgHack.png b/docs/ims/umn/public_sys-resources/macFFBgHack.png index c6473b324..ec811470c 100644 Binary files a/docs/ims/umn/public_sys-resources/macFFBgHack.png and b/docs/ims/umn/public_sys-resources/macFFBgHack.png differ
                Table 1 CreateMF.jar package

                Tool Package

                @@ -36,8 +36,8 @@

                Method 1: Register a private image on the console.

                1. Access the IMS console.
                  1. Log in to the management console.
                  2. Under Compute, click Image Management Service.

                    The IMS console is displayed.

                  -
                2. In the upper right corner, click Create Image.
                3. In the Image Type and Source area, select System disk image or Data disk image for Type.
                4. Select Image File for Source. Select the bucket storing the ZVHD2 or RAW image file and then select the image file. If the image file is in the RAW format, you also need to select its bitmap file.
                5. Select Enable Fast Create, and select the sentence following Image File Preparation.
                  Figure 1 Quickly importing an image file
                  -
                6. Set parameters as prompted.

                  For details about the parameters, see Registering an External Image File as a Private Image and Registering an External Image File as a Private Image.

                  +
                7. In the upper right corner, click Create Image.
                8. In the Image Type and Source area, select System disk image or Data disk image for Type.
                9. Select Image File for Source. Select the bucket storing the ZVHD2 or RAW image file and then select the image file. If the image file is in the RAW format, you also need to select its bitmap file.
                10. Select Enable Fast Create, and select the sentence following Image File Preparation.
                  Figure 1 Quickly importing an image file
                  +
                11. Set parameters as prompted.

                  For details about the parameters, see Registering an External Image File as a Private Image.

                  • The OS must be the same as that in the image file.
                  • The system disk size must be greater than the one specified in the image file.

                    Run the following command to check the system disk size in the image file:

                    qemu-img-hw info test.zvhd2

                  diff --git a/docs/ims/umn/en-us_topic_0176812699.html b/docs/ims/umn/en-us_topic_0176812699.html index 1cf20f531..f7036f5ab 100644 --- a/docs/ims/umn/en-us_topic_0176812699.html +++ b/docs/ims/umn/en-us_topic_0176812699.html @@ -1,22 +1,23 @@

                  Creating a Full-ECS Image from a CBR Backup

                  -

                  Scenarios

                  You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.

                  +

                  Scenarios

                  You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.

                  -

                  Background

                  • The Cloud Backup and Recovery (CBR) service provides backup services for EVS disks, ECSs, and BMSs, and supports restoring data of servers and disks using backups. If you have created a backup for an ECS using CBR, you can use the backup to create a full-ECS image.
                  • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
                  +

                  Background

                  • The Cloud Backup and Recovery (CBR) service provides backup services for EVS disks, ECSs, and BMSs, and supports restoring data of servers and disks using backups. If you have created a backup for an ECS using CBR, you can use the backup to create a full-ECS image.
                  • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
                  -

                  Constraints

                  • When creating a full-ECS image from a CBR backup, ensure that the source ECS of the CBR backup has been properly configured, or the image creation may fail.
                  • A CBR backup can be used to create only one full-ECS image.
                  • A full-ECS image created from a CBR backup can be shared with other tenants. However, if it is a shared CBR backup, the full-ECS image created from it cannot be shared.
                  • A full-ECS image cannot be exported or replicated.
                  +

                  Constraints

                  • When creating a full-ECS image from a CBR backup, ensure that the source ECS of the CBR backup has been properly configured, or the image creation may fail.
                  • A CBR backup can be used to create only one full-ECS image.
                  • If an ECS is in Stopped state, do not start it when you are using it to create a full-ECS image.
                  • A full-ECS image created from a CBR backup can be shared with other tenants. However, if it is a shared CBR backup, the full-ECS image created from it cannot be shared.
                  • A full-ECS image cannot be exported or replicated.

                  Procedure

                  1. Access the IMS console.

                    1. Log in to the management console.
                    2. Under Compute, click Image Management Service.

                      The IMS console is displayed.

                    -

                  2. Create a full-ECS image.

                    1. Click Create Image in the upper right corner.
                    2. In the Image Type and Source area, select Full-ECS image for Type.
                    3. Select Cloud Server Backup for Source and then select a backup from the list.
                    4. In the Image Information area, configure basic image details, such as the image name and description.
                    5. Click Create Now.
                    6. Confirm the parameters and click Submit.
                    +

                  3. Create a full-ECS image.

                    1. Click Create Image in the upper right corner.
                    2. In the Image Type and Source area, select Full-ECS image for Type.
                    3. Select Cloud Server Backup for Source and then select a backup from the list.
                    4. In the Image Information area, configure basic image details, such as the image name and description.
                    5. Click Create Now.
                    6. Confirm the settings and click Submit.

                  4. Switch back to the Image Management Service page to monitor the image status.

                    When the image status changes to Normal, the image creation is complete.

                  Follow-up Procedure

                  After the full-ECS image creation is complete, you can perform the following operations:

                  -
                  • If you want to use the image to create ECSs, click Apply for Server in the Operation column. On the displayed page, select Private image and then select the created full-ECS image. For details, see Elastic Cloud Server User Guide.

                    If a full-ECS image contains one or more data disks, the system configures data disk parameters automatically when you use the image to create ECSs.

                    +
                    • If you want to use the image to create ECSs, click Apply for Server in the Operation column. On the displayed page, select Private image and then select the created full-ECS image. For details, see Elastic Cloud Server User Guide.

                      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.
                      • If the full-ECS image contains multiple data disks, it takes some time to load and display the disk information.
                      -
                    • If you want to share the image with other tenants, click More in the Operation column and select Share from the drop-down list. In the displayed dialog box, enter the project IDs of the image recipients. For details, see Sharing Specified Images.
                    +
                  • If you want to share the image with other tenants, click More in the Operation column and select Share from the drop-down list. In the displayed dialog box, enter the project IDs of the image recipients. For details, see Sharing Specified Images.
                  • If you use a full-ECS image to change an ECS OS, only the system disk data can be written into the ECS. Therefore, if you want to restore or migrate the data disk data of an ECS by using a full-ECS image, you can only use the image to create a new ECS rather than use it to change the ECS OS.
                  diff --git a/docs/ims/umn/en-us_topic_0183293890.html b/docs/ims/umn/en-us_topic_0183293890.html index c0f078f8b..530aa4496 100644 --- a/docs/ims/umn/en-us_topic_0183293890.html +++ b/docs/ims/umn/en-us_topic_0183293890.html @@ -1,7 +1,7 @@

                  Image Sharing FAQs

                  -

                  How Many Tenants Can I Share an Image with?

                  128

                  +

                  How Many Tenants Can I Share an Image with?

                  A system disk image or data disk image can be shared with up to 256 tenants, but a full-ECS image can only be shared with up to 10 tenants.

                  How Many Images Can Be Shared with Me?

                  There is no limit.

                  @@ -9,6 +9,8 @@

                  I Shared an Image to an Account But the Account Did Not Accept or Reject the Image. Will My Image Sharing Quota Be Consumed?

                  No.

                  +

                  Can I Share Images Shared with Me with Other Tenants?

                  You cannot directly share such images with other tenants. If you do need to do so, you can replicate a shared image to a private image and then share the private image.

                  +

                  Can I Use an Image I Have Shared with Others to Create an ECS?

                  Yes. After sharing an image with other tenants, you can still use the image to create an ECS and use the created ECS to create a private image.

                  When Can I Do If I Want to Use a Rejected Image?

                  If you have rejected an image shared by another tenant, but now want to use it, two methods are available:

                  diff --git a/docs/ims/umn/en-us_topic_0187108863.html b/docs/ims/umn/en-us_topic_0187108863.html index 376f99b13..073468c5a 100644 --- a/docs/ims/umn/en-us_topic_0187108863.html +++ b/docs/ims/umn/en-us_topic_0187108863.html @@ -1,7 +1,7 @@

                  How Do I Make a System Disk Image Support Fast ECS Creation?

                  -

                  Scenarios

                  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. Some existing system disk images may not support this feature, you can make them support it through image replication.

                  +

                  Scenarios

                  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. Some existing system disk images may not support this feature, you can make them support it through image replication.

                  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 configured using this method.

                  @@ -10,7 +10,7 @@
              4. Click the Private Images tab to display the image list.
              5. Click the name of the target image.
              6. On the displayed image details page, check the value of Fast ECS Creation.
                7. -

                Configure an Image to Make It Support Fast ECS Creation

                1. Locate the target system disk image, click More in the Operation column, and select Replicate from the drop-down list.

                  The Replicate Image dialog box is displayed.

                  +

                  Configure an Image to Make It Support Fast ECS Creation

                  1. Locate the target system disk image, click More in the Operation column, and select Replicate from the drop-down list.

                    The Replicate Image dialog box is displayed.

                  2. Set parameters based on Replicating Images.
                  3. After the image is successfully replicated, the generated image can be used to quickly create ECSs.
                diff --git a/docs/ims/umn/en-us_topic_0199451475.html b/docs/ims/umn/en-us_topic_0199451475.html index 250a95093..e02c5cb3d 100644 --- a/docs/ims/umn/en-us_topic_0199451475.html +++ b/docs/ims/umn/en-us_topic_0199451475.html @@ -17,12 +17,13 @@

                Maximum file size: 128 GB

                During the import, operations such as driver injection will be performed in the background. Therefore, the import takes a longer time than fast import.

                -                		 + +

                Fast import

                When importing an external image file in the RAW or ZVHD2 format to the management console, you can select Enable Fast Create. The system does not perform any operations such as driver injection. Verify that:

                +

                When importing an external image file in the RAW or ZVHD2 format to the management console, you can select Enable Fast Create. The system does not perform any operations such as driver injection. Verify that:

                • The image file converted to the RAW format has been optimized as required and a bitmap file has been generated for it.
                • The image file converted to the ZVHD2 format has been optimized as required.

                Maximum file size: 1 TB

                Fast export

                On the Export Image page, select Enable following Fast Export. You cannot specify the format of the exported image file. After the export is complete, you can use a tool to convert the exported image to your desired format.

                +

                On the Export Image page, select Enable following Fast Export. You cannot specify the format of the exported image file. After the export is complete, you can use a tool to convert the exported image to your desired format.

                The file size is not limited.

                Encrypted images do not support fast export.