GraDS MacroGrid Carl Kesselman USC/Information Sciences Institute

MacroGrid Goals l Runtime environment for Grads Experiments l Infrastructure services for higher-level GraDS function l Clearinghouse for user-oriented resource information l Side effect: u Develop technology and tools to support specialized Grid communities

Previous Testbed Experiences l GUSTO, National Technology Grid u Many sites, no attempt to specialize, no software resources. u Scalablity issues highlighted (e.g. N 2 network performance data). l IPG, ASCI u Closed testbeds, smaller scale, stand-alone information services

GraDS MacroGrid Approach l Customized information space to capture execution space u GraDS testbed as a “virtual organization” l Web based tools to disseminate information u Oriented towards users and administrators l Additional services to support software distribution and other group activities

What is a Virtual Organization? Facilitates the workflow of a group of users across multiple domains who share [some of] their resources to solve particular classes of problems Collates and presents information about these resources in a uniform view

Virtual Organization Structure ? R R R R R ? R R R R R ? R R R R R ? RR VO A VO B VO C

Characteristics of VOs Shared resources (hardware, software, tools) Geographically dispersed Across administrative domains Differing policies for access Heterogeneous Common tasks and goals Community of users POC, web pages, mailing lists etc

Requirements for Creating a VO Unified view of collated hardware resources View of software on each resource (software, versions, patches, include libraries) Local environment info policies, installation locations Resource availability within the nodes Use Information Services as basis for creating and organizing virtual organizations.

Two Classes Of Information Servers l Resource Description Services (ResDesc) u Supplies information about a specific resource (e.g. Globus GRIS). l Aggregate Directory Services (AggDir) u Supplies collection of information which was gathered from multiple GRIS servers (e.g. Globus GIIS).

Information Protocols l Grid Resource Registration Protocol u Support information/resource discovery u Designed to support machine/network failure l Grid Resource Inquiry Protocol u Query resource description server for information u Query aggregate server for information u LDAP V3.0 in Globus 1.1.3

VO Architecture AA VO-specific AggDirs RRRR Standard ResDesc Services Registration Protocol Users Enquiry Protocol

GrADs VO Services Testbed status Software information Administrative Information Resource Availability Two VO servers set up: USC/ISI UIUC

VO Server l Server at ISI and U. Illinois u Multiple registrations per GRIS l Information cached in VO server u TTL associated with each piece of information u Access time bounded by slowest GRIS l Problems with GIIS timeout discovered and fixed l Faulty nodes discovered l Simplified configuration in next version of server

GraDS Testbed Status l Enumerate resources available on testbed u Based on service registration protocol l Available via Web page and programmatically via LDAP protocol l Limitations in current approach u Don’t have notion of GraDS compliant systems l Filtering based on basic software and functionality u Don’t distinguish between systems that are down and systems that are in the testbed

System Status

Software Information l A customized software object for GrADS l Provided by GRIS and accessed via Web page and LDAP protocol l Limited tools provided: u Template that is filled in manually l Limitations of current approach u These must be automatically generated u Not used by runtime tools. This is partly a communication issue

Software Status Page

Resource Availability l Information published through GRIS u Load averages u System configuration (CPU type, OS, etc) u Links to registered software u NWS information l Partially integrated l Easily extensible to incorporate other information

Resource Status Information

Administrative Information l Standard account pool and common map file l No tools to support mapfile dissemination u Probably adequate for current GraDS testbed

Project Milestones l Year one: u “…define….interfaces that enable information sharing across Grid compilers, runtime systems, and libraries.” l Year two: u “… create early prototypes of… runtime and testbed components, …”

MacroGrid Summary l Testbed operational for nine months u Used for two application experiments to date l Starting second iteration of testbed technology u Performance tuning, feature enhancement u Extend scope