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

Proof of concept SODA-Rucio-Datalink Rucio integration demonstrator

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

Details

    • SRCnet
    • Hide

      This would serve to connect a Datalink service that can understand Rucio DIDs with a SODA service and allow the latter to serve data that is managed by Rucio. Current prototype SODA service doesn't support OIDC yet, thus this feature would attempt a simpler way of connecting the services such that the Datalink service provides authentication but this integration isn't managing authorization yet.

      Show
      This would serve to connect a Datalink service that can understand Rucio DIDs with a SODA service and allow the latter to serve data that is managed by Rucio. Current prototype SODA service doesn't support OIDC yet, thus this feature would attempt a simpler way of connecting the services such that the Datalink service provides authentication but this integration isn't managing authorization yet.
    • Hide
      • User discovers some data managed by Rucio based on IVOA metadata, discovers the SODA Services via DataLink Service, requests a cutout to the SODA service using the PFN provided by Rucio, SODA service serves this data to the user (by having 'back door' access).
      Show
      User discovers some data managed by Rucio based on IVOA metadata, discovers the SODA Services via DataLink Service, requests a cutout to the SODA service using the PFN provided by Rucio, SODA service serves this data to the user (by having 'back door' access).
    • 2
    • 2
    • 0
    • Team_ORANGE
    • Sprint 5
    • Hide

      Confluence page

      Show
      Confluence page
    • 20.2
    • Stories Completed

    • PI24 - UNCOVERED

    • PI19-PB multi-team

    Description

       

      Deploy an RSE colocated with a simple docker deployment of a SODA service. The storage exposed via the SRM and storage mounted/visible to SODA service is the same with simple, implicitly deducible file path structures.

       

      Noting this schematic from a discussion during PI planning 

      https://docs.google.com/presentation/d/16ZNeIRHCWLQR6dsncx-K8p3aNFpH4NTPFjQ8xKsnedI/edit#slide=id.p 

      Attachments

        Issue Links

          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-3071 Deploy external Rucio metadata database and connect IVOA discovery and access interfaces

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          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-3751 Advanced data discovery with the Rucio-datalink demonstrator using HiPS

          • 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.
          • 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-3504 Metadata Management Integration - Metadata Access Implementation

          • 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-3750 Advanced data discovery with the Rucio-datalink demonstrator using recursive DataLink

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                R.Barnsley Barnsley, Rob
                r.joshi Joshi, Rohini
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1135.0
                  Total1135.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel