Articles in this section

viewpolicy modify

Sara Levy
  • Updated
Follow

This command modifies a view policy.

Usage
viewpolicy modify --id ID
                  [--name NAME]
                  [--flavor NFS|SMB|MIXED_LAST_WINS|S3_NATIVE]
                  [--auth-source RPC|PROVIDERS|RPC_AND_PROVIDERS]
                  [--path-length LCD|NPL]
                  [--allowed-characters LCD|NPL]
                  [--gid-inheritance linux|bsd]
                  [--atime-frequency ATIME_FREQUENCY]
                  [--nfs-read-write [HOSTS]]
                  [--nfs-read-only [HOSTS]]
                  [--nfs-no-squash [HOSTS]]
                  [--nfs-root-squash [HOSTS]]
                  [--nfs-all-squash [HOSTS]]                  
                  [--enable-nfs-return-open-permissions]
                  [--disable-nfs-return-open-permissions]
                  [--enable-nfs-posix-acl]
                  [--disable-nfs-posix-acl]
                  [--enable-32bit-fileid]
                  [--disable-32bit-fileid]
                  [--enable-expose-id-in-fsid]
                  [--disable-expose-id-in-fsid]
                  [--nfs-trash-access [HOSTS]]
                  [--smb-file-mode SMB_FILE_MODE]
                  [--smb-directory-mode SMB_DIRECTORY_MODE]
                  [--vip-pool-ids POOL_IDs]
                  [--nfs-minimal-protection-level]
                  [--s3-visibility USERS]
                  [--s3-visibility-groups GROUPS]
                  [--enable-apple-sid]
                  [--disable-apple-sid]
Required Parameters

--id ID

Specifies the view policy to modify.
General Options

--name NAME

Sets a unique name for the view policy.

--flavor NFS|SMB|MIXED_LAST_WINS|S3_NATIVE

Sets the security flavor for a multiprotocol view policy to one of two security flavors:

  • 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 set of initial permission bits, configurable using the --smb-file-mode and --smb-directory-mode options.

  • 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.

    This flavor is required for NFSv4.1 with support for NFSv4 ACLs.

  • S3_NATIVE. Supports S3 and NFSv3. Does not support NFSv4.1 or SMB. Permissions can be changed by S3 clients using S3 ACLs. Access checks are done using the S3 access check algorithm.New buckets receive a default initial S3 bucket ACL, which gives the bucket owner FullControl. New objects receive a default initial S3 object ACL, which gives the owner FullControl.

To learn more about security modes, see: Controlling File and Directory Permissions Across Protocols.

--auth-source RPC|PROVIDERS|RPC_AND_PROVIDERS

Specifies which source is trusted for the user's group memberships, when users' access to the view is authorized. Possible values:

  • RPC. For NFS only. The GIDs declared in the NFS request as the user's leading group and auxiliary groups are trusted and provider-sourced groups are not considered.

    Note

    This option is not supported for NFSv4.1.

  • PROVIDERS. Group memberships retrieved from authorization providers are considered as the user's group memberships. The GIDs declared in the request are ignored.

    Note

    This option is required for views that have SMB enabled.

  • RPC_AND_PROVIDERS. Both the GIDs declared in an NFS request and group memberships retrieved from authorization providers are considered.

    Note

    If Kerberos authentication is used by NFSv4.1 clients, the groups declared in the RPC are ignored.

--vip-pool-ids POOL_IDs

Dedicates VIP Pools to the view policy. Specify POOL_IDs as a comma separated list of VIP pool IDs.

For example: --vip-pool-ids 1,2,3,4
NFS Security Flavor Options

--smb-file-mode SMB_FILE_MODE

--smb-directory-mode SMB_DIRECTORY_MODE

For multiprotocol views, if the security flavor is NFS, specify default unix permission bits for files (--smb-file-mode) and directories (--smb-directory-mode). These are applied as initial permissions to files and directories created by SMB or S3 clients.

Since these are initial permissions, changes to these values affect subsequently created files and directories and do not affect existing files and directories.

Specify SMB_FILE_MODE and SMB_DIRECTORY_MODE in three digit numeric notation, in which each digit represents a component of the permissions: user, group and others (in that order). Each digit is the sum of the following component bits:

  • If reading is permitted, the read bit adds 4 to the component.

  • If writing is permitted, the write bit adds 2 to the component.

  • If execution is permitted, the execute bit adds 1 to the component

Example

Supposing you want to set the following permissions for file mode:

user

group

others

read

permitted

permitted

permitted

write

permitted

not permitted

not permitted

execute

not permitted

not permitted

not permitted

The user's read bit (4) and a write bit (2) total 6, the group and others each have a read bit only so that is 4 each. Therefore, you set the permission bits to 644:

--smb-file-mode 644
Defaults

SMB file mode permission bits: 644

SMB directory mode permission bits: 755
S3 Options

--s3-visibility USERS

Specify users to enables those users to list buckets that are created using this policy even if they do not have permission to access those buckets.

When an S3 user sends a bucket listing request, the command returns a list of all buckets the user owns and all buckets that they have this listing permission for, even if they do not have permission to access those buckets.

Specify USERS as a comma separated list of user names.

Example: --s3-visibility jsmith,sjobs

--s3-visibility-groups GROUPS

Specify groups to enable members of those groups to list buckets that are created using this policy even if they do not have permission to access those buckets.

Specify GROUPS as a comma separated list of group names.

Example: --s3-visibility-groups interns,deptheads
SMB Options

--enable-apple-sid

For use when connecting from Mac clients to SMB shares, this option enables Security IDs (SIDs) to be returned in Apple compatible representation.

--disable-apple-sid

Disables --enable-apple-sid.
Advanced Multi-Protocol Options

--path-length LCD|NPL

Specifies the policy for limiting file path component name length.

Possible values:

  • LCD (default) (=Lowest Common Denominator). Imposes the lowest common denominator file path component length limit of all VAST Cluster-supported protocols, regardless of the specific protocol enabled on a specific view.

  • NPL. (=Native Protocol Limit). Imposes no limitation beyond that of the client protocol.

    Caution

    If you select this mode in a view policy and then in the future expose a view using this policy to a previously not exposed protocol, that view might contain files that won't be accessible by the newly added protocol, due to the limitations of that protocol.

--allowed-characters LCD|NPL

Specifies the policy for which characters are allowed in file names.

Possible values:

  • LCD (default). Allows only characters allowed by all VAST Cluster-supported protocols, regardless of the specific protocol enabled on a specific view.

  • NPL. (=Native Protocol Limit). Imposes no limitation beyond that of the client protocol.

    Caution

    If you select this mode in a view policy and then in the future expose a view using this policy to a previously not exposed protocol, that view might contain files that won't be accessible by the newly added protocol, due to the limitations of that protocol.

--gid-inheritance linux|bsd

Specifies how files receive their owning group when they are created.

Possible values:

  • linux (default). Each new file inherits its owning group from the group ID of the user who creates the file.

  • bsd. Each new file inherits its owning group from the group ID of the parent directory.
Advanced NFS Options

--atime-frequency 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. Consider that a very low value might have a performance impact if high numbers of files are being read.

Specify ATIME_FREQUENCY as an integer followed by a unit of time (s = seconds, m= minutes, h=hours, d=days).

Example: 1h

--enable-nfs-return-open-permissions

Sets the NFS server to unilaterally return open (777) permission for all files and directories when responding to client side access checks.

This setting works around a permissions issue that occurs with Windows clients. Windows clients perform NFSv3 access checks before executing read/write requests. This client side check uses the UID and the primary GID of the user without taking into account secondary GIDs. If the check fails, requests are not executed. This means that some permissions may not be honored as they should be, such as those based on secondary groups.

When return open permissions is enabled, VAST Cluster returns open permissions for client side access checks, so that the Windows client allows access rights and executes read/write requests. VAST Cluster does a proper permission check when the request is executed.

Caution

Use this feature with caution if Windows client systems are shared by more than one user, since the following security breach could occur: While a user is accessing a file with correct permissions and the file is cached in memory on the Windows system, if another user tries to access the same file, access is incorrectly allowed. No proper access check is done for the second user.

--disable-nfs-return-open-permissions

Disables the NFS return open permissions setting. See --nfs-return-open-permissions.

--enable-nfs-posix-acl

Enables full support of extended POSIX Access Control Lists (ACL). By default, VAST Cluster supports the traditional POSIX file system object permission mode bits, (minimal ACL mode) in which each file has three ACL entries defining the permissions for the owner, owning group, and others, respectively. To learn more about POSIX ACL, see https://linux.die.net/man/5/acl.

Note

Thesetfacl Linux command is blocked if this option is not enabled.

--disable-nfs-posix-acl

Disables support for extended POSIX ACLs, restoring default minimal ACL mode.

--enable-32bit-fileid

Sets the VAST Cluster's NFS server to use 32bit file IDs. This setting supports legacy 32-bit applications running over NFS.

--disable-32bit-fileid

Disables 32bit file IDs (default).

--nfs-minimal-protection-level

Set the Minimal Protection Level to accept from NFSv4.1 client RPCs:

  • KRB_AUTH_ONLY. Allows client mounts with Kerberos authentication only.

  • SYSTEM. Allows client mounts using either the AUTH_SYS RCP security flavor (the traditional default NFS authentication scheme) or Kerberos authentication.

  • NONE. Allows client mounts with the AUTH_NONE (anonymous access), or AUTH_SYS RCP security flavors, or with Kerberos authentication.
NFS Host Access Options

These options set which NFS client hosts can access the view with which access types. In each access type option, HOSTS can be specified as a comma separated series of any of the following:

  • A single IP.

  • A netgroup key, which starts with '@'. This is supported for NIS netgroups if NIS is configured. For information about how to use netgroups, see Using NIS Netgroups to Authorize Host Access to NFS Exports for more information.

    Note

    Netgroups are not supported for multiprotocol views.

  • A subnet indicated by CIDR notation. For example: 1.1.1.1/24.

  • A range of IPs indicated by an IP address with '*' as a wildcard in place of any of the 8-bit fields in the address. For example, 3.3.3.*, or 3.3.*.*.

The access types comprise these categories:

  • Controlling read and write operations:

    • Read / Write. Read/write access.

    • Read Only. Read only access.

  • Controlling squash policy:

    • No Squash. All operations are supported. Use this option if you trust the root user not to perform operations that will corrupt data.

      Note

      This option is not relevant for NFSv4.1 users if Kerberos is used, since AD does not include the 'root' user principal by default and since the handling of credentials for the user with UID 0 depends on configuration of the rpc.gssd service.

    • Root Squash. The root user is mapped to nobody for all file and folder management operations on the export. This enables you to prevent the strongest super user from corrupting all user data on the VAST Cluster.

      Note

      This option is not relevant for NFSv4.1 users if Kerberos is used, since AD does not include the 'root' user principal by default and since the handling of credentials for the user with UID 0 depends on configuration of the rpc.gssd service.

    • All Squash. All client users are mapped to nobody for all file and folder management operations on the export.

  • Controlling access to the trash folder:

    • Trash Access. This option does not appear here by default. It appears only if Enable trash folder access is enabled on the Settings page. Granting this permission gives hosts the ability to delete files by moving them into a trash folder, from which they are automatically deleted. Requires also No Squash. For more information, see Trash Folder (for Rapid Parallel File Deletion).

      Note

      This access type is applicable for NFSv3 clients only. The Trash folder feature is not supported for NFSv4.1 clients.

You can add hosts to any and all of the types, but within each category no more than one type will be applied to any given host. If a host is specified with multiple entries in mutually exclusive types, the conflict is resolved as follows:

  • An IP overrides a netgroup, a netgroup overrides a CIDR, and a CIDR overrides a wildcard expression.

  • If a conflict remains after the previous rule is applied, then:

    • Read Only overrides Read / Write.

    • All Squash overrides Root Squash.

    • Root Squash overrides No Squash.

By default, all hosts have read-write and root squash access.

--nfs-read-write [HOSTS]

Controls which NFS client hosts have read-write access to the view.

By default, all hosts have read-write access.

To remove all hosts from read-write access, include this option without any values.

To restrict read-write access to specific hosts, specify HOSTS according to the format description above this table.

For example: --read-write 98.51.100.1,98.51.100.2

--nfs-read-only [HOSTS]

Specifies which NFS client hosts have read-only access to the view.

Specify HOSTS according to the format description above this table.

--nfs-no-squash [HOSTS]

Specifies which hosts have no squash access. With no squash, all operations are supported. Use this option if you trust the root user not to perform operations that will corrupt data.

Specify HOSTS according to the format description above this table.

--nfs-root-squash [HOSTS]

Controls which hosts have root squash access. With root squash, the root user is mapped to nobody for all file and folder management operations on the export. This enables you to prevent the strongest super user from corrupting all user data on the VAST Cluster.

By default, all hosts have root squash access.

To remove all hosts from root squash access, include this option without values.

To restrict root squash to specific hosts, specify HOSTS according to the format description above this table.

--nfs-all-squash [HOSTS]

Specifies which hosts have all squash access. With all squash, all client users are mapped to nobody for all file and folder management operations on the export.

Specify HOSTS according to the format description above this table.

--nfs-trash-access [HOSTS]

Specifies which hosts have access to the trash folder, if the trash folder is enabled.

Specify HOSTS according to the format description above this table.
Example

This example modifies some of the NFS host access rules of an existing view policy.

vcli: admin> viewpolicy modify --id 4 --nfs-read-write 10.0.0.2,10.0.0.3,10.0.0.4  --nfs-read-only 10.0.0.* --nfs-trash-access 10.0.0.4

Related articles

Comments

0 comments

Article is closed for comments.