1.0.2
Table Of Contents
- Lifecycle Manager Administration Guide
- Contents
- Updated Information
- About This Book
- Understanding LCM
- Installing LCM
- Migrating from LCM 1.0.1 to LCM 1.0.2
- Configuring LCM
- Check Configuration Readiness
- Initial Configuration of Lifecycle Manager
- Configure the LCM Webview
- Set Approval Requirements
- Configure Archiving Settings
- Change Authorization Groups
- Change the Base Name for Virtual Machines
- Enable Email Notifications
- Configure Email Notification Content
- Configure Currency and Date Formats
- Customizing the User Interface
- Setting Up the Virtual Machine Environment
- Using LCM
- LCM Administrator’s Interface
- Request a Virtual Machine
- Display Requested Virtual Machines
- Modify Request Options
- Check the Power State of a Virtual Machine
- Power a Virtual Machine On and Off
- Connecting to a Virtual Machine
- Create or Revert to a Snapshot
- Generate Reports
- Register Virtual Machines with LCM
- Activate Webview Debug Mode
- Relink Tokens to Virtual Machines
- Check Licensing Status
- Export Logs and Application Settings
- Troubleshoot LCM
- Index
VMware, Inc. 11
Chapter 1 Understanding LCM
Lifecycle Manager Terminology
LCMusesspecificterminologytodescribelifecycleeventsandattributes.
Role-Based User Interface
LCMhasarole‐basedinterface.Usersarepresentedonlytheoptionsthatarerelevanttoaspecificrole.
All rolescanrequestavirtualmachine.
LCMhasthefollowingroles:
LCMAdministrator–Establishesthecriteriausedformachineplacementanddetermineshowthe
criteriaconverttosizingorplacementvalues.TheLCMAdministratorconfiguresLCMandestablishes
theplacementofvirtualmachines.
LCMRequester–Canrequesttoextendthelifeofacreatedvirtualmachine.Requesterscanpower
virtualmachinesonandoff,aswellasdelegatethiscontroltootherusers.
LCMTechRequester–Inadditiontodoingeverythingthattherequesterrolecando,thetechrequester
canmodifycustomizationtemplates.
LCMApprover–Approvesvirtualmachinedeploymentandextensionrequests.Ifamachinecannotbe
placedbasedontheprovidedcriteria,auserwiththeLCMITStaffrolemustmanuallychoosethesizing
andplacementofthenewmachine.
LCMITStaff–Completesmanualplacementofapprovedvirtualmachines.
Formoreinformationonthetasksthatuserscanper form,seetheLifecycleManagerUserʹsGuide.
LCM Administrator
TheLCMAdministratorisresponsibleforthefollowingtasks:
ConfiguringLCM
Determiningtheinfrastructure,suchastheserverenvironment
Settingupemailnotifications,thelookandfeeloftheuserinterface,andstylesheets
Specifyingwhocanaccesselements,suchasresourcepoolsordatastores
Table 1-1. Terminology
Term Definition
Commission Dateandtimetocreatearequestedvirtualmachine.Thecommissiontimeissubmittedduring
therequestprocess.
Decommission Therequestedmachinereachesitsendoflife.Adecommissiondateissubmittedduringthe
requestprocess.Thedecommissionedmachinecanbearchivedordeleted.
Extension Extendingthelife ofavirtualmachine
thatistobedecommissioned.Ifapprovalisrequired,the
requestforextensionmustbeapprovedbeforetheownerofthevirtualmachinecancontinueto
useit.
Infrastructure Attributessuchasthenetwork,domain,anddatastoreaffectwheretherequestedvirtual
machineisplacedinVMwareInfrastructure.
Criteria Attributesattachedto
arequestedvirtualmachinethatareselectedduringtherequestprocess,
suchaslocation,organization,serverenvironment,servicelevel,andperformance.TheLCM
Administratormapsthisinformationtotheinfrastructure.
TemplateProfile Theprofilethatisusedwhenarequestedvirtualmachineiscloned.
Customization
Template
Thetemplatethatdeterminestheresourcesthat
therequestedvirtualmachineuses,suchas
memoryreservation,memorylimit,CPUshares,anddiskshares.OnlytheLCMITStaff,LCM
TechRequester,andLCMAdministratorcanmodifythecustomizationtemplate.
Placing Therequestedvirtualmachineiscreatedormovedintotheinfrastructure,basedontheselected
criteriaandinfrastructure.