From 4bf2a1f37c17433ff37246acd0fd292aabd02d70 Mon Sep 17 00:00:00 2001
From: Jean-Philippe Evrard <jean-philippe.evrard@belnet.be>
Date: Thu, 6 Aug 2015 12:33:38 +0200
Subject: [PATCH] Cinder_volumes_containers are automatically tagged with
 is_metal

In env.d/cinder.yml there is is_metal:true.
But there was no mention of it in the documentation.
Therefore, if an user wants to use a cinder volume container with
netapp/ceph/whatever, the container will be (by default)
considered as metal.
This should be documented somewhere.

Change-Id: I65e9d0654d50d8c8825f858e89fdf4595134dddb
---
 doc/source/install-guide/configure-cinder.rst | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/doc/source/install-guide/configure-cinder.rst b/doc/source/install-guide/configure-cinder.rst
index 6edbd73af0..def6a44ddd 100644
--- a/doc/source/install-guide/configure-cinder.rst
+++ b/doc/source/install-guide/configure-cinder.rst
@@ -9,8 +9,16 @@ Configuring the Block Storage service (optional)
    configure-cinder-backup.rst
    configure-cinder-az.rst
 
-By default, the Block Storage service uses the LVM back end. To use a
-NetApp storage appliance back end, edit the
+By default, the Block Storage service uses the LVM back end. Therefore
+the container hosting the Block Storage service has to be considered
+as is_metal.
+
+If you rather use another backend (like NetApp, Ceph, etc.) in a
+container instead of bare metal, you may edit
+the ``/etc/openstack_deploy/env.d/cinder.yml`` and remove the
+``is_metal: true`` stanza under the cinder_volumes_container properties.
+
+To use a NetApp storage appliance back end, edit the
 ``/etc/openstack_deploy/openstack_user_config.yml`` file and configure
 each storage node that will use it: