CTA Dev Meeting
-
- 15:00 → 15:10
-
15:10
→
15:20
CTA Catalogue Schema 10m
Upgrade procedure status
- Readiness of container, procedures and documentation for external collaborators to perform v10.0 upgrade (#Ops-712)
Schema - v10.0
- Production DB migrated on 18 May 2022 - Success (#Ops-721)
- First tested on a production DB clone - always do this in the future (#Ops-722)
Schema - v10.1/v11
- Milestones link
- Separate branch catalogue_v10.1
- Schema-only release.
- Release date TBD
- Schema v10.0 has been deployed successfully.
- Instructions about the process to upgrade and about how to use the containers have been updated. They are ready to be shared with our external users. Issue #Ops-712 has been closed.
- Schema v11.0 (no longer v10.1) will be released when ready. There is no reason to delay it, but also no pressure to rush it.
-
15:20
→
15:30
CTA Release Roadmap 10m
Release 4.7.0
4.7.0-1
- Replaced by 4.7.0-2.
4.7.0-2
- Deployed in production - 18 May 2022 (#721)
Release 4.7.1-1
- Milestones link
- Only for testing in ppd
Release 4.7.2-1
- Deprecated
Release 4.7.3-1
- Milestones link
- Deployed in pre-production
- Related issues:
Future releases (4.7.x)
Catalogue v10.1
- Milestones link
- Separate branch: catalogue_v10.1
Release 4.7.4
TBD
Public Release
- New label: Public Release - Check remaining tasks
- Move subdirectories from CTA dev repo into new repos (#1182)
- Nightly runs status
Deployment Schedule
- Release 4.7.0-2 / Deployed to Prod - 18 May 2022
- Release 4.7.3-1 / Deployed to Pre-Prod / Stress tests ongoing / Prod deployment TBD
- Release 4.7.4-1 / Freeze date TBD
- Version 4.7.3 is ready to be deployed to prod, but it was decided that we should wait for the stress tests to complete successfully. Vova will execute them this weekend. Following the result, we will decide when/if we will deploy it do production.
- Michael reminded that the release instructions have been updated. We should fill the %changelog part of cta.spec.in appropriately.
Public release:
- Only missing nightly runs and documentation fixes. After that the release should be ready.
- Michael will check with Steven how we can avoid having the Cern Oracle Instant Client as dependency, since it cannot be accessed outside of cern.
- 15:30 → 15:40
- 15:40 → 15:50
- 15:50 → 16:00