50 likes | 173 Vues
In November 2013, a brainstorming session focused on improving the WLCG Information System (IS) was conducted by experts Alessandro Di Girolamo, Andrea Sciaba, Maria Alandes, and Julia Andreeva. The discussion centered around optimizing VO feeds incorporating major databases like ATLAS, CMS, LHCb, and ALICE. Key proposals included the simplification of configuration processes, a unified API to handle complexities, and the assessment of necessity for various BDII layers. The goal is to enhance the monitoring of downtimes, improve resource availability, and facilitate better utilization of opportunistic resources.
E N D
Information/Configuration Systems Alessandro DI GIROLAMO, Andrea SCIABA, Maria ALANDES, Julia ANDREEVA Common Projects - Brainstorming
Current components and interactions within the WLCG IS Monitoring Downtimes and sites VO feed ATLAS DB CMSDB LHCb DB ALICE DB Site BDII Site BDIIs Top BDIIs EGI GOCDB OSG OIM Opportunistic Resources Site BDII Site BDIIs Site BDIIs WLCG Resources WLCG Resources Resource BDIIs Common Projects - Brainstorming - November 2013
Towards a simplified and integrated WLCG IS Monitoring VO feed ATLAS DB CMSDB LHCb DB ALICE DB API EGI GOCDB OSG OIM Opportunistic Resources DB WLCG Resources WLCG Resources Resource BDIIs Site BDIIs Top BDIIs Common Projects - Brainstorming - November 2013
Areas for improvement (I) • Main IS components (GOCDB/OIM and BDII) • Already under discussion within the Infosys task force • Ensure VO DBs can be configured by only using a single IS entry point • A unique API will hide the underlying complexity • Flexibility to add/remove new components to the IS (see opportunistic DB) • Move more static info to GOCDB/OIM and leave dynamic info on the resource BDII • Are the site and top BDIIs actually needed? Is it enough with the resource BDII? • Consider other technologies • Could we use messaging instead of LDAP to publish dynamic information? • Publication of sites offering cloud resources Common Projects - Brainstorming - November 2013
Areas for improvement (I) • VO DB • There are currently 4 different abstraction layers to gather VO specific information • We could profit from existing implementations and share the way VOs interact with the IS • Reduce the duplication of effort by using a common approach • Opportunistic DB • Identify how experiments are currently using opportunistic resources • Implement a DB where opportunistic resources could be declared Common Projects - Brainstorming - November 2013