Versioning same as internal release, but with v5 (v5.Y.Z).
The DB team has asked for the CPU load to be reduced as soon as possible (by fixing the DB indexes). Therefore we will release the Catalogue v12.0 first, as version 4.7.10. The code changes will come after.
The public release will be released on top of the future version 4.7.11. There is no need to wait for 4.8.x.
15:20
→
15:30
Collaborations10m
CTA read support for non-native tape formats (OSM/dCache and Enstore)
btime needs to be filled in by EOS (development on EOS): #86
The cta-frontend-grpc integration for CTA is blocked by the need to pass the `cta.common.Clock btime` from EOS to CTA (CTA is already prepared to receive it) - #86
A diagram containing all the new and old tape states was presented here.
The new states were accepted: REPACKING_DISABLED, EXPORTED, EXPORTED_PENDING.
REPACKING_DISABLED can only be changed to BROKEN or EXPORTED.
The diagram is good but can be improved: add dash lines to distinguish between mountable, temporary, queueable states, user-land, operator-land.
Temperature & humidity values collection from the tape drives
It may be possible to ignore the humidity alerts (if spectra logic experts suggest so), but any decision to do so needs to be approved first by upper management. They are the ones that can make the decision based on the risk.
Julien will manage the work on the monitoring tool originally developed by Miguel and on the dashboards.
There will be a meeting next Monday with the datacenter operations to discuss possible solutions regarding the humidity issue.
cta-taped encryption ERROR when upgrading ctaproductionfrontend
Only the Key ID will be passed from the Tape Server to the python script cta-get-encryption-key.
The work is split on 3 parts:
Add the column Key ID to the table TAPE_POOL. We can use the same definition for the Key ID that exists in the table TAPE. This change should be included in the next catalogue version v12.0.
The cta-get-encryption-key needs to be modified to accept the Key ID from the Tape Server and directly use it to obtain the Encryption Key, without using cta-admin command.
The Tape Server code needs to be modified to pass the Key ID to the script.
15:40
→
15:50
AOB10m
HTTP REST API, Activities and Priorities
[Julien]: Specification document status and remarks.
Other
No dev meeting on 9 Sep 2022.
Room 513/R-068 is booked every week, until the EOY, for the CTA dev meeting.