Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Type: Enabler
Priority: High
Fix Version/s: PI24
Component/s: COM CICD, MID CBF SW, MID CSP LMC, MID Dish LMC HW, MID Dish LMC SW, MID ITF TST FACILITY, MID SDP
Labels:
- Team_ATLAS

ARTs:

MID ART
Benefit hypothesis:

Hide

Getting ready for Site deployments using correct deployment mechanism is vital. KAROO depend on this as well for DishLMC deployments, as well as PDTs of SPFRx, SPFC.

Show
Getting ready for Site deployments using correct deployment mechanism is vital. KAROO depend on this as well for DishLMC deployments, as well as PDTs of SPFRx, SPFC.
Feature Points:
3
Initial Size:
3
WSJF:
0
Agile Teams:

Team_ATLAS
Due Sprint:
Sprint 5
Story Point Burn-up:
Overdue:

Reorganise configuration of SUT deployments, by removing dependency on `Makefile` for configuration, ONLY WHERE SENSIBLE / APPLICABLE:
- Define environment specific static configuration in `values.yaml` only
- Migrate all dynamic configuration done in Makefiles into `VAULT`
Setup FluxCD Kustomizations for deploying HelmReleases of DishLMC, SPFRx deployer etc to DishLMC HW in ITF, and "SUT chart contents" to the Telescope Manager cluster in ITF (TangoDB, TMC, CSPLMC, CBFMCS, SDP Deployer, EDA, AlarmHandler (product decision TBD), CIA).
Use FluxCD Kustomizations / HelmReleases for deployments into Mid ITF, including DishLMC instances (namespaced or VM based)
Confirm that SUT deployments work as expected in ITF using FluxCD, by using Smoke test suite (see SP-4666)

relates to

SS-152 Release, deployment & integration improvements

Story Point Burn-up: (0%)

Feature Estimate: 3.0

Prepare for deployment of SUT in the KAPB cluster using HelmReleases supported by FluxCD