1.2.0

Table Of Contents
Table 9-1. Installation Prerequisites (Continued)
Component Description
LCM database Choose one of the following approaches:
n
Use the same database as Orchestrator.
n
Use a separate database for LCM (recommended).
NOTE Because of CPU and memory usage, you should consider hosting the
LCM database and the Orchestrator server on different machines on a local
network with low latency.
Static account for each vCenter Server that
LCM and Orchestrator can use
DHCP server and fixed range of IP addresses
for new virtual machines
Required vCenter Server Privileges
To manage virtual machines, an LCM user must have a minimum set of privileges in vCenter Server.
The following privileges are required.
n
Datastore>Allocate Space
n
Datastore>Browse Datastore
n
Folder>Create Folder
n
Host Profile>View
n
Resource>Assign virtual machine to resource pool
n
Resource>Create resource pool
n
Virtual Machine>Configuration>Change CPU count
n
Virtual Machine>Configuration>Change resource
n
Virtual Machine>Configuration>Memory
n
Virtual Machine>Configuration>Modify device Settings
n
Virtual Machine>Interaction>Console interaction
n
Virtual Machine>Interaction>Power Off
n
Virtual Machine>Interaction>Power On
n
Virtual Machine>Interaction>Reset
n
Virtual Machine>Interaction>Suspend
n
Virtual Machine>Inventory>Create from existing
n
Virtual Machine>Inventory>Remove
n
Virtual Machine>Inventory>Unregister
n
Virtual Machine>Provisioning>Clone template
n
Virtual Machine>Provisioning>Clone virtual machine
n
Virtual Machine>Provisioning>Customize
n
Virtual Machine>Provisioning>Deploy template
n
Virtual Machine>State>Create Snapshot
n
Virtual Machine>State>Revert to snapshot
Lifecycle Manager Installation and Configuration Guide
64 VMware, Inc.