CTA Dev Meeting

Friday 24 Mar 2023, 15:00 → 16:30 Europe/Zurich

513/R-068 (CERN)

Michael Davis (CERN)

python-build-and-versioning.pdf

1 CTA Release Roadmap

See CTA Release Roadmap

Release 4.8.6-1

• Release date: 8 Mar
• Pre-prod deployment date: 9 Mar
• Prod deployment date: 9 Mar
• Small release from branch "release_4.8.6"
• Fixed queue cleanup bug in CTA
• Milestone link

Release 4.8.7-1

• Release date: TBD
• Pre-prod deployment date: TBD
• Prod deployment date: TBD
• Milestone link

Public Release

• Latest version available on public repo: v4.7.14-1, v5.7.14-1
• For release v4.8.6-1/v5.8.6-1

Release 4.8.6-0.rc1

• It has been released
• Vova will deploy to pre-production and test.

Release 4.8.7-1

• We need to find a fix to the "no tape block movement" warning (previously error) message before doing this release. It was a regression.

Public Release

• Will be done on top of the future release 4.8.7-1, as long as it works well for around a week.

2 CTA dev topics

Normalize usage of encryptionKeyName

• For more details: #341

Compile CTA using devtoolset-11

• For more details: #342

"Needs discussion" topics

• Issues link

"Dev issue needed" topics

• Ops issues link

Solution to count and monitor log events in CTA

• Adopting OpenTelemetry can be a risk (vs the option of creating our own mechanism).
• In addition, we may not need all the complexity that it provides.
• Task 1: Select 1 or 2 use cases.
• Task 2: Check which infrastructure would need to be used.
• Task 3: Experiment and prototype on a separate branch. Have a POC.

Allow VO override for repack

• We will call the new column IS_REPACK_VO.

Review error messages for prepare abort

• We need to find ways to improve our error messages returned with query prepare.

Tasks:

• Add new fields to the file xattrs that help improving the "error_text" message in the query prepare command (For example "[123456789.00][cta-taped] trigger workflow - synchronous workflow failed"). Examples:
  • Timestamp
  • Message type
  • Message origin (cta-taped, cta-frontend, EOS, ...)
  • Etc...
• Check existing xattrs.
• Review default "error_text" messages filed by EOS. Check if they are adjusted to each specific scenario.
• Review mechanism that passes messages from CTA to EOS (&mgm.errmsg= field).

Unify permission configuration across different CTA tools

• Needs more investigation.

3 PostgreSQL SchedulerDB

Update

4 dCache Integration

AOBs

Fons and Michael have started working on the refactoring of the cta-frontend, to remove any duplicated code between the EOS and dCache versions,

5 AOB

Other

• Room 513/R-068 is booked every week, until the EOY, for the CTA dev meeting.

Next meeting will be on Thursday.

6 CTA dev board review

Objective

• Look at the active issues in our CTA dev board.
• Decide if they should be kept, removed, reassigned, prioritised, etc.

Review "Assigned" labeled issues

Full CTA board: link

• Add test that file has been deleted from FST #11
• Harmonize retrieve/recall reporting interface for success. #40
• Revise the cleanup logic of the tapeserver #50
• Do not queue file for retrieve if EOS size/checksum do not match CTA Catalogue #75
• Testing format import for tests #45
• CI compatible with recent kubernetes versions #32
• dbunittests_oracle CI jobs are timing out and silently failing #66
• Put in place automatic container registry cleanup #84
• quarkDB xrootd must come from eos-xrootd package #60

Review unlabelled issues

• Unlabelled issues list: link

Review "In progress" issues

• Full CTA board: link

Review specific topic

• Every week we review the issues of one topic.
• This week: "Scheduler" and "Object Store" labels