A view exposes an Element Store path to one or more client protocols.
A view specifies the following:
A location within the VAST Element Store that the view exposes to clients.
A view can be created at an existing path in the filesystem, or at a new path (specified during view creation). Deleting a view from the VMS does not delete the underlying path in the filesystem.
In multi-tenant environments, a view also specifies the tenant to which it belongs.
Client access protocols that are allowed to store and access data at the exposed path, along with the respective methods for exposing the path to each enabled protocol.
Available protocols may depend on the tenant configuration and include NFS, SMB and S3. In addition, you can create views that expose tabular data.
A view policy, which defines various security and protocol-related settings to further control access to the data. For example, you can use a view policy to restrict access by host IP, or to determine how the cluster handles file and directory permissions for multi-protocol access.
Additional settings for various features, such as Global Synchronization (for replicated views) or WORM.
A view policy defines security settings that further control access to the data, such as restricting types of access by host IP or choosing a security 'flavor' which determines cross protocol behavior for handling permissions for users and groups to access files or objects.
VAST Cluster has one default view and one default view policy. Every view has a view policy and a view policy may be used by multiple views.
Initially, a view is preconfigured 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.