WLCG-EGEE-OSG Interoperability

1
WLCG-EGEE-OSG Interoperability

• Rob Quick
• Open Science Grid Operations Center - Indiana
  University
• Special Thanks to Rob Gardner your presenter, and
  Torsten Antoni who helped with the original
  presentation this one is based on.

2
Outline

• Goals of Interoperability
• Cross Grid Monitoring
• Communication
• Challenges
• Conclusion

3
Goals of Interoperability

• Seamless operations for users who wish to cross
  administrative boundaries
• Users who want to cross grid boundaries need to
  know the environments, both technical and
  administrative, will be similar
• Site Validation and Availability
• Cross Grid Publication and Notification
• Trouble Reporting
• Security Response

4
Goals (Cont.)

• Preserving the autonomous boundaries between
  infrastructures and provide a framework for
  scalability and defined areas of responsibility
• Communication between operations groups to assure
  users feel at home in all WLCG environments

5
Publication and Monitoring

• BDII
• In place at EGEE and OSG
• SAMs (EGEE testing of OSG sites)
• Testing has begun on a single OSG node and is
  progressing (moderate success with job
  submission)
• At this point no modifications have been made
  explicitly to the OSG node to allow SAM to
  function
• I expect a minimal subset of the GLite package
  will need to be installed to have useful SAM
  results
• Problems are being worked through as they are
  encountered
• Short term stop in testing while OSG-ITB-0.5.2 is
  being rolled out
• Will be restarted on Monday 29 January

6
Publication and Monitoring (Cont.)

• VORS (OSG testing of EGEE sites)
• A single pre-production site is being set up to
  run OSG critical tests against
• Problems will be worked through as encountered
• Ops VO will be used for all interop testing and
  monitoring
• Limited set of users from both EGEE and OSG

7
Critical Communications

• Ownership of each communication so each reported
  problem gets the proper followup and reaches
  proper resolution
• Critical Updates
• Relies on communication between operations
  groups, no formal policy exists
• This should be a priority
• Security Notification
• WLCG Security Model has been implemented
• Standard patches and updates
• With interoperability monitoring we need to be
  careful that standard patches/updates do not
  break the tools we are using

8
Trouble Ticket Communication

• Ticketing
• OSG Footprints
• Global Grid User Support
• Each OSG VO and EGEE ROCs individual ticket
  system
• All these helpdesks/ticketing systems are
  connected and are used for user support and for
  operations to formally communicate inside and
  across the infrastructures

9
Ticket Communication
Example OSG User Communicates with EGEE site
ExampleEGEE Service Communication with OSG Site
10
Communication and Planning

• Joint Meeting (every 6 months)
• Next Joint Meeting, 4-7 June 2007, Indianapolis,
  IN - US
• Focus on LHC Data Taking Ramp Up
• Weekly WLCG Operations Meetings
• Individual Communications as Needed
• Software groups
• Monitoring groups
• Operations teams

11
Challenges

• Different Software Stacks
• Critical Tests on both sides rely on services
  that may not be standard parts of the other grids
  software
• ExampleGRIS will not be a standard on OSG
  releases gt 0.5.1, SAMs tests rely on information
  used by GRIS
• GRIS will be installed and can be started on OSG
  0.5.2
• Binaries and conf files SAM is looking for are
  not available by default on OSG nodes
• glite-gridftp-remove, edg-wl-logev
• A small OSG WLCG Validation software package
  may need to be developed and configured to allow
  usefull testing by SAMs
• Environmental structures are different between
  GLite and OSG stacks

12
Challenges (Cont.)

• Policies are different, meshing is not always
  easy or desired
• Policies are determined by the project drivers,
  and these are not always the same
• Ticketed communication is quick, human
  communication is not always so fast
• Time differences make it difficult to just pick
  up the phone and work through problems
• Face-to-face meetings create a flurry of
  activity, but it tends to fade between meetings

13
Conclusions

• Communications is the key to interoperability and
  these processes are in place, continuing to
  refine procedures will be critical to success
• Operations problems are getting solved
• Technical and Monitoring issues are being
  addressed, this is not always a quick and easy
  process as we are working with different software
  stacks
• OSG is committed to interoperability with EGEE,
  WLCG, and TeraGrid
• With dedicated effort both technical and
  administrative challenges can be overcome