[wiki.lml] push by - Edited wiki page InstallationAndSetup through web user interface. on 2011-05-12 08:01 GMT

[l...@googlecode.com]

Revision: 00c76d11e171
Author: schlomo....@gmail.com
Date: Thu May 12 01:01:53 2011
Log: Edited wiki page InstallationAndSetup through web user interface.
http://code.google.com/p/lml/source/detail?repo=wiki&r=00c76d11e171

Modified:
/InstallationAndSetup.wiki

=======================================
--- /InstallationAndSetup.wiki Thu May 12 00:58:02 2011
+++ /InstallationAndSetup.wiki Thu May 12 01:01:53 2011
@@ -46,3 +46,4 @@
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)
+Create a service user and assign this service user with the LML service
role either at the top of the vCenter tree or at the appropriate VM folders.