Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4570

Develop and deploy Helm chart for deploying SODA service in K8s

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      SODA will likely be needed by the DM service to carry out server-side data operations in support of some SRCNet user tasks (e.g. image cube cutouts). Since some SRCNet sites have to deploy all services on K8s, a Helm chart will make much easier/reproducible the process of deploying SODA at these sites.

      Show
      SODA will likely be needed by the DM service to carry out server-side data operations in support of some SRCNet user tasks (e.g. image cube cutouts). Since some SRCNet sites have to deploy all services on K8s, a Helm chart will make much easier/reproducible the process of deploying SODA at these sites.
    • Hide

      AC1: New Helm chart configurations added to appropriate GitLab repository in the SKA Regional Centres project.

      AC2: Service deployed via Helm at at least one SRCNet site.

      Show
      AC1: New Helm chart configurations added to appropriate GitLab repository in the SKA Regional Centres project. AC2: Service deployed via Helm at at least one SRCNet site.
    • 1
    • 1
    • 0
    • Team_MAGENTA
    • Sprint 2

    • PI24 - UNCOVERED

    • PI24-PB SRCNet0.1
    • SPO-3479

    Description

      A Helm chart for the SODA service prototyped by the Coral will be needed for sites needing to deploy SODA on K8s clusters (required for SRCNet 0.1). Since there are docker-compose files available, this work should involve developing the Deployment CRDs, and then parametrising these in a Helm values.yaml with corresponding Chart.yaml identifying any chart dependencies.

      Attachments

        Issue Links

          is required by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4554 NLSRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4564 CHSRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4658 CNSRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4659 ITSRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4662 JPSRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4494 UKSRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Implementing

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4582 CASRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Implementing

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4660 SPSRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Implementing

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4661 SWESRC - Deploy all v0.1 local compulsory services

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Implementing
          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                r.joshi Joshi, Rohini
                j.collinson Collinson, James
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (44.44%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do23.0
                  In Progress   22.0
                  Complete24.0
                  Total69.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel