Open Science Grid Operations Update Rob Quick Indiana University Research Technologies - High Throughput Computing Open Science Grid - Communication, Operations and Production EGI Community Forum - November 9, 2015
A review of EGI-OSG Interoperations Selected updates since the last OMB report OSG Operations Directions
other sciences life sciences ATLAS other physics CMS
“…provide researchers with a secure and consistent experience for those Virtual Organizations wishing to utilize resources in both the Open Science Grid and the European Grid Infrastructure cyberinfrastructures…the OSG and EGI will work toward cooperative communication goals and a persistent set of interoperable services.” -EGI OSG MoU - Signed July 2013
Interoperable Services BDII Information Services GGUS Ticketing APEL Accounting CVMFS Repository Replication Incidence Response and Information Sharing
Service Updates BDII, GGUS Stable with minor operational updates APEL - Added multicore accounting and non-LHC VO accounting CVMFS/OASIS - Added desy.de repo for ILC PerfSONAR - Now Production http://psmad.grid.iu.edu/maddash-webui https://psomd.grid.iu.edu/
Upcoming Service Changes BDII - OSG has long term plans to retire the BDII GGUS - OSG may be changing to a Service Now system APEL - OSG needs to implement comparison visualization CVMFS - OSG backdoor process for desy.de need to implement easy repository replication
“…provide researchers with a secure and consistent experience for those Virtual Organizations wishing to utilize resources in both the Open Science Grid and the European Grid Infrastructure cyberinfrastructures, and to lower the hurdle for new VOs attempting to harness these resources, the OSG and EGI will work toward cooperative communication goals and a persistent set of interoperable services.” -EGI OSG MoU
Fundamental Shifts in OSG Almost all submissions go through GlideInWMS HTCondor CE now widely deployed GRAM Retirement mid to late 2016 Credential services independent of CA
What is the Open Science Grid? A single geographically dispersed provisioning O(100) system to create Resources community specific overlay batch systems O(1) Infrastructure O(1000) Users
What should EGI-OSG Interopeations look like? O(100) Resources O(1) Infrastructure O(1000) Users
Successful long term operational collaboration We have succeeded in providing a persistent set of interoperable services and cooperative communication Invitation to use the PerfSONAR data store and visualization tools Have we succeeded in lowering the hurdles for interoperable VOs? How should ‘long tail’ VOs interoperate?
Recommend
More recommend