Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 Reference

Also see for PLATESPIN ORCHESTRATE 2.0.2: Reference Getting started Reference Reference Upgrade guide

Contents

Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 Reference Manual pdf 59 page image

The Explorer Tree559novdocx (en) 13 May 20095The Explorer TreeThe PlateSpin ® Orchestrate Development Client from Novell® lets you visualize the modelmaintained 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 theExplorer Tree or the Explorer View. This tree lets you navigate to different objects to see theirdetails. When you navigate to these objects, you can edit their attributes and view more detail abouttheir configurations. The two objects highest in the tree are The Orchestrate Server Object (page 59)and The Server Admin Object (page 67). Each object in the Explorer Tree is referred to as a “Gridobject.” 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 Policiesassociated with them. For more information about Jobs, see Section 5.3, “The Job Object,” onpage 68. Resources: These objects represent physical or virtual machines managed by PlateSpinOrchestrate. If a resource is running the PlateSpin Orchestrate Agent, that resource can bescheduled for remote execution of a job. For more information about resources, see Section 5.4,“The Resource Object,” on page 81. VM Hosts: These objects represent a VM host technology (for example,. Xen*, Hyper-V, andso on) running on a physical resource. VM host objects can be used when making provisioningdecisions to a resource. For more information about VM hosts, see Section 5.5, “The VM HostObject,” on page 104. Repositories: These objects represent the physical or virtual storage that is accessible for VMimages or other use. For more information about repositories, see Section 5.6, “The RepositoryObject,” on page 109. Users: These objects represent the individual accounts that are allowed to connect to thePlateSpin Orchestrate Server. Administrator users are also allowed to connect by using thezosadmin command line and the PlateSpin Orchestrate Development Client user interfaces.For more information about Users, see Section 5.7, “The User Object,” on page 117.For information on creating individual user login accounts for VM operators, see “Adding UserLogins 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 healthof the object. For more information, see Appendix A, “Grid Object Health Monitoring,” onpage 133.Additional objects, such as Policies, Public JDL Libraries, Computed Facts, Events, and Metrics arealso displayed in the Explorer panel. To learn more about these other objects, see Section 5.8, “OtherDisplayed Objects,” on page 124.5.1 The Orchestrate Server ObjectThe object highest in the Explorer Tree is the Orchestrate Server Object, sometimes called the “gridserver” object because it represents the PlateSpin Orchestrate Server acting as the holding place forall of the information used to manage objects for a single computing grid.