From 349ba403cea1c3108eaf364c2a81f5c38592484b Mon Sep 17 00:00:00 2001 From: Andy McCrae Date: Tue, 21 Feb 2017 16:15:50 -0500 Subject: [PATCH] [Docs] Fix block storage refs in scale-environment Change-Id: I30b4f44325c91e13d670750be14ad449f2f4d01b --- .../maintenance-tasks/scale-environment.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/source/draft-operations-guide/maintenance-tasks/scale-environment.rst b/doc/source/draft-operations-guide/maintenance-tasks/scale-environment.rst index e440ef84db..e5b18f4c86 100644 --- a/doc/source/draft-operations-guide/maintenance-tasks/scale-environment.rst +++ b/doc/source/draft-operations-guide/maintenance-tasks/scale-environment.rst @@ -254,10 +254,10 @@ Having a plan in place for how you will manage these types of events is a vital part of maintaining your OpenStack environment. For a Compute host, shut down the instance on the host before -it goes down. For a Block Storage (cinder) host, shut down any instances with -volumes attached that require that mount point. Unmount the drive within -your operating system and re-mount the drive once the Block Storage -host is back online. +it goes down. For a Block Storage (cinder) host using non-redundant storage, +shut down any instances with volumes attached that require that mount point. +Unmount the drive within your operating system and re-mount the drive once the +Block Storage host is back online. Shutting down the Compute host ------------------------------ @@ -309,7 +309,7 @@ If a Compute host needs to be shut down: Shutting down the Block Storage host ------------------------------------ -If a Block Storage host needs to be shut down: +If a LVM backed Block Storage host needs to be shut down: #. Disable the ``cinder-volume`` service: