PlateSpin Orchestrate 2.0 VM Client Guide and Reference
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.
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
4PlateSpin Orchestrate 2.0 VM Client Guide and Reference
8PlateSpin Orchestrate 2.0 VM Client Guide and Reference
About This Guide
This guide introduces the PlateSpin® Orchestrate VM Client, including its basic administration
environment, which is accessed through an Eclipse* rich client platform. The guide provides an
introductory overview of the VM Client, and explains how to install, monitor, and manage VMs.
The guide is organized as follows:
Chapter 1, “Overview,” on page 11
Chapter 2, “Getting Started,” on page 15
Chapter 3, “Understanding the VM Client Interface,” on page 25
Chapter 4, “Managing VM Host Servers,” on page 55
Chapter 5, “Managing Virtual Machines,” on page 67
Chapter 6, “Managing Repositories,” on page 115
Chapter 7, “Managing Templates,” on page 127
Chapter 8, “Managing Clones of Templates,” on page 141
Chapter 9, “Managing with Groups,” on page 145
novdocx (en) 13 May 2009
Chapter 10, “Troubleshooting Virtual Machine Management,” on page 149
Appendix A, “VM Installation Sources,” on page 153
Appendix B, “NPIV Terminology,” on page 155
Appendix C, “VM Client Preferences,” on page 157
Appendix E, “VM Client Documentation Quick Index,” on page 163
Audience
This book is for data center VM operators. 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 VM Client Guide and Reference, PlateSpin Orchestrate 2.0.2 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
About This Guide9
PlateSpin Orchestrate 2.0 Upgrade Guide
PlateSpin Orchestrate 2.0 High Availability Configuration Guide
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.2 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.
novdocx (en) 13 May 2009
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.
10PlateSpin Orchestrate 2.0 VM Client Guide and Reference
1
Overview
Review the following sections to understand the PlateSpin® Orchestrate VM Client from Novell®:
Section 1.1, “What Is the PlateSpin Orchestrate VM Client?,” on page 11
Section 1.2, “Understanding the Virtual Machine Life Cycle,” on page 12
Section 1.3, “Using This Guide to Manage VMs,” on page 13
1.1 What Is the PlateSpin Orchestrate VM Client?
The VM Client is a management interface that VM operators can use to manage the life cycle of the
virtual machines (VMs) in your enterprise, including creating, starting, stopping, migrating, and
deleting VMs. PlateSpin Orchestrate lets you better align IT to your business, control costs, and
minimize risks across all VM platforms in the data center. You can increase the functionality of your
data center by fully leveraging VMs as a usable resource.
novdocx (en) 13 May 2009
1
The VM Client provides management of VMs from several different virtualization host types,
including SUSE
vCenter* technology that adds VMotion* capability to ESX servers), and Microsoft* Windows
Server* 2008 with Hyper-V*.
The VM Client also allows you to manage both VMs and VM host servers in your data center. A
VM host is a server running the Orchestrate Agent.
For information on installing the VM Client, see “Installing the Orchestrate VM Client” in the
PlateSpin Orchestrate 2.0 Installation and Configuration Guide.
The VM Client provides the following:
A VM creation wizard that covers a VM’s installation source and mode, its virtualization mode,
repository, and hardware configurations
A VM editing wizard, which can also be used to edit existing VMs, even those that are in a
running state
The ability to discover existing VMs residing on your VM host servers
The ability to discover VM host servers in your virtualization grid; a machine can be a host
server if it is running hypervisor software
Methods for controlling VMs, such as starting, stopping, pausing, and suspending
The ability to migrate a running VM from one host server to another in real time
The ability to install and manage the PlateSpin Orchestrate Agent on your VMs
The ability to make templates of VMs, including making clones of the templates
The ability to move a VM’s repository from one host server to another
®
Linux Enterprise Server (SLES) Xen*, VMware* ESX Server (including the
The ability to group VMs, VM hosts, repositories, and templates for easier management
Detailed views of the properties for each VM, host server, repository, and template
The ability to monitor your VMs and host servers in real time
Event logs for VMs, host servers, and templates
Overview
11
The VM Client enhances the functionality of the PlateSpin Orchestrate Server, enabling it to control
VMs in your data center.
PlateSpin Orchestrate also provides the Development Client, where you can manage and control
data center jobs and processes through the application of rules, policies, scheduling, utilization, and
billing data center resources. For more information on the Development Client, see the PlateSpin
Orchestrate 2.0 Development Client Reference.
The VM Client and the Development Client management interfaces work together to help you to
maximize the use of VMs in your data center. You can have fewer physical machines while giving
your data center many additional resources, and you can manage the physical VM host machines
and their VMs in your data center.
The Orchestrate Server manages resources to perform work. It does this through automated jobs
(written in Jython) that in turn are broken down into joblets that are distributed among multiple
resources. For more information about PlateSpin Orchestrate and Orchestrate Server operations, see
“What You Should Know” in the PlateSpin Orchestrate 2.0 Developer Guide and Reference.
In addition, as calls for resources lessen and resources are released, the Orchestrate Server evaluates
the capabilities of the active resources (VM or physical machine) and keeps the best resource for the
job. This might include any of the currently running VMs.
novdocx (en) 13 May 2009
1.2 Understanding the Virtual Machine Life Cycle
The life cycle of a VM includes its creation, testing, modifications, use in your environment, and
removal when it’s no longer needed.
For example, in setting up your VM environment, you might want to first create basic VMs from
which you can create templates. Then, to enable the most efficient use of your current hardware
capabilities, you can use those templates to create the many different specialized VMs that you need
to perform the various jobs. You can create and manage VM-related jobs through the Development
Client interface.
Life cycle functions are performed one at a time per given VM as jobs on the host server in order to
prevent conflicts in using the VM. Life cycle events include:
Creating a VM
Starting and stopping a VM
Pausing, suspending, and resuming a VM
Installing the Orchestrate Agent on a VM
Creating a template from a VM
Using the VM (starting, stopping, pausing, suspending, restarting, and shutting down)
Running jobs for the VM
Editing a VM
Editing a template
Moving a stopped VM to another host server
Migrating a running VM to another host server
12PlateSpin Orchestrate 2.0 VM Client Guide and Reference
Resynchronizing a VM to ensure that the state of the VM displayed in the Orchestrate
Development Client is accurate
Cloning a VM from a template
To view the histories of life cycle events or why they might fail, simply review a VM’s logs. For
more information, see Section 5.2, “Using Feedback to Manage VMs,” on page 70.
1.3 Using This Guide to Manage VMs
After installing the PlateSpin Orchestrate VM Client, do the following:
1. Become familiar with the VM Client interface.
2. Start the VM Client interface.
3. Register existing VM host servers.
4. Discover the registered host servers.
5. Discover the registered VMs.
6. Log in to a virtualization grid.
novdocx (en) 13 May 2009
7. Create your VMs.
8. Install the VMs.
9. Install the Orchestrate Agent on the VMs.
10. Create templates of the VMs.
11. Add repositories.
12. Configure the VMs:
Edit a VM or template.
Delete a VM.
Delete a template.
Clone a template.
Move a VM.
Migrate a VM.
Create groups for managing VMs, host servers, repositories, and templates.
13. Use the VMs:
Understand the various VM statuses.
Start VMs.
Stop VMs.
View a VM’s server console.
Pause a VM.
Suspend a VM.
Resynchronize a host server with the Development Client.
Resynchronize a VM with the Development Client.
View logging details that are fed back from the Orchestrate Server.
View the error log for a VM.
Overview13
Open the Progress View for a VM while a life cycle function is running.
View a VM’s details.
View a host server’s details.
View a repository’s details.
View a template’s details.
14. Troubleshoot VMs.
15. Find operating system installation sources for VMs.
novdocx (en) 13 May 2009
14PlateSpin Orchestrate 2.0 VM Client Guide and Reference
2
Getting Started
To get started with the PlateSpin® Orchestrate VM Client, do the following:
Section 2.1, “Starting and Logging In to the VM Client Interface,” on page 15
Section 2.2, “Logging In to Another Virtualization Grid,” on page 19
Section 2.3, “Registering VM Hosts,” on page 20
Section 2.4, “Discovering Registered VM Hosts,” on page 21
Section 2.5, “Discovering VMs of the Registered VM Hosts,” on page 22
Section 2.6, “Registering VMs,” on page 22
2.1 Starting and Logging In to the VM Client
Interface
novdocx (en) 13 May 2009
2
You can run the VM Client on both Windows and Linux workstations:
Section 2.1.1, “Starting the Interface on a Windows Workstation,” on page 15
Section 2.1.2, “Starting the Interface on a Linux Workstation,” on page 17
2.1.1 Starting the Interface on a Windows Workstation
1 On your Windows workstation, double-click the PlateSpin Orchestrate VM Client icon () on
your desktop to open the interface.
If you do not have the icon, the executable’s location is determined by where you installed the
VM Client software. The default is
Client 2.0.2\bin\vmclient.bat
For information on multiple VM operators logging in to the VM Client, see Section 3.2.1,
“Multiple VM Operator Logins,” on page 31.
C:\Program Files\PlateSpin Orchestrate VM
.
Getting Started
15
The first time you start the VM Client, the following Welcome page is displayed:
novdocx (en) 13 May 2009
The Welcome page does not display the next time you log in to the VM Client.
The Welcome page can be accessed at any time by clicking View > Show Welcome Page.
For more information, see Section 3.1, “Understanding and Navigating the Welcome Page,” on
page 26.
2 To close the Welcome page, click Manage Your VMs to display the following login dialog box:
16PlateSpin Orchestrate 2.0 VM Client Guide and Reference
3 Specify the IP address or DNS name of a PlateSpin Orchestrate Server.
The PlateSpin Orchestrate Server is associated with a virtualization grid, which can be
associated with registered VM host servers. Therefore, logging in to one of the Orchestrate
Servers allows you to manage all VMs in the datagrid.
4 Enter a username and password to authenticate you as the administrator of the Orchestrate
Server, then click Login to view the VM Client interface:
This example shows how the interface looks the first time anyone logs in to the VM Client.
novdocx (en) 13 May 2009
5 (Conditional) If this is the first time that anyone has logged in to the VM Client, continue with
Section 2.3, “Registering VM Hosts,” on page 20 to set up the virtualization environment.
2.1.2 Starting the Interface on a Linux Workstation
1 On your Linux workstation, open a command terminal, change to the
zenworks/vmmanagement/bin/
directory (the default installation location), or to wherever
you installed the client, then enter the following command:
./vmclient.sh
For information on multiple VM operators logging in to the VM Client, see Section 3.2.1,
“Multiple VM Operator Logins,” on page 31.
/opt/novell/
Getting Started17
The first time you start the VM Client, the following Welcome page is displayed:
novdocx (en) 13 May 2009
The Welcome page does not display the next time you log in to the VM Client.
The Welcome page can be accessed at any time by clicking View > Show Welcome Page.
For more information, see Section 3.1, “Understanding and Navigating the Welcome Page,” on
page 26.
2 To close the Welcome page, click Manage Your VMs to display the login dialog box:
18PlateSpin Orchestrate 2.0 VM Client Guide and Reference
3 Specify the IP address or DNS name of a PlateSpin Orchestrate Server.
The PlateSpin Orchestrate Server is associated with a virtualization grid, which can be
associated with registered VM host servers. Therefore, logging in to an Orchestrate Server
allows you to manage all VMs in the grid.
4 Enter a username and password to authenticate you as the administrator of the Orchestrate
Server, then click Login to view the VM Client interface:
5 (Conditional) If this is the first time that anyone has logged in to the VM Client, continue with
Section 2.3, “Registering VM Hosts,” on page 20 to set up the virtualization environment.
novdocx (en) 13 May 2009
2.2 Logging In to Another Virtualization Grid
You can log in to a different Orchestrate Server at any time for access to a different virtualization
grid. However, you cannot be logged in to multiple Orchestrate Servers. If you log in to another
Orchestrate Server, the previous login is replaced.
For information on multiple VM operators logging in to the VM Client, see Section 3.2.1, “Multiple
VM Operator Logins,” on page 31.
1 In the VM Client, click File > Log In.
If you are already logged in to a virtualization grid, you can press Ctrl+Shift+I to log in to a
different datagrid.
2 Fill in the fields:
Server: Specify either the DNS name or IP address of the Orchestrate Server.
User ID: Specify a username that has admin rights on the server.
Password: Specify this user’s password.
3 Click Login.
Getting Started19
2.3 Registering VM Hosts
After being installed on a computing node, having its credentials defined, and associating itself with
the computing node, the Orchestrate Agent begins broadcasting the availability of its host as a
potential computing resource. A host is defined as a machine running a supported hypervisor agent.
However, before the Orchestrate Server can allow an agent to authenticate and establish ongoing
communication, you need to create a resource account for the agent on the Orchestrate Server. When
this account is created or “registered,” the agent’s host node can be discovered and recognized as a
computing resource that can perform the jobs assigned to it. In the Orchestrate Development Client,
you can choose to automatically or manually register a VM host server to the Orchestrate Server by
configuring the Auto Register Agents option (the Resources panel in the Authentication tab of the
datagrid). If you choose to manually register to the Orchestrate Server, the unregistered VM host
servers are displayed in the VM Client. These hosts might or might not have a supported hypervisor
installed and running on them.
To register the VM host servers:
1 In the VM Client, click Host Servers in the Inventory panel:
novdocx (en) 13 May 2009
Discovered (#) is displayed below Host Servers, where # represents the number of host servers
that are waiting to be registered with the Orchestrate Server.
2 Click Discovered (#) to display the unregistered host servers in the details section on the right.
You can accept (see Step 3) or reject (see Step 4) any of the listed host servers. The host servers
that you accept become part of your virtualization grid.
3 Accept an unregistered host server in one of the following ways:
Select the server in the details view, then click the button.
Right-click the server in the details view, then select Accept.
Select the server in the details view, then click Actions > Accept.
You can choose to register multiple host servers at a time.
20PlateSpin Orchestrate 2.0 VM Client Guide and Reference
After the host server has been registered with the Orchestrate Server, it is listed with its
operating system.
If the host server doesn’t become registered after a few minutes, run the Discover Hosts job
from the Action menu.
4 (Optional) To reject the registration of a host server, do one of the following:
Select the server in the details view, then click the button.
Right-click the server in the details view, then select Reject.
Select the server in the details view, then click Actions > Reject.
The unregistered server is removed from the Host Servers.
The next time that an unregistered host server attempts to register to the Orchestrate Server, the
rejected servers are again listed as candidates for acceptance into the virtualization grid.
5 Click the Storage view.
The only repositories shown are ZOS and the host’s local repository. ZOS is the shared datagrid
repository for all hosts to use in storing templates. For information on repositories, see
Chapter 6, “Managing Repositories,” on page 115. For information on templates, see
Chapter 7, “Managing Templates,” on page 127.
6 To discover whether there are other VM hosts in the datagrid, continue with Section 2.4,
“Discovering Registered VM Hosts,” on page 21.
novdocx (en) 13 May 2009
2.4 Discovering Registered VM Hosts
When you first install the VM Client, it is not aware of all of the possible registered VM hosts in the
virtualization grid that you log in to. The discovery process finds all hosts that have a supported
hypervisor installed and running on them.
You should discover these hosts before continuing to use the product. You should discover hosts
before attempting to discover VMs so that any VMs belonging to a particular host can be
discovered.
Before discovering the VMware technology-based hosts, ensure that the appropriate policies have
been configured in the Orchestrate Development Client. For more information on configuring the
policies, see “Configuring Policies for VM Provisioning Adapters” in the PlateSpin Orchestrate 2.0
Virtual Machine Management Guide.
To discover the existing registered VM hosts:
1 In the VM Client, click Actions > Discover Hosts.
Getting Started21
All the registered VM hosts that are in the virtualization grid and that have hypervisors
installed are displayed.
2 To discover any VMs belonging to the VM hosts that you discovered, continue with
Section 2.5, “Discovering VMs of the Registered VM Hosts,” on page 22.
2.5 Discovering VMs of the Registered VM Hosts
You can use the VMs you have previously created or the VMs you have built by using other
hypervisors in your data center. To make use of these VMs, you need to run a discover job. You use
the VM Client to detect the VMware ESX, Microsoft Hyper-V, VMware Server, VMware Virtual
Center, and SUSE
detect the VMs contained on the host machines and in other VM storage repositories.
®
Xen VM host machines. After you have detected the host machines, you can
novdocx (en) 13 May 2009
The only VMs that are automatically discovered are those that are stored in the default location of
var/lib/xen/images
storage location.
Before discovering the VMware technology-based VMs, ensure that the appropriate policies have
been configured in the Orchestrate Development Client. For more information on configuring the
policies, see “Configuring Policies for VM Provisioning Adapters” in the PlateSpin Orchestrate 2.0
Virtual Machine Management Guide.
To discover the VMs belonging to the registered VM Hosts:
1 In the VM Client, click Actions > Discover Virtual Machines.
2 To accept the discovered VMs, continue with Section 2.6, “Registering VMs,” on page 22.
, unless an Orchestrate repository is created that represents an alternative
2.6 Registering VMs
If you install the Orchestrate Agent on a VM, it must then be registered (accepted) in order to be
managed in the VM Client.
In the Orchestrate Development Client, you can choose to automatically or manually register a VM
to the Orchestrate Server by configuring the Auto Register Agents option (the Resources panel in the
Authentication tab of the datagrid). If you choose to manually register to the Orchestrate Server, the
unregistered VMs are displayed in the VM Client in the Discovered (#) group.
To regi s t e r a VM:
/
1 In the VM Client, double-click the Virtual Machines view.
22PlateSpin Orchestrate 2.0 VM Client Guide and Reference
Discovered (#) is displayed below Virtual Machines, where # represents the number of VMs
that are waiting to be registered with the Orchestrate Server.
2 Click Discovered (#) to display the unregistered VMs in the details section on the right.
You can accept (see Step 3) or reject (see Step 4) any of the listed VMs that were discovered.
The VMs that you accept become part of your virtualization grid.
3 Accept a discovered VM in one of the following ways:
Select the VM in the details view, then click the button.
Right-click the VM in the details view, then select Accept.
Select the VM in the details view, then click Actions > Accept.
You can choose to register multiple VMs at a time.
After a VM has been registered, it is listed with its operating system.
It can take a few minutes for this acceptance process to be completed. Do not proceed with
using the VMs until the acceptance process is complete.
4 (Optional) To reject a VM, do one of the following:
Select the VM in the details view, then click the button.
novdocx (en) 13 May 2009
Right-click the VM in the details view, then select Reject.
Select the VM in the details view, then click Actions > Reject.
The unregistered VM is removed from the Virtual Machines list.
The next time that an unregistered VM attempts to register to the Orchestrate Server, the
rejected VMs are again listed as candidates for acceptance into the datagrid.
If the VM is running, you can tell whether a VM has the Orchestrate Agent installed on it by
whether there are pie charts in its CPU and Memory columns.
Getting Started23
novdocx (en) 13 May 2009
24PlateSpin Orchestrate 2.0 VM Client Guide and Reference
3
Understanding the VM Client
novdocx (en) 13 May 2009
Interface
The PlateSpin® Orchestrate VM Client interface, built on an Eclipse-based rich client platform, uses
a graphical user interface (GUI) to help you create, store, edit, and use VMs. This interface can be
installed on both Windows and Linux administration devices.
Review the following sections for tips on navigating and using the VM Client interface:
Section 3.1, “Understanding and Navigating the Welcome Page,” on page 26
Section 3.2, “Understanding the VM Client Window,” on page 30
Section 3.3, “Using the Error Log,” on page 48
Section 3.4, “Using the Progress View,” on page 50
Section 3.5, “Resetting the VM Client Perspectives,” on page 51
Section 3.6, “Changing the VM Client Theme,” on page 51
3
Understanding the VM Client Interface
25
3.1 Understanding and Navigating the Welcome
Page
The Welcome page provides basic information on the VM Client. By default, it is displayed when
you first open the VM Client. Thereafter, you can access the Welcome page using Vie w > Show Welcome Page.
Figure 3-1 PlateSpin Orchestrate the VM Client Welcome Page
novdocx (en) 13 May 2009
Starting the VM Client from your desktop icon or the program’s executable does not automatically
log you in to the VM Client. This Welcome Page is available without authenticating.
To authenticate, click the Manage Your VMs button on the Welcome page to open the VM Client
Login dialog box.
The Eclipse-based VM Client GUI allows you to detach any section from the main VM Client
window. For example, you can click within the Welcome page and drag it to another location on
your desktop. This can also be done with various other sections in the VM Client, such as the
Progress View and Error Log sections.
The VM Client window is resizable, as are any sections that can be dragged out of the VM Client
window. Sections can also be resized within the full VM Client window.
Review the following sections for other navigation tips:
Section 3.1.1, “Welcome Page Main Menu Options,” on page 27
Section 3.1.2, “Welcome Page Buttons,” on page 28
26PlateSpin Orchestrate 2.0 VM Client Guide and Reference
3.1.1 Welcome Page Main Menu Options
The main VM Client menu options are available at the top of the Welcome page, but only those that
are applicable are enabled:
File > Exit: Closes the VM Client interface.
Closing the VM Client interface does not affect the status of any VMs, meaning that the VMs
that have processes running, such as cloning, starting, moving, and so on, continue to run those
processes. These processes are jobs that are being run on the servers hosting the VMs.
View > Show Welcome Page: Displays the Welcome page.
View > Show Inventory Views: Displays the Inventory panel. For more information, see
Section 3.2, “Understanding the VM Client Window,” on page 30.
View > Change Theme: Opens the Change Theme dialog box, where you can change the VM
Client’s appearance. For more information, see Section 3.6, “Changing the VM Client Theme,”
on page 51.
Help > Version Information: Opens the following dialog box:
novdocx (en) 13 May 2009
This provides software compatibility information that you might need to know when the
software is not working correctly.
To view more details for an entry, mouse over its row:
Help > Readme: Opens the product Readme in your default Web browser.
Help > VM Client Reference and Guide: Opens the product documentation for the VM Client in
your default Web browser.
Understanding the VM Client Interface27
Help > How to Use This Guide: Opens a section of the product documentation in your default
Web browser and provides a list of things you can do in the VM Client. The list is ordered in a
tutorial fashion.
Help > Index: Opens a quick index to hard-to-find VM Client information in your default Web
browser.
Help > About PlateSpin Orchestrate VM Client: Displays the following dialog box:
novdocx (en) 13 May 2009
The Configuration Details button opens the following dialog box where you can copy the textbased configuration information to your operating system’s clipboard for further use.
3.1.2 Welcome Page Buttons
The following buttons are available on the Welcome page:
“Overview” on page 29
28PlateSpin Orchestrate 2.0 VM Client Guide and Reference
“Latest Features” on page 30
“Manage Your VMs” on page 30
Overview
The Overview button provides the following information:
Figure 3-2 Welcome Page Overview
novdocx (en) 13 May 2009
To navigate to the other locations on the Welcome page, you can use the links in the upper right of
the Overview page.
Understanding the VM Client Interface29
Latest Features
The Latest Features button provides the following information:
Figure 3-3 Welcome Page Latest Features
novdocx (en) 13 May 2009
Manage Your VMs
The Manage Your VMs button opens the VM Client Login dialog box:
Figure 3-4 The VM Client Login Dialog Box
For more information on logging in to the VM Client, see Section 2.2, “Logging In to Another
Virtualization Grid,” on page 19.
3.2 Understanding the VM Client Window
Review the following sections for an understanding of the VM Client window:
Section 3.2.1, “Multiple VM Operator Logins,” on page 31
30PlateSpin Orchestrate 2.0 VM Client Guide and Reference
Loading...
+ 134 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.