Importing image templates (OpenStack only)

Using IBM® Cloud Manager with OpenStack, you can import image templates to an OpenStack cloud.

Before you begin

The supported network adapters are:
For VMware images:
VirtualE1000, VirtualE1000e, VirtualPCNet32, VirtualSriovEthernetCard, VirtualVmxnet, and VirtualVmxnet3
For KVM images:
virtio, ne2k_pci, pcnet, rtl8139, e1000, e1000e, netfront, and spapr_vlan

About this task

You can use existing OpenStack compatible image templates. For more information about creating OpenStack compatible image templates, see Create image templates manually in the OpenStack documentation.

Notes:
  • The imported image template file is stored in the OpenStack cloud and not in the IBM Cloud Manager with OpenStack database.
  • An image template with the VMDK disk format must have its disk that is contained in a single VMDK file.
  • IBM Cloud Manager with OpenStack does not support directly deploying image templates with the AKI and ARI disk formats. Such image templates are deployed with an AMI disk formatted image template. As a result, image templates with the AKI and ARI disk formats have an Undeployable state in IBM Cloud Manager with OpenStack.
  • IBM Cloud Manager with OpenStack does not support importing image templates for deployment to PowerVC. Only the PowerVC image templates that were synchronized into the OpenStack cloud and made available to IBM Cloud Manager with OpenStack can be deployed to PowerVC. For information about working with PowerVC image templates, see the IBM Power® Virtualization Center Standard information center:

    http://www.ibm.com/support/knowledgecenter/SSXK2N_1.2.1/com.ibm.powervc.standard.help.doc/powervc_image_hmc.html.

Procedure

  1. Update the cloud, project, image template name, disk format, and container format for the image template being imported.
    Note: When the AMI disk format is selected, you can select the associated AKI (kernel image) and ARI (ramdisk image) disk formatted image templates. If these image templates have not been imported, then you can edit these image template properties later.
  2. Update the hypervisor type for the image template being imported. The hypervisor type might have a default value set based on the disk format selected. If the image template does not have a specific hypervisor type requirement, then select the “Not Specified” option. If a specific hypervisor type is selected and there is no hypervisor in the OpenStack cloud that has a matching type, the image template is not deployable.
  3. Optional: If the image template has a minimum memory or storage size requirement, update the minimum memory (MB) and minimum storage (GB) fields.
    Note: By default, OpenStack uses the size of the image template as the minimum storage size requirement when deploying the image template. This default is often sufficient. However, if the image template uses a compressed disk format, such as QCOW2, then the minimum storage size requirement should be set to the decompressed image template size.
  4. Optional: If the image template has specific OpenStack architecture requirements, update the architecture fields.

Results

Note: When you upload an image template file using some older browser versions, space for the image template file is required in the server temp directory. This temporary file is deleted when the upload completes. If the upload does not complete successfully, it is possible that the temporary file is not deleted automatically. If you must use an older browser, place the image template file in a location where it can be imported using a URL.

After the image template is successfully imported, you can edit a subset of the image template properties. For more information on editing OpenStack image template properties, see liaca_editing_image_properties_OS.dita.

If an image template is not deployable after it is imported, check the log entries for the image template for more information. You might must modify the image template properties to make the image template deployable.