openstack/openstack-manuals
Code Issues Proposed changes
26cda19a35
openstack-manuals/doc/admin-guide/source/cli_cinder_scheduling.rst
Joseph Robinson 2ce5b11b1a [User Guides] Rename Admin-Guide-Cloud to Admin-Guide 
This patch changes the name of the Admin-Guide from the Cloud
Admin Guide to the Administrator guide. This affects the
filename in the repository, and references to cloud administrators
within the document texts.

1.) Changing instances of 'cloud administrator'
    to 'administrator'.

2.) Change links from '/admin-guide-cloud/' to
    '/admin-guide/' within the Admin Guide.

3.) Adjust .htaccess file.

Change-Id: I7f21a710e922981aa295afc0616de36fd819b523
Implements: blueprint user-guides-reorganised
2016-04-01 19:50:13 +09:00

1.4 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:

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

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

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

  3. Create a 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 a 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