diff --git a/docs/ims/umn/ALL_META.TXT.json b/docs/ims/umn/ALL_META.TXT.json index ddda995b..5d99986d 100644 --- a/docs/ims/umn/ALL_META.TXT.json +++ b/docs/ims/umn/ALL_META.TXT.json @@ -70,7 +70,7 @@ "node_id":"en-us_topic_0053967838.xml", "product_code":"ims", "code":"4", - "des":"Migrating servers to the cloud or on the cloudYou can import local images to the cloud platform and use the images to quickly create cloud servers for service migration t", + "des":"Migrating servers to the cloud or on the cloudYou can import local images in various formats such as VHD, VMDK, QCOW2, and RAW to the cloud platform and use the images to", "doc_type":"usermanual", "kw":"Application Scenarios,Overview,User Guide", "search_title":"", @@ -448,7 +448,7 @@ "node_id":"en-us_topic_0030713189.xml", "product_code":"ims", "code":"22", - "des":"You need to prepare an image file that meets the platform requirements.You are advised to complete the network, tool, and driver configurations in Table 1 on the source V", + "des":"You need to prepare an image file that can be used to create a private image.Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In", "doc_type":"usermanual", "kw":"Preparing an Image File,Creating a Windows System Disk Image from an External Image File,User Guide", "search_title":"", @@ -574,7 +574,7 @@ "node_id":"en-us_topic_0030713198.xml", "product_code":"ims", "code":"28", - "des":"You need to prepare an image file that meets the platform requirements.You are advised to complete the file system, network, and driver configurations in Table 1 on the s", + "des":"You need to prepare an image file that can be used to create a private image.Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In", "doc_type":"usermanual", "kw":"Preparing an Image File,Creating a Linux System Disk Image from an External Image File,User Guide", "search_title":"", @@ -763,7 +763,7 @@ "node_id":"en-us_topic_0176812699.xml", "product_code":"ims", "code":"37", - "des":"You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.The CBR service provides backup services for EVS disks, ", + "des":"You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.CBR provides the backup service for EVS disks, BMSs, and", "doc_type":"usermanual", "kw":"Use backup to create image,full-ECS image,Creating a Full-ECS Image from a CBR Backup,Creating a Pri", "search_title":"", @@ -826,9 +826,9 @@ "node_id":"en-us_topic_0146474781.xml", "product_code":"ims", "code":"40", - "des":"A Windows system with the Integrated Drive Electronics (IDE) hard drive and Virtio NIC is used on the cloud. Therefore, you need to integrate the VMTools driver into the ", + "des":"Windows uses IDE disks and VirtIO NICs. Before registering an image on the cloud platform, integrate VirtIO drivers into the Windows ISO file. Typically, an ISO file cont", "doc_type":"usermanual", - "kw":"Integrating the VMTools Driver into an ISO File,Creating a Windows System Disk Image from an ISO Fil", + "kw":"Integrating VirtIO Drivers into an ISO File,Creating a Windows System Disk Image from an ISO File,Us", "search_title":"", "metedata":[ { @@ -839,7 +839,7 @@ "IsMulti":"Yes" } ], - "title":"Integrating the VMTools Driver into an ISO File", + "title":"Integrating VirtIO Drivers into an ISO File", "githuburl":"" }, { @@ -847,7 +847,7 @@ "node_id":"en-us_topic_0146474782.xml", "product_code":"ims", "code":"41", - "des":"Register an external ISO file on the cloud platform as a private image (ISO image). Before registering an image, upload the ISO file exported in Integrating the VMTools D", + "des":"Register an external ISO file on the cloud platform as a private image (ISO image). Before registering an image, upload the ISO file exported in Integrating VirtIO Driver", "doc_type":"usermanual", "kw":"Registering an ISO File as an ISO Image,Creating a Windows System Disk Image from an ISO File,User G", "search_title":"", @@ -889,9 +889,9 @@ "node_id":"en-us_topic_0146474784.xml", "product_code":"ims", "code":"43", - "des":"This section uses Windows Server 2008 R2 64-bit as an example to describe how to install Windows on an ECS.The installation procedure varies depending on the image file y", + "des":"This section uses Windows Server 2019 64-bit as an example to describe how to install Windows on an ECS.The installation procedure varies depending on the image file you ", "doc_type":"usermanual", - "kw":"Installing a Windows OS and the VMTools Driver,Creating a Windows System Disk Image from an ISO File", + "kw":"Installing a Windows OS and VirtIO Drivers,Creating a Windows System Disk Image from an ISO File,Use", "search_title":"", "metedata":[ { @@ -902,7 +902,7 @@ "IsMulti":"Yes" } ], - "title":"Installing a Windows OS and the VMTools Driver", + "title":"Installing a Windows OS and VirtIO Drivers", "githuburl":"" }, { @@ -910,7 +910,7 @@ "node_id":"en-us_topic_0146480985.xml", "product_code":"ims", "code":"44", - "des":"After installing an OS for the temporary ECS, configure the ECS and install the Guest OS drivers provided by the cloud platform to ensure that ECSs created subsequently a", + "des":"After installing an OS for the temporary ECS, configure the ECS and install Guest OS drivers provided by the cloud platform so that ECSs that will be created with this te", "doc_type":"usermanual", "kw":"Configuring the ECS and Creating a Windows System Disk Image,Creating a Windows System Disk Image fr", "search_title":"", @@ -1036,7 +1036,7 @@ "node_id":"en-us_topic_0146480990.xml", "product_code":"ims", "code":"50", - "des":"After installing an OS for the temporary ECS, configure the ECS and install the native Xen and KVM drivers to ensure that ECSs created subsequently are available.This sec", + "des":"After installing an OS for the temporary ECS, configure the ECS and install KVM drivers to ensure that ECSs created from this temporary ECS can work properly.This sectio", "doc_type":"usermanual", "kw":"Configuring the ECS and Creating a Linux System Disk Image,Creating a Linux System Disk Image from a", "search_title":"", @@ -1059,7 +1059,7 @@ "code":"51", "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":"Quickly Importing an Image File", + "kw":"Fast Import of an Image File", "search_title":"", "metedata":[ { @@ -1070,7 +1070,7 @@ "IsMulti":"Yes" } ], - "title":"Quickly Importing an Image File", + "title":"Fast Import of an Image File", "githuburl":"" }, { @@ -1078,9 +1078,9 @@ "node_id":"en-us_topic_0133773658.xml", "product_code":"ims", "code":"52", - "des":"If an image file is larger than 128 GB, you can import it using fast import. Only the RAW and ZVHD2 formats support fast import. The image file to be imported cannot exce", + "des":"If an image file is larger than 128 GB, you can import it using fast import.The image file must be in RAW or ZVHD2 format.The image file size cannot exceed 1 TB.You can i", "doc_type":"usermanual", - "kw":"Overview,Quickly Importing an Image File,User Guide", + "kw":"Overview,Fast Import of an Image File,User Guide", "search_title":"", "metedata":[ { @@ -1099,9 +1099,9 @@ "node_id":"en-us_topic_0133773660.xml", "product_code":"ims", "code":"53", - "des":"This section describes how to convert the format of an image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an EulerOS EC", + "des":"This section describes how to convert the format of a large image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an Euler", "doc_type":"usermanual", - "kw":"Quickly Importing an Image File (Linux),Quickly Importing an Image File,User Guide", + "kw":"Fast Import in Linux,Fast Import of an Image File,User Guide", "search_title":"", "metedata":[ { @@ -1112,7 +1112,7 @@ "IsMulti":"Yes" } ], - "title":"Quickly Importing an Image File (Linux)", + "title":"Fast Import in Linux", "githuburl":"" }, { @@ -1122,7 +1122,7 @@ "code":"54", "des":"This section describes how to convert the format of an image file on a Windows server and then quickly import it to the cloud platform. You are advised to use a local Win", "doc_type":"usermanual", - "kw":"Quickly Importing an Image File (Windows),Quickly Importing an Image File,User Guide", + "kw":"Fast Import in Windows,Fast Import of an Image File,User Guide", "search_title":"", "metedata":[ { @@ -1133,7 +1133,7 @@ "IsMulti":"Yes" } ], - "title":"Quickly Importing an Image File (Windows)", + "title":"Fast Import in Windows", "githuburl":"" }, { @@ -1162,9 +1162,9 @@ "node_id":"en-us_topic_0030713199.xml", "product_code":"ims", "code":"56", - "des":"You can modify the following attributes of a private image:NameDescriptionMinimum MemoryMaximum MemoryNIC Multi-QueueNIC multi-queue enables multiple CPUs to process NIC ", + "des":"You can modify the following attributes of a private image:NameDescriptionMinimum memoryMaximum memoryNIC multi-queueNIC multi-queue enables multiple CPUs to process NIC ", "doc_type":"usermanual", - "kw":"Change,Image name,Image memory,NIC multi-queue,Name,Description,Minimum Memory,Maximum Memory,NIC Mu", + "kw":"Change,Image name,Image memory,NIC multi-queue,Name,Description,Minimum memory,Maximum memory,NIC mu", "search_title":"", "metedata":[ { @@ -1540,7 +1540,7 @@ "node_id":"en-us_topic_0047501112.xml", "product_code":"ims", "code":"74", - "des":"The proper running of ECSs depends on KVM Guest OS driver (UVP VMTools). To ensure that ECSs support KVM and to improve network performance, the UVP VMTools must be insta", + "des":"An ECS can run properly only after KVM Guest OS drivers (VirtIO drivers) are installed on it. To ensure that ECSs support KVM and to improve network performance, VirtIO d", "doc_type":"usermanual", "kw":"Optimization Process,Optimizing a Windows Private Image,User Guide", "search_title":"", @@ -1561,9 +1561,9 @@ "node_id":"en-us_topic_0037352059.xml", "product_code":"ims", "code":"75", - "des":"Table 1 lists the UVP VMTools software packages required for optimizing Windows private images.", + "des":"Download a VirtIO driver package from:https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/You can select a version as needed.", "doc_type":"usermanual", - "kw":"UVP VMTools,Obtaining Required Software Packages,Optimizing a Windows Private Image,User Guide", + "kw":"Obtaining Required Software Packages,Optimizing a Windows Private Image,User Guide", "search_title":"", "metedata":[ { @@ -1578,24 +1578,21 @@ "githuburl":"" }, { - "uri":"en-us_topic_0037352061.html", - "node_id":"en-us_topic_0037352061.xml", + "uri":"en-us_topic_0000001841305273.html", + "node_id":"en-us_topic_0000001841305273.xml", "product_code":"ims", "code":"76", - "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", + "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 VirtIO dri", "doc_type":"usermanual", - "kw":"UVP VMTools,KVM virtualization,UVP VMTools,Citrix Xen Tools and,Installing UVP VMTools,Optimizing a ", + "kw":"Installing VirtIO Drivers,Optimizing a Windows Private Image,User Guide", "search_title":"", "metedata":[ { "prodname":"ims", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes", - "IsMulti":"Yes" + "documenttype":"usermanual" } ], - "title":"Installing UVP VMTools", + "title":"Installing VirtIO Drivers", "githuburl":"" }, { @@ -1603,7 +1600,7 @@ "node_id":"en-us_topic_0125075472.xml", "product_code":"ims", "code":"77", - "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", + "des":"After installing PV and VirtIO drivers, perform the following operations to clear system logs:For Windows Server 2008 and Windows Server 2012, right-click Computer and se", "doc_type":"usermanual", "kw":"Clearing System Logs,Optimizing a Windows Private Image,User Guide", "search_title":"", @@ -1794,7 +1791,7 @@ "code":"86", "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. For details, see", "doc_type":"usermanual", - "kw":"image encryption,Overview,Encrypting Images,User Guide", + "kw":"image encryption,Encrypted images,Overview,Encrypting Images,User Guide", "search_title":"", "metedata":[ { @@ -1834,7 +1831,7 @@ "node_id":"en-us_topic_0049177180.xml", "product_code":"ims", "code":"88", - "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", + "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 image replication. You m", "doc_type":"usermanual", "kw":"replicate an image,Replicating Images,Managing Private Images,User Guide", "search_title":"", @@ -1918,7 +1915,7 @@ "node_id":"en-us_topic_0107462582.xml", "product_code":"ims", "code":"92", - "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 ", + "des":"After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records generated in the last seven d", "doc_type":"usermanual", "kw":"Viewing Traces,Auditing Key Operations,User Guide", "search_title":"", @@ -2191,7 +2188,7 @@ "node_id":"en-us_topic_0122876047.xml", "product_code":"ims", "code":"105", - "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", + "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 ECS obtains its IP", "doc_type":"usermanual", "kw":"Cloud-Init,Configuring Cloud-Init,Linux Operations,User Guide", "search_title":"", @@ -2212,7 +2209,7 @@ "node_id":"en-us_topic_0082002007.xml", "product_code":"ims", "code":"106", - "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 ", + "des":"Before using a private image to create GPU-accelerated ECSs, install a GPU driver for the image.There are two types of GPU drivers: GRID and Tesla.To use graphics acceler", "doc_type":"usermanual", "kw":"Installing Special Linux Drivers,Linux Operations,User Guide", "search_title":"", @@ -2506,7 +2503,7 @@ "node_id":"en-us_topic_0049196766.xml", "product_code":"ims", "code":"120", - "des":"You can back up the ECS in any of the following ways:(Recommended) Use CBR to create a scheduled backup task for the ECS. If the ECS fails, select a backup corresponding ", + "des":"You can back up the ECS in any of the following ways:(Recommended) Use CBR to create a scheduled backup for the ECS. If the ECS fails, select a backup you want to use to ", "doc_type":"usermanual", "kw":"How Can I Back Up the Current Status of an ECS for Restoration in the Case of a System Fault?,Image ", "search_title":"", @@ -2527,7 +2524,7 @@ "node_id":"en-us_topic_0069896389.xml", "product_code":"ims", "code":"121", - "des":"You can change the OS of the ECS later. When you change the OS, select the created private image. For details about how to change the OS, see \"Changing the OS\" in Elastic", + "des":"You can use the image to change the ECS OS. When you change the OS, select that image. For details about how to change the OS, see \"Changing the OS\" in Elastic Cloud Serv", "doc_type":"usermanual", "kw":"How Can I Apply a Private Image to an Existing ECS?,Image Consulting,User Guide", "search_title":"", @@ -2569,9 +2566,9 @@ "node_id":"en-us_topic_0173986473.xml", "product_code":"ims", "code":"123", - "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.", + "des":"Yes.You can use the private images other accounts shared with you.For details, see Sharing Specified Images.", "doc_type":"usermanual", - "kw":"Can I Use Private Images of Other Tenants?,Image Consulting,User Guide", + "kw":"Can I Use Private Images of Other Accounts?,Image Consulting,User Guide", "search_title":"", "metedata":[ { @@ -2582,7 +2579,7 @@ "IsMulti":"Yes" } ], - "title":"Can I Use Private Images of Other Tenants?", + "title":"Can I Use Private Images of Other Accounts?", "githuburl":"" }, { @@ -2613,7 +2610,7 @@ "code":"125", "des":"If you have an ECS with applications deployed, you can use the ECS to create a private image and then use the image to create identical ECSs. In this way, you do not need", "doc_type":"usermanual", - "kw":"Image Creation FAQs,Image Creation,User Guide", + "kw":"General Creation FAQs,Image Creation,User Guide", "search_title":"", "metedata":[ { @@ -2624,7 +2621,7 @@ "IsMulti":"Yes" } ], - "title":"Image Creation FAQs", + "title":"General Creation FAQs", "githuburl":"" }, { @@ -2695,7 +2692,7 @@ "node_id":"en-us_topic_0106444267.xml", "product_code":"ims", "code":"129", - "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", + "des":"You are not advised to use a Windows ECS that has a spanned volume to create a full-ECS image. If you create such an image and then use it to create new ECSs, data may be", "doc_type":"usermanual", "kw":"How Do I Create a Full-ECS Image Using an ECS That Has a Spanned Volume?,Image Creation,User Guide", "search_title":"", @@ -2716,7 +2713,7 @@ "node_id":"en-us_topic_0030742197.xml", "product_code":"ims", "code":"130", - "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", + "des":"Sysprep is used to generalize images. It removes server-specific information, like the security identifier (SID), from an image so that ECSs created from this image can h", "doc_type":"usermanual", "kw":"Why Is Sysprep Required for Creating a Private Image from a Windows ECS?,Image Creation,User Guide", "search_title":"", @@ -2737,9 +2734,9 @@ "node_id":"en-us_topic_0030713206.xml", "product_code":"ims", "code":"131", - "des":"After Sysprep is executed, the following message is displayed when you start the ECS.Message displayedThen, the following information is displayed in the dialog box:Windo", + "des":"When you start the ECS, information similar to the following is displayed.Message displayedThen, the following information is displayed in the dialog box:Windows could no", "doc_type":"usermanual", - "kw":"What Do I Do If an ECS Created from a Windows Image Failed to Start After Running Sysprep?,Image Cre", + "kw":"How Do I Handle the Startup Failure of a Windows ECS Created from a Windows Image Generalized by Sys", "search_title":"", "metedata":[ { @@ -2750,7 +2747,7 @@ "IsMulti":"Yes" } ], - "title":"What Do I Do If an ECS Created from a Windows Image Failed to Start After Running Sysprep?", + "title":"How Do I Handle the Startup Failure of a Windows ECS Created from a Windows Image Generalized by Sysprep?", "githuburl":"" }, { @@ -2800,9 +2797,9 @@ "node_id":"en-us_topic_0183293890.xml", "product_code":"ims", "code":"134", - "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.Switch ", + "des":"128A 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.Swit", "doc_type":"usermanual", - "kw":"Image Sharing FAQs,Image Sharing,User Guide", + "kw":"General Sharing FAQs,Image Sharing,User Guide", "search_title":"", "metedata":[ { @@ -2813,7 +2810,7 @@ "IsMulti":"Yes" } ], - "title":"Image Sharing FAQs", + "title":"General Sharing FAQs", "githuburl":"" }, { @@ -2844,7 +2841,7 @@ "code":"136", "des":"Some images cannot be shared. Therefore, the Share option is not provided for them in the Operation column. The following images cannot be shared:Encrypted imagesFull-ECS", "doc_type":"usermanual", - "kw":"What Do I Do If I Cannot Share My Images?,Image Sharing,User Guide", + "kw":"Why Can't I Share My Images?,Image Sharing,User Guide", "search_title":"", "metedata":[ { @@ -2855,7 +2852,7 @@ "IsMulti":"Yes" } ], - "title":"What Do I Do If I Cannot Share My Images?", + "title":"Why Can't I Share My Images?", "githuburl":"" }, { @@ -2884,7 +2881,7 @@ "node_id":"en-us_topic_0030713223.xml", "product_code":"ims", "code":"138", - "des":"LinuxUsed for development platforms or services that run Linux. CentOS and Ubuntu are provided. CentOS is recommended.The system disk must be no less than 40 GB, and the ", + "des":"LinuxUsed for development platforms or services that run Linux. CentOS and Ubuntu are provided. CentOS is recommended.The system disk must be at least 40 GB, and there mu", "doc_type":"usermanual", "kw":"How Do I Select an OS?,OS,User Guide", "search_title":"", @@ -2921,32 +2918,11 @@ "title":"How Is BIOS Different from UEFI?", "githuburl":"" }, - { - "uri":"en-us_topic_0093842586.html", - "node_id":"en-us_topic_0093842586.xml", - "product_code":"ims", - "code":"140", - "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", - "search_title":"", - "metedata":[ - { - "prodname":"ims", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes", - "IsMulti":"Yes" - } - ], - "title":"How Do I Install the NVIDIA Driver on a P1 ECS?", - "githuburl":"" - }, { "uri":"en-us_topic_0106312064.html", "node_id":"en-us_topic_0106312064.xml", "product_code":"ims", - "code":"141", + "code":"140", "des":"Press Win+R. In the displayed dialog box, enter regedit and press Enter to open the registry editor.Modifying a registry may cause a system startup failure. So, back up t", "doc_type":"usermanual", "kw":"How Do I Delete Redundant Network Connections from a Windows ECS?,OS,User Guide", @@ -2967,7 +2943,7 @@ "uri":"en-us_topic_0117142739.html", "node_id":"en-us_topic_0117142739.xml", "product_code":"ims", - "code":"142", + "code":"141", "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", @@ -2988,7 +2964,7 @@ "uri":"en-us_topic_0081802526.html", "node_id":"en-us_topic_0081802526.xml", "product_code":"ims", - "code":"143", + "code":"142", "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", @@ -3009,7 +2985,7 @@ "uri":"en-us_topic_0290353431.html", "node_id":"en-us_topic_0290353431.xml", "product_code":"ims", - "code":"144", + "code":"143", "des":"The possible cause is the incompatible boot modes.If a private image is created from an ECS configured for BIOS boot or if you use an external image file to create such a", "doc_type":"usermanual", "kw":"Why Can't I Find My Private Image When I Want to Use It to Create an ECS or Change the OS of an ECS?", @@ -3030,10 +3006,10 @@ "uri":"en-us_topic_0030713195.html", "node_id":"en-us_topic_0030713195.xml", "product_code":"ims", - "code":"145", + "code":"144", "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", + "kw":"Image Import", "search_title":"", "metedata":[ { @@ -3044,17 +3020,17 @@ "IsMulti":"Yes" } ], - "title":"Image Importing", + "title":"Image Import", "githuburl":"" }, { "uri":"en-us_topic_0030713217.html", "node_id":"en-us_topic_0030713217.xml", "product_code":"ims", - "code":"146", - "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", + "code":"145", + "des":"No. Currently, only VMDK, VHD, RAW, QCOW2, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD formats are supported.Images in -flat.vmdk format and image file packages containing snap", "doc_type":"usermanual", - "kw":"Can I Use Images in Formats Other Than the Specified Ones?,Image Importing,User Guide", + "kw":"Can I Use Images in Formats not Described in This Document?,Image Import,User Guide", "search_title":"", "metedata":[ { @@ -3065,17 +3041,17 @@ "IsMulti":"Yes" } ], - "title":"Can I Use Images in Formats Other Than the Specified Ones?", + "title":"Can I Use Images in Formats not Described in This Document?", "githuburl":"" }, { "uri":"en-us_topic_0030713216.html", "node_id":"en-us_topic_0030713216.xml", "product_code":"ims", - "code":"147", + "code":"146", "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", + "kw":"What Are the Impacts If I Do Not Pre-configure an ECS Used to Create a Private Image?,Image Import,U", "search_title":"", "metedata":[ { @@ -3093,10 +3069,10 @@ "uri":"en-us_topic_0118990097.html", "node_id":"en-us_topic_0118990097.xml", "product_code":"ims", - "code":"148", - "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 ", + "code":"147", + "des":"Open Virtualization Appliance (OVA) is a single file archive (with the .ova extension) of all of the files comprising an Open Virtualization Format (OVF) package. OVF is ", "doc_type":"usermanual", - "kw":"How Do I Import an OVF or OVA File to the Cloud Platform?,Image Importing,User Guide", + "kw":"How Do I Import an OVF or OVA File to the Cloud Platform?,Image Import,User Guide", "search_title":"", "metedata":[ { @@ -3114,10 +3090,10 @@ "uri":"en-us_topic_0030713213.html", "node_id":"en-us_topic_0030713213.xml", "product_code":"ims", - "code":"149", - "des":"If you selected an incorrect OS, ECSs may fail to be created from the private image. If the configured system disk capacity is less than the one in the image file, image ", + "code":"148", + "des":"If you selected the wrong OS, the ECS creation may fail when the image is used.If the system disk capacity you configured is less than the one in the image file, image re", "doc_type":"usermanual", - "kw":"What Do I Do If I Configured an Incorrect OS or System Disk Capacity During Private Image Registrati", + "kw":"What Do I Do If I Chose the Wrong OS or System Disk Capacity When Registering a Private Image?,Image", "search_title":"", "metedata":[ { @@ -3128,17 +3104,17 @@ "IsMulti":"Yes" } ], - "title":"What Do I Do If I Configured an Incorrect OS or System Disk Capacity During Private Image Registration Using an Image File?", + "title":"What Do I Do If I Chose the Wrong OS or System Disk Capacity When Registering a Private Image?", "githuburl":"" }, { "uri":"en-us_topic_0058841396.html", "node_id":"en-us_topic_0058841396.xml", "product_code":"ims", - "code":"150", - "des":"The possible causes may be:You have specified a small value.Check the system disk capacity in the VHD image file. Specify a value no less than this value when you use the", + "code":"149", + "des":"The possible causes may be:Too small a value was specified when registering the image. Check the system disk capacity in the VHD image file. Specify a value at least this", "doc_type":"usermanual", - "kw":"What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the", + "kw":"Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger ", "search_title":"", "metedata":[ { @@ -3149,17 +3125,17 @@ "IsMulti":"Yes" } ], - "title":"What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?", + "title":"Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger Than What I Specified on the Management Console?", "githuburl":"" }, { "uri":"en-us_topic_0030713222.html", "node_id":"en-us_topic_0030713222.xml", "product_code":"ims", - "code":"151", + "code":"150", "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", + "kw":"Image Export", "search_title":"", "metedata":[ { @@ -3170,17 +3146,17 @@ "IsMulti":"Yes" } ], - "title":"Image Exporting", + "title":"Image Export", "githuburl":"" }, { "uri":"en-us_topic_0249675952.html", "node_id":"en-us_topic_0249675952.xml", "product_code":"ims", - "code":"152", - "des":"Yes. You can download private images in VMDK, VHD, QCOW2, or ZVHD format as instructed in Exporting an Image.", + "code":"151", + "des":"Yes. You can download private images as instructed in Exporting an Image.Currently, only images in VMDK, VHD, QCOW2, or ZVHD format can be exported.The default format of ", "doc_type":"usermanual", - "kw":"Can I Download My Private Images to a Local PC?,Image Exporting,User Guide", + "kw":"Can I Download My Private Images to a Local PC?,Image Export,User Guide", "search_title":"", "metedata":[ { @@ -3198,8 +3174,8 @@ "uri":"en-us_topic_0030713153.html", "node_id":"en-us_topic_0030713153.xml", "product_code":"ims", - "code":"153", - "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", + "code":"152", + "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. So, it cannot be used on a BMS", "doc_type":"usermanual", "kw":"Can I Use the System Disk Image of an ECS on a BMS After I Export It from the Cloud Platform?,Image ", "search_title":"", @@ -3219,10 +3195,10 @@ "uri":"en-us_topic_0274352601.html", "node_id":"en-us_topic_0274352601.xml", "product_code":"ims", - "code":"154", - "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", + "code":"153", + "des":"When 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 G", "doc_type":"usermanual", - "kw":"Why Is the Image Size in an OBS Bucket Different from That Displayed in IMS?,Image Exporting,User Gu", + "kw":"Why Is the Image Size in an OBS Bucket Different from That Displayed in IMS?,Image Export,User Guide", "search_title":"", "metedata":[ { @@ -3240,10 +3216,10 @@ "uri":"en-us_topic_0030713186.html", "node_id":"en-us_topic_0030713186.xml", "product_code":"ims", - "code":"155", - "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 ", + "code":"154", + "des":"You cannot directly download a public image. However, you can use the public image to create an ECS, use the ECS to create a private image, export the private image to yo", "doc_type":"usermanual", - "kw":"Can I Download a Public Image to My Local PC?,Image Exporting,User Guide", + "kw":"Can I Download a Public Image to My PC?,Image Export,User Guide", "search_title":"", "metedata":[ { @@ -3254,17 +3230,17 @@ "IsMulti":"Yes" } ], - "title":"Can I Download a Public Image to My Local PC?", + "title":"Can I Download a Public Image to My PC?", "githuburl":"" }, { "uri":"en-us_topic_0199451475.html", "node_id":"en-us_topic_0199451475.xml", "product_code":"ims", - "code":"156", + "code":"155", "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", + "kw":"What Are the Differences Between Import/Export and Fast Import/Export?,Image Export,User Guide", "search_title":"", "metedata":[ { @@ -3282,10 +3258,10 @@ "uri":"en-us_topic_0199396601.html", "node_id":"en-us_topic_0199396601.xml", "product_code":"ims", - "code":"157", - "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", + "code":"156", + "des":"Some images cannot be exported. So, the Export option is not provided for them in the Operation column. The following images cannot be exported:Public imagesFull-ECS imag", "doc_type":"usermanual", - "kw":"What Do I Do If the Export Option Is Unavailable for My Image?,Image Exporting,User Guide", + "kw":"Why the Export Option Is Unavailable for My Image?,Image Export,User Guide", "search_title":"", "metedata":[ { @@ -3296,14 +3272,14 @@ "IsMulti":"Yes" } ], - "title":"What Do I Do If the Export Option Is Unavailable for My Image?", + "title":"Why the Export Option Is Unavailable for My Image?", "githuburl":"" }, { "uri":"en-us_topic_0030713203.html", "node_id":"en-us_topic_0030713203.xml", "product_code":"ims", - "code":"158", + "code":"157", "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", @@ -3324,7 +3300,7 @@ "uri":"en-us_topic_0030713214.html", "node_id":"en-us_topic_0030713214.xml", "product_code":"ims", - "code":"159", + "code":"158", "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", @@ -3345,10 +3321,10 @@ "uri":"en-us_topic_0165718046.html", "node_id":"en-us_topic_0165718046.xml", "product_code":"ims", - "code":"160", - "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", + "code":"159", + "des":"VirtIO drivers are paravirtualized drivers that provide high-performance disks and NICs for ECSs.Windows does not have VirtIO drivers installed by default.Public images h", "doc_type":"usermanual", - "kw":"Why Do I Need to Install and Update VMTools for Windows?,Image Optimization,User Guide", + "kw":"Why Do I Need to Install and Update VirtIO Drivers for Windows?,Image Optimization,User Guide", "search_title":"", "metedata":[ { @@ -3359,14 +3335,14 @@ "IsMulti":"Yes" } ], - "title":"Why Do I Need to Install and Update VMTools for Windows?", + "title":"Why Do I Need to Install and Update VirtIO Drivers for Windows?", "githuburl":"" }, { "uri":"en-us_topic_0032307025.html", "node_id":"en-us_topic_0032307025.xml", "product_code":"ims", - "code":"161", + "code":"160", "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", @@ -3387,10 +3363,10 @@ "uri":"en-us_topic_0040740508.html", "node_id":"en-us_topic_0040740508.xml", "product_code":"ims", - "code":"162", + "code":"161", "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", + "kw":"How Do I Configure an ECS, a BMS, or an Image File Before I Use It to Create an Image?,Image Optimiz", "search_title":"", "metedata":[ { @@ -3401,15 +3377,15 @@ "IsMulti":"Yes" } ], - "title":"How Do I Configure an ECS, BMS, or Image File Before I Use It to Create an Image?", + "title":"How Do I Configure an ECS, a BMS, or an Image File Before I Use It to Create an Image?", "githuburl":"" }, { "uri":"en-us_topic_0030713185.html", "node_id":"en-us_topic_0030713185.xml", "product_code":"ims", - "code":"163", - "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 ", + "code":"162", + "des":"If an image file is not configured as instructed in Table 1 before it is exported from the original platform, you can use it to create an ECS, configure the ECS, and use ", "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", "search_title":"", @@ -3429,8 +3405,8 @@ "uri":"en-us_topic_0030713211.html", "node_id":"en-us_topic_0030713211.xml", "product_code":"ims", - "code":"164", - "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 ", + "code":"163", + "des":"If an image file is not configured as instructed in Table 1 before it is exported from the original platform, you can use it to create an ECS, configure the ECS, and use ", "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?,", "search_title":"", @@ -3450,8 +3426,8 @@ "uri":"en-us_topic_0085214115.html", "node_id":"en-us_topic_0085214115.xml", "product_code":"ims", - "code":"165", - "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", + "code":"164", + "des":"Network I/O bandwidth can keep increasing to the point where a single vCPU cannot process all of the NIC interrupts. NIC multi-queue allows multiple vCPUs to process NIC ", "doc_type":"usermanual", "kw":"How Do I Enable NIC Multi-Queue for an Image?,Image Optimization,User Guide", "search_title":"", @@ -3471,10 +3447,10 @@ "uri":"en-us_topic_0129883696.html", "node_id":"en-us_topic_0129883696.xml", "product_code":"ims", - "code":"166", + "code":"165", "des":"IPv6 addresses are used to deal with IPv4 address exhaustion. If an ECS uses an IPv4 address, the ECS can run in dual-stack mode after IPv6 is enabled for it. Then, the E", "doc_type":"usermanual", - "kw":"How Do I Configure an ECS to Dynamically Acquire IPv6 Addresses?,Image Optimization,User Guide", + "kw":"How Do I Configure an ECS to Use DHCPv6?,Image Optimization,User Guide", "search_title":"", "metedata":[ { @@ -3485,15 +3461,15 @@ "IsMulti":"Yes" } ], - "title":"How Do I Configure an ECS to Dynamically Acquire IPv6 Addresses?", + "title":"How Do I Configure an ECS to Use DHCPv6?", "githuburl":"" }, { "uri":"en-us_topic_0187108863.html", "node_id":"en-us_topic_0187108863.xml", "product_code":"ims", - "code":"167", - "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 ", + "code":"166", + "des":"Fast Create greatly reduces the time required to create ECSs from a system disk image. Currently, this feature is supported for all newly created system disk images by de", "doc_type":"usermanual", "kw":"How Do I Make a System Disk Image Support Fast ECS Creation?,Image Optimization,User Guide", "search_title":"", @@ -3513,10 +3489,10 @@ "uri":"en-us_topic_0030713215.html", "node_id":"en-us_topic_0030713215.xml", "product_code":"ims", - "code":"168", - "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 ", + "code":"167", + "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 Guest OS drivers of ", "doc_type":"usermanual", - "kw":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?,Image Optimization,U", + "kw":"Why Did I Fail to Install Guest OS Drivers on a Windows ECS?,Image Optimization,User Guide", "search_title":"", "metedata":[ { @@ -3527,15 +3503,15 @@ "IsMulti":"Yes" } ], - "title":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?", + "title":"Why Did I Fail to Install Guest OS Drivers on a Windows ECS?", "githuburl":"" }, { "uri":"en-us_topic_0183293891.html", "node_id":"en-us_topic_0183293891.xml", "product_code":"ims", - "code":"169", - "des":"In-region replicationThis is used for conversion between encrypted and unencrypted images or for enabling advanced features (such as fast ECS creation) for images. For de", + "code":"168", + "des":"In-region replicationThis is used for conversion between encrypted and unencrypted images or for enabling advanced features (such as fast ECS creation). For details, see ", "doc_type":"usermanual", "kw":"Image Replication,FAQs,User Guide", "search_title":"", @@ -3555,8 +3531,8 @@ "uri":"en-us_topic_0032326546.html", "node_id":"en-us_topic_0032326546.xml", "product_code":"ims", - "code":"170", - "des":"No. Private images created using ECSs are stored in OBS buckets. Deleting the ECS used to create a private image does not affect the image.Yes. You can delete a shared im", + "code":"169", + "des":"No. Private images created using ECSs are stored in OBS buckets. Deleting the ECSs does not affect the images.If an image is shared with a project, you can delete the ima", "doc_type":"usermanual", "kw":"Image Deletion,FAQs,User Guide", "search_title":"", @@ -3576,8 +3552,8 @@ "uri":"en-us_topic_0049196765.html", "node_id":"en-us_topic_0049196765.xml", "product_code":"ims", - "code":"171", - "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 ", + "code":"170", + "des":"You can select an encryption key when you replicate the image. Then, the system will generate an encrypted version of the unencrypted image.", "doc_type":"usermanual", "kw":"Image Encryption,FAQs,User Guide", "search_title":"", @@ -3597,7 +3573,7 @@ "uri":"en-us_topic_0205273057.html", "node_id":"en-us_topic_0205273057.xml", "product_code":"ims", - "code":"172", + "code":"171", "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", @@ -3618,7 +3594,7 @@ "uri":"en-us_topic_0133773781.html", "node_id":"en-us_topic_0133773781.xml", "product_code":"ims", - "code":"173", + "code":"172", "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", @@ -3639,7 +3615,7 @@ "uri":"en-us_topic_0138479468.html", "node_id":"en-us_topic_0138479468.xml", "product_code":"ims", - "code":"174", + "code":"173", "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", @@ -3660,7 +3636,7 @@ "uri":"en-us_topic_0132216287.html", "node_id":"en-us_topic_0132216287.xml", "product_code":"ims", - "code":"175", + "code":"174", "des":"You are advised to install Cloud-Init on the ECS that will be used to create a private image so that new ECSs created from the private image support custom configurations", "doc_type":"usermanual", "kw":"Cloud-Init Installation FAQ,Cloud-Init,User Guide", @@ -3681,8 +3657,8 @@ "uri":"en-us_topic_0148873774.html", "node_id":"en-us_topic_0148873774.xml", "product_code":"ims", - "code":"176", - "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", + "code":"175", + "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 customize initia", "doc_type":"usermanual", "kw":"What Can I Do with a Cloud-Init ECS?,Cloud-Init,User Guide", "search_title":"", @@ -3702,10 +3678,10 @@ "uri":"en-us_topic_0113992021.html", "node_id":"en-us_topic_0113992021.xml", "product_code":"ims", - "code":"177", - "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", + "code":"176", + "des":"One likely possibility is that the version of Cloud-Init is incompatible with that of NetworkManager. In Debian 9.0 and later versions, NetworkManager is incompatible wit", "doc_type":"usermanual", - "kw":"What Do I Do If Injecting the Key or Password Using Cloud-Init Failed After NetworkManager Is Instal", + "kw":"What Do I Do If Installed NetworkManager and Now I Can't Inject the Key or Password Using Cloud-Init", "search_title":"", "metedata":[ { @@ -3716,15 +3692,15 @@ "IsMulti":"Yes" } ], - "title":"What Do I Do If Injecting the Key or Password Using Cloud-Init Failed After NetworkManager Is Installed?", + "title":"What Do I Do If Installed NetworkManager and Now I Can't Inject the Key or Password Using Cloud-Init?", "githuburl":"" }, { "uri":"en-us_topic_0078454810.html", "node_id":"en-us_topic_0078454810.xml", "product_code":"ims", - "code":"178", - "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", + "code":"177", + "des":"For SUSE and openSUSE, growpart is an independent tool and is not included in a cloud-* package. You need to install it separately.Check whether Cloud-Init and growpart a", "doc_type":"usermanual", "kw":"How Do I Install growpart for SUSE 11 SP4?,Cloud-Init,User Guide", "search_title":"", @@ -3744,7 +3720,7 @@ "uri":"en-us_topic_0030713220.html", "node_id":"en-us_topic_0030713220.xml", "product_code":"ims", - "code":"179", + "code":"178", "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", @@ -3765,8 +3741,8 @@ "uri":"en-us_topic_0030713208.html", "node_id":"en-us_topic_0030713208.xml", "product_code":"ims", - "code":"180", - "des":"Yes.If you have selected an incorrect image or your service requirements have changed, you can change the image of your ECS.You can change the image type (public, private", + "code":"179", + "des":"Yes.If you have selected the wrong image or your service requirements have changed, you can change the image of your ECS.You can change the image type (public, private, a", "doc_type":"usermanual", "kw":"Can I Change the Image of a Purchased ECS?,ECS Creation,User Guide", "search_title":"", @@ -3786,10 +3762,10 @@ "uri":"en-us_topic_0030713209.html", "node_id":"en-us_topic_0030713209.xml", "product_code":"ims", - "code":"181", - "des":"Yes. You can specify the CPU, memory, bandwidth, data disks of the new ECSs if necessary. You can also specify their system disk capacity. The value must be smaller than ", + "code":"180", + "des":"Yes. You can specify the CPU, memory, bandwidth, system and data disks of the ECS you are creating. The system disk must be smaller than 1,024 GB but no less than the sys", "doc_type":"usermanual", - "kw":"Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to", + "kw":"Can I Change the Specifications Defined by a Private Image When I Use the Image to Create an ECS?,EC", "search_title":"", "metedata":[ { @@ -3800,15 +3776,15 @@ "IsMulti":"Yes" } ], - "title":"Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to Create the Private Image?", + "title":"Can I Change the Specifications Defined by a Private Image When I Use the Image to Create an ECS?", "githuburl":"" }, { "uri":"en-us_topic_0030713221.html", "node_id":"en-us_topic_0030713221.xml", "product_code":"ims", - "code":"182", - "des":"Yes. However, the value must be smaller than 30,768 GB but no less than the system disk capacity in the image.Ensure that your ECS OS supports the system disk capacity yo", + "code":"181", + "des":"Yes, but you cannot create a system disk smaller than the original and the maximum allowed is 30,768 GB.Ensure that your ECS OS can support the system disk size you speci", "doc_type":"usermanual", "kw":"Can I Specify the System Disk Capacity When I Create an ECS Using an Image?,ECS Creation,User Guide", "search_title":"", @@ -3828,10 +3804,10 @@ "uri":"en-us_topic_0034220644.html", "node_id":"en-us_topic_0034220644.xml", "product_code":"ims", - "code":"183", - "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 ", + "code":"182", + "des":"Disk partition IDs are changed after the cross-platform image import. As a result, no partition can be found at startup. In this case, you need to change disk partition I", "doc_type":"usermanual", - "kw":"What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private ", + "kw":"What Do I Do If a Partition Is Not Found During the Startup of an ECS Created from an Imported Priva", "search_title":"", "metedata":[ { @@ -3842,17 +3818,17 @@ "IsMulti":"Yes" } ], - "title":"What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private Image?", + "title":"What Do I Do If a Partition Is Not Found During the Startup of an ECS Created from an Imported Private Image?", "githuburl":"" }, { "uri":"en-us_topic_0113403127.html", "node_id":"en-us_topic_0113403127.xml", "product_code":"ims", - "code":"184", - "des":"This issue is probably caused by the failure of offline VirtIO driver injection.When you inject VirtIO drivers for a Windows ECS offline, there are some restrictions:If t", + "code":"183", + "des":"This may be caused by an issue with offline VirtIO driver injection.When you inject VirtIO drivers into the image for a Windows ECS, note that:If the boot mode in the ima", "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", + "kw":"What Do I Do If I Enabled Automatic Configuration During Image Registration for an ECS Created from ", "search_title":"", "metedata":[ { @@ -3863,17 +3839,17 @@ "IsMulti":"Yes" } ], - "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?", + "title":"What Do I Do If I Enabled Automatic Configuration During Image Registration for an ECS Created from a Windows Image and Now It Won't Start?", "githuburl":"" }, { "uri":"en-us_topic_0161870891.html", "node_id":"en-us_topic_0161870891.xml", "product_code":"ims", - "code":"185", - "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", + "code":"184", + "des":"An ECS created from a private image booting to UEFI cannot start.The image is configured for UEFI boot, but the uefi attribute was not added to the image.Delete the ECS t", "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", + "kw":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using UEFI Boot?,ECS C", "search_title":"", "metedata":[ { @@ -3884,14 +3860,14 @@ "IsMulti":"Yes" } ], - "title":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mode?", + "title":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using UEFI Boot?", "githuburl":"" }, { "uri":"en-us_topic_0000001397367656.html", "node_id":"en-us_topic_0000001397367656.xml", "product_code":"ims", - "code":"186", + "code":"185", "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":"Driver Installation", @@ -3912,7 +3888,7 @@ "uri":"en-us_topic_0000001397535494.html", "node_id":"en-us_topic_0000001397535494.xml", "product_code":"ims", - "code":"187", + "code":"186", "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?,Driver Installation,User Guide", @@ -3933,10 +3909,10 @@ "uri":"en-us_topic_0000001447895377.html", "node_id":"en-us_topic_0000001447895377.xml", "product_code":"ims", - "code":"188", - "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", + "code":"187", + "des":"VirtIO drivers are paravirtualized drivers that provide high-performance disks and NICs for ECSs.Windows does not have VirtIO drivers installed by default.Public images h", "doc_type":"usermanual", - "kw":"Why Do I Need to Install and Update VMTools for Windows?,Driver Installation,User Guide", + "kw":"Why Do I Need to Install and Update VirtIO Drivers for Windows?,Driver Installation,User Guide", "search_title":"", "metedata":[ { @@ -3947,17 +3923,17 @@ "IsMulti":"Yes" } ], - "title":"Why Do I Need to Install and Update VMTools for Windows?", + "title":"Why Do I Need to Install and Update VirtIO Drivers for Windows?", "githuburl":"" }, { "uri":"en-us_topic_0000001447815605.html", "node_id":"en-us_topic_0000001447815605.xml", "product_code":"ims", - "code":"189", - "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 ", + "code":"188", + "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 Guest OS drivers of ", "doc_type":"usermanual", - "kw":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?,Driver Installation,", + "kw":"Why Did I Fail to Install Guest OS Drivers on a Windows ECS?,Driver Installation,User Guide", "search_title":"", "metedata":[ { @@ -3968,17 +3944,17 @@ "IsMulti":"Yes" } ], - "title":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?", + "title":"Why Did I Fail to Install Guest OS Drivers on a Windows ECS?", "githuburl":"" }, { "uri":"en-us_topic_0000001398100610.html", "node_id":"en-us_topic_0000001398100610.xml", "product_code":"ims", - "code":"190", - "des":"This only applies to KVM ECSs. 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 subseq", + "code":"189", + "des":"The installation only applies to KVM ECSs.Before using an ECS or external image file to create a private image, ensure that VirtIO drivers have been installed in the OS s", "doc_type":"usermanual", - "kw":"UVP VMTools,KVM virtualization,How Do I Install UVP VMTools in Windows?,Driver Installation,User Gui", + "kw":"VirtIO drivers,KVM virtualization,How Do I Install VirtIO Drivers in Windows?,Driver Installation,Us", "search_title":"", "metedata":[ { @@ -3989,14 +3965,14 @@ "IsMulti":"Yes" } ], - "title":"How Do I Install UVP VMTools in Windows?", + "title":"How Do I Install VirtIO Drivers in Windows?", "githuburl":"" }, { "uri":"en-us_topic_0000001398260514.html", "node_id":"en-us_topic_0000001398260514.xml", "product_code":"ims", - "code":"191", + "code":"190", "des":"When optimizing a Linux private image, you need to install native KVM drivers on the ECS from which the image will be created. If you ECS already has native KVM drivers i", "doc_type":"usermanual", "kw":"native KVM drivers,How Do I Install Native KVM Drivers in Linux?,Driver Installation,User Guide", @@ -4017,7 +3993,7 @@ "uri":"en-us_topic_0000001397207656.html", "node_id":"en-us_topic_0000001397207656.xml", "product_code":"ims", - "code":"192", + "code":"191", "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 Tags", @@ -4038,7 +4014,7 @@ "uri":"en-us_topic_0000001398583638.html", "node_id":"en-us_topic_0000001398583638.xml", "product_code":"ims", - "code":"193", + "code":"192", "des":"An image can have a maximum of 10 tags.", "doc_type":"usermanual", "kw":"How Many Tags Can I Add to an Image?,Image Tags,User Guide", @@ -4059,7 +4035,7 @@ "uri":"en-us_topic_0000001398421074.html", "node_id":"en-us_topic_0000001398421074.xml", "product_code":"ims", - "code":"194", + "code":"193", "des":"When adding predefined tags to an image or searching for an image using predefined tags, you must have permission to access the Tag Management Service (TMS).Access the IM", "doc_type":"usermanual", "kw":"How Do I Add, Delete, and Modify Image Tags?,Image Tags,User Guide", @@ -4080,7 +4056,7 @@ "uri":"en-us_topic_0000001398423666.html", "node_id":"en-us_topic_0000001398423666.xml", "product_code":"ims", - "code":"195", + "code":"194", "des":"When adding predefined tags to an image or searching for an image using predefined tags, you must have permission to access the Tag Management Service (TMS).Access the IM", "doc_type":"usermanual", "kw":"How Do I Search for Private Images by Tag?,Image Tags,User Guide", @@ -4101,7 +4077,7 @@ "uri":"en-us_topic_0041178787.html", "node_id":"en-us_topic_0041178787.xml", "product_code":"ims", - "code":"196", + "code":"195", "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", @@ -4122,7 +4098,7 @@ "uri":"en-us_topic_0047898081.html", "node_id":"en-us_topic_0047898081.xml", "product_code":"ims", - "code":"197", + "code":"196", "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 d1e59851..52f701f1 100644 --- a/docs/ims/umn/CLASS.TXT.json +++ b/docs/ims/umn/CLASS.TXT.json @@ -27,7 +27,7 @@ "code":"3" }, { - "desc":"Migrating servers to the cloud or on the cloudYou can import local images to the cloud platform and use the images to quickly create cloud servers for service migration t", + "desc":"Migrating servers to the cloud or on the cloudYou can import local images in various formats such as VHD, VMDK, QCOW2, and RAW to the cloud platform and use the images to", "product_code":"ims", "title":"Application Scenarios", "uri":"en-us_topic_0053967838.html", @@ -189,7 +189,7 @@ "code":"21" }, { - "desc":"You need to prepare an image file that meets the platform requirements.You are advised to complete the network, tool, and driver configurations in Table 1 on the source V", + "desc":"You need to prepare an image file that can be used to create a private image.Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In", "product_code":"ims", "title":"Preparing an Image File", "uri":"en-us_topic_0030713189.html", @@ -243,7 +243,7 @@ "code":"27" }, { - "desc":"You need to prepare an image file that meets the platform requirements.You are advised to complete the file system, network, and driver configurations in Table 1 on the s", + "desc":"You need to prepare an image file that can be used to create a private image.Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In", "product_code":"ims", "title":"Preparing an Image File", "uri":"en-us_topic_0030713198.html", @@ -324,7 +324,7 @@ "code":"36" }, { - "desc":"You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.The CBR service provides backup services for EVS disks, ", + "desc":"You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.CBR provides the backup service for EVS disks, BMSs, and", "product_code":"ims", "title":"Creating a Full-ECS Image from a CBR Backup", "uri":"en-us_topic_0176812699.html", @@ -351,16 +351,16 @@ "code":"39" }, { - "desc":"A Windows system with the Integrated Drive Electronics (IDE) hard drive and Virtio NIC is used on the cloud. Therefore, you need to integrate the VMTools driver into the ", + "desc":"Windows uses IDE disks and VirtIO NICs. Before registering an image on the cloud platform, integrate VirtIO drivers into the Windows ISO file. Typically, an ISO file cont", "product_code":"ims", - "title":"Integrating the VMTools Driver into an ISO File", + "title":"Integrating VirtIO Drivers into an ISO File", "uri":"en-us_topic_0146474781.html", "doc_type":"usermanual", "p_code":"38", "code":"40" }, { - "desc":"Register an external ISO file on the cloud platform as a private image (ISO image). Before registering an image, upload the ISO file exported in Integrating the VMTools D", + "desc":"Register an external ISO file on the cloud platform as a private image (ISO image). Before registering an image, upload the ISO file exported in Integrating VirtIO Driver", "product_code":"ims", "title":"Registering an ISO File as an ISO Image", "uri":"en-us_topic_0146474782.html", @@ -378,16 +378,16 @@ "code":"42" }, { - "desc":"This section uses Windows Server 2008 R2 64-bit as an example to describe how to install Windows on an ECS.The installation procedure varies depending on the image file y", + "desc":"This section uses Windows Server 2019 64-bit as an example to describe how to install Windows on an ECS.The installation procedure varies depending on the image file you ", "product_code":"ims", - "title":"Installing a Windows OS and the VMTools Driver", + "title":"Installing a Windows OS and VirtIO Drivers", "uri":"en-us_topic_0146474784.html", "doc_type":"usermanual", "p_code":"38", "code":"43" }, { - "desc":"After installing an OS for the temporary ECS, configure the ECS and install the Guest OS drivers provided by the cloud platform to ensure that ECSs created subsequently a", + "desc":"After installing an OS for the temporary ECS, configure the ECS and install Guest OS drivers provided by the cloud platform so that ECSs that will be created with this te", "product_code":"ims", "title":"Configuring the ECS and Creating a Windows System Disk Image", "uri":"en-us_topic_0146480985.html", @@ -441,7 +441,7 @@ "code":"49" }, { - "desc":"After installing an OS for the temporary ECS, configure the ECS and install the native Xen and KVM drivers to ensure that ECSs created subsequently are available.This sec", + "desc":"After installing an OS for the temporary ECS, configure the ECS and install KVM drivers to ensure that ECSs created from this temporary ECS can work properly.This sectio", "product_code":"ims", "title":"Configuring the ECS and Creating a Linux System Disk Image", "uri":"en-us_topic_0146480990.html", @@ -452,14 +452,14 @@ { "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":"Quickly Importing an Image File", + "title":"Fast Import of an Image File", "uri":"en-us_topic_0030713151.html", "doc_type":"usermanual", "p_code":"16", "code":"51" }, { - "desc":"If an image file is larger than 128 GB, you can import it using fast import. Only the RAW and ZVHD2 formats support fast import. The image file to be imported cannot exce", + "desc":"If an image file is larger than 128 GB, you can import it using fast import.The image file must be in RAW or ZVHD2 format.The image file size cannot exceed 1 TB.You can i", "product_code":"ims", "title":"Overview", "uri":"en-us_topic_0133773658.html", @@ -468,9 +468,9 @@ "code":"52" }, { - "desc":"This section describes how to convert the format of an image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an EulerOS EC", + "desc":"This section describes how to convert the format of a large image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an Euler", "product_code":"ims", - "title":"Quickly Importing an Image File (Linux)", + "title":"Fast Import in Linux", "uri":"en-us_topic_0133773660.html", "doc_type":"usermanual", "p_code":"51", @@ -479,7 +479,7 @@ { "desc":"This section describes how to convert the format of an image file on a Windows server and then quickly import it to the cloud platform. You are advised to use a local Win", "product_code":"ims", - "title":"Quickly Importing an Image File (Windows)", + "title":"Fast Import in Windows", "uri":"en-us_topic_0174703579.html", "doc_type":"usermanual", "p_code":"51", @@ -495,7 +495,7 @@ "code":"55" }, { - "desc":"You can modify the following attributes of a private image:NameDescriptionMinimum MemoryMaximum MemoryNIC Multi-QueueNIC multi-queue enables multiple CPUs to process NIC ", + "desc":"You can modify the following attributes of a private image:NameDescriptionMinimum memoryMaximum memoryNIC multi-queueNIC multi-queue enables multiple CPUs to process NIC ", "product_code":"ims", "title":"Modifying an Image", "uri":"en-us_topic_0030713199.html", @@ -657,7 +657,7 @@ "code":"73" }, { - "desc":"The proper running of ECSs depends on KVM Guest OS driver (UVP VMTools). To ensure that ECSs support KVM and to improve network performance, the UVP VMTools must be insta", + "desc":"An ECS can run properly only after KVM Guest OS drivers (VirtIO drivers) are installed on it. To ensure that ECSs support KVM and to improve network performance, VirtIO d", "product_code":"ims", "title":"Optimization Process", "uri":"en-us_topic_0047501112.html", @@ -666,7 +666,7 @@ "code":"74" }, { - "desc":"Table 1 lists the UVP VMTools software packages required for optimizing Windows private images.", + "desc":"Download a VirtIO driver package from:https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/You can select a version as needed.", "product_code":"ims", "title":"Obtaining Required Software Packages", "uri":"en-us_topic_0037352059.html", @@ -675,16 +675,16 @@ "code":"75" }, { - "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", + "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 VirtIO dri", "product_code":"ims", - "title":"Installing UVP VMTools", - "uri":"en-us_topic_0037352061.html", + "title":"Installing VirtIO Drivers", + "uri":"en-us_topic_0000001841305273.html", "doc_type":"usermanual", "p_code":"73", "code":"76" }, { - "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", + "desc":"After installing PV and VirtIO drivers, perform the following operations to clear system logs:For Windows Server 2008 and Windows Server 2012, right-click Computer and se", "product_code":"ims", "title":"Clearing System Logs", "uri":"en-us_topic_0125075472.html", @@ -783,7 +783,7 @@ "code":"87" }, { - "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", + "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 image replication. You m", "product_code":"ims", "title":"Replicating Images", "uri":"en-us_topic_0049177180.html", @@ -819,7 +819,7 @@ "code":"91" }, { - "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 ", + "desc":"After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records generated in the last seven d", "product_code":"ims", "title":"Viewing Traces", "uri":"en-us_topic_0107462582.html", @@ -936,7 +936,7 @@ "code":"104" }, { - "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", + "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 ECS obtains its IP", "product_code":"ims", "title":"Configuring Cloud-Init", "uri":"en-us_topic_0122876047.html", @@ -945,7 +945,7 @@ "code":"105" }, { - "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 ", + "desc":"Before using a private image to create GPU-accelerated ECSs, install a GPU driver for the image.There are two types of GPU drivers: GRID and Tesla.To use graphics acceler", "product_code":"ims", "title":"Installing Special Linux Drivers", "uri":"en-us_topic_0082002007.html", @@ -1071,7 +1071,7 @@ "code":"119" }, { - "desc":"You can back up the ECS in any of the following ways:(Recommended) Use CBR to create a scheduled backup task for the ECS. If the ECS fails, select a backup corresponding ", + "desc":"You can back up the ECS in any of the following ways:(Recommended) Use CBR to create a scheduled backup for the ECS. If the ECS fails, select a backup you want to use to ", "product_code":"ims", "title":"How Can I Back Up the Current Status of an ECS for Restoration in the Case of a System Fault?", "uri":"en-us_topic_0049196766.html", @@ -1080,7 +1080,7 @@ "code":"120" }, { - "desc":"You can change the OS of the ECS later. When you change the OS, select the created private image. For details about how to change the OS, see \"Changing the OS\" in Elastic", + "desc":"You can use the image to change the ECS OS. When you change the OS, select that image. For details about how to change the OS, see \"Changing the OS\" in Elastic Cloud Serv", "product_code":"ims", "title":"How Can I Apply a Private Image to an Existing ECS?", "uri":"en-us_topic_0069896389.html", @@ -1098,9 +1098,9 @@ "code":"122" }, { - "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.", + "desc":"Yes.You can use the private images other accounts shared with you.For details, see Sharing Specified Images.", "product_code":"ims", - "title":"Can I Use Private Images of Other Tenants?", + "title":"Can I Use Private Images of Other Accounts?", "uri":"en-us_topic_0173986473.html", "doc_type":"usermanual", "p_code":"113", @@ -1118,7 +1118,7 @@ { "desc":"If you have an ECS with applications deployed, you can use the ECS to create a private image and then use the image to create identical ECSs. In this way, you do not need", "product_code":"ims", - "title":"Image Creation FAQs", + "title":"General Creation FAQs", "uri":"en-us_topic_0193146244.html", "doc_type":"usermanual", "p_code":"124", @@ -1152,7 +1152,7 @@ "code":"128" }, { - "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", + "desc":"You are not advised to use a Windows ECS that has a spanned volume to create a full-ECS image. If you create such an image and then use it to create new ECSs, data may be", "product_code":"ims", "title":"How Do I Create a Full-ECS Image Using an ECS That Has a Spanned Volume?", "uri":"en-us_topic_0106444267.html", @@ -1161,7 +1161,7 @@ "code":"129" }, { - "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", + "desc":"Sysprep is used to generalize images. It removes server-specific information, like the security identifier (SID), from an image so that ECSs created from this image can h", "product_code":"ims", "title":"Why Is Sysprep Required for Creating a Private Image from a Windows ECS?", "uri":"en-us_topic_0030742197.html", @@ -1170,9 +1170,9 @@ "code":"130" }, { - "desc":"After Sysprep is executed, the following message is displayed when you start the ECS.Message displayedThen, the following information is displayed in the dialog box:Windo", + "desc":"When you start the ECS, information similar to the following is displayed.Message displayedThen, the following information is displayed in the dialog box:Windows could no", "product_code":"ims", - "title":"What Do I Do If an ECS Created from a Windows Image Failed to Start After Running Sysprep?", + "title":"How Do I Handle the Startup Failure of a Windows ECS Created from a Windows Image Generalized by Sysprep?", "uri":"en-us_topic_0030713206.html", "doc_type":"usermanual", "p_code":"124", @@ -1197,9 +1197,9 @@ "code":"133" }, { - "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.Switch ", + "desc":"128A 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.Swit", "product_code":"ims", - "title":"Image Sharing FAQs", + "title":"General Sharing FAQs", "uri":"en-us_topic_0183293890.html", "doc_type":"usermanual", "p_code":"133", @@ -1217,7 +1217,7 @@ { "desc":"Some images cannot be shared. Therefore, the Share option is not provided for them in the Operation column. The following images cannot be shared:Encrypted imagesFull-ECS", "product_code":"ims", - "title":"What Do I Do If I Cannot Share My Images?", + "title":"Why Can't I Share My Images?", "uri":"en-us_topic_0037352060.html", "doc_type":"usermanual", "p_code":"133", @@ -1233,7 +1233,7 @@ "code":"137" }, { - "desc":"LinuxUsed for development platforms or services that run Linux. CentOS and Ubuntu are provided. CentOS is recommended.The system disk must be no less than 40 GB, and the ", + "desc":"LinuxUsed for development platforms or services that run Linux. CentOS and Ubuntu are provided. CentOS is recommended.The system disk must be at least 40 GB, and there mu", "product_code":"ims", "title":"How Do I Select an OS?", "uri":"en-us_topic_0030713223.html", @@ -1250,15 +1250,6 @@ "p_code":"137", "code":"139" }, - { - "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", - "product_code":"ims", - "title":"How Do I Install the NVIDIA Driver on a P1 ECS?", - "uri":"en-us_topic_0093842586.html", - "doc_type":"usermanual", - "p_code":"137", - "code":"140" - }, { "desc":"Press Win+R. In the displayed dialog box, enter regedit and press Enter to open the registry editor.Modifying a registry may cause a system startup failure. So, back up t", "product_code":"ims", @@ -1266,7 +1257,7 @@ "uri":"en-us_topic_0106312064.html", "doc_type":"usermanual", "p_code":"137", - "code":"141" + "code":"140" }, { "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", @@ -1275,7 +1266,7 @@ "uri":"en-us_topic_0117142739.html", "doc_type":"usermanual", "p_code":"137", - "code":"142" + "code":"141" }, { "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", @@ -1284,7 +1275,7 @@ "uri":"en-us_topic_0081802526.html", "doc_type":"usermanual", "p_code":"137", - "code":"143" + "code":"142" }, { "desc":"The possible cause is the incompatible boot modes.If a private image is created from an ECS configured for BIOS boot or if you use an external image file to create such a", @@ -1293,25 +1284,25 @@ "uri":"en-us_topic_0290353431.html", "doc_type":"usermanual", "p_code":"137", - "code":"144" + "code":"143" }, { "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":"Image Importing", + "title":"Image Import", "uri":"en-us_topic_0030713195.html", "doc_type":"usermanual", "p_code":"112", - "code":"145" + "code":"144" }, { - "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", + "desc":"No. Currently, only VMDK, VHD, RAW, QCOW2, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD formats are supported.Images in -flat.vmdk format and image file packages containing snap", "product_code":"ims", - "title":"Can I Use Images in Formats Other Than the Specified Ones?", + "title":"Can I Use Images in Formats not Described in This Document?", "uri":"en-us_topic_0030713217.html", "doc_type":"usermanual", - "p_code":"145", - "code":"146" + "p_code":"144", + "code":"145" }, { "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-", @@ -1319,80 +1310,80 @@ "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":"145", - "code":"147" + "p_code":"144", + "code":"146" }, { - "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 ", + "desc":"Open Virtualization Appliance (OVA) is a single file archive (with the .ova extension) of all of the files comprising an Open Virtualization Format (OVF) package. OVF is ", "product_code":"ims", "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":"145", + "p_code":"144", + "code":"147" + }, + { + "desc":"If you selected the wrong OS, the ECS creation may fail when the image is used.If the system disk capacity you configured is less than the one in the image file, image re", + "product_code":"ims", + "title":"What Do I Do If I Chose the Wrong OS or System Disk Capacity When Registering a Private Image?", + "uri":"en-us_topic_0030713213.html", + "doc_type":"usermanual", + "p_code":"144", "code":"148" }, { - "desc":"If you selected an incorrect OS, ECSs may fail to be created from the private image. If the configured system disk capacity is less than the one in the image file, image ", + "desc":"The possible causes may be:Too small a value was specified when registering the image. Check the system disk capacity in the VHD image file. Specify a value at least this", "product_code":"ims", - "title":"What Do I Do If I Configured an Incorrect OS or System Disk Capacity During Private Image Registration Using an Image File?", - "uri":"en-us_topic_0030713213.html", - "doc_type":"usermanual", - "p_code":"145", - "code":"149" - }, - { - "desc":"The possible causes may be:You have specified a small value.Check the system disk capacity in the VHD image file. Specify a value no less than this value when you use the", - "product_code":"ims", - "title":"What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?", + "title":"Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger Than What I Specified on the Management Console?", "uri":"en-us_topic_0058841396.html", "doc_type":"usermanual", - "p_code":"145", - "code":"150" + "p_code":"144", + "code":"149" }, { "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":"Image Exporting", + "title":"Image Export", "uri":"en-us_topic_0030713222.html", "doc_type":"usermanual", "p_code":"112", - "code":"151" + "code":"150" }, { - "desc":"Yes. You can download private images in VMDK, VHD, QCOW2, or ZVHD format as instructed in Exporting an Image.", + "desc":"Yes. You can download private images as instructed in Exporting an Image.Currently, only images in VMDK, VHD, QCOW2, or ZVHD format can be exported.The default format of ", "product_code":"ims", "title":"Can I Download My Private Images to a Local PC?", "uri":"en-us_topic_0249675952.html", "doc_type":"usermanual", - "p_code":"151", - "code":"152" + "p_code":"150", + "code":"151" }, { - "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", + "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. So, it cannot be used on a BMS", "product_code":"ims", "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":"151", - "code":"153" + "p_code":"150", + "code":"152" }, { - "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", + "desc":"When 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 G", "product_code":"ims", "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":"151", - "code":"154" + "p_code":"150", + "code":"153" }, { - "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 ", + "desc":"You cannot directly download a public image. However, you can use the public image to create an ECS, use the ECS to create a private image, export the private image to yo", "product_code":"ims", - "title":"Can I Download a Public Image to My Local PC?", + "title":"Can I Download a Public Image to My PC?", "uri":"en-us_topic_0030713186.html", "doc_type":"usermanual", - "p_code":"151", - "code":"155" + "p_code":"150", + "code":"154" }, { "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.", @@ -1400,17 +1391,17 @@ "title":"What Are the Differences Between Import/Export and Fast Import/Export?", "uri":"en-us_topic_0199451475.html", "doc_type":"usermanual", - "p_code":"151", - "code":"156" + "p_code":"150", + "code":"155" }, { - "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", + "desc":"Some images cannot be exported. So, the Export option is not provided for them in the Operation column. The following images cannot be exported:Public imagesFull-ECS imag", "product_code":"ims", - "title":"What Do I Do If the Export Option Is Unavailable for My Image?", + "title":"Why the Export Option Is Unavailable for My Image?", "uri":"en-us_topic_0199396601.html", "doc_type":"usermanual", - "p_code":"151", - "code":"157" + "p_code":"150", + "code":"156" }, { "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.", @@ -1419,7 +1410,7 @@ "uri":"en-us_topic_0030713203.html", "doc_type":"usermanual", "p_code":"112", - "code":"158" + "code":"157" }, { "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", @@ -1427,17 +1418,17 @@ "title":"Must I Install Guest OS Drivers on an ECS?", "uri":"en-us_topic_0030713214.html", "doc_type":"usermanual", - "p_code":"158", - "code":"159" + "p_code":"157", + "code":"158" }, { - "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", + "desc":"VirtIO drivers are paravirtualized drivers that provide high-performance disks and NICs for ECSs.Windows does not have VirtIO drivers installed by default.Public images h", "product_code":"ims", - "title":"Why Do I Need to Install and Update VMTools for Windows?", + "title":"Why Do I Need to Install and Update VirtIO Drivers for Windows?", "uri":"en-us_topic_0165718046.html", "doc_type":"usermanual", - "p_code":"158", - "code":"160" + "p_code":"157", + "code":"159" }, { "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", @@ -1445,98 +1436,98 @@ "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":"158", - "code":"161" + "p_code":"157", + "code":"160" }, { "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", "product_code":"ims", - "title":"How Do I Configure an ECS, BMS, or Image File Before I Use It to Create an Image?", + "title":"How Do I Configure an ECS, a BMS, or an Image File Before I Use It to Create an Image?", "uri":"en-us_topic_0040740508.html", "doc_type":"usermanual", - "p_code":"158", - "code":"162" + "p_code":"157", + "code":"161" }, { - "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 ", + "desc":"If an image file is not configured as instructed in Table 1 before it is exported from the original platform, you can use it to create an ECS, configure the ECS, and use ", "product_code":"ims", "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":"158", - "code":"163" + "p_code":"157", + "code":"162" }, { - "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 ", + "desc":"If an image file is not configured as instructed in Table 1 before it is exported from the original platform, you can use it to create an ECS, configure the ECS, and use ", "product_code":"ims", "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":"158", - "code":"164" + "p_code":"157", + "code":"163" }, { - "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", + "desc":"Network I/O bandwidth can keep increasing to the point where a single vCPU cannot process all of the NIC interrupts. NIC multi-queue allows multiple vCPUs to process NIC ", "product_code":"ims", "title":"How Do I Enable NIC Multi-Queue for an Image?", "uri":"en-us_topic_0085214115.html", "doc_type":"usermanual", - "p_code":"158", - "code":"165" + "p_code":"157", + "code":"164" }, { "desc":"IPv6 addresses are used to deal with IPv4 address exhaustion. If an ECS uses an IPv4 address, the ECS can run in dual-stack mode after IPv6 is enabled for it. Then, the E", "product_code":"ims", - "title":"How Do I Configure an ECS to Dynamically Acquire IPv6 Addresses?", + "title":"How Do I Configure an ECS to Use DHCPv6?", "uri":"en-us_topic_0129883696.html", "doc_type":"usermanual", - "p_code":"158", - "code":"166" + "p_code":"157", + "code":"165" }, { - "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 ", + "desc":"Fast Create greatly reduces the time required to create ECSs from a system disk image. Currently, this feature is supported for all newly created system disk images by de", "product_code":"ims", "title":"How Do I Make a System Disk Image Support Fast ECS Creation?", "uri":"en-us_topic_0187108863.html", "doc_type":"usermanual", - "p_code":"158", + "p_code":"157", + "code":"166" + }, + { + "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 Guest OS drivers of ", + "product_code":"ims", + "title":"Why Did I Fail to Install Guest OS Drivers on a Windows ECS?", + "uri":"en-us_topic_0030713215.html", + "doc_type":"usermanual", + "p_code":"157", "code":"167" }, { - "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 ", - "product_code":"ims", - "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":"158", - "code":"168" - }, - { - "desc":"In-region replicationThis is used for conversion between encrypted and unencrypted images or for enabling advanced features (such as fast ECS creation) for images. For de", + "desc":"In-region replicationThis is used for conversion between encrypted and unencrypted images or for enabling advanced features (such as fast ECS creation). For details, see ", "product_code":"ims", "title":"Image Replication", "uri":"en-us_topic_0183293891.html", "doc_type":"usermanual", "p_code":"112", - "code":"169" + "code":"168" }, { - "desc":"No. Private images created using ECSs are stored in OBS buckets. Deleting the ECS used to create a private image does not affect the image.Yes. You can delete a shared im", + "desc":"No. Private images created using ECSs are stored in OBS buckets. Deleting the ECSs does not affect the images.If an image is shared with a project, you can delete the ima", "product_code":"ims", "title":"Image Deletion", "uri":"en-us_topic_0032326546.html", "doc_type":"usermanual", "p_code":"112", - "code":"170" + "code":"169" }, { - "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 ", + "desc":"You can select an encryption key when you replicate the image. Then, the system will generate an encrypted version of the unencrypted image.", "product_code":"ims", "title":"Image Encryption", "uri":"en-us_topic_0049196765.html", "doc_type":"usermanual", "p_code":"112", - "code":"171" + "code":"170" }, { "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.", @@ -1545,7 +1536,7 @@ "uri":"en-us_topic_0205273057.html", "doc_type":"usermanual", "p_code":"112", - "code":"172" + "code":"171" }, { "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. ", @@ -1553,8 +1544,8 @@ "title":"How Do I Authorize a Key?", "uri":"en-us_topic_0133773781.html", "doc_type":"usermanual", - "p_code":"172", - "code":"173" + "p_code":"171", + "code":"172" }, { "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.", @@ -1563,7 +1554,7 @@ "uri":"en-us_topic_0138479468.html", "doc_type":"usermanual", "p_code":"112", - "code":"174" + "code":"173" }, { "desc":"You are advised to install Cloud-Init on the ECS that will be used to create a private image so that new ECSs created from the private image support custom configurations", @@ -1571,35 +1562,35 @@ "title":"Cloud-Init Installation FAQ", "uri":"en-us_topic_0132216287.html", "doc_type":"usermanual", - "p_code":"174", - "code":"175" + "p_code":"173", + "code":"174" }, { - "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", + "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 customize initia", "product_code":"ims", "title":"What Can I Do with a Cloud-Init ECS?", "uri":"en-us_topic_0148873774.html", "doc_type":"usermanual", - "p_code":"174", + "p_code":"173", + "code":"175" + }, + { + "desc":"One likely possibility is that the version of Cloud-Init is incompatible with that of NetworkManager. In Debian 9.0 and later versions, NetworkManager is incompatible wit", + "product_code":"ims", + "title":"What Do I Do If Installed NetworkManager and Now I Can't Inject the Key or Password Using Cloud-Init?", + "uri":"en-us_topic_0113992021.html", + "doc_type":"usermanual", + "p_code":"173", "code":"176" }, { - "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", - "product_code":"ims", - "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":"174", - "code":"177" - }, - { - "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", + "desc":"For SUSE and openSUSE, growpart is an independent tool and is not included in a cloud-* package. You need to install it separately.Check whether Cloud-Init and growpart a", "product_code":"ims", "title":"How Do I Install growpart for SUSE 11 SP4?", "uri":"en-us_topic_0078454810.html", "doc_type":"usermanual", - "p_code":"174", - "code":"178" + "p_code":"173", + "code":"177" }, { "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.", @@ -1608,61 +1599,61 @@ "uri":"en-us_topic_0030713220.html", "doc_type":"usermanual", "p_code":"112", - "code":"179" + "code":"178" }, { - "desc":"Yes.If you have selected an incorrect image or your service requirements have changed, you can change the image of your ECS.You can change the image type (public, private", + "desc":"Yes.If you have selected the wrong image or your service requirements have changed, you can change the image of your ECS.You can change the image type (public, private, a", "product_code":"ims", "title":"Can I Change the Image of a Purchased ECS?", "uri":"en-us_topic_0030713208.html", "doc_type":"usermanual", - "p_code":"179", + "p_code":"178", + "code":"179" + }, + { + "desc":"Yes. You can specify the CPU, memory, bandwidth, system and data disks of the ECS you are creating. The system disk must be smaller than 1,024 GB but no less than the sys", + "product_code":"ims", + "title":"Can I Change the Specifications Defined by a Private Image When I Use the Image to Create an ECS?", + "uri":"en-us_topic_0030713209.html", + "doc_type":"usermanual", + "p_code":"178", "code":"180" }, { - "desc":"Yes. You can specify the CPU, memory, bandwidth, data disks of the new ECSs if necessary. You can also specify their system disk capacity. The value must be smaller than ", - "product_code":"ims", - "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":"179", - "code":"181" - }, - { - "desc":"Yes. However, the value must be smaller than 30,768 GB but no less than the system disk capacity in the image.Ensure that your ECS OS supports the system disk capacity yo", + "desc":"Yes, but you cannot create a system disk smaller than the original and the maximum allowed is 30,768 GB.Ensure that your ECS OS can support the system disk size you speci", "product_code":"ims", "title":"Can I Specify the System Disk Capacity When I Create an ECS Using an Image?", "uri":"en-us_topic_0030713221.html", "doc_type":"usermanual", - "p_code":"179", + "p_code":"178", + "code":"181" + }, + { + "desc":"Disk partition IDs are changed after the cross-platform image import. As a result, no partition can be found at startup. In this case, you need to change disk partition I", + "product_code":"ims", + "title":"What Do I Do If a Partition Is Not Found During the Startup of an ECS Created from an Imported Private Image?", + "uri":"en-us_topic_0034220644.html", + "doc_type":"usermanual", + "p_code":"178", "code":"182" }, { - "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 ", + "desc":"This may be caused by an issue with offline VirtIO driver injection.When you inject VirtIO drivers into the image for a Windows ECS, note that:If the boot mode in the ima", "product_code":"ims", - "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", + "title":"What Do I Do If I Enabled Automatic Configuration During Image Registration for an ECS Created from a Windows Image and Now It Won't Start?", + "uri":"en-us_topic_0113403127.html", "doc_type":"usermanual", - "p_code":"179", + "p_code":"178", "code":"183" }, { - "desc":"This issue is probably caused by the failure of offline VirtIO driver injection.When you inject VirtIO drivers for a Windows ECS offline, there are some restrictions:If t", + "desc":"An ECS created from a private image booting to UEFI cannot start.The image is configured for UEFI boot, but the uefi attribute was not added to the image.Delete the ECS t", "product_code":"ims", - "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":"179", - "code":"184" - }, - { - "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", - "product_code":"ims", - "title":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mode?", + "title":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using UEFI Boot?", "uri":"en-us_topic_0161870891.html", "doc_type":"usermanual", - "p_code":"179", - "code":"185" + "p_code":"178", + "code":"184" }, { "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.", @@ -1671,7 +1662,7 @@ "uri":"en-us_topic_0000001397367656.html", "doc_type":"usermanual", "p_code":"112", - "code":"186" + "code":"185" }, { "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", @@ -1679,35 +1670,35 @@ "title":"Must I Install Guest OS Drivers on an ECS?", "uri":"en-us_topic_0000001397535494.html", "doc_type":"usermanual", - "p_code":"186", + "p_code":"185", + "code":"186" + }, + { + "desc":"VirtIO drivers are paravirtualized drivers that provide high-performance disks and NICs for ECSs.Windows does not have VirtIO drivers installed by default.Public images h", + "product_code":"ims", + "title":"Why Do I Need to Install and Update VirtIO Drivers for Windows?", + "uri":"en-us_topic_0000001447895377.html", + "doc_type":"usermanual", + "p_code":"185", "code":"187" }, { - "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", + "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 Guest OS drivers of ", "product_code":"ims", - "title":"Why Do I Need to Install and Update VMTools for Windows?", - "uri":"en-us_topic_0000001447895377.html", + "title":"Why Did I Fail to Install Guest OS Drivers on a Windows ECS?", + "uri":"en-us_topic_0000001447815605.html", "doc_type":"usermanual", - "p_code":"186", + "p_code":"185", "code":"188" }, { - "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 ", + "desc":"The installation only applies to KVM ECSs.Before using an ECS or external image file to create a private image, ensure that VirtIO drivers have been installed in the OS s", "product_code":"ims", - "title":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?", - "uri":"en-us_topic_0000001447815605.html", - "doc_type":"usermanual", - "p_code":"186", - "code":"189" - }, - { - "desc":"This only applies to KVM ECSs. 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 subseq", - "product_code":"ims", - "title":"How Do I Install UVP VMTools in Windows?", + "title":"How Do I Install VirtIO Drivers in Windows?", "uri":"en-us_topic_0000001398100610.html", "doc_type":"usermanual", - "p_code":"186", - "code":"190" + "p_code":"185", + "code":"189" }, { "desc":"When optimizing a Linux private image, you need to install native KVM drivers on the ECS from which the image will be created. If you ECS already has native KVM drivers i", @@ -1715,8 +1706,8 @@ "title":"How Do I Install Native KVM Drivers in Linux?", "uri":"en-us_topic_0000001398260514.html", "doc_type":"usermanual", - "p_code":"186", - "code":"191" + "p_code":"185", + "code":"190" }, { "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.", @@ -1725,7 +1716,7 @@ "uri":"en-us_topic_0000001397207656.html", "doc_type":"usermanual", "p_code":"112", - "code":"192" + "code":"191" }, { "desc":"An image can have a maximum of 10 tags.", @@ -1733,8 +1724,8 @@ "title":"How Many Tags Can I Add to an Image?", "uri":"en-us_topic_0000001398583638.html", "doc_type":"usermanual", - "p_code":"192", - "code":"193" + "p_code":"191", + "code":"192" }, { "desc":"When adding predefined tags to an image or searching for an image using predefined tags, you must have permission to access the Tag Management Service (TMS).Access the IM", @@ -1742,8 +1733,8 @@ "title":"How Do I Add, Delete, and Modify Image Tags?", "uri":"en-us_topic_0000001398421074.html", "doc_type":"usermanual", - "p_code":"192", - "code":"194" + "p_code":"191", + "code":"193" }, { "desc":"When adding predefined tags to an image or searching for an image using predefined tags, you must have permission to access the Tag Management Service (TMS).Access the IM", @@ -1751,8 +1742,8 @@ "title":"How Do I Search for Private Images by Tag?", "uri":"en-us_topic_0000001398423666.html", "doc_type":"usermanual", - "p_code":"192", - "code":"195" + "p_code":"191", + "code":"194" }, { "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.", @@ -1761,7 +1752,7 @@ "uri":"en-us_topic_0041178787.html", "doc_type":"usermanual", "p_code":"", - "code":"196" + "code":"195" }, { "desc":"For details about the terms involved in this document, see Glossary.", @@ -1770,6 +1761,6 @@ "uri":"en-us_topic_0047898081.html", "doc_type":"usermanual", "p_code":"", - "code":"197" + "code":"196" } ] \ No newline at end of file diff --git a/docs/ims/umn/en-us_image_0000001492921309.png b/docs/ims/umn/en-us_image_0000001492921309.png deleted file mode 100644 index ffdce3af..00000000 Binary files a/docs/ims/umn/en-us_image_0000001492921309.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0000001493042877.png b/docs/ims/umn/en-us_image_0000001493042877.png deleted file mode 100644 index 469e9479..00000000 Binary files a/docs/ims/umn/en-us_image_0000001493042877.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0000001494625768.png b/docs/ims/umn/en-us_image_0000001494625768.png deleted file mode 100644 index 41a41ab8..00000000 Binary files a/docs/ims/umn/en-us_image_0000001494625768.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0000001696678850.png b/docs/ims/umn/en-us_image_0000001696678850.png new file mode 100644 index 00000000..6b11888b Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001696678850.png differ diff --git a/docs/ims/umn/en-us_image_0000001696838310.png b/docs/ims/umn/en-us_image_0000001696838310.png new file mode 100644 index 00000000..582b1618 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001696838310.png differ diff --git a/docs/ims/umn/en-us_image_0000001696838318.png b/docs/ims/umn/en-us_image_0000001696838318.png new file mode 100644 index 00000000..e4fcbfa9 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001696838318.png differ diff --git a/docs/ims/umn/en-us_image_0000001744598325.png b/docs/ims/umn/en-us_image_0000001744598325.png new file mode 100644 index 00000000..3e15dbf9 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001744598325.png differ diff --git a/docs/ims/umn/en-us_image_0000001744678489.jpg b/docs/ims/umn/en-us_image_0000001744678489.jpg new file mode 100644 index 00000000..fac6892b Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001744678489.jpg differ diff --git a/docs/ims/umn/en-us_image_0000001758618249.png b/docs/ims/umn/en-us_image_0000001758618249.png new file mode 100644 index 00000000..0d21733f Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001758618249.png differ diff --git a/docs/ims/umn/en-us_image_0000001795626446.png b/docs/ims/umn/en-us_image_0000001795626446.png new file mode 100644 index 00000000..965408a4 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001795626446.png differ diff --git a/docs/ims/umn/en-us_image_0000001795638722.png b/docs/ims/umn/en-us_image_0000001795638722.png new file mode 100644 index 00000000..b4e92091 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001795638722.png differ diff --git a/docs/ims/umn/en-us_image_0000001795638958.png b/docs/ims/umn/en-us_image_0000001795638958.png new file mode 100644 index 00000000..b4c9e21d Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001795638958.png differ diff --git a/docs/ims/umn/en-us_image_0000001795641858.png b/docs/ims/umn/en-us_image_0000001795641858.png new file mode 100644 index 00000000..d140d578 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001795641858.png differ diff --git a/docs/ims/umn/en-us_image_0000001829389966.png b/docs/ims/umn/en-us_image_0000001829389966.png new file mode 100644 index 00000000..da983aad Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001829389966.png differ diff --git a/docs/ims/umn/en-us_image_0000001829550782.png b/docs/ims/umn/en-us_image_0000001829550782.png new file mode 100644 index 00000000..e3f8c270 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001829550782.png differ diff --git a/docs/ims/umn/en-us_image_0000001842117653.png b/docs/ims/umn/en-us_image_0000001842117653.png new file mode 100644 index 00000000..a42c02c6 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001842117653.png differ diff --git a/docs/ims/umn/en-us_image_0000001842120221.png b/docs/ims/umn/en-us_image_0000001842120221.png new file mode 100644 index 00000000..33aa5566 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001842120221.png differ diff --git a/docs/ims/umn/en-us_image_0000001842120669.png b/docs/ims/umn/en-us_image_0000001842120669.png new file mode 100644 index 00000000..88a3b703 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001842120669.png differ diff --git a/docs/ims/umn/en-us_image_0000001842227233.png b/docs/ims/umn/en-us_image_0000001842227233.png new file mode 100644 index 00000000..514cf2e2 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001842227233.png differ diff --git a/docs/ims/umn/en-us_image_0000001842239205.png b/docs/ims/umn/en-us_image_0000001842239205.png new file mode 100644 index 00000000..4d9f757d Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001842239205.png differ diff --git a/docs/ims/umn/en-us_image_0000001842240965.png b/docs/ims/umn/en-us_image_0000001842240965.png new file mode 100644 index 00000000..fd7ee348 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001842240965.png differ diff --git a/docs/ims/umn/en-us_image_0000001860906473.png b/docs/ims/umn/en-us_image_0000001860906473.png new file mode 100644 index 00000000..d68dec34 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001860906473.png differ diff --git a/docs/ims/umn/en-us_image_0000001860980389.png b/docs/ims/umn/en-us_image_0000001860980389.png new file mode 100644 index 00000000..c676386c Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001860980389.png differ diff --git a/docs/ims/umn/en-us_image_0000001890826049.png b/docs/ims/umn/en-us_image_0000001890826049.png new file mode 100644 index 00000000..86f37899 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001890826049.png differ diff --git a/docs/ims/umn/en-us_image_0000001926097585.png b/docs/ims/umn/en-us_image_0000001926097585.png new file mode 100644 index 00000000..605fc2db Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001926097585.png differ diff --git a/docs/ims/umn/en-us_image_0000001948967564.png b/docs/ims/umn/en-us_image_0000001948967564.png new file mode 100644 index 00000000..ef240b04 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001948967564.png differ diff --git a/docs/ims/umn/en-us_image_0000001954451565.png b/docs/ims/umn/en-us_image_0000001954451565.png new file mode 100644 index 00000000..05538b60 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001954451565.png differ diff --git a/docs/ims/umn/en-us_image_0000001978685553.png b/docs/ims/umn/en-us_image_0000001978685553.png new file mode 100644 index 00000000..5d7d4bbd Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001978685553.png differ diff --git a/docs/ims/umn/en-us_image_0000001979249001.png b/docs/ims/umn/en-us_image_0000001979249001.png new file mode 100644 index 00000000..409afd62 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001979249001.png differ diff --git a/docs/ims/umn/en-us_image_0000001979408863.png b/docs/ims/umn/en-us_image_0000001979408863.png new file mode 100644 index 00000000..5021fb07 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001979408863.png differ diff --git a/docs/ims/umn/en-us_image_0099872706.png b/docs/ims/umn/en-us_image_0099872706.png deleted file mode 100644 index 84d438e8..00000000 Binary files a/docs/ims/umn/en-us_image_0099872706.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0099872707.png b/docs/ims/umn/en-us_image_0099872707.png deleted file mode 100644 index 84d438e8..00000000 Binary files a/docs/ims/umn/en-us_image_0099872707.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0099872708.png b/docs/ims/umn/en-us_image_0099872708.png deleted file mode 100644 index 04716d1b..00000000 Binary files a/docs/ims/umn/en-us_image_0099872708.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 new file mode 100644 index 00000000..21428f82 Binary files /dev/null and b/docs/ims/umn/en-us_image_0118549088.png differ diff --git a/docs/ims/umn/en-us_image_0120595879.png b/docs/ims/umn/en-us_image_0120595879.png new file mode 100644 index 00000000..31483316 Binary files /dev/null and b/docs/ims/umn/en-us_image_0120595879.png differ diff --git a/docs/ims/umn/en-us_image_0120595887.png b/docs/ims/umn/en-us_image_0120595887.png new file mode 100644 index 00000000..35f9e6f8 Binary files /dev/null and b/docs/ims/umn/en-us_image_0120595887.png differ diff --git a/docs/ims/umn/en-us_image_0127506675.png b/docs/ims/umn/en-us_image_0127506675.png deleted file mode 100644 index 7b0eacb2..00000000 Binary files a/docs/ims/umn/en-us_image_0127506675.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0137070023.png b/docs/ims/umn/en-us_image_0137070023.png deleted file mode 100644 index 0d93e170..00000000 Binary files a/docs/ims/umn/en-us_image_0137070023.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0146478919.png b/docs/ims/umn/en-us_image_0146478919.png deleted file mode 100644 index 565843b3..00000000 Binary files a/docs/ims/umn/en-us_image_0146478919.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0146478941.png b/docs/ims/umn/en-us_image_0146478941.png deleted file mode 100644 index 9a22ecdb..00000000 Binary files a/docs/ims/umn/en-us_image_0146478941.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0146478943.png b/docs/ims/umn/en-us_image_0146478943.png deleted file mode 100644 index 6c3d8a9d..00000000 Binary files a/docs/ims/umn/en-us_image_0146478943.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0146478945.png b/docs/ims/umn/en-us_image_0146478945.png deleted file mode 100644 index 78094fae..00000000 Binary files a/docs/ims/umn/en-us_image_0146478945.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0160277563.png b/docs/ims/umn/en-us_image_0160277563.png deleted file mode 100644 index e5fe8df6..00000000 Binary files a/docs/ims/umn/en-us_image_0160277563.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0160277938.png b/docs/ims/umn/en-us_image_0160277938.png deleted file mode 100644 index f46c9940..00000000 Binary files a/docs/ims/umn/en-us_image_0160277938.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0160277992.png b/docs/ims/umn/en-us_image_0160277992.png deleted file mode 100644 index f7572479..00000000 Binary files a/docs/ims/umn/en-us_image_0160277992.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0160277998.png b/docs/ims/umn/en-us_image_0160277998.png deleted file mode 100644 index 61de07a2..00000000 Binary files a/docs/ims/umn/en-us_image_0160277998.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0160278257.png b/docs/ims/umn/en-us_image_0160278257.png deleted file mode 100644 index 6d606bd3..00000000 Binary files a/docs/ims/umn/en-us_image_0160278257.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0160278288.png b/docs/ims/umn/en-us_image_0160278288.png deleted file mode 100644 index 7b2e572c..00000000 Binary files a/docs/ims/umn/en-us_image_0160278288.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0179492194.png b/docs/ims/umn/en-us_image_0179492194.png deleted file mode 100644 index ffdce3af..00000000 Binary files a/docs/ims/umn/en-us_image_0179492194.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0179492273.png b/docs/ims/umn/en-us_image_0179492273.png deleted file mode 100644 index 89d6e8c1..00000000 Binary files a/docs/ims/umn/en-us_image_0179492273.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0180992674.png b/docs/ims/umn/en-us_image_0180992674.png new file mode 100644 index 00000000..d48cc79b Binary files /dev/null and b/docs/ims/umn/en-us_image_0180992674.png differ diff --git a/docs/ims/umn/en-us_image_0185000270.gif b/docs/ims/umn/en-us_image_0185000270.gif deleted file mode 100644 index cbfc870f..00000000 Binary files a/docs/ims/umn/en-us_image_0185000270.gif and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0196045691.png b/docs/ims/umn/en-us_image_0196045691.png deleted file mode 100644 index 8a64c307..00000000 Binary files a/docs/ims/umn/en-us_image_0196045691.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0209970890.png b/docs/ims/umn/en-us_image_0209970890.png deleted file mode 100644 index 36b6c5e9..00000000 Binary files a/docs/ims/umn/en-us_image_0209970890.png and /dev/null differ diff --git a/docs/ims/umn/en-us_image_0285376505.png b/docs/ims/umn/en-us_image_0285376505.png deleted file mode 100644 index 12e570b7..00000000 Binary files a/docs/ims/umn/en-us_image_0285376505.png and /dev/null differ diff --git a/docs/ims/umn/en-us_topic_0000001328477720.html b/docs/ims/umn/en-us_topic_0000001328477720.html index 1bf74a5d..b343d9f7 100644 --- a/docs/ims/umn/en-us_topic_0000001328477720.html +++ b/docs/ims/umn/en-us_topic_0000001328477720.html @@ -24,7 +24,7 @@

Shared

A shared image is a private image another user has shared with you.

-

For more information about shared images, see "Sharing Images" in Image Management Service User Guide.

+

For more information, see "Sharing Images" in Image Management Service User Guide.

@@ -42,7 +42,7 @@

Modifying an image

-

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

+

You can modify the following attributes of an image: name, description, minimum memory, maximum memory, and advanced functions such as NIC multi-queue and SR-IOV driver.

Modifying an Image

@@ -58,12 +58,12 @@

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

- +

Encrypting images

-

You can create encrypted images to improve data security. The encryption mode is KMS envelope encryption.

+

You can create encrypted images to improve data security. KMS envelope encryption is used.

Encrypted images can be created from external image files or encrypted ECSs.

@@ -71,7 +71,7 @@

Replicating images

-

By replicating images, you can convert encrypted and unencrypted images into each other or enable some advanced features, for example, quick instance provisioning.

+

By replicating images, you can convert encrypted and unencrypted images into each other or enable some advanced features, for example, fast instance provisioning.

Replicating Images

@@ -85,7 +85,7 @@

Exporting image list

-

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

+

You can export the public or private image list in a given region as a CSV file for local maintenance and query.

Exporting Image List

diff --git a/docs/ims/umn/en-us_topic_0000001379315093.html b/docs/ims/umn/en-us_topic_0000001379315093.html index e0591f01..e40fbcf6 100644 --- a/docs/ims/umn/en-us_topic_0000001379315093.html +++ b/docs/ims/umn/en-us_topic_0000001379315093.html @@ -2,7 +2,7 @@

What Are the Differences Between Sharing Images and Replicating Images?

The following table describes the details.
- @@ -19,18 +19,18 @@ - - - - diff --git a/docs/ims/umn/en-us_topic_0000001397367656.html b/docs/ims/umn/en-us_topic_0000001397367656.html index ed54bbf0..e53e7966 100644 --- a/docs/ims/umn/en-us_topic_0000001397367656.html +++ b/docs/ims/umn/en-us_topic_0000001397367656.html @@ -10,11 +10,11 @@ diff --git a/docs/ims/umn/en-us_topic_0030713142.html b/docs/ims/umn/en-us_topic_0030713142.html index d4d4c8ac..9cac4f71 100644 --- a/docs/ims/umn/en-us_topic_0030713142.html +++ b/docs/ims/umn/en-us_topic_0030713142.html @@ -2,7 +2,7 @@

OSs Supported by Different Types of ECSs

This section describes the OSs supported by different types of ECSs.

-

x86 ECSs

  • Table 1 lists the OSs supported by the following ECSs:

    General-purpose S2, S3

    +

    x86 ECSs

    • Table 1 lists the OSs supported by the following ECSs:

      General-purpose S2, S3

      Dedicated general-purpose C3, C4

      Memory-optimized M3, M4

      Disk-intensive D2

      diff --git a/docs/ims/umn/en-us_topic_0030713143.html b/docs/ims/umn/en-us_topic_0030713143.html index be2338d8..ee3beb2c 100644 --- a/docs/ims/umn/en-us_topic_0030713143.html +++ b/docs/ims/umn/en-us_topic_0030713143.html @@ -6,8 +6,8 @@

      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.
      -
      • 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).
      +
      • 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.
      • You can only use external image files containing Windows 10 64bit or Windows 7 Enterprise 64bit to create ECSs on a Dedicated Host (DeH).

Scenario

@@ -11,7 +11,7 @@

Description

Helpful Links

+

Helpful Link

Share

The image is shared with another user in the same region. The target user can use the image (with the same ID as the source image) but the image owner is still the user who shared it.

+

The image is shared with another user in the same region. The target user can use the image (with the same ID as the source image) but the image is still owned by the user who shared it.

For details, see Sharing Specified Images.

+

Sharing Specified Images

In-region replication under the same account

Replicate

This is used for conversion between encrypted images and unencrypted images or for enabling advanced features (such as fast ECS creation from an image).

+

This is used for conversion between encrypted and unencrypted images or for enabling advanced features (such as fast ECS creation from an image).

For details, see Replicating Images.

+

Replicating Images

Shared

A shared image is a private image another user has shared with you.

-

For more information about shared images, see "Sharing Images" in Image Management Service User Guide.

+

For more information, see "Sharing Images" in Image Management Service User Guide.

- - - - - - - - - - - + + + + + + + + + diff --git a/docs/ims/umn/en-us_topic_0030713149.html b/docs/ims/umn/en-us_topic_0030713149.html index 8454bf28..2eed70c0 100644 --- a/docs/ims/umn/en-us_topic_0030713149.html +++ b/docs/ims/umn/en-us_topic_0030713149.html @@ -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 UVP VMTools driver to ensure that new ECSs created from the image support KVM virtualization and to improve network performance.

      For details, see steps 2 to 4 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 VirtIO drivers to ensure that new ECSs created from the image support KVM virtualization and to improve network performance.

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

      diff --git a/docs/ims/umn/en-us_topic_0030713151.html b/docs/ims/umn/en-us_topic_0030713151.html index 3a4d9deb..4c1dd4ef 100644 --- a/docs/ims/umn/en-us_topic_0030713151.html +++ b/docs/ims/umn/en-us_topic_0030713151.html @@ -1,14 +1,14 @@ -

      Quickly Importing an Image File

      +

      Fast Import of an Image File

      diff --git a/docs/ims/umn/en-us_topic_0030713152.html b/docs/ims/umn/en-us_topic_0030713152.html index 1e2a8701..309c2b1a 100644 --- a/docs/ims/umn/en-us_topic_0030713152.html +++ b/docs/ims/umn/en-us_topic_0030713152.html @@ -7,13 +7,13 @@

    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
      -
    5. Click Properties and select the configured Internet protocol version.
    6. On the General tab, select Obtain an IP address automatically and Obtain DNS server address automatically and click OK. Figure 3 shows the dialog box for configuring the IP address obtaining mode.

      You are advised to record the original network information so that you can restore the network if necessary.

      +
    7. Click Properties and select the configured Internet protocol version.
    8. On the General tab, select Obtain an IP address automatically and Obtain DNS server address automatically and click OK, as shown in Figure 3. The system will automatically obtain an IP address.

      You are advised to record the original network information so that you can restore the network if necessary.

      -
      Figure 3 Configuring the IP address obtaining mode
      +
      Figure 3 Configuring DHCP

    diff --git a/docs/ims/umn/en-us_topic_0030713153.html b/docs/ims/umn/en-us_topic_0030713153.html index 32fa9c39..1578332d 100644 --- a/docs/ims/umn/en-us_topic_0030713153.html +++ b/docs/ims/umn/en-us_topic_0030713153.html @@ -1,11 +1,11 @@

    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.

    +

    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. So, 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 92d865b2..d8aeb67d 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_0030713178.html b/docs/ims/umn/en-us_topic_0030713178.html index 71ec7281..029da6be 100644 --- a/docs/ims/umn/en-us_topic_0030713178.html +++ b/docs/ims/umn/en-us_topic_0030713178.html @@ -2,7 +2,7 @@

      Is There Any Difference Between the Image Created from a CSBS/CBR Backup and That Created from an ECS?

      No.

      -

      You can create a full-ECS image from an ECS, a CSBS backup, or a CBR backup.

      +

      You can create a full-ECS image from an ECS, a CSBS backup, or a CBR backup.

      When you create a full-ECS image from an ECS, the system first creates a backup for the ECS and then uses the backup to create an image. Therefore, the image is essentially created from an ECS backup no matter you use an ECS or a CSBS/CBR backup.

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

      diff --git a/docs/ims/umn/en-us_topic_0030713184.html b/docs/ims/umn/en-us_topic_0030713184.html index 32b4db57..9c009664 100644 --- a/docs/ims/umn/en-us_topic_0030713184.html +++ b/docs/ims/umn/en-us_topic_0030713184.html @@ -37,7 +37,7 @@
    @@ -63,7 +63,7 @@ - @@ -78,14 +78,14 @@ diff --git a/docs/ims/umn/en-us_topic_0030713185.html b/docs/ims/umn/en-us_topic_0030713185.html index 4c5b5ba9..bbce915b 100644 --- a/docs/ims/umn/en-us_topic_0030713185.html +++ b/docs/ims/umn/en-us_topic_0030713185.html @@ -1,10 +1,10 @@

    What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?

    -

    If an image file is not configured as instructed in Table 1 before it is exported from the original platform, configure it by referring to Figure 1.

    -

    The proper running of ECSs depends on the KVM Guest OS driver (UVP VMTools), without which the performance of ECSs will be affected and some functions will be unavailable. Ensure that the driver installation has been completed for the image file before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.

    +

    If an image file is not configured as instructed in Table 1 before it is exported from the original platform, you can use it to create an ECS, configure the ECS, and use the ECS to create a private image. Figure 1 shows the process.

    +

    An ECS can run properly only after KVM Guest OS drivers (VirtIO drivers) are installed on it. Without these drivers, the performance of this ECS will be affected and some functions will be unavailable. Ensure that the drivers have been installed for the image file before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.

    -

    For details about how to install UVP VMTools, see Installing UVP VMTools.

    +

    To install VirtIO drivers, see Installing VirtIO 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,14 +13,14 @@

    Step 3: Create an ECS

    1. Access the IMS console.
      1. Log in to the management console.
      2. Under Computing, 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.
      +
    5. Click the Private Images tab.
    6. Locate the row that contains the private image and click Apply for Server in the Operation column.
    7. Set parameters as promoted to create an ECS. Note that:
      • Bind an EIP to the ECS so that you can upload installation packages to the ECS or download them from the ECS.
      • You must add inbound rules for the ECS security groups 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 when 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.

      -
    8. 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.
      +
    9. Check the ECS to see if the private image used to create the ECS has been pre-configured.
      1. Check whether the ECS can be successfully started. If it can, Guest OS drivers have been installed for the image file on the original platform or the drivers have been automatically installed for the private image on the cloud platform. If the ECS cannot start up, install Guest OS drivers for the image file on the original platform and go back to Step 1: Upload the Image File.
      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 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 about how to enable this function, 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 abbd454d..44f6d908 100644 --- a/docs/ims/umn/en-us_topic_0030713186.html +++ b/docs/ims/umn/en-us_topic_0030713186.html @@ -1,7 +1,7 @@ -

    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.

    +

    Can I Download a Public Image to My PC?

    +

    You cannot directly download a public image. However, 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 then download the image.

    Helpful links:

    • 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.
    @@ -9,7 +9,7 @@
    diff --git a/docs/ims/umn/en-us_topic_0030713189.html b/docs/ims/umn/en-us_topic_0030713189.html index 43610dca..a678fe86 100644 --- a/docs/ims/umn/en-us_topic_0030713189.html +++ b/docs/ims/umn/en-us_topic_0030713189.html @@ -1,65 +1,78 @@

    Preparing an Image File

    -

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

    -
    +

    You need to prepare an image file that can be used to create a private image.

    +

    Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In addition to the requirements described in Table 2, a bitmap file needs to be generated alongside each RAW image file. The bitmap file is uploaded together with the image file. For details, see Fast Import of an Image File.

    +

    Initial Configuration for an Image File

    The initial configuration must be completed on the source VM before an image file is exported from it. If you did not configure it, use the image file to create an ECS, configure the ECS, and use the ECS to create a private image. For details, see What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?

    -
    Table 1 Supported OSs

    OS

    @@ -22,6 +22,10 @@

    Windows 7 Enterprise 64bit

    Windows 7 Professional 64bit

    Windows 7 Professional 32bit

    +

    Windows Server 2022 Standard 64bit

    +

    Windows Server 2022 Datacenter 64bit

    +

    Windows Server 2019 Standard 64bit

    +

    Windows Server 2019 Datacenter 64bit

    Windows Server 2016 Standard 64bit

    Windows Server 2016 Datacenter 64bit

    Windows Server 2012 R2 Standard 64bit

    @@ -37,7 +41,11 @@

    SUSE

    SUSE Linux Enterprise Server 15 SP1 64bit

    +

    SUSE Linux Enterprise Server 15 SP5 64bit

    +

    SUSE Linux Enterprise Server 15 SP4 64bit

    +

    SUSE Linux Enterprise Server 15 SP3 64bit

    +

    SUSE Linux Enterprise Server 15 SP2 64bit

    +

    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

    @@ -48,7 +56,6 @@

    SUSE Linux Enterprise Server 11 SP4 64bit

    SUSE Linux Enterprise Server 11 SP3 64bit

    SUSE Linux Enterprise Server 11 SP3 32bit

    -

    SUSE Linux Enterprise Server 11 SP1 32bit

    Oracle Linux

    @@ -69,7 +76,16 @@

    Red Hat

    Red Hat Linux Enterprise 8.0 64bit

    +

    Red Hat Linux Enterprise 9.1 64bit

    +

    Red Hat Linux Enterprise 9.0 64bit

    +

    Red Hat Linux Enterprise 8.7 64bit

    +

    Red Hat Linux Enterprise 8.6 64bit

    +

    Red Hat Linux Enterprise 8.5 64bit

    +

    Red Hat Linux Enterprise 8.4 64bit

    +

    Red Hat Linux Enterprise 8.3 64bit

    +

    Red Hat Linux Enterprise 8.2 64bit

    +

    Red Hat Linux Enterprise 8.1 64bit

    +

    Red Hat Linux Enterprise 8.0 64bit

    Red Hat Linux Enterprise 7.6 64bit

    Red Hat Linux Enterprise 7.5 64bit

    Red Hat Linux Enterprise 7.4 64bit

    @@ -90,7 +106,8 @@

    Ubuntu

    Ubuntu 20.04 Server 64bit

    +

    Ubuntu 22.04 Server 64bit

    +

    Ubuntu 20.04 Server 64bit

    Ubuntu 19.04 Server 64bit

    Ubuntu 18.04.2 Server 64bit

    Ubuntu 18.04.1 Server 64bit

    @@ -117,6 +134,10 @@

    openSUSE 42.3 64bit

    openSUSE 42.2 64bit

    openSUSE 42.1 64bit

    +

    openSUSE 15.5 64bit

    +

    openSUSE 15.4 64bit

    +

    openSUSE 15.3 64bit

    +

    openSUSE 15.2 64bit

    openSUSE 15.1 64bit

    openSUSE 15.0 64bit

    openSUSE 13.2 64bit

    @@ -125,7 +146,12 @@

    CentOS

    CentOS 8.0 64bit

    +

    CentOS 8.5 64bit

    +

    CentOS 8.4 64bit

    +

    CentOS 8.3 64bit

    +

    CentOS 8.2 64bit

    +

    CentOS 8.1 64bit

    +

    CentOS 8.0 64bit

    CentOS 7.9 64bit

    CentOS 7.8 64bit

    CentOS 7.7 64bit

    @@ -155,7 +181,29 @@

    Debian

    Debian GNU/Linux 10.0.0 64bit

    +

    Debian GNU/Linux 12.0.0 64bit

    +

    Debian GNU/Linux 11.7.0 64bit

    +

    Debian GNU/Linux 11.6.0 64bit

    +

    Debian GNU/Linux 11.5.0 64bit

    +

    Debian GNU/Linux 11.4.0 64bit

    +

    Debian GNU/Linux 11.3.0 64bit

    +

    Debian GNU/Linux 11.2.0 64bit

    +

    Debian GNU/Linux 11.1.0 64bit

    +

    Debian GNU/Linux 11.0.0 64bit

    +

    Debian GNU/Linux 10.13.0 64bit

    +

    Debian GNU/Linux 10.12.0 64bit

    +

    Debian GNU/Linux 10.11.0 64bit

    +

    Debian GNU/Linux 10.10.0 64bit

    +

    Debian GNU/Linux 10.9.0 64bit

    +

    Debian GNU/Linux 10.8.0 64bit

    +

    Debian GNU/Linux 10.7.0 64bit

    +

    Debian GNU/Linux 10.6.0 64bit

    +

    Debian GNU/Linux 10.5.0 64bit

    +

    Debian GNU/Linux 10.4.0 64bit

    +

    Debian GNU/Linux 10.3.0 64bit

    +

    Debian GNU/Linux 10.2.0 64bit

    +

    Debian GNU/Linux 10.1.0 64bit

    +

    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.8.0 64bit

    @@ -164,12 +212,20 @@

    Debian GNU/Linux 8.5.0 64bit

    Debian GNU/Linux 8.4.0 64bit

    Debian GNU/Linux 8.2.0 64bit

    -

    Debian GNU/Linux 8.1.0 64bit

    Fedora

    Fedora 30 64bit

    +

    Fedora 39 64bit

    +

    Fedora 38 64bit

    +

    Fedora 37 64bit

    +

    Fedora 36 64bit

    +

    Fedora 35 64bit

    +

    Fedora 34 64bit

    +

    Fedora 33 64bit

    +

    Fedora 32 64bit

    +

    Fedora 31 64bit

    +

    Fedora 30 64bit

    Fedora 29 64bit

    Fedora 28 64bit

    Fedora 27 64bit

    @@ -182,23 +238,62 @@

    EulerOS

    EulerOS 2.9 64bit

    +

    EulerOS 2.12 64bit

    +

    EulerOS 2.11 64bit

    +

    EulerOS 2.10 64bit

    +

    EulerOS 2.9 64bit

    +

    EulerOS 2.8 64bit

    +

    EulerOS 2.7 64bit

    EulerOS 2.5 64bit

    EulerOS 2.3 64bit

    EulerOS 2.2 64bit

    EulerOS 2.1 64bit

    CoreOS

    -

    CoreOS 1068.10.0

    -

    CoreOS 1010.5.0

    -

    CoreOS 1298.6.0

    -

    openEuler

    openEuler 20.03 64bit

    +

    openEuler 22.03 SP1 64bit

    +

    openEuler 22.03 64bit

    +

    openEuler 20.03 SP3 64bit

    +

    openEuler 20.03 SP2 64bit

    +

    openEuler 20.03 SP1 64bit

    +

    openEuler 20.03 64bit

    +

    CentOS Stream

    +

    9.6 64bit

    +

    8.6 64bit

    +

    Rocky LInux

    +

    9.2 64bit

    +

    9.1 64bit

    +

    9.0 64bit

    +

    8.8 64bit

    +

    8.7 64bit

    +

    8.6 64bit

    +

    8.5 64bit

    +

    8.4 64bit

    +

    8.3 64bit

    +

    FreeBSD

    +

    13.2 64bit

    +

    13.1 64bit

    +

    13.0 64bit

    +

    12.4 64bit

    +

    12.3 64bit

    +

    12.2 64bit

    +

    12.1 64bit

    +

    12.0 64bit

    +

    11.4 64bit

    +

    11.3 64bit

    +

    11.2 64bit

    +

    11.1 64bit

    +

    11.0 64bit

    This parameter is available only when you select a ZVHD2 or RAW image file.

    This function enables fast image creation and supports import of large files (maximum: 1 TB) as long as the files to be uploaded are converted to ZVHD2 or RAW format and optimized. If you have a file that meets the requirements, select Enable Fast Create and select the confirmation information following Image File Preparation.

    -
    NOTE:

    To learn how to convert image file formats and generate bitmap files, see Quickly Importing an Image File.

    +
    NOTE:

    To learn how to convert image file formats and generate bitmap files, see Fast Import of an Image File.

    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?

    +

    This parameter is optional. The value can be BIOS or UEFI. For details about the differences between them, see How Is BIOS Different from UEFI?

    For details about which OSs support UEFI boot, see OSs Supporting UEFI Boot Mode.

    The boot mode must be the same as that in the image file. You need to confirm which boot mode is used in the image file. After you select the correct boot mode, the boot mode will be configured for the image at the background. Select the right boot mode, or ECSs created using the image will not be able to boot up.

    System Disk (GB)

    The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is at least equal to the system disk capacity in the image file.

    -
    NOTE:

    If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity based on What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?

    +
    NOTE:

    If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity based on Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger Than What I Specified on the Management Console?

    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 capacity, and click Select Image File. In the displayed dialog box, select the target bucket and then the target image file containing the data disk.

    +

    To add data disks, click , configure the data disk capacity, and click Select Image File. In the displayed dialog box, select the target bucket and then the target image file containing the data disk.

    A maximum of three data disks can be added.

    @@ -63,7 +63,7 @@ - @@ -78,14 +78,14 @@ diff --git a/docs/ims/umn/en-us_topic_0030713195.html b/docs/ims/umn/en-us_topic_0030713195.html index 5d817b86..57040664 100644 --- a/docs/ims/umn/en-us_topic_0030713195.html +++ b/docs/ims/umn/en-us_topic_0030713195.html @@ -1,18 +1,18 @@ -

    Image Importing

    +

    Image Import

    diff --git a/docs/ims/umn/en-us_topic_0030713198.html b/docs/ims/umn/en-us_topic_0030713198.html index c9af356c..1c426a3a 100644 --- a/docs/ims/umn/en-us_topic_0030713198.html +++ b/docs/ims/umn/en-us_topic_0030713198.html @@ -1,69 +1,91 @@

    Preparing an Image File

    -

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

    -
    +

    You need to prepare an image file that can be used to create a private image.

    +

    Currently, a large image file (maximum: 1 TB) can be imported only in RAW or ZVHD2 format. In addition to the requirements described in Table 2, a bitmap file needs to be generated alongside each RAW image file. The bitmap file is uploaded together with the image file. For details, see Fast Import of an Image File.

    +

    Initial Configuration for an Image File

    The initial configuration must be completed on the source VM before an image file is exported from it. If you did not configure it, use the image file to create an ECS, configure the ECS, and use the ECS to create a private image. For details, see What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?

    -
    Table 1 Windows image file requirements

    Image File Property

    +
    - - - - - - - - - - - - - - - - - - -
    Table 1 Initial configuration for an image file

    Configuration Item

    Requirement

    +

    How to Configure

    OS

    +

    Network

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

    -

    Image format

    -

    VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD

    -

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

    Network

    -

    The NIC must be set to DHCP. Otherwise, the ECS startup or network capability will be abnormal. For details, see:

    -

    Setting the NIC to DHCP

    -

    The following value-added operations are optional:

    -

    The NIC must be set to DHCP. Otherwise, the ECS startup or network capability will be abnormal. For details, see:

    +

    Setting the NIC to DHCP

    +

    The following operations are optional:

    +

    Tool

    +

    Tools

    You are advised to install Cloudbase-Init.

    -

    Cloudbase-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloudbase-Init, you can use user data injection to inject customized initialization details (for example, an ECS login password) to the ECSs. You can also configure and manage a running ECS by querying and using metadata. If Cloudbase-Init is not installed, you cannot apply custom configurations to the ECSs. You will have to use the original password in the image file to log in to the ECSs.

    -

    For details, see Installing and Configuring Cloudbase-Init.

    +

    You are advised to install Cloudbase-Init.

    +

    Cloudbase-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloudbase-Init, you can use user data injection to inject customized initialization details (for example, an ECS login password) to the ECSs. You can also configure and manage a running ECS by querying and using metadata. If Cloudbase-Init is not installed, you cannot apply custom configurations to the ECSs. You will have to use the original password in the image file to log in to the ECSs.

    +

    For details, see Installing and Configuring Cloudbase-Init.

    +

    If each of your ECSs requires a unique SID in a domain, run Sysprep after Cloudbase-Init is installed. For details, see Running Sysprep.

    Driver

    +

    Drivers

    -

    Installing UVP VMTools

    -

    Other requirements

    -
    • Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk capacity must be between 1 GB and 1 TB.
    • The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
    • The boot partition and system partition must be on the same disk.
    • For an external image file, you need a tenant administrator account and password combination.
    • Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see OSs Supporting UEFI Boot Mode.
    • The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
    +

    An ECS can run properly only after KVM Guest OS drivers (VirtIO drivers) are installed on it. To ensure that ECSs support KVM and to improve network performance, VirtIO drivers must be installed for the image.

    + +

    Installing VirtIO drivers

    +

    For GPU-accelerated ECSs, you need to install special drivers when creating a private image. For details, see Installing Special Windows Drivers.

    +

    Image File Properties

    +
    + + + + + + + + + + + + + +
    Table 2 Windows image file properties

    Image File Property

    +

    Requirement

    +

    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 Guest OS drivers. 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

    +

    VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD

    +

    Image size

    +

    If an image is no larger than 128 GB, import it directly.

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

    Other

    • Currently, images with data disks cannot be created. The image file must contain only a system disk, and the system disk size must be between 1 GB and 1 TB.
    • The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
    • The boot partition and system partition must be on the same disk.
    • For an external image file, you need a tenant administrator account and password combination.
    • Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see OSs Supporting UEFI Boot Mode.
    • The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
    +
    +

    This parameter is available only when you select a ZVHD2 or RAW image file.

    This function enables fast image creation and supports import of large files (maximum: 1 TB) as long as the files to be uploaded are converted to ZVHD2 or RAW format and optimized. If you have a file that meets the requirements, select Enable Fast Create and select the confirmation information following Image File Preparation.

    -
    NOTE:

    To learn how to convert image file formats and generate bitmap files, see Quickly Importing an Image File.

    +
    NOTE:

    To learn how to convert image file formats and generate bitmap files, see Fast Import of an Image File.

    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?

    +

    This parameter is optional. The value can be BIOS or UEFI. For details about the differences between them, see How Is BIOS Different from UEFI?

    For details about which OSs support UEFI boot, see OSs Supporting UEFI Boot Mode.

    The boot mode must be the same as that in the image file. You need to confirm which boot mode is used in the image file. After you select the correct boot mode, the boot mode will be configured for the image at the background. Select the right boot mode, or ECSs created using the image will not be able to boot up.

    System Disk (GB)

    The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is at least equal to the system disk capacity in the image file.

    -
    NOTE:

    If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity based on What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?

    +
    NOTE:

    If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity based on Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger Than What I Specified on the Management Console?

    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 capacity, and click Select Image File. In the displayed dialog box, select the target bucket and then the target image file containing the data disk.

    +

    To add data disks, click , configure the data disk capacity, and click Select Image File. In the displayed dialog box, select the target bucket and then the target image file containing the data disk.

    A maximum of three data disks can be added.

    - @@ -89,7 +89,7 @@

    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

      +
    • 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/archive/epel/7/x86_64/Packages/e/epel-release-7-14.noarch.rpm

  • 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

    @@ -100,7 +100,7 @@
  • Run the following commands to enable Cloud-Init to automatically start upon system boot:

    systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

    systemctl status cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

  • -
  • Debian and Ubuntu

    Before installing Cloud-Init, ensure that the network installation source address has been configured for the OS by checking whether the /etc/apt/sources.list file contains the installation source address of the software package. If the file does not contain the address, configure the address by following the instructions on the Debian or Ubuntu official website.

    +
  • Debian and Ubuntu

    Before installing Cloud-Init, ensure that the network installation source address has been configured for the OS by checking whether the /etc/apt/sources.list file contains the installation source address of the software package. If the file does not contain the address, configure the address by following the instructions on the Debian or Ubuntu official website.

    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

      diff --git a/docs/ims/umn/en-us_topic_0030742197.html b/docs/ims/umn/en-us_topic_0030742197.html index dd466662..290b28e6 100644 --- a/docs/ims/umn/en-us_topic_0030742197.html +++ b/docs/ims/umn/en-us_topic_0030742197.html @@ -1,14 +1,14 @@

      Why Is Sysprep Required for Creating a Private Image from a Windows ECS?

      -

      Why Is Sysprep Required?

      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 image will contain information about the original ECS, especially the SID. ECSs with the same SID cannot be added to a domain. If Windows does not require any user or ECS to be added to a domain, you do not need to run Sysprep.

      -
      +

      Why Is Sysprep Required?

      Sysprep is used to generalize images. It removes server-specific information, like the security identifier (SID), from an image so that ECSs created from this image can have unique SIDs in a domain. If your windows ECSs do not need to join a domain, Sysprep is not required.

      +

      Before running Sysprep, ensure that Windows is activated.

      -

      Restrictions on Running Sysprep

      Sysprep can only be used for configuring a new Windows installation. You can run Sysprep multiple times to install and configure Windows. However, you can reset and activate a Windows OS only three times, and you are not allowed to use Sysprep to re-configure an existing Windows OS.

      -

      In the Windows command line, enter the following command to check how many times you can run Sysprep in the displayed Windows Script Host dialog box:

      +

      Restrictions on Running Sysprep

      Sysprep can only be used to configure new installations of Windows and not to reconfigure an existing installation. You can run Sysprep as many times as required to build and to configure your installation of Windows. However, you can reset Windows activation only up to three times.

      +

      In the Windows command line, run the following command to check how many times you can run Sysprep:

      slmgr /dlv

      -

      If the value of Remaining Windows rearm count is 0, you cannot run Sysprep.

      +

      In the displayed Windows Script Host dialog box, if the value of Remaining Windows rearm count is 0, you cannot run Sysprep.

      diff --git a/docs/ims/umn/en-us_topic_0032042417.html b/docs/ims/umn/en-us_topic_0032042417.html index 2aaa1b7b..69a1b90a 100644 --- a/docs/ims/umn/en-us_topic_0032042417.html +++ b/docs/ims/umn/en-us_topic_0032042417.html @@ -4,13 +4,13 @@

      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.

      The cloud platform is not responsible for the integrity or security of shared images. When you use a shared image, ensure that the image is from a trusted sharer.

      -

      Constraints

      • You can share images only within the region where they reside.
      • Each image can be shared with a maximum of 256 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.
      +

      Constraints

      • You can share images only within the region where they reside.
      • Each image can be shared with a maximum of 256 tenants.
      • Encrypted images cannot be shared.
      • 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 General Sharing FAQs.

      diff --git a/docs/ims/umn/en-us_topic_0032042418.html b/docs/ims/umn/en-us_topic_0032042418.html index dfbfd1bd..4dc86f8c 100644 --- a/docs/ims/umn/en-us_topic_0032042418.html +++ b/docs/ims/umn/en-us_topic_0032042418.html @@ -3,11 +3,11 @@

      Obtaining the Project ID

      Scenarios

      Before a tenant shares an image with you, you need to provide your project ID.

      -

      Procedure

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

          The IMS console is displayed.

          +

          Procedure

          1. Access the IMS console.
            1. Log in to the management console.
            2. Under Computing, 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.

            Images can be shared only within the region where they reside. So, obtain the project ID in the same region.

            -
            Figure 1 Viewing the project ID
            +
            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 098516b6..f88dbaf8 100644 --- a/docs/ims/umn/en-us_topic_0032042419.html +++ b/docs/ims/umn/en-us_topic_0032042419.html @@ -6,13 +6,13 @@

      Prerequisites

      • If the image to be shared is an encrypted image, authorize the key (it must be a custom key) used for encrypting the image. For details, see How Do I Authorize a Key?
      • You have obtained the project ID from the target tenant.
      • Before sharing an image, ensure that any sensitive data has been deleted from the image.
      -

      Procedure

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

            The IMS console is displayed.

            +

            Procedure

            • Share multiple images.
              1. Access the IMS console.
                1. Log in to the management console.
                2. Under Computing, 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 share images only within the region where they reside.
                • If the target tenant is a multi-project user, you can share images to any project of the tenant.
              5. Click OK.
              -
            • Share a single image.
              1. Access the IMS console.
                1. Log in to the management console.
                2. Under Computing, click Image Management Service.

                  The IMS console is displayed.

                  +
                3. Share a single image.
                  1. Access the IMS console.
                    1. Log in to the management console.
                    2. Under Computing, 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 share images only within the region where they reside.
                    • If the target tenant is a multi-project user, you can share images to any project of the tenant.
                    diff --git a/docs/ims/umn/en-us_topic_0032042420.html b/docs/ims/umn/en-us_topic_0032042420.html index 6324a84d..a7d7da8a 100644 --- a/docs/ims/umn/en-us_topic_0032042420.html +++ b/docs/ims/umn/en-us_topic_0032042420.html @@ -7,9 +7,9 @@

                    Prerequisites

                    • Another tenant has shared images with you.
                    • If the shared image is a full-ECS image, you need to create a server backup vault to store the full-ECS image and the backups of the full-ECS image before accepting the shared image. When creating a server backup vault, set Protection Type to Backup.
                    -

                    Procedure

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

                        The IMS console is displayed.

                        +

                        Procedure

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

                            The IMS console is displayed.

                          -
                        2. In the upper left corner, switch to the region where the target project resides and then select the project.
                        3. Click the Images Shared with Me tab.

                          A message is displayed above the image list asking you whether to accept the shared images.

                          +
                        4. In the upper left corner, switch to the region where the target project is and then select the project.
                        5. Click the Images Shared with Me tab.

                          A message is displayed above the image list asking you whether to accept the shared images.

                          • To accept all the shared images, click Accept All in the upper right corner.
                          • To accept some images, select the images and click Accept.
                          • To reject some images, select the images and click Reject.

                          If no message is displayed, check whether you have selected a correct region.

                          diff --git a/docs/ims/umn/en-us_topic_0032307025.html b/docs/ims/umn/en-us_topic_0032307025.html index ec7581bb..ee4326ee 100644 --- a/docs/ims/umn/en-us_topic_0032307025.html +++ b/docs/ims/umn/en-us_topic_0032307025.html @@ -2,12 +2,12 @@

                          What Will the System Do to an Image File When I Use the File to Register a Private Image?

                          You are advised to enable automatic configuration when registering a private image using an image file. Then, the system will perform the following operations:

                          -

                          Linux

                          • Check whether any PV drivers exist. If yes, the system deletes them.
                          • Modify the grub and syslinux configuration files to add the OS kernel boot parameters and change the disk partition name (UUID=UUID of the disk partition).
                          • Change the names of the disk partitions in the /etc/fstab file (UUID=UUID of the disk partition).
                          • Check whether the initrd file has the IDE driver. If no, the system will load the IDE driver.
                          • Modify the X Window configuration file /etc/X11/xorg.conf to prevent display failures.
                          • Delete services of VMware tools.
                          • Record the latest automatic modification made to the image into /var/log/rainbow_modification_record.log.
                          • Copy built-in VirtIO drivers to initrd or initramfs. For details, see External Image File Formats and Supported OSs.
                          -

                          For the following image files, the system does not copy this driver after Enable automatic configuration is selected:

                          +

                          Linux

                          • Check whether any PV drivers exist. If yes, the system deletes them.
                          • Modify the grub and syslinux configuration files to add OS kernel boot parameters and change disk partition names to UUIDs.
                          • Change disk partition names in the /etc/fstab file to UUIDs.
                          • Check whether the initrd file has IDE driver. If no, the system will load the IDE driver.
                          • Modify the X Window configuration file /etc/X11/xorg.conf to prevent display failures.
                          • Delete services of VMware tools.
                          • Record the latest automatic modification made to the image into /var/log/rainbow_modification_record.log.
                          • Copy built-in VirtIO drivers to initrd or initramfs. For details, see External Image File Formats and Supported OSs.
                          +

                          For the following image files, the system does not copy built-in VirtIO drivers after Enable automatic configuration is selected:

                          • Image files whose /usr directory is an independent partition
                          • Fedora 29 64bit, Fedora 30 64bit, and CentOS 8.0 64bit image files that use the XFS file system
                          • SUSE 12 SP4 64bit image files that use the ext4 file system
                          -

                          Windows

                          • Restore the IDE driver so that the OS can use this driver for its initial start.
                          • Delete the registry keys of the mouse and keyboard and generate the registry keys again to ensure that the mouse and keyboard are available on the new cloud platform.
                          • Inject VirtIO drivers offline so that the OS can start without UVP VMTools installed.
                          • Restore DHCP. The OS will dynamically obtain information such as the IP address based on the DHCP protocol.
                          +

                          Windows

                          • Restore the IDE driver so that the OS can use this driver for its initial start.
                          • Delete the registry keys of the mouse and keyboard and generate the registry keys again to ensure that the mouse and keyboard are available on the new cloud platform.
                          • Restore DHCP so that the OS will dynamically obtain information such as the IP address based on the DHCP protocol.
                          diff --git a/docs/ims/umn/en-us_topic_0032326546.html b/docs/ims/umn/en-us_topic_0032326546.html index 9fcbf0cb..5f09016d 100644 --- a/docs/ims/umn/en-us_topic_0032326546.html +++ b/docs/ims/umn/en-us_topic_0032326546.html @@ -1,11 +1,11 @@

                          Image Deletion

                          -

                          Will a Private Image Be Automatically Deleted If I Delete the ECS Used to Create the Image?

                          No. Private images created using ECSs are stored in OBS buckets. Deleting the ECS used to create a private image does not affect the image.

                          +

                          Will a Private Image Be Automatically Deleted If I Delete the ECS Used to Create the Image?

                          No. Private images created using ECSs are stored in OBS buckets. Deleting the ECSs does not affect the images.

                          -

                          Can I Delete an Image I Shared with Others If My Image Quota Becomes Insufficient?

                          Yes. You can delete a shared image without requiring any operation by image recipients. After you delete the image, the image recipients cannot use it any longer. Inform the image recipients to back up their data before you delete the image.

                          +

                          Can I Delete an Image I Shared with Others?

                          • If an image is shared with a project, you can delete the image without requiring any participation from the image recipients. After you delete the image, the image recipients cannot use it any longer. Inform the recipients to back up their data before you delete the image.
                          -

                          How Do I Delete a Shared Image? Does the Deletion Affect an ECS or EVS Disk Created from It?

                          Reject this image on the Images Shared with Me tab page. This does not affect an ECS or EVS disk created from it.

                          +

                          How Do I Delete a Shared Image? Does the Deletion Affect Any ECS or EVS Disk Created from It?

                          Reject this image on the Images Shared with Me tab page. This does not affect any ECS or EVS disk created from it.

                          diff --git a/docs/ims/umn/en-us_topic_0034011241.html b/docs/ims/umn/en-us_topic_0034011241.html index 08c748ac..e8c7be12 100644 --- a/docs/ims/umn/en-us_topic_0034011241.html +++ b/docs/ims/umn/en-us_topic_0034011241.html @@ -4,15 +4,14 @@

                          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 ZVHD2, QCOW2, VMDK, VHD, or ZVHD format. The default format of a private image is ZVHD2. 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.

                            +
                          • The time required for exporting an image depends on the image size and the number of concurrent export tasks.
                          • You can export images in ZVHD2, QCOW2, VMDK, VHD, or ZVHD format. The default format of a private image is ZVHD2. Images exported in different formats may vary in size.
                          • If an image is larger than 128 GB, you can select Enable for Fast Export when exporting the image to an OBS bucket. The image will be exported as a ZVHD2 file. 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

                          • An image can only be exported to a Standard bucket that is in the same region as the image.
                          • The following private images cannot be exported:
                            • Full-ECS images
                            • ISO images
                            • Private images created from a Windows, SUSE, Red Hat, Ubuntu, or Oracle Linux public image
                          • The image size must be less than 1 TB. Images larger than 128 GB support only fast export.
                          -

                          Prerequisites

                          • You have Administrator permissions for OBS.

                            -
                          • An OBS bucket is available in the region where the private image is located.

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

                            +

                            Prerequisites

                            • You have Administrator permissions for OBS.
                            • 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.

                            Procedure

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

                                The IMS console is displayed.

                                diff --git a/docs/ims/umn/en-us_topic_0034220644.html b/docs/ims/umn/en-us_topic_0034220644.html index cd847c03..65f2753a 100644 --- a/docs/ims/umn/en-us_topic_0034220644.html +++ b/docs/ims/umn/en-us_topic_0034220644.html @@ -1,11 +1,11 @@ -

                                What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private Image?

                                -

                                Symptom

                                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 the image. In this case, you need to change the disk partition in the image (UUID=UUID of the disk partition).

                                +

                                What Do I Do If a Partition Is Not Found During the Startup of an ECS Created from an Imported Private Image?

                                +

                                Cause

                                Disk partition IDs are changed after the cross-platform image import. As a result, no partition can be found at startup. In this case, you need to change disk partition IDs in the image to UUIDs.

                                -

                                Solution

                                The following uses openSUSE 13.2 as an example to describe how to change the partition name.

                                -
                                1. Run the following command to query the disk partition ID:

                                  ls -l /dev/disk/by-id/

                                  -

                                  The example command output is as follows.

                                  +

                                  Solution

                                  openSUSE 13.2 is used as an example.

                                  +
                                  1. Check disk partition IDs.

                                    ls -l /dev/disk/by-id/

                                    +

                                    An output similar to the following should be seen:

                                    total 0
                                     lrwxrwxrwx 1 root root 10 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001 -> ../../xvda
                                     lrwxrwxrwx 1 root root 11 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part1 -> ../../xvda1
                                    @@ -27,9 +27,9 @@ lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part7 -&g
                                     lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part8 -> ../../xvda8
                                     lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part9 -> ../../xvda9
                                     lrwxrwxrwx 1 root root 10 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00005 -> ../../xvde
                                    -

                                    ata-QEMU_HARDDISK_xxx and scsi-SATA_QEMU_HARDDISK_xxx indicate that the disk of the ECS is simulated using Quick EMUlator (QEMU). The content on the left of -> is the disk partition ID, and that on the right of -> is the partition name.

                                    -
                                  2. Run the following command to query the disk partition UUID:

                                    ls -l /dev/disk/by-uuid/

                                    -

                                    The example command output is as follows.

                                    +

                                    ata-QEMU_HARDDISK_xxx and scsi-SATA_QEMU_HARDDISK_xxx indicate that the ECS disks are simulated using Quick EMUlator (QEMU). The content on the left of -> are disk partition IDs, and that on the right of -> are partition names.

                                    +
                                  3. Check disk partition UUIDs.

                                    ls -l /dev/disk/by-uuid/

                                    +

                                    An output similar to the following should be seen:

                                    total 0
                                     lrwxrwxrwx 1 root root 11 Jul 22 01:35 45ecd7a0-29da-4402-a017-4564a62308b8 -> ../../xvda5
                                     lrwxrwxrwx 1 root root 11 Jul 22 01:35 55386c6a-9e32-41d4-af7a-e79596221f51 -> ../../xvda9
                                    @@ -38,9 +38,9 @@ lrwxrwxrwx 1 root root 11 Jul 22 01:35 780f36bc-0ada-4c98-9a8d-44570d65333d ->
                                     lrwxrwxrwx 1 root root 11 Jul 22 01:35 b3b7c47f-6a91-45ef-80d6-275b1cc16e19 -> ../../xvda6
                                     lrwxrwxrwx 1 root root 11 Jul 22 01:35 ea63b55d-3b6e-4dcd-8986-956b72bac3e9 -> ../../xvda7
                                     lrwxrwxrwx 1 root root 12 Jul 22 01:35 eb3cc645-925e-4bc5-bedf-c2a6f3b65809 -> ../../xvda10
                                    -

                                    The content on the left of -> is the disk partition UUID, and that on the right of -> is the partition name. Obtain the relationship between the disk partition name, partition ID, and partition UUID.

                                    -
                                  4. Run the following command to check the partition names in the /etc/fstab file:

                                    vi /etc/fstab

                                    -

                                    The example command output is as follows.

                                    +

                                    The content on the left of -> are disk partition UUIDs, and that on the right of -> are partition names. Based on the outputs in 1 and this step, you can obtain the mappings between the partition names, IDs, and UUIDs.

                                    +
                                  5. Open the /etc/fstab file to check partition names.

                                    vi /etc/fstab

                                    +

                                    An example command output is as follows:

                                    /dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part5 / ext3 defaults,errors=panic 1 1
                                     /dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part1 /boot ext3 defaults,errors=panic 1 2
                                     /dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part6 /home ext3 nosuid,errors=panic 1 2
                                    @@ -55,7 +55,7 @@ devpts /dev/pts devpts mode=0620,gid=5 0 0
                                     /dev/cdrom /media/ udf,iso9660 noexec,noauto,nouser,nodev,nosuid 1 2
                                     tmpfs /dev/shm tmpfs noexec,nodev,nosuid 0 0

                                    The values in the first column are the disk partition IDs.

                                    -
                                  6. Press i to enter editing mode. Change the disk partition ID in the row that contains /dev/disk/xxx in the /etc/fstab file in step 3 to UUID=UUID of the disk partition based on the query results in step 1 and step 2.
                                    The modified content is as follows.
                                    UUID=45ecd7a0-29da-4402-a017-4564a62308b8 / ext3 defaults,errors=panic 1 1
                                    +
                                  7. Press i to enter editing mode. Change each disk partition ID to a UUID based on the outputs in 1 and 2.
                                    The modified content is as follows.
                                    UUID=45ecd7a0-29da-4402-a017-4564a62308b8 / ext3 defaults,errors=panic 1 1
                                     UUID=780f36bc-0ada-4c98-9a8d-44570d65333d /boot ext3 defaults,errors=panic 1 2
                                     UUID=b3b7c47f-6a91-45ef-80d6-275b1cc16e19 /home ext3 nosuid,errors=panic 1 2
                                     UUID=eb3cc645-925e-4bc5-bedf-c2a6f3b65809 /opt ext3 defaults,errors=panic 1 2
                                    @@ -69,10 +69,10 @@ devpts /dev/pts devpts mode=0620,gid=5 0 0
                                     /dev/cdrom /media/ udf,iso9660 noexec,noauto,nouser,nodev,nosuid 1 2
                                     tmpfs /dev/shm tmpfs noexec,nodev,nosuid 0 0
                                    -

                                    Ensure that the UUIDs are correct. Otherwise, the ECS cannot start properly.

                                    +

                                    Ensure that the UUIDs are correct, or the ECS will be unable to start up normally.

                                    -
                                  8. Press Esc, enter :wq, and press Enter. The system saves the configuration and exits the vi editor.
                                  9. Check the partition names in the system boot configuration file.

                                    The system boot configuration files vary depending on the OS. Confirm the boot configuration file of the current OS.

                                    -
                                    • Grand Unified Boot Loader (GRUB) configuration file
                                      • /boot/grub/grub.conf
                                      • /boot/grub/menu.lst
                                      • /boot/grub/grub.cfg
                                      • /boot/grub2/grub.cfg
                                      +
                                    • Press Esc, enter :wq, and press Enter. The system saves the configuration and exits the editor.
                                    • Check the partition names in the system boot configuration file.

                                      The system boot configuration file varies depending on the OS. Confirm the boot configuration file of the current OS.

                                      +
                                      • GRUB configuration file
                                        • /boot/grub/grub.conf
                                        • /boot/grub/menu.lst
                                        • /boot/grub/grub.cfg
                                        • /boot/grub2/grub.cfg
                                      • Syslinux configuration file
                                        • /extlinux.conf
                                        • /boot/syslinux/extlinux.conf
                                        • /boot/extlinux/extlinux.conf
                                        • /boot/syslinux/syslinux.cfg
                                        • /syslinux/syslinux.cfg
                                        • /syslinux.cfg

                                      The boot file in this example is /boot/grub/menu.lst. Run the following command to check it:

                                      @@ -82,7 +82,7 @@ timeout 3 title xxx Server OS - xxxxxx kernel /boot/vmlinuz-3.0.101-0.47.52-default root=/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part5 resume= memmap=0x2000000$0x3E000000 nmi_watchdog=2 crashkernel=512M-:256M console=ttyS0,115200 console=tty0 xen_emul_unplug=all initrd /boot/initrd-3.0.101-0.47.52-default -
                                    • Press i to enter editing mode and change the partition names in the system boot configuration file.

                                      Change the disk partition name in the /boot/grub/menu.lst file in 6 to UUID=UUID of the disk partition based on the query results in 1 and 2.

                                      +
                                    • Press i to enter editing mode and change the partition names in the system boot configuration file.

                                      Change each disk partition name in the /boot/grub/menu.lst file in 6 to UUID=UUID of the disk partition based on the query results in 1 and 2.

                                      default 0
                                       timeout 3
                                       title xxx Server OS - xxxxxx
                                      diff --git a/docs/ims/umn/en-us_topic_0037352059.html b/docs/ims/umn/en-us_topic_0037352059.html
                                      index 41dd39de..bc00398a 100644
                                      --- a/docs/ims/umn/en-us_topic_0037352059.html
                                      +++ b/docs/ims/umn/en-us_topic_0037352059.html
                                      @@ -1,40 +1,9 @@
                                       
                                       
                                       

                                      Obtaining Required Software Packages

                                      -

                                      UVP VMTools

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

                                      - -
  • Table 1 Linux image file requirements

    Image File Property

    +
    - - - - - - - - - - - - - - - - - - - - + + +
    Table 1 Initial configuration for an image file

    Configuration Item

    Requirement

    +

    How to Configure

    OS

    +

    Network

    • 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 VirtIO drivers (see Installing Native KVM Drivers). On the image registration page, select Other Linux. After the image is imported, whether the system is started depends on the driver integrity.

    -

    Image format

    -

    VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD

    -

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

    Network

    -

    The NIC must be set to DHCP and files must be deleted from the network role directory. Otherwise, the ECS startup or network capability will be abnormal. For details, see:

    - -

    The following value-added operations are optional:

    -

    The NIC must be set to DHCP and files must be deleted from the network role directory. Otherwise, the ECS startup or network capability will be abnormal. For details, see:

    + +

    The following value-added operations are optional:

    +

    Tool

    +

    Tools

    You are advised to install Cloud-Init.

    -

    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 customized initialization details (for example, an ECS login password) to the ECSs. You can also configure and manage a running ECS by querying and using metadata. If Cloud-Init is not installed, you cannot apply custom configurations to the ECSs. You will have to use the original password in the image file to log in to the ECSs.

    -

    For details, see Installing Cloud-Init.

    +

    You are advised to install Cloud-Init.

    +

    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 customize initialization details (for example, an ECS login password) to the ECSs. You can also configure and manage a running ECS by querying and using metadata. If Cloud-Init is not installed, you cannot apply these custom configurations to your ECSs, and you will have to use the original password in the image file to log in to the ECSs.

    +

    For details, see Installing Cloud-Init.

    Driver

    +

    Drivers

    Installing native KVM drivers

    +

    Installing native KVM drivers

    File system

    +

    File system

    +

    Other requirements

    +

    Data disks

    • Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk capacity must be between 1 GB and 1 TB.
    • The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
    • The boot partition and system partition must be on the same disk.
    • Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see "OSs Supporting UEFI Boot Mode" in Image Service Management User Guide.
    • The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
    • The /etc/fstab file cannot contain automatic mounting information of non-system disks. Otherwise, the login to the created ECS may fail.
    • If the external image file uses LVM as the system disk, ECSs created from the private image do not support file injection.
    • If the VM where the external image file is located has been shut down, it must be a graceful shutdown. Otherwise, a blue screen may occur when the ECS created from the private image is started.
    +

    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 disks from the ECS before using it to create a private image.

    +

    For details, see Detaching Data Disks from an ECS.

    +

    Logs

    +

    If you want to use the ECS console logging function, you need to configure related parameters on the ECS.

    +

    For details, see Configuring Console Logging.

    +

    Image File Properties

    +
    + + + + + + + + + + + + + +
    Table 2 Linux image file properties

    Image File Property

    +

    Requirement

    +

    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 VirtIO drivers (see Installing Native KVM Drivers). On the image registration page, select Other Linux. After the image is imported, whether the system is started depends on the driver integrity.

    +

    Image format

    +

    VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD

    +

    Image size

    +

    Maximum file size: 128 GB

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

    Other

    • Currently, images with data disks cannot be created. The image file must contain only a system disk, and the system disk size must be between 1 GB and 1 TB.
    • The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
    • The boot partition and system partition must be on the same disk.
    • Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see "OSs Supporting UEFI Boot Mode" in Image Service Management User Guide.
    • The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
    • The /etc/fstab file cannot contain automatic mounting information of non-system disks. Otherwise, the login to the created ECS may fail.
    • If the external image file uses LVM as the system disk, ECSs created from the private image do not support file injection.
    • If the VM where the external image file is located has been shut down, it must be a graceful shutdown. Otherwise, a blue screen may occur when the ECS created from the private image is started.
    +
    +

    7 64-bit

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

    +

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

    - - - - - - - - - - - - - - - - - -
    Table 1 UVP VMTools software packages

    Software Package

    -

    OS

    -

    How to Obtain

    -

    vmtools-WIN2008R2-x64.exe

    -

    Windows Server 2008 R2

    -

    https://obs.eu-de.otc.t-systems.com/osdriver/vmtools/windows/vmtools-WIN2008R2-x64.exe

    -

    vmtools-WIN2012-x64.exe

    -

    Windows Server 2012 R2

    -

    https://obs.eu-de.otc.t-systems.com/osdriver/vmtools/windows/vmtools-WIN2012R2-x64.exe

    -

    vmtools-WIN2016-x64.exe

    -
    • Windows Server 2016
    • Windows Server 2019
    -

    https://obs.eu-de.otc.t-systems.com/osdriver/vmtools/windows/vmtools-WIN2016-x64.exe

    -
    -
    +

    VirtIO Drivers

    Download a VirtIO driver package from:

    +

    https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/

    +

    You can select a version as needed.

    diff --git a/docs/ims/umn/en-us_topic_0037352060.html b/docs/ims/umn/en-us_topic_0037352060.html index 59e9ba06..a1e0212e 100644 --- a/docs/ims/umn/en-us_topic_0037352060.html +++ b/docs/ims/umn/en-us_topic_0037352060.html @@ -1,6 +1,6 @@ -

    What Do I Do If I Cannot Share My Images?

    +

    Why Can't I Share My Images?

    • Some images cannot be shared. Therefore, the Share option is not provided for them in the Operation column. The following images cannot be shared:
      • Encrypted images
      • Full-ECS images created from a CSBS backup
    diff --git a/docs/ims/umn/en-us_topic_0037352061.html b/docs/ims/umn/en-us_topic_0037352061.html deleted file mode 100644 index 83ee08b0..00000000 --- a/docs/ims/umn/en-us_topic_0037352061.html +++ /dev/null @@ -1,40 +0,0 @@ - - -

    Installing UVP VMTools

    -

    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:

    -

    Open the version configuration file to check whether UVP VMTools is the latest:

    -

    C:\Program Files (x86)\virtio\bin\version

    -

    If the version is 2.5.0 or later, the current UVP VMTools can be used. Otherwise, perform operations in Installing UVP VMTools to install UVP VMTools.

    -
    -

    Prerequisites

    • An EIP has been bound to the ECS.
    • The UVP VMTools installation package has been downloaded on the ECS. For how to obtain the installation package, see Obtaining Required Software Packages.
    • Ensure that the ECS has at least 50 MB disk space.
    • 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 UVP VMTools is installed.
      -
    -
    -

    Installing UVP VMTools

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

    -
    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 vmtools-WIN2016-x64.zip.
    4. Right-click vmtools-WIN2016-x64.exe, and select Run as administrator from the shortcut menu.
    5. In the displayed dialog box, select I agree to the license terms and conditions and click Install.
      Figure 1 Installing UVP VMTools
      -
    6. Restart the OS for UVP VMTools to take effect.
    7. 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:

    -
    1. Click Start. Choose Control Panel > Programs and Features.
    2. Locate UVP VMTools for Windows.
      If UVP VMTools for Windows exists, the installation is successful, as shown in Figure 2.
      Figure 2 Verifying the installation
      -
      -
    -
    -
    -
    - -
    - - - \ No newline at end of file diff --git a/docs/ims/umn/en-us_topic_0040740508.html b/docs/ims/umn/en-us_topic_0040740508.html index f301e3b7..6827e830 100644 --- a/docs/ims/umn/en-us_topic_0040740508.html +++ b/docs/ims/umn/en-us_topic_0040740508.html @@ -1,6 +1,6 @@ -

    How Do I Configure an ECS, BMS, or Image File Before I Use It to Create an Image?

    +

    How Do I Configure an ECS, a BMS, or an Image File Before I Use It to Create an Image?

    ECS or Image File Configurations

    @@ -12,7 +12,7 @@ - @@ -38,14 +38,14 @@ - - diff --git a/docs/ims/umn/en-us_topic_0041178787.html b/docs/ims/umn/en-us_topic_0041178787.html index 9f41fa7a..7e07249d 100644 --- a/docs/ims/umn/en-us_topic_0041178787.html +++ b/docs/ims/umn/en-us_topic_0041178787.html @@ -8,7 +8,23 @@ - + + + + + + @@ -145,13 +161,13 @@ @@ -189,7 +205,7 @@ - - - @@ -23,59 +23,59 @@ - - - - - - - - - - - @@ -83,42 +83,40 @@

    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.

    -

    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.

    +

    Enable NIC Multi-Queue for the Image

    Windows has not commercially supported NIC multi-queue. If you enable NIC multi-queue for a Windows image, an ECS created from such an image may take longer than normal to start.

    +

    Use any of the following methods to enable NIC multi-queue for an image:

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

        The IMS console is displayed.

      -
    2. On the displayed Private Images page, locate the row that contains the target image and click Modify in the Operation column.
    3. Set NIC multi-queue for the image.
    +
  • On the displayed Private Images page, locate the row that contains the image and click Modify in the Operation column.
  • Enable NIC multi-queue for the image.
  • Method 2:
    1. Access the IMS console.
      1. Log in to the management console.
      2. Under Computing, click Image Management Service.

        The IMS console is displayed.

      -
    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.
    +
  • On the displayed Private Images page, click the name of the image.
  • In the upper right corner of the displayed image details page, click Modify. In the displayed Modify Image dialog box, enable 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.

      -
    4. Add Content-Type to the request header.

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

      +
    5. Add Content-Type to the request header.

      Set Content-Type to application/openstack-images-v2.1-json-patch.

      The request URI is in the following format:

      PATCH /v2/images/{image_id}

      The request body is as follows:
      [       
                { 
                 "op":"add",
                 "path":"/hw_vif_multiqueue_enabled", 
      -          "value": "true" 
      +          "value": true
                } 
        ]
      -

      Figure 1 shows an example request body for setting NIC multi-queue.

      -
      Figure 1 Example request body

    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.

    +

    Enable NIC Multi-Queue on the ECS

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

    For Linux ECSs, which run CentOS 7.4 as an example, perform the following operations to enable NIC multi-queue:

    1. Enable NIC multi-queue.

      1. Log in to the ECS.
      2. Run the following command to obtain the number of queues supported by the NIC and the number of queues with NIC multi-queue enabled:

        ethtool -l NIC

      3. Run the following command to configure the number of queues used by the NIC:

        ethtool -L NIC combined Number of queues

        @@ -138,12 +136,12 @@ Other: 0 Combined: 1 #Indicates that one queue has been enabled. [root@localhost ~]# ethtool -L eth0 combined 4 #Enable four queues on NIC eth0. -

      4. (Optional) Enable irqbalance so that the system automatically allocates NIC interruptions to multiple vCPUs.

        1. Run the following command to enable irqbalance:

          service irqbalance start

          +

        2. (Optional) Enable irqbalance so that the system automatically allocates NIC interrupts to multiple vCPUs.

          1. Run the following command to enable irqbalance:

            service irqbalance start

          2. Run the following command to view the irqbalance status:

            service irqbalance status

            If the Active value in the command output contains active (running), irqbalance has been enabled.

            -
            Figure 2 Enabled irqbalance
            +
            Figure 1 Enabled irqbalance
          -

        3. (Optional) Enable interrupt binding.

          Enabling irqbalance allows the system to automatically allocate NIC interruptions, improving network performance. If the improved network performance fails to meet your expectations, manually configure interrupt affinity on the target ECS.

          +

        4. (Optional) Enable interrupt binding.

          Enabling irqbalance allows the system to automatically allocate NIC interrupts, improving network performance. If the improved network performance fails to meet your expectations, manually configure interrupt affinity on the target ECS.

          The detailed operations are as follows:

          Run the following script so that each ECS vCPU responds the interrupt requests initialized by one queue. That is, one queue corresponds to one interrupt, and one interrupt binds to one vCPU.

          #!/bin/bash
          diff --git a/docs/ims/umn/en-us_topic_0093344231.html b/docs/ims/umn/en-us_topic_0093344231.html
          index 2c00c18d..23bf3af2 100644
          --- a/docs/ims/umn/en-us_topic_0093344231.html
          +++ b/docs/ims/umn/en-us_topic_0093344231.html
          @@ -7,7 +7,7 @@
           

    Procedure

    1. Access the IMS console.

      1. Log in to the management console.
      2. Under Computing, 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 Create Image for Type and then select Full-ECS image for Image Type.
      3. Select CSBS 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.
      +

    3. Create a full-ECS image.

      1. Click Create Image in the upper right corner.
      2. In the Image Type and Source area, select Create Image for Type and then select Full-ECS image for Image Type.
      3. Select CSBS 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.

    diff --git a/docs/ims/umn/en-us_topic_0093842586.html b/docs/ims/umn/en-us_topic_0093842586.html deleted file mode 100644 index 951eccd9..00000000 --- a/docs/ims/umn/en-us_topic_0093842586.html +++ /dev/null @@ -1,297 +0,0 @@ - - -

    How Do I Install the NVIDIA Driver on a P1 ECS?

    -

    Prerequisites

    • The target ECS has had an EIP bound.
    • You have obtained the driver installation package required for an OS. For details, see Table 1.
    - -
    Table 1 ECS configurations

    OS

    Windows

    • Set the NIC to DHCP.
    • Enable remote desktop connection.
    • (Optional) install special Windows drivers.
    • (Optional) Install Cloudbase-Init.
    • Install the Guest OS driver (UVP VMTools).
    • Run Sysprep.
    +
    • Set the NIC to DHCP.
    • Enable remote desktop connection.
    • (Optional) install special Windows drivers.
    • (Optional) Install Cloudbase-Init.
    • Install Guest OS drivers (VirtIO drivers).
    • Run Sysprep.

    Creating a System Disk Image from a Windows ECS

    Windows

    • Set the NIC to DHCP.
    • Enable remote desktop connection.
    • Install the Guest OS driver (UVP VMTools).
    • (Optional) Install Cloudbase-Init.
    • (Optional) Enable NIC multi-queue.
    +
    • Set the NIC to DHCP.
    • Enable remote desktop connection.
    • Install Guest OS drivers (VirtIO drivers).
    • (Optional) Install Cloudbase-Init.
    • (Optional) Enable NIC multi-queue.

    Preparing an Image File

    Linux

    • Delete files from the network rule directory.
    • Set the NIC to DHCP.
    • Install native KVM drivers.
    • Change the disk identifier in the GRUB configuration file to UUID.
    • Change the disk identifier in the fstab file to UUID.
    • Delete the automatic attachment information of non-system disks from the /etc/fstab file.
    • (Optional) Install Cloud-Init.
    • (Optional) Enable NIC multi-queue.
    +
    • Delete files from the network rule directory.
    • Set the NIC to DHCP.
    • Install native KVM drivers.
    • Change the disk identifier in the GRUB configuration file to UUID.
    • Change the disk identifier in the fstab file to UUID.
    • Delete the automatic mount configuration of non-system disks from the /etc/fstab file.
    • (Optional) Install Cloud-Init.
    • (Optional) Enable NIC multi-queue.

    Preparing an Image File

    2024-05-11

    +

    2024-08-12

    +

    Modified the following content:

    +

    Updated the supported OSs in External Image File Formats and Supported OSs.

    +

    2024-06-07

    +

    Added the following content:

    +

    Installing VirtIO Drivers

    +

    Modified the following content:

    +

    Updated GPU drivers and deleted the InfiniBand NIC driver in Installing Special Linux Drivers.

    +

    Deleted the "Installing UVP VMTools" section.

    +

    Deleted the "How Do I Install the NVIDIA Driver on a P1 ECS?" section.

    +

    2024-05-11

    Modified the following content:

    Deleted ECSs from OSs Supported by Different Types of ECSs that have been taken offline, including M2, P1, P2, HL1, H2, FP1c, and FP1cne.

    @@ -26,10 +42,10 @@

    2023-10-30

    Added the following content:

    - +

    Modified the following content:

    • Added the figure showing relationships between IMS and other services in Related Services.
    - +

    2023-05-10

    @@ -53,15 +69,15 @@

    2023-03-17

    Modified the following content:

    - +
    • Updated image export restrictions in 1.
    • Updated the steps for installing UVP VMTools.

    2023-02-14

    Modified the following content:

    - +

    Deleted the following sections:

    -
    • Installing the PV Driver
    • Uninstalling PV Drivers from a Linux ECS
    • How Do I Install Native Xen and KVM Drivers?
    • What Do I Do If the Disks of an ECS Created from a CentOS Image Cannot Be Found?
    +
    • Installing PV Drivers
    • Uninstalling PV Drivers from a Linux ECS
    • How Do I Install Native Xen and KVM Drivers?
    • What Do I Do If the Disks of an ECS Created from a CentOS Image Cannot Be Found?

    2023-02-07

    @@ -85,17 +101,17 @@

    2022-10-31

    Added the following content:

    - +

    Modified the following content:

    - +

    2021-08-15

    Added the following content:

    - +

    Modified the following content:

    - +

    2020-08-12

    @@ -121,7 +137,7 @@

    2019-03-29

    Added the following content:

    -

    What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mode?

    +

    What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using UEFI Boot?

    Modified the following content:

    2018-12-21

    Modified the following content:

    - +

    2018-09-30

    Added the following content:

    -

    Added Quickly Importing an Image File.

    +

    Added Fast Import of an Image File.

    Modified the following content:

    2018-05-30

    Modified the following content:

    Changed Tools for Windows to Guest OS drivers.

    @@ -279,7 +295,7 @@

    2017-04-28

    Modified the following content:

    Added support for external image files containing CoreOS 1298.6.0 in External Image File Formats and Supported OSs.

    diff --git a/docs/ims/umn/en-us_topic_0046588154.html b/docs/ims/umn/en-us_topic_0046588154.html index 11d9456c..41ae1408 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. For details, see Creating a User and Granting Permissions.

    -

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

    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.
    diff --git a/docs/ims/umn/en-us_topic_0047501112.html b/docs/ims/umn/en-us_topic_0047501112.html index dd220bad..55d75c1a 100644 --- a/docs/ims/umn/en-us_topic_0047501112.html +++ b/docs/ims/umn/en-us_topic_0047501112.html @@ -1,8 +1,8 @@

    Optimization Process

    -

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

    -
    1. Create an ECS using the Windows private image to be optimized and log in to the ECS.
    2. Install the UVP VMTools which is required to create ECSs using KVM virtual resources.

      For details, see Installing UVP VMTools.

      +

      An ECS can run properly only after KVM Guest OS drivers (VirtIO drivers) are installed on it. To ensure that ECSs support KVM and to improve network performance, VirtIO drivers must be installed for the image.

      +
      1. Create an ECS from the Windows private image to be optimized and log in to the ECS.
      2. Install VirtIO drivers that are needed to create KVM ECSs.

        For details, see Installing VirtIO Drivers.

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

        For details, see Clearing System Logs.

      5. Create a Windows private image from the ECS.
      diff --git a/docs/ims/umn/en-us_topic_0049177180.html b/docs/ims/umn/en-us_topic_0049177180.html index 00e3f031..1282e4ee 100644 --- a/docs/ims/umn/en-us_topic_0049177180.html +++ b/docs/ims/umn/en-us_topic_0049177180.html @@ -1,10 +1,10 @@

      Replicating Images

      -

      Scenarios

      You can convert encrypted and unencrypted images into each other or enable some advanced features (such as fast ECS creation from an image) using the image replication function. You may need to replicate an image to:

      +

      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 image replication. You may need to replicate an image to:

      • Replicate an encrypted image to an unencrypted one.
      • Replicate an encrypted image to an encrypted one.

        Keys for encrypting the images cannot be changed. If you want to change the key of an encrypted image, you can replicate this image to a new one and encrypt the new image using an encryption key.

      • Replicate an unencrypted image to an encrypted one.

        If you want to store an unencrypted image in an encrypted way, you can replicate this image as a new one and encrypt the new image using a key.

        -
      • Optimize a system disk image so that it can be used to quickly create ECSs.

        Fast Create greatly reduces the time required for creating ECSs from a system disk image. Currently, this feature is supported by all newly created system disk images by default. Existing system disk images may not support this function. You can optimize the images using the image replication function. For example, if image A does not support fast ECS creation, you can replicate it to generate image copy_A that supports fast ECS creation.

        +
      • Optimize a system disk image so that it can be used to quickly create ECSs.

        Fast Create greatly reduces the time required for creating ECSs from a system disk image. Currently, this feature is supported by all newly created system disk images by default. Existing system disk images may not support this function. You can optimize the images 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 replicated.
      • Private images created using ISO files do not support in-region replication.
      diff --git a/docs/ims/umn/en-us_topic_0049196765.html b/docs/ims/umn/en-us_topic_0049196765.html index f10ba312..aa851279 100644 --- a/docs/ims/umn/en-us_topic_0049196765.html +++ b/docs/ims/umn/en-us_topic_0049196765.html @@ -1,7 +1,7 @@

      Image Encryption

      -

      How Can I Change an Unencrypted Image to an Encrypted One?

      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 replica of the unencrypted image.

      +

      How Can I Change an Unencrypted Image to an Encrypted One?

      You can select an encryption key when you replicate the image. Then, the system will generate an encrypted version of the unencrypted image.

      diff --git a/docs/ims/umn/en-us_topic_0049196766.html b/docs/ims/umn/en-us_topic_0049196766.html index ab2fd1c7..0bb882f0 100644 --- a/docs/ims/umn/en-us_topic_0049196766.html +++ b/docs/ims/umn/en-us_topic_0049196766.html @@ -2,7 +2,7 @@

      How Can I Back Up the Current Status of an ECS for Restoration in the Case of a System Fault?

      You can back up the ECS in any of the following ways:

      -
      • (Recommended) Use CBR to create a scheduled backup task for the ECS. If the ECS fails, select a backup corresponding to the time you want the ECS to restore to, create a full-ECS image from the backup, and use the image to apply for a new ECS or to reinstall the OS.
      • Create a system disk image from the ECS. If the ECS fails, use the system disk image to apply for a new ECS or to reinstall the OS.
      • Create a snapshot for the system disk of the ECS. If the ECS fails, you can roll it back from the snapshot.
      +
      • (Recommended) Use CBR to create a scheduled backup for the ECS. If the ECS fails, select a backup you want to use to restore the ECS, create a full-ECS image from the backup, and use the image to create a new ECS or to reinstall the OS of the ECS.
      • Create a system disk image from the ECS. If the ECS fails, use the system disk image to create a new ECS or to reinstall the OS.
      • Create a snapshot for the system disk of the ECS. If the ECS fails, you can restore the system disk data from the snapshot.
  • For SUSE Linux 12, openSUSE 13, and openSUSE 42, perform the following steps:
    1. Run the following command to open the configuration file:

      vi /boot/grub2/grub.cfg

      -
    2. Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    +
  • Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
  • For Debian and Ubuntu 16, perform the following steps:
    1. Run the following command to open the configuration file:

      vi /boot/grub/grub.cfg

      -
    2. Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    +
  • Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
  • For Fedora, perform the following steps:
    1. Run the following command to open the configuration file:

      vi /boot/grub2/grub.cfg

      -
    2. Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
    +
  • Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
  • For FreeBSD, perform the following steps:
    1. Run the following command to open the configuration file:

      vi /boot/loader.conf

      -
    2. Add console="comconsole". If console="comconsole" already exists, you do not need to add it. Save the change and exit.
    +
  • Add console="comconsole". If console="comconsole" already exists, you do not need to add it. Save the change and exit.
  • For CoreOS, perform the following steps:
    1. Run the following command to check whether ttyS0 has been configured:

      cat /proc/cmdline | grep ttyS0

      • If yes, ttyS0 has been configured.
      • If no, ttyS0 has not been configured. Go to 2.
    2. Run the following command to open the configuration file to be edited:

      vi /usr/share/oem/grub.cfg

      diff --git a/docs/ims/umn/en-us_topic_0058841396.html b/docs/ims/umn/en-us_topic_0058841396.html index aaa404a2..11c8f3bf 100644 --- a/docs/ims/umn/en-us_topic_0058841396.html +++ b/docs/ims/umn/en-us_topic_0058841396.html @@ -1,21 +1,20 @@ -

      What Do I Do If the System Disk Capacity in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?

      -
      The possible causes may be:
      1. You have specified a small value.

        Check the system disk capacity in the VHD image file. Specify a value no less than this value when you use the VHD image file to register an image.

        -
      2. After being converted using qemu-img or a similar tool, the VHD's virtual disk size becomes smaller than the actual system disk size. For details, see https://bugs.launchpad.net/qemu/+bug/1490611.

        Run the following command to check the VHD image file information:

        +

        Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger Than What I Specified on the Management Console?

        +
        The possible causes may be:
        1. Too small a value was specified when registering the image. Check the system disk capacity in the VHD image file. Specify a value at least this large when you use the VHD image file to register an image.
        2. The VHD's actual disk size is larger than its virtual size. This can happen if the VHD image file was generated using qemu-img or a similar tool. For details, see https://bugs.launchpad.net/qemu/+bug/1490611.

          Run the following command to check the VHD image file information:

          [xxxx@xxxxx test]$ qemu-img info 2g.vhd
           image: 2g.vhd
           file format: vpc
           virtual size: 2.0G (2147991552 bytes)
           disk size: 8.0K
           cluster_size: 2097152
          -

          The virtual size is converted from the actual size (unit: byte) to an integer in GB. After the conversion, the output virtual size 2 GB is smaller than the input actual size 2.0004 GB (2147991552 bytes). You need to specify an integer larger than the actual size 2.0004 GB on the management console.

          +

          The virtual size is always an integer number of GBs. As a result, if an actual size is, like in the example here, 2147991552 bytes (2.0004 GB), the virtual size will be only 2 GB. In this example, you need to specify an integer larger than the actual size 2.0004 GB. The system disk capacity on the management console can only be an integer value, so you enter an integer larger than 2 GB.

        diff --git a/docs/ims/umn/en-us_topic_0068002265.html b/docs/ims/umn/en-us_topic_0068002265.html index a3aa7d9f..3895e1c8 100644 --- a/docs/ims/umn/en-us_topic_0068002265.html +++ b/docs/ims/umn/en-us_topic_0068002265.html @@ -25,7 +25,7 @@

        After you accept private image image_test with tag (Enterprise=A) which is shared by another tenant, you can search for the image by tag.

        You cannot add tags to a shared image. The tags of a shared image are added by the tenant who shares the image with you.

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

          The Private Images page is displayed.

          +
          1. Log in to the management console.
          2. Under Computing, 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_0069896389.html b/docs/ims/umn/en-us_topic_0069896389.html index 06fc85a0..bd31d8e8 100644 --- a/docs/ims/umn/en-us_topic_0069896389.html +++ b/docs/ims/umn/en-us_topic_0069896389.html @@ -1,7 +1,7 @@

            How Can I Apply a Private Image to an Existing ECS?

            -
            • You can change the OS of the ECS later. When you change the OS, select the created private image. For details about how to change the OS, see "Changing the OS" in Elastic Cloud Server User Guide.
            +
            • You can use the image to change the ECS OS. When you change the OS, select that image. For details about how to change the OS, see "Changing the OS" in Elastic Cloud Server User Guide.
  • Image

    Supported By

    +

    Support for NIC Multi-Queue

    Windows Server 2008 WEB R2 64bit

    Private images

    +

    Yes (only supported by private images)

    Windows Server 2008 R2 Standard/Datacenter/Enterprise 64bit

    Private images

    +

    Yes (only supported by private images)

    Windows Server 2012 R2 Standard/Datacenter 64bit

    Private images

    +

    Yes (only supported by private images)

    Windows Server 2016 Standard/Datacenter 64bit

    Private images

    +

    Yes (only supported by private images)

    Linux

    Ubuntu 14.04/16.04 Server 64bit

    Public images

    +

    Yes

    openSUSE 42.2 64bit

    Public images

    +

    Yes

    SUSE Enterprise 12 SP1/SP2 64bit

    Public images

    +

    Yes

    CentOS 6.8/6.9/7.0/7.1/7.2/7.3/7.4/7.5/7.6 64bit

    Public images

    +

    Yes

    Debian 8.0.0/8.8.0/8.9.0/9.0.0 64bit

    Public images

    +

    Yes

    Fedora 24/25 64bit

    Public images

    +

    Yes

    EulerOS 2.2 64bit

    Public images

    +

    Yes

    - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 1 NVIDIA drivers

    OS

    -

    Driver

    -

    How to Obtain

    -

    Ubuntu 16.04

    -

    GPU driver installation package NVIDIA-Linux-x86_64-375.66.run

    -

    http://www.nvidia.com/download/driverResults.aspx/118955/en-us

    -

    CUDA Toolkit installation package cuda_8.0.61_375.26_linux.run

    -

    https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda_8.0.61_375.26_linux-run

    -

    CentOS 7.4

    -

    GPU driver installation package NVIDIA-Linux-x86_64-375.66.run

    -

    http://www.nvidia.com/download/driverResults.aspx/118955/en-us

    -

    CUDA Toolkit installation package cuda_8.0.61_375.26_linux.run

    -

    https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda_8.0.61_375.26_linux-run

    -

    Debian 9.0

    -

    GPU driver installation package NVIDIA-Linux-x86_64-384.81.run

    -

    http://www.nvidia.com/download/driverResults.aspx/124722/en-us

    -

    CUDA Toolkit installation package cuda_9.0.176_384.81_linux.run

    -

    https://developer.nvidia.com/compute/cuda/9.0/Prod/local_installers/cuda_9.0.176_384.81_linux-run

    -
    -
    -
    -

    Procedure

    The procedure for installing the NVIDIA driver varies according to the OS.

    -
    • Ubuntu 16.04 64bit
    -
    1. Log in to the target ECS and run the following command to switch to user root:

      sudo su

      -

    2. (Optional) Install the GCC and g++ software.

      Perform this step only if the GCC and g++ software has not been installed.

      -

      apt-get install gcc

      -

      apt-get install g++

      -

      apt-get install make

      -

    3. (Optional) Disable the Nouveau driver.

      Perform this step if the Nouveau driver has been installed on the target ECS. This prevents conflict with the NVIDIA driver installation.

      -
      1. Run the following command to check whether the Nouveau driver is running on the target ECS:

        lsmod | grep nouveau

        -
        • If yes, go to 3.b.
        • If no, go to 4.
        -
      2. Add the following statement to the end of the /etc/modprobe.d/blacklist.conf file:

        blacklist nouveau

        -

        options nouveau modeset=0

        -
      3. Run the following commands to back up and create an initramfs application:

        mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak

        -

        update-initramfs -u

        -
      4. Run the following command to restart the ECS:

        reboot

        -
      -

    4. (Optional) Disable the X service.

      If the ECS has been logged in using the GUI, disable the X service before installing the NVIDIA driver.

      -
      1. Run the following command to switch to multi-user mode:

        systemctl set-default multi-user.target

        -
      2. Run the following command to restart the ECS:

        reboot

        -
      -

    5. (Optional) Install the GPU driver.

      You can either use the GPU driver provided in the CUDA Toolkit installation package or download the required GPU driver. Unless otherwise specified, you are advised to install GPU driver NVIDIA-Linux-x86_64-375.66.run, which has been fully verified.
      1. Upload the GPU driver installation package NVIDIA-Linux-x86_64-xxx.yy.run to the /tmp directory of the ECS.

        To download the GPU driver, log in at http://www.nvidia.com/Download/index.aspx?lang=en.

        -
        Figure 1 Downloading the GPU driver
        -
      2. Run the following command to install the GPU driver:

        sh ./NVIDIA-Linux-x86_64-xxx.yy.run

        -
      3. Run the following command to delete the installation package:

        rm -f NVIDIA-Linux-x86_64-xxx.yy.run

        -
      -
      -

    6. Install the CUDA Toolkit.

      Unless otherwise specified, you are advised to install CUDA Toolkit cuda_8.0.61_375.26_linux.run, which has been fully verified.
      1. Upload the CUDA Toolkit installation package cuda_a.b.cc_xxx.yy_linux.run to the /tmp directory of the ECS.

        To download the CUDA Toolkit, log in at https://developer.nvidia.com/cuda-downloads.

        -
      2. Run the following command to change the permission:

        chmod +x cuda_a.b.cc_xxx.yy_linux.run

        -
      3. Run the following command to install the CUDA Toolkit:

        ./cuda_a.b.cc_xxx.yy_linux.run -toolkit -samples -silent -override --tmpdir=/tmp/

        -
      4. Run the following command to delete the installation package:

        rm -f cuda_a.b.cc_xxx.yy_linux.run

        -
      5. Run the following commands to check whether the installation is successful:

        cd /usr/local/cuda/samples/1_Utilities/deviceQueryDrv/

        -

        make

        -

        ./deviceQueryDrv

        -

        If the terminal display contains "Result = PASS", both CUDA Toolkit and GPU driver have been installed.

        -
        ./deviceQueryDrv Starting...  
        -   
        - CUDA Device Query (Driver API) statically linked version   
        - Detected 1 CUDA Capable device(s)  
        -   
        - Device 0: "Tesla P100-PCIE-16GB"  
        -   CUDA Driver Version:                           8.0  
        -   CUDA Capability Major/Minor version number:    6.0  
        -   Total amount of global memory:                 16276 MBytes (17066885120 bytes)  
        -   (56) Multiprocessors, ( 64) CUDA Cores/MP:     3584 CUDA Cores  
        -   GPU Max Clock rate:                            1329 MHz (1.33 GHz)  
        -   Memory Clock rate:                             715 Mhz  
        -   Memory Bus Width:                              4096-bit  
        -   L2 Cache Size:                                 4194304 bytes  
        -   Max Texture Dimension Sizes                    1D=(131072) 2D=(131072, 65536) 3D=(16384, 16384, 16384)  
        -   Maximum Layered 1D Texture Size, (num) layers  1D=(32768), 2048 layers  
        -   Maximum Layered 2D Texture Size, (num) layers  2D=(32768, 32768), 2048 layers  
        -   Total amount of constant memory:               65536 bytes  
        -   Total amount of shared memory per block:       49152 bytes  
        -   Total number of registers available per block: 65536  
        -   Warp size:                                     32  
        -   Maximum number of threads per multiprocessor:  2048  
        -   Maximum number of threads per block:           1024  
        -   Max dimension size of a thread block (x,y,z): (1024, 1024, 64)  
        -   Max dimension size of a grid size (x,y,z):    (2147483647, 65535, 65535)  
        -   Texture alignment:                             512 bytes  
        -   Maximum memory pitch:                          2147483647 bytes  
        -   Concurrent copy and kernel execution:          Yes with 2 copy engine(s)  
        -   Run time limit on kernels:                     No  
        -   Integrated GPU sharing Host Memory:            No  
        -   Support host page-locked memory mapping:       Yes  
        -   Concurrent kernel execution:                   Yes  
        -   Alignment requirement for Surfaces:            Yes  
        -   Device has ECC support:                        Enabled  
        -   Device supports Unified Addressing (UVA):      Yes  
        -   Device PCI Domain ID / Bus ID / location ID:   0 / 0 / 6  
        -   Compute Mode:  
        -      < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >  
        - Result = PASS 
        -
      -
      -

    -
    • CentOS 7.4
    -
    1. Log in to the target ECS and run the following command to switch to user root:

      sudo su

      -

    2. (Optional) Install GCC, g++, and kernel-devel.

      Perform this step only if GCC, g++, and kernel-devel have not been installed.

      -

      yum install gcc

      -

      yum install gcc-c++

      -

      yum install make

      -

      yum install kernel-devel-`uname -r`

      -

    3. (Optional) Disable the Nouveau driver.

      Perform this step if the Nouveau driver has been installed on the target ECS. This prevents conflict with the NVIDIA driver installation.

      -
      1. Run the following command to check whether the Nouveau driver is running on the target ECS:

        lsmod | grep nouveau

        -
        • If yes, go to 3.b.
        • If no, go to 4.
        -
      2. Add the following statement to the end of the /etc/modprobe.d/blacklist.conf file:

        blacklist nouveau

        -
      3. Run the following commands to back up and create an initramfs application:

        mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak

        -

        dracut -v /boot/initramfs-$(uname -r).img $(uname -r)

        -
      4. Run the following command to restart the ECS:

        reboot

        -
      -

    4. (Optional) Disable the X service.

      If the ECS has been logged in using the GUI, disable the X service before installing the NVIDIA driver.

      -
      1. Run the following command to switch to multi-user mode:

        systemctl set-default multi-user.target

        -
      2. Run the following command to restart the ECS:

        reboot

        -
      -

    5. (Optional) Install the GPU driver.

      You can either use the GPU driver provided in the CUDA Toolkit installation package or download the required GPU driver. Unless otherwise specified, you are advised to install GPU driver NVIDIA-Linux-x86_64-375.66.run, which has been fully verified.
      1. Upload the GPU driver installation package NVIDIA-Linux-x86_64-xxx.yy.run to the /tmp directory of the ECS.

        To download the GPU driver, log in at http://www.nvidia.com/Download/index.aspx?lang=en.

        -
        Figure 2 Downloading the driver installation package
        -
      2. Run the following command to install the GPU driver:

        sh ./NVIDIA-Linux-x86_64-xxx.yy.run

        -
      3. Run the following command to delete the installation package:

        rm -f NVIDIA-Linux-x86_64-xxx.yy.run

        -
      -
      -

    6. Install the CUDA Toolkit.

      Unless otherwise specified, you are advised to install CUDA Toolkit cuda_8.0.61_375.26_linux.run, which has been fully verified.
      1. Upload the CUDA Toolkit installation package cuda_a.b.cc_xxx.yy_linux.run to the /tmp directory of the ECS.

        To download the CUDA Toolkit, log in at https://developer.nvidia.com/cuda-downloads.

        -
      2. Run the following command to change the permission:

        chmod +x cuda_a.b.cc_xxx.yy_linux.run

        -
      3. Run the following command to install the CUDA Toolkit:

        ./cuda_a.b.cc_xxx.yy_linux.run -toolkit -samples -silent -override --tmpdir=/tmp/

        -
      4. Run the following command to delete the installation package:

        rm -f cuda_a.b.cc_xxx.yy_linux.run

        -
      5. Run the following commands to check whether the installation is successful:

        cd /usr/local/cuda/samples/1_Utilities/deviceQueryDrv/

        -

        make

        -

        ./deviceQueryDrv

        -

        If the terminal display contains "Result = PASS", both CUDA Toolkit and GPU driver have been installed.

        -
        ./deviceQueryDrv Starting...  
        -   
        - CUDA Device Query (Driver API) statically linked version   
        - Detected 1 CUDA Capable device(s)  
        -   
        - Device 0: "Tesla P100-PCIE-16GB"  
        -   CUDA Driver Version:                           8.0  
        -   CUDA Capability Major/Minor version number:    6.0  
        -   Total amount of global memory:                 16276 MBytes (17066885120 bytes)  
        -   (56) Multiprocessors, ( 64) CUDA Cores/MP:     3584 CUDA Cores  
        -   GPU Max Clock rate:                            1329 MHz (1.33 GHz)  
        -   Memory Clock rate:                             715 Mhz  
        -   Memory Bus Width:                              4096-bit  
        -   L2 Cache Size:                                 4194304 bytes  
        -   Max Texture Dimension Sizes                    1D=(131072) 2D=(131072, 65536) 3D=(16384, 16384, 16384)  
        -   Maximum Layered 1D Texture Size, (num) layers  1D=(32768), 2048 layers  
        -   Maximum Layered 2D Texture Size, (num) layers  2D=(32768, 32768), 2048 layers  
        -   Total amount of constant memory:               65536 bytes  
        -   Total amount of shared memory per block:       49152 bytes  
        -   Total number of registers available per block: 65536  
        -   Warp size:                                     32  
        -   Maximum number of threads per multiprocessor:  2048  
        -   Maximum number of threads per block:           1024  
        -   Max dimension size of a thread block (x,y,z): (1024, 1024, 64)  
        -   Max dimension size of a grid size (x,y,z):    (2147483647, 65535, 65535)  
        -   Texture alignment:                             512 bytes  
        -   Maximum memory pitch:                          2147483647 bytes  
        -   Concurrent copy and kernel execution:          Yes with 2 copy engine(s)  
        -   Run time limit on kernels:                     No  
        -   Integrated GPU sharing Host Memory:            No  
        -   Support host page-locked memory mapping:       Yes  
        -   Concurrent kernel execution:                   Yes  
        -   Alignment requirement for Surfaces:            Yes  
        -   Device has ECC support:                        Enabled  
        -   Device supports Unified Addressing (UVA):      Yes  
        -   Device PCI Domain ID / Bus ID / location ID:   0 / 0 / 6  
        -   Compute Mode:  
        -      < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >  
        - Result = PASS 
        -
      -
      -

    -
    • Debian 9.0 OS
    -
    1. Log in to the target ECS and run the following command to switch to user root:

      sudo su

      -

    2. (Optional) Install the dependency software GCC and g++ of the NVIDIA driver.

      Perform this step only if the GCC and g++ software has not been installed.

      -

      apt-get install gcc

      -

      apt-get install g++

      -

      apt-get install make

      -

      apt-get install linux-headers-$(uname -r)

      -

    3. (Optional) Disable the Nouveau driver.

      Perform this step if the Nouveau driver has been installed on the target ECS. This prevents conflict with the NVIDIA driver installation.

      -
      1. Run the following command to check whether the Nouveau driver is running on the target ECS:

        lsmod | grep nouveau

        -
        • If yes, go to 3.b.
        • If no, go to 4.
        -
      2. Add the following statement to the end of the /etc/modprobe.d/blacklist.conf file:

        blacklist nouveau

        -

        options nouveau modeset=0

        -
      3. Run the following commands to back up and create an initramfs application:

        mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak

        -

        update-initramfs -u

        -
      4. Run the following command to restart the ECS:

        reboot

        -
      -

    4. (Optional) Disable the X service.

      If the ECS has been logged in using the GUI, disable the X service before installing the NVIDIA driver.

      -
      1. Run the following command to switch to multi-user mode:

        systemctl set-default multi-user.target

        -
      2. Run the following command to restart the ECS:

        reboot

        -
      -

    5. (Optional) Install the GPU driver.

      You can either use the GPU driver provided in the CUDA Toolkit installation package or download the required GPU driver. Unless otherwise specified, you are advised to install GPU driver NVIDIA-Linux-x86_64-384.81.run, which has been fully verified.
      1. Upload the GPU driver installation package NVIDIA-Linux-x86_64-xxx.yy.run to the /tmp directory of the ECS.

        To download the GPU driver, log in at http://www.nvidia.com/Download/index.aspx?lang=en.

        -
        Figure 3 Downloading the GPU driver
        -
      2. Run the following command to install the GPU driver:

        sh ./NVIDIA-Linux-x86_64-xxx.yy.run

        -
      3. Run the following command to delete the installation package:

        rm -f NVIDIA-Linux-x86_64-xxx.yy.run

        -
      -
      -

    6. Install the CUDA Toolkit.

      The CUDA Toolkit version required by Debian 9.0 GCC must be 9.0 or later. Unless otherwise specified, you are advised to install CUDA Toolkit cuda_9.0.176_384.81_linux.run, which has been fully verified.
      1. Upload the CUDA Toolkit installation package cuda_a.b.cc_xxx.yy_linux.run to the /tmp directory of the ECS.

        To download the CUDA Toolkit, log in at https://developer.nvidia.com/cuda-downloads.

        -
      2. Run the following command to change the permission:

        chmod +x cuda_a.b.cc_xxx.yy_linux.run

        -
      3. Run the following command to install the CUDA Toolkit:

        ./cuda_a.b.cc_xxx.yy_linux.run -toolkit -samples -silent -override --tmpdir=/tmp/

        -
      4. Run the following command to delete the installation package:

        rm -f cuda_a.b.cc_xxx.yy_linux.run

        -
      5. Run the following commands to check whether the installation is successful:

        cd /usr/local/cuda/samples/1_Utilities/deviceQueryDrv/

        -

        make

        -

        ./deviceQueryDrv

        -

        If the terminal display contains "Result = PASS", both CUDA Toolkit and GPU driver have been installed.

        -
        ./deviceQueryDrv Starting...
        - 
        -CUDA Device Query (Driver API) statically linked version 
        -Detected 1 CUDA Capable device(s)
        - 
        -Device 0: "Tesla P100-PCIE-16GB"
        -  CUDA Driver Version:                           9.0
        -  CUDA Capability Major/Minor version number:    6.0
        -  Total amount of global memory:                 16276 MBytes (17066885120 bytes)
        -  (56) Multiprocessors, ( 64) CUDA Cores/MP:     3584 CUDA Cores
        -  GPU Max Clock rate:                            1329 MHz (1.33 GHz)
        -  Memory Clock rate:                             715 Mhz
        -  Memory Bus Width:                              4096-bit
        -  L2 Cache Size:                                 4194304 bytes
        -  Max Texture Dimension Sizes                    1D=(131072) 2D=(131072, 65536) 3D=(16384, 16384, 16384)
        -  Maximum Layered 1D Texture Size, (num) layers  1D=(32768), 2048 layers
        -  Maximum Layered 2D Texture Size, (num) layers  2D=(32768, 32768), 2048 layers
        -  Total amount of constant memory:               65536 bytes
        -  Total amount of shared memory per block:       49152 bytes
        -  Total number of registers available per block: 65536
        -  Warp size:                                     32
        -  Maximum number of threads per multiprocessor:  2048
        -  Maximum number of threads per block:           1024
        -  Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
        -  Max dimension size of a grid size (x,y,z):    (2147483647, 65535, 65535)
        -  Texture alignment:                             512 bytes
        -  Maximum memory pitch:                          2147483647 bytes
        -  Concurrent copy and kernel execution:          Yes with 2 copy engine(s)
        -  Run time limit on kernels:                     No
        -  Integrated GPU sharing Host Memory:            No
        -  Support host page-locked memory mapping:       Yes
        -  Concurrent kernel execution:                   Yes
        -  Alignment requirement for Surfaces:            Yes
        -  Device has ECC support:                        Enabled
        -  Device supports Unified Addressing (UVA):      Yes
        -  Supports Cooperative Kernel Launch:            Yes
        -  Supports MultiDevice Co-op Kernel Launch:      Yes
        -  Device PCI Domain ID / Bus ID / location ID:   0 / 0 / 6
        -  Compute Mode:
        -     < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >
        -Result = PASS
        -
      -
      -

    -
    -
    -
    - -
    - - - \ No newline at end of file diff --git a/docs/ims/umn/en-us_topic_0096558549.html b/docs/ims/umn/en-us_topic_0096558549.html index 7e7742d1..17989c56 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 lazy loading, 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 a79c6367..b47a267a 100644 --- a/docs/ims/umn/en-us_topic_0102644450.html +++ b/docs/ims/umn/en-us_topic_0102644450.html @@ -12,8 +12,8 @@

    Procedure

    1. Access the IMS console.

      1. Log in to the management console.
      2. Under Computing, 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 Create Image for Type and then select Data disk image for Image 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.
      +

    3. Create a data disk image.

      1. Click Create Image in the upper right corner.
      2. In the Image Type and Source area, select Create Image for Type and then select Data disk image for Image 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:

    diff --git a/docs/ims/umn/en-us_topic_0106444267.html b/docs/ims/umn/en-us_topic_0106444267.html index ab3933ed..5b785bb7 100644 --- a/docs/ims/umn/en-us_topic_0106444267.html +++ b/docs/ims/umn/en-us_topic_0106444267.html @@ -1,8 +1,8 @@

    How Do I Create a Full-ECS Image Using an ECS That Has a Spanned Volume?

    -

    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 to create new ECSs, data may be lost.

    -

    If an ECS has a spanned volume, back up data in the spanned volume and then delete this volume from the ECS. Use the ECS to create a full-ECS image. Use the full-ECS image to create an ECS. Then, use the backup to create a spanned volume for the new ECS if necessary.

    +

    You are not advised to use a Windows ECS that has a spanned volume to create a full-ECS image. If you create such an image and then use it to create new ECSs, data may be lost.

    +

    If an ECS has a spanned volume, back up data in the spanned volume and then delete the volume. Use the ECS to create a full-ECS image. You can then use the full-ECS image to create an ECS and use the backup to create a spanned volume for the new ECS if necessary.

    If a Linux ECS has a volume group or a logical volume consisting of multiple physical volumes, to ensure you do not lose any data, back up data in the volume group or logical volume and delete the volume group or logical volume before using this ECS to create a full-ECS image.

    diff --git a/docs/ims/umn/en-us_topic_0107462581.html b/docs/ims/umn/en-us_topic_0107462581.html index 54fb6815..06f1f2bb 100644 --- a/docs/ims/umn/en-us_topic_0107462581.html +++ b/docs/ims/umn/en-us_topic_0107462581.html @@ -75,13 +75,13 @@
    -
    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 42e3ee15..f89946e2 100644 --- a/docs/ims/umn/en-us_topic_0107462582.html +++ b/docs/ims/umn/en-us_topic_0107462582.html @@ -1,16 +1,20 @@

    Viewing Traces

    -

    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.

    +

    Scenarios

    After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records generated in the last seven days.

    +

    This section describes how to query and export operation records of the last seven days on the CTS console.

    +
    -

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

      Viewing Real-Time Traces in the Trace List

      1. Log in to the management console.
      2. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
      3. Choose Trace List in the navigation pane on the left.
      4. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available:
        Figure 1 Filters
        +
        • Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
          • If you select Resource ID for Search By, specify a resource ID.
          • If you select Trace name for Search By, specify a trace name.
          • If you select Resource name for Search By, specify a resource name.
          +
        • Operator: Select a user.
        • Trace Status: Select All trace statuses, Normal, Warning, or Incident.
        • Time range: You can query traces generated during any time range in the last seven days.
        • Click Export to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
        -
      5. Locate the target trace and click to expand the trace details.
      6. Click View Trace in the upper right corner of the trace details area.
      +
    4. Click Query.
    5. On the Trace List page, you can also export and refresh the trace list.
      • Click Export to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
      • Click to view the latest information about traces.
      +
    6. Click on the left of a trace to expand its details.

      +

      +

      +
    7. Click View Trace in the Operation column. The trace details are displayed.

      +
    8. For details about key fields in the trace structure, see section "Trace References" > "Trace Structure" and section "Trace References" > "Example Traces" in the CTS User Guide.
    @@ -19,3 +23,10 @@
    + + \ No newline at end of file diff --git a/docs/ims/umn/en-us_topic_0113403127.html b/docs/ims/umn/en-us_topic_0113403127.html index 7525d98d..4a384aeb 100644 --- a/docs/ims/umn/en-us_topic_0113403127.html +++ b/docs/ims/umn/en-us_topic_0113403127.html @@ -1,11 +1,11 @@ -

    What Do I Do If an ECS Created from a Windows Image Failed to Start When I Have Enabled Automatic Configuration During Image Registration?

    -

    Symptom

    This issue is probably caused by the failure of offline VirtIO driver injection.

    +

    What Do I Do If I Enabled Automatic Configuration During Image Registration for an ECS Created from a Windows Image and Now It Won't Start?

    +

    Cause

    This may be caused by an issue with offline VirtIO driver injection.

    -

    Solution

    When you inject VirtIO drivers for a Windows ECS offline, there are some restrictions:

    -
    • If the boot mode in the image file is UEFI, the VirtIO drivers cannot be injected offline.
    • It is recommended that you disable Group Policy Object (GPO). Some policies may cause the failure of VirtIO driver injection offline.
    • It is recommended that you stop antivirus software. Otherwise, the VirtIO drivers may fail to be injected offline.
    -

    To update VirtIO drivers, you must install UVP VMTools. For how to install UVP VMTools, see Optimizing a Windows Private Image.

    +

    Solution

    When you inject VirtIO drivers into the image for a Windows ECS, note that:

    +
    • If the boot mode in the image file is UEFI, the VirtIO drivers cannot be injected offline.
    • Disable Group Policy Object (GPO) because some policies may cause offline VirtIO driver injection to fail.
    • Stop any installed antivirus software. They may cause offline VirtIO driver injection to fail.
    +

    To install VirtIO drivers, see Optimizing a Windows Private Image.

    diff --git a/docs/ims/umn/en-us_topic_0113992021.html b/docs/ims/umn/en-us_topic_0113992021.html index 4d04f74d..053bb550 100644 --- a/docs/ims/umn/en-us_topic_0113992021.html +++ b/docs/ims/umn/en-us_topic_0113992021.html @@ -1,7 +1,7 @@ -

    What Do I Do If Injecting the Key or Password Using Cloud-Init Failed After NetworkManager Is Installed?

    -

    Symptom

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

    +

    What Do I Do If Installed NetworkManager and Now I Can't Inject the Key or Password Using Cloud-Init?

    +

    Cause

    One likely possibility 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-Init 0.7.9.

    Solution

    Uninstall the current Cloud-Init and install Cloud-Init 0.7.6 or an earlier version.

    For details about how to install Cloud-Init, see Installing Cloud-Init.

    diff --git a/docs/ims/umn/en-us_topic_0116125142.html b/docs/ims/umn/en-us_topic_0116125142.html index f153c305..32cbda29 100644 --- a/docs/ims/umn/en-us_topic_0116125142.html +++ b/docs/ims/umn/en-us_topic_0116125142.html @@ -43,10 +43,10 @@

    Procedure

    1. Access the IMS console.

      1. Log in to the management console.
      2. Under Computing, 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 Create Image for Type and then select Full-ECS image for Image 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 Create Image for Type and then select Full-ECS image for Image 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 settings and click Submit.
        +
      5. In the Image Information area, configure basic image details, such as the image name and description.
      6. Click Create Now.
      7. 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
      diff --git a/docs/ims/umn/en-us_topic_0117262219.html b/docs/ims/umn/en-us_topic_0117262219.html index c03475dc..eb50e416 100644 --- a/docs/ims/umn/en-us_topic_0117262219.html +++ b/docs/ims/umn/en-us_topic_0117262219.html @@ -77,7 +77,7 @@ Command syntax: compare [-f fmt] [-F fmt] [-T src_cach]
    4. 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 part 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 part 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
        diff --git a/docs/ims/umn/en-us_topic_0118990097.html b/docs/ims/umn/en-us_topic_0118990097.html
        index ef9d9873..11101dab 100644
        --- a/docs/ims/umn/en-us_topic_0118990097.html
        +++ b/docs/ims/umn/en-us_topic_0118990097.html
        @@ -1,24 +1,24 @@
         
         
         

        How Do I Import an OVF or OVA File to the Cloud Platform?

        -

        Scenarios

        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 that contains the files required for defining and deploying VMs. An OVF folder always includes .ovf, .mf, and .vmdk files.

        -
        • An .ovf file is an XML descriptor that defines metadata of a VM, such as the name and hardware requirements, and contains reference information about other files in the OVF folder.
        • An .mf file contains the SHA hash codes of all the files in the folder and is used to prevent the image file from being tampered with.
        • A .vmdk file is a virtual disk file that is used to create a disk image. An OVF folder may contain multiple .vmdk files.
        +

        Scenarios

        Open Virtualization Appliance (OVA) is a single file archive (with the .ova extension) of all of the files comprising an Open Virtualization Format (OVF) package. OVF is a package of the files required for defining and deploying VMs. An OVF package generally includes .ovf, .mf, and .vmdk files.

        +
        • An .ovf file is an XML descriptor that defines the metadata of a VM, such as the name and hardware requirements, and contains information about other files in the OVF package.
        • An .mf file contains the SHA hash codes of all the files in the package and is used to prevent the image file from being tampered with.
        • A .vmdk file is a virtual disk file that is used to create a disk image. An OVF package may contain multiple .vmdk files.

        This section describes how to import OVF and OVA files to the cloud platform.

        -

        Procedure

        Manually extract VMDK files from an OVF or OVA template and upload them to an OBS bucket. Then, you can select one from the bucket when you use an external file to create a system or data disk image.

        +

        Procedure

        Manually extract VMDK files from an OVF or OVA template and upload them to an OBS bucket. Then, you can select one of them from the bucket when you use an external file to create a system or data disk image.

        The following assumes that the OVF or OVA template contains only one VMDK file. If there are multiple VMDK files (for example, there are three VMDK files, one used as a system disk image file and the others as data disk image files), upload them to an OBS bucket and register them as a system disk image and data disk images, respectively.

        -
        • The source VM runs the Windows OS.
          • If you choose to export an OVF template named MyVm and save it to the OvfLib folder in drive C, the following files will be generated in the folder (the VMDK file can be uploaded to the cloud platform):
            ├C
            +
            • The source VM runs Windows.
              • If you choose to export an OVF template named MyVm and save it to the OvfLib folder in drive C, the following files will be generated in the folder (the VMDK file can be uploaded to the cloud platform):
                ├C
                 │  ├OvfLib
                 │       ├MyVm
                 │          ├MyVm.ovf
                 │       ├MyVm.mf
                 │       ├MyVm-disk1.vmdk
                -
              • If you choose to export an OVA template and name it MyVm, the C:\MyVm.ova file will be generated. The VMDK file extracted from MyVm.ova can be uploaded to the cloud platform.

                You can import an image file in the VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to create a private image.

                +
              • If you choose to export an OVA template and name it MyVm, the C:\MyVm.ova file will be generated. The VMDK file extracted from MyVm.ova can be uploaded to the cloud platform.

                You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to create a private image.

              For details, see Creating a Windows System Disk Image from an External Image File or Creating a Data Disk Image from an External Image File.

              -
            • The source VM runs the Linux OS.
              • If you choose to export an OVF template, upload the VMDK file generated in the folder to the cloud platform.
              • If you choose to export an OVA template and name it MyVm, perform the following operations:
                1. Run the following command to view the OVA file:

                  file MyVm.ova

                  +
                2. The source VM runs Linux.
                  • If you choose to export an OVF template, upload the VMDK file generated in the folder to the cloud platform.
                  • If you choose to export an OVA template and name it MyVm, perform the following operations:
                    1. Run the following command to check the OVA file:

                      file MyVm.ova

                      The command output is as follows:

                      MyVm.ova: POSIX tar archive (GNU)

                      MyVm.ova contains the following two files:

                      @@ -29,7 +29,7 @@ MyVm.vmdk

            The extracted folder contains the following files:

            MyVm.ovf
             MyVm.vmdk
            -

            The image file in the VMDK format can be uploaded to the cloud platform.

            +

            The .vmdk image file can be uploaded to the cloud platform.

            You can import an image file in the VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to create a private image.

      @@ -40,7 +40,7 @@ MyVm.vmdk
    diff --git a/docs/ims/umn/en-us_topic_0122876047.html b/docs/ims/umn/en-us_topic_0122876047.html index b686dec6..af485055 100644 --- a/docs/ims/umn/en-us_topic_0122876047.html +++ b/docs/ims/umn/en-us_topic_0122876047.html @@ -3,7 +3,7 @@

    Configuring Cloud-Init

    Scenarios

    You need to configure Cloud-Init after it is installed.

    -

    Prerequisites

    • Cloud-Init has been installed.
    • 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.
    +

    Prerequisites

    • Cloud-Init has been installed.
    • An EIP has been bound to the ECS.
    • You have logged in to the ECS.
    • The ECS obtains its IP address using DHCP.

    Procedure

    The following operations are required:

    1. Configure Cloud-Init.

      For details, see Configure Cloud-Init.

      diff --git a/docs/ims/umn/en-us_topic_0125075472.html b/docs/ims/umn/en-us_topic_0125075472.html index 5b29b13b..56808b78 100644 --- a/docs/ims/umn/en-us_topic_0125075472.html +++ b/docs/ims/umn/en-us_topic_0125075472.html @@ -1,7 +1,7 @@

      Clearing System Logs

      -

      After installing the PV driver and UVP VMTools, perform the following operations to clear system logs:

      +

      After installing PV and VirtIO drivers, perform the following operations to clear system logs:

      1. For Windows Server 2008 and Windows Server 2012, right-click Computer and select Manage.
      2. In the displayed dialog box, choose System Tools > Event Viewer > Windows Logs and delete logs of five items.
      3. Stop the ECS.
      diff --git a/docs/ims/umn/en-us_topic_0129883696.html b/docs/ims/umn/en-us_topic_0129883696.html index fd101d8b..cacaf82b 100644 --- a/docs/ims/umn/en-us_topic_0129883696.html +++ b/docs/ims/umn/en-us_topic_0129883696.html @@ -1,6 +1,6 @@ -

      How Do I Configure an ECS to Dynamically Acquire IPv6 Addresses?

      +

      How Do I Configure an ECS to Use DHCPv6?

      Scenarios

      IPv6 addresses are used to deal with IPv4 address exhaustion. If an ECS uses an IPv4 address, the ECS can run in dual-stack mode after IPv6 is enabled for it. Then, the ECS will have two IP addresses to access the intranet and Internet: an IPv4 address and an IPv6 address.

      In some cases, an ECS cannot dynamically acquire an IPv6 address even if it meets all the requirements in Constraints. You need to configure the ECS to dynamically acquire IPv6 addresses. For public images:

      • By default, dynamic IPv6 address assignment is enabled for Windows public images. You do not need to configure it. The operations in Windows Server 2012 are for your reference only.
      • Before enabling dynamic IPv6 address assignment for a Linux public image, check whether IPv6 has been enabled and then whether dynamic IPv6 address assignment has been enabled. Currently, IPv6 is enabled for all Linux public images.
      @@ -109,7 +109,7 @@

    2. Enable IPv6 for the ECS.

      1. Run the following command to check whether IPv6 is enabled for the kernel:

        sysctl -a | grep ipv6

        • If a command output is displayed, IPv6 is enabled.
        • If no information is displayed, IPv6 is disabled. Go to 2.b to load the IPv6 module.
      2. Run the following command to load the IPv6 module:

        modprobe ipv6

        -
      3. Add the following content to the /etc/sysctl.conf file:

        net.ipv6.conf.all.disable_ipv6=0

        +
      4. Add the following content to the /etc/sysctl.conf file:

        net.ipv6.conf.all.disable_ipv6=0

      5. Save the configuration and exit. Then, run the following command to load the configuration:

        sysctl -p

    3. Enable dynamic IPv6 address assignment for the ECS.

      • Ubuntu 18.04/20.04
        1. Run the following command to access /etc/netplan/:

          cd /etc/netplan

          @@ -195,15 +195,15 @@ DHCPV6C=yes
          • CentOS 6.x:
            1. Run the following command to edit the dhclient.conf file:

              vi /etc/dhcp/dhclient.conf

            2. Press i to enter editing mode and add the timeout attribute to the file.
              timeout  30;
            3. Enter :wq to save the settings and exit.
            -
          • Debian 7.5:
            1. Run the following command to edit the networking file:

              vi /etc/init.d/networking

              +
            2. Debian 7.5:
              1. Run the following command to edit the networking file:

                vi /etc/init.d/networking

              1. Press i to enter editing mode and add the timeout attribute.
                Figure 20 Modification 1
                Figure 21 Modification 2
              -
            3. Debian 8.2.0/8.8.0
              1. Run the following command to edit the network-pre.conf file:

                vi /lib/systemd/system/networking.service.d/network-pre.conf

                +
              2. Debian 8.2.0/8.8.0
                1. Run the following command to edit the network-pre.conf file:

                  vi /lib/systemd/system/networking.service.d/network-pre.conf

                2. Press i to enter editing mode and add the timeout attribute to the file.
                  [Service]
                   TimeoutStartSec=30
                -
              3. Debian 9.0
                1. Run the following command to edit the networking.service file:

                  vi /etc/system/system/network-online.target.wants/networking.service

                  +
                2. Debian 9.0
                  1. Run the following command to edit the networking.service file:

                    vi /etc/system/system/network-online.target.wants/networking.service

                  2. Press i to enter editing mode and change TimeoutStartSec=5min to TimeoutStartSec=30.
    diff --git a/docs/ims/umn/en-us_topic_0130878289.html b/docs/ims/umn/en-us_topic_0130878289.html index 9df6e84b..e7e6036b 100644 --- a/docs/ims/umn/en-us_topic_0130878289.html +++ b/docs/ims/umn/en-us_topic_0130878289.html @@ -30,7 +30,7 @@ -
    diff --git a/docs/ims/umn/en-us_topic_0130878748.html b/docs/ims/umn/en-us_topic_0130878748.html index 1ed1e732..cdc9333f 100644 --- a/docs/ims/umn/en-us_topic_0130878748.html +++ b/docs/ims/umn/en-us_topic_0130878748.html @@ -8,7 +8,7 @@ - diff --git a/docs/ims/umn/en-us_topic_0132216287.html b/docs/ims/umn/en-us_topic_0132216287.html index 5bc0eea6..996a0c51 100644 --- a/docs/ims/umn/en-us_topic_0132216287.html +++ b/docs/ims/umn/en-us_topic_0132216287.html @@ -5,16 +5,16 @@

    For details about how to install Cloud-Init, see Installing Cloud-Init.

    For details about how to configure Cloud-Init, see Configuring Cloud-Init.

    The following describes common problems you may encounter when installing Cloud-Init and their solutions.

    -

    Ubuntu 16.04/CentOS 7: Failed to Set Cloud-Init Automatic Start

    • Symptom:

      After Cloud-Init is installed, run the following command to set Cloud-Init automatic start:

      +

      Ubuntu 16.04/CentOS 7: Failed to Set Cloud-Init Automatic Start

      • Symptom

        After Cloud-Init is installed, you run the following command to configure Cloud-Init automatic start:

        systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

        Information similar to the following is displayed:

        Figure 1 Failed to enable Cloud-Init to start automatically
        -
      • Solution:
        1. Run the following command to roll back the configuration:

          systemctl unmask cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

          -
        2. Run the following command to set automatic start again:

          systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

          +
        3. Solution
          1. Run the following command to roll back the configuration:

            systemctl unmask cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

            +
          2. Run the following command to configure automatic start again:

            systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

          3. Run the following command to check the Cloud-Init status:

            systemctl status cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

            As shown in the following figures, failed is displayed and all services are in the inactive state.

            -
            Figure 2 Checking Cloud-Init status
            -
            Figure 3 Checking Cloud-Init status
            +
            Figure 2 Checking Cloud-Init status (1)
            +
            Figure 3 Checking Cloud-Init status (2)

            This is because the address that the system uses to access Cloud-Init is redirected to /usr/bin/, but the actual installation path is /usr/local/bin.

          4. Run the following command to copy Cloud-Init to the usr/bin directory:

            cp /usr/local/cloud-init /usr/bin/

          5. Run the following command to restart Cloud-Init:

            systemctl restart cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

            @@ -23,8 +23,8 @@
      -

      Ubuntu 14.04: chkconfig and systemctl Not Installed

      • Symptom:

        chkconfig is not installed.

        -
      • Solution:

        Run the following commands to install chkconfig:

        +

        Ubuntu 14.04: chkconfig and systemctl Not Installed

        • Symptom

          chkconfig is not installed.

          +
        • Solution

          Run the following commands to install chkconfig:

          apt-get update

          apt-get install sysv-rc-conf

          cp /usr/sbin/sysv-rc-conf /usr/sbin/chkconfig

          @@ -32,24 +32,24 @@

          cloud-init -v

          Information similar to the following is displayed:

          -bash:/usr/bin/cloud-init:not found this command
          -

          Solution: Run the following command to copy Cloud-Init to the usr/bin directory:

          +

          Run the following command to copy Cloud-Init to the usr/bin directory:

          cp /usr/local/bin/cloud-init /usr/bin/

        -

        Debian 9.5: Failed to Query the Cloud-Init Version and Set Automatic Start

        1. Run the following command to query the Cloud-Init version:

          cloud-init -v

          +

          Debian 9.5: Failed to Query the Cloud-Init Version and Configure Automatic Start

          1. Run the following command to query the Cloud-Init version:

            cloud-init -v

            Information similar to the following is displayed:

            -bash:/usr/bin/cloud-init:not found this command
            -

            Solution: Run the cp /usr/local/bin/cloud-init /usr/bin/ command to copy Cloud-Init to the usr/bin directory.

            +

            Run the cp /usr/local/bin/cloud-init /usr/bin/ command to copy Cloud-Init to the usr/bin directory.

          2. Run the cloud-init init --local command.

            Information similar to the following is displayed:

            -
            Figure 5 Information returned when Cloud-Init automatic start successfully set
            -

            Cause analysis: The compilation fails because GCC is not installed.

            -

            Solution:

            +
            Figure 5 Information returned when Cloud-Init automatic start successfully set
            +

            The compilation fails because GCC is not installed.

            +

            To solve this issue:

            Run the following command to install GCC. Then, install Cloud-Init again.

            yum -y install gcc

            -
          3. After Cloud-Init is installed, run the following command to set Cloud-Init automatic start:

            systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

            +
          4. After Cloud-Init is installed, run the following command to configure Cloud-Init automatic start:

            systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

            Information similar to the following is displayed.

            -
            Figure 6 Prompt indicating the failure to set Cloud-Init automatic start
            -

            Solution:

            +
            Figure 6 Prompt indicating the failure to configure Cloud-Init automatic start
            +

            To solve this issue:

            1. Run the following command to roll back the configuration:

              systemctl unmask cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

            2. Run the following command to set automatic start again:

              systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

            3. Run the following command to restart Cloud-Init:

              systemctl restart cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service

              @@ -58,7 +58,7 @@
          -

          CentOS 7/Fedora 28: Required C Compiler Not Installed

          • Symptom

            After Cloud-Init is successfully installed, run the following command:

            +

            CentOS 7/Fedora 28: Required C Compiler Not Installed

            • Symptom

              After Cloud-Init is successfully installed, you run the following command:

              cloud-init init --local

              The following information is displayed:

              /usr/lib/python2.5/site-packages/Cheetah/Compiler.py:1532: UserWarning: 
              @@ -70,9 +70,9 @@ You don't have the C version of NameMapper installed! I'm disabling Cheetah's us
               

              Reinstall Cloud-Init.

            -

            CentOS 7/Fedora: Failed to Use the New Password to Log In to an ECS Created from an Image

            • Symptom

              After Cloud-Init is successfully installed on an ECS, an image is created from the ECS. You cannot use a new password to log in to the ECSs created from this image. When you log in to the ECSs using the old password, you find that NICs of these ECSs are not started.

              +

              CentOS 7/Fedora: Failed to Use the New Password to Log In to an ECS Created from an Image

              • Symptom

                You cannot use a new password to log in to an ECS created from an image with Cloud-Init installed. After logging in to the ECS using the old password, you find that NICs of the ECS are not started.

                Figure 8 NIC not started
                -
              • Solution:

                Log in to the ECS used to create the image, open the DHCP configuration file /etc/sysconfig/network-scripts/ifcfg-ethX, and comment out HWADDR.

                +
              • Solution

                Log in to the ECS used to create that image, open the DHCP configuration file /etc/sysconfig/network-scripts/ifcfg-ethX, and comment out HWADDR.

            diff --git a/docs/ims/umn/en-us_topic_0133773658.html b/docs/ims/umn/en-us_topic_0133773658.html index 30f4f1d1..f8be2bb9 100644 --- a/docs/ims/umn/en-us_topic_0133773658.html +++ b/docs/ims/umn/en-us_topic_0133773658.html @@ -1,7 +1,10 @@

            Overview

            -

            If an image file is larger than 128 GB, you can import it using fast import. Only the RAW and ZVHD2 formats support fast import. The image file to be imported cannot exceed 1 TB.

            +

            If an image file is larger than 128 GB, you can import it using fast import.

            +

            Constraints

            • The image file must be in RAW or ZVHD2 format.
            +
            +
            • The image file size cannot exceed 1 TB.

            Methods

            You can import an image file in any of the following methods depending on the file format:
            • ZVHD2
              1. Optimize the image file.
              2. Upload the image file to an OBS bucket.
              3. Register the image file on the cloud platform.
            • RAW
              1. Optimize the image file.
              2. Generate a bitmap file for the image file.
              3. Upload the image file and bitmap file to an OBS bucket.
              4. Register the image file on the cloud platform.
            • Others
              • If the file format is converted to ZVHD2:
                1. Optimize the image file.
                2. Convert the image file format to ZVHD2.
                3. Upload the image file to an OBS bucket.
                4. Register the image file on the cloud platform.
                @@ -9,27 +12,27 @@
            -
            • 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.
            +
            • Fast import is used to quickly import large files. It depends on lazy loading which defers loading of file data until the data is needed. This reduces the initial loading time. However, RAW files do not support lazy loading. 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.

            +

            Import Process

            Assume that you need to convert the file format to ZVHD2 or RAW.

            You can use qemu-img-hw or the open-source tool qemu-img to convert the image format. qemu-img-hw can only be used in Linux.

            The tool package contains qemu-img-hw (for converting image formats) and CreateMF.jar (for generating bitmap files).

            • Linux

              You are advised to use an EulerOS ECS to convert the file format.

              -
              Figure 1 Import process
              -

              For details, see Quickly Importing an Image File (Linux).

              +
              Figure 1 Import process (Linux)
              +

              For details, see Fast Import in Linux.

            • Windows

              You are advised to use a local PC running Windows to convert the file format.

              qemu-img cannot convert image files to the ZVHD2 format. You need to convert an image file to the RAW format and then use CreateMF.jar to generate a bitmap file.

              Figure 2 Import process (Windows)
              -

              For details, see Quickly Importing an Image File (Windows).

              +

              For details, see Fast Import in Windows.

            diff --git a/docs/ims/umn/en-us_topic_0133773660.html b/docs/ims/umn/en-us_topic_0133773660.html index 15be02e8..270f45d3 100644 --- a/docs/ims/umn/en-us_topic_0133773660.html +++ b/docs/ims/umn/en-us_topic_0133773660.html @@ -1,10 +1,10 @@ -

            Quickly Importing an Image File (Linux)

            -

            Scenarios

            This section describes how to convert the format of an image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an EulerOS ECS for converting image file formats and generating bitmap files.

            +

            Fast Import in Linux

            +

            Scenarios

            This section describes how to convert the format of a large image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an EulerOS ECS for converting image file formats and generating bitmap files.

            In Linux, you are advised to use qemu-img-hw to convert image formats.

            -

            Prerequisites

            • The image file has been optimized. For details, see Optimization Process (Windows) or Optimization Process (Linux). Ensure that the image file meets the requirements in Table 1 (Windows) or Table 1 (Linux).

              Select the reference content based on the OS type in the image file.

              +

              Prerequisites

              • The image file has been optimized. For details, see Optimization Process (Windows) or Optimization Process (Linux). Ensure that the image file meets the requirements in Table 2 (Windows) or Table 2 (Linux).

                Select the reference content based on the OS type in the image file.

              • You have created an ECS running EulerOS on the management console and bound an EIP to the ECS.
              • An OBS bucket has been created on the management console.
              @@ -81,7 +81,7 @@ 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 Computing, 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 Import Image for Type and then select System disk image or Data disk image for Image Type.
              4. 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. In the upper right corner, click Create Image.
              7. In the Image Type and Source area, select Import Image for Type and then select System disk image or Data disk image for Image Type.
              8. 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.
              9. Select Enable Fast Create, and select the sentence following Image File Preparation.
                Figure 1 Fast import of an image file
              10. 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 capacity must be greater than that specified in the image file.

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

                  qemu-img-hw info test.zvhd2

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

              Method 2: Register a private image using an API.

              -

              You can use the POST /v2/cloudimages/quickimport/action API to quickly import an image file.

              +

              The API is POST /v2/cloudimages/quickimport/action.

              For details about how to call this API, see "Importing an Image File Quickly" in Image Management Service API Reference.

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

  • @@ -125,7 +125,7 @@ Save settings? y (Specifies whethe
    diff --git a/docs/ims/umn/en-us_topic_0133773782.html b/docs/ims/umn/en-us_topic_0133773782.html index a6d83b81..41bf5723 100644 --- a/docs/ims/umn/en-us_topic_0133773782.html +++ b/docs/ims/umn/en-us_topic_0133773782.html @@ -8,8 +8,6 @@ - - diff --git a/docs/ims/umn/en-us_topic_0138479468.html b/docs/ims/umn/en-us_topic_0138479468.html index 48c6c9f9..2696793a 100644 --- a/docs/ims/umn/en-us_topic_0138479468.html +++ b/docs/ims/umn/en-us_topic_0138479468.html @@ -8,7 +8,7 @@ - diff --git a/docs/ims/umn/en-us_topic_0146328750.html b/docs/ims/umn/en-us_topic_0146328750.html index 4af15dfc..ebea0426 100644 --- a/docs/ims/umn/en-us_topic_0146328750.html +++ b/docs/ims/umn/en-us_topic_0146328750.html @@ -6,13 +6,13 @@
    - - @@ -52,7 +52,7 @@ @@ -78,7 +78,7 @@ - @@ -94,12 +94,12 @@ - - - @@ -121,7 +121,7 @@ - diff --git a/docs/ims/umn/en-us_topic_0192505040.html b/docs/ims/umn/en-us_topic_0192505040.html index c4f73fc8..6646c56c 100644 --- a/docs/ims/umn/en-us_topic_0192505040.html +++ b/docs/ims/umn/en-us_topic_0192505040.html @@ -76,7 +76,7 @@ @@ -138,7 +138,7 @@ - - - diff --git a/docs/ims/umn/en-us_topic_0199396601.html b/docs/ims/umn/en-us_topic_0199396601.html index 6438182f..0c8fbdf3 100644 --- a/docs/ims/umn/en-us_topic_0199396601.html +++ b/docs/ims/umn/en-us_topic_0199396601.html @@ -1,12 +1,12 @@ -

    What Do I Do If the Export Option Is Unavailable for My Image?

    -

    Some images cannot be exported. Therefore, the Export option is not provided for them in the Operation column. The following images cannot be exported:

    +

    Why the Export Option Is Unavailable for My Image?

    +

    Some images cannot be exported. So, the Export option is not provided for them in the Operation column. The following images cannot be exported:

    • Public images
    • Full-ECS images
    • Private images created from a Windows or SUSE public image
    diff --git a/docs/ims/umn/en-us_topic_0199396602.html b/docs/ims/umn/en-us_topic_0199396602.html index 4c519fbe..3ff0479e 100644 --- a/docs/ims/umn/en-us_topic_0199396602.html +++ b/docs/ims/umn/en-us_topic_0199396602.html @@ -2,8 +2,8 @@

    How Can I Use a Backup to Create an EVS Disk or ECS?

    You can use CSBS backups to create ECSs and use VBS backups to create EVS disks.

    -
    • CSBS backups cannot be directly used to create ECSs. You need to use a backup to create a private image and then use the private image to create ECSs.

      For details about how to create a private image from a CSBS backup, see Creating a Full-ECS Image from a CSBS Backup. For details about how to create ECSs from a private image, see Creating an ECS from an Image.

      -
    • VBS backups can be directly used to create EVS disks. For details, see "Using a Backup to Create a Disk" in Cloud Backup and Recovery User Guide.
    +
    • CSBS backups cannot be directly used to create ECSs. You need to use a backup to create a private image and then use the private image to create ECSs.

      For details about how to create a private image from a CSBS backup, see Creating a Full-ECS Image from a CSBS Backup. For details about how to use a private image to create ECSs, see Creating an ECS from an Image.

      +
    • VBS backups can be directly used to create EVS disks. For details, see "Using a Backup to Create a Disk" in Cloud Backup and Recovery User Guide.
    - -
    Table 2 Relationship between IMS operations and native OpenStack APIs

    Operation

    Trace Name

    +

    Trace Name

    Service Type

    Resource Type

    +

    Resource Type

    OpenStack Component

    You can import a system disk from your local PC or other cloud platforms, and use the imported image to create new cloud servers or reinstall or change the OSs of existing cloud servers.

    +

    Creating a system disk image from an ISO file

    In contrast with other image formats, an ISO file can be used only after it is decompressed using a tool, such as UltraISO or VirtualBox. For details about the image creation process, see the Related Operations column in the table.

    +

    In contrast with other image formats, an ISO file can be used only after it is decompressed using a tool, such as UltraISO or VirtualBox. For details about the image creation process, see the Helpful Link column in the table.

    Creating a full-ECS image from an ECS, a CSBS backup, or a CBR backup

    You can use an ECS with data disks to create a full-ECS image, complete with an OS, various applications, and your service data. The full-ECS image then can be used to quickly provision identical ECSs for data migration.

    -

    A full-ECS image can be created by using an ECS, a CSBS backup, or a CBR backup.

    +

    A full-ECS image can be created from an ECS, a CSBS backup, or a CBR backup.

    Modifying an image

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

    +

    You can modify the following attributes of an image: name, description, minimum memory, maximum memory, and advanced functions such as NIC multi-queue and SR-IOV driver.

    Modifying an Image

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

    +

    Encrypting images

    You can create encrypted images to improve data security. The encryption mode is KMS envelope encryption.

    +

    You can create encrypted images to improve data security. KMS envelope encryption is used.

    Encrypted images can be created from external image files or encrypted ECSs.

    @@ -107,7 +107,7 @@

    Replicating images

    By replicating images, you can convert encrypted and unencrypted images into each other or enable some advanced features, for example, quick instance provisioning.

    +

    By replicating images, you can convert encrypted and unencrypted images into each other or enable some advanced features, for example, fast instance provisioning.

    Replicating Images

    Exporting image list

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

    +

    You can export the public or private image list in a given region as a CSV file for local maintenance and query.

    Exporting Image List

    Image size

    The image size cannot exceed 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 through 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 through fast import.

    Private image status

    Normal

    +

    Normal

    Replicating images within a region

    @@ -196,7 +196,7 @@

    Creating an encrypted image from an encrypted ECS or an external image file

    • An encrypted image cannot be shared with other tenants.
    • The key used for encrypting an image cannot be changed.
    +
    • An encrypted image cannot be shared with others.
    • The key used for encrypting an image cannot be changed.

    Deleting images

    diff --git a/docs/ims/umn/en-us_topic_0193137621.html b/docs/ims/umn/en-us_topic_0193137621.html index ec57702e..8074460d 100644 --- a/docs/ims/umn/en-us_topic_0193137621.html +++ b/docs/ims/umn/en-us_topic_0193137621.html @@ -4,7 +4,7 @@

    Linux

    • High-performance server applications (for example, Web) and working with common programming languages such as PHP and Python.
    • Databases such as MySQL. (You need to install the database.)
    +
    • High-performance server applications (for example, Web) and common programming languages such as PHP and Python
    • Databases such as MySQL. (You need to install the database.)

    The system disk must be at least 1 GB, and there must be at least 512 MB of memory.

    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 import is fast because the system does not perform any operations like 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

    Quickly Importing an Image File

    +

    Fast Import of an Image File

    Export

    You can export private images to OBS buckets and download them to your local PC for further use on other cloud platforms.

    -

    Maximum file size: 128 GB (If an image file is larger than 128 GB, use fast export to export it.)

    +

    Maximum file size: 128 GB (If an image file is larger than 128 GB, use fast export.)

    You can specify the format of the exported image file. Currently, only QCOW2, VMDK, VHD, and ZVHD are supported.

    Exporting an Image

    @@ -54,7 +54,7 @@
    diff --git a/docs/ims/umn/en-us_topic_0205267846.html b/docs/ims/umn/en-us_topic_0205267846.html index 6a1955d6..75c66a3b 100644 --- a/docs/ims/umn/en-us_topic_0205267846.html +++ b/docs/ims/umn/en-us_topic_0205267846.html @@ -2,19 +2,19 @@

    Full-ECS Image FAQs

    What Is a Full-ECS Image?

    A full-ECS image contains the OS, applications, and service data of an ECS. Generally, a full-ECS image is used to migrate all data of an ECS. For example:

    -
    • Sharing an ECS with other tenants
    • Migrating data from an old ECS to a new one
    +
    • Sharing an ECS with other users
    • Migrating data from an old ECS to a new one
    -

    Why Do I Have to Select a Vault When Creating a Full-ECS Image? Do I Need to Pay for the Vault?

    When creating a full-ECS image from a CBR backup, you must select a vault. The vault is where your images and backups are stored. You need to pay for the vault.

    -

    When creating a full-ECS image from a CSBS backup, the vaults storing CSBS backups are not open to users but still need to be billed.

    -

    Therefore, no matter which backup type you select, you need to pay for the vault. Selecting a vault does not mean that you need to pay extra fees.

    +

    Why Do I Have to Select a Vault When Creating a Full-ECS Image? Do I Need to Pay for the Vault?

    When creating a full-ECS image from a CBR backup, you must select a vault. The vault is where your image and backup are stored. You need to pay for the vault.

    +

    When creating a full-ECS image from a CSBS backup, the space used to store the image and CSBS backup is not open to users but still need to be billed.

    +

    So, no matter which backup type you select, you need to pay for the storage. Selecting a vault does not mean that you need to pay extra fees.

    -

    Where Can I View the Data Disk Information of a Successfully Created Full-ECS Image?

    After a full-ECS image is created, only the system disk information (Disk Capacity) is displayed in the image list and image details. You can view the data disk information on the CSBS or CBR console, depending on where the full-ECS image is created from.

    +

    Where Can I Check the Data Disk Details of a Full-ECS Image?

    To check data disk details, you need to go to the CSBS or CBR console, depending on where the full-ECS image is created from. That is because only system disk information (Disk Capacity) is displayed in the image list and image details after a full-ECS image is created.

    The following describes how to view the data disk details in CBR:

    1. In the private image list, click the full-ECS image name.

      Image details are displayed.

      -
    2. Locate Source and click the backup ID following it.

      The CBR details page is displayed.

      +
    3. Locate Source and click the backup ID following it.

      The CBR backup details page is displayed.

    4. Click the Disk Backup tab. Details about the system disk and data disks are displayed.
    -

    What Are the Restrictions on Using a Full-ECS Image?

    • A full-ECS image cannot be exported. You are advised to create images for the system disk and data disks separately and then export the images.
    • Only the full-ECS image created from a CBR backup is shareable with other tenants.
    • A full-ECS image cannot be replicated within the same region.
    +

    What Are the Restrictions on Using a Full-ECS Image?

    • A full-ECS image cannot be exported. You are advised to create images for the system disk and data disks separately and then export the images.
    • Only the full-ECS image created from a CBR backup can be shared with other users.
    • A full-ECS image cannot be replicated within the same region.
    diff --git a/docs/ims/umn/en-us_topic_0249675952.html b/docs/ims/umn/en-us_topic_0249675952.html index 1eb9a6b0..9ea036ef 100644 --- a/docs/ims/umn/en-us_topic_0249675952.html +++ b/docs/ims/umn/en-us_topic_0249675952.html @@ -1,11 +1,13 @@

    Can I Download My Private Images to a Local PC?

    -

    Yes. You can download private images in VMDK, VHD, QCOW2, or ZVHD format as instructed in Exporting an Image.

    +

    Yes. You can download private images as instructed in Exporting an Image.

    +

    Currently, only images in VMDK, VHD, QCOW2, or ZVHD format can be exported.

    +

    The default format of a private image is ZVHD2. Images exported in different formats may vary in size.

    diff --git a/docs/ims/umn/en-us_topic_0274352601.html b/docs/ims/umn/en-us_topic_0274352601.html index f9c5001e..39f54b8a 100644 --- a/docs/ims/umn/en-us_topic_0274352601.html +++ b/docs/ims/umn/en-us_topic_0274352601.html @@ -1,14 +1,15 @@

    Why Is the Image Size in an OBS Bucket Different from That Displayed in IMS?

    -

    Symptom

    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 GB on the IMS console. After it is exported to an OBS bucket, the size is displayed as 2.91 GB.

    +

    Symptom

    When 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 GB on the IMS console, but in an OBS bucket, the size is 2.91 GB.

    -

    Cause Analysis

    The size of an image in an OBS bucket varies depending on the file's storage format in the bucket.

    +

    Cause Analysis

    The default format of a private image is ZVHD2, but it may be stored in a different format (VMDK, VHD, QCOW2, or ZVHD) in an OBS bucket after it is exported. The format conversion may lead to size changes.