CTA Dev Meeting

Friday Jan 27, 2023, 3:00 PM → 4:30 PM Europe/Zurich

513/R-068 (CERN)

Michael Davis (CERN)

1 CTA Release Workflow

• Release procedure instructions

2 CTA Release Roadmap

See CTA Release Roadmap

Release 4.8.3-1

• Milestones link
• Release date: 18 Jan
• Pre-prod deployment date: 18 Jan
• Prod deployment date: 19 Jan
• Added counters for profiling high-rate DB queries (MR link)

Release 4.8.4-1

• Milestones link
• Release date: 23 Jan
• Pre-prod deployment date: 25 Jan
• Prod deployment date: 26 Jan
• Will include only the catalogue DB query optimisations resulting from the 4.8.3-1 analysis

Release 4.8.5-1

• Milestones link
• Release date: TBD
• Pre-prod deployment date: TBD
• Prod deployment date: TBD
• This will be a large release, with many new features/fixes added since December.

Public Release

• Latest version available on public repo: v4.7.14-1, v5.7.14-1

• Release 4.8.5-1, should be done next week.
• Before, we need to merge:
  • Changes from 4.8.4-1 (including removal of counters).
  • Usage of new CTA-catalogue schema
• Next public release can be done on 4.8.5-1, as long as it performs well in our production environment.

3 CTA dev topics

Add new physical tape library table to the CTA catalogue

• For details check #276
• Do we enforce a normalisation form to the CTA catalogue schema?

Tape server querying DB at very high rate

• Improvements to DB queries done by the tape server.
• Tape server querying DB at very high rate: #155
• Fix 1 worked: #275
• Fix 2 seems not to have worked: #274

"Needs discussion" topics

• Issues link

"Dev issue needed" topics

• Ops issues link

Add new physical tape library table to the CTA catalogue

• For details check #276
• We will use 3NF in most cases, but for this specific table it was decided that it is unnecessary.

Tape server querying DB at very high rate

• It seems that the changes are having the expected results (significant reduction in number of DB queries).
• In addition, this seems to have reduced the average duration of fetchMountInfo(...) from 8 to 2 seconds.
• On monday a new analysis will be done to confirm these results.

Other

• We must develop the counter logging system, ASAP. This can be added as part of the stress tests and monitoring to detect important variations in performance.
• Add a dCatche stick topic to the CTA dev planning

 

4 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 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

5 AOB

Other

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