Deleting incremental backup metadata after restore

The incremental backup was previously being unpacked in
/var/lib/mysql. This was mistakenly causing mysql to present this
folder as a database schema.

Change-Id: I22d5dbcf1e811d59bf19404ca884a09f87ca6bd0
Closes-Bug: #1334059
Fixed '--version' for trove processes/utilities

The trove processes (trove-manage, trove-conductor, trove-api, etc.)
returned an empty string when invoked with --version. They now return
the correct version string.

Change-Id: Ic14597e30928c753eae3090b401fbd66e042b93b
Closes-Bug: #1338767
Fix updated timestamp for SecurityGroup model

Reasons:
 - Security group "updated" timestamp is not being
   updated when new rule appears. It still the same as "created".
 - Security group "updated" timestamp is not being
   updated when rule is being deleted.

Changes:
 - adding `save` step after security group rules creation.
 - adding `save` step after security group rules deletion.
 - adding integration test that validates that timestamp
   was changed after creation and deletion.

Change-Id: I92ee7207366511cd4bc5dff07337031faeed0182
Closes-Bug: #1325967
Add instance IP to /instances

This new response will be used by Horizon instead of the 1+N calls
Horizon makes today in order to render IPs in the instances list

Change-Id: Ice8f07cdaf873034dc7dc8840fcc403b4756ac12
Closes-Bug: #1339400
Change default for update_status_on_fail

Default 'update_status_on_fail' to True so that instances do not get stuck
in the BUILD state.

When this option is set, instances that remain in BUILD for longer than
the datastore's configured 'usage_timeout' will be considered failed and
moved to the ERROR state.

Closes-Bug: 1339826
Change-Id: I5f4b734830a21a1fbb6f169edb5424bac6f883cd
Enable trove to specify cinder volume_type when creating a volume

The volume_type is configurable via the trove-taskmanager.conf.
By default the volume_type is None.

Change-Id: I23dab1a6223803b03f2857842150cf1433af6ad0
Implements: blueprint cinder-volume-type
Merge "Deleting incremental backup metadata after restore"
Stop cassandra during configuration and volume migration

The cassandra service is left running after installation.
The next operation(s) are to rewrite the configuration, and
migrate the data onto a volume (if provided). It is not a
good thing for the database to be running during the latter,
and a restart is required after the former.

Failing to stop the database during the data migration can
result in an rsync error 24 because files that were present
when rsync made its list may be missing by the time rsync
gets around to trying to sync that file. This can lead rsync
to not make a 'true' copy of the source on the destination.

The only way around this is to stop the database, something
that is already done by both MongoDB and MySQL in their
guest agents.

Change-Id: I74ecc5c12d43eccc6295488e344bc0e75fe8116d
Closes-bug: #1338660
Imported Translations from Transifex

Change-Id: I11a18399496420a1b760de0b93af80aa38b8eec0
Merge "Fix updated timestamp for SecurityGroup model"
Merge "Imported Translations from Transifex"
Merge "Enable trove to specify cinder volume_type when creating a volume"
Remove setuptools_git requirement

PBR replaces what this does.

Change-Id: Id523888a65a31a7e7a31a4edc4602c9c2600b000
Merge "Change default for update_status_on_fail"
Merge "Fixed '--version' for trove processes/utilities"
Merge "Add instance IP to /instances"
Merge "Stop cassandra during configuration and volume migration"
Merge "Remove setuptools_git requirement"
Add instance metadata functionality to trove

Implements: blueprint trove-metadata

Change-Id: I1925b58b0ead307babe57d0ee28dcb5449fd6ce5
Rename sqlalchemy migration file