The PlateSpin® Orchestrate Development Client from Novell® lets you visualize the model 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 The Orchestrate Server Object and The Server Admin Object. Each object in the Explorer Tree is referred to as a “Grid 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 Section 5.3, The Job Object.
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 Section 5.4, The Resource Object.
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 Section 5.5, The VM Host Object.
Repositories: These objects represent the physical or virtual storage that is accessible for VM images or other use. For more information about repositories, see Section 5.6, The Repository Object.
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 zosadmin command line and the PlateSpin Orchestrate Development Client user interfaces. For more information about Users, see Section 5.7, The User Object.
For information on creating individual user login accounts for VM operators, see Adding User Logins for VM Operators
in the PlateSpin Orchestrate 2.0 VM Client Guide and Reference.
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 Section A.0, Grid Object Health Monitoring.
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 Section 5.8, Other Displayed Objects.