openstack/cinder
Code Issues Proposed changes
817f34ce5d
cinder/doc/source/admin/cli-cinder-scheduling.rst
Jay S. Bryant 7a6180575c Migrate Cinder Scheduling CLI documentation 
The next chapter in the Cinder documentation migration.

This change brings over the scheduling documentation from
openstack-manuals.

As with the other changes, this is just intended to make the
content accessible again.  Future patches will be proposed to
improve the content.

Change-Id: Idf0366bdf7bf1a3f5b67ea46c30bbf5d92120c3b
2017-07-08 14:06:39 -05:00

1.7 KiB
Raw Blame History

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 multi_backend.

Example Usages

  1. Create a new volume on the same back end as Volume_A:

    $ openstack volume create --hint same_host=Volume_A-UUID \
  --size SIZE VOLUME_NAME

  2. Create a new volume on a different back end than Volume_A:

    $ openstack volume create --hint different_host=Volume_A-UUID \
  --size SIZE VOLUME_NAME

  3. Create a new volume on the same back end as Volume_A and Volume_B:

    $ openstack volume create --hint same_host=Volume_A-UUID \
  --hint same_host=Volume_B-UUID --size SIZE VOLUME_NAME

    Or:

    $ openstack volume create --hint same_host="[Volume_A-UUID, \
  Volume_B-UUID]" --size SIZE VOLUME_NAME

  4. Create a new volume on a different back end than both Volume_A and Volume_B:

    $ openstack volume create --hint different_host=Volume_A-UUID \
  --hint different_host=Volume_B-UUID --size SIZE VOLUME_NAME

    Or:

    $ openstack volume create --hint different_host="[Volume_A-UUID, \
  Volume_B-UUID]" --size SIZE VOLUME_NAME