Tenant settings - Dataphin - Alibaba Cloud Documentation Center

Creating multiple tenants allows for the assignment of distinct data units and functional modules to each, ensuring data isolation and catering to the diverse needs of various tenants. This topic explains how to create, edit, delete, and restore tenants.

Permission description

Only super administrators and system administrators of the metadata warehouse tenant can create and manage tenants.

Resource usage description

The total number of processing unit specifications and the total number of quality rules depend on the data processing unit and rule quota purchased by the customer. For more information, see view resource usage.

Create a tenant

Log on to the metadata warehouse tenant using a super administrator or system administrator account.
On the Dataphin home page, select Management Center > System Settings from the top menu bar.
In the left-side navigation pane, select System Settings > Tenant Settings .
On the Tenant Settings page, click Add Tenant to open the Create Tenant dialog box.

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

Parameter		Description
Basic Information	Tenant Name	Custom tenant name. No more than 128 characters.
Basic Information	Super Administrator	You can select the super administrator to which the target tenant belongs. Note After the tenant is created, the super administrator cannot be changed. If you select Hide Super Administrator And System Administrator, the member information will be displayed as administrator, but the operations that the member corresponding to the role can perform will not be affected.
Schedule Resource Settings		Note Only the schedule resources of the default Dataphin cluster are allocated here. The available lower limit represents the guaranteed resources of the current tenant. When each tenant needs resources exceeding the lower limit to run tasks, all tenants will be given priority to obtain the set lower limit. The unused resource lower limit of this tenant can be borrowed by other tenants. However, when this tenant needs to use it, the borrowed resources can be reclaimed through queuing. This tenant can also borrow unused resource quotas from other tenants. However, the total amount of resources available after borrowing cannot exceed the set available upper limit. Enter the CPU and Memory Available Lower Limit and Available Upper Limit respectively. Available lower limit: Only values >=0 are supported, with one decimal place retained. The entered value cannot exceed the remaining allocable resources. The sum of the available resource lower limits for all tenants cannot exceed 100%. Available upper limit: Only values >=0 are supported, with one decimal place retained. The entered value must be greater than or equal to the available lower limit and less than 100%.
Function Settings	Metadata Processing Resource Group	When executing metadata acquisition tasks, they will be split into multiple subtasks: The process of obtaining initial metadata from the data source and storing it in the Metadata Center to initialize the specified project will use the schedule resource group specified by the acquisition task to ensure network connectivity. Subsequent processing tasks and data backflow tasks will uniformly use the schedule resource group configured here to reduce the impact on other task resources. It is recommended to use the Dataphin cluster resource group. Note When the CPU or memory configuration in the schedule resource is not 0, you can select the tenant default resource group of the current tenant. After modifying the resource group configuration, it takes about 10 minutes to take effect. The resource group of the acquisition instance generated before the modification will not be modified accordingly.
Function Settings	Development, Administration, Asset, Application, Platform	Select the functional modules available to the current tenant. Data Processing Unit: Set the number of data processing unit configurations. The data processing unit quota must be greater than 0 but cannot exceed the remaining processing units. Rule Quota: The domain quality rules and global quality rules share this quota, and only the number of quality rules in the active status is counted. The upper left corner of the tenant list shows the total amount of data processing units, quality rules purchased, and allocated. Note The ArgoDB compute engine does not support real-time development, real-time integration, resource administration, and data service functions. If the tenant uses ArgoDB as the compute engine, do not select the intelligent development function template. The AnalyticDB for PostgreSQL compute engine does not support resource administration functions. The Lindorm (compute engine) does not support real-time development, real-time integration, resource administration, data service, and tag-related functions. The GaussDB (DWS) compute engine does not support resource administration, offline version of the tag platform, real-time version of the tag platform, and audience group selection functions. The Databricks compute engine does not support resource administration, offline version of the tag platform, real-time version of the tag platform, and audience group selection functions. Metadata acquisition and management are supported only after the Metadata Center initialization configuration is completed in the metadata warehouse tenant. Each tenant can create one consumption channel by default, and additional channels can be purchased. Enabling domain quality or global quality allows you to create data source monitoring rules. If both global quality rules and domain quality rules are purchased, the number of data source quality rules is counted as domain rules. If only global quality rules are enabled, they are counted as global rules.

Click OK to complete the addition of the tenant.

Manage tenants

You can edit, delete, and restore tenants on the Tenant Settings page after adding them.

Block

Description

①Tenant List

Displays Tenant Name/id, Super Administrator, the Used Quota of data processing units/quality rules, Total Quota, Resource Scope Settings, Current Resource Usage, and Functional Modules information.

Resource scope settings: The lower and upper limits set in the schedule resource settings, not the actual usage value.
Current resource usage: The amount of resources allocated to the tenant up to the time of refreshing the interface, which is the actual resource usage of the current tenant.

②Operation area

You can perform Edit, Delete, and Restore operations on the tenant.

When the tenant status is Creating, no operations are supported. When the tenant status is Updating, edit and delete operations are not supported. When the tenant status is Creation failed or Update failed, you can re-edit the tenant. After re-editing the failed tenant, it will be reinitialized.

Note

The data processing units, schedule resources, and quality rule resources allocated to the tenant being created will be deducted in advance. If the creation fails, the deducted resources will be returned.

Edit: You can edit the tenant's name, data processing unit quota, and functional modules. You can set the available lower limit and available upper limit of CPU and memory for the metadata warehouse tenant.
Function downgrade has the following limitations:
- If intelligent development-related objects (business segments, business objects, data domains, business activities, logical tables, business filters, atomic metrics, derived metrics, etc.) already exist, intelligent development cannot be canceled. You need to delete the target objects before canceling.
- If real-time development tasks, quality rules, data detection rules, or data masking rules, data service APIs, etc., are already configured, the corresponding functional modules cannot be canceled. You need to delete the corresponding configurations before canceling.
  If real-time integration tasks (including draft, development, and production states) already exist, real-time integration cannot be disabled. You need to delete the corresponding tasks before canceling.
  If baseline and rate limiting rules already exist, artificial intelligence for IT operations cannot be disabled. You need to delete the corresponding baseline and rate limiting rules before canceling.
- The basic development version cannot be canceled.
Note
If you have enabled the custom resource group function, you can modify the schedule resource amount allocated to the metadata warehouse tenant. Please note that if the resources of the metadata warehouse tenant are allocated too little, it may cause system task output delays, thereby affecting the display of some page functions (such as field heat information on the directory page) and the data update of the metadata sharing model.
Delete: Select the tenant to be deleted, and click the Delete icon in the Actions column of the target tenant. In the Delete Tenant dialog box, enter the 6-digit verification code and click OK.
Note
- The metadata warehouse tenant cannot be deleted.
- After a tenant is deleted, the deleted tenant will remain in the tenant list for 30 days. During this period, the tenant can be restored. After 30 days, the deleted tenant will be removed from the tenant list, and the tenant data will not be deleted. If you need to delete it, please contact technical support.
- If a custom resource group has been configured under the current tenant, please delete the custom resource group before deleting the tenant.
Restore: Select the tenant to be restored, and in the Restore Tenant dialog box, click OK.
If your tenant does not support restoration, the possible reasons are as follows:
- The number of data processing units used is greater than the remaining allocable data processing units.
- The number of quality rules used is greater than the remaining allocable quality rules.
- There is a downgrade situation in the tenant function.
- The schedule resources (CPU or memory) configured for the tenant exceed the maximum remaining allocable amount in the system.