Fixed backups GET and DELETE to restrict access to the owner of backup

Fixed the db model find_by so that when a model instance is looked up and a
context is passed in, the find_by operation fails if the tenant_id in the
instance is not the same as the tenant_id in the context (except if the
tenant is an admin).

Fixed bug 1188822

Change-Id: I0374f999601fa3f2bc817901bbc428b8be219683
Merge "Fixed backups GET and DELETE to restrict access to the owner of backup"
API Validation for Trove API

    Replaced validation with new and improved json schema validation
    Fixed malformed json schema bug #1177969
    Fixed integration test for create_user; correct databases
    Fixed integration for create_users; invalid character_set param

Implements: json-schema-support

Change-Id: I6ca09803654d9e78362fde69185b5b9e05a5eb6b
Enable disk usage view in instance detail view

- support both volume and ephemeral modes

Bug #1194597

Change-Id: I407268a74d979f95969e29cf54191f92afe0c3e9
Adding instance id to the security group extension API

- Secgroup list now show their corresponding instances
- Secgroup get also show its corresponding instance

Fixes bug 1190410

Change-Id: Ifb7b1c9be741fca221267243b86ce0d91b994015
Restore should use pgrep instead of mysqladmin to check for mysql down

For a short window, while mysql is shutting down, it stops accepting
network connections but the mysqld process is still alive.

During this window mysqladmin ping reports that mysql is down and
trying to start mysql fails with:
"mysqld_safe A mysqld process already exists"

Use pgrep (during restore) instead of mysqladmin ping to check mysql
is down to fix this.

Fixes bug: 1197161

Change-Id: Id8b8e15b4b6136c8acbc3cac17691a65a1a4ed14
Merge "Enable disk usage view in instance detail view"
Merge "API Validation for Trove API"
Merge "Restore should use pgrep instead of mysqladmin to check for mysql down"