Docs for vm/task state transitions.

Added diagrams to RST docs that show  required vm_state / task_state
transitions for compute api operations.

(Set Sandy Walsh as author since he created the diagrams)

Change-Id: Ie6a9cd4b54321a98fea5429ee52eb781f57f31a4
fix bug 992008, we should config public interface on compute

Change-Id: I35a7d63c9613161f9fea052edf39759e4e2c6227
Remove instance Foreign Key in volumes table, replace with instance_uuid

* Remove the instance relationship and instance_id FK
* Add instance_uuuid column to volumes table
* Passed unit tests and devstack tests

Change-Id: Id598f1f1d7915d1af6bf3dd75e5819dce08aaa0f
Destroy system metadata when destroying instance

instance system_metadata was not being marked as deleted when an
instance is marked as deleted.

Fixes bug 997849

Change-Id: I876b402ca33f4574bb426615f6c467ded6908fc2
Store image properties with instance system_metadata

In implementing adding 'image_meta' to instance notifications,
this was committed:

https://review.openstack.org/#/c/7309
commit 53adfd289bf7226f1c6f59c17608e42f3083f130

However, it's buggy because an instance could have been deleted after we
built from it... and bin/instance-usage-audit uses an admin context with
which we cannot query glance.

This stores image properties with instances in nova as system_metadata
and notifications will use that data.

Fixes bug 997833

Change-Id: I50575969b5cb28adaae9a713e749dc486772c417
Provide a transition to new .info files.

Change-Id: I2fb6ef93c0652a797dba72cf75fb78baaa9c9c5a
Actually use xenapi fake setter

It was implemented (with a small bug), but never used. Also, lean on
the xenapi fake over using stubs in the migration tests to ensure we
test more code.

Change-Id: I96a7222a017302332bd6a3600fa645a74c502944
Remove unnecessary stubout_loopingcall_start

The xenapi driver no longer uses utils.LoopingCall

Change-Id: I144e5331e871570d8d22b87844ecebb63ed02697
Added img metadata validation. Fixes bug 962117.

1. Added validation for image metadata.
2. Renamed the method 'check_img_metadata_quota_limit' to
'check_img_metadata_quota_limit' since it also validates the image metadata.
3. Added unit test cases.

Change-Id: I0e9dad97c03070363d14977897701e146870e41a
Use default qemu-img cluster size in libvirt connection driver

The recommended cluster size [1] for qcow2 is 64k, which is the default
when invoking 'qemu-img create ...'.  Remove the cluster_size option
from qemu-img invocation.

[1] http://www.mail-archive.com/openstack@lists.launchpad.net/msg11371.html

V2: Fix test.

Change-Id: Iafc290720a820cb5f57ded10a2f584fdc5cd5b49
Merge "Remove instance Foreign Key in volumes table, replace with instance_uuid"
Setup logging, particularly for keystone middleware

Fixes bug 979282 and bug 988951

Change-Id: I895d00ac9648e8b3cb3ad1bf141c9bfe02ef3680
Merge "Docs for vm/task state transitions."
Merge changes I144e5331,I96a7222a

* changes:
  Remove unnecessary stubout_loopingcall_start
  Actually use xenapi fake setter
Merge "Provide a transition to new .info files."
Merge "Store image properties with instance system_metadata"
Merge "Destroy system metadata when destroying instance"
Merge "Setup logging, particularly for keystone middleware"
Merge "Use default qemu-img cluster size in libvirt connection driver"
Merge "Added img metadata validation. Fixes bug 962117."