2005 GRIDS Community Workshop1 Learning From Cyberinfrastructure Initiatives Grid Research Integration Development & Support

2005 GRIDS Community Workshop2 Welcome to Chicago!

2005 GRIDS Community Workshop3 Logistics

2005 GRIDS Community Workshop4 Introductions

2005 GRIDS Community Workshop5 Why Are We Here? GRIDS work –Identify priorities for the coming year –Identify system integration opportunities Your work –Learn from each other’s experiences –Identify opportunities to leverage work from other CI projects –Identify partnership opportunities

2005 GRIDS Community Workshop6 NSF Middleware Initiative NMI is a program of NSF’s Division for Shared Cyberinfrastructure (SCI) 4 System Integrators –GRIDS - Grid software integration –EDIT - Campus IT system integration –OGCE - Grid portal tools and frameworks –CIMA - Instrument and sensor networks Middleware Development Projects Middleware Deployment Projects

2005 GRIDS Community Workshop7 GRIDS Center Goal Ease the information technology burden on Grid deployment efforts for e-Science and cyberinfrastructure. Teragrid BIRN NEES Open Science Grid UK e-Science LOOKING EGEE NEON GEON LEAD LIGO And many more!

2005 GRIDS Community Workshop8 GRIDS In Action Delivery of Customized Services –Develop and deliver the services needed by deployment initiatives –Success measured by volume, breadth of use Community Engagement –Work side-by-side with deployment projects to identify needs, provide services –Success measured by perceived value of contributions

2005 GRIDS Community Workshop9 Distributed Builds Facility Automatically generates customized software builds and distributions for deployment projects –Regularly scheduled builds –Multi-platform builds –Distributed builds Used to produce important Grid “software stacks” –GRIDS software releases (of course) –Globus Toolkit 4.0 releases –Condor releases –Rocks - GRIDS roll –Open Science Grid - VDT releases –NEW: Teragrid GIG software

2005 GRIDS Community Workshop10 Integrated Solutions Useful combinations of NMI components –Recognizing and reproducing useful integrations from cyberinfrastructure projects –Avoids redundant integration –Simplifies use in CI initiatives For example: –Portal-based User Registration Service (from ESG) –Data Replication Service (from LIGO) –System Monitoring Service (from ESG) –TeraGrid Copy or TGCP (from TeraGrid) –Workspace Management Service (from EGEE)

2005 GRIDS Community Workshop11 Documentation An essential element of development for reuse, but typically not a priority in R&D projects GRIDS invested in GT4 documentation –Improvements in breadth, depth, and organization –Recognized by everyone as a significant improvement

2005 GRIDS Community Workshop12 Education/Training Customized training materials –Customized course content for 2004 and 2005 OSG/GriPhyN/iVDGL Summer Grid School –Custom course for LIGO LSC Workshop –“Beyond Globus: Lessons Learned from the Grid” at GGF-10, GGF-11, SC04, GlobusWORLD 2005 –Full day tutorial with lab exercises: “Working with Grids: Just Do It!” at GlobusWorld 2005 –Full day tutorial with lab exercises: “Build a Grid Service with GT4” at GlobusWorld, Edinburgh, China, UCSD, NCSA –Grid Primer at UCSD, NCS, Kansas City

2005 GRIDS Community Workshop13 Customized Consultation Helping application deployment efforts to plan… –Architectural questions –Component selection –Standards use –Methodology and best practices Examples –LTERgrid architecture document –BIRN/GEON/LTER security consulting/solutions –NEON IT strategy consultation –TeraGrid software packaging & deployment team –TeraGrid user portal and information services –LOOKING architecture discussions –OSG GT4 deployment plans –you know who you are…

2005 GRIDS Community Workshop14 Integrative Testing Framework Software –A Grid workflow system for software testing –Full separation between the build and test processes –Automated deployment and configuration –Integrates with developer source repositories –Support routine/repeatable testing, monitoring test results, and routing test results to responsible individuals Hardware –Large pool of systems at UWM –Systems at ISI –Ability to add systems dynamically (e.g., Teragrid)

2005 GRIDS Community Workshop15 Last Year’s Workshop Workshop revealed common themes –Security features (registration, credential management, authorization, auditing) –Data management (replication, integration with storage systems) –Builds, testing, and deployment validation Two key points –Developing components is not sufficient. Consultation on planning and architecture is also needed. –There is no “one size fits all” solution. Each community has unique requirements, especially regarding deployment.

2005 GRIDS Community Workshop16 You Are Not Alone Your projects are each important parts of the larger cyberinfrastructure community. –Every NSF division has CI initiatives underway. –Other agencies and countries have similar activities. NSF’s Shared Cyberinfrastructure (SCI) Division is charged with supporting you. –NSF Middleware Initiative (NMI) –GRIDS Center –Open Grid Collaborative Environment (OCGE) –Enterprise and Desktop Integration Technologies (EDIT) –Globus Alliance –Condor –And many others… The CI community must learn from your experiences.

2005 GRIDS Community Workshop17 Keep Talking Each CI initiative has a unique scientific focus. All CI initiatives have IT in common. –Stay in touch with GRIDS and other NMI system integrators. –Stay in touch with peers in other CI initiatives. –Share your experiences, successes, lessons. –Leverage each other’s resources. –Track community standards.

2005 GRIDS Community Workshop18 For Example Clear successes –BIRN’s use of Rocks for infrastructure deployment –NEESgrid’s experiment-based deployment technique –OSG’s governance model Things to watch –LOOKING’s service-oriented science model –TeraGrid’s science gateways & user portal –TeraGrid and OSG interoperability

2005 GRIDS Community Workshop19 Agenda Deployment Issues CI Projects - Requirements and Status Broadening Access to HPC Capabilities Data-intensive Science In each area, we will hear from CI projects with relevant experiences. In each area, we will discuss opportunities and priorities.

2005 GRIDS Community Workshop20 Expected Outcomes You will go away with things to follow up on. –Potential partnerships with other CI projects –Solutions from other CI projects –Potential partnerships with GRIDS –Useful “tricks” from other projects GRIDS will learn how to help you. –Training and consultation –Integrated solutions –Build and test facility –Anything else…