openstack-manuals/doc/user-guide-admin/source/cli_cinder_scheduling.rst
venkatamahesh d1808ed9c8 [user-guide-admin] Fix rst markups whereever required
Implements: blueprint user-guides-reorganised

Change-Id: I147cd09381789a48f361552055e01469746cb398
2015-12-18 09:38:34 +00:00

1.5 KiB

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.

Example Usages

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

    $ cinder create --hint same_host=Volume_A-UUID SIZE
  2. Create new volume on a different back end than Volume_A:

    $ cinder create --hint different_host=Volume_A-UUID SIZE
  3. Create new volume on the same back end as Volume_A and Volume_B:

    $ cinder create --hint same_host=Volume_A-UUID --hint same_host=Volume_B-UUID SIZE

    Or:

    $ cinder create --hint same_host="[Volume_A-UUID, Volume_B-UUID]" SIZE
  4. Create new volume on a different back end than both Volume_A and Volume_B:

    $ cinder create --hint different_host=Volume_A-UUID --hint different_host=Volume_B-UUID SIZE

    Or:

    $ cinder create --hint different_host="[Volume_A-UUID, Volume_B-UUID]" SIZE