User manual NOVELL PLATESPIN ORCHESTRATE 2.0.2 ADMINISTRATOR REFERENCE 06-17-2009

[. . . ] novdocx (en) 13 May 2009 AUTHORIZED DOCUMENTATION Administrator Reference Novell® 2. 0. 2 June 17, 2009 PlateSpin® Orchestrate www. novell. com PlateSpin Orchestrate 2. 0 Administrator Reference novdocx (en) 13 May 2009 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. 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. 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. [. . . ] It is run each time a new resource appears and once every 24 hours to ensure validity of the resources. For a more detailed review of this example, see "osInfo. job" in "Using PlateSpin Orchestrate Jobs" in the PlateSpin Orchestrate 2. 0 Developer Guide and Reference. System Jobs Jobs can be scheduled to to periodically trigger specific system resources based on specific time constraints or events. As shown in the following figure, PlateSpin Orchestrate provides a built-in job scheduler that enables you or system administrators to flexibly deploy and run jobs. 16 PlateSpin Orchestrate 2. 0 Administrator Reference novdocx (en) 13 May 2009 Figure 1-4 The Job Scheduler For more information, see "Resource Selection" in "Using PlateSpin Orchestrate Jobs" in the PlateSpin Orchestrate 2. 0 Developer Guide and Reference and "The PlateSpin Orchestrate Job Scheduler" in the PlateSpin Orchestrate 2. 0 Development Client Reference. See also "Job Scheduling" and "Job" in the PlateSpin Orchestrate 2. 0 Developer Guide and Reference. Provisioning Jobs Jobs also drive provisioning for virtual machines and blade servers. Provisioning adapter jobs are deployed and organized into appropriate job groups for management convenience. Provisioning adapters are deployed as part of your VMM license. For more information, see "Virtual Machine Management" in the "PlateSpin Orchestrate 2. 0 Developer Guide and Reference" and Section 1. 2. 1, "Resource Virtualization, " on page 20. 1. 1. 5 Constraint-Based Job Scheduling The Orchestrate Server is a "broker" that can distribute jobs to every "partner" agent on the grid. Based on assigned policies, jobs have priorities and are executed based on the following contexts: User Constraints User Facts Job Constraints Job Facts Job Instance Resource User Constraints Resource Facts Groups Basic PlateSpin Orchestrate Concepts 17 novdocx (en) 13 May 2009 Each object in a job context contains the following elements: Figure 1-5 Constraint-Based Resource Brokering For more information, see "Working with Facts and Constraints" in the PlateSpin Orchestrate 2. 0 Developer Guide and Reference. 1. 1. 6 Understanding PlateSpin Orchestrate API Interfaces There are three API interfaces available to the Orchestrate Server: Orchestrate Server Management Interface: The PlateSpin Orchestrate Server, written entirely in Java using the JMX (Java MBean) interface for management, leverages this API for the PlateSpin Orchestrate Development Client. The Development Client is a robust desktop GUI designed for administrators to apply, manage, and monitor usage-based policies on all infrastructure resources. The Development Client also provides at-a-glance grid health and capacity checks. For more information, see the PlateSpin Orchestrate 2. 0 Development Client Reference. 18 PlateSpin Orchestrate 2. 0 Administrator Reference novdocx (en) 13 May 2009 Figure 1-6 PlateSpin Orchestrate Development Client Job Interface: Includes a customizable/replaceable Web application and the zosadmin command line tool. The Web-based Server Portal built with this API provides a universal job viewer from which job logs and progress can be monitored. The job interface is accessible via a Java API or CLI. A subset is also available as a Web Service. The default PlateSpin Orchestrate Server Portal leverages this API. It can be customized or alternative J2EE* application can be written. PlateSpin Orchestrate Monitoring System: Monitors all aspects of the data center through an open source, Eclipse*-based interrface referred to as the PlateSpin Orchestrate VM Client. This interface operates in conjunction with the Orchestrate Server and monitors the following objects: Deployed jobs that teach PlateSpin Orchestrate and provide the control logic that PlateSpin Orchestrate runs when performing its management tasks. Users and Groups Virtual Machines For more information, see the PlateSpin Orchestrate 2. 0 VM Client Guide and Reference. Basic PlateSpin Orchestrate Concepts 19 novdocx (en) 13 May 2009 Figure 1-7 The PlateSpin Orchestrate VM Client Interface 1. 2 Understanding PlateSpin Orchestrate Functionality Section 1. 2. 1, "Resource Virtualization, " on page 20 Section 1. 2. 2, "Policy-Based Management, " on page 21 Section 1. 2. 3, "Grid Object Visualization, " on page 21 Section 1. 2. 4, "Understanding Job Semantics, " on page 22 Section 1. 2. 5, "Distributed Messaging and Failover, " on page 23 Section 1. 2. 6, "Web-Based User Interaction, " on page 24 1. 2. 1 Resource Virtualization Host machines or test targets managed by the Orchestrate Server form nodes on the grid (sometimes referred to as the matrix). All resources are virtualized for access by maintaining a capabilities database containing extensive information (facts) for each managed resource. This information is automatically polled and obtained from each resource periodically or when it first comes online. The extent of the resource information the system can gather is customizable and highly extensible, controlled by the jobs you create and deploy. [. . . ] Multicasting might not function correctly on systems that lack a default route. Attempts to send messages on such systems fail with a Network Unreachable message because the operating system is unable to determine the correct network interface on which to send the message. The quick solution is to add a default route on such systems. In some environments, however, it might not make sense to add a default route. [. . . ]