xenapi: separate disk for cinder volumes

Some kernels have lockup issues while serving cinder volumes from
file-loopback-lvm kind of cinder setup. This patch provides a way to
create an additional drive to the OpenStack VM, and use that to store
cinder volumes, thus eliminating the lockup issue. It will help when
testing XenServer. Now, you can specify devices for stack-volumes
through:

    VOLUME_BACKING_DEVICE

In case you are using CINDER_MULTI_LVM_BACKEND, you can use

    VOLUME_BACKING_DEVICE2

as well.

Xenserver:
Should you whish to use a 10 gig disk backend for your cinder volumes,
specify:

    XEN_XVDB_SIZE_GB=10
    VOLUME_BACKING_DEVICE=/dev/xvdb

Citrix is using this approach on its internal CI system to run tests
against OpenStack. This is a workaround for this bug:

  https://bugs.launchpad.net/cinder/+bug/1023755

Related to blueprint xenapi-devstack-cleanup

Change-Id: Iee633d2704185bfbf9234882654c47b850fa168a
Restore admin role to ceilometer user.

Fixes bug 1193004

The ceilometer user needs the admin role, so that the resources
(instances etc.) associated with all tenants are visible to the
ceilometer agents for metering purposes.

Change-Id: I4d8a88d2d88a11a4b408e0c68ef227ec2af2d822
Set default volume backing file size to 10G

This commit changes the default volume backing file size from 5G to
10G. This is already done in devstack-gate because on tempest runs
we would frequently go above 5G. This will mirror the change for all
devstack runs not just in the gate.

Change-Id: I7023237653a28a4bb9413540ad9ecf3dfa588b0a
Merge "Restore admin role to ceilometer user."
Merge "Set default volume backing file size to 10G"
Merge "xenapi: separate disk for cinder volumes"