From 334b78e2a5535d82783efb332847add0b3d0deaa Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Wed, 23 Mar 2022 11:41:50 +0900 Subject: [PATCH] doc: Rephrase customers by users As open source software, cinder itself doesn't expect any "customers" but only users. Change-Id: Ia9e3e0234a9dfd5ecf8e0d16ebe34b5a67440236 --- .../block-storage/drivers/solidfire-volume-driver.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/configuration/block-storage/drivers/solidfire-volume-driver.rst b/doc/source/configuration/block-storage/drivers/solidfire-volume-driver.rst index 1f7a80d98d4..4eb9c2f32a4 100644 --- a/doc/source/configuration/block-storage/drivers/solidfire-volume-driver.rst +++ b/doc/source/configuration/block-storage/drivers/solidfire-volume-driver.rst @@ -36,9 +36,9 @@ To configure the use of a SolidFire cluster with Block Storage, modify your The SolidFire driver creates names for volumes on the back end using the format UUID-. This works well, but there is a possibility of a - UUID collision for customers running multiple clouds against the same - cluster. In Mitaka the ability was added to eliminate the possibility of - collisions by introducing the **sf_volume_prefix** configuration variable. + UUID collision for users running multiple clouds against the same cluster. + In Mitaka the ability was added to eliminate the possibility of collisions + by introducing the **sf_volume_prefix** configuration variable. On the SolidFire cluster each volume will be labeled with the prefix, providing the ability to configure unique volume names for each cloud. The default prefix is 'UUID-'.