WLCG/EGI accounting technical meeting
Summary
The meeting focused on presenting technical details of the current WAU service, understanding the existing EGI/APEL components, and aligning on a WAU-based approach. Concrete next steps were defined towards a minimal first functional prototype consuming accounting data directly from APEL MQ instead of the EGI Portal.
Discussion Points
• Greg shared the last EGI Portal accounting code he is aware of (likely outdated).
• https://github.com/cesga-egi/accounting
• Adrian shared the APEL database schemas used for server and cloud accounting.
• https://github.com/apel/apel/blob/dev/schemas/server.sql
• https://github.com/apel/apel/blob/dev/schemas/cloud.sql
• Most identified use cases appear to be covered by the existing schemas; cloud accounting may require minor adaptations.
• Accounting data from APEL is provided at CE level; this was not considered an issue.
• For non-LHC VOs, topology information is expected to come from GOCDB / CRIC; some EGI-Portal-specific logic may be hardcoded.
• The group agreed to start with a minimal implementation and iterate from there.
Action Points
• Panos
• Create CERN accounts for Adrian, Greg, and Deniza.
• Set up a dedicated Mattermost channel.
• Adrian
• Provide a token to consume from the APEL MQ.
• Nikos & Panos
• Start consuming APEL MQ data once access is available.
• Review the shared APEL schemas, including cloud-specific aspects.
• STFC team
• Review the WAU codebase once access is granted.
• Prototype deployment at STFC likely after the next 2–4 weeks.
• Julia
• Request access to EGI Portal code and database to understand data ingestion, storage, and visualisation.
• All
• Prepare a short document describing the use cases to be covered and share it with EGI to see if they need more functionalities ported from the EGI portal.
• Propose and agree on a name for the new system.