2,187
edits
Difference between revisions of "Lab Manager"
Jump to navigation
Jump to search
Added "Put Spanned ESX Host into Maintenance Mode"
(→SOAP API: Added "Configuration IP's Lister and RDP Tester") |
(Added "Put Spanned ESX Host into Maintenance Mode") |
||
| Line 49: | Line 49: | ||
# Go to '''Manage | Resources | Physical Networks''' and add network bindings for each of the ESX's | # Go to '''Manage | Resources | Physical Networks''' and add network bindings for each of the ESX's | ||
# Go to '''Manage | Resources | Hosts''' and '''Enable''' the hosts | # Go to '''Manage | Resources | Hosts''' and '''Enable''' the hosts | ||
=== Put Spanned ESX Host into Maintenance Mode === | |||
You can't put an ESX directly into maintenance mode, if its enable for host spanning, as the service VM (called something like <code>012345-VMwareLM-ServiceVM-I6-H78</code>) won't power-down or undeploy automatically. | |||
# Deployed but powered off LM VM's can't be moved, so any on the host have to be either powered on, or undeployed | |||
# With DRS set to '''Fully Automated''', select '''Enter Maintenance Mode''' for your ESX host | |||
# Once all deployed (non service) VM's have migrated off, put DRS to '''Partially Automated''' and '''''cancel'''''' the ''Enter Maintenance Mode'' task | |||
# Then '''Disable''' the host in Lab Manager, and unselect the '''Enable host for Host Spanning''' to undeploy the service VM | |||
#* In Lab Manager, go to Manage > Resources > Hosts tab to Disable, and go into the ESX's Properties to disable host spanning | |||
# Finally, put the host in '''Maintenance Mode''' | |||
Once your work is complete, take the host out of maintenance mode, enable for host spanning and as LM host, then put DRS back to Fully Automated | |||
== Change a Deployed VM's Resources == | == 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 on what can be | 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 on what can be achieved. | ||
Any changes will be lost when the template is undeployed and its state not saved. If this isn't wanted, or if its a regular occurrence, the VM templates should be edited (CPU and memory can be edited with Lab Manager, the VM doesn't need to be re-imported). | Any changes will be lost when the template is undeployed and its state not saved. If this isn't wanted, or if its a regular occurrence, the VM templates should be edited (CPU and memory can be edited with Lab Manager, the VM doesn't need to be re-imported). | ||