Fast Import of an Image File in Linux

Scenarios

Prerequisites

• The image file has been initially configured as instructed in Table 2 based on the OS 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.

Procedure

1. Upload an image file.
   • If the image file is uploaded from a Linux PC, run the scp command.

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

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

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

   • If the image file is uploaded from a Windows PC, use a file transfer tool, such as WinSCP, to upload the image file.

2. Obtain the image conversion tool (qemu-img-hw.zip) and bitmap file generation tool (createMF.zip), upload them to the ECS, and decompress the packages.

   Table 1 Tool packages

   Tool Package	How to Obtain
   qemu-img-hw.zip	https://ecs-instance-driver.obs.ru-moscow-1.hc.sbercloud.ru/qemu-img-hw.zip
   createMF.zip	https://ecs-instance-driver.obs.ru-moscow-1.hc.sbercloud.ru/createMF.zip

3. Use qemu-img-hw to convert the image format.
   1. Go to the directory where qemu-img-hw is stored, for example, /usr/qemu-img-hw.

      cd /usr/qemu-img-hw

   2. Run the following command to make qemu-img-hw executable:

      chmod +x qemu-img-hw

   3. Execute qemu-img-hw to convert the image file format to ZVHD2 (recommended) or RAW.

      Command format:

      ./qemu-img-hw convert -p -O Target_image_format Source_image_file Target_image_file

      For example, run the following command to convert an image01.qcow2 file to an image01.zvhd2 file:

      ./qemu-img-hw convert -p -O zvhd2 image01.qcow2 image01.zvhd2

      • If the image file is converted to the ZVHD2 format, go to 5.
      • If the image file is converted to the RAW format, go to 4.

4. Use CreateMF.jar to generate a bitmap file.
   1. Ensure that JDK has been installed on the ECS.

      Run the following commands to check whether JDK is installed:

      source /etc/profile

      java -version

      If a Java version is displayed, JDK has been installed.

   2. Run the following command to enter the directory where CreateMF.jar is stored:

      cd /usr/createMF

   3. Run the following command to generate a bitmap file:

      java -jar CreateMF.jar /Original RAW file path/Generated .mf file path

      Example:

      java -jar CreateMF.jar image01.raw image01.mf

      Caution

      • The generated .mf bitmap file must have the same prefix as the RAW image file. For example, if the image file name is image01.raw, the generated bitmap file name is image01.mf.

5. Use s3cmd to upload the file(s) to an OBS bucket.
   1. Install s3cmd on the ECS.

      If s3cmd has been installed, skip this step.

      1. Run the following command to install setuptools:

         yum install python-setuptools

      2. Run the following command to install wget:

         yum install wget

      3. Run the following commands to obtain the s3cmd software package:

         wget https://github.com/s3tools/s3cmd/archive/master.zip

         mv master.zip s3cmd-master.zip

      4. Run the following commands to install s3cmd:

         unzip s3cmd-master.zip

         cd s3cmd-master

         python setup.py install

   2. Configure s3cmd.

      Run the following command to configure s3cmd:

      s3cmd --configure
      Access Key: Enter an AK.
      Secret Key: Enter an SK.
      Default Region: Enter the region where the bucket is located.
      S3 Endpoint: Refer to the OBS endpoint.
      DNS-style bucket+hostname:port template for accessing a bucket: Enter a server address with a bucket name, for example, mybucket.obs.myclouds.com.
      Encryption password: Press Enter.
      Path to GPG program: Press Enter.
      Use HTTPS protocol: Specifies whether to use HTTPS. The value can be Yes or No.
      HTTP Proxy server name: Specifies the proxy address used to connect the cloud from an external network. (If you do not need it, press Enter.)
      HTTP Proxy server port: Specifies the proxy port used to connect to the cloud from an external network (If you do not need it, press Enter.)
      Test access with supplied credentials? y
      (If "Success. Your access key and secret key worked fine :-)" is displayed, the connection is successful.)
      Save settings? y (Specifies whether to save the configurations. If you enter y, the configuration will be saved.)
      
      

      Note

      The configurations will be stored in /root/.s3cfg. If you want to modify these configurations, run the s3cmd --configure command to configure the parameters or run the vi .s3cfg command to edit the .s3cfg file.

   3. Run the following command to upload the ZVHD2 image file (or the RAW image file and its bitmap file) to an OBS bucket.

      s3cmd put image01.zvhd2 s3://mybucket/

      Caution

      The .mf bitmap file must be in the same OBS bucket as the RAW image file.

6. Register a private image.

   You can register a private image using the converted ZVHD2 or RAW file on the console or using an API.

   Method 1: Register a private image on the console.

   1. Log in to the management console.
      1. 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.
   5. Select Enable Fast Create, and select the sentence following Image File Preparation.
   6. Set parameters as prompted.

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

      Caution

      • 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

   Method 2: Register a private image using an API.

   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.

Appendix 1: Common qemu-img-hw Commands

• Converting image file formats: qemu-img-hw convert -p -O Target_image_format Source_image__file Target_image_file

  The parameters are described as follows:

  -p: indicates the conversion progress.

  The part following -O (which must be in upper case) consists of the target image format, source image file, and target image file.

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

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

• Querying image file information: qemu-img-hw info Source image file

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

• Viewing help information: qemu-img-hw -help

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

• Symptom:

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

  ./qemu-img-hw: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./qemu-img-hw)
  
  

  Solution:

  Run the strings /lib64/libc.so.6 | grep glibc command to check the glibc version. If the version is too early, install the latest version. Run the following commands in sequence:

  wget http://ftp.gnu.org/gnu/glibc/glibc-2.15.tar.gz

  wget http://ftp.gnu.org/gnu/glibc/glibc-ports-2.15.tar.gz

  tar -xvf glibc-2.15.tar.gz

  tar -xvf glibc-ports-2.15.tar.gz

  mv glibc-ports-2.15 glibc-2.15/ports

  mkdir glibc-build-2.15

  cd glibc-build-2.15

  ../glibc-2.15/configure --prefix=/usr --disable-profile --enable-add-ons --with-headers=/usr/include --with-binutils=/usr/bin

  Note

  If configure: error: no acceptable C compiler found in $PATH is displayed, run the yum -y install gcc command.

  make

  make install

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

• Symptom:

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

  ./qemu-img-hu: error while loading shared libraries: libcrypto.so.10: cannot open shared object file: No such file or directory
  
  

  Solution: Run openssl version to check whether the OpenSSL version is later than 1.0. If yes, install OpenSSL 1.0.

  Run the following commands to install OpenSSL 1.0:

  wget https://github.com/openssl/openssl/releases/download/OpenSSL_1_0_2k/openssl-1.0.2k.tar.gz

  tar -xvf openssl-1.0.2k.tar.gz

  cd openssl-1.0.2k

  ./config -d shared --prefix=/tmp/openssl (custom installation directory)

  make

  make install

  cp /tmp/openssl/lib/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.10

  Delete the /usr/lib64/libcrypto.so.10 file if you do not need it any longer.