Modified 404 error response for server actions

User-friendly messages are returned if any server action
is requested on non-existent servers

Fixes bug 1050922

Change-Id: I884285fcb62225acd9078d16191398d844a227cb
Inherit the base images qcow2 properties

When creating an image based off a base image we
likely want to ensure that we are inheriting some
of that bases properties. This includes items
like cluster_size and encryption for now. Likely
it is not intended for those to differ in a child
image.

Blueprint backing-file-options

Change-Id: I0d684ca9825a3d9c4310e4a6d4279f10331d210e
Replace builtin hash with MD5 to solve 32/64-bit issues.

It seems that Python's builtin hash returns different
values on 32-bit and 64-bit architectures, so it's
safer to use a well-defined hash like MD5.

bug 1050359

Change-Id: Ibb49f7b9028085d2aedaf05b94e1e1dcdf5e4cb4
Adds API sample testing for rescue API extension

Adds tests and templates for testing of the server rescue
API extension. Tests both json and XML API functionality.

Change-Id: Icb241e96ebedde0b6385f8ba60eebd0e768f22da
Raise NotFound for non-existent volume snapshot create

When user tries to create snapshot of a non-existent volume then
handle the VolumeNotFound exception raised during snapshot creation
and throw it as HTTPNotFound

Fixes bug 1050388

Change-Id: I869ed6a29f66889636bcf92115117d407079e539
Restore SIGPIPE default action for subprocesses

Python ignores SIGPIPE on startup, because it prefers to check every
write and raise an IOError exception rather than taking the signal. Most
Unix subprocesses don't expect to work this way. This patch (adapted
from Colin Watson's post at http://tinyurl.com/2a7mzh5) sets SIGPIPE
back to the default action for nova.utils.execute and nova-rootwrap
created subprocesses.

Fixes bug 1053364

Change-Id: I17e1629bb4ef4268515c6734ddb6e12746739c52
Fix solidfire option declaration

Fixes bug #1053427

The sf_allow_tenant_qos option is a boolean, not a string.

Change-Id: I7d1e8c7e8f545710314395c91e269f08cc110c36
Fix startup with DELETED instances

Make sure that compute manager with DELETED and SOFT_DELETED instances
starts up properly. Before it was possible to end up with only the db
entry and no local configuration allowing a successful restart (even
then it would be the wrong decision to try).

Fixes bug 1053441

Change-Id: Iab1ca81068733a5e8546c32ad122f1d60d22310b
Use test.TestingException instead of duplicating it

As much as like the name, it's not really necessary to duplicate
test.TestingException

Change-Id: Ieaca2b57a7cad58e86d2f92d4555fe26538ec47d
Re-generate sample config file

Changes include:

  - recent resource tracker changes moved around options and added
    new options like disk_allocation_ratio
  - new send_arp_for_ha_count option
  - qpid_heartbeat default increased
  - volume_tmp_dir added by image cloning support
  - netapp_nfs and solidfire volume driver additions

DocImpact: update nova.conf docs
Change-Id: I4b53e4c51a40de1321f70a2bed16ac7020a2f160
Recreate nw_info after auto assigning floating ip.

When auto assigning floating IPs recreate the nw_info array
so that API calls to get instance details will immediately
display the assigned floating IP info.

Fixes LP Bug #1053479.

Change-Id: Ia58a5391099317479d968fcf01682229926a4a99
Merge "Restore SIGPIPE default action for subprocesses"
Merge "Adds API sample testing for rescue API extension"
Merge "Replace builtin hash with MD5 to solve 32/64-bit issues."
Merge "Use test.TestingException instead of duplicating it"
Merge "Fix solidfire option declaration"
Stop double logging to the console

The code in nova for logging added an extra root handler to be
able to log messages to the console during log setup. This handler
was removed in the setup method. The common setup method no longer
removes this handler, so don't create it. Note that there may be
a small period before the logging setup is finished where messages
will not appear.

Fixes bug 1053512

Change-Id: I879360ecd60d607112b1210d7afd5860e9ccb295
Fix solidfire unit tests

A couple of tests attempted to reimplement assertRaises(), but did so
badly. self.fail() will raise AssertionError, which is a subclass of
Exception, so even if the tested exception wasn't raised, it would
silently treat it as a success.

This buggy testing code hid a failure to properly test the intended
functionality in test_delete_volume_fails_no_volume.

Change-Id: I4e31bf6cb3b042aa2d9ba2a5ccaf40319d0fc124
Merge "Raise NotFound for non-existent volume snapshot create"
Merge "Inherit the base images qcow2 properties"