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

Review ESCAPE JHub + Rucio integration

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

Details

    • SRCnet
    • Hide

      Wider knowledge of the approach within SRCNet which is a foundation for later discussions

      Show
      Wider knowledge of the approach within SRCNet which is a foundation for later discussions
    • 0.5
    • 0

    • Feature SP-2902 Integrate JupyterHub with the SRCNet Rucio datalake

    • 16.5

    • PI24 - UNCOVERED

    • SRC-DM SRC-SciPlat

    Description

      Who: Coral team and SRC nodes

      What: Recipe / Documented knowledge on how to connect RUCIO datalake to a JupyterHub instance

      Why: - To know how to add RUCIO as Storage endpoint within a JupyterHub instance - To be able to deploy a testbed with a working RUCIO storage instance connected to a JupyterHub

      Update for PI16: This is related to work done in PI15 (https://confluence.skatelescope.org/display/SRCSC/SKAO+Data+Lake+as+a+Service+Deployment+-+Setup+Guide). However, a precursory learning/replication exercise could be a good enabler for a team to then work on e.g. https://jira.skatelescope.org/browse/SP-2835 or https://jira.skatelescope.org/browse/SP-2834. 

       

      Attachments

        Issue Links

          Is delivered 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-2902 Integrate JupyterHub with the SRCNet Rucio datalake

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

          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-2902 Integrate JupyterHub with the SRCNet Rucio datalake

          • 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-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
          mentioned in

          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: (0%)

                  Feature Estimate: 0.5

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel