DIRAC Project meeting
Visio Zoom
Dirac Updates
6 patches releases
v7r2p49, v7r3p28
v8.0.0a29
WebAppDIRAC 5.0.0a10
python3 only, OAuth2/OIDC AAI user management
hopefully last hackathon this Thursday August 25th
-> LHCbDIRAC hacakthon based on 8.0.0a29
-> v8.0 release !
OAuth/OIDC AuthN/AuthZ
=> Andrii a quitté le projet, développement doivent être repris par d'autres personnes...
Andrei, CERN ou CC-IN2P3 ou via EGI-ACE
Prerelease 8.0.0a27 installed on ccdirac06
Authorization server for EGI, almost in production
EGI SSO login in the WebApp, dirac-login in jupyter notebooks
Access by tokens to HTCondorCE
demonstrated to work with HTCondorCE at CC (Vanessa)
integration with the SiteDirector/TokenManager on-going
hackathon with ARC/HTcondorCE developpers in September in Amsterdam
-> organized by WLCG A&A group
-> using CEs with tokens
EGI/FG services
9M jobs, 900 average -> all fine
Service Migration
migration to new set of VM (new hosts) using CEPH disk
new hosts configured and software installed v7r3p27, python3 servers
setting up token management
migration to be finalized this week
Jupyter
successful DIRAC access thank to CVMFS mount
> source bashrc_egi_dev
> dirac-login (does not work yet for it needs proper token management)
EOSC procurement plan
handled for us by EGI as a successor to EGI-ACE
EGI meeting on September 9th
our contribution/corrections to the draft mid-setpember
proposal to be sent by September 30th
ESCAPE
magor upgrade of EscapeDIRAC extension on-going
=> could evolve as a proper system to run containers via DIRAC?
python3, pypi, new WebAppDIRAC
recognizing DIRAC as the base WMS for ESCAPE => Johan
EGI Conference
19-23 septembre à Prague
DIRAC sessions
-> together with Eiscat 3D project
-> other? more WMS?
-> present Dirac WMS within the CTA use case
Sorina
question sur les jobs en Statut "Waiting" sur lesquel une commande "kill" n'a aucun effet...
à retester, doc pas claire, voir le code.
+ après vérification :
1. la nouvelle state machine n'autorise pas la transition Waiting->Killed
2. l'implémentation du killJob retourne une erreur si appeler sur un job Waiting
3. il faut utiliser une commande "delete" sur les jobs Waiting
Prochaine réunion le mardi 13 septembre à *15h*