DOCSLIB.ORG

Parallelism of Machine Learning Algorithms

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Parallelism of Machine Learning Algorithms 10/9/2013 Outline Condor Presented by : Walid Budgaga The Anatomy of the Grid Globus Toolkit CS 655 – Advanced Topics in Distributed Systems Computer Science Department Colorado State University 1 2 Motivation Motivation High Throughput Computing (HTC)? HTC is suitable for scientific research Large amounts of computing capacity over long Example(Parameter sweep): periods of time. Testing parameter combinations to Measured: operations per month or per year High Performance Computing (HPC)? keep temp. at particular level Large amounts of computing capacity for short periods of time op(x,y,z) takes 10 hours, 500(MB) memory, I/O 100(MB) Measured: FLOPS x(100), y(50), z(25)=> 100x50x25=125,000(145 years) 3 4 Motivation HTC Environment Fort Collins Large amounts of processing capacity? Exploiting computers on the network Science Center Utilizing heterogeneous resources Uses Condor for Overcoming differences of the platforms By building portable solution scientific projects Including resource management framework Over long periods of time? System must be reliable and maintainable Surviving failures (software & hardware) Allowing leaving and joining of resources at any time Upgrading and configuring without significant downtimes Source: http://www.fort.usgs.gov/Condor/ComputingTimes.asp 5 6 1 10/9/2013 HTC Environment HTC Also, the system must meet the needs of: Other considerations: Resource owners The distributive owned resources lead to: Rights respected Decentralized maintenance and configuration of resources Policies enforced Resource availability Customers Benefit of additional processing capacity outweigh complexity of Applications preempted at any time usage Adds an additional degree of resource heterogeneity System administrators Real benefit provided to users outweigh the maintenance cost 7 8 Condor Overview Open-source high-throughput computing framework for computing intensive tasks. Manages distributive owned resources to provide large amount of capacity Developed at the Computer Sciences Department at the University of Wisconsin-Madison Name changed to HTCondor in October 2012 9 10 Condor Overview Condor Overview Customer agent Represent the customer job(application) Can state the its requirement as following: Need a Linux/x86 platform Want the machine with the high memory capacity Prefer a machine in the lab 120 11 12 2 10/9/2013 Condor Overview Condor Overview Resource agent Matchmaker Represent the resource Matches jobs and resources Can state its offers as following: Platform: a Linux/x86 platform based on requirements and offers Memory: 1GB Can state its requirements as following: Notifies the agents when a match found Run jobs only when keyboard and mouse are idle for 15 m Run jobs only from the computer department Never run jobs belong to [email protected] 13 14 Challenges of HTC system: Software Development System Administration 15 16 Software Development Software Development Four primary challenges Utilization of heterogeneous resources: Utilization of heterogeneous resources Requires system portability obtained through layered system design • Network API : Requires system portability. • Connection-oriented and connectionless Network Protocol Flexibility • Reliable and unreliable interfaces. Required to cope with constantly changing of the resource and customer needs • Authentication and encryption Required for adding new features • Process management API : • Create , suspend, resume, Remote file access and kill a process. Required for giving ability for accessing data from any workstation • Workstation statistics API: Utilization of non dedicated resources • Reports information needed to Implement resource owner policies Required for preempt and resume application. Verify the validation of the applications requirements 17 18 3 10/9/2013 Software Development Software Development Network Protocol Flexibility: Remote file access(1): To cope with adding new services in HTC without frequently updating HTC To guarantee that HTC applications can access their data components, general purpose data format may be used from any workstation in the cluster. • Three possible solutions: • For example: Condor uses protocol similar to RPC • Using existing distributed file system (NFS) • Authenticates customer application, • Condor: • Privileges need to assigned, or • Grant file access permission 19 20 Software Development Software Development Remote file access (2): Remote file access(3): • Redirecting file I/O system calls • Implementing data file staging • Interposing HTC between application & operating system • By Linking application with an interposition library • Transferring input and output files to remote workstation • Does not require file storage on remote workstation specified by customer • Reduce performance. • Require free disk space on workstation • Difficult to develop & maintain portable interposition • High cost for large data files 21 22 Software Development Software Development Utilization of non-dedicated resources Checkpoints in Condor (1) Requires the ability for preempting and resuming application. Used as migration mechanism It can be obtained using checkpoints Job scheduler to migrate jobs from workstations to others Checkpoint: Used to resume a vacated jobs snapshot of the state of the executing program The program has the ability to checkpoint itself It can be used to restart the program at a later time Using a checkpointing library Provide reliability To provide additional reliability Enable preemptive-resume scheduling HTCondor can be configured to write checkpoints periodically 23 24 4 10/9/2013 Software Development Software Development Checkpoints in Condor (2) Checkpoints in Condor (3) When checkpoints are stored: Storing of checkpoints Periodically, if HTCondor is configured By default, At any time by the program checkpoints are stored on local disk of the machine When higher priority job has to start on the same machine where job was submitted When the machine becomes busy However, It can be configured to stored them on checkpoints server 25 26 System Administration Administrator has to answer to: Resource owners By guaranteeing that HTC enforces their policies Customers By ensuring receipt of valuable services from HTC Policy makers By demonstrating that HTC is meeting the stated goals. 28 27 System Administration System Administration Access Policies Access Policies Example from Condor: Specifies when and how the resources can be accessed and by whom The policies might be specified using a set of expressions For example in Condor: Requirements (true: to start accessing the resources) Rank (preference) Suspend Continue Vacate (notification to stop using resources) Kill (immediately stopping using the resources) 29 30 5 10/9/2013 System Administration System Administration Reliability System logs The HTC must be prepared against failures and It is primary tools for diagnosing system failures. It gives the ability to must be automate failure recover for common failure. reconstruct the events leading up to the failure . Problems and Suggested solutions It is not easy job Logs files can grow to unbounded size. Detect difference between normal and abnormal termination Detailed logs for recently events and summaries for old information Don’t leave running applications unattended Managing distributed log file Choose the correct checkpoint to restart Store logs centrally on a file server or a customized log server Decide when it is safe to restart the application Provide single interface by installing logging agents on each workstation Determine & avoid bad nodes 31 32 System Administration System Administration Monitoring and Accounting CondorView Usage Graph It helps the Administrator to: Assess the current and historical state of the system Track the system usage 33 34 System Administration System Administration Security (1) Security (2) Possible attacks To protect against an unauthorized of resource access policy Resource attack Resource owner may specify authorized users in his access policy Unauthorized user gains access to a resource Condor Example: Authorized user violates resource owner’s access policy Requirement = (Customer == “[email protected]”) || Customer attack ( Customer == “[email protected]”) Customer’s account or files are risked via HTC environment 35 36 6 10/9/2013 System Administration System Administration Security (3) Security (4) To protect against violations of resource access policy, To protect the customer’s account and files The resource agent may: HTC must ensure that all resource agents are trustworthy Set resource consumption limit by using system API Placing data files only on trusty hosts Run the application under “guest” account Using authentication mechanism Set file system root directory to “sandbox” directory Encrypting network streams Intercept the system calls performed by app. via OS interposition interface 37 38 System Administration Remote Customers Remote access is more convenient than direct access Customer creates an HTC account Customer agent can be installed on customer workstation The administrator allows this agent to access the HTC cluster For non- trustworthy customers, extra security procedures may be required 39 40 Condor Condor Condor is suitable for high throughput computations Running programs unattended and in the background Redirecting console input & outputs from and to files Running many
Load more

Recommended publications
  • Grid Computing: What Is It, and Why Do I Care?*
    Grid Computing: What Is It, and Why Do I Care?* Ken MacInnis <[email protected]> * Or, “Mi caja es su caja!” (c) Ken MacInnis 2004 1 Outline Introduction and Motivation Examples Architecture, Components, Tools Lessons Learned and The Future Questions? (c) Ken MacInnis 2004 2 What is “grid computing”? Many different definitions: Utility computing Cycles for sale Distributed computing distributed.net RC5, SETI@Home High-performance resource sharing Clusters, storage, visualization, networking “We will probably see the spread of ‘computer utilities’, which, like present electric and telephone utilities, will service individual homes and offices across the country.” Len Kleinrock (1969) The word “grid” doesn’t equal Grid Computing: Sun Grid Engine is a mere scheduler! (c) Ken MacInnis 2004 3 Better definitions: Common protocols allowing large problems to be solved in a distributed multi-resource multi-user environment. “A computational grid is a hardware and software infrastructure that provides dependable, consistent, pervasive, and inexpensive access to high-end computational capabilities.” Kesselman & Foster (1998) “…coordinated resource sharing and problem solving in dynamic, multi- institutional virtual organizations.” Kesselman, Foster, Tuecke (2000) (c) Ken MacInnis 2004 4 New Challenges for Computing Grid computing evolved out of a need to share resources Flexible, ever-changing “virtual organizations” High-energy physics, astronomy, more Differing site policies with common needs Disparate computing needs
    [Show full text]
  • GT 4.0 RLS GT 4.0 RLS Table of Contents
    GT 4.0 RLS GT 4.0 RLS Table of Contents 1. Key Concepts .................................................................................................................................. 1 1. Overview of Data Management in GT4 ........................................................................................ 1 2. Data movement ........................................................................................................................ 1 3. Data replication ....................................................................................................................... 2 4. Higher level data services .......................................................................................................... 4 2. 4.0.0 Release Note ............................................................................................................................ 5 1. Component Overview ............................................................................................................... 5 2. Feature Summary ..................................................................................................................... 5 3. Bug Fixes ............................................................................................................................... 5 4. Known Problems ...................................................................................................................... 6 5. Technology Dependencies .........................................................................................................
    [Show full text]
  • A Globus Primer Or, Everything You Wanted to Know About Globus, but Were Afraid to Ask Describing Globus Toolkit Version 4
    A Globus Primer Or, Everything You Wanted to Know about Globus, but Were Afraid To Ask Describing Globus Toolkit Version 4 An Early and Incomplete Draft Please send comments, criticisms, and suggestions to: [email protected] Preface The Globus Toolkit (GT) has been developed since the late 1990s to support the development of service-oriented distributed computing applications and infrastructures. Core GT components address basic issues relating to security, resource access and management, data movement and management, resource discovery, and so forth. A broader “Globus universe” comprises numerous tools and components that build on core GT4 functionality to provide many useful application- level functions. These tools have been used to develop many Grid systems and applications. Version 4 of the Globus Toolkit, GT4, released in April 2005, represents a significant advance relative to the GT3 implementation of Web services functionality in terms of the range of components provided, functionality, standards conformance, usability, and quality of documentation. This document is intended to provide a first introduction to key features of both GT4 and associated tools, and the ways in which these components can be used to develop Grid infrastructures and applications. Its focus is on the user’s view of the technology and its application, and the practical techniques that should be employed to develop GT4-based applications. We discuss in turn the applications that motivate the development of GT4 and related tools; the four tasks involved in building Grids: design, deployment, application, operations; GT4 structure, including its Web services (WS) and pre-WS components; the Globus universe and its various components; GT4 performance, scalability, and functionality testing; porting to GT4 from earlier versions of GT; who’s using GT4; likely future directions, and a few words of history.
    [Show full text]
  • The Advanced Resource Connector User Guide
    NORDUGRID NORDUGRID-MANUAL-6 7/12/2010 The NorduGrid/ARC User Guide Advanced Resource Connector (ARC) usage manual 2 Contents 1 Preface 11 2 Roadmap 13 3 Client Installation 15 3.1 Beginner Installation . 15 3.1.1 Download . 15 3.1.2 Unpack . 15 3.1.3 Configure . 16 3.2 System-wide installation . 16 3.2.1 Installation via repositories . 17 3.2.2 Globus Toolkit . 18 3.2.3 Download the client . 18 3.2.4 Build . 19 3.2.5 Install the client . 20 3.3 Client configuration files . 21 3.3.1 client.conf . 21 3.3.2 srms.conf . 23 3.3.3 Deprecated configuration files . 24 4 Grid Certificates 25 4.1 Quick start with certificates . 25 4.1.1 Certificates in local standalone client . 25 4.1.2 Certificates for system-wide client installation . 27 4.1.3 Obtain a personal certificate . 27 4.2 Grid Authentication And Certificate Authorities . 28 4.2.1 Grid Login, Proxies . 28 4.2.2 Certificate Authorities . 29 4.2.3 Globus Grid certificates . 29 4.2.4 Associating yourself with a proper CA . 30 4.2.5 Friendly CAs . 31 4.2.6 Certificate Request . 32 4.2.7 Working with certificates: examples . 33 3 4 CONTENTS 5 Getting Access to Grid Resources: Virtual Organisations 35 5.1 NorduGrid Virtual Organisation . 35 5.2 Other Virtual Organisations . 36 6 Grid Session 37 6.1 Logging Into The Grid . 37 6.1.1 Proxy Handling Tips . 38 6.2 First Grid test . 38 6.3 Logging Out .
    [Show full text]
  • Reflections on Building a High-Performance Computing Cluster Using Freebsd
    Reflections on Building a High-performance Computing Cluster Using FreeBSD NYCBUG March 2008 Brooks Davis The Aerospace Corporation El Segundo, California, USA http://people.freebsd.org/~brooks/pubs/meetbsd2007/ © Copyright 2007 The Aerospace Corporation Outline ● Fellowship Overview ● Evaluation of Design Issues ● Lessons Learned ● Thoughts on Future Clusters ● Conclusions A Brief History of Fellowship ● Started in 2001 ● Primarily motivated by the needs of the GPS program office ● Intended to be a corporate resource – Diverse set of users Fellowship Hardware ● 352 dual-processor nodes – 64 Quad-core Woodcrest Xeons – 288 Opterons (152 dual-core) – 1-4GB RAM, 80-250GB disk ● 6 core systems – fellowship – shell server – fellowship64 – amd64 shell server – arwen – node netboot server, scheduler, NIS, DNS, Mathematica License Server – elrond – /scratch – moria – NetApp FAS250 /home, /usr/aero Fellowship Circa February, 2007 Fellowship Composition by processor count Fellowship Composition by core count Fellowship Network r01n01 r01n02 fellowship r01n03 ... frodo r02n01 10.5.0.0/16 Aerospace gamgee r02n02 r02n03 Network arwen Cat6509 ... elrond r03n01 r03n01 r03n02 moria r03n02 r03n03 r03n03 ... ... Fellowship Software ● FreeBSD 6.2-RELEASE-p8 ● Sun Grid Engine (SGE) 6.0u11 ● Message Passing Interface (MPI) – MPICH – MPICH2 – OpenMPI ● PVM ● Mathematica ● Matlab Design Issues ● The Issue ● What We Did ● How it worked Operating System ● FreeBSD 4.x initially – Many years of service – Userland threading forced some application design choices
    [Show full text]
  • Experimental Study of Remote Job Submission and Execution on LRM Through Grid Computing Mechanisms
    Experimental Study of Remote Job Submission and Execution on LRM through Grid Computing Mechanisms Harshadkumar B. Prajapati Vipul A. Shah Information Technology Department Instrumentation & Control Engineering Dharmsinh Desai University Department Nadiad, INDIA Dharmsinh Desai University e-mail: [email protected], Nadiad, INDIA [email protected] e-mail: [email protected], [email protected] Abstract —Remote job submission and execution is The fundamental unit of work-done in Grid fundamental requirement of distributed computing done computing is successful execution of a job. A job in using Cluster computing. However, Cluster computing Grid is generally a batch-job, which does not interact limits usage within a single organization. Grid computing with user while it is running. Higher-level Grid environment can allow use of resources for remote job services and applications use job submission and execution that are available in other organizations. This execution facilities that are supported by a Grid paper discusses concepts of batch-job execution using LRM and using Grid. The paper discusses two ways of middleware. Therefore, it is very important to preparing test Grid computing environment that we use understand how a job is submitted, executed, and for experimental testing of concepts. This paper presents monitored in Grid computing environment. experimental testing of remote job submission and Researchers and scientists who are working in higher- execution mechanisms through LRM specific way and level Grid services and applications do not pay much Grid computing ways. Moreover, the paper also discusses attention to the underlying Grid infrastructure in their various problems faced while working with Grid published work.
    [Show full text]
  • Introduction to Grid Computing with the Globus Toolkit Version 3 Page 1 Colorado Software Summit: October 26 – 31, 2003 © Copyright 2003, IBM Corporation
    Colorado Software Summit: October 26 – 31, 2003 © Copyright 2003, IBM Corporation Introduction to Grid Programming with the Globus Toolkit Version 3 Michael Brown IBM Linux Integration Center Austin, Texas Michael Brown – Introduction to Grid Computing with the Globus Toolkit Version 3 Page 1 Colorado Software Summit: October 26 – 31, 2003 © Copyright 2003, IBM Corporation Session Introduction Who am I? ➢ [email protected] ➢ Team Leader for Americas Projects ➢ IBM Linux Integration Center, Austin ➢ Author on 2 IBM Redbooks about Globus 3 What will we talk about ? ➢ Recent history of grid computing ➢ Intro to the galaxy of Globus ➢ Run a Globus V3 example (fingers crossed) Michael Brown – Introduction to Grid Computing with the Globus Toolkit Version 3 Page 2 Colorado Software Summit: October 26 – 31, 2003 © Copyright 2003, IBM Corporation Introduction to Grid Computing Don't panic: it's just the new word for distributed computing We want to exploit resources on a wide, loose network ➢ Not a cluster, but heterogeneous systems ➢ CPU, storage, software, devices, all w/quality-of-service We started small in the early days with file copying, printing Later we moved to program-program communication We have to solve the same problems every time ➢ Comms protocol, data format, security, management Why can't we just focus on the high-level tasks? Please? ➢ Leverage existing standards ➢ Follow accepted patterns Michael Brown – Introduction to Grid Computing with the Globus Toolkit Version 3 Page 3 Colorado Software Summit: October 26 – 31,
    [Show full text]
  • The Globus Toolkit Lecture of the Course of Complements of Enabling Platforms
    The Globus Toolkit Lecture of the course of Complements of Enabling Platforms Master in Computer Science and Networking - SSSUP, UNIPI Gianmarco Saba Contents 1 Introduction to the Globus Toolkit .................... 1-1 2 Grid Security .................................. 2-1 3 Globus Upper Layers ............................. 3-1 4 Grid Information Services .......................... 4-1 5 Grid Resource Management ......................... 5-1 6 Grid Data Management ........................... 6-1 1 Introduction to the Globus Toolkit 1.1 Examples of the Globus Impact ..................... 1-1 1.2 General Approach ..................................... 1-2 Gianmarco Saba 1.3 Evolution of the Globus Toolkit..................... 1-4 [email protected] 1.4 Web Services ........................................... 1-5 The Globus Toolkit 1 is a software toolkit addressing key technical problems in the development of Grid Enabled Tools, services and applications. It offers a modular ”bag of technologies”, enables in- cremental development of Grid-enabled tools and applications and implements standard Grid protocols and API’s (the ”core” of the so called hourglass). The inventors decided to provide not just an oper- ating system of which you don’t know anything of what is going on 0.1 inside, but they provided a small set of independent technologies in such a way that if I provide 3, 4 basic technologies, you can use just the one you need for your particular grid and you can completely forget the others; you don’t have to install the whole middleware to have a grid. If you are just interested in grid security, you can completely forget Resource Management, File Transfers, Information Management: just build the grid. This has been decided and ac- cording to the hourglass model that we have seen, on this few components we build some more components in such a way to provide an incremental association of tools according to this model.
    [Show full text]
  • A Grid Computing Framework for Mobile Devices
    AN ANDROID APPROACH TO THE WEB SERVICES RESOURCE FRAMEWORK by Adriana Garcia Kunzel A Thesis Submitted to the Faculty of The College of Engineering and Computer Science in Partial Fulfillment of the Requirements for the Degree of Master of Science Florida Atlantic University Boca Raton, Florida August 2010 Acknowledgments I would like to thank my husband Sebastian and my mother Elizabeth for being there with me during my graduate studies; without your support this journey would not have been possible. I would also like to thank Dr. Shihong Huang, Dr. Hari Kalva and Dr. Imad Mahgoub; your teachings have opened my mind to the research world and have changed me as a professional and as an individual. A very special thank you goes out to Dr. Junwei Cao and his team at Tsinghua University in Beijing China, your input was essential part of this work. Additionally, I would like to thank Dr. Maria Petrie for giving me the opportunity of being part of the Florida Atlantic University and supporting me over the course of my master’s degree. Finally, I would like to thank at the Florida Atlantic University’s faculty and staff for their support and encouragement. Your kindness and friendship have made my time here unforgettable. iii Abstract Author: Adriana Garcia Kunzel Title: An Android Approach to the Web Services Resource Framework Institution: Florida Atlantic University Thesis Advisor: Dr. Shihong Huang Degree: Master of Science Year: 2010 Web services have become increasingly important over the past decades. Versatility and platform independence are just some of their advantages. On the other hand, grid computing enables the efficient distribution of computing resources.
    [Show full text]
  • GT4 Admin Guide GT4 Admin Guide
    GT4 Admin Guide GT4 Admin Guide Published February 2005 Table of Contents 1. Introduction .................................................................................................................................... 1 2. Before you begin .............................................................................................................................. 2 3. Software Prerequisites ....................................................................................................................... 3 Required software ........................................................................................................................ 3 Optional software ........................................................................................................................ 3 Platform Notes ............................................................................................................................ 4 Apple MacOS X .................................................................................................................. 4 Debian ............................................................................................................................... 4 Fedora Core ........................................................................................................................ 4 FreeBSD ............................................................................................................................ 4 HP/UX .............................................................................................................................
    [Show full text]
  • Tutorial 1: Introduction to Globus Toolkit
    Tutorial 1: Introduction to Globus Toolkit Prof. Richard Sinnott Dr. John Watt The Globus Project (1995) Consortium dedicated to collaborative design, development, testing and support of Globus U.S. Argonne National Laboratory University of Southern California/Information Sciences Institute University of Chicago The Globus Alliance (2003) New members form an international consortium Swedish Centre for Parallel Computers (PDC) Edinburgh Parallel Computing Centre (EPCC) Includes Academic Affiliates program with participation from Asia-Pacific, Europe and US US Federal sponsorship NASA, DoE, NSF, DARPA Industry sponsorship IBM, Microsoft Research The Globus Toolkit (1998-) An open-architecture, open-source set of software services and libraries that support computational grids. Components can be used independently or together to develop useful grid applications. “the de facto standard for grid computing” - New York Times Accolades R&D Magazine R&D100 Award: "Most Promising New Technology” ,2002 MIT Technology Review: "Ten Technologies That Will Change the World” ,2003 Globus Toolkit timeline GT1 (1998) GRAM and MDS GT2 (2001) GridFTP, The Grid Packaging Toolkit (GPT) GT3 (2002) Implementation of the Open Grid Services Architecture (OGSA) GT4 (2005) Implementation of the Web Services Resource Framework (WSRF) We will work with GT3.3 Allows an introduction to Grid Service implementation with stable, production standard software Is compatible with other Grid apps (Condor, PERMIS) Implements OGSA not WSRF WSRF is the (current) goal for Web Services standardisation Learning OGSA is a good introduction to WS Implementation of the two is very similar OGSA: GT3 Overview GT3 Core Container, APIs, Runtime env GT3 Security SOAP, GSI GT3 Base GRAM, MDS, RFT GT3 Data & Other GridFTP, RLS….
    [Show full text]
  • Grid Computing with the IBM Grid Toolbox Rid Toolbox
    Front cover Grid Computingg with the IBM Gridrid Toolbox Introduces IBM Grid Toolbox V3 for Multiplatforms V1.1 Demonstrates installation and use Outlines sample services Luis Ferreira, Lee B Wilson, Dennis Mosby, Antonio Castro, Michael Brown, Luis G Kiatake, Bradley Smoley, Jon Rossow, and Darwin Dumonceaux ibm.com/redbooks International Technical Support Organization Grid Computing with IBM Grid Toolbox May 2004 SG24-6332-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (May 2004) This edition applies to the IBM Grid Toolbox V3 for Multiplatforms V1.1. © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . x Preface . xi The team that wrote this redbook. xii Become a published author . xv Comments welcome. xv Chapter 1. Introduction. 1 1.1 Introduction to Grid Computing . 2 1.2 Open Standards . 2 1.2.1 Web services. 3 1.2.2 Open Grid Services Architecture (OGSA). 3 1.2.3 Open Grid Services Infrastructure (OGSI) . 3 1.2.4 Grid services . 4 1.2.5 The Globus Alliance . 5 1.2.6 Future directions on grid services . 5 1.3 Introduction to the IBM Grid Toolbox. 6 1.3.1 IBM Grid Toolbox goals. 7 1.3.2 Platform support and availability . 8 1.4 An overview of IBM Grid Toolbox components . 9 1.4.1 Hosting environment . 10 Chapter 2. Planning. 11 2.1 IBM Grid Toolbox packaging .
    [Show full text]