Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Must have
Fix Version/s: PI21
Component/s: None
Labels:
- Team_SYSTEM

ARTs:

Services
Benefit hypothesis:

Hide

The release and deployment flow for a project has still some uncertainties at the moment regarding deployment process, ci/cd flow, configuration management and deployment responsibilities for AIV teams repositories (skampi-like). There are many tools used at the moment from different teams resulting in a non unified approach.

The objective https://jira.skatelescope.org/browse/SPO-2790 helped in sharing the CICD tools have been prepared and shared with teams by ST and !# and it's important to keep that objective for AIV teams.

AIV teams repositories must follow the same solution for release and deployment flow available for developer - with a clear idea on how to deploy subsystem to different environments in different clusters (PSI, ITF, etc.).

Possible collaborations with Atlas, Viola, Himalaya, etc.

Show
The release and deployment flow for a project has still some uncertainties at the moment regarding deployment process, ci/cd flow, configuration management and deployment responsibilities for AIV teams repositories (skampi-like). There are many tools used at the moment from different teams resulting in a non unified approach. The objective https://jira.skatelescope.org/browse/SPO-2790 helped in sharing the CICD tools have been prepared and shared with teams by ST and !# and it's important to keep that objective for AIV teams. AIV teams repositories must follow the same solution for release and deployment flow available for developer - with a clear idea on how to deploy subsystem to different environments in different clusters (PSI, ITF, etc.). Possible collaborations with Atlas, Viola, Himalaya, etc.
Acceptance criteria:
Hide

The unified approach for Software CI/CD, release and deployment are adapted/implemented to AIV teams repositories (skampi-like) in order to increase the frequency integration cycle

The approach is used with AIV teams in a co-located shared sessions to move them to the process while educating the teams

The selected teams (developer or AIV) increase and share the same concept in term of release and deployment flow.
Show
The unified approach for Software CI/CD, release and deployment are adapted/implemented to AIV teams repositories (skampi-like) in order to increase the frequency integration cycle The approach is used with AIV teams in a co-located shared sessions to move them to the process while educating the teams The selected teams (developer or AIV) increase and share the same concept in term of release and deployment flow.
Feature Points:
1.5
Initial Size:
1.5
WSJF:
0
Epic Link:
DevSecOps Implementation
Agile Teams:

Team_SYSTEM
Due Sprint:
Sprint 4
Story Point Burn-up:
Overdue:
Outcomes:
Hide

Collaborated and reshaped ATLAS repositories to follow the rest of the project guidelines and faster deployments (this still needs some more work)

Config Management tickets has been dropped as the Consul is not chosen

This resulted dropping the collaboration with CIPA and KAROO

Helped MAPLE team define staging environments and streamline variables across different deployments
Show
Collaborated and reshaped ATLAS repositories to follow the rest of the project guidelines and faster deployments (this still needs some more work) Config Management tickets has been dropped as the Consul is not chosen This resulted dropping the collaboration with CIPA and KAROO Helped MAPLE team define staging environments and streamline variables across different deployments

Requirement Status:

PI24 - UNCOVERED
Labels_MIRO:
Team_SYSTEM

Description

According to this confluence page and the related discussion available here, it is possible to classify a repository as

subsystem specific (for example ska-dish-lmc or ska-mid-cbf-mcs): used for develop the subsystem with no environment in mind and therefore that deploys only on cloud environments for testing;
subsystem and environment specific (for examples ska-mid-cbf-system-tests): used for develop system level tests for a specific subsystem targetting a specific environment where the HW needed (FPGA) by the subsystem is available;
environment specific: used for developing system level tests without a specific subsystem in mind (ska-mid-itf or ska-low-itf)

The current solution proposed by the ST accomodate the first 2 cases while the third one has grown with the effort of specific team (for example VIOLA or ATLAS).

The feature aim to identify a clear release and deployment flow for AIV teams and developer teams so that it results in a faster deployments and feedback without new complexity. The work potentially needs collaboration commitment from 2 teams while implementing so that we work with the "customer".

Details will be finalised before PI planning.

Attachments

Issue Links

relates to

SS-117 Com-C3: Sub-system level software release & delivery improvements

Done

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(4 mentioned in)

Structure

Activity

People

Assignee:: Harding, Piers

Reporter:: Di Carlo, Matteo

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Feature Progress

Story Point Burn-up: (100.00%)

Feature Estimate: 1.5

	Issues	Story Points
To Do	0	0.0
In Progress	0	0.0
Complete	4	4.0
Total	4	4.0

Dates

Created:: 28/Nov/23 8:23 AM

Updated:: 28/Feb/24 11:22 AM

Release and Deployment Flow for AIV teams