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.  Its main advantage over existing solutions is its ability to provide access to existing storage, integrating with existing workflows. This is achieved by identifying incoming requests against existing users of a facility, and honouring the file-system permissions already in place.  No modification to the storage is needed of the storage to support this access.

Teapot supports direct data transfers (uploads and download) with various publicly available clients.  It also supports site-to-site file transfers, as initiated and monitored by FTS.

 

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

The teapot software has been developed within the interTwin project.  Teapot is 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. It also offers integration with ALISE, to support automated identity management.

Future Plans

Some further improvements are planned for teapot, including a more user-friendly configuration and the addition of VO membership-based authentication.  More features will be considered, as the software is deployed by additional facilities and under different use-cases.