Table of contents: <<TableOfContents()>>
This blueprint defines a set of solutions to ensure that an instance creation is as fast as possible within a given XenServer. Once an image has been streamed to a given XenServer host, reuse the local image for subsequent instances rather than re-streaming them.
On a XenServer host, nova-compute gets the image from glance for instance creation. There will be local copies of an image on a given XenServer if multiple instance (of one image) are created on it. We can avoid streaming the image and creating local copies by re-using the images that have already been streamed to a given XenServer host. This can be achieved by using the copy on write feature provided by XenServer. Copy on write allows an image to be cloned and re-used. Cloning of a disk is almost instantaneous and avoids the overhead of the time spend re-streaming the image.
- When an instance create request is placed, nova-compute searches the local cache for the image. The search is done based on the image-id. If the image is not present it is streamed from glance and the instance is created.
- When an instance create request is placed, nova-compute searches the local cache for the image. The search is done based on the image-id. If the image is present the instance is created from it.
- Openstack on Xenserver host will use copy on write by default.
- If it is the first time that an instance of an image is being created on a given Xenserver, stream the image from glance.
- If the image is already present on a given Xenserver host, clone that image and use the cloned image to create a new instance.
- "use_cow_images" flag must be used to identify whether an existing image should be cloned or a new one streamed from glance.
- If the copy on write option is turned off, we'll stream the image from glance.
- Functionality would be supported on Local SR of type Ext. Support for other SR's will be added later. LVM and LVHD based Local SRs will not support fast cloning.
- There are two ways to set up the Local storage SR. One is called "LVHD" and involves putting VHD files inside LVM volumes on the local disk. The other is called "ext" and involves putting VHD files inside an ext3 filesystem on the local disk instead.
- Most of Xenserver storage types support thin provisioning. When we want to stream from glance to start a VM, we need to know which disks are already present, and which need to be streamed. Having the VHD files easily visible inside Dom0 makes it very easy to check which disks have been streamed and which ones haven't. This is why we have choosen to use ext. The advantage of ext is that the VHD file is easily visible inside Dom.
- To identify whether an image has already been streamed to a given Xenserver host, "image id" will be stored in the other-config parameter field. If copy on write is to be used, existing vhds will be listed and checked if there is one present with the given image id. If present a new vhd will be cloned and used for creating the new instance.
- If "use_cow_images" is given as false, but the image has already been streamed to the Xenserver host and is available, we'll copy that image (not clone) and use it while spawning a new instance.
- For Local SR of type LVM (or LVHD), vhd file tracking will not be possible. Copy on write will not be supported on them. If the "use_cow_images" flag is set to 'true', it'll be ignored and an instance will be created by making a copy of the image.