X-Git-Url: https://code.grnet.gr/git/ganeti-local/blobdiff_plain/0c7d4422715c27c597da8bcc8baa3e886e36e246..1bf1ce3f9a72cdd4efadeb50d4ca7162e4239c13:/man/htools.rst

diff --git a/man/htools.rst b/man/htools.rst
index cc9ef39..ea9019f 100644
--- a/man/htools.rst
+++ b/man/htools.rst
@@ -12,6 +12,9 @@ SYNOPSIS
 **hbal**
   cluster balancer
 
+**hcheck**
+  cluster checker
+
 **hspace**
   cluster capacity computation
 
@@ -21,6 +24,9 @@ SYNOPSIS
 **hscan**
   saves cluster state for later reuse
 
+**hinfo**
+  cluster information printer
+
 
 DESCRIPTION
 -----------
@@ -35,6 +41,9 @@ environment variable HTOOLS can be used to set the desired role.
 Installed as ``hbal``, it computes and optionally executes a suite of
 instance moves in order to balance the cluster.
 
+Installed as ``hcheck``, it preforms cluster checks and optionally
+simulates rebalancing with all the ``hbal`` options available.
+
 Installed as ``hspace``, it computes how many additional instances can
 be fit on a cluster, while maintaining N+1 status. It can run on models
 of existing clusters or of simulated clusters.
@@ -45,6 +54,9 @@ by Ganeti to compute new instance allocations and instance moves.
 Installed as ``hscan``, it scans the local or remote cluster state and
 saves it to files which can later be reused by the other roles.
 
+Installed as ``hinfo``, it prints information about the current cluster
+state.
+
 COMMON OPTIONS
 --------------
 
@@ -203,6 +215,11 @@ support all options. Some common options are:
   on which the master daemon listens; otherwise, the default path used
   by Ganeti (configured at build time) is used.
 
+-I|\--ialloc-src *path*
+  Backend specification: load data directly from an iallocator request
+  (as produced by Ganeti when doing an iallocator call).  The iallocator
+  request is read from specified path.
+
 \--simulate *description*
   Backend specification: instead of using actual data, build an empty
   cluster given a node description. The *description* parameter must be
@@ -216,7 +233,7 @@ support all options. Some common options are:
   - the cpu core count for the nodes
   - the spindle count for the nodes
 
-  An example description would be **preferred,B20,100G,16g,4,2**
+  An example description would be **preferred,20,100G,16g,4,2**
   describing a 20-node cluster where each node has 100GB of disk space,
   16GiB of memory, 4 CPU cores and 2 disk spindles. Note that all nodes
   must have the same specs currently.