Novell PLATESPIN ORCHESTRATE Virtual Machine Management Guide
Virtual Machine Management Guide
Novell®
PlateSpin Orchestrate
novdocx (en) 13 May 2009
AUTHORIZED DOCUMENTATION
2.0.2
November 17, 2009
www.novell.com
PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
novdocx (en) 13 May 2009
Copyright © 2007-2009 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
novdocx (en) 13 May 2009
novdocx (en) 13 May 2009
4 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
Contents
About This Guide 7
1 Managing Virtual Machine Hosts 9
1.1 Configuring Policies for VM Provisioning Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.1 Configuring Policies for Virtual Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.2 Configuring Policies for Xen 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.1.3 Configuring Policies for VMware Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.1.4 Configuring Policies for Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.5 Configuring Policies for ESX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2 Discovering VM Hosts and Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3 Discovering VM Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 Resynchronizing the VM Host’s State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5 Shutting Down VM Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.6 Restarting VM Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.7 Understanding VM Host Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
novdocx (en) 13 May 2009
2 Managing Virtual Machines 21
2.1 Provisioning a Virtual Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Managing a Virtual Machine in Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2.1 Using the Right-Click Menu for Provisioning Actions. . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2.2 Prerequisites for Performing Provisioning Actions on ESX VMs . . . . . . . . . . . . . . . . 25
2.2.3 Releasing a Virtual Machine from Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.4 Managing Virtual Machine Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.5 Managed Virtual Machine Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.6 Virtual Machine Technology-Specific Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3 Resynchronizing the State of All VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4 Resynchronizing the State of All VMs of a Specific VM Host. . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.5 Shutting Down Multiple VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.6 Destroying and Deleting a Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3 Managing VM Repositories 31
3.1 Deploying a VM to the Local Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2 Deploying a VM to the Datagrid Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3 Deploying a VM to the NAS Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.4 Deploying a VM to the SAN Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.5 Virtual Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4 Troubleshooting Provisioning Actions 35
5 Understanding Autoprep 41
5.1 Setting Autoprep Facts in the Development Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.1.1 Setting Linux Autoprep Config Facts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.1.2 Setting Autoprep Network Adapter Facts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2 Applying Autoprep Facts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.2.1 Example Autoprep Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Contents 5
5.2.2 How Autoprep Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3 Known Autoprep Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
A Virtual Machine Technologies and Actions 47
A.1 Virtual Machine Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
A.2 Xen Hypervisor on SLES 10 SP2 or SLES 11 Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
A.2.1 Additional Xen Provisioning Adapter Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
A.3 VMware Virtual Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
A.3.1 Additional VMware Virtual Center Provisioning Adapter Information. . . . . . . . . . . . . 51
A.4 Microsoft Hyper-V Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
A.5 VMware ESX VM Hypervisor (Experimental). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
B Documentation Updates 55
B.1 November 17, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
B.2 July 9, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
B.3 June 17, 2009 (2.0.2 Release). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
novdocx (en) 13 May 2009
6 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
About This Guide
In addition to managing virtual machines (VMs) and host servers using the PlateSpin® Orchestrate
VM Client, you can do other management work using the PlateSpin Orchestrate Development
Client. This Virtual Machine Management Guide provides instructions on the management tasks
that you can do in the Development Client.
The guide is organized as follows:
Chapter 1, “Managing Virtual Machine Hosts,” on page 9
Chapter 2, “Managing Virtual Machines,” on page 21
Chapter 3, “Managing VM Repositories,” on page 31
Chapter 4, “Troubleshooting Provisioning Actions,” on page 35
Chapter 5, “Understanding Autoprep,” on page 41
Appendix A, “Virtual Machine Technologies and Actions,” on page 47
Appendix B, “Documentation Updates,” on page 55
novdocx (en) 13 May 2009
For documentation on using Orchestrate jobs to further manage VMs, host machines, and physical
machines, see “Virtual Machine Job Development” in the PlateSpin Orchestrate 2.0 Developer
Guide and Reference.
Audience
This book is for data center administrators. It assumes that users of the product have the following
background:
General understanding of network operating environments and systems architecture
Knowledge of basic Linux* shell commands, the Windows* command prompt, and text editors
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html (http://
www.novell.com/documentation/feedback.html) and enter your comments there.
Additional Documentation
In addition to this Virtual Machines Management Guide, PlateSpin Orchestrate 2.0 includes the
following additional guides that contain valuable information about the product:
PlateSpin Orchestrate 2.0 Getting Started Reference
PlateSpin Orchestrate 2.0 Installation and Configuration Guide
PlateSpin Orchestrate 2.0 Upgrade Guide
PlateSpin Orchestrate 2.0 High Availability Configuration Guide
PlateSpin Orchestrate 2.0 Administrator Reference
PlateSpin Orchestrate 2.0 Command Line Reference
About This Guide 7
PlateSpin Orchestrate 2.0 VM Client Guide and Reference
PlateSpin Orchestrate 2.0 Development Client Reference
PlateSpin Orchestrate 2.0 Developer Guide and Reference
PlateSpin Orchestrate 2.0 Server Portal Reference
Documentation Updates
For the most recent version of this guide, visit the PlateSpin Orchestrate 2.0 documentation Web site
(http://www.novell.com/documentation/ps_orchestrate20/).
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
A trademark symbol (
®
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux, should use forward slashes as required by your software.
novdocx (en) 13 May 2009
8 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
1
Managing Virtual Machine Hosts
After installing the PlateSpin® Orchestrate Agent on the physical resource, you can discover for the
hypervisor technology residing on the resource by editing the appropriate policies and running the
Discover VM hosts job. Later on, you can discover and manage VMs residing on the VM hosts.
These launch the adapter job to connect to the appropriate hypervisor Web service.
Section 1.1, “Configuring Policies for VM Provisioning Adapters,” on page 9
Section 1.2, “Discovering VM Hosts and Repositories,” on page 15
Section 1.3, “Discovering VM Images,” on page 16
Section 1.4, “Resynchronizing the VM Host’s State,” on page 16
Section 1.5, “Shutting Down VM Hosts,” on page 17
Section 1.6, “Restarting VM Hosts,” on page 18
Section 1.7, “Understanding VM Host Failover,” on page 18
novdocx (en) 13 May 2009
1
1.1 Configuring Policies for VM Provisioning Adapters
This section contains information on the policies required to manage the Provisioning adapters.
Provisioning adapters are programs that provision (start, stop, snapshot, migrate, or pause) a VM.
They run just like regular jobs on the PlateSpin Orchestrate Server.
Section 1.1.1, “Configuring Policies for Virtual Center,” on page 9
Section 1.1.2, “Configuring Policies for Xen 3.0,” on page 12
Section 1.1.3, “Configuring Policies for VMware Server,” on page 12
Section 1.1.4, “Configuring Policies for Hyper-V,” on page 13
Section 1.1.5, “Configuring Policies for ESX,” on page 14
1.1.1 Configuring Policies for Virtual Center
Before provisioning and managing the Virtual Center provisioning adapter, you must configure
certain policies in the Development Client. However, before configuring the policies for the Virtual
Center, make sure that the following prerequisites are met:
Make sure that the Orchestrate Agent for Windows* is installed and started on the Windows
host running Virtual Center.
IMPORTANT: The PlateSpin Orchestrate Server supports only one VMware Virtual Center
server per grid.
Make sure that J2RE with version 1.4.2 for VCenter 1.x or version 1.5 for VCenter 2.x is
installed on the Windows system running Virtual Center.
Managing Virtual Machine Hosts
9
NOTE: In the 2.0.2 release of PlateSpin Orchestrate, the VMware Virtual Center Provisioning
Adapter supports only VMware Virtual Center 2.x. Virtual Center 1.x is not supported in this
release.
The JREs that ship with Virtual Center and with the Orchestrate Agent are version 1.5. Version
1.4.2_15 can be downloaded from the Sun* Download Center (https://sdlc4a.sun.com/ECom/
EComActionServlet;jsessionid=88B0E4E7E868F2F6C671427ACC9C0D13).
Make sure that the keystore is created on the server where Virtual Center is installed.
If the keystore is not created, do the following on the server where Virtual Center is installed to
generate it
novdocx (en) 13 May 2009
1. Find the
rui.crt
On Windows, the default location is:
Users\Application Data\VMware\VMware VirtualCenter\SSL\rui.crt
2. Create a
C:\VCenter_Certs\
3. Copy
4. Run
VCenter_Certs
rui.crt
keytool
The default location is
2.0\jre\bin\keytool.exe
certificate.
directory at the top level by entering
.
to
C:\VCenter_Certs\
.
C:\Program Files\VMware\VMware VirtualCenter
.
C:\Documents and Settings\All
.
mkdir
.
5. Enter:
cd C:\VCenter_Certs
[path]keytool -import -keystore keystore -file rui.crt
6. Enter a password when prompted.
The following table provides detailed information about the policies associated with the Virtual
Center provisioning adapter that are used to manage the Virtual Center hosts and the VMs in the
grid. The policy settings are applied to all the Virtual Center VMs in the grid.
Table 1-1 Virtual Machine Management Policies for Virtual Center
Policy Name Explanation Additional Details
vcenter Contains the constraints used
to select the vCenter Server
resources.
10 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
Do not edit the policy.
Policy Name Explanation Additional Details
novdocx (en) 13 May 2009
vcenter1x Contains the constraints used
to select the vCenter 1.x Server
resources.
vcenter2x Contains the constraints used
to select the vCenter 2.x Server
resources
You must configure the following facts in the
policy before running any job for the vCenter
1.x servers:
webservice_url
webservice_user
webservice_password
Additionally, you can configure the following
facts depending upon your requirements:
joblet.maxwaittime
timeout
debug
You must configure the following facts in the
policy before running any job for the vCenter
2.x servers:
webservice_url
webservice_user
webservice_password
Additionally, you can configure the following
facts depending upon your requirements:
vcenter_client1x Contains the settings used to
run only the vCenter job on the
associated vCenter resource.
vcenter_client2x Contains the settings used to
run only the vCenter job on the
associated vCenter resource.
vcenterDiscovery Contains the settings required
to discover the vCenter Server
host machines. It also contains
the default installation path of
the vCenter server.
joblet.maxwaittime
timeout
debug
You must configure the following facts in the
policy before running any job for the vCenter
1.x servers:
java1.4.2
vcenter.truststore
joblets.slots
You must configure the following facts in the
policy before running any job for the vCenter
1.x servers:
java1.5.0
vcenter.truststore
joblets.slots
Do not edit the policy.
Managing Virtual Machine Hosts 11
NOTE: VM host discovery on the vcenter adapter can fail because VM host discovery with Virtual
Center requires JRE 1.4.2 for VCenter 1.x and JRE 1.5 for VCenter 2.x to be installed on the
Windows-based Virtual Center host. The JRE that ships with the Orchestrate Agent and with
VMware* Virtual Center is v1.5.
1.1.2 Configuring Policies for Xen 3.0
Before provisioning and managing the Xen* 3.0 Server provisioning adapter, you must configure
certain policies in the Development Client. The following table provides detailed information about
the policies associated with the Xen 3.0 Server provisioning adapter that are used to manage the Xen
3.0 Server hosts and VMs in the grid. The policy settings are applied to all the VMs in the grid.
Table 1-2 Virtual Machine Management Policies for Xen 3.0 Server
Policy Name Explanation Additional Details
novdocx (en) 13 May 2009
xen30 Contains the policy settings for the Xen 3.0
Server Provisioning Adapter.
xenDiscovery Contains the settings required to discover the
Xen 3.0 Server host machines. It also
contains the default installation path of the
Xen server.
xenPA Contains the constraints used to check
whether the Xen 3.0 Server host is registered
to the Orchestrate Server, and the host is up
and running.
By default, the optimal values are
configured for the job and joblets
in the policy.
If the Xen Server is not installed in
the default path, edit this policy to
provide the correct information.
Do not edit the policy.
1.1.3 Configuring Policies for VMware Server
Before provisioning and managing the VMware Server provisioning adapter, you must configure
certain policies in the Development Client. The following table provides detailed information about
the policies associated with the VMware Server provisioning adapter that are used to manage the
VMware Server hosts and VMs in the grid. The policy settings are applied to all the VMware Server
VMs in the grid.
Table 1-3 Virtual Machine Management Policies for VMware Server
Policy Name Explanation Additional Details
vmserver Contains the policy settings for the VMware
Server provisioning adapter.
vmserverPA Contains the constraints used to check
whether the VMware Server host is registered
to the Orchestrate Server, and whether the
host is up and running.
12 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
By default, the optimal values are
configured for the job and joblets
in the policy.
Do not edit the policy.
Policy Name Explanation Additional Details
novdocx (en) 13 May 2009
vmserverDiscovery Contains settings required to discover the
VMware Server host machines. It also
contains the default installation path of the
VMware server.
Edit the policy only if the VMware
Server is not installed in the
default path.
1.1.4 Configuring Policies for Hyper-V
Before provisioning and managing the Hyper-V provisioning adapter, you must configure certain
policies in the Development Client. The following table provides detailed information about the
policies associated with the Hyper-V provisioning adapter that are used to manage the Hyper-V
hosts and VMs in the grid. The policy settings are applied to all the Hyper-V VMs in the grid.
Table 1-4 Virtual Machine Management Policies for Hyper-V
Policy Name Explanation Additional Details
hyperv Contains the policy settings for the Hyper-V
provisioning adapter
hypervDiscovery Contains the settings required to discover the
Hyper-V host.
By default, the optimal values are
configured for the job and joblets
in the policy.
Do not edit the policy.
Managing Virtual Machine Hosts 13
1.1.5 Configuring Policies for ESX
Before provisioning and managing the ESX provisioning adapter, you must configure certain
policies in the Development Client. The following table provides detailed information about the
policies associated with the ESX provisioning adapter that are used to manage the ESX hosts and
VMs in the grid. The policy settings are applied to all the ESX VMs in the grid.
Table 1-5 Virtual Machine Management Policies for ESX
Policy Name Explanation Additional Details
novdocx (en) 13 May 2009
esx Contains the policy settings for the
ESX provisioning adapter.
esxPA Contains the constraints used to
check whether the ESX host is
registered to the Orchestrate Server,
and whether the host is up and
running.
esxServerDiscovery Contains the settings required to
discover the ESX host.
You must configure the following facts
in the policy before running any job for
the ESX VM hosts:
webservice_user
webservice_password
root_user
root_password
Additionally, you can configure the
following facts depending upon your
requirements:
joblet.maxwaittime
timeout
debug
Do not edit the policy.
Do not edit the policy.
esxvmPrep Contains the settings required to
perform the Install Agent action and
the Personalize Provisioning action.
esxVncServerConfig Contains the settings required to
perform the Launch Remote Desktop
Provisioning action.
You can customize the facts for a specific ESX VM. This overrides the policy settings configured in
the ESX policy of the ESX host on which the VM is hosted.
To customize the facts for an ESX VM, do the following in the Development Client:
1 Click Resources > Physical.
2 Click the ESX machine whose policy settings you want to edit.
The Constraints/Facts tab is displayed by default.
14 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
Do not edit the policy.
Do not edit the policy.
3 To customize the Web service credentials, edit the resoruce.webservice_user.override and
resource.webservice_password.override facts. (To edit a fact, click the fact, click the Edit the
fact icon, make the necessary changes, then click OK.)
4 To customize the VM credentials for installing the Orchestrate agent, edit the
resource.root_user.override and the resource.root_password.override facts.
This overrides the default values configured in the ESX policy for all the ESX machines at the
grid level.
1.2 Discovering VM Hosts and Repositories
1 Ensure that the policies appropriate to the VM technology are configured.
For more information on the policies, see Section 1.1, “Configuring Policies for VM
Provisioning Adapters,” on page 9.
2 Ensure that you have set the correct number of joblet slots for the VM hosts in the policies
appropriate to the VM technology.
For more information on the policies, see Section 1.1, “Configuring Policies for VM
Provisioning Adapters,” on page 9.
3 In the Development Client, click Provision > Discover VM Hosts and Repositories.
The Discover VM Hosts and Repositories dialog box is displayed.
novdocx (en) 13 May 2009
4 Select your provisioning adapter from the drop-down list.
5 Click OK.
6 Click Jobs to view the Jobs section in the Development Client and verify that the job has
started.
After your VM host machines are discovered, you can refresh your tree view or wait for the
automatic tree refresh to see the VM host machine listed under the provisioning adapter,
although no VMs are listed.
This also discovers:
Local repositories for all types of hypervisors.
SAN repositories for Xen and ESX.
To view the discovered repositories, click Repositories, then click xen30 or esx.
For a list of the VM technologies and supported host and guest operating systems, see
Section A.1, “Virtual Machine Technologies,” on page 47.
By default, the VM host is started when you initiate the Discover VM Hosts and Repositories
action.
Managing Virtual Machine Hosts 15
1.3 Discovering VM Images
To discover the VM images on a specific repository:
1 In the Development Client, click Provision > Discover VM Images.
The Discover VM Images dialog box is displayed.
novdocx (en) 13 May 2009
2 In the Provisioning Adapter drop-down list, select the provisioning adapter for which you want
to discover the VM images.
The source repositories for the selected provisioning adapter are displayed.
For information on provisioning adapters, see Section 2.1, “Provisioning a Virtual Machine,”
on page 21.
3 Select the source repositories, then click Add.
The selected repositories are added to the Target Repositories pane.
4 Click OK.
The VM images are displayed.
1.4 Resynchronizing the VM Host’s State
To manually verify and ensure that the state of a VM host displayed in the Development Client is
accurate:
1 In the Development Client, right-click the VM Host, then click Discover.
To manually verify and ensure that the state of multiple VM hosts displayed in the Development
Client is accurate:
1 In the Development Client, click Provision > Resync VM Host’s State.
The Resync VM Host’s State dialog box is displayed.
16 PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
2 In the Source VM Hosts pane, select the VM hosts to be resynchronized, then click Add.
The selected VM hosts are added to the Target VM Hosts pane.
3 Click OK.
1.5 Shutting Down VM Hosts
novdocx (en) 13 May 2009
To shut down a single VM host:
1 In the Development Client, right-click the VM host you want to shut down, then click
Shutdown.
To shut down multiple VM hosts:
1 In the Development Client, click Provision > Shutdown Hosts.
The Shut Down VM Hosts dialog box is displayed.
2 You can choose to shut down the VM hosts after the Orchestrate Agent becomes idle or to
immediately shut down the VM hosts. By default, the Wait for Agent to become Idle option is
selected.
3 In the Source VM Hosts pane, select the VM hosts you want to shut down, then click Add.
The selected VM hosts are added to the Target V M Hos t s pane.
4 Click OK.
The VMs running on the host are automatically shut down and the VM host is moved to the Shutting
Down state in which it will not accept any Provisioning actions.
Managing Virtual Machine Hosts 17
Loading...