EGEE/OSG interoperability

1. EGEE/OSG interoperability EGEE OSG Interoperability

2. CMS • CMS computing resources do not allow replication of data between EGEE and OSG • 50% of computing resources (and thus of CMS data) will be in USA • EGEE users need to be able to run analysis jobs on US sites • Interoperability is very important to CMS • Can not come as an afterthought • Mostly to be remembered for future evolution • Two examples follows EGEE OSG Interoperability

3. Recent accident • OSG moved on to next minor release of Openssl • From 0.9.6 to 0.9.7 • Same binary OID printed as Email or emailAddress • Globus relies on matching the ASCII printout • Aaargh !! • This breaks compatibility for users who have an email address in their certificate • One day things stopped working • Had to discover problem and invent solution (hack) • Two days, tons of mails EGEE OSG Interoperability

4. But experts knew • After the fact: e-mail from Alain Roy (March 3, 2007): I recall that this came up in conversation several times. Once was with Maarten Litmaath: I have an email from 2005 where he says: Upgrade of OpenSSL from 0.9.6 to 0.9.7: this changes the textual    representation of DNs with e-mail addresses; probably we can hack    the grid-mapfile to include both forms. I want to say that it was discussed at least once at an EMT meeting, but I wouldn't swear to it. • Please ! EMT participants, developers, meeting goers, all of you • If you hear of something like that again, and know that EGEE or OSG are changing something that may affect us • Speak up ! • I can not know OSG has changed VDT and Openssl with it etc. etc. EGEE OSG Interoperability

5. Job submission • Submitting from LCG –RB to OSG works well • CMS members use it to submit analysis jobs • Can not move them to gLite if this functionality is lost • gLite 3.0 uses edg-gridftp-* utilities, only deployed on EGEE sites • gLite 3.1 should be using uberftp, part of VDT • We gave 3.1 a try: • Only worked at one of seven OSG sites (Florida) • Maybe because Florida installs edg-gridftp-* stuff ? • We understand priority on gLite WMS was and still is performance and robustness, but… would like to be sure this does not get forgotten EGEE OSG Interoperability

6. A worry • What else may change in the future and “break it” ? • OSG is bringing online new information system • Based on CEMON, I hear • Still we do not have real transparency and compatibility • Some problems in “interpretation of GLUE specs” e.g. came up with lcg-infosites and SAM (both fixed) • What can be done to reassure us ? EGEE OSG Interoperability

7. Near future actions proposed • Openssl versions • Suspect talking to CA’s into reissuing certs is a waste of time • Put two entries in VOMS for each user with email in DN • It works (tested on another user besides SB), procedure documented in twiki • Propose to adopt this as solution • gLite 3.1 WMS • Maybe OSG do not deploy uberftp yet ? • Maybe something else • We can help, also Burt Holzman at FNAL available to help • But need JRA1-IT to be on board • In general • Do we need (have already) a clear communication channel with OSG on this where it is addressed before users notice ? • Is EMT the proper forum ? EGEE OSG Interoperability