2 Managing Images #

1. In SUSE Studio or SUSE Studio Onsite, switch to the Configuration › Appliance tab.

2. Enable the Integrate with SUSE OpenStack Cloud/OpenStack check box.

3. On the Build tab, choose the respective appliance format. It mainly depends on the hypervisor on which you want to use the image—see Section 2.1.2, “Image Requirements Depending on Hypervisor”.

1. Make sure the virt-utils package is installed on the machine used for conversion.

2. Download the image from SUSE Studio.

3. To convert qcow2 to vhd images, use the following command:

   qemu-img convert -O vpc CURRENT_IMAGE_FILE FINAL_IMAGE_FILE.vhd

Upload a disk image using the python-openstackclient client.

Images are owned by projects and can be private (accessible to members of the particular project only) or public (accessible to members of all projects). Private images can also be explicitly shared with other projects, so that members of those projects can access the images, too. Any image uploaded to OpenStack Image will get an owner attribute. By default, ownership is set to the primary project of the user that uploads the image.

Set or modify hypervisor-specific properties with the --property key=value option. This can be done directly during image upload (as shown in the examples below). To change the properties after image upload, refer to Procedure 2.3, “Modifying Image Properties”.

1. In a shell, source the OpenStack RC file for the project that you want to upload an image to. For details, refer to http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html.

2. Upload the image using openstack image create. Find some example commands for different hypervisors below:

   • For KVM:

     openstack image create IMAGE_NAME \
       --public --container-format bare \
       --property architecture=x86_64 \
       --property hypervisor_type=kvm \
       --disk-format qcow2 \
       --file PATH_TO_IMAGE_FILE.qcow2

   • For Xen:

     openstack image create IMAGE_NAME \
       --public --container-format bare \
       --property architecture=x86_64 \
       --property hypervisor_type=xen \
       --property vm_mode=xen \
       --disk-format qcow2 \
       --file PATH_TO_IMAGE_FILE.qcow2

     

     Note: Value of vm_mode

     For Xen PV image import, use vm_mode=xen, for Xen HVM image import use vm_mode=hvm.

   • For VMware:

     openstack image create IMAGE_NAME \
       --public --container-format bare \
       --property vmware_adaptertype="lsiLogic" \
       --property vmware_disktype="preallocated" \
       --property hypervisor_type=vmware \
       --disk-format vmdk --file PATH_TO_IMAGE_FILE.vmdk

     

     Note: Value of vmware_disktype

     Depending on which disk type you use, adjust the value of vmware_disktype accordingly. For an overview of which values to use, refer to https://docs.openstack.org/nova/pike/admin/configuration/hypervisor-vmware.html, section OpenStack Image service disk type settings.

   • For Docker:

     Find an image in the Docker registry you want to use and save it locally with docker pull IMAGE_NAME, where IMAGE_NAME is the name of the image in the Docker registry. The same name needs to be used when uploading the image with the following command:

     docker save IMAGE_NAME | openstack image create \
     --public --property hypervisor_type=docker \
     --container-format=docker --disk-format=raw IMAGE_NAME

     

     Important: Docker Images Need to Run a Long-Living Process

     Docker instances will only be able to spawn successfully, when running a long-living process, for example sshd. Such a process can be configured with CMD or ENTRYPOINT in the Docker.

     Alternatively, such a process can be specified on the command line with the image property os_command_line.

     openstack image set --property os_command_line='/usr/sbin/sshd -D' \
            IMAGE_ID

   If the image upload has been successful, a message appears, displaying the ID that has been assigned to the image.

1. In a shell, source the OpenStack RC file for the project that you want to upload an image to. For details, refer to http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html.

2. If you do not know the ID or the exact name of the image whose properties you want to modify, look it up with:

   openstack image list

3. Use the openstack image set command to set the properties for architecture, hypervisor type, and virtual machine mode. In the following, find some examples with properties for different hypervisors:

   • For KVM:

     openstacke image set IMAGE_ID_OR_NAME \
       --property architecture=x86_64 \
       --property hypervisor_type=kvm

   • For Xen:

     openstack image set IMAGE_ID_OR_NAME \
       --property architecture=x86_64 \
       --property hypervisor_type=xen \
       --property vm_mode=xen

     

     Note: Value of vm_mode

     For Xen PV image import, use vm_mode=xen, for Xen HVM image import use vm_mode=hvm.

   • For VMware:

     openstack image update IMAGE_ID_OR_NAME \
       --property vmware_adaptertype="lsiLogic" \
       --property vmware_disktype="preallocated" \
       --property hypervisor_type=vmware

     

     Note: Value of vmware_disktype

     Depending on which disk type you use, adjust the value of vmware_disktype accordingly. For an overview of which values to use, refer to https://docs.openstack.org/glance/latest/admin/useful-image-properties.html, section OpenStack Image service disk type settings.

1. Install the grub2-xen package. It provides the grub.xen file required to boot para-virtualized VMs that use the Btrfs file system:

   root # zypper in grub2-x86_64-xen

2. Create a glance image with the kernel from this package. For example:

   openstack image create img-grub-xen-x64 \
    --file /usr/lib/grub2/x86_64-xen/grub.xen --public \
    --container-format bare --disk-format raw

3. Create a second image which uses Btrfs as root file system. For example:

   openstack image create img-btrfs \
     --file openSUSE-Leap-42.1-JeOS-for-XEN.x86_64.qcow2 \
     --container-format bare --disk-format qcow2

4. Update the image named img-btrfs by adding a kernel_id property to it:

   openstack image set 376c245d-24fe-41e2-8abd-655d4ed8da95 \
   --property kernel_id=72ad3069-6003-4653-86f2-b5914ce33f66

   where 376c245d-24fe-41e2-8abd-655d4ed8da95 is the ID of the image named img-btrfs and 72ad3069-6003-4653-86f2-b5914ce33f66 is the ID of the image named img-grub-xen-x64

5. Boot the image to start the instance:

   openstack server create --flavor FLAVOR --image 376c245d-24fe-41e2-8abd-655d4ed8da95

   This results in a domain XML which contains the kernel you need:

   <domain type='xen' id="2">
    <name>instance-00000003</name>
    <uuid>12b2ce2b-ba1d-4c14-847f-9476dbae7199</uuid>
    <memory unit='KiB'>524288</memory>
    <currentMemory unit='KiB'>524288</currentMemory>
    <vcpu placement='static'>1</vcpu>
    <bootloader></bootloader>
    <os>
      <type>linux</type>
      <kernel>/var/lib/nova/instances/12b2ce2b-ba1d-4c14-847f-9476dbae7199/kernel</kernel>
      <cmdline>ro root=/dev/xvda</cmdline>
    </os>