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

CHSRC - Deploy all v0.1 local compulsory services

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

Details

    • SRCnet
    • Hide

      Deployed, monitorable, documented and supportable services: will enable initial operations activities, including test campaigns; will (later) enable test users to interact with our systems; will provide the SOG with valuable operating experience; and will provide stakeholders with a tangible, assessable demonstration of SRCNet's progress so far.

      Deploying all local compulsory services is one requirement for SRCNet to "confirm" that an SRC will be a v0.1 node.

      A sufficient number of nodes must be "confirmed" for SRCnet to begin the v0.1 phase of work. This will be a landmark achievement for SRCNet. 

      Show
      Deployed, monitorable, documented and supportable services: will enable initial operations activities, including test campaigns; will (later) enable test users to interact with our systems; will provide the SOG with valuable operating experience; and will provide stakeholders with a tangible, assessable demonstration of SRCNet's progress so far. Deploying all local compulsory services is one requirement for SRCNet to "confirm" that an SRC will be a v0.1 node. A sufficient number of nodes must be "confirmed" for SRCnet to begin the v0.1 phase of work. This will be a landmark achievement for SRCNet. 
    • Hide

      For this SRC, all v0.1 local compulsory services are:

      AC1: Deployed locally

      AC2: Local integration test(s) are completed to check the connection with global services - as informed by deployment documentation (to be populated)

      AC3: Monitorable via the centralised service monitoring dashboards and shown to be running successfully

      AC4: Documented - meaning that any SRC-specific deployment instructions / troubleshooting are captured and (where applicable) added to ska-src-docs-operator

      AC5: Supportable - meaning that an operator (a SOG member if possible) is able to access the service deployment and provide support next PI

      AC6: Deployed via a GitOps Tool (e.g. ArgoCD, FluxCD) OR repeatable deployment methods fully documented with deployment velocity expectations (e.g. new versions are deployed within 1 working day)

      v0.1 local compulsory services:

      • Rucio Storage Element (configured to use SKA IAM)
      • JupyterHub (specifically JupyterHub, not another service that provides Jupyter Notebooks)
      • at least one Visualisation Service out of: CARTA, VisIVO, Aladin
        note: CANFAR can provide this visualisation service
      • SODA Service
      • Gate-Keeper API (see via features under SP-4654)
      • cavern see description 
      • a Orchestrator Service (e.g. Kubernetes)
      • perfSONAR
      • Local Service Monitoring stack (e.g. Prometheus)
      Show
      For this SRC, all v0.1 local compulsory services are: AC1: Deployed locally AC2: Local integration test(s) are completed to check the connection with global services - as informed by deployment documentation ( to be populated ) AC3: Monitorable via the centralised service monitoring dashboards and shown to be running successfully AC4: Documented - meaning that any SRC-specific deployment instructions / troubleshooting are captured and (where applicable) added to ska-src-docs-operator AC5: Supportable - meaning that an operator (a SOG member if possible) is able to access the service deployment and provide support next PI AC6: Deployed via a GitOps Tool (e.g. ArgoCD, FluxCD) OR repeatable deployment methods fully documented with deployment velocity expectations (e.g. new versions are deployed within 1 working day) v0.1 local compulsory services: Rucio Storage Element (configured to use SKA IAM) JupyterHub (specifically JupyterHub, not another service that provides Jupyter Notebooks) at least one Visualisation Service out of: CARTA, VisIVO, Aladin note: CANFAR can provide this visualisation service SODA Service Gate-Keeper API (see via features under SP-4654 ) cavern see description  a Orchestrator Service (e.g. Kubernetes) perfSONAR Local Service Monitoring stack (e.g. Prometheus)
    • 1.5
    • 1.5
    • 0
    • Team_CHOCOLATE
    • Sprint 5
    • Hide
        AC1 AC2 AC3 AC4 AC5 AC6
      Service Deployed Integrated Monitorable/Running Documented Supportable GitOps (or ...)
      Rucio Storage Element y y y y y y
      JupyterHub wip       y y
      Visualisation Service y   y y y y
      SODA Service y   - y y y
      Gate-Keeper API         y y
      cavern y   y y y y
      Orchestrator Service y   y y y -
      perfSONAR y   y y y y
      Local Service Monitoring y   y y y y

       

      Show
        AC1 AC2 AC3 AC4 AC5 AC6 Service Deployed Integrated Monitorable/Running Documented Supportable GitOps (or ...) Rucio Storage Element y y y y y y JupyterHub wip       y y Visualisation Service y   y y y y SODA Service y   - y y y Gate-Keeper API         y y cavern y   y y y y Orchestrator Service y   y y y - perfSONAR y   y y y y Local Service Monitoring y   y y y y  

    • PI24 - UNCOVERED

    • PI24-PB SRCNet0.1 Team_Chocolate
    • SPO-3480

    Description

      For this feature, these deployments may be hosted on temporary infrastructure and/or infrastructure that does not meet the full operational requirements committed to via the v0.1 EoIs

      Some of these deployments may already be completed. The size of this feature will vary per SRC. Do not include optional services as part of this feature.

      See the implementation plan doc and miro for additional information and ongoing SRC plans.

      cavern has been conditionally added to the compulsory service list. Early PI24 development work / architectural decisions will answer if this is required to deliver the Data Management API and/or SODA Service.

      Deployment is intended to be a simple process. Additional development work required, per service or per SRC, may be split out into other features or contained here - whichever approach best enables teams to plan their efforts.

      For some local compulsory services, the technology stack is not fixed. If a technology is chosen that differs from proven implementations, it is the SRCs responsibility to plan and complete any additional work necessary to integrate their deployment with SRCNet's global services, including service monitoring. 

      Multiple other features are required to enable this work and should be linked and sequenced accordingly, IBNLT SP-4598, SP-4570, SP-4570, SP-4569, SP-4517

       

       

      Deploy the missing compulsory v0.1 services on CHSRC 

      • solve untrusted certificate issue
      • ~~perfSONAR
      • Local DM API
      • SODA
      • Jupyterhub (or compatible)
        • jupyterhub vs CANFAR vs openondemand
      • non-det RSE?

      See dev, prod cluster panels and v0.1 panels on miro board https://miro.com/app/board/uXjVK55UYPc=/ 

      CHSRC panel on the node implementation plan board - https://miro.com/app/board/uXjVK0qVHVs=/ 

      These services will be deployed on the CHSRC dev and prod clusters via argocd.

       

      Kubernetes storage resources need to be increased at CSCS.

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-4681 Deploy compulsory SRCNet 0.1 services in at least 4 SRC sites

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

          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-4570 Develop and deploy Helm chart for deploying SODA service in K8s

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

          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-4598 Develop and deploy helm chart for deploying perfSONAR in k8s

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Releasing
          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-4467 Service monitoring infra to incorporate v0.1 sites and 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...

          Page Loading...

          Structure

            Activity

              People

                Jesus.Salgado Salgado, Jesus
                Robert.Perry Perry, Robert
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (7.69%)

                  Feature Estimate: 1.5

                  IssuesStory Points
                  To Do56.0
                  In Progress   56.0
                  Complete11.0
                  Total1113.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel