The filesystem mount feature allows the automatic addition of NFS v3 or v4 volumes or mounts to virtual nodes/containers. This allows virtual nodes/containers to directly access NFS shares as if they were local directories. You can use this feature to provide common files across all of the virtual nodes/containers of a given tenant, such as a common configuration file that will be used by each of the virtual nodes/containers in the Marketing tenant. This eliminates the need to manually copy common files to individual virtual nodes/containers.
All virtual nodes/containers include a root directory called /bd-fs-mnt.
If one or more filesystems have been mounted, then this directory will contain the
mounted filesystems. Each mounted filesystem in this directory will have the same name
as the Mount Name that was assigned when creating the FS mount (see Creating a New FS Mount).
Filesystems are mounted on a per-tenant basis, meaning that a given filesystem mount will be applied to each of the virtual nodes/containers in the tenant where that filesystem was created. For example, if you create a filesystem mount in the Marketing tenant, then each of the virtual nodes/containers created in the Marketing tenant will include that filesystem mount. Tenant Administrator users can create, modify, and delete filesystem mounts. Tenant Member and Platform Administrator users may view filesystem mounts but cannot modify them.
A filesystem may be mounted as either:
FSmount is backed by a POSIX-based filesystem, such as the HPE Ezmeral Data Fabric POSIX client or NFS server. When HPE Ezmeral Container Platform is configured with HPE Ezmeral Data Fabric storage as its tenant storage, then FSmount points to HPE Ezmeral Data Fabric POSIX clients by default.
Inside every container:
/bd-fs-mnt directory./bd-fs-mnt.See the following articles for additional information: