Loading...

Xporter

XML

Word

Printable

ARTs:

Data Processing
Benefit hypothesis:

Hide

Gain experience in deploying and operating Rucio, this will allow us to initiate long haul data transfers in the future and assess if and where Rucio as a data management solution fits into the SRC-tech sphere.

Show
Gain experience in deploying and operating Rucio, this will allow us to initiate long haul data transfers in the future and assess if and where Rucio as a data management solution fits into the SRC-tech sphere.
Acceptance criteria:

Hide

Rucio server running with the essential daemons, test transfers to/from UK sites successfully performed via Rucio.

Show
Rucio server running with the essential daemons, test transfers to/from UK sites successfully performed via Rucio.
Feature Points:
2.5
Initial Size:
2.5
WSJF:
10
Epic Link:
SRC Prototyping
Agile Teams:

Team_ESCAPEES
Due Sprint:
Sprint 5
Story Point Burn-up:
Overdue:
Outcomes:

Hide

Documented in the repo README: https://gitlab.com/ska-telescope/src/ska-rucio-prototype

Show
Documented in the repo README: https://gitlab.com/ska-telescope/src/ska-rucio-prototype
Resolved PI.Sprint:
11.3

Feature Checklist:

Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

Deploy an SKA-owned Rucio instance on multi-node K8s cluster running on IRIS cloud machines.

This will mostly entail:

Rucio server with the essential daemons running. These are packaged in the helm charts (core functionality only atm which is what we desire)
Server auth: using existing Robot certificate
User auth: user accounts created manually, no IAM integration planned till at least next PI
RSE config: Will be done manually,
FTS: CERN FTS + RAL FTS
Storage: UK storage sites to start with
Resources: multinode k8s cluster on STFC Cloud (c2.large flavour)
(Stretch) Monitoring: Helm charts exist, also for daemon monitoring (LIGO)

Story Point Burn-up: (100.00%)

Feature Estimate: 2.5

Deploy a Rucio instance on IRIS