Manage images

Manage images The cloud operator assigns roles to users. Roles determine who can upload and manage images. The operator might restrict image upload and management to only cloud administrators or operators. You can upload images through the glance client or the Image service API. Besides, you can use the nova client for the image management. The latter provides mechanisms to list and delete images, set and delete image metadata, and create images of a running instance of snapshot and backup types. After you upload an image, you cannot change it. For details about image creation, see the Virtual Machine Image Guide.

filesystem_store_metadata_file =
                                            filePath

, where filePath points to a JSON file that defines the mount point for OpenStack images on your system and a unique ID. For example: [{ "id": "2d9bb53f-70ea-4066-a68b-67960eaae673", "mountpoint": "/var/lib/glance/images/" }] After you restart the Image service, you can use the following syntax to view the image's location information: $ glance --os-image-api-version 2 image-show imageID For example, using the image ID shown above, you would issue the command as follows: $ glance --os-image-api-version 2 image-show 2d9bb53f-70ea-4066-a68b-67960eaae673

Create or update an image (glance) To create an image, use glance image-create: $ glance image-create imageName To update an image by name or ID, use glance image-update: $ glance image-update imageName The following table lists the optional arguments that you can use with the create and update commands to modify image properties. For more information, refer to Image service chapter in the OpenStack Command-Line Interface Reference. --name NAME The name of the image. --disk-format DISK_FORMAT The disk format of the image. Acceptable formats are ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso. --container-format CONTAINER_FORMAT The container format of the image. Acceptable formats are ami, ari, aki, bare, and ovf. --owner TENANT_ID The tenant who should own the image. --size SIZE The size of image data, in bytes. --min-disk DISK_GB The minimum size of the disk needed to boot the image, in gigabytes. --min-ram DISK_RAM The minimum amount of RAM needed to boot the image, in megabytes. --location IMAGE_URL The URL where the data for this image resides. For example, if the image data is stored in swift, you could specify swift://account:key@example.com/container/obj. --file FILE Local file that contains the disk image to be uploaded during the update. Alternatively, you can pass images to the client through stdin. --checksum CHECKSUM Hash of image data to use for verification. --copy-from IMAGE_URL Similar to --location in usage, but indicates that the image server should immediately copy the data and store it in its configured image store. --is-public [True|False] Makes an image accessible for all the tenants (admin-only by default). --is-protected [True|False] Prevents an image from being deleted. --property KEY=VALUE Arbitrary property to associate with image. This option can be used multiple times. --purge-props Deletes all image properties that are not explicitly set in the update request. Otherwise, those properties not referenced are preserved. --human-readable Prints the image size in a human-friendly format. The following example shows the command that you would use to upload a CentOS 6.3 image in qcow2 format and configure it for public access: $ glance image-create --name centos63-image --disk-format qcow2 \ --container-format bare --is-public True --file ./centos63.qcow2 The following example shows how to update an existing image with a properties that describe the disk bus, the CD-ROM bus, and the VIF model: $ glance image-update \ --property hw_disk_bus=scsi \ --property hw_cdrom_bus=ide \ --property hw_vif_model=e1000 \ f16-x86_64-openstack-sda Currently the libvirt virtualization tool determines the disk, CD-ROM, and VIF device models based on the configured hypervisor type (libvirt_type in /etc/nova/nova.conf). For the sake of optimal performance, libvirt defaults to using virtio for both disk and VIF (NIC) models. The disadvantage of this approach is that it is not possible to run operating systems that lack virtio drivers, for example, BSD, Solaris, and older versions of Linux and Windows. If you specify a disk or CD-ROM bus model that is not supported, see . If you specify a VIF model that is not supported, the instance fails to launch. See . The valid model values depend on the libvirt_type setting, as shown in the following tables.

Disk and CD-ROM bus model values
libvirt_type setting	Supported model values
qemu or kvm	ide scsi virtio
xen	ide xen

VIF model values
libvirt_type setting	Supported model values
qemu or kvm	e1000 ne2k_pci pcnet rtl8139 virtio
xen	e1000 netfront ne2k_pci pcnet rtl8139
vmware	VirtualE1000 VirtualPCNet32 VirtualVmxnet

Troubleshoot image creation If you encounter problems in creating an image in Image service or Compute, the following information may help you troubleshoot the creation process. Ensure that the version of qemu you are using is version 0.14 or later. Earlier versions of qemu result in an unknown option -s error message in the nova-compute.log file. Examine the /var/log/nova-api.log and /var/log/nova-compute.log log files for error messages.