Update README

Signed-off-by: Martin Schwenke <martin@meltin.net>

diff --git a/README b/README
index 73fb7a717ca752d6ec87590d8a930227746f83c7..2550b17ebf333ff99bbaeea18df0dc92c9c59ceb 100644 (file)
--- a/README
+++ b/README
@@ -314,7 +314,7 @@ all of this as root.
 
     4) autocluster -c m1.autocluster cluster boot
 
-    5) autocluster -c m1.autocluster cluster configure
+    5) autocluster -c m1.autocluster cluster setup
 
 BOOTING/DESTROY A CLUSTER
 =========================
@@ -326,9 +326,9 @@ nodes in the cluster.
 
     The most useful vircmd commands are:
  
-      start    : boot a node
-      shutdown : graceful shutdown of a node
-      destroy  : power off a node immediately
+      start    : boot a cluster
+      shutdown : graceful shutdown of a cluster
+      destroy  : power off a cluster immediately
 
     You can watch boot progress like this:
 
@@ -343,12 +343,14 @@ POST-BOOT SETUP
 
 Autocluster copies some scripts to cluster nodes to enable post-boot
 configuration.  These are used to configure specialised subsystems
-like GPFS or Samba and are installed in /root/scripts/ on each node.
-The main 2 entry points are install_packages.sh and setup_cluster.sh.
-To setup a clustered NAS system you will normally need to run
-setup_gpfs.sh and setup_cluster.sh on one of the nodes.  If you want
-to run these manually, see autocluster's cluster_configure() function
-for example usage.
+like GPFS or Samba, and are installed in /root/scripts/ on each node.
+The main entry point is cluster_setup.sh, which invokes specialised
+scripts depending on the cluster filesystem type or the node type.
+cluster_setup.sh is invoked by the cluster_setup() function in
+autocluster.
+
+See cluster_setup() if you want to do things manually or if you want
+to add support for other node types and/or cluster filesystems.
 
 There are also some older scripts that haven't been used for a while
 and have probably bit-rotted, such as setup_tsm_client.sh and