import_ was renamed import

Due to VMS-547, so vmsctl CLI call 'import' would be more natural

Change-Id: Ied2b99f7334a461f9a09cd3310feb5cc00406215
Fix excess bless artifacts in glance

Amends upstream merge 47edcd658df9bf9bd22f8e1ed04b286ab8bcdef8;
part of commit 93c40a2c57711028b0fdaf07aa444e03cd9054c9 was not included

Change-Id: Ic97b43a523b8ae5750de42990f31e3effec558d1
Allow cobalt-compute to run on database-less nodes

Since Grizzly there is no guarantee that cobalt-compute will have
access to the database. This removes the extraneous database calls
that would prevent cobalt-compute from running on a database-less
host.

Change-Id: I02bf86df555651e992471b9b189f8f7a454fc9ed
Import the cobalt_topic config from cobalt.nova.api

The cobalt_topic configuration value is defined in the
cobalt.nova.api module. This module was previously imported and used
by the manager, but was removed because the api accesses the database
and manager should be able to run in a no db environment. Once the
cobalt.nova.api module was removed from the manager, the cobalt_topic
configuration value was also removed.

This imports the configuration value from the cobalt.nova.api
module.

Fixes OS-218

Change-Id: Idf7ac1b4742ba476a89e06db7f4db8e5bf54a27b
Use Conductor to migrate floating ips

The network API can no longer be used directly to migrate the
instance's floating ip address because it communicates with the
database directly. Since compute nodes can be isolated from the
db cobalt-compute needs to go through the conductor API.

Fixes OS-219

Change-Id: I5a95551966435132374351aca81ef3d4c92749cf
Fix migrating a launched instance when using LVM image backends.

The instance's backend type (e.g. raw, LVM, qcow2) is preserved
during migration. In other words, if the system is configured to
use LVM backends, then the instance's back will remain LVM after
migration. In contrast, the instance's backend will always end up
as qcow2 after being launched. This different caused issues when
migrating a launched instance because migration would attempt
to keep the configured backend, LVM, for an instance backed by
qcow2.

To fix this, if there is no LVM information associated with the
instance during migration then a qcow2 backend will be used.

Fixes OS-221

Change-Id: I6d84a7bb570222ae658ff726c331e3fee80a24b3
trivial cherry pick for migration of floating IPs on quantum.

Change-Id: I4477ff864f3d1b461ad20192d80f44b7761fa456
Merge branch 'stable/grizzly' into next/grizzly

Change-Id: Iaa7b7cabd465eb160b5b02d42a0fe1a6d2be36b3