Speakers:
Alexander Tapper
(Imperial College London), Pierre Lasorak
(Imperial College London)
2
Round table: control
Speakers:
Pawel Plesniak
(Imperial College London), Pierre Lasorak
(Imperial College London), Tiago Alves
(Imperial College London), Zbynek Kral
(CTU Prague)
ELisA work completed for nanorc and drunc. Config removed from nanorc.
Gordon:
Can now start connectivity service automatically.
3
Round table: config
Speakers:
Alan Watson, Alessandro Thea
(STFC Rutherford Appleton Laboratory), Giovanna Lehmann
(CERN), Gordon Crone
(University College London), Henry Wallace
(Royal Holloway, University of London)
Roland:
Organisation of storage of objects in xml
Gitlab repo already well structured
Henry:
Looking into developing config editor
Possibilities:
GUI similar technology to run control
CLI
Some tools ported by John available from ATLAS
OKS Qt GUI is quite well factorised into
Discussion:
Need careful coordination with existing (continuing) development of tools for configuration editor
Pursue on two fronts: continue understanding how the current tools work and document possible improvements
4
Round table: k8s etc.
Speakers:
Alessandro Thea
(STFC Rutherford Appleton Laboratory), Bonnie King
(FNAL), Jonathan Hancock
(University of Birmingham), Patrick Riehecky
(Fermilab), Pierre Lasorak
(Imperial College London), Tiago Alves
(Imperial College London), Tiago Alves
(Imperial College London)
5
Round table: monitoring
Speaker:
Marco Roda
(University of Liverpool)
Marco:
Grafana-dashboard tagged for v4.4.4, new development area for v4.4.5 already created
For v4.4.5 we expect at least changes in the PDS dashboard following restructuring of the configurations of the Daphne Controllers
New opmon level logic implemented in for the v5 monitoring
Code merged and tagged (opmonlib, kafkaopmon). Code available for v5.1.0 but with no implications for the rest of the code
There is a draft for the new opmon microservice, PRs in microservice and daq-kube. An initial image is already created. Pat and John already had a look, things seem reasonable.
We will wait util the end of the beam next week and then we will attempt to deploy the microservice. If it goes well, it will stay there to allow the development of the rest of the infrastructure.
There will be need to have a command to set the opmon level at the application level. This makes sense to happen after the full transition takes place. It can be considered as the 5th activity related to this transition.