added a README

3 files changed, 80 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..23c39e4
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,2 @@
+tmp
+config
diff --git a/README b/README
new file mode 100644
index 0000000..d25163c
--- /dev/null
+++ b/README
@@ -0,0 +1,77 @@
+To setup a virtual cluster for SoFS follow these steps:
+
+
+ 1) download and install the latest kvm-userspace and kvm tools 
+    from http://kvm.qumranet.com/kvmwiki/Code
+
+ 2) install a squid proxy on your host. See
+    host_setup/etc/squid/squid.conf for a sample config suitable for a
+    virtual cluster. Make sure it caches large objects and has plenty
+    of space. This will be needed to make downloading all the RPMs to
+    each client sane
+
+ 3) setup a DNS server on your host. See host_setup/etc/bind/ for a
+    sample config that is suitable. It needs to redirect DNS queries
+    for your SOFS virtual domain to your windows domain controller
+
+ 4) download a RHEL-5.2 install ISO. You can get it from
+    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. You need to
+    have virt-manager open, and when the script exits you have to
+    immediately open the console on the SoFS-1.5-base image it
+    created, then at the boot prompt type "linux ks=floppy"
+
+    The base RHEL OS will then install. This will take about 10
+    minutes. You can watch progress while its going. The last stage
+    "running post install scripts" will download the SoFS RPMs from
+    mainz, so if they are not already in your squid cache this may
+    take some time. You can watch progress by switching to a different
+    virtual console with alt-RIGHTARROW in the kvm window
+
+ 6) when that has finished, 'destroy' that machine (ie. power it off),
+    then I recommend you mark that base image immutable like this:
+
+      chattr +i /virtual/SoFS-1.5-base.img
+
+    That will ensure it won't change. This is a precaution as the
+    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:
+
+      ./create_cluster c1
+
+    That will create your cluster nodes and the TSM server node
+
+ 8) now boot your cluster nodes like this:
+
+       virsh start c1n1
+       virsh start c1n2
+       virsh start c1n3
+       virsh start c1n4
+       virsh start c1tsm
+
+   The most useful virsh 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:
+
+       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:
+
+    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
+
+
diff --git a/create_cluster.sh b/create_cluster.sh
index af157da..62f835c 100755
--- a/create_cluster.sh
+++ b/create_cluster.sh
@@ -11,6 +11,7 @@ fi
 CLUSTER="$1"
 
 mkdir -p $VIRTBASE/$CLUSTER
+mkdir -p /var/log/kvm
 
 echo "Creating 3 shared disks"
 for i in `seq 1 3`; do