Description:

The primary objective of this blueprint is to extend the server group (formerly known as "instance groups") APIs such that VMs can be added [1] or removed from the group [2]. At present, a VM can only be "added" to a group when it's booted and "removed" from a group when the VM is deleted. This blueprint capitalizes on the foundation already in place (i.e., namely the related affinity rules within the scheduler) and adds some small, incremental API enhancements that make server groups much more consumable from an end-user perspective.

Description:

Swap volume feature has been implemented.
* https://blueprints.launchpad.net/nova/+spec/volume-swap
* https://review.openstack.org/#/c/28995/

While the volume is swapped, no reads or writes should be lost. Given that it could take a long time to swap, provide the ability to cancel a swap volume.

This feature would expose an API to cancel a swap volume.

Link to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1031012

Description:

This Cinder RFE aims to enable two functionalities.

First, Replication between Cinders: Currently we have basic replication in a single Cinder deployment.
Second, Consistency data replication: Align CG design and volume-replication spec, one CG could support different volume-types, where the volume-type to decide which volume-replication is going to be created and added to CG.

https://bugzilla.redhat.com/show_bug.cgi?id=1258645

Description:

In order to support Hypervisor / Application clusters level, a single volume would need to be exported to multiple host. The patch that adds the multi-attach flag to volumes was merged in Cinder during the Kilo release. Nova's work to support Cinder's multi-attach capability is targeted to Liberty development cycle.

http://specs.openstack.org/openstack/cinder-specs/specs/kilo/multi-attach-volume.html

Description:

This RFE on the Cinder component would accomplish the following: Allow users to import volumes snapshot from one Cinder to another. In addition, it would provide the ability to import "non" Openstack snapshots already on a backend-device, where export snapshots should work the same way as export volumes.

http://specs.openstack.org/openstack/cinder-specs/specs/liberty/support-import-export-snapshots.html

Description:

Volume state enforcer: In order to mitigate the concurrent resource access problems in Cinder, work was done in the last cycles to refactor the concept of a lock to be a set of allowed and disallowed state transitions (instead of acquiring local filesystem locks in the manager processes) by implementing a new enforcer model.

http://specs.openstack.org/openstack/cinder-specs/specs/liberty/create-states.html

Provide a command line based tool that let's users check for split-brain scenarios

https://bugzilla.redhat.com/show_bug.cgi?id=1109690

Allow for placement of files on storage devices selectively for best performance.
For example, regularly accessed or newer files should be placed on faster disks, while less relevant data is placed on slower disks.
BZ 826758