Clarify risks of not using shared storage

Make it clearer what the risks of not using shared storage are.
Information is based on:

  http://docs.openstack.org/user-guide-admin/cli_nova_evacuate.html

which says "The command rebuilds the instance from the original image or
volume" but later says that "To preserve the user disk data on the
evacuated server, deploy Compute with a shared file system" and then use
--on-shared-storage.

Change-Id: I09600414eb0d7fff1cf301b11b3fa9a76fc08c77
This commit is contained in:
Adam Spiers 2016-03-25 13:13:05 +00:00
parent 734f5f4e60
commit 5ecafd666f
2 changed files with 6 additions and 2 deletions

View File

@ -120,7 +120,9 @@ This option should be used with caution.
<parameter name="no_shared_storage" unique="0" required="0">
<longdesc lang="en">
Disable shared storage recovery for instances. Use at your own risk!
Disable shared storage recovery for instances. This will cause instances
on dead hypervisors to be rebuilt from their original image or volume,
so anything on ephemeral storage will be lost.
</longdesc>
<shortdesc lang="en">Disable shared storage recovery for instances</shortdesc>
<content type="boolean" default="0" />

View File

@ -120,7 +120,9 @@ This option should be used with caution.
<parameter name="no_shared_storage" unique="0" required="0">
<longdesc lang="en">
Disable shared storage recovery for instances. Use at your own risk!
Disable shared storage recovery for instances. This will cause instances
on dead hypervisors to be rebuilt from their original image or volume,
so anything on ephemeral storage will be lost.
</longdesc>
<shortdesc lang="en">Disable shared storage recovery for instances</shortdesc>
<content type="boolean" default="0" />