Updated 15/02/2024
DTE Infrastructure Component

Teapot

Federated Data Infrastructure
Image

Description

An easy-to-install edge service that a facility may deploy to provide remote access to their storage, in order to facilitate data ingress and egress.

Teapot is an easy-to-install edge service that a facility may deploy to provide remote access to their storage, in order to facilitate data ingress and egress.  It provides the reference implementation of the teapot architecture: a scalable and technology agnostic approach to support data ingress and egress.

FTS uses teapot to copy files from some external source into the facility’s file storage, or to copy data from the facility’s storage to some external destination. Rucio uses teapot to manage replicas at the facility: creating new replicas with FTS or deleting cached data when the storage is under space pressure.

Unlike existing storage solutions that are compatible with Datalake, teapot does not require exclusive control of the underlying storage. Instead, it supports existing access methods. This allows facility admins to deploy teapot on top of existing storage solutions without disrupting established modes of access.

 

 

Target Audience
+

Teapot is a core component that most users do not access directly.  Instead, teapot is used by any DT manager or user who is (directly or otherwise) managing data locality.

One reason for transferring data is to satisfy the data requirements of some workflow when the required data is missing from the local storage of the facility that will run the workflow.  Under these circumstances, the user that triggered the workflow is using the teapot software if either the source facility (hosting the data) or destination facility (requiring the data) has deployed the teapot software.

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.