Testbed: Status & Plans

1. Testbed: Status & Plans Charles Loomis (CNRS) Sept. 5, 2002 5th Project Conference (Budapest) charles.loomis@cern.ch (See http://documents.cern.ch/age?a021246 for trans.)

2. Software Status EDG 1.2.0 • Deployed on application testbed. • 20’ time-limit on jobs; high-rate submissions • Other bugs: replica manager, GDMP replication EDG 1.2.1 • Deployed on application testbed (CERN, Karlsruhe). • No time-limit; low-rate submissions. • Other bug: GDMP replication EDG 1.2.2 • To be tagged when GDMP rpm tested. • No time-limit; low-rate submissions.

3. Testbed Status Application Testbed (formerly “Production Testbed”) • EDG release 1.2.0 deployed on six sites. • CC-IN2P3, CERN, CNAF, Karlsruhe, NIKHEF, RAL. • Actually split into two parts: • 1.2.0 no GASS Cache hack: long jobs, low submission rate • 1.2.0 proper: 20’ limit on jobs, high submission rate • But, migrating to 1.2.1/2. • ATLAS tests in progress  See F. Harris’ WP8 talk. Development Testbed • EDG 1.2.1 installed. • Testing 1.2.2 today.

4. Sites Six main sites currently participating. • CERN, CNAF, Karlsruhe, Lyon, NIKHEF, RAL • See transparancies for individual status. • THANKS! • Markus Schulz, Emanuele Leonardi, Alessandro Cavalli, Andrea Chierici, Alessandro Italiano, Markus Hardt, Fabio Hernandez, David Groep, Jeff Templon, Steve Traylen • Beginning to see real computing power available. • Storage beginning to ramp up as well. Around 15 others waiting to join. • Other grid projects (CrossGrid, GridPP, INFN Grid,…) • More still once some national CAs are approved.

5. Certification Authority Group (D. Kelsey) CAs are under control. • Acceptance procedure working. • Added German CA; Greece made report; Poland & Slovakia by email. • Min. requirements updated (RA procedures; Online CA with special hardware.) • Scalable for future? • Procedures for establishing trust are quite involved. • ATLAS raised issue about length of time to obtain approval. Cross-domain trust. • Will participate in “CA Operations” group in GGF. Kerberos-based CAs: • CERN and FNAL interested with this. VO Authorization Issues.

6. Authorization Group (L. Gaido) Currently use LDAP-based membership services. • Will have grid-proxy-init with –vo option. • Inserts VO-name into proxy subject. • Requires patch to Globus code and change to mkgridmap. • Available 30 Sept. 2002. VO Membership Service (VOMS) • Inserts membership info into proxy as optional attributes. • Client command (voms-proxy-init), Server, and migration tools exist. • API & Admin. tools available 30 Sept. 2002. Real shift in the way we do VO-authorization.

7. Other Projects NorduGrid (Balazs Koyna) • Good communication though overlap of people. • Grid Manager: replaces gatekeeper, smart input/output staging • User Interface: contains built-in brokering. • Info. System: based on MDS, includes job monitoring, user-specific info. CrossGrid (Markus Hardt) • Close collaboration between EDG & CrossGrid testbed groups. • Significant contributions to CA group. Globus • Support shaky (distracted by OGSA, fixes supplied by others) • Find EDG effort to support/fix Globus full-time. • Reduce dependencies on Globus as much as possible.

8. Globus Version Globus 2.1.2 • Has fix from CONDOR of GASS Cache problem. • Lot of work to apply to beta-21. • Includes many additional changes job manager. • WP1 logging patches no longer work. • Whole LRMS backend changes to perl framework. Globus 2.2 • Exists, but… • Some question about what is happening with the MDS 2.2 in this. Will make Globus Release-24 and test.

9. Short Term Plans (I) EDG 1.2 series NOT suitable for widespread deployment. EDG 1.2.0 • Available now, known limitations. EDG 1.2.1 • Deploying now: long jobs, low submission rate. • Deploy multiple resource brokers to reduce problem. EDG 1.2.2 • GDMP replication fix. • Done today? Quick upgrade for sites at 1.2.1. EDG 1.2.x • Other critical fixes, but very high threshold now.

10. Short Term Plans (II) EDG 1.3 series will be widely deployed. EDG 1.3.0 • Upgrade Globus—will contain GASS cache patch from Condor. • Hopefully will also have MDS 2.2. • Subject to testing, will be deployed on application testbed. EDG 1.3.x • Clean up LCFG objects/configuration. • Modify setup to support new developer guidelines. EDG 1.4.x • Begin incremental inclusion of new middleware packages.

11. Rolling Release Autobuild procedure will run daily: • On all supported platforms (RH6.2, 7.2 now) • To build, package, and unit test HEAD version of modules. • Feedback information to developers. Middleware developers: • Use development machines to test software. • Tag package when ready for integration. • Schedule time on development testbed to test package. ITeam • Current baseline release  Add test package  New baseline release. • Will use acceptance test suite to determine if package is included.

12. Autobuild Procedure (Y. Patois) On RH6.2 • All but ~5/30 packages build and are packaged without errors. On RH7.2 • Around 10/30 packages fail the “make install” step. • All fail “make rpm” because of rpm command change. Warning: • Won’t integrate packages unless autobuild procedure works.

13. Testing Group (G. Merino) Cooperation between testing groups (combine?): • TSTG • INFN EDG Testing Group • CrossGrid test/validation group. • LCG Testing Group: • Goals: • Testing of EDG services. • Validation of new site installation & configuration. • Methodology • A priori definition of features to be tested. • Collect tests from group and from others. • Keep framework and tests in CVS.

14. Documentation Release Notes: • Exist for 1.2.0 (will be updated for 1.2.1). User’s Guide: • Exists, but should be considered draft. • Comments welcome  please use Bugzilla for this. Installation Guide: • Won’t be rewritten until Globus upgrade. • LCFG configuration files up-to-date  must move this to Installation Guide. Tutorial materials also available.