openstack/openstack-manuals
Code Issues Proposed changes

Enabling multi-backend orphans existing cinder volumes.

Browse Source 
Upon enabling multi-backend, existing cinder volumes may no longer
be usable as the "old" default cinder host name is no longer
running. You need to convert the host name of existing volumes
to the new "host@backend" type naming.

Partial-Bug: #1437761

Change-Id: I1beb83e0117bd35eb17ece8953f204f1a26089ea
This commit is contained in:
David Medberry 2015-03-28 18:21:12 -06:00
parent 6de5986d03
commit 5f33b97fb3
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/admin-guide-cloud/blockstorage/section_multi_backend.xml
View File

@ -7,8 +7,9 @@
<title>Configure multiple-storage back ends</title> <title>Configure multiple-storage back ends</title>
<para>When you configure multiple-storage back ends, you can <para>When you configure multiple-storage back ends, you can
create several back-end storage solutions that serve the same create several back-end storage solutions that serve the same
OpenStack Compute configuration and one <systemitem class="service">cinder-volume</systemitem> OpenStack Compute configuration and one <systemitem
is launched for each back-end storage or back-end storage pool.</para> class="service">cinder-volume</systemitem> is launched for each
back-end storage or back-end storage pool.</para>
<para>In a multiple-storage back end configuration, each back end has a name <para>In a multiple-storage back end configuration, each back end has a name
(<literal>volume_backend_name</literal>). Several back (<literal>volume_backend_name</literal>). Several back
ends can have the same name. In that case, the scheduler ends can have the same name. In that case, the scheduler
@ -33,6 +34,15 @@
<para>The configuration group name is not related to the <para>The configuration group name is not related to the
<literal>volume_backend_name</literal>.</para> <literal>volume_backend_name</literal>.</para>
</note> </note>
<note>
<para>After setting the <option>enabled_backends</option> flag
on an existing cinder service, and restarting the Block Storage
services, the original <literal>host</literal>
service is replaced with a new host service. The new service
appears with a name like <literal>host@backend</literal>. Use:
<screen><prompt>$</prompt> <userinput>cinder-manage volume host --currentname <replaceable>CURRENTNAME</replaceable> --newname <replaceable>CURRENTNAME</replaceable>@<replaceable>BACKEND</replaceable></userinput></screen>
to convert current block devices to the new hostname.</para>
</note>
<para>The options for a configuration group must be defined in <para>The options for a configuration group must be defined in
the group (or default options are used). All the standard the group (or default options are used). All the standard
Block Storage configuration options Block Storage configuration options