This command creates a tenant.
Usage
tenant create --name NAME
[--enable-privileged-domain-user-restore-access]|[--disable-privileged-domain-user-restore-access]
[--enable-privileged-domain-group-backup-access]|[--disable-privileged-domain-group-backup-access]
[--enable-privileged-domain-group-restore-access]|[--disable-privileged-domain-group-restore-access]
[--privileged-domain-user-logon-name]
[--privileged-domain-group-sid SID]
[--local-administrators-group-name NAME]
[--default-others-share-level-perm FULL|READ|CHANGE]
[--encryption-group ENCRYPTION_GROUP]
[--trash-gid TRASH_GID]
[--client-ip-ranges IP_RANGES]
[--posix-primary-provider AD|LDAP|NIS]
[--login-name-primary-provider AD|LDAP|NIS]
[--ad-provider-id ID]
[--ldap-provider-id ID]
[--nis-provider-id ID]
[--enable-use-smb-native|--disable-use-smb-native]
[--enable-require-smb-signing|--disable-require-smb-signing]
[--allow-disabled-users]|[--prohibit-disabled-users]
[--allow-locked-users]|[--prohibit-locked-users]
[--enable-nfs-v4.2]|[--disable-nfs-v4.2]
[--local-provider-id ID]
[--preferred-owning-group PROTOCOL_BASED|POSIX_GID]
[--allowed-delegations READ|WRITE|READ_WRITE|NONE]
[--enable-grant-unrequested-delegations-by-default|--disable-grant-unrequested-delegations-by-default]
[--smb-encryption-state OFF|AVAILABLE|DESIRED|REQUIRED]
[--max-views MAX]
[--capacity-rules CAPACITY_RULES]
[--static-limits STATIC_LIMITS]
Required Parameters
| Specifies a name for the tenant. |
Options
| Enables the privileged SMB user. |
| Disables the privileged SMB user. |
| Enables the privileged SMB group. |
| Disables the privileged SMB group. |
| Enables read and write control access for the privileged SMB user group. Members of the group can perform backup and restore operations on all files and directories, without requiring read or write access to the specific files and directories. |
| Disables write control access for the SMB privileged user group. If enabled (see |
| An optional custom user name for the SMB or NFSv4.1 privileged user. If not set, the user name is 'vastadmin' in the cluster's joined domain. |
| Specify a custom group SID in order to have a working SMB or NFSv4.1 privileged group with backup operator privileges. If not set, the SMB privileged group is set to the Backup Operators domain group (S-1-5-32-551), which, due to a known issue, does not receive backup operator privileges. |
| Specify a custom name for the privileged SMB group. If not specified, the privileged SMB group name is Backup Operators. |
| Sets the default 'Everyone' Group SMB share-level permission for the tenant. This default permission affects all views in which share-level ACL is disabled. For more information about SMB share-level permissions, see Share-Level ACLs. Possible values:
|
| If encryption is enabled on the cluster with external key management (EKM), enter a string identifier for the tenant's encryption group for encryption group management. You can optionally provide the same group for more than one tenant if you want to join multiple tenants to the same encryption group on the EKM. Tenants that belong to the same group will be managed by the same encryption key. Supply the group's Cloud Resource Name (CRN) identifier as Valid format: string, up to 128 characters An encryption group is required for tenant creation if EKM encryption is enabled. The encryption group cannot be changed after creating the tenant. For more information about EKM encryption, see Encryption of Data at Rest. |
| If you want to allow access to the trash folder for non-root NFSv3 users serviced by the tenant, specify this option and provide the GID of the user group that you want to use for this purpose as By default, the operation of moving files into the trash folder is supported for the root user only. |
| Specifies an array of ranges of client IPs to be served by the tenant. Specify For example: See Overview of Tenants for more information about dedicating virtual IP pools to tenants and associating client IPs to a tenant. |
| Specifies one provider to take precedence over other providers in case of any conflicts between attribute values when user information is retrieved from the providers. Applicable if more than one provider is enabled (see |
| Determines which authorization provider is the primary provider for the user’s login name. Applicable if more than one provider is enabled (see |
| Select which external authorization providers should be enabled for the tenant. Providers configured on the cluster are available for you to select up to one of each type (Active Directory, LDAP and NIS), subject to combination restrictions per tenant described in Authorization Providers in VAST Cluster. Providers configured on the cluster are available for you to select up to one of each type (Active Directory, LDAP and NIS), subject to combination restrictions per tenant described in |
| Specify up to one LDAP server configuration by its ID in order to enable it for the tenant. Providers configured on the cluster are available for you to select up to one of each type (Active Directory, LDAP and NIS), subject to combination restrictions per tenant described in Authorization Providers in VAST Cluster. |
| Specify up to one NIS configuration by its ID in order to enable it for the tenant. Providers configured on the cluster are available for you to select up to one of each type (Active Directory, LDAP and NIS), subject to combination restrictions per tenant described in Authorization Providers in VAST Cluster. |
| When this option is specified, VAST Cluster authorizes client access by using user and group information supplied via Kerberos or NTLM authentication, rather than by querying that user in Active Directory. For more information, see Authentication for SMB Access. |
| Disables use of Kerberos or NTLM authentication to authorize SMB client access. This is the default setting.
|
| When specified, SMB clients are required to sign SMB requests. SMB requests with missing or invalid signatures are not accepted. |
| When specified, SMB clients are not required to sign SMB requests. |
| Allows IO to be performed on the cluster by users whose accounts are disabled in Active Directory. By default, if the user's account is disabled in Active Directory by an administrator, the user is blocked from performing IO on the cluster. This setting overrides the default behavior. |
| Restores default behavior, where users whose accounts are disabled in Active Directory are blocked from performing IO on the cluster. |
| Allows IO to be performed on the cluster by users whose accounts are automatically locked out in Active Directory by account lockout policies. Active Directory account lockout policies determine when and for how long users are automatically locked out after invalid login attempts. By default, if the user's account is locked out by Active Directory lockout policies, the user is blocked from performing IO on the cluster. This setting overrides the default behavior. |
| Restores default behavior, where users whose accounts are locked out by Active Directory lockout policies are blocked from performing IO on the cluster. |
| Enables support of NFS version 4.2 for this tenant.
|
| Disables support of NFS version 4.2 for this tenant. |
| Specifies a local provider with which the tenant is associated. If not specified, the default tenant is used. |
| Controls the way VAST Cluster sets the owning group when creating files on a view controlled with the SMB and Mixed Last Wins security flavor:
|
| Enables/disables SMB encryption for the tenant, and also sets the encryption protection level:
|
| Set the maximum number of views the tenant can have to MAX. A value of 0 indicates unlimited views. Default: 0. |
NFSv4 File Delegation Options
| Enables NFSv4 file delegations for the tenant and specifies the type of NFSv4 file delegations that the cluster can grant to a client opening a file: read, write, or both. A value of Valid values: |
| If specified, the cluster grants the allowed delegations even when the client does not explicitly request a delegation. This is the default behavior. |
| If specified, the cluster does not grant the allowed delegations to clients that do not explicitly request a delegation. |
Capacity and Performance Limits (QoS)
Note
With VAST Cluster 5.4, block protocol operations are not subject to tenant's capacity and performance limitations.
| Enables and sets capacity limits for the tenant. Specify
For example:
|
| Enables and sets static performance limits for the tenant. Specify
For example:
|
Example
vcli: admin> tenant create --name Tenant1 --client-ip-ranges 10.10.10.2,10.10.10.4 11.11.11.2,11.11.11.4
--posix-primary-provider AD --ad-provider-id 1 --nis-provider-id 1 --localprovider 1