1 / 8

EDG Release Status

Update on EDG 1.2.2 deployment, including successes, known problems, testing outcomes, necessary changes, and future plans for Grid software. Focus on improving functionality and addressing issues for ATLAS evaluation.

munizr
Download Presentation

EDG Release Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EDG Release Status C. Loomis (LAL/Orsay) DataGrid France September 24, 2002 charles.loomis@cern.ch

  2. Current Deployment Application Testbed • EDG 1.2.2 • Core Sites • CC-IN2P3, CERN, CNAF, NIKHEF, RAL • Additional Sites • Karlsruhe (CrossGrid), Padova • Others waiting… • Focus on ATLAS evaluation. • Viewed generally positively. • Lots of feedback from ATLAS-EDG task force. Development Testbed • EDG 1.2.2 • Available for testing next release.

  3. EDG 1.2.2 Known Successes • Overall functionality which is useful. • Job submission is reliable. • Data management is usable. Known Problems • MDS unstable (hangs when GIIS/GRIS disappears) • 20 minute limit on file transfers • Limited to low-rate submissions (GASS cache problem) Fix problems with “binary patch” with Globus 2.1.3 services.

  4. GridFTP GridFTP server/client • Statically-linked GridFTP server built from Globus 2.1.3. • Statically-linked globus-url-copy also built. Testing • Both server/client have been tested. • 20 minute limit has indeed been fixed. Necessary Changes • Needs minor changes to EDG configuration rpms.

  5. Job Manager Software • Statically-linked JobManager built from Globus 2.1.3. • “Fork” interface exists. • PBS, LSF, Condor just received. Testing • Interaction with Gatekeeper is OK. • Basic submission works, still problem with globus-job-get-output. • Performance at high-rates much improved (39/40 simultaneous submissions) • Only “fork” tested so far, need to look at other schedulers. Necessary Changes • Needs significant changes to EDG configuration rpms. • Will have to create a BQS (perl) interface.

  6. MDS Software • Dynamically-linked MDS built from Globus 2.1.3. • Statically-link MDS built. Testing • Basic testing done on dynamic version. • Hanging problem is gone. • Have not successfully tested static version. Necessary Changes • Some minor changes to EDG configuration rpms. • Probably will require parallel Globus trees in “binary patch” release.

  7. EDG Software Data Management Software (WP2) • Depends on GridFTP libraries. • Must be recompiled and relinked. • Replica Manager • already relinked • no API changes; only reorganization of libraries • GDMP • Still remains to be done. • Will have changes in configuration and MSS interface (with WP5). Job Submission/Brokering • Change to RC lookups to improve speed. Numerous other minor fixes.

  8. Summary EDG 1.2.2 deployed on Application Testbed. • First release with usable functionality (e.g. ATLAS). • Still three significant problems with software. Moving to 1.2.x via “binary patch” to Globus • GridFTP problem in hand • JobManager additional testing but looks OK • need to write BQS interface • MDS dynamic version OK; will need parallel Globus trees Rolling Release Mode • Upgrade fully to Globus 2.1.3 (or 2.2). • Upgrade LCFG; clean distribution. • More testbed2 software…

More Related