VAST Cluster has one default view and one default view policy. A view policy is a reusable set of configurations. Every view has a view policy and a view policy may be used by multiple views.
Initially, a view is pre-configured for access via NFS. It exposes the top location of the file system "/". The default view policy gives read/write access to all hosts and root squashes all hosts. Both the initially configured view and the default view policy can be modified.
To see the existing views configured on the cluster, go to the Element Store page and select the Views tab.
The following settings are displayed:
Path |
The full path from the top level of the storage system on the cluster to the location exposed by the view. |
Alias |
An alias for the mount path of an NFS export. |
Share |
For SMB shares, the share name. |
Bucket |
Name of the S3 bucket used to access the view via S3, if there is one. |
Bucket Owner |
User name of the S3 bucket owner. |
Policy Name |
The view policy. |
Protocols |
The protocol(s) the view is exposed to. Possible values:
|
Physical Capacity |
The amount of physical capacity used by the view. |
Logical Capacity |
The amount of data logically written to the view directory prior to data reduction. |
You can modify and remove views using the Actions menu in the far right column.
To see the existing view policies configured on the cluster, go to the Element Store page and select the View Policies tab.
The following settings can be displayed (to change which fields appear, click the Choose Columns to Display button (
):
Name |
The name of the policy. |
Atime Frequency |
atime is a metadata attribute of NFS files that represents the last time the file was updated. atime is updated on read operations if the difference between the current time and the file's atime value is greater than the configured atime frequency. |
Flavor |
The security flavor of the policy. The security flavor determines how file and directory permissions are controlled. For a full description of the security flavors, see Controlling File and Directory Permissions Across Protocols. In brief, the possible values are:
|
Group Membership Source |
Determines the source for retrieving group memberships of NFS users for the purposes of authorizing access to files and directories. Possible values:
For more information about the impact of this setting, see The VAST Cluster Authorization Flow. |
Read Write |
The hosts that have read/write access to the view via NFS. * is a wildcard indicating all hosts. |
Read Only |
The hosts that have read only access to the view via NFS. * is a wildcard indicating all hosts. |
All Squash |
The hosts that have all squash applied to them when accessing the view via NFS. With all squash, all client users are mapped to nobody for all file and folder management operations on the export. |
No Squash |
The hosts that have no squash applied to them when accessing the view via NFS. With no squash, all operations are supported. Use this option if you trust the root user not to perform operations that will corrupt data. |
Root Squash |
The hosts that have root squash applied to them when accessing the view via NFS. With root squash, the root user is mapped to nobody for all file and folder management operations on the export. |
Trash |
The hosts that have access to the trash folder when accessing the view via NFS (NFSv3 only). These hosts have the ability to delete files by moving them into a trash folder, from which they are automatically deleted. |
You can modify and remove view policies using the Actions menu in the far right column.
Run the view list and viewpolicy list commands to list existing views and view policies via the VAST CLI.
Comments
0 comments
Article is closed for comments.