Displaying View Policies

Displaying View Policies via VAST Web UI

To see the existing views configured on the cluster, select Element Store and then View Policies from the left navigation menu.

The following information can be displayed for each view policy:

Tip
To display or hide fields, click to the right of a column title, and then click to open a dropdown where you can select or unselect fields.

ID	The ID of the view policy.
Name	The name of the view 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. 0 means no atime updates.
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: NFS. NFS clients can set permission mode bits on files and directories when creating new files and directories or modifying existing files and directories. Attempts by SMB clients to set file and directory permissions are ignored. Files and directories created by SMB clients receive a configurable set of initial permission bits. SMB. SMB clients can set permissions on files and directories. Attempts by NFS clients to set permission bits for files and directories are ignored. Files and directories created on NFS clients inherit permissions set on the parent directory by the SMB client. Mixed Last Wins. This flavor is designed to act as natively as possible to whichever protocol is used to create or modify a file or directory. It allows permissions to be set and modified from all clients. As far as possible, this flavor is designed such that whenever a user changes permissions via a given protocol, the permission change that is applied in vast permissions is as the user intended. S3 Native. Supports S3 and provides a native experience for S3 usage. Also supports NFSv3 and NFSv4.1. S3 clients can set S3 ACLs on objects and on the view bucket. Attempts by NFS clients to set permission bits for files and directories are ignored. Access checks are done using the S3 access check algorithm. New objects created by NFS clients or created by S3 without setting ACL receive a default initial S3 object ACL, which gives the owner FullControl.
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: Client. The GIDs declared in the RPC as the user's leading group and auxiliary groups are trusted and provider-sourced groups are not considered. Providers. Group memberships retrieved from authorization providers are considered as the user's group memberships (as for SMB-only and multiprotocol views). The GIDs declared in the RPC are ignored. Client And Providers. Both the GIDs declared in the RPC and group memberships retrieved from authorization providers are considered. If the GID provided by the client does not match the GID retrieved from the authorization provider, the GID from the client is set. For more information about the impact of this setting, see The VAST Cluster Authorization Flow.The VAST Cluster Authorization Flow
NFS Read Write	The hosts that have read/write access to the view via NFS. An asterisk (*) is a wildcard character that includes all hosts.
NFS Read Only	The hosts that have read-only access to the view via NFS. An asterisk (*) is a wildcard character that includes all hosts.
SMB Read Write	The hosts that have read/write access to the view via SMB. An asterisk (*) is a wildcard character that includes all hosts.
Continuous Available	Indicates whether the view exposes continuously available SMB shares.
SMB Ready Only	The hosts that have read-only access to the view via SMB. An asterisk (*) is a wildcard character that includes all hosts.
S3 Read Write	The hosts that have read/write access to the view via S3. An asterisk (*) is a wildcard character that includes all hosts.
S3 Read Only	The hosts that have read-only access to the view via S3. An asterisk (*) is a wildcard character that includes 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.
Creation Time	The date and time at which the view policy was created.
Tenant	The tenant associated with the policy.

Displaying View Policies via VAST CLI

Run the viewpolicy list or viewpolicy show command.