Details
-
Enabler
-
Not Assigned
-
None
-
None
-
Services
-
-
8
-
8
-
2
-
Team_BUTTONS, Team_CIPA, Team_CREAM, Team_KAROO, Team_MCCS, Team_NCRA, Team_PERENTIE, Team_SYSTEM
-
Sprint 4
-
-
-
-
9.5
-
Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
-
-
SPO-718
Description
Background: historically, SKA has used Docker exclusively with docker-compose, as a mechanism for small scale Container Orchestration primarily for the purposes of delivering small scale integrated testing of Tango based software suites. This approach has been replaced with the use of Kubernetes as the Orchestration platform of choice, which requires migration of existing docker-compose resource files to Kubernetes Helm Charts, as well as integration of the development, test and CI/CD workflow with a Kubernetes environment.
Current Situation: Whilst a number of teams have embraced the Kubernetes centric approach, there are a number of projects/repositories that are still based on the docker-compose workflow.
Desired State: All teams/maintainers of outstanding repositories should migrate their development, test and CI/CD workflow processes to Kubernetes, and obsolete the use of docker-compose.
Identified repositories that mention docker-compose:
cdm-shared-library (Buttons)
csp-lmc (CREAM)
csp-lmc-prototype (CREAM)(INACTIVE)
csp-lmc-subelement (CREAM)
dish-master (NCRA?)
lfaa-lmc-prototype (MCCS)
lmc-base-classes (Karoo )
low-cbf-gemini (Perentie)
low-cbf-integration (Perentie)
low-cbf-mcs (Perentie)
low-cbf-pss-interface (Perentie)
mid-cbf-mcs (CIPA)
observation-execution-tool (Buttons)
pst-lmc (PST)
rascil (Tim Cornwell SIM??)
rdma-data-transport (Andrew Ensor NZAPP)
sep_pipeline_imaging (Adam Campbell NZAPP)
ska-docker (ST)
ska-engineering-ui-compose-utils (CREAM/BUTTONS) (INACTIVE)?
ska-low-mccs (MCCS)
skampi (ST)
ska-project-data-model-library (Buttons)
tango-example (ST)
tangogql (CREAM)
tangosnmp (Perentie)
tmc-prototype (NCRA?)
webjive (CREAM)
webjive-auth (CREAM)
web-maxiv-tangogql (CREAM)
Attachments
Issue Links
- is required by
-
SP-1259 Establish resource requirements for each application workload in terms of CPU, Memory, ephemeral storage, and persistent storage
- Done
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- mentioned on