Administering and Using EGO Platform EGO Version 1.2.3 January 2008 Copyright © 1994-2007 Platform Computing Corporation All rights reserved. Although the information in this document has been carefully reviewed, Platform Computing Corporation (“Platform”) does not warrant it to be free of errors or omissions. Platform reserves the right to make corrections, updates, revisions or changes to the information in this document. UNLESS OTHERWISE EXPRESSLY STATED BY PLATFORM, THE PROGRAM DESCRIBED IN THIS DOCUMENT IS PROVIDED “AS IS” AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL PLATFORM COMPUTING BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, DATA, OR SAVINGS, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS PROGRAM. We'd like to hear You can help us make this document better by telling us what you think of the content, organization, and usefulness of the information. from you If you find an error, or just want to make a suggestion for improving this document, please address your comments to [email protected]. Your comments should pertain only to Platform documentation. For product support, contact [email protected]. Document This document is protected by copyright and you may not redistribute or translate it into another language, in part or in whole. redistribution and translation Internal You may only redistribute this document internally within your organization (for example, on an intranet) provided that you continue redistribution to check the Platform Web site for updates and update your version of the documentation. You may not make it available to your organization over the Internet. Trademarks ® LSF is a registered trademark of Platform Computing Corporation in the United States and in other jurisdictions. ™ ACCELERATING INTELLIGENCE, PLATFORM COMPUTING, PLATFORM SYMPHONY, PLATFORM JOBSCHEDULER, PLATFORM ENTERPRISE GRID ORCHESTRATOR, PLATFORM EGO, and the PLATFORM and PLATFORM LSF logos are trademarks of Platform Computing Corporation in the United States and in other jurisdictions. ® UNIX is a registered trademark of The Open Group in the United States and in other jurisdictions. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. ® Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Intel®, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Other products or services mentioned in this document are identified by the trademarks or service marks of their respective owners. Third-party license http://www.platform.com/Company/third.part.license.htm agreements Third-party http://www.platform.com/Company/Third.Party.Copyright.htm copyright notices Contents Part I: Managing the Cluster ... 5 1 At a Glance: Critical Concepts .................................................................................................... 7 2 Administrative Basics ............................................................................................................... 13 3 Managing Services ................................................................................................................... 45 4 Managing Hosts ........................................................................................................................ 67 5 Managing Users ....................................................................................................................... 99 6 Monitoring Resource Allocation .............................................................................................. 111 7 Reporting ................................................................................................................................ 119 8 Reports: Data Sources ........................................................................................................... 131 9 Reports: Loader Controller ..................................................................................................... 137 10 Reports: Data Loaders ........................................................................................................... 143 11 Reports: Data Purger .............................................................................................................. 151 12 Managing Reports .................................................................................................................. 159 Part II: Managing Resource Distribution ... 175 13 Managing the Tree ................................................................................................................. 177 14 Resource Groups ................................................................................................................... 191 15 The Resource Plan ................................................................................................................. 213 Part III: Inside Platform EGO: Advanced Topics and Troubleshooting ... 251 16 Advanced Concepts and Overviews ....................................................................................... 253 17 Logs and Traces ..................................................................................................................... 267 18 Events ..................................................................................................................................... 289 Part III: Scenarios and Tutorials ... 295 Administering and Using EGO 3 4 Administering and Using EGO PART I Managing the Cluster Administering and Using EGO 5 Managing the Cluster 6 Administering and Using EGO CHAPTER 1 At a Glance: Critical Concepts Administering and Using EGO 7 At a Glance: Critical Concepts What is EGO? An overview Enterprise Grid Orchestrator™ (EGO) allows developers, administrators, and users to treat a collection of distributed software and hardware resources on a shared computing infrastructure (cluster) as parts of a single virtual computer. EGO assesses the demands of competing business services (consumers) operating within a cluster and dynamically allocates resources so as to best meet a company's overriding business objectives. These objectives might include • Reducing the time or the cost of providing key business services • Maximizing the revenue generated by existing computing infrastructure • Configuring, enforcing, and auditing service plans for multiple consumers • Ensuring high availability and business continuity through disaster scenarios • Simplifying IT management and reducing management costs • Consolidating divergent and mixed computing resources into a single virtual infrastructure that can be shared transparently between many business users EGO also provides a full suite of services to support and manage resource orchestration. These include cluster management, configuration and auditing of service-level plans, resource facilitation to provide fail-over if a master host goes down, monitoring and data distribution. EGO is only sensitive to the resource requirements of business services; EGO has no knowledge of any run-time dynamic parameters that exist for them. This means that EGO does not interfere with how a business service chooses to use the resources it has been allocated. 8 Administering and Using EGO At a Glance: Critical Concepts How does EGO work? A general overview Platform products work in various ways to match business service (consumer) demands for resources with an available supply of resources. While a specific application manager or consumer (for example, Platform Symphony or an LSF cluster) identifies what its resource demands are, EGO is responsible for supplying those resources. EGO determines the number of resources each consumer is entitled to, takes into account a consumer’s priority and overall objectives, and then allocates the number of required resources (for example, the number of slots, virtual machines, or physical machines). Once the consumer receives its allotted resources from EGO, the consumer applies its own rules and policies. How the consumer decides to balance its workload across the fixed resources allotted to it is not the responsibility of EGO. So how does EGO know the demand? Administrators or developers use various EGO interfaces (such as the SDK or CLI) to tell EGO what constitutes a “demand” for more resources. When EGO identifies that there is a demand, it then distributes the required resources based on the resource plans given to it by the administrator or developer. For all of this to happen smoothly, various components are built into EGO. Each EGO component performs a specific job. An illustrated overview of how these components fit within a larger system installation and interact with each other can be seen in the section EGO architecture. Definitions of each of the major components can be found in the section EGO components. EGO architecture EGO comprises a rich collection of cluster orchestration software components. The overall architecture is shown below: Administering and Using EGO 9 At a Glance: Critical Concepts 10 Administering and Using EGO At a Glance: Critical Concepts Important definitions About¼ Definition Client A piece of software that