corrections and expanded information

Author: Charles Loomis

source/admin-tutorial/02-prerequisites.rst

@@ -29,10 +29,20 @@ The machine must have a CPU that supports the VT-x virtualization
 extensions and must have this support enabled in the BIOS.  **Many
 vendors ship machines with these extensions disabled.**
 
-RedHat has a `good document <http://virt-tools.org/learning/check-hardware-virt/>`__ 
-for checking if your machine will support virtualization.  In short, check
-the `/proc/cpuinfo` for the proper flags and check the `dmesg` console
-for any KVM errors when trying to load the KVM kernel module.
+RedHat has a `good document
+<http://virt-tools.org/learning/check-hardware-virt/>`__ for checking
+if your machine will support virtualization.  In short, check the
+`/proc/cpuinfo` for the proper flags::
+
+    $ grep vmx /proc/cpuinfo 
+
+and check the `dmesg` console for any KVM errors when trying to load
+the KVM kernel module::
+
+    $ dmesg | grep kvm
+
+looking for any messages about KVM not supporting virtualisation or
+having it disabled in BIOS.
 
 Operating System
 ----------------
@@ -100,6 +110,21 @@ configuration parameters below as necessary.
 
 The "Node" machine can be configured with a single LVM group.
 
+You can see the configured volume groups with the command::
+
+    $ vgdisplay
+
+     --- Volume group ---
+     VG Name               rootvg
+     System ID             
+     Format                lvm2
+     ...
+
+You'll need the volume group name "VG Name" of the volume group you'll
+be using for the cloud storage.  Verify that the device associated
+with the group name exists.  Here for example, the device is
+`/dev/rootvg`.
+
 Software
 --------
 
@@ -131,6 +156,9 @@ The configuration for the CentOS repository is done when the system is
 installed and the IGTF repository will be configured by the StratusLab
 tools as necessary.  The others require explicit configuration. 
 
+The directory `/etc/yum.repos.d` contains the currently configured yum
+repositories.
+
 EPEL Repository
 ^^^^^^^^^^^^^^^
 

source/admin-tutorial/04-config-params.rst

@@ -47,6 +47,7 @@ for the Persistent Disk service::
 
     # *** NOTE: Copy the following exactly.  Be careful of ***
     # *** the opening and closing single quotes!           ***
+
     $ stratus-config persistent_disk_backend_sections '
     [%(persistent_disk_ip)s]
             type=LVM
@@ -70,9 +71,11 @@ Use the frontend as the general gateway for the cloud::
 
 Set the IP and mac addresses for virtual machines::
 
+    # space-separated list
     $ stratus-config one_public_network_addr \
         134.158.xx.yy 134.158.xx.yy 134.158.xx.yy
 
+    # space-separated list
     $ stratus-config one_public_network_mac \
         0a:0a:86:9e:49:2a 0a:0a:86:9e:49:2b 0a:0a:86:9e:49:2c
 
@@ -99,9 +102,11 @@ the Front End. Do the following::
     $ stratus-config dhcp_lease_time 3600
 
     $ stratus-config dhcp_one_public_network True
-    $ stratus-config dhcp_one_local_network_routers $FRONTEND_IP
-    $ stratus-config dhcp_one_local_network_domain_name lal.in2p3.fr
-    $ stratus-config dhcp_one_local_network_domain_name_servers \
+    $ stratus-config dhcp_one_public_network_routers $FRONTEND_IP
+    $ stratus-config dhcp_one_public_network_domain_name lal.in2p3.fr
+
+    # comma-separated list
+    $ stratus-config dhcp_one_public_network_domain_name_servers \
          134.158.91.80, 134.158.88.149
 
 Use **your** values for these parameters!

source/admin-tutorial/05-frontend.rst

@@ -6,10 +6,45 @@ Now that we have defined all of the configuration parameters, you can
 now do the full Front End installation by issuing the following
 command::
 
-    $ stratus-install -vv
+    $ stratus-install -vv 2>&1 | tee frontend-install.log
 
 To get more details on what the command is (because of curiosity or
 errors), use the option ``-v``, ``-vv``, or ``-vvv``.
 
 If you run into errors, the ``stratus-install`` command can simply be
 rerun after adjusting the configuration parameters.
+
+When the installation completes successfully, you should see the
+following services running on the machine::
+
+    $ service nginx status
+    nginx (pid  15215) is running...
+
+    $ service one-proxy status
+    Checking arguments to Jetty: 
+    ...
+    Jetty running pid=15847
+
+    $ service pdisk status
+    Checking arguments to Jetty: 
+    ...
+    Jetty running pid=17099
+
+You should also see a web page running at `https://${FRONTEND_HOST}/`
+that lists these services::
+
+    $ curl -k https://${FRONTEND_HOST}/ 
+    <html>
+    ...
+    <a href="readme.html">readme.html</a>
+    ...
+    <a href="svc-one-proxy.html">svc-one-proxy.html</a>
+    ...
+    <a href="svc-pdisk.html">svc-pdisk.html</a>
+    ...
+    </html>
+
+If the page doesn't appear or any of the services are not running, you
+should investigate the errors in the log files.  The log files for all
+StratusLab services are in `/var/log/stratuslab`.  Each service in a
+separate subdirectory.