[wiki.lml] push by - Edited wiki page InstallationAndSetup through web user interface. on 2011-05-12 07:58 GMT
l...@googlecode.com
Author: schlomo....@gmail.com
Date: Thu May 12 00:58:02 2011
Log: Edited wiki page InstallationAndSetup through web user interface.
http://code.google.com/p/lml/source/detail?repo=wiki&r=200a765d9b57
Modified:
/InstallationAndSetup.wiki
=======================================
--- /InstallationAndSetup.wiki Fri May 6 02:59:21 2011
+++ /InstallationAndSetup.wiki Thu May 12 00:58:02 2011
@@ -7,11 +7,42 @@
Basically LML could also run on Windows, I just did not try it out.
+= Preparation =
+
+To make use of Lab Manager Light one needs the following ingredients:
+ * One or more VMware ESX servers managed through a vCenter
+ * A dedicated network for Virtual Machines that will be managed by LML
+ * A dedicated DNS domain for this network
+ * A (virtual) server to host DHCP, TFTP, DNS and HTTP servers preferably
on the dedicated network. Other setups are possible but beyond the scope of
this guide.
= Installation =
LML requires the following Packages:
- * TODO
- *
-
-= Setup =
+ * libsvn-perl
+ * libconfig-inifiles-perl
+ * [http://www.vmware.com/support/developer/viperltoolkit/ vSphere SDK for
Perl]
+
+The following services need to be configured for LML to work properly:
+ # DHCP server
+ # TFTP server
+ # DNS server
+ # HTTP server
+ # VMware vCenter server
+
+== DHCP & TFTP ==
+Since LML manages a DHCP server one should first start by setting up the
DHCP server to manage the lab network and the TFTP server to provide the
[http://syslinux.zytor.com/wiki/index.php/Download gpxelinux.0] boot image:
+ * All systems on the lab network should be able to PXE boot
+ * Assign a dynamic range that is large enough for the expected amount of
VM
+
+== DNS ==
+LML uses the DHCP server to update the DNS server, so the next step is to
configure the DHCP-DNS update mechanism. Check the
[http://linux.die.net/man/5/dhcpd.conf dhcpd.conf(5)] man page or search
for a guide, like
[http://www.randombugs.com/linux/linux-isc-dhcp-server-dynamic-dns-updates-debian-ubuntu.html
this one for example].
+
+== HTTP ==
+
+The LML scripts work as CGI scripts and are access via the HTTP server.
The 'web/conf.d' directory contains a suitable configuration snippet for
the Apache HTTP server. The content of the 'web/www' directory should go to
the docroot of the HTTP server.
+
+== vCenter server ==
+
+LML needs read-only access rights for the managed VMs and optionally the
right to edit the advanced options of the VMs. If you don't want LML to
force all VMs to always boot off the network then read-only access is
sufficient. Typically one creates a new vCenter role, e.g. "Lab Manager
Light Service" with the following permissions:
+ * Virtual Machine -> Configuration -> Advanced (for changing the advanced
options and force VMs into network boot)
+ * Global -> Set custom attribute (not yet used by LML, would allow LML to
give feedback to the user via custom attributes)