moved to template based configuration

1 files changed, 13 insertions, 5 deletions

diff --git a/README b/README
index a2de449..01f25e8 100644
--- a/README
+++ b/README
@@ -24,13 +24,14 @@ To setup a virtual cluster for SoFS with autocluster follow these steps:
 
        ./configure --without-xen --prefix=/usr
 
- 2) install a squid proxy on your host. See
+ 2) You need a cacheing web proxy on your local network. If you don't
+    have one, then 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
 
-    To test your squid setup, run this command:
+    To test your squid setup, run a command like this:
 
       http_proxy=http://10.0.0.1:3128/ wget http://9.155.61.11/mediasets/SoFS-daily/
 
@@ -45,17 +46,24 @@ To setup a virtual cluster for SoFS with autocluster follow these steps:
  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
+       . 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   
 
+    Then look through config.sample and check for any config options
+    you want to override. Add them to your config file.
+
  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
 
+    Before you start create_base.sh make sure your web proxy cache is
+    authenticated with the Mainz BSO (eg. connect to
+    https://9.155.61.11 with a web browser)
+
  7) when that has finished, 'destroy' that machine (ie. power it off),
     with "virsh destroy SoFS-1.5-base"