Dataphin:Tenant settings

Permissions

Only super administrators and system administrators in a Yuancang tenant can create and manage other tenants.

Engine feature support

Resource usage

Your purchased data processing units and rule quotas determine the maximum processing units and quality rules available. For details, see View resource usage or .

Create a tenant

1. Log on to the Yuancang tenant as a super administrator or system administrator.

2. In the top navigation bar of Dataphin, choose Management Center > System Settings.

3. In the left-side navigation pane, choose System Settings > Tenant Settings.

4. On the Tenant Settings page, click Add Tenant. The Create Tenant dialog box appears.

5. In the Create Tenant dialog box, configure the following parameters.

   Parameter		Description
   Basic information	Tenant Name	Enter a name for the tenant. The name can be up to 128 characters long.
   	Super Administrator	Select a super administrator for the tenant. Note The super administrator cannot be changed after the tenant is created. If you select Hide Super Administrator and System Administrator, members with these roles are displayed as 'Administrator'. This setting does not affect their permissions.
   Feature settings	Engine Type	Select the required offline computing engine for the tenant. For more information, see Features supported by different engines. After you select an engine type, select the features to enable for the tenant. Data processing unit: Enter the number of data processing units. This value must be greater than 0 and cannot exceed the remaining available units. Rule quota: This quota is shared by domain-level quality rules and global quality rules. Only enabled rules count against this quota. The total number of purchased and allocated data processing units and quality rules is displayed in the upper-left corner of the tenant list. Note The engine type selected here does not affect which engine types users can choose within this tenant. You cannot configure the engine type for multi-engine tenants. By default, all features supported by this tenant type are included. By default, each tenant can create one consumption channel. You can purchase additional channels. You can create data source monitoring rules if you enable either domain-level quality rules or global quality rules. If you enable both, data source monitoring rules count against your domain-level rule quota. If you enable only global quality rules, they count against your global rule quota. To use X-DataEngineering, you must enable the Intelligent R&D Edition. To use X-Analytics, X-AssetQA, or X-CatalogManagement, you must enable Asset Operation. You can select the Data Operation Enhancement feature only if you have selected Data Service Standard Edition.
   Scheduling resource settings	CPU/Memory allocatable resources	Note This section allocates scheduling resources for the default Dataphin cluster only. If resource contention occurs, tenants are first allocated their minimum guaranteed resource. Other tenants can borrow unused resources from a tenant's minimum guarantee. A tenant can also borrow unused resources from other tenants. The total resources used by the tenant cannot exceed its configured maximum resource limit. Enter the minimum guaranteed resource and maximum resource limit for CPU and memory. minimum guaranteed resource: Enter a value that is >=0. The value can have up to one decimal place and cannot exceed the remaining allocatable resources. The sum of the minimum guaranteed resources for all tenants cannot exceed 100%. maximum resource limit: Enter a value that is >=0. The value can have up to one decimal place, must be greater than or equal to the minimum guaranteed resource, and must be less than 100%.
   	Metadata processing resource group	When a metadata collection task runs, it is split into the following subtasks: The initial metadata collection and project initialization use the scheduling resource group specified for the collection task. This is necessary to ensure network connectivity. Subsequent processing tasks use the scheduling resource group configured here to minimize the impact on other tasks. We recommend using a resource group from the Dataphin cluster. Note If the CPU or memory configuration for scheduling resources is not 0, you can select the tenant default resource group for the current tenant. After you modify the resource group configuration, the changes take effect in about 10 minutes. These changes do not apply to collection instances created before the modification.
   Cross-tenant settings	Cross-tenant dependency	If you enable this feature, tasks in this tenant can depend on tasks in other tenants, and vice versa.

6. Click OK to create the tenant.

Manage tenants

After you add a tenant, you can edit, delete, or restore it on the Tenant Settings page.

Single-tenant multi-engine

Create a tenant

When you create a tenant, the following features are unavailable if the metadata warehouse has not been initialized with an offline computing engine.

• The entry points and pages for instance statistics and exception statistics in the Operations Center are hidden.

• You cannot view information in Asset Inventory, such as project storage, table storage, table access counts, and popularity.

• You cannot share models from the metadata warehouse.

When you create a tenant, you cannot select an engine type. Other parameters and descriptions are the same as for single-engine mode.

Manage tenants

When editing a tenant, you can upgrade it from single-engine mode to multi-engine mode, but you cannot revert it to single-engine mode. In multi-engine mode, compute sources can only be created based on a cluster, and they cannot access compute sources from other clusters.

Other management operations are the same as for single-engine mode. For details, see Manage tenants.