1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
===============================
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 :ref:`multi_backend`.
Example Usages
~~~~~~~~~~~~~~
#. Create a new volume on the same back end as Volume_A:
.. code-block:: console
$ openstack volume create --hint same_host=Volume_A-UUID \
--size SIZE VOLUME_NAME
#. Create a new volume on a different back end than Volume_A:
.. code-block:: console
$ openstack volume create --hint different_host=Volume_A-UUID \
--size SIZE VOLUME_NAME
#. Create a new volume on the same back end as Volume_A and Volume_B:
.. code-block:: console
$ openstack volume create --hint same_host=Volume_A-UUID \
--hint same_host=Volume_B-UUID --size SIZE VOLUME_NAME
Or:
.. code-block:: console
$ openstack volume create --hint same_host="[Volume_A-UUID, \
Volume_B-UUID]" --size SIZE VOLUME_NAME
#. Create a new volume on a different back end than both Volume_A and
Volume_B:
.. code-block:: console
$ openstack volume create --hint different_host=Volume_A-UUID \
--hint different_host=Volume_B-UUID --size SIZE VOLUME_NAME
Or:
.. code-block:: console
$ openstack volume create --hint different_host="[Volume_A-UUID, \
Volume_B-UUID]" --size SIZE VOLUME_NAME
|
