v2 replication has been merged in cinder, but there is no way to call
the api methods. This patch allows the following methods to be called
in order to fully support v2 replication:
  - os-enable_replication
  - os-disable_replication
  - os-list_replication_targets
  - os-failover_replication

Change-Id: Ic3cf082916bdf089de05eebce456dff8cdc11f7c
Implements: blueprint replication-v2

This patch adds the ability to reset the state of
a backup with the command backup-reset-state.

DocImpact

Change-Id: I5851bb21c62252f61ad6a09f01859582e774a9db
Closes-Bug: #1279764

- cinder image-metadata-show volume_id
This command can be used to show the image metadata associated
with the specific volume.

Partially implements: bp support-modify-volume-image-metadata

Change-Id: I960af66038b47c1206619b99a2bb5ae561a59c4f

This change adds a new admin-api to allow admin to fetch
specified backend capabilities which includes volume stats and
vendor unique properties.
With this command, admin can obtain what the current deployed
backend in Cinder is able to do from the endpoint.

DocImpact
Implements: blueprint get-volume-type-extra-specs

Change-Id: I355a5b57994d1407a088c86530d7ef362ecd31ed

These are Cinder Client specific changes for modifying volume
and snapshot's image metadata.

- cinder image-metadata volume_id set key=value
This command can be used to create a new image metadata associated
with the volume when the key not exists, and update the value for
the existed key.

- cinder image-metadata volume_id unset key
This command can be used to delete image metadata associated
with the volume.

Depends-On: I22792ef7bd49c763d7c130aa8cac9abc3fff2d4c
Partially implements: bp support-modify-volume-image-metadata
Change-Id: I03787563cb3ea4ef96ed145a37fc665f80565a12

This modification adds support for updating volume encryption types. The
encryption-type-update command requires a single argument, the name or
ID of the volume type whose associated encryption type should be
updated, and up to four optional arguments representing new values for
the encryption type attributes. The update implementation supports three
use cases:

1. The user wants to specify new values for attributes of an
   encryption type.
   - include the attribute and its new value at invocation
2. The user wants to preserve the values for attributes of an
   encryption type.
   - exclude the attribute at invocation
3. The user wants to set the values for attributes of an encryption
   type to provider defaults (only valid for cipher and key-size).
   - include the attribute but provide no value at invocation

The encryption type may only be updated if the associated volume type is
unused.

This modification leverages update support for encryption types provided
by the cinder volume encryption type API extension. See the following
patch for more information:

https://review.openstack.org/#/c/58344/

blueprint: encrypt-cinder-volumes
https://blueprints.launchpad.net/nova/+spec/encrypt-cinder-volumes

Change-Id: I8e6a37428e76ba69a422468630fdb66b4fe460ab
DocImpact

There is a need to limit maximum size of a volume to levels
that the storage infrastructure can handle.
Setting a maximum limit on size of a volume also prevents
a tenant from creating large volumes that have not been tested
and certified to satisfy SLA objectives.

This feature allows admin to set volume size limit
[per_volume_gigabytes] for a tenant.

Change-Id: Iab584c72a34f9171000b20b2200ac12d21fc40ae
Implements: blueprint cinder-quota-define-per-volume