added some iMacros for automating the GUI

1 files changed, 35 insertions, 17 deletions

diff --git a/README b/README
index ae98b22..a2de449 100644
--- a/README
+++ b/README
@@ -42,11 +42,21 @@ To setup a virtual cluster for SoFS with autocluster follow these steps:
     fscc-install.mainz.de.ibm.com in
       /instgpfs/instsrv/dists/ISO/RHEL5.2-Server-20080430.0-x86_64-DVD.iso
 
- 5) use ./create_base.sh to create the base install image.  The
+ 5) create a 'config' file in the autocluster directory. I suggest you
+    create it like this:
+
+      . config.sample
+      MEM=what ever mem you want
+      KVM=path to your kvm
+    
+    That way when you upgrade autocluster with "git pull" you will
+    inherit the new addtions to config.sample   
+
+ 6) use ./create_base.sh to create the base install image.  The
     install will take about 10 to 15 minutes and you will see the
     packages installing in your terminal
 
- 6) when that has finished, 'destroy' that machine (ie. power it off),
+ 7) when that has finished, 'destroy' that machine (ie. power it off),
     with "virsh destroy SoFS-1.5-base"
 
     Then I recommend you mark that base image immutable like this:
@@ -57,39 +67,47 @@ To setup a virtual cluster for SoFS with autocluster follow these steps:
     image will be used as a basis file for the per-node images, and if
     it changes your cluster will become corrupt
 
- 7) now run ./create_cluster, specifying a cluster name. For example:
+ 8) now run ./create_cluster, specifying a cluster name. For example:
 
       ./create_cluster c1
 
     That will create your cluster nodes and the TSM server node
 
- 8) now boot your cluster nodes like this:
+ 9) now boot your cluster nodes like this:
 
-       virsh start c1n1
-       virsh start c1n2
-       virsh start c1n3
-       virsh start c1n4
-       virsh start c1tsm
+       ./vircmd start c1
 
-   The most useful virsh commands are:
+   The most useful vircmd commands are:
  
        start    : boot a node
        shutdown : graceful shutdown of a node
        destroy  : power off a node immediately
 
- 9) you can watch boot progress like this:
+ 10) you can watch boot progress like this:
 
        tail -f /var/log/kvm/serial.c1*
 
     All the nodes have serial consoles, making it easier to capture
     kernel panic messages and watch the nodes via ssh
 
- 10) now you can ssh into your nodes. You may like to look at the
- small set of scripts in roots home directory on the nodes for some
- scripts. In particular:
+ 11) now you can ssh into your nodes. You may like to look at the
+     small set of scripts in roots home directory on the nodes for
+     some scripts. In particular:
+
+      setup_tsm_server.sh:  run this on the TSM node to setup the TSM server
+      setup_tsm_client.sh:  run this on the GPFS nodes to setup HSM
+      mknsd.sh           :  this sets up the local shared disks as GPFS NSDs
+
 
-    setup_tsm_server.sh:  run this on the TSM node to setup the TSM server
-    setup_tsm_client.sh:  run this on the GPFS nodes to setup HSM
-    mknsd.sh           :  this sets up the local shared disks as GPFS NSDs
+ 12) If using the SoFS GUI, then you may want to lower the memory it
+     uses so that it fits easily on the first node. Just edit this
+     file on the first node:
 
+          /opt/IBM/sofs/conf/overrides/sofs.javaopt
 
+ 13) For automating the SoFS GUI, you may wish to install the iMacros
+     extension to firefox, and look at some sample macros I have put
+     in the imacros/ directory of autocluster. They will need editing
+     for your environment, but they should give you some hints on how
+     to automate the final GUI stage of the installation of a SoFS
+     cluster.