You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background
Now we are using FS shareMount as a root mount point for all FS storage with such shareMount in application services such as cp-api-srv and cp-search-srv.
In some cases it would be beneficial to mount specific Shared FS location with exact path (f.e. when permissions on NFS allows only specific folders to be mounted).
Approach
Let's introduce new field of the DataStorage object mountExactPath (boolean, default false) if true - such storage will be mounted to the API container with exact path.
This property can be specified only during storage creation. (DataStorageVO now also accepts mountExactPath value)
The text was updated successfully, but these errors were encountered:
…choose mount strategy for storage, if mountExactPath is true, will try to mount storage by exact path and not by fileShareMount path (#3746)
(cherry picked from commit 0c0fe21)
Background
Now we are using FS shareMount as a root mount point for all FS storage with such shareMount in application services such as
cp-api-srv
andcp-search-srv
.In some cases it would be beneficial to mount specific Shared FS location with exact path (f.e. when permissions on NFS allows only specific folders to be mounted).
Approach
Let's introduce new field of the DataStorage object
mountExactPath
(boolean, default false) if true - such storage will be mounted to the API container with exact path.This property can be specified only during storage creation. (DataStorageVO now also accepts
mountExactPath
value)The text was updated successfully, but these errors were encountered: