Table of Contents
Advertisement
The Explorer Tree
5
®
The PlateSpin
Orchestrate Development Client from Novell
maintained by the Orchestrate Server used to make Virtual Machine (VM) provisioning decisions.
The left pane of the Orchestrate Development Client displays a hierarchical tree known as the
Explorer Tree or the Explorer View. This tree lets you navigate to different objects to see their
details. When you navigate to these objects, you can edit their attributes and view more detail about
their configurations. The two objects highest in the tree are
and
The Server Admin Object (page
object." Most Grid objects can also be associated with one or more containers called Groups.
The primary Grid objects include the following:
Jobs: These objects are deployed to the Orchestrate Server to automate processes, such as on-
demand provisioning. Jobs consist of JDL scripts(s) and might have one or more Policies
associated with them. For more information about Jobs, see
page
68.
Resources: These objects represent physical or virtual machines managed by PlateSpin
Orchestrate. If a resource is running the PlateSpin Orchestrate Agent, that resource can be
scheduled for remote execution of a job. For more information about resources, see
"The Resource Object," on page
VM Hosts: These objects represent a VM host technology (for example,. Xen*, Hyper-V, and
so on) running on a physical resource. VM host objects can be used when making provisioning
decisions to a resource. For more information about VM hosts, see
Object," on page
104.
Repositories: These objects represent the physical or virtual storage that is accessible for VM
images or other use. For more information about repositories, see
Object," on page
109.
Users: These objects represent the individual accounts that are allowed to connect to the
PlateSpin Orchestrate Server. Administrator users are also allowed to connect by using the
command line and the PlateSpin Orchestrate Development Client user interfaces.
zosadmin
For more information about Users, see
For information on creating individual user login accounts for VM operators, see
Logins for VM
Operators" in the
Grid objects can be visualized in various ways. One of the most important of these depicts the health
of the object. For more information, see
page
133.
Additional objects, such as Policies, Public JDL Libraries, Computed Facts, Events, and Metrics are
also displayed in the Explorer panel. To learn more about these other objects, see
Displayed Objects," on page
5.1 The Orchestrate Server Object
The object highest in the Explorer Tree is the Orchestrate Server Object, sometimes called the "grid
server" object because it represents the PlateSpin Orchestrate Server acting as the holding place for
all of the information used to manage objects for a single computing grid.
67). Each object in the Explorer Tree is referred to as a "Grid
81.
Section 5.7, "The User Object," on page
PlateSpin Orchestrate 2.0 VM Client Guide and
Appendix A, "Grid Object Health Monitoring," on
124.
®
lets you visualize the model
The Orchestrate Server Object (page 59)
Section 5.3, "The Job Object," on
Section 5.5, "The VM Host
Section 5.6, "The Repository
Section 5.8, "Other
5
Section 5.4,
117.
"Adding User
Reference.
The Explorer Tree
59
Advertisement
Table of Contents
