Modified:
/InstallationAndSetup.wiki
=======================================
--- /InstallationAndSetup.wiki Thu May 12 02:00:46 2011
+++ /InstallationAndSetup.wiki Fri May 13 08:46:32 2011
@@ -62,7 +62,7 @@
It is possible to start with the example configuration with the following
exceptions:
* Fill in the '[vsphere]' section, especially the data for the service
account. If you don't want to check VM owner or expiration then disable the
corresponding _field values in this section.
* Set the lab DNS domain in the '[dhcp]' and optionally the '[vsphere]'
sections
- * Edit the '[hostrules]' section to match your host rules or disable
hostname validation.
+ * Edit the '[hostrules]' section to match your host rules or disable
hostname validation. For starters disabling the pattern matching might help
if the VMs don't follow an easy naming convention.
* Edit the '[subversion]' section and remove the settings unless you have
a SVN where you want LML to manage hostname entries.
=== First Test ===
@@ -127,4 +127,11 @@
=== Putting it All Together ===
-Now it is time to put all the pieces to work together.
+Now it is time to put all the pieces to work together and making sure that
all components work together, please refer to the included sample config
files for hints how to do this:
+ * The DHCP server must set the pxelinux prefix (DHCP option 210) to point
to the HTTP server and the location of LML, e.g. 'http://<host>/boot'
+ * The HTTP server must be set up to pass any calls
to 'pxelinux.cfg/<UUID>' to the pxelinux.pl script
+ * There must be a default configuration in 'pxelinux.cfg/default'
as 'pxelinux.pl' redirects the client there if all is fine
+
+=== Detailed Configuration ===
+
+After getting LML to work you can try out is various features and options.
Please refer to [Configuration] for details.