Difference between revisions of "Lab Manager"

From vwiki
Jump to navigation Jump to search
(Initial creation)
 
(Added VMware Category)
Line 32: Line 32:
# Locate the problem network and go to '''Properties'''
# Locate the problem network and go to '''Properties'''
# Update the '''Physical Network Bindings''' for the relevant ESX
# Update the '''Physical Network Bindings''' for the relevant ESX
[[Category:VMware]]

Revision as of 09:27, 18 August 2010

Import Machine into Lab Manager

Prerequisites

  • Source Virtual Machine
    • Will be cloned (or moved) into Lab Manager, can be a template or a VM (but must be powered off)
  • Destination info
    • Hostname
    • Description (optional)
    • Network (an existing Physical [lab] Network)
    • Datastore

Procedure

  1. Within Lab Manager, select the correct Organisation
  2. Go to Build and Deploy > VM Templates, and hit the Import VM Template... button (if the button doesn't exist then your account doesn't have sufficient rights)
  3. Enter the new Template's Name and Description, then locate the source Virtual Machine and hit Next
  4. Select the appropriate Network and Datastore, leave Make a Copy option selected unless you want the source VM to be lost/moved, then hit Import
  5. Once the import has completed, check/change the following options
    • Owner
    • Published

Change a Deployed VM's Resources

In theory a deployed VM's config shouldn't be changed, in reality its bound to be required at some point as a one off, but its quite limited. Obviously any changes will be lost when the template is redeployed, if this isn't wanted, or if its a regular occurrence the VM templates should probably be edited.

  • CPU - Update the deployed VM's config through vCentre
  • Memory - Update the deployed VM's config through vCentre
  • Network - Update the deployed VM's config through vCentre
  • Disk - Can't be changed, a deployed template is a delta from the original template (think snapshotting), you must reconfigure the template

Troubleshooting

Unable to Deploy Virtual Machine

External network PortGroup is not deployed on host "ESX"
Caused by a Physical Network not being correctly configured on the ESX property

  1. Go to Manage > Resources
  2. Locate the problem network and go to Properties
  3. Update the Physical Network Bindings for the relevant ESX