Imported Translations from Transifex

Change-Id: I1fffca39a7dc7a5832f0be0505bbadad9a194f48
Merge "Fix to disallow server name with all blank spaces"
Merge "Refactors qemu image info parsing logic"
Merge "Don't make nova-compute depend on iSCSI"
Merge "Fix bad vm_state change in reboot_instance()"
Merge "Quantum API _get_floating_ip_by_address mismatch with Nova-Net"
Merge "Some libvirt driver lookups lacks proper exception handling"
Merge "Replace functions in utils with oslo.fileutils"
Merge "Imported Translations from Transifex"
Fix the ServerPasswordController class doc string

The code must have been copied from the flavor access extension to start
with and the old class doc string was left in place.

Fixes bug 1191232

Change-Id: Ie60ea629270c8185abc05fd4e08bbd7a9945c2b5
Initial scheduler support for instance_groups

Scheduler support for blueprint instance-group-api-extension

The patch set adds the following:
1. conductor support for getting instances via the instance_group uuid
2. conductor support for removing an instance from the instance_group
   members

In addition to this it replaces the 'group' hint with 'instance_group'.

DocImpact

Change-Id: I4a4febc2e85d4ffc8b1579d2673fa107171a3c5b
Merge "Remove unused db api call."
Allow reboot or rebuild from vm_state=Error

In general most operations are only valid on an
instance that has booted successfully at least once
so this change extends the instance state check
logic to include evidence that the instance has
been successfully started at least once.

This enables more operations to be allowed in
against instances in an Error state.  For example
reboot and rebuild are useful recover options for
an instance which has reached an error state, but
not if the instance failed during its initial build.

With this change the only actions allowed on an
instance which has never booted successfully are
delete and force_delete.  Soft delete is not
allowed, as the restore is in effect a start unless
there is specific virt driver support.

In addition the following actions are now allowed
against instances in an Error state providing the
instance has booted at least once:  Reboot, Rebuild,
and Rescue.

Fixes bug:   1183946

Change-Id: I63fd8d2a182df5cf12754892e8076933b3b1e79f
libvirt fix resize/migrates with swap or ephemeral

Fixes bug 1191608

The code was not properly guarding against backing files not
existing with QCOW2 images. As such, get_disk_backing_file() would
return None, then the subsequent call to basename() on None would
cause an exception.

This bug was introduced with the fix for bug 1185588 and commit
6e768363.

Change-Id: I4b1237ddf01b9398bfdc141180260136b36cae5a
Port fping extension to v3 API Part 1

This changeset only copies the v2 files (implementation and test)
into the appropriate v3 directories unchanged. The copy as-is
will not be loaded by either the v2 or v3 extension loaders. The
second changeset will then make the changes required for it to
work as a v3 extension.

This is being done in order to make reviewing of extension porting
easier as gerrit will display only what is actually changed for v3
rather than entirely new files

Partially implements blueprint nova-v3-api

Change-Id: I55d15ab5f9f59a83dc67bac2d2f41ceee06085d5
Add old display name to update notification

Add old display name to payload of update notification when it is
changed, so the notification consumer could know the display name is
changed which is the same as task_state.
Fixes bug 1191612

Change-Id: I47b8ad8ffc2988212b59fb141e83b8110994b8da
Port server_diagnostics extension to v3 API Part1

This changeset only copies the v2 files (implementation and test)
into the appropriate v3 directories unchanged. The copy as-is
will not be loaded by either the v2 or v3 extension loaders. The
second changeset will then make the changes required for it to
work as a v3 extension.

This is being done in order to make reviewing of extension porting
easier as gerrit will display only what is actually changed for v3
rather than entirely new files

Implements blueprint nova-v3-api

Change-Id: I52f906948b5873cf3fdfff14270c7384ee5e7b9f
Don't deallocate network if destroy time out

Fixes bug #1169057
Sames as bug 1180178, if libvirt returns time out error during destroy
an instance, we also can't deallocate the network of the instance,
otherwise the fixed ip of it may be re-used by another new instance,
and resulted in the new instance can't be accessed by the fixed ip.

Change-Id: I04dfd21bb1b7168abc71f39e836126a11dad6d8d
Add missing tests for nova.db.api.instance_metadata_*

blueprint db-api-tests

Change-Id: Ied09a4aacd3709cd4e63f939df3b812c6ad2533e
Add missing tests for cell_* methods

There was no tests in test_db_api for cell_*
methods.
Also small fix CellNotFound exception.
Add tests to ensure that all works.

blueprint db-api-tests

Change-Id: I63f3a449238f870fe2549ea5c008b636104e5002