On Fri, Apr 17, 2015 at 06:46:44PM +0200, 'Klaus Aehlig' via ganeti-devel wrote:
Also explain that N+1 redundancy for DRBD instances is always checked,
whereas global N+1 redundancy checks (mainly involving shared-storage
instances) can be disabled.
Signed-off-by: Klaus Aehlig <[email protected]>
---
man/hail.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/man/hail.rst b/man/hail.rst
index 67408db..cc71d18 100644
--- a/man/hail.rst
+++ b/man/hail.rst
@@ -116,6 +116,11 @@ The options that can be passed to the program are as
follows:
for possible allocations. In this way a useful decission can be made
even in overloaded clusters.
+\--no-capacity-checks
+ Normally, hail will only consider those allocations where all instances
+ of a node can immediately restarted should that node fail. With this
+ option given, hail will check only N+1 redundancy for DRBD instances.
+
\--simulate *description*
Backend specification: similar to the **-t** option, this allows
overriding the cluster data with a simulated cluster. For details
--
2.2.0.rc0.207.ga3a616c
LGTM, thanks
