As we know, those are just defaults, mostly chosen by replicating the
only behavior we supported before allowing customization. They may need
changes, to work in specific environments (which is why we introduced
them in the first place).

This tries to address issue 83, which was caused by the default
parameters not being correct for the target cluster.

Signed-off-by: Guido Trotter <[email protected]>
---
Again, this is ok on devel-2.1 as well, but since there's no code change,
stable- might do. Let me know which one you prefer.

 doc/install.rst |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)

diff --git a/doc/install.rst b/doc/install.rst
index f8a0221..5b6f7f0 100644
--- a/doc/install.rst
+++ b/doc/install.rst
@@ -549,6 +549,16 @@ pass ``--enabled-hypervisors=kvm`` to the init command.
 You can also invoke the command with the ``--help`` option in order to
 see all the possibilities.
 
+Hypervisor/Network/Cluster parameters
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Please note that the default hypervisor/network/cluster parameters may
+not be the correct one for your environment. Carefully check them, and
+change them at cluster init time, or later with ``gnt-cluster modify``.
+
+Your instance types, networking environment, hypervisor type and version
+may all affect what kind of parameters should be used on your cluster.
+
 Joining the nodes to the cluster
 ++++++++++++++++++++++++++++++++
 
-- 
1.6.5

Reply via email to