openstack/openstack-manuals
Code Issues Proposed changes

Add affinity/anti-affinity documentation

Browse Source 
This patch documents the affinity and anti-affinity
features in Cinder that allow admins some control
over volume scheduling.

Change-Id: I23404f5974c0e03fca7bdb0af0f8a49644258fed
Closes-Bug: #1342628
This commit is contained in:
Nate Potter 2015-10-15 14:53:09 +00:00
parent 42bc28a9fa
commit cd8356339d
2 changed files with 53 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/user-guide-admin/source/cli.rst
View File

@ -19,3 +19,4 @@ OpenStack command-line clients
cli_admin_manage_environment.rst cli_admin_manage_environment.rst
cli_set_quotas.rst cli_set_quotas.rst
analyzing-log-files-with-swift-cli.rst analyzing-log-files-with-swift-cli.rst
cli_cinder_scheduling.rst

52
doc/user-guide-admin/source/cli_cinder_scheduling.rst Normal file
View File

@ -0,0 +1,52 @@
===============================
Manage Block Storage scheduling
===============================
As an administrative user, you have some control over which volume
back end your volumes reside on. You can specify affinity or
anti-affinity between two volumes. Affinity between volumes means
that they are stored on the same back end, whereas anti-affinity
means that they are stored on different back ends.
For information on how to set up multiple back ends for Cinder,
refer to the guide for `Configuring multiple-storage back ends
<http://docs.openstack.org/admin-guide-cloud/blockstorage_multi_backend.html/>`_.
Example Usages
~~~~~~~~~~~~~~
#. Create new volume on the same back end as Volume_A:
.. code::
$ cinder create --hint same_host=Volume_A-UUID SIZE
#. Create new volume on a different back end than Volume_A:
.. code::
$ cinder create --hint different_host=Volume_A-UUID SIZE
#. Create new volume on the same back end as Volume_A and Volume_B:
..code::
$ cinder create --hint same_host=Volume_A-UUID --hint same_host=Volume_B-UUID SIZE
Or:
..code::
$ cinder create --hint same_host="[Volume_A-UUID, Volume_B-UUID]" SIZE
#. Create new volume on a different back end than both Volume_A and Volume_B:
..code::
$ cinder create --hint different_host=Volume_A-UUID --hint different_host=Volume_B-UUID SIZE
Or:
..code::
$ cinder create --hint different_host="[Volume_A-UUID, Volume_B-UUID]" SIZE