88
Image Management Service User Guide Issue 13 Date 2017-08-30

User Guide · Debian 7.5 32bit Debian 8.8.0 64bit Debian 9.0.0 64bit ... GPU-optimized (g1) ECS Windows Server 2008 R2 Enterprise SP1 64bit Windows Server 2012 R2 Standard 64bit Windows

  • Upload
    others

  • View
    50

  • Download
    0

Embed Size (px)

Citation preview

  • Image Management Service

    User Guide

    Issue 13

    Date 2017-08-30

  • Contents

    1 Overview......................................................................................................................................... 11.1 Concept...........................................................................................................................................................................11.1.1 What Is Image Management Service?......................................................................................................................... 11.1.2 OSs for Public Images Supported by IMS...................................................................................................................21.1.3 Image Formats and OS Types of External Image Files............................................................................................... 41.2 Charging......................................................................................................................................................................... 71.2.1 Charging Standard....................................................................................................................................................... 71.3 IMS Access and Usage................................................................................................................................................... 71.3.1 Accessing IMS.............................................................................................................................................................71.3.2 IMS Relationships with Other Services.......................................................................................................................7

    2 Getting Started............................................................................................................................... 82.1 Introduction.................................................................................................................................................................... 82.2 Creating a Windows Private Image Using an ECS.........................................................................................................82.2.1 Overview..................................................................................................................................................................... 82.2.2 Configuring a Windows ECS...................................................................................................................................... 92.2.3 Installing Cloudbase-Init........................................................................................................................................... 122.2.4 (Optional) Optimizing a Windows Private Image..................................................................................................... 162.2.5 Creating a Windows Private Image........................................................................................................................... 162.3 Creating a Linux Private Image Using an ECS............................................................................................................ 172.3.1 Overview................................................................................................................................................................... 172.3.2 Querying and Configuring NIC Attributes................................................................................................................172.3.3 Installing Cloud-Init.................................................................................................................................................. 192.3.4 Configuring Linux VM Network Attributes (Using Cloud-Init)...............................................................................252.3.5 (Optional) Optimizing a Linux Private Image...........................................................................................................272.3.6 Querying and Detaching EVS Data Disks from the ECS..........................................................................................272.3.7 Creating a Private Linux Image.................................................................................................................................282.4 Creating a Linux Private Image Using an External Image File....................................................................................292.4.1 Overview................................................................................................................................................................... 292.4.2 Uploading an External Image File.............................................................................................................................312.4.3 Registering an External Image File as a Private Image.............................................................................................322.4.4 Creating an ECS........................................................................................................................................................ 342.4.5 Configuring a Linux ECS.......................................................................................................................................... 352.4.6 Creating a Private Image Using an ECS....................................................................................................................36

    Image Management ServiceUser Guide Contents

    Issue 13 (2017-08-30) ii

  • 2.4.7 (Optional) Cleaning Up the Environment................................................................................................................. 36

    3 Management................................................................................................................................. 373.1 Modifying Image Attributes......................................................................................................................................... 373.2 Creating an ECS Using an Image................................................................................................................................. 383.3 Deleting an Image.........................................................................................................................................................393.4 Sharing an Image.......................................................................................................................................................... 393.4.1 Overview................................................................................................................................................................... 393.4.2 Obtaining the Account Name and Project Name.......................................................................................................403.4.3 Sharing Specified Images.......................................................................................................................................... 413.4.4 Accepting or Refusing Shared Images...................................................................................................................... 413.4.5 Removing Accepted Images......................................................................................................................................433.4.6 Canceling Image Sharing...........................................................................................................................................433.4.7 Adding Tenants Who Can Use Shared Images..........................................................................................................443.4.8 Deleting Tenants Who Can Use Shared Images........................................................................................................ 443.5 Exporting an Image...................................................................................................................................................... 453.6 (Optional) Optimizing a Windows Private Image........................................................................................................ 463.6.1 Overview................................................................................................................................................................... 463.6.2 Uninstalling Tools from a Windows ECS..................................................................................................................483.6.3 Installing Tools on a Windows ECS.......................................................................................................................... 493.6.4 Installing UVP VMTools on a Windows ECS...........................................................................................................503.7 (Optional) Optimizing a Linux Private Image..............................................................................................................523.7.1 Overview................................................................................................................................................................... 523.7.2 Uninstalling Tools from a Linux ECS....................................................................................................................... 533.7.3 Changing UUIDs of fstab and grub and Installing Native Xen and KVM Drivers...................................................543.8 Encrypting an Image.....................................................................................................................................................633.8.1 Overview................................................................................................................................................................... 633.8.2 Creating an Encrypted Image.................................................................................................................................... 643.9 Replicating an Image.................................................................................................................................................... 64

    4 FAQs...............................................................................................................................................664.1 Image FAQs.................................................................................................................................................................. 664.1.1 What Are the Charging Standards of IMS?...............................................................................................................664.1.2 Will I Be Charged for Creating an Image Using an ECS?........................................................................................ 664.1.3 Is the OBS for Private Images Charged?...................................................................................................................664.1.4 How Many Private Images Can Be Created Using One Account?........................................................................... 664.1.5 Can Specifications of ECSs Created Using a Private Image Differ from Those of ECSs Used to Create the Image?............................................................................................................................................................................................ 664.1.6 How Long Does It Take to Create a Private Image Using an ECS?..........................................................................674.1.7 Should I Stop the ECS Before Creating a Private Image Using that ECS?...............................................................674.1.8 What Can I Do If I Configure an Incorrect System Disk Size During Private Image Registration Using an ImageFile?.................................................................................................................................................................................... 674.1.9 What Are the Impacts If the ECS That Has Not Been Configured Is Used to Create the Private Image?................674.1.10 Can I Use Images in Formats Other Than Those Specified in This Document?.....................................................67

    Image Management ServiceUser Guide Contents

    Issue 13 (2017-08-30) iii

  • 4.1.11 What Can I Do If the Disks of ECS Created Using a CentOS Image Cannot Be Found?...................................... 684.1.12 How Can a Refused Image Be Used?......................................................................................................................694.1.13 What Changes Will Be Made to an Image File Used for Registering a Private Image?......................................... 694.1.14 What Should I Do If No Partition Is Found During the Startup of an ECS Created Using a Private Image That IsCreated Using an External Image File?..............................................................................................................................704.1.15 What Initial Configuration Needs to Be Performed for an External Image File Used to Create a Private Image?............................................................................................................................................................................................ 734.1.16 How Can I Share an Encrypted Image or Publish It in Marketplace?.....................................................................784.1.17 How Can I Change an Unencrypted Image to an Encrypted One?......................................................................... 784.1.18 Why Does the Error Message Displayed on Task Center Indicates That the System Disk Size of the ExternalImage File Exceeds the Maximum System Disk Size When a VHD Image File Failed to Be Uploaded?........................784.2 OS FAQs.......................................................................................................................................................................794.2.1 Can I Specify the Size of the EVS System Disk When Using a Private Image to Create an ECS?..........................794.2.2 What Should I Do If the Provided OS Images Cannot Meet My Requirement?.......................................................794.2.3 What Are the Usage Requirements of Each Type of OS?......................................................................................... 794.2.4 Why Is the Sysprep Operation Required for Creating Private Images Using a Windows ECS?.............................. 794.2.5 What Impact Will Be Brought by an Inconsistency Between the Image OS I Select or Identified by the System andThat of the Actual Image During Creation of a Private Image Using an External Image File?.........................................80

    A Change History........................................................................................................................... 82

    Image Management ServiceUser Guide Contents

    Issue 13 (2017-08-30) iv

  • 1 Overview1.1 Concept

    1.1.1 What Is Image Management Service?

    Image and IMSAn image is an Elastic Cloud Server (ECS) template containing mandatory software, such asthe operating system (OS). The template may also contain application software, such asdatabase software and proprietary software. Images are classified into public images, privateimages, and shared images. The system provides public images by default, and you can createprivate images by yourself.

    Image Management Service (IMS) provides easy-to-use self-service image managementfunctions. You can apply for an ECS using a private image, public image, or shared image.You can also create a private image using an existing ECS or an external image file.

    Image Types

    Table 1-1 Image types

    Image Type Description

    Public image A widely used standard image that contains an OS and pre-installedpublic applications and is visible to all users. You can configure the OSand software in the public image as needed.

    Image Management ServiceUser Guide 1 Overview

    Issue 13 (2017-08-30) 1

    http://www.hwclouds.com/product/ims.html

  • Image Type Description

    Private image Contains an OS, pre-installed public applications, and users' privateapplications. It is visible only to the user who creates it. Using a privateimage to create an ECS can eliminate the time required for repeatedlyconfiguring the ECS. You can create private images using either of thefollowing two methods:l Using ECSsl Using external image files

    You can upload external image files and register the images on thepublic cloud platform to make them function as private images.External image files can be in VMDK, VHD, QCOW2, or ZVHDformat.

    Shared images A private image that is shared by other tenants on the public cloud systemand accepted by you as your own private image

    IMS FunctionsIMS provides the following functions:

    l Providing public images that contain mainstream OSs. For details about supported OSs,see section 1.1.2 OSs for Public Images Supported by IMS.

    l Creating private images– Creating private images using ECSs– Creating private images using external image files

    l Managing images– Modifying attributes of private images– Deleting existing private images– Sharing images– Exporting images– Encrypting images– Replicating images

    l Creating ECSs using imagesFor details, see the Elastic Cloud Server User Guide.

    1.1.2 OSs for Public Images Supported by IMSTable 1-2 lists the OSs supported by IMS for public images.

    Image Management ServiceUser Guide 1 Overview

    Issue 13 (2017-08-30) 2

  • Table 1-2 OSs supported by IMS for public images

    OS Version

    Windows Windows 2012 R2 Datacenter EnglishWindows 2012 R2 Standard EnglishWindows 2012 R2 StandardWindows 2012 R2 DatacenterWindows Server Standard 2008 R2 64bitWindows Server Datacenter 2008 R2 64bitWindows Server Enterprise 2008 R2 64bitWindows Server Enterprise 2008 SP2 64bitWindows Web Server 2008 R2 64bit

    Ubuntu Server Ubuntu Server 14.04 64bitUbuntu Server 14.04 32bit

    CentOS CentOS 7.0 64bitCentOS 7.1 64bitCentOS 6.5 64bitCentOS 6.3 64bit

    Debian Debian 8.2 64bitDebian 8.6.0 64bitDebian 7.5 64bitDebian 7.5 32bitDebian 8.8.0 64bitDebian 9.0.0 64bit

    OpenSUSE OpenSUSE 13.2 64bit

    The following table lists the supported OSs of public images used to create special types ofECSs. OSs of ECSs not listed in the table are consistent with those supported for publicimages.

    Table 1-3 Special ECSs and OSs supported by them

    ECS Supported OS

    GPU-optimized (g1) ECS Windows Server 2008 R2 Enterprise SP164bitWindows Server 2012 R2 Standard 64bitWindows Server 2016 Datacenter

    Image Management ServiceUser Guide 1 Overview

    Issue 13 (2017-08-30) 3

  • ECS Supported OS

    GPU-optimized (g2) ECS Windows Server 2008 R2 Enterprise SP164bitWindows Server 2012 R2 Standard 64bit

    Disk-intensive ECS CentOS 7.2 64bitCentOS 7.3 64bitCentOS 6.8 64bitSUSE Enterprise Linux Server 11 SP3 64bitSUSE Enterprise Linux Server 11 SP4 64bitSUSE Enterprise Linux Server 12 SP1 64bitSUSE Enterprise Linux Server 12 SP2 64bitRed Hat Enterprise Linux 6.8 64bitRed Hat Enterprise Linux 7.3 64bit

    High-performance ECS CentOS 6.8 64bitCentOS 7.2 64bitCentOS 7.3 64bitWindows Server 2008Windows Server 2012Windows Server 2016SUSE Linux Enterprise Server 11 SP3 64bitSUSE Linux Enterprise Server 11 SP4 64bitSUSE Linux Enterprise Server 12 SP1 64bitSUSE Linux Enterprise Server 12 SP2 64bitRed Hat Enterprise Linux 6.8 64bitRed Hat Enterprise Linux 7.3 64bit

    1.1.3 Image Formats and OS Types of External Image Files

    Image FormatExternal image files in VMDK, VHD, QCOW2, or ZVHD format can be used to createprivate images. You can select an appropriate image format as you need.

    OS TypeFor how to register an image, see section 2.4.3 Registering an External Image File as aPrivate Image. For Linux, if the required version is not listed in Table 1-4, Other (64bit)will be selected automatically.

    NOTE

    Images using OSs not listed in Table 1-4 may fail to be uploaded. You are advised to contact customerservice.

    Image Management ServiceUser Guide 1 Overview

    Issue 13 (2017-08-30) 4

  • Table 1-4 Supported image formats and OSs

    OS Type OS Version

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

    Oracle Linux Oracle Linux Server release 7.3 64bitOracle Linux Server release 7.2 64bitOracle Linux Server release 7.1 64bitOracle Linux Server release 7.0 64bitOracle Linux Server release 6.9 64bitOracle Linux Server release 6.8 64bitOracle Linux Server release 6.7 64bitOracle Linux Server release 6.5 64bit

    Redhat Redhat Linux Enterprise 7.3 64bitRedhat Linux Enterprise 7.2 64bitRedhat Linux Enterprise 7.1 64bitRedhat Linux Enterprise 7.0 64bitRedhat Linux Enterprise 6.9 64bitRedhat Linux Enterprise 6.8 64bitRedhat Linux Enterprise 6.7 64bitRedhat Linux Enterprise 6.6 64bitRedhat Linux Enterprise 6.6 32bitRedhat Linux Enterprise 6.4 64bitRedhat Linux Enterprise 6.4 32bit

    Ubuntu Ubuntu 16.04 server 64bitUbuntu 14.04.4 server 64bitUbuntu 14.04.4 server 32bitUbuntu 14.04.3 server 64bitUbuntu 14.04.3 server 32bitUbuntu 14.04.1 server 64bitUbuntu 14.04.1 server 32bitUbuntu 14.04 server 64bitUbuntu 14.04 server 32bit

    Image Management ServiceUser Guide 1 Overview

    Issue 13 (2017-08-30) 5

  • OS Type OS Version

    OpenSUSE OpenSUSE 42.3 64bitOpenSUSE 42.2 64bitOpenSUSE 42.1 64bitOpenSUSE 13.2 64bitOpenSUSE 11.3 64bit

    CentOS CentOS 7.3 64bitCentOS 7.2 64bitCentOS 7.1 64bitCentOS 7.0 64bitCentOS 7.0 32bitCentOS 6.9 64bitCentOS 6.8 64bitCentOS 6.7 64bitCentOS 6.7 32bitCentOS 6.6 64bitCentOS 6.6 32bitCentOS 6.5 64bitCentOS 6.5 32bitCentOS 6.4 64bitCentOS 6.4 32bitCentOS 6.3 64bitCentOS 6.3 32bit

    Debian Debian GNU/Linux 8.7.0 64bitDebian GNU/Linux 8.6.0 64bitDebian GNU/Linux 8.5.0 64bitDebian GNU/Linux 8.4.0 64bitDebian GNU/Linux 8.2.0 64bitDebian GNU/Linux 8.8.0 64bitDebian GNU/Linux 9.0.0 64bit

    Fedora Fedora 26 64bitFedora 25 64bitFedora 24 64bitFedora 23 64bitFedora 22 64bit

    EulerOS EulerOS 2.2 64bit

    Image Management ServiceUser Guide 1 Overview

    Issue 13 (2017-08-30) 6

  • NOTE

    If you upload an image using an OS not listed in Table 1-4, the OS type will be set to Other (64bit).

    1.2 Charging

    1.2.1 Charging StandardIMS and the OS license are free. You are required to pay for storing your private images inthe Object Storage Service (OBS) bucket. You can use the OBS storage free of charge duringthe trial period.

    1.3 IMS Access and Usage

    1.3.1 Accessing IMSThe public cloud system provides web-based service management. You can use themanagement console or HTTPS-based application programming interfaces (APIs) to manageIMS.

    l APIYou can access IMS using APIs. For details, see the Image Management Service APIReference.

    l Management consoleYou can perform other operations provided by IMS on the management console. If youhave registered an account in the public cloud system, log in to the management consoleand click Image Management Service on the homepage.

    1.3.2 IMS Relationships with Other Servicesl Elastic Cloud Server (ECS)

    You can use an image to create an ECS or convert an ECS into an image.l Object Storage Service (OBS)

    Images are stored in OBS buckets.l Key Management Service (KMS)

    Keys used for encrypting images are provided by KMS.

    Image Management ServiceUser Guide 1 Overview

    Issue 13 (2017-08-30) 7

    http://www.hwclouds.com/product/ims.htmlhttp://www.hwclouds.com/product/ecs.htmlhttp://www.hwclouds.com/product/obs.htmlhttp://www.hwclouds.com/en-us/product/kms.html

  • 2 Getting Started2.1 Introduction

    Public images are standard images provided by the public cloud system. You can use theseimages to create ECSs.

    Private images are visible only to their creators. Private images contain OSs, pre-installedpublic applications, and users' private applications. Creating ECSs using private images canreduce ECS configuration time. Private images can be created using ECSs or external imagefiles.

    This chapter describes the following private image creation methods:

    l Create a Windows private image using an ECS.l Create a Linux private image using an ECS.l Create a Linux private image using an external image file.

    2.2 Creating a Windows Private Image Using an ECS

    2.2.1 OverviewYou can create a Windows private image using an ECS running Windows.

    Before creating the Windows private image, you need to log in to the Windows ECS used tocreate the image and perform the following operations:

    l Configure a Windows ECS.l Install Cloudbase-Init.l Create a Windows private image.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 8

  • 2.2.2 Configuring a Windows ECS

    ScenariosIf the Windows ECS used to create a private image is using a static IP address, set its IPaddress obtaining mode to DHCP.

    This section uses Windows Server 2008 R2 as an example to describe how to configureDHCP on a Windows ECS. For details about how to configure DHCP on ECSs running otherOSs, see the relevant OS documentation.

    PrerequisitesYou have logged in to the ECS that will be used to create the Windows private image.

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

    Procedure1. On the ECS, choose Start > Control Panel.2. Click Network and Internet Connections.3. Click Network and Sharing Center. Figure 2-1 shows the Network and Sharing

    Center window.

    Figure 2-1 Network and Sharing Center

    4. Select the connection configured with the static IP address. For example, click LocalArea Connection 2.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 9

  • Figure 2-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 2-3 shows the dialog box forconfiguring the IP address obtaining mode.

    NOTE

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

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 10

  • Figure 2-3 Configuring the IP address obtaining mode

    The system will automatically obtain an IP address.

    (Optional) Install the GPU driver.

    If an independent GPU is configured for the ECS, you must first install the GPU driver beforeusing the ECS to create an image.

    7. Obtain the ECS GPU driver package from NVIDIA website http://www.nvidia.com/grid-eval. Select NVIDIA GRID version 4.1 and the software package GRID for UVP.

    8. Copy the Windows driver package in the downloaded software package to the ECS. Thedriver package version must be consistent with the ECS OS version.

    9. Install the driver on the ECS.

    10. Set the ECS resolution to 1920 x 1080 (recommended) or smaller.

    (Optional) Enable the Remote Desktop Connection function.

    You must enable the Remote Desktop Connection function of ECSs if you want to connect tothem using this function subsequently.

    This function must be enabled for GPU-optimized ECSs.

    11. Choose Start, right-click Computer, and choose Properties from the shortcut menu.

    12. Click Remote settings.

    13. In the Remote tab, select Allow connections from computers running any version ofRemote Desktop (less secure).

    14. Click OK.

    15. Choose Start > Control Panel and navigate to Windows Firewall.

    16. Choose Allow a program or feature through Windows Firewall in the left pane.

    17. Select programs and features that are allowed through by the Windows firewall forRemote Desktop based on user network requirements and click OK in the lower part.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 11

    http://www.nvidia.com/grid-evalhttp://www.nvidia.com/grid-eval

  • Figure 2-4 Configuring Remote Desktop

    2.2.3 Installing Cloudbase-Init

    Scenarios

    To ensure that ECSs created using a private image support custom configurations, you areadvised to install Cloudbase-Init on the ECS before using it to create a private image.

    If you do not install Cloudbase-Init, you can log in to the ECS only with the original imagepassword, and you will be unable to customize ECS configurations.

    NOTE

    This feature is supported in Southern and Eastern China.

    Prerequisitesl An elastic IP address has been bound to the Windows ECS.l You have logged in to the Windows ECS.l The IP address obtaining mode of the Windows ECS has been set to DHCP.

    Procedure1. On the Windows Start menu, choose Control Panel > Programs > Programs and

    Features to check whether Cloudbase-Init is installed.– If yes, go to step 16.– If no, go to step 2.

    2. Check whether the OS is a Windows desktop version:– If yes, go to step 3.– If no and the OS is Windows Server, go to step 4.

    3. Perform the following operations to ensure that the administrator account is enabled(Windows 7 is used as an example):

    a. Click Start and choose Control Panel > System and Security > AdministrativeTools.

    b. Double-click Computer Management.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 12

  • c. Choose System Tools > Local Users and Groups > Users.

    d. Right-click Administrator and select Properties.

    e. Ensure that Account is disabled is not selected.

    4. Download the Cloudbase-Init installation package.

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

    Cloudbase-Init has two versions, the stable and Beta version.

    To obtain the stable version, visit the following paths:

    – 64-bit: https://www.cloudbase.it/downloads/CloudbaseInitSetup_Stable_x64.msi

    – 32-bit: https://www.cloudbase.it/downloads/CloudbaseInitSetup_Stable_x86.msi

    To obtain the Beta version, visit the following paths:

    – 64-bit: https://www.cloudbase.it/downloads/CloudbaseInitSetup_x64.msi

    – 32-bit: https://www.cloudbase.it/downloads/CloudbaseInitSetup_x86.msi

    5. Double-click the Cloudbase-Init installation package.

    6. Click Next.

    7. Select I accept the terms in the License Agreement, and click Next.

    8. Retain the default path and click Next.

    9. In the Configuration options window, enter Administrator for Username and selectCOM1 for Serial port for logging. Figure 2-5 shows the parameters to be specified.

    Figure 2-5 Configuring parameters

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 13

    http://www.cloudbase.it/cloud-init-for-windows-instances/http://www.cloudbase.it/cloud-init-for-windows-instances/https://www.cloudbase.it/downloads/CloudbaseInitSetup_Stable_x64.msihttps://www.cloudbase.it/downloads/CloudbaseInitSetup_Stable_x64.msihttps://www.cloudbase.it/downloads/CloudbaseInitSetup_Stable_x86.msihttps://www.cloudbase.it/downloads/CloudbaseInitSetup_Stable_x86.msihttps://www.cloudbase.it/downloads/CloudbaseInitSetup_x64.msihttps://www.cloudbase.it/downloads/CloudbaseInitSetup_x86.msi

  • NOTE

    The version number in the figure is for reference only. Use the latest version.

    10. Click Next.11. Click Install.12. In the Files in Use dialog box, select Close the application and attempt to restart

    them and click OK.13. Check whether the OS is a Windows desktop version:

    – If yes, go to step 15.– If no, go to step 14.

    14. In the Completed the Cloudbase-Init Setup Wizard window, ensure that Run Sysprepto create a generalized Image. This is necessary if you plan to duplicate thisinstance, for example by creating a Glance image and Shutdown when Sysprepterminates are not selected.

    Figure 2-6 Completing the Cloudbase-Init installation

    NOTE

    The version number in the figure is for reference only. Use the latest version.

    15. Click Finish.16. Add configuration item netbios_host_name_compatibility=false to the last row in the

    C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf file.This will allow the host name to contain a maximum of 63 characters.

    NOTE

    The length of NetBIOS is limited by Windows and can contain at most 15 characters.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 14

  • 17. (Optional) If you log in using the password injection method for the first time, you willbe forced to change the password. If you do not want to change the password, you candisable this function. Add configuration item first_logon_behaviour=no to thecloudbase-init.conf configuration file in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\ directory.

    18. Release the current DHCP address so that created ECSs can obtain the correct addresses.

    In the Windows command line, run the following command to release the current DHCPaddress:

    ipconfig /release

    NOTE

    This operation will interrupt network connection and adversely affect the use of the ECS. After theECS is restarted, network connection will restore.

    19. Check whether the ECS needs to be added to a domain.

    – If yes, go to step 20.

    – If no, the installation is complete.

    20. Perform the following Sysprep operations on Windows:

    – Enter the Cloudbase-Init installation directory.

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

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

    – Run the following command to encapsulate Windows:

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

    After the command is executed, the ECS will stop automatically.

    NOTE

    l Ensure that /unattend:Unattend.xml is contained in the preceding command.Otherwise, the username, password, and other important configuration information ofthe ECS will be reset, and you must configure the OS manually when you use ECSscreated using the Windows private image.

    l After the Sysprep operation is performed on the ECS running Windows Server 2012 orWindows Server 2012 R2, the administrator account and password of the ECS will bedeleted. You need to log in to the ECS and configure the password of the administratoraccount. After this, the ECS password configured on the management console willbecome invalid. Keep the new password secure.

    l If the domain account is required to log in to Windows, perform the Sysprep operationbefore creating the private image. For details about the impact of the Sysprep operation,see http://support.hwclouds.com/ims_faq/ims_faq_0024.html.

    l Do not start a Windows ECS on which the Sysprep operation has been performed.Otherwise, you need to perform the Sysprep operation again on the ECS.

    l The Cloudbase-Init account of a Windows ECS is an internal account of the Cloudbase-Init agent. This account is used for obtaining metadata and completing relevantconfiguration when the Windows ECS starts. If you modify or delete this account, oruninstall the Cloudbase-Init agent, you will be unable to inject the initialized customizedinformation into an ECS created using a Windows private image. Therefore, you are notadvised to modify or delete the Cloudbase-Init account.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 15

    http://support.hwclouds.com/ims_faq/ims_faq_0024.html

  • 2.2.4 (Optional) Optimizing a Windows Private ImageFor how to optimize a Windows private image, see section 3.6 (Optional) Optimizing aWindows Private Image.

    2.2.5 Creating a Windows Private Image

    Scenarios

    This section describes how to create a Windows private image using an ECS.

    Prerequisitesl A Windows ECS is available and is stopped.

    l The IP address obtaining mode of the Windows ECS NIC has been set to DHCP. Fordetails, see section 2.2.2 Configuring a Windows ECS.

    l Cloudbase-Init has been installed.

    Procedure1. Log in to the management console.2. Under Computing, click Image Management Service.3. On the Image Mgmt Service page, click Create Private Image.4. On the image configuration page, click Select and select the required ECS. Set the

    required information, such as Name and Description on the displayed page.

    Figure 2-7 Creating an image

    5. Click Apply Now.6. Confirm image parameters as prompted.7. Read and agree to the ECS agreement and system image disclaimer and click Submit

    Application.8. Switch back to the Image Mgmt Service page to view the image status.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 16

  • The time required to create an image varies depending on the image file size. Generally,creating an image takes about 20 minutes. The image is created successfully when theimage status on the Image Mgmt Service page changes to Normal.

    NOTE

    l Do not perform any operation on the selected ECS or its associated resources during imagecreation.

    l An ECS created using an encrypted image is an encrypted ECS. The key of the encrypted ECSis the same as that of the encrypted image.

    2.3 Creating a Linux Private Image Using an ECS

    2.3.1 OverviewYou can create a Linux private image using a Linux ECS.

    Before creating the Linux private image, you need to log in to the Linux ECS used to createthe image and perform the following operations:

    l Query and configure NIC attributes.l Query and delete files in the network rule directory.l Install Cloud-Init.l Configuring Linux VM Network Attributes (Using Cloud-Init)l Query and detach EVS data disks from the ECS.

    This section introduces how to configure a Linux ECS and use it to create a Linux privateimage.

    2.3.2 Querying and Configuring NIC Attributes

    Scenarios

    If the Linux ECS that will be used to create a private image is using a static IP address,configure the IP address obtaining mode of the ECS NIC to DHCP.

    The configuration method varies depending on OSs.

    Prerequisites

    You have logged in to the ECS used to create the Linux private image.

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

    Procedurel For Red Hat, CentOS, Oracle Enterprise Linux, and EulerOS, use the vi editor to add

    PERSISTENT_DHCLIENT="y" to the configuration file /etc/sysconfig/network-scripts/ifcfg-ethX.

    l For SUSE Linux Enterprise, use the vi editor to set DHCLIENT_USE_LAST_LEASEto no in the configuration file /etc/sysconfig/network/dhcp.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 17

  • l For Ubuntu 12.04, upgrade dhclient to ISC dhclient 4.2.4 so that the NIC canconsistently obtain IP addresses from the DHCP server. For the detailed upgrade method,see the OS documentation.

    This section uses Ubuntu14.04 as an example to describe how to query and configure NICattributes.

    1. Run the following command on the ECS to open the /etc/network/interfaces file usingthe vi editor and query the IP address obtaining mode:vi /etc/network/interfaces– If the IP address obtaining mode of all NICs is DHCP, as shown in Figure 2-8,

    enter :q to exit the vi editor.

    Figure 2-8 DHCP IP address obtaining mode

    – If the IP address obtaining mode of a NIC is static, as shown in Figure 2-9, go to 2.

    Figure 2-9 Static IP address obtaining mode

    2. Press i to enter the editing mode.3. Delete the static IP address configuration and configure the DHCP IP address obtaining

    mode. Figure 2-10 shows the configuration commands.You can insert a number sign (#) in front of each line of the static IP addressconfiguration to comment it out.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 18

  • Figure 2-10 Setting the IP address obtaining mode of a NIC to DHCP

    If the ECS has multiple NICs, configure all other NICs in the same way. Figure 2-11shows the configuration commands.

    Figure 2-11 Setting the IP address obtaining mode of multiple NICs to DHCP

    4. Press Esc, type :wq, and press Enter.The system saves the configuration and exits the vi editor.

    2.3.3 Installing Cloud-Init

    Scenarios

    To ensure that ECSs created using private images support custom configurations, you areadvised to install Cloud-Init before creating private images. To install Cloud-Init on an ECSrunning Linux, download Cloud-Init from the official website. Therefore, you need toconfigure an elastic IP address for the ECS.

    If you do not install Cloud-Init, you can log in to the ECS only with the original imagepassword, and cannot customize ECS configuration.

    NOTE

    This feature is supported in Southern and Eastern China.

    Prerequisitesl An elastic IP address has been bound to the Linux ECS.l You have logged in to the Linux ECS.l DHCP has been enabled for the Linux ECS.

    Procedure

    Check whether Cloud-Init is installed.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 19

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

    rpm -qa |grep cloud-init

    l Cloud-Init has been installed if the following command output is displayed:cloud-init-0.7.5-10.el6.centos.2.x86_64– Check whether to continue to use the certificate in the ECS OS. If the certificate is

    no longer used, delete it.n If the certificate is stored in a directory of user root, such as .ssh/

    authorized_keys in the /$path/$to/$root directory, run the followingcommands:cd /root/.sshrm authorized_keys

    n If the certificate is not stored in a directory of user root, such as .ssh/authorized_keys in the /$path/$to/$none-root directory, run the followingcommands:cd /home/centos/.sshrm authorized_keys

    – Run the following command to ensure that the ECS created using the Linux imagesupports login using the certificate:sudo rm -rf /var/lib/cloud/*

    NOTE

    After the configuration is complete, do not restart the ECS. Otherwise, you must configure theECS again.

    l If Cloud-Init has not been installed, install it.

    Install Cloud-Init.

    You can install Cloud-Init in two ways:

    l Method 1: use the official package (recommended).l Method 2: use the official Cloud-Init source code package and pip.l Method 1: install Cloud-Init using the official package.

    The methods of installing Cloud-Init on ECSs running different OSs vary. Perform theinstallation operations as user root.

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

    Table 2-1 lists the Cloud-Init's network installation addresses for different versions ofSUSE Linux OSs.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 20

  • Table 2-1 Cloud-Init's network installation addresses for different versions of SUSELinux OSs

    OS Type Version How to Obtain

    SUSE SUSE EnterpriseLinux Server 12 SP2

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

    SUSE EnterpriseLinux Server 12 SP1

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

    SUSE EnterpriseLinux Server 11 SP4

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

    SUSE EnterpriseLinux Server 11 SP3

    https://anorien.csc.warwick.ac.uk/mirrors/download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/Cloud:Tools.repo

    OpenSUSE openSUSE Leap42.3

    http://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.3/Cloud:Tools.repo

    openSUSE Leap42.2

    http://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.2/Cloud:Tools.repo

    openSUSE Leap42.1

    http://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.1/Cloud:Tools.repo

    Take the SUSE Enterprise Linux Server 11 SP3 as an example. Perform the followingsteps to install Cloud-Init:

    a. Log in to the ECS used to create the private Linux image.

    b. Run the following command to install the network installation source for SUSEEnterprise Linux Server 11 SP3:

    zypper ar https://anorien.csc.warwick.ac.uk/mirrors/download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/Cloud:Tools.repo

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

    zypper refresh

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

    zypper install cloud-init

    e. Run the following command to enable Cloud-Init to automatically start upon systemstartup:

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 21

    http://download.opensuse.org/repositories/Cloud:/Tools/SLE_12_SP2/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/SLE_12_SP2/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/SLE_12_SP2/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/SLE_12_SP1/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/SLE_12_SP1/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/SLE_12_SP1/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP4/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP4/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP4/Cloud:Tools.repohttps://anorien.csc.warwick.ac.uk/mirrors/download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/Cloud:Tools.repohttps://anorien.csc.warwick.ac.uk/mirrors/download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/Cloud:Tools.repohttps://anorien.csc.warwick.ac.uk/mirrors/download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/Cloud:Tools.repohttps://anorien.csc.warwick.ac.uk/mirrors/download.opensuse.org/repositories/Cloud:/Tools/SLE_11_SP3/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.3/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.3/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.3/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.3/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.2/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.2/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.2/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.2/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.1/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.1/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.1/Cloud:Tools.repohttp://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.1/Cloud:Tools.repo

  • n SUSE 11chkconfig cloud-init-local on; chkconfig cloud-init on; chkconfig cloud-configon; chkconfig cloud-final onservice cloud-init-local status; service cloud-init status; service cloud-configstatus; service cloud-final statusn SUSE 12 and openSUSE 12/13/42systemctl enable cloud-init-local.service cloud-init.service cloud-config.servicecloud-final.servicesystemctl status cloud-init-local.service cloud-init.service cloud-config.servicecloud-final.service

    NOTICEFor SUSE and OpenSUSE, perform the following steps to disable dynamic changeof the ECS name:1. Run the following command to open the dhcp file using the vi editor:

    vi etc/sysconfig/network/dhcp2. Change the value of DHCLIENT_SET_HOSTNAME in the dhcp file to no.

    l CentOS and RedHatTable 2-2 lists the Cloud-Init's network installation addresses for CentOS and RedHat.

    Table 2-2 Cloud-Init installation addresses

    OS Type Version How to Obtain

    CentOS, RedHat, or OracleLinux

    7 https://dl.fedoraproject.org/pub/epel/7/x86_64/e/

    6 32-bit https://dl.fedoraproject.org/pub/epel/6/i386/

    6 64-bit https://dl.fedoraproject.org/pub/epel/6/x86_64/

    NOTE

    Select the required epel-release installation package in the addresses listed in Table 2-2.

    To install Cloud-Init on CentOS 6 and later versions, run the following commands(CentOS 6.5 64-bit is used as an example):yum install https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpmyum install cloud-init

    l FedoraBefore installing Cloud-Init, ensure that the network installation source address has beenconfigured for the OS by checking whether the /etc/yum.repo.d/fedora.repo filecontains the installation source address of the software package. If it does not, configurethe installation source address of the software package by following the instructions atthe Fedora official website.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 22

    https://dl.fedoraproject.org/pub/epel/7/x86_64/e/https://dl.fedoraproject.org/pub/epel/6/i386/https://dl.fedoraproject.org/pub/epel/6/x86_64/

  • Run the following command to install Cloud-Init:yum install cloud-init

    l Debian and UbuntuBefore installing Cloud-Init, ensure that the network installation source address has beenconfigured for the OS by checking whether the /etc/apt/sources.list file contains theinstallation source address of the software package. If it does not, configure theinstallation source address of the software package by following the instructions at theDebian or Ubuntu official website.Run the following command to install Cloud-Init:apt-get updateapt-get install cloud-init

    l Method 2: install Cloud-Init using the official source code and PIP.

    The following procedure uses Cloud-Init 0.7.5 as an example to describes how to installCloud-Init.

    1. Download the cloud-init-0.7.5.tar.gz source code package (version 0.7.5 isrecommended) and upload it to the /home/ directory on the VM.Download cloud-init-0.7.5.tar.gz from the following path:The download path is https://launchpad.net/cloud-init/trunk/0.7.5/+download/cloud-init-0.7.5.tar.gz.

    2. Create a pip.conf file in the ~/.pip/ directory and edit the following content:

    NOTE

    If the ~/.pip/ directory does not exist, run the mkdir ~/.pip command to create it in the makedirectory.

    [global]index-url = https:///simple/trusted-host =

    NOTE

    Replace with a public or education network PyPI source.

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

    l Education network PyPI source: https://pypi.tuna.tsinghua.edu.cn/

    https://pypi.mirrors.ustc.edu.cn/

    3. Run the following command to install the downloaded cloud-init-0.7.5.tar.gz sourcecode package (during installation, select --upgrade):# pip install [--upgrade] /home/cloud-init-0.7.5.tar.gz

    4. Run the cloud-init -v command. Cloud-Init is installed successfully if the followinginformation is displayed:cloud-init 0.7.5

    5. OS vendors need to set Cloud-Init services to start automatically. The configurationmethod varies depending on the OS.– If the OS uses sysvinit to manage automatic start of services, run the following

    commands:# chkconfig --add cloud-init-local; chkconfig --add cloud-init; chkconfig --addcloud-config; chkconfig --add cloud-final

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 23

    https://launchpad.net/cloud-init/trunk/0.7.5/+download/cloud-init-0.7.5.tar.gzhttps://launchpad.net/cloud-init/trunk/0.7.5/+download/cloud-init-0.7.5.tar.gzhttps://pypi.python.org/https://pypi.tuna.tsinghua.edu.cn/https://pypi.mirrors.ustc.edu.cn/

  • # chkconfig cloud-init-local on; chkconfig cloud-init on; chkconfig cloud-configon; chkconfig cloud-final on# service cloud-init-local status; service cloud-init status; service cloud-configstatus; service cloud-final status

    – If the OS uses systemd to manage automatic start of services, run the followingcommands:# 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.servicecloud-final.service

    NOTICEIf you install Cloud-Init using the official source code package and pip, pay attention to thefollowing two points:1. During the Cloud-Init installation, you need to add user syslog to the adm group. If user

    syslog exists, add it to the adm group. If user syslog (such as RHEL, CentOS, and SLES)does not exist, run the following commands to create user syslog and add it to the admgroup.# useradd sysloggroupadd adm

    2. Change the value of distro in system_info in the /etc/cloud/cloud.cfg file based on theOS release version, such as distro: ubuntu, distro: rhel, distro: sles, distro: debian, anddistro: fedora.

    Configure permissions of the user for logging in to the ECS.

    Select the type of the user.

    If you select user root, enable the SSH permissions of user root and enable remote login tothe ECS using a password.

    l If you inject a password, use it to log in to the ECS remotely using SSH or noVNC.l If you inject a private key, use it to log in to the ECS remotely using SSH.

    Perform the following operations:

    1. Run the following command to open the /etc/cloud/cloud.cfg file using the vi editor:vi /etc/cloud/cloud.cfgEnable remote login using the password of user root and enable the SSH permissions ofuser root. Take CentOS 6.7 as an example. If the value of disable_root in theconfiguration file is 1, the permissions are disabled. If the value is 0, the permissions areenabled. In some OSs, the value true indicates that the permissions are disabled andfalse indicates that the permissions are enabled). Set the value of disable_root to 0 andthat of ssh_pwauth to 1.users: - root

    disable_root: 0ssh_pwauth: 1

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 24

  • 2. Run the following command to open the /etc/ssh/sshd_config file using the vi editor:vi /etc/ssh/sshd_config

    3. Change the value of PasswordAuthentication in the sshd_config file to yes.

    NOTE

    For SUSE and openSUSE, change the values of the following parameters in the sshd_config fileto yes:l PasswordAuthenticationl ChallengeResponseAuthentication

    4. Delete user linux and the /home/linux directory from the image template of the ECS.# userdel linux# rm -fr /home/linux

    Check whether the Cloud-Init configuration is successful.

    Run the following command (if no error occurs, Cloud-Init is properly configured):

    cloud-init init --local

    If Cloud-Init is properly installed, the version information will be displayed and no errorinformation is displayed. such as a message indicating lack of files, will be displayed. If amessage is displayed indicating a configuration error, contact technical support.

    2.3.4 Configuring Linux VM Network Attributes (Using Cloud-Init)

    ScenariosConfigure network attributes for a Linux VM. If the Linux VM is converted to a template tocreate other VMs or clone the Linux VM to a new VM, this configuration is required if thecreated VMs need to automatically obtain an IP address using the Dynamic HostConfiguration Protocol (DHCP) or the VMs run Linux. This configuration, includingactivating NIC and enabling DHCP service, enables the created VMs to access networks andautomatically obtain IP addresses.

    This section uses SUSE Linux 11 SP1 OS as an example to describe how to configurenetwork attributes for a Linux VM. For details about the configuration methods for other OSs,see product documents of the target OSs.

    PrerequisitesPrerequisites

    The OS and Tools have been installed on the VM.

    ProcedureDelete files in the network rule directory.

    1. Run the following command to query the files in the network rule directory:ls -l /etc/udev/rules.d

    2. Run the following commands to delete the rule files whose names contain persistent andnet from the network rule directory:

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 25

  • Example:

    rm /etc/udev/rules.d/30-net_persistent-names.rules

    rm /etc/udev/rules.d/70-persistent-net.rules //Replace the italic part in the commandwith the actual value at your site.

    3. Run the following command to check whether the initrd image file started with initrdand ended with default contains both persistent and net network rules:

    lsinitrd /boot/initrd-2.6.32.12-0.7-default |grep persistent|grep net

    – If no, go to step 5.a.

    – If yes, go to step 4.

    4. Run the following command to back up the initrd image file:

    cp /boot/initrd-2.6.32.12-0.7-default /boot/initrd-2.6.32.12-0.7-default_bak

    5. Run the following command to generate the initrd file again:

    mkinitrd

    NOTE

    Perform the following operations if an OS, such as Ubuntu, uses inittramfs images:

    1. Run the following command to check whether the inittramfs image files starting with initrdand ending with generic contain persistent and net rule files.

    lsinitramfs /boot/initrd.img-3.19.0-25-generic|grep persistent|grep net

    If no, go to step 5.a.

    If yes, go to step 5.b.

    2. Run the following command to back up the initrd image file:

    cp /boot/initrd.img-3.19.0-25-generic /boot/initrd.img-3.19.0-25-generic_bak

    3. Run the following command to generate the inittramfs image file again:

    update-initramfs -u

    Disable the NetworkManager service.

    There are two methods of installing Linux online:

    – NetworkManager: automatic network configuration function provided by Linux

    – Traditional Method with ifup

    To enable the VM to obtain an IP address automatically by static injection, use thepredefined configuration file to overwrite the network configuration file in the VMduring the VM creation to configure an IP address for it.

    Therefore, the purpose of configuring the Linux OS online installation method is todisable the NetworkManager function. After it is disabled, the network configuration filein the VM can be overwritten.

    You can run one of the following commands to disable NetworkManager depending onthe OS:

    # service NetworkManager stop; chkconfig NetworkManager off

    or

    # systemctl stop NetworkManager.service; systemctl disableNetworkManager.service

    For SUSE Linux, you can also use YaST to disable NetworkManager. The procedure isas follows:

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 26

  • NOTE

    These steps are not required if no NetworkManager is deployed on the VM OS, for example,SUSE Linux Enterprise 12.

    a. Run the following command on the VM to enter the control center:yast

    b. Choose Network Devices > Network Settings.c. On the Network Settings page, press Alt+G.

    The Global Options page is displayed.

    NOTE

    If the shortcut keys provided in the steps do not take effect in practice due to OS version orlanguage diversities, use Tab, ←, and → keys to select the required options.

    d. Press Alt+T and select Traditional Method with ifup.e. Press F10 to save the configuration and exit the control center.f. Hold down Alt and press Q.

    The command-line interface is displayed.

    2.3.5 (Optional) Optimizing a Linux Private ImageFor how to optimize a Linux private image, see section 3.7 (Optional) Optimizing a LinuxPrivate Image.

    2.3.6 Querying and Detaching EVS Data Disks from the ECS

    Scenarios

    You must detach all EVS data disks attached to the ECS before using it to create a privateimage, because if the ECS used to create the private image has multiple EVS data disksattached, new ECSs created using the private image may be unavailable. Therefore, you mustdetach all EVS data disks attached to the ECS before using it to create a private image.

    Prerequisites

    You have logged in to the ECS used to create the Linux private image.

    Procedure1. Run the following command to check the EVS disks attached to the ECS:

    mount– If the command output does not contain any EVS disk information, no EVS data

    disks need to be detached.– If information similar to the following is displayed, go to 2:

    /dev/xvde1 on /mnt/test type ext4 (rw)

    2. Ensure that no data read and write operations are being performed on the EVS disks thatwill be detached. Otherwise, the detaching operation will fail.Run the following command to detach the EVS data disks attached to the ECS:umount /dev/xvde1

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 27

  • 3. Run the following command to edit the fstab file:vi /etc/fstab

    4. Delete the configuration information of the EVS data disks from the fstab file.The /etc/fstab file contains information about the file systems and storage devicesautomatically attached to the ECS when the ECS starts. The configuration informationabout data disks automatically attached to the ECS needs to be deleted. For example, thelast row shown in Figure 2-12 is the data disk configuration information to be deletedfrom the fstab file.

    Figure 2-12 EVS configuration information contained in the fstab file

    5. Run the following command to check the data partitions attached to the ECS:mountIf the command output does not contain information about the EVS data disks, they havebeen successfully detached.

    2.3.7 Creating a Private Linux Image

    Scenarios

    Create a private Linux image using an ECS.

    Prerequisitesl A Linux ECS is available and is stopped.l The IP address assignment mode of the Linux ECS NIC has been set to DHCP.l Cloud-Init has been installed and configured.l ECS network attributes have been configured.l All EVS data disks attached to the Linux ECS have been detached.

    Procedure1. Log in to the management console.2. Under Computing, click Image Management Service.3. On the Image Mgmt Service page, click Create Private Image.4. On the image configuration page, click Select and select the required ECS on the

    displayed page.5. Set the required information, such as Name and Description on the displayed page

    shown in Figure 2-13 .

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 28

  • Figure 2-13 Creating an image

    6. Click Apply Now.7. Confirm image parameters as prompted.8. Read and agree to the ECS agreement and system image disclaimer and click Submit

    Application.9. Switch back to the Image Mgmt Service page to view the image status.

    The time required to create an image varies depending on the image file size. Generally,creating an image takes about 20 minutes. The image is created successfully when theimage status on the Image Mgmt Service page changes to Normal.

    NOTE

    l Do not perform any operation on the selected ECS or its associated resources during imagecreation.

    l An ECS created using an encrypted image is an encrypted ECS. The key of the encrypted ECSis the same as that of the encrypted image.

    2.4 Creating a Linux Private Image Using an ExternalImage File

    2.4.1 Overview

    Application ScenariosIf you have an external Linux image file and the file meets the type and OS requirementslisted in 1.1.3 Image Formats and OS Types of External Image Files, you can use thisexternal image file to create a private Linux image.

    Creation ProcessTo initialize an image, delete network rule files, configure the NIC attribute, and install andconfigure Cloud-Init. For details, see section What Initial Configuration Needs to BePerformed for an External Image File Used to Create a Private Image?.

    The procedure of creating a private image using an external image file varies depending onwhether the image file has been initialized.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 29

    http://support.hwclouds.com/en-us/ims_faq/ims_faq_0022.htmlhttp://support.hwclouds.com/en-us/ims_faq/ims_faq_0022.html

  • l If the external image file has been initialized, the procedure of creating a private image isas follows.

    Figure 2-14 Creating a private image using an initialized image file

    The procedure is as follows:

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

    b. On the management console, select the uploaded image file and register it as aprivate image. For details, see 2.4.3 Registering an External Image File as aPrivate Image.

    l If the external image file has not been initialized, the procedure of creating a privateimage is as follows.

    Figure 2-15 Creating a private image using an uninitialized image file

    The procedure is as follows:

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

    b. On the management console, select the uploaded image file and register it as aprivate image that has not been initialized. For details, see 2.4.3 Registering anExternal Image File as a Private Image.

    c. Use the private image to create an ECS. For details, see 2.4.4 Creating an ECS.d. Log in to the ECS created in c remotely and configure it. For details, see 2.4.5

    Configuring a Linux ECS.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 30

  • NOTE

    Linux ECSs running on the public cloud platform must use PVOPS.

    e. Create a private image in normal state using the ECS. For details, see 2.4.6Creating a Private Image Using an ECS.

    Restrictions and Limitationsl Image files in QCOW2 format must not be encrypted.l Images with EVS data disks cannot be created. External image files contain only EVS

    system disks.l If the private image uses Linux, the /etc/fstab file must not contain configuration items

    for automatic data disk attaching. Otherwise, ECSs created using a private image cannotbe logged in to.

    l An external image file cannot be larger than 128 GB.l The external image file system disk size must be greater than 1 GB and less than or equal

    to 255 GB.l Ensure that the image file contains the password or certificate used to log in to the ECS

    created using the image, or ensure that Cloud-Init has been installed and configured inthe image system.

    l Username root and its password must have been configured for the private image thatuses Linux. In subsequent operations, you may use the username and password to log into and configure the ECS.

    l To prevent ECSs created using the image file from being attacked, ensure that the initialpassword of the image file contains at least the following types of characters:– Uppercase letters– Lowercase letters– Digits– Special characters, including !@$%^-_=+[{}]:,./?

    l The image must support the Integrated Drive Electronics (IDE) and ParaVirtualOPerationS (PVOPS) device driver. The driver must be automatically loaded when thesystem starts.

    l The boot partition and system partition of the image must be on the same disk.l You must use BIOS to boot the ECS used to create the image.l If the disk of the external image file uses specific encryption mechanisms, the ECS

    created using the private image may become unavailable.l Some drivers are not supported on the public cloud platform. Therefore, you cannot use

    external image files containing OEM OSs to create private images.l OSs in external image files cannot be bound to specified hardware.l The OSs in your external image files must support full virtualization.l If the external image file uses the LVM as the system disk, ECSs created using the

    private image from the external image file do not support file injection.

    2.4.2 Uploading an External Image FileUpload the external image file to your OBS bucket. For details, see the Object StorageService User Guide. Any image file uploaded to an OBS bucket must be an unencrypted oneor one encrypted using SSE-KMS.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 31

  • 2.4.3 Registering an External Image File as a Private Image

    ScenariosThis section describes how to register an uninitialized image file as an uninitialized privateimage on the public cloud platform, or register an initialized image file as a private image innormal state.

    PrerequisitesYou have uploaded the image file to the OBS bucket.

    Procedure1. Log in to the management console.2. Under Computing, click Image Management Service.3. On the Image Mgmt Service page, click Create Private Image.

    Select Image File to use an external image file as the source, as shown in Figure 2-16.

    Figure 2-16 Registering an external image file as a private image

    4. Click Type and select the image type.5. Click Select to choose the external image file.6. Select the bucket that stores the image file in the left navigation tree and select the image

    file.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 32

  • Figure 2-17 Select Image File

    7. Click OK.If you selected an ECS image, go to step 8.

    8. Check whether the image file has been initialized.– If yes, select Initial configuration has been performed for this image file..– If no, go to 9.

    NOTE

    To initialize an image, delete network rule files, configure the NIC attribute, and install andconfigure Cloud-Init. For details, see section What Initial Configuration Needs to BePerformed for an External Image File Used to Create a Private Image?.

    9. Enter the image name.10. (Optional) Select the OS required by the image.

    To ensure that images can be created and used, select the OS consistent with that of theimage file. If you do not select an OS for the image file, the system will automaticallyidentify the OS of the image file.

    NOTE

    l If the system detects that the image file OS is different from that you configure, the OSdetected by the system will prevail.

    l If the system cannot detect the OS of the image file, the OS you select will prevail.

    l If the OS you select or identified by the system is inconsistent with that of the actual image,ECSs created using this image may be affected. For detailed impact, see section What ImpactWill Be Brought by an Inconsistency Between the Image OS I Select or Identified by theSystem and That of the Actual Image During Creation of a Private Image Using anExternal Image File?.

    11. (Optional) Encrypt the image.If the image needs to be encrypted, select KMS encryption and select the key to be usedfrom the list of keys. For how to encrypt an image, see section 3.8 Encrypting anImage.

    NOTE

    If you select KMS encryption, the system will create a default master private key ims/default foryou. You can also select a private key from the private key list.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 33

    http://support.hwclouds.com/en-us/ims_faq/ims_faq_0022.htmlhttp://support.hwclouds.com/en-us/ims_faq/ims_faq_0022.htmlhttp://support.hwclouds.com/en-us/ims_faq/ims_faq_0023.htmlhttp://support.hwclouds.com/en-us/ims_faq/ims_faq_0023.htmlhttp://support.hwclouds.com/en-us/ims_faq/ims_faq_0023.htmlhttp://support.hwclouds.com/en-us/ims_faq/ims_faq_0023.html

  • 12. Select a system disk size and enter the image description as required.

    NOTE

    If the uploaded VHD image is generated using qemu-img or similar tools, check the system disksize based on Why Does the Error Message Displayed on Task Center Indicates That theSystem Disk Size of the External Image File Exceeds the Maximum System Disk Size When aVHD Image File Failed to Be Uploaded?.

    13. Select Enable automatic configuration. The system will perform the followingoperations on the image file:Modify the grub and syslinux configuration files to add the OS kernel boot parametersand change the disk partition name to UUID=UUID of the disk partition.– Change the names of the disk partitions in the /etc/fstab file to UUID=UUID of the

    disk partition.– Check whether the initrd file has the Xen and IDE drivers. If no, load the Xen and

    IDE drivers.– Modify the xwindows configuration file /etc/X11/xorg.conf to prevent display

    failures.– Delete services of VMware tools.

    If the image file has the preceding configuration, you can choose not to selectEnable automatic configuration. Otherwise, select Enable automaticconfiguration.

    – For CentOS 7.2, CentOS 6.5, SUSE SLES 11 SP4, and Red Hat 7.2, the Linuxbuilt-in virtio frontend driver is added to initrd or initramfs.

    14. Click Apply Now.15. On the resource details page, confirm the specifications and click Submit Order.

    NOTE

    The time required for image registration is determined by the image file size. You may need to wait along period of time for the external image file to be successfully registered as a private image that is notinitialized.

    2.4.4 Creating an ECS

    Scenarios

    Create an ECS using a private image that is not initialized.

    Prerequisites

    A private image that is not initialized is available.

    Procedure1. Log in to the management console.2. Under Computing, click Image Management Service.3. On the Image Mgmt Service page, click the Private Image tab to switch to the page

    that displays all private images.4. Locate the row that contains the newly registered private image that is not initialized,

    and click Apply for ECS in the Operation column to create an ECS. You need to

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 34

    http://support.hwclouds.com/en-us/ims_faq/en-us_topic_0058841396.htmlhttp://support.hwclouds.com/en-us/ims_faq/en-us_topic_0058841396.htmlhttp://support.hwclouds.com/en-us/ims_faq/en-us_topic_0058841396.html

  • configure and delete this ECS later. Therefore, you are advised to choose the on-demandcharging mode when creating it.

    5. Complete ECS creation as prompted.For how to create an ECS, see the Elastic Cloud Server User Guide.If the image file system has Cloud-Init installed and configured, log in to the ECS usingthe password as prompted. If the image file system does not have Cloud-Init installed,log in to the ECS using the password or certificate contained in the image file.

    2.4.5 Configuring a Linux ECS

    Scenarios

    Configure the ECS created using the private image which is not initialized on the public cloudplatform to ensure that the ECS can be properly used.

    The following describes how to configure a Linux ECS.

    Procedure1. Log in to the Linux ECS.

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

    2. Check whether the private IP address of the ECS is consistent with that displayed on themanagement console. The methods of checking this vary depending on the OSs. TakeCentOS 6 as an example and run the following command to check the private IP addressof the ECS:ifconfigIf the IP address is incorrect, check and delete network udev rules on the Linux ECS. Fordetails, see 2.3.4 Configuring Linux VM Network Attributes (Using Cloud-Init).

    3. Check and configure the IP address assignment mode of the ECS NIC to DHCP. If theLinux ECS is using a static IP address, configure it by following the instructionsprovided in 2.3.2 Querying and Configuring NIC Attributes.

    4. Enable SSH for remote access and ensure that your host firewall (such as Linux iptables)allows access to SSH.

    5. Check whether Cloudbase-Init has been installed and configured:– If yes, go to step 6.– If no, install and configure Cloudbase-Init by following the instructions in 2.3.3

    Installing Cloud-Init.6. Perform the following steps to check and delete automatic attaching information about

    data disks in the /etc/fstab configuration file to prevent adverse impacts on future datadisk attaching operations:– Run the following command to edit the fstab file:

    vi /etc/fstab– Delete the configuration information about relevant data disks from the fstab file.

    The /etc/fstab file contains configuration information about all disks automaticallyattached to the ECS when the ECS starts. Such configuration information needs tobe deleted. For example, the last row shown in Figure 2-18 is the data diskconfiguration information which needs to be deleted from the fstab file.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 35

  • Figure 2-18 EVS configuration information contained in the fstab file

    NOTE

    l To use an image to create a memory-optimized generation II (m2) ECS, ensure that the virtio driveris installed.

    l To use an image to create a high-performance generation II (h2) ECS, ensure that the VirtIO andInfiniBand drivers are installed. Download the appropriate version of the InfiniBand NIC driverbased on the IB type from the Mellanox official website and install the driver by following theinstructions provided by Mellanox.

    InfiniBand NIC type: Mellanox Technologies ConnectX-4 Infiniband HBA (MCX455A-ECAT)Mellanox official website: http://www.mellanox.com/

    2.4.6 Creating a Private Image Using an ECSSelect the private image creation method based on the ECS OS. If the ECS runs Linux, createa private image using the ECS by following the steps provided in 2.3.7 Creating a PrivateLinux Image.

    2.4.7 (Optional) Cleaning Up the Environment

    ScenariosThe private image registered in 2.4.3 Registering an External Image File as a PrivateImage and the ECS created in 2.4.4 Creating an ECS incur additional fees. Therefore, youare advised to perform the following steps to clean up the environment after the private imageis created.

    Procedure1. Delete the uninitialized private image registered using the external image file. For

    details, see 3.3 Deleting an Image.2. Delete the ECS created in 2.4.3 Registering an External Image File as a Private

    Image. For details, see the Elastic Cloud Server User Guide.3. Delete the image file stored in the OBS bucket. For details, see the Object Storage

    Service User Guide.

    Image Management ServiceUser Guide 2 Getting Started

    Issue 13 (2017-08-30) 36

    http://www.mellanox.com/

  • 3 Management3.1 Modifying Image Attributes

    ScenariosYou can only modify private images that are in Normal or Normal (Uninitialized) state. Youcan modify the name, description, and status of a private image.

    ProcedureYou can modify the name and description of a private image using either of the followingmethods:

    Method 1:

    1. Log in to the management console.2. Under Computing, click Image Management Service.3. Click Private Image to display the image list.4. Locate the row that contains the image and click Modify in the Operation column.5. Modify the image name and description.

    Method 2:

    1. Log in to the management console.2. Under Computing, click Image Management Service.3. Click Private Image to display the image list.

    4. In the image list on the Private Image page, locate the row that contains the image, click

    on the left of the row, and click the modification icon highlighted in Figure 3-1.

    Image Management ServiceUser Guide 3 Management

    Issue 13 (2017-08-30) 37

  • Figure 3-1 Modifying attributes of an image

    You can change the image status based on whether initial configuration has been performedfor the image.

    1. Log in to the management console.2. Under Computing, click Image Management Service.3. Click Private Image to display the image list.4. Locate the row that contains the image and click Modify in the Operation column.5. Check whether initial configuration has been performed for the image.

    – If yes, select Initial configuration has been performed for this image. andchange the image status to Normal.

    – If no, deselect Initial configuration has been performed for this image. andchange the image status to Normal (Uninitialized).

    For how to perform initial configuration for an image, see What Initial ConfigurationNeeds to Be Performed for an External Image File Used to Create a PrivateImage?.

    6. Click OK.

    3.2 Creating an ECS Using an Image

    ScenariosYou can use a private or public image to create an ECS.

    The difference is as follows:

    l If you use a public image to create an ECS, the ECS contains only the OS and pre-installed public applications. You will need to install your private applications ifrequired.

    l If you use a private image to create an ECS, the ECS contains the OS, pre-installedpublic applications, and your private applications.

    Procedure1. Log in to the management console.2. Under Computing, click Image Management Service.3. Click Public Image or Private Image to display the image list.4. Locate the row that contains the target image and click Apply for ECS in the Operation

    column.

    Image Management ServiceUser Guide 3 Management

    Issue 13 (2017-08-30) 38

    http://support.hwclouds.com/en-us/ims_faq/ims_faq_0022.htmlhttp://support.hwclouds.com/en-us/ims_faq/ims_faq_0022.htmlhttp://support.hwclouds.com/en-us/ims_faq/ims_faq_0022.html

  • For how to create an ECS, see the Elastic Cloud Server User Guide.

    3.3 Deleting an Image

    Scenarios

    Delete an image if it is unneeded.

    You can delete only private images that are in the Normal or Normal (Uninitialized) state,and that are Not Released.

    Procedure1. Log in to the management console.

    2. Under Computing, click Image Management Service.

    3. Click Private Image to display the image list.

    To view the status of an image, click on the right of the row that contains the image.

    – To delete a single image, go to 4.

    – To delete images in batches, go to 5.

    4. Locate the row that contains the image, click More in the Operation column and selectDelete. Go to 7.

    5. Select the image you are to delete on the image list.

    6. Click Delete on top of the image list.

    7. Click OK.

    3.4 Sharing an Image

    3.4.1 Overview

    Application ScenariosNOTE

    A project is used for grouping and isolating computing, storage, and network resources of FusionSphereOpenStack. A project can be a department or a project team. Multiple projects can be created for anaccount.

    You can use the image sharing function to share your private images with other users on thepublic cloud platform.

    If you are a DeC or multi-project user, the image sharing function allows you to use imagesconveniently in multiple projects in the same region.

    The image provider can share specified images, cancel sharing images, and add or deletetenants with whom they share images. The recipient can choose to accept or refuse imagesshared by other users, and can remove the images they have accepted.

    Image Management ServiceUser Guide 3 Management

    Issue 13 (2017-08-30) 39

  • ProcedureUser A (image provider) shares a private image with user B (image recipient). The procedureis as follows:

    1. User B sends the account name to user A. If user B is a DeC or multi-project user, user Bmust also provide the project name.

    2. User A shares an image with user B.3. User B accepts the shared image.

    User B uses the image shared by user A to perform operations, such as creating ECSs.

    Restrictions and Limitations1. Users can only share private images that have not been published as market images.2. A user can only share images with other users within the same region.3. An image can be shared with 128 users at most.4. You can cancel image sharing anytime without notifying the user with whom you share

    an image.5. You can delete the shared image anytime without notifying the user with whom you

    share an image.6. An encrypted image cannot be shared.

    3.4.2 Obtaining the Account Name and Project Name

    ScenariosBefore user A shares an image with user B, user B needs to provide the account name to userA. If user B is a DeC or multi-project user, user B also needs to provide the project name.This section describes how to obtain the account name and project name.

    Procedure1. User B logs in to the management console.

    2. Click the username in the upper right corner and select My Credential from the drop-down list.On the My Credential page, view the account name and project name in the projectlist. .

    Figure 3-2 Viewing the account name and project name

    Image Management ServiceUser Guide 3 Management

    Issue 13 (2017-08-30) 40

  • 3.4.3 Sharing Specified Images

    Scenarios

    If user A wants to share a private image with user B, user A needs to obtain user B's accountname (if user B is a DeC user or multi-project user, user A needs to obtain the account nameand project name of user B). A user can share a single image or share images in batches basedon your requirements.

    Prerequisites

    User A has obtained user B's account name (If user B is a DeC user or multi-project user, userA has obtained the account name and project name of user B).

    Procedure1. User A logs in to the management console.

    1. Under Computing, click Image Management Service.2. On the Image Mgmt Service page, click the Private Image tab to switch to the page

    that displays all private images.3. Determine the next step based on how many images you are to share:

    – To share images in batches, go to 4.– To share a single image, go to 6.

    4. Select the private images to share, click Share on top of the image list.

    Figure 3-3 Sharing images in batches

    5. In the Share Image window, enter user B's account name and click Add. If user B is aDeC or multi-project user, you also need to select user B's project name. Go to 8.

    6. Locate the row that contains the private image you are to share, click More in theOperation column and select Share.

    7. In the Share Image window, enter user B's account name and click Add. If user B is aDeC or multi-project user, you also need to select user B's project name.

    8. To add multiple image recipients, enter the account names and project names of theserecipients.

    9. Click OK.

    3.4.4 Accepting or Refusing Shared Images

    Scenarios

    After user A shares specified images, user B will receive a message. User B can choose toaccept or refuse all or part of the shared images. User B can only use accepted images.

    Image Management ServiceUser Guide 3 Management

    Issue 13 (2017-08-30) 41

  • PrerequisitesUser A has shared specified images.

    Procedure1. User B logs in to the management console.

    1. Under Computing, click Image Management Service.2. On the Image Mgmt Service page, click the Shared Image tab to switch to the page

    that displays all private images.A message is displayed on top of the image list inquiring whether user B wants to acceptthe shared images. Figure 3-4 shows the message page.

    Figure 3-4 Message asking whether to accept the shared images

    – To refuse all shared images, click Refuse All.– To accept the shared images or refuse part of the shared images, click View details

    and then go to 3.3. Accept the shared images or refuse part of the shared images.

    – To accept the shared images, select the images on the Shared