Updated 15/02/2024
DTE Infrastructure Component

RUCIO

Federated Data Infrastructure
Image

Description

Providing a service that manages data locality. It provides a scalable solution for managing the dynamic locality of files in a heterogeneous, federated storage Datalake.

Built on more than a decade of experience, Rucio serves the data needs of modern scientific experiments. Large amounts of data, countless numbers of files, heterogeneous storage systems, globally distributed data centres, monitoring, and analytics. All coming together in a modular solution to fit your needs. Rucio provides a service that manages data locality.  It provides a scalable solution for managing the dynamic locality of files in a heterogeneous, federated storage Datalake.

When deployed, the Rucio software provides a service that allows a group of researchers to manage non-trivial amounts of data.  For any given file, dataset, collection of files, or container (a collection of files and datasets), it provides information on where that data is currently available. It also supports dynamic, time-limited data placement, with data being made available for some period (e.g., to support some computational workflow). It optimises the use of available storage by operating a cache, assuming that data that was previously used is more likely to be needed in the future. Desired data locality is expressed in terms of declarative rules.  These rules may be applied both to existing datasets and anticipated, future data.

Target Audience
+

In principle, all DT users that use the Datalake concept to manage their data are using Rucio.  Depending on the use cases, DT users may interact directly with Rucio, or they may use Rucio via some intermediate service.

License
+

Apache 2.0

Created by
+

Release Notes

This release represents the final release of the interTwin federated data management solution.

There are two external software components: FTS and Rucio.  They are fully established projects, independent of the interTwin project.  The software is production-ready, at TRL 9, and hardened with many years of production-critical use.  Both projects have multiple deployments of their software, operated by different communities.

The ALISE software is currently in a development phase, under the aegis of interTwin.  At the time of release, ALISE is TRL 4.  The user-facing functionality of ALISE is mostly feature-complete; however, anticipated changes to the API imply that the necessary integration work (whereby a service uses ALISE to identify a user) should be considered experimental. Feedback from early adopters is encouraged, but any plans to deploy ALISE should be tempered by the anticipated changes to the API.

The teapot software has also been developed within the interTwin project.  With this release, teapot is now TRL 6–7 and supports data transfer requirements of multiple, concurrent users. The per-user WebDAV instance management is automated, starting new services on demand, and terminating them if there is sufficient idle time.

Finally the first version of the Onedata S3 component is released, allowing integration of Onedata technology in the interTwin federated data management solution.

Future Plans

Some further improvements are planned for teapot. This includes integrating teapot with ALISE, to support automated identity management.

For ALISE, we anticipate possible improvements and stabilisation of the service-integration API, based on experience gained from integrating ALISE into various services. In addition, we plan to add support for client authentication in future versions of ALISE. This will limit access to the identity mapping information, providing this information to authorised services only.

As work continues with integrating the Datalake with various science use-cases, limitations may be found with the various components within the Datalake.  Any such problems will be reported to the corresponding component’s development and support teams.  The members of interTwin will offer effort to fix such issues, should such capacity become available during the project’s remaining lifetime.