CTA Dev Meeting
-
- 1
-
2
CTA Release Roadmap
Release 4.7.12-1
- Milestones link
- Release date: 7 Oct
- Pre-prod deployment date: 7 Oct
- Prod deployment date: 12 Oct
- Includes: fix that drastically reduces number of DB queries (tape drive states #160)
- Includes: CI config for public release of CTA-4/CTA-5.
Release 4.8.0-1
- Milestones link
- Release date: TBD
- Pre-prod deployment date: TBD
- Prod deployment date: TBD
- v4.8.0-0.rc2 has been released on top of v4.7.11-1.
- v4.8.0-0.rc3 will be released on top of v4.7.12-1 (after v4.7.12-1 is tagged).
Future releases (4.7.x)
Public Release
- Remaining tasks
- Release date: Sep 2022
- On top of internal release v4.7.12
- Includes Xrootd 5
- Versioning same as internal release, but with v5 (v5.Y.Z)
- TODO: Provide a set of public repositories for all EOS-4/5 and CTA-4/5 dependencies.
v4.8.0 release
- Vlado will on on holidays for 2 weeks (from 15 Oct). He will write down the tests that he wants to run for CTA v4.8.0-0.rc3, so that another person can run them on his behalf.
- This can be integrated with the procedure that Julien wants to develop for the tests run against the pre-production instance.
Public release
- Tigran offered to test/experiment with the new public release with xrootd5. They have a test machine prepared for it. We will still release the same (minor) version RPMs with xrootd4.
- Julien will prepare the set of public repos that will make CTA-specific dependencies available to the public. TODO: Create ticket to discuss this in more detail.
-
3
Collaborations
CTA read support for non-native tape formats (OSM/dCache and Enstore)
cta-frontend-grpc integration for CTA
- Project roadmap: #38
-
4
CTA dev topics
Refactor operations cmd line tools to use common parsing logic
- [Lasse]: cta-restore-deleted-files, when run with postgreSQL, fails on TABLE TEMP_DISK_FXIDS #161
- [Lasse] Update to parsing of cta-verify-file #173
REPACKING tape state and queue cleanup
- [Joao]: Next steps (testing of release v4.8.0-0.rc3)
Upgrade of gtest suite to v1.12.0 (repackaged for internal use)
- Adds 11 years of new features and improvements #107
Existing issues with MHVTL / tape labelling in CI
- Very negative impact in our CI.
- Possible explanations: CI runner randomly crashing in cta-tape-label #171
- Fix: MR link
"Needs discussion" topics
"Dev issue needed" topics
Refactor operations cmd line tools to use common parsing logic
- Lasse found a solution for the DB problem, together with Steve.
- Issue #173 relates with the operation issue #ops-883. We should allow a file to be passed with the list of all files that we want to verify.
- This should be consistent with the behaviour of all other operational tools.
Existing issues with MHVTL / tape labelling in CI
- The explanation and solution can be found on issue #171.
- One of the problems in the origin of this was that the error was not being reported correctly.
- Therefore, Julien will create a ticket for Vlado #174, where he can check all messages that are/should be generated by the tape labelling tool. The messages missing will need to be added.
Others
ctaproductionfrontent02.cern.ch segfault
- We will discuss this on the next ops meeting.
- The important take is that the cta-frontend should not be auto-segfaulting if there is a problem with cpu/memory. Instead, the cta-admin command should refuse intensive tasks, or we should have a mechanism to abort intensive processes before they become a problem.
- Tigran suggesting separating the hosts of the cta-frontend and cta-admin tools. This would remove the impact that one service is having on the other.
How to inform the community of what we have ? (Jorge question)
- Jorge will check what we can do.
- One idea is to have a sticky note telling every version of the software that we currently deploy in prod.
-
5
AOB
HTTP REST API, Activities and Priorities
- [Julien]: Specification document status and remarks. Scheduled discussion between CTA devs and FTS team.
Other
- Room 513/R-068 is booked every week, until the EOY, for the CTA dev meeting.