Tenant/Project Storage

NOTE This article uses the term "tenant" to refer to tenants and AI/ML projects.

Tenant storage is an optional storage location that is shared by all nodes within a given tenant. Tenant storage can be configured to use HPE Ezmeral Data Fabric on Bare Metal, HPE Ezmeral Data Fabric on Kubernetes, or a remote NFS system. To use an HPE Ezmeral Data Fabric implementation as tenant storage, you must register HPE Ezmeral Data Fabric. See HPE Ezmeral Data Fabric as Tenant/Persistent Storage. Alternatively, you can create a tenant without dedicated storage.

NOTE If all tenants are created using the same tenant storage service settings, then no tenant can access the storage space of any other tenant.

When a new tenant is created, that tenant automatically receives a DataTap called TenantStorage that points at a unique directory within the tenant storage space. This DataTap can be used in the same manner as other DataTaps, but it cannot be edited or deleted. This does not apply if tenant storage has not been defined (meaning that you selected None for Tenant Storage during installation, as described in Platform Controller Setup).

The TenantStorage DataTap points at the top-level directory that a tenant can access within the Tenant Storage service. The Tenant Administrator can create or edit additional DataTaps that point at or below that directory.

If the tenant storage is based on a local HDFS, then the Platform Administrator can specify a storage quota for each tenant. The HDFS back-end is used to enforce this quota, meaning that the quota applies to storage operations that originate from either the DataTap browser or the nodes within that tenant.

Root tenant storage folders are created under the deployment global tenant storage root. For example, given a global tenant storage root of /a/b, the tenant-specific tenant storage root directories will be /a/b/1 for Tenant 1 and /a/b/2 for Tenant 2.

You may create DataTaps that point to any subdirectory within the global tenant storage root, so long as that location cannot access another tenant's tenant storage root directory, nor the global tenant storage root. For example:

  • You could create a DataTap in Tenant 1 that points to /a/b/SharedStorage, because that directory is not part of any existing tenant's Tenant Storage root.
  • You will also be able, as Tenant 2, to create another DataTap that points to /a/b/SharedStorage, thereby allowing data sharing between Tenant 1 and Tenant 2.
NOTE Tenant 2 cannot create a DataTap to the /a/b/1/SharedStorage directory, because the /a/b/1 directory is the root tenant storage directory for Tenant 1.

Users who have a Tenant Administrator role may view and modify detailed DataTap information. Members may only view general DataTap information and are unable to create, edit, or remove a DataTap.

NOTE Data conflicts may occur if more than one DataTap points to a location being used by multiple jobs at once.