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

Integrate JupyterHub with the SRCNet Rucio datalake

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

Details

    • SRCnet
    • Hide

      The proposed measurable end-user benefit is that this feature would validate access from the SRCNet to existing data in the SKAO Datalake Testbed via JupyterNotebooks.

      Show
      The proposed measurable end-user benefit is that this feature would validate access from the SRCNet to existing data in the SKAO Datalake Testbed via JupyterNotebooks.
    • Hide

      AC1: Put into practice the documentation on how to configure/activate components/plugins for JupyterNotebooks provided in https://jira.skatelescope.org/browse/SP-2654 within SPSRC (and other Coral Team facilities).
      AC2: Demonstrate that from JHub it is possible to list/access SKAO DataLake testbed data through the corresponding extensions.
      AC3: Document data authorisation model for this.

      Show
      AC1: Put into practice the documentation on how to configure/activate components/plugins for JupyterNotebooks provided in https://jira.skatelescope.org/browse/SP-2654 within SPSRC (and other Coral Team facilities). AC2: Demonstrate that from JHub it is possible to list/access SKAO DataLake testbed data through the corresponding extensions. AC3: Document data authorisation model for this.
    • 1
    • 1
    • 0
    • Team_CORAL
    • Sprint 5
    • Hide

      Platform deployed with all the components and working but with an error authenticating users from IAM and the container related. FO was contacted to continue this issue next PI17.

      Main result: https://github.com/manuparra/dlaas

      AC1: https://confluence.skatelescope.org/display/SRCSC/COR-67+Learn+SKAO+Datalake+as+a+Service+documentation?src=contextnavpagetreemode

      AC2 and AC3, gathered in https://github.com/manuparra/dlaas

      Show
      Platform deployed with all the components and working but with an error authenticating users from IAM and the container related. FO was contacted to continue this issue next PI17. Main result:  https://github.com/manuparra/dlaas AC1: https://confluence.skatelescope.org/display/SRCSC/COR-67+Learn+SKAO+Datalake+as+a+Service+documentation?src=contextnavpagetreemode AC2 and AC3, gathered in https://github.com/manuparra/dlaas
    • 20.2
    • Stories Completed, Outcomes Reviewed, Demonstrated, Accepted by FO

    • PI23 - UNCOVERED

    • SRC-DM SRC-SciPlat

    Description

      The idea is to create a testbed where we can validate that data stored in the SRCNet Rucio can be accessed through a JupyterHub instance. This is related to the SP-2654

      Attachments

        Issue Links

          Delivers

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-2654 Review ESCAPE JHub + Rucio integration

          • 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.
          • Discarded
          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-2834 Improve Rucio uploads with DLaaS

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded

          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-2835 Improve session persistence within DLaaS

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded
          relates to

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-2654 Review ESCAPE JHub + Rucio integration

          • 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.
          • Discarded
          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...

          Structure

            Activity

              People

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

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete47.0
                  Total47.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel