RUCIO Jupyterlab extension

Federated Data Infrastructure

Description

Allows using certain Rucio capabilities like interactive data browsing and triggering data replicas to the storage volume attached to the jupyter server.

The Rucio extension is a jupyterlab add-on that acts as an interactive user client, intended to ease data accessibility and data discoverability. It allows using certain Rucio capabilities like interactive data browsing and triggering data replicas to the storage volume attached to the jupyter server.

The extension acts as an interface to the federated data infrastructure, amining to simplify the interaction with the Rucio instance.

Once a Jupyter session is spawned, the extension will be available on the left sidebar. The configuration to interact with the interTwin Rucio instance is executed in the background during the spawning of the session, allowing DT users to interact immediately with the Datalake.

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.

Documentation

https://rucio.cern.ch/documentation/

License

Apache 2.0

Source Code

https://github.com/rucio/rucio

Created by

CERN

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.

RUCIO Jupyterlab extension

Description

Release Notes

Future Plans

Related Components