Novell PLATESPIN ORCHESTRATE 2.0.2 - ADMINISTRATOR REFERENCE 06-17-2009, Руководство для клиента

Страница: 12 / 164

12 PlateSpin Orchestrate 2.0 VM Client Guide and Reference
no
vd
ocx
(e
n)
13
Ma
y 20
09
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.
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