Lightweight Sites Profile
Introduction
In transitioning to simpler sites which are easier to install and maintain than a traditional WLCG grid site ("lightweight sites"), we need to retain or replicate some interfaces which are still needed. Many of these changes are driven by the wider decision to drop the BDII requirement. This page collects these interfaces and solutions for continuing to provide them. It starts from an EGI-WLCG focus and needs OSG-WLCG information adding.
GOCDB
To be able to declare downtimes in GOCDB, services themselves need to be declared in GOCDB, and this in turn requires that their service types are registered. This process is
managed by EGI
.
Interfaces
Name |
Traditional |
Lightweight |
Downtimes |
GOCDB |
GOCDB |
Publishing CPU capacity |
BDII |
GOCDB pointer to JSON file? |
Publishing SE capacity |
BDII |
GOCDB pointer to JSON file? |
Accounting |
Site APEL service |
Direct publishing to central APEL service |
ETF testing |
ETF job submission |
Experiment specific (DIRAC: in pilots; others: ETF jobs to pilot job pools?) |
To Do List
- REBUS capacity information from GOCDB (via CRIC?)
- ...
--
AndrewMcNab - 2018-03-29