Prevent hacking.py from crashing on unexpected import exception

If a module isn't importable due to an unexpected error during
__import__.  Ignore it, hacking.py is only a style checker.

Fix bug 1134622

Change-Id: I704b7cc9a7bd415018ae7634767b7bd9c3b7d9b2
Merge "Revert IP Address column length to 39"
Remove un-needed methods.

These methods are un-needed. Their functionality is now provided by the
HostAPI and ComputeRPCProxyAPI.

Change-Id: I771f1e4669f8b7fb779a0fec0209c3e2a899a469
Merge "Bump python-quantumclient version to 2.1.2"
Merge "Makes sure required powervm config options are set"
Merge "Add API Sample tests for Snapshots extension."
ec2 _format_security_group() accesses db when using quantum_driver

This patch fixes _format_security_group() so that it does not
access the db when using quantum. In addition, this patch implements
the querying params that were missing in get() and list() in the quantum
security group driver.

Fixes bug 1131956

Change-Id: I5ec65829301bca7e5b215d5052a18528dff76517
Adds retry on upload_vhd for xapi glance plugin

Add a retry for the xapi glance plugin to handle transient issues
when uploading the vhd.

An example issue we're seeing is a connection timeout:

['XENAPI_PLUGIN_FAILURE', 'upload_vhd', 'error',
		"(110, 'Connection timed out')"]

To work around transient issues such as a connection timeout, we
should retry based on glance_num_retries before outright failing.

Change-Id: Ice6fdd3dd39ef40e5997d69209aaafa66bff5d6e
Fixes: bug #1134493
Actually run baremetal migration tests.

The baremetal migration tests weren't being run because the test lookup
code was looking for a tests of form 'check_#' instead of 'check_###'.

Change-Id: I8f162d6493dd09b2d0cff36c40ae9acc5df1269c
BM Migration 004: Actually drop column

SQLAlchemy-migrate appears to support passing in a Column or a
column-name string into `drop_column`. In practice though, only the
column-name form actually works.

Change-Id: I1bcc28511d652df44f7168fb84c8be7dacd60cfd
Fix `with_data` handling in test-migrations.

Two issues with the existing code:

1) migrate-down wasn't respecting the `with_data` flag

2) migrate-up was not actually migrating unless `with_data` was True.
The correct behavior is to always migrate up, but only run checks when
`with_data` is set.

Change-Id: I781fa4796908bea684d4499fa9ff5e4d7a18fbd4
Suppress retries on UnexpectedTaskStateErrors

Don't try to re-schedule if an UnexpectedTaskStateError occurs during
a build.  If the instance was deleted mid-build, just catch the
exception and log a message.

Change-Id: I5e577f252ee71f310a749186060808723b676854
Merge "Migration 147: Prevent duplicate aggregate_hosts"
Imported Translations from Transifex

Change-Id: Iec7e5058224d31481ccba6944772123ac8096808
Merge "Migration 148: Fix drop table dependency order"
Don't blindly skip first migration.

The existing code would, no matter-what, skip the first migration when
running through the migrations tests. This makes the code
slightly counterintuitive (why skip the first one?), and is not very
flexible.

The reworked logic lets a migration raise a `NotImplementedError` to
signal that it doesn't support a `downgrade`. This lets the
walk-versions code treat the first-migration just like any other.

Change-Id: I19fd8ebc6075392cf9e573b8b4166291584b4a83
Merge "Actually run baremetal migration tests."
Merge "BM Migration 004: Actually drop column"
Return proper error messages while disassociating floating IP

Currently, when a floating IP is not associated with an instance, and if we try
to disassociate it, a response likes "HTTP/1.1 404 Not Found" will be returned,
it is not proper, so change it to "HTTP/1.1 422 Unprocessable Entity" with body
likes '{"computeFault": {"message": "Floating ip 172.24.4.225 is not associated
with instance a33857af-b18b-4b88-a5cc-7d84c7fd41c8.", "code": 422}}'.

Fixes bug: #1129719

Change-Id: I18194ccf59edb5eb2bcd52a65f38d5632fef95d3
Remove old commented out code in sqlalchemy models

Change-Id: I0e49d00ce8790c8498976c2bf7bcfd9b69bfb5a4