openstack/cinder
Code Issues Proposed changes
3c6c2ee656
cinder/doc/source/cli/cli-cinder-scheduling.rst
Jay S. Bryant 1423480fb6 Make doc/source directory compliant with design in spec 
The following spec defines what each project's doc/source
directory is supposed to look like:

https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html

I had not yet moved existing content to follow this design.
This patch does that, moving the devref to the
'contributor' directory.  It also moves the CLI
related documentation into the 'cli' directory.  I have
updated the autodoc generation to now create the api
documentation in 'doc/source/contributor/api'.

This patch also creates a template for future documentation
contribution.  I have created all of the directories
recommended by the spec and have included documentation
as to what should go in each directory.

The index file is updated to point at the new locations for
existing content.

'doc/.gitignore' is updated so that it won't complain about the
automatically generated 'doc/contributor/api' directory.

Change-Id: I55c50fa0b7c1d06c91e40dbcfd11b1c8e8378aa6
2017-07-19 15:59:02 -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