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

Science Gateway v0.1 - Roadmap

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

Details

    • Science Gateway v0.1 - Roadmap
    • SRCnet
    • 0

    Description

      Key Initiatives and Features

      Deployment and Operation of CANFAR Science Platform:

      • Support all SRCNet sites.
      • Deploy interactive and batch queues using kueue from Kubernetes.
      • Demonstrate interactive job execution under heavy batch load.

      User Journey Mapping:

      • Create user journeys based on user personas to inform system design.
      • This analysis will shape the SRCNet v0.1 and future versions.

      Data Management Integration:

      • Users can create data collections tied to SRCNet Groups in the AAI system.
      • Develop an API for user preferences to manage data access.

      Single Sign-On for Science Platform Services:

      • Enable seamless access to services like CANFAR, JHub, and Azimuth without additional credentials after initial login.

      Docker Image Management:

      • Integrate public Docker images with proper labeling for user sessions.
      • Ensure compliance with OCI standards and facilitate metadata retrieval from images.

      Compute Quotas Enforcement:

      • Implement project-based compute quotas within CANFAR based on SRCNet Groups.
      • Initial iterations will focus on human-managed group and quota creation.

      SODA Service Functionality Extension:

      • Explore new features for the SODA service, including coordinate system conversions and pixel down-sampling.

      Service Discovery API Integration:

      • Integrate service discovery based on metadata into the Science Gateway.

      Data Environment Creation for Analysis:

      • Automate the creation of data environments for user-selected data products, tracking job status asynchronously.

      Kubernetes Deployment Updates:

      • Complete Kubernetes deployment in the OpenStack cloud for the CANFAR Science Platform, ensuring capabilities for the Swedish site.

      Collaboration and Feedback for Architecture Document:

      • Various teams (Coral, Tangerine, Olive) to provide feedback on architecture components related to distributed deployment, science archive, user interface, and resource management.

      Nextflow Workflow Deployment:

      ••Utilize AusSRC’s Nextflow system for deploying workflows on heterogeneous HPC platforms, with a focus on running a representative workflow for evaluation.

      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-4747 Science Gateway All Versions - Roadmap

          • Not Assigned - Priority is not assigned yet.
          • Funnel

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-4873 Development VS v0.1 - Roadmap

          • Not Assigned - Priority is not assigned yet.
          • Funnel
          Parent Of

          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-4203 Implementation of CANFAR Science platform to kubernetes cluster on JPSRC OpenStack

          • Not Assigned - Priority is not assigned yet.
          • Funnel

          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-4310 Prototype a "Project" data model within the science gateway

          • Not Assigned - Priority is not assigned yet.
          • Funnel

          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-4016 Deploy and maintain instance of CANFAR science platform at CNSRC

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Analyzing

          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-4583 Support unforseen CANFAR Science Platform deployment issues

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • 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-4300 Single Sign-On to access Science Platform services from the Science Gateway

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • 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-4389 Allow access to/from CANFAR science platform at CNSRC

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • 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-4581 Further optimize CANFAR Science Platform resource utilization

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • 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-4001 Migration of Canfar Science platform to kubernetes cluster on SWESRC OpenStack

          • 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-4265 Pull containers from alternate repositories for CANFAR Science Platform

          • 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-4263 Implement Compute Quotas for CANFAR Science Platform

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • 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-4318 Consolidate Fragmented SRCNet User Artefacts (cases, stories, journeys, flows, personas)

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • 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-4547 Add Group Management UI to the Science gateway

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • 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-4548 Science Gateway Deployment Improvements

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Implementing

          Spike - A time limited investigation to get some knowledge SP-3285 Understand requirements of SDH&P pipelines (time boxed spike)

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

          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-3286 Pick a workflow and a workflow engine, and API that can be used to execute the pipeline that we want to use for demonstration

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

          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-3307 Olive: Review Architecture Document and Top-Level Roadmap

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

          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-3310 Tangerine: Review Architecture Document

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

          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-3311 Coral: Review Architecture Document and Top-Level Roadmap

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

          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-4102 Add query UI to Science Gateway Discover Services through Services Discovery Service

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

          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-3925 Mapping MSND computing environments to workflows in the SRCNet repository 

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done

          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-3295 Describe Nextflow workflow deployment platform.

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done

          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-3926 Software repository for the Mini-SRCNet demonstrator (MSND)

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done

          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-4101 Define Science Gateway - Data Management Server Interface for selected data

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done

          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-4124 Add more data operations on SODA Service

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done

          Structure

            Activity

              People

                Debashis.Mitra Mitra, Debashis
                Debashis.Mitra Mitra, Debashis
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Structure Helper Panel