No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionInsight HD 6.5.0 Administrator Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Creating Tenants

Creating Tenants

Adding a Tenant

Scenario

Based on the resource consumption and isolation plan and requirements of services, administrators can create tenants on FusionInsight Manager to meet actual application scenarios.

Prerequisites
  • A tenant name has been planned based on service requirements. The name cannot be the same as that of a role, HDFS directory, or Yarn queue that exists in the current cluster.
  • Resources to be allocated to the current tenant have been planned to ensure that the sum of capacities of direct sub-tenants at every level cannot exceed the current tenant.
Procedure
  1. On FusionInsight Manager, click Tenant Resources.
  2. Click . On the displayed page, configure tenant properties based on Table 9-11.

    Table 9-11 Tenant parameters

    Parameter

    Description

    Name

    • Specifies the name of the current tenant. The value consists of 3 to 50 characters, which can be letters, digits, or underscores (_).
    • Plan a tenant name based on service requirements. The name cannot be the same as that of a role, HDFS directory, or Yarn queue that exists in the current cluster.

    Type

    Specifies whether the specified tenant is a leaf tenant.

    • When Leaf is selected, the current tenant is a leaf tenant and no sub-tenant can be added.
    • When Non-leaf is selected, the current tenant is not a leaf tenant and sub-tenants can be added to the current tenant.

    Computing Resource

    Specifies the dynamic computing resources for the current tenant.

    • When Yarn is selected, the system automatically creates a task queue in Yarn and the queue is named the same as the name of the tenant.
      • A leaf tenant can directly submit tasks to the task queue.
      • A non-leaf tenant cannot directly submit tasks to the task queue. However, Yarn adds an extra task queue (hidden) named Default for the non-leaf tenant to record the remaining resource capacity of the tenant. Actual tasks do not run in this queue.
    • When dynamic resources are not Yarn resources, the system does not automatically create a task queue.

    Default Resource Pool Capacity (%)

    Specifies the computing resource usage in the Default resource pool of the current tenant. The value ranges from 0 to 100%.

    Default Resource Pool Max Capacity (%)

    Specifies the maximum computing resource usage in the Default resource pool of the current tenant. The value ranges from 0 to 100%.

    Storage Resource

    Specifies storage resources of the current tenant.

    • When HDFS is selected, the system automatically allocates storage resources.
    • When HDFS is not selected, the system does not automatically allocate storage resources.

    Quota

    Specifies the file and directory quantity quota.

    Space Quota Unit

    Specifies the storage unit of Space Quota, which can be MB or GB.

    Space Quota

    Specifies the used HDFS storage space quota of the current tenant.

    • Value range: When Space Quota Unit is set to MB, this parameter ranges from 1 to 8796093022208. When Space Quota Unit is set to GB, this parameter ranges from 1 to 8589934592. The maximum value of this parameter does not exceed the total storage quota of the parent tenant.
    • This parameter indicates the maximum HDFS storage space that can be used by the tenant, but does not indicate the actual space used.
    • If the value is greater than the size of the HDFS physical disk space, the maximum space that can be used is all the HDFS physical disk space.

    Storage Path

    Specifies the HDFS storage directory for a tenant.

    • The system creates a file folder named after the tenant name in the /tenant directory by default. For example, the default HDFS storage directory for ta1 is /tenant/ta1.
    • When a tenant is created for the first time, the system creates the /tenant directory in the HDFS root directory. The storage path is customizable.

    Description

    Configure the description of the current tenant.

    NOTE:

    During the creation of a tenant, the system automatically creates a corresponding role, the computing resources, and the storage resources.

    • The new role has the rights on the computing resources and storage resources. The role and its rights are controlled by the system automatically and cannot be controlled manually under System > Permission > Role.
    • When using this tenant, create a system user and bind the user to the role of the tenant. For details, see Adding a User and Binding the User to a Tenant Role.
    • During the creation of a tenant, the system automatically creates a Yarn task queue named after the tenant. If the queue name exists, the new queue is named Tenant name-N. N indicates a natural number starting from 1. When a same name exists, the value N increases automatically to differentiate the queue from others. For example, saletenant, saletenant-1, and saletenant-2.

  3. Whether the current tenant need to associate resources of other services.

    • If yes, go to 4.
    • If no, go to Step 5.

  4. Click Associated Service to configure other service resources used by the current tenant.

    1. Select HBase in Service.
    2. Make a selection in Association Type:

      Exclusive indicates service resources used by the tenant exclusively. Other tenants cannot associate with this service.

      Share indicates shared service resources, which can be used by other tenants.

    NOTE:
    • When creating a tenant, you can only associate HBase with the tenant. For existing tenants, you can associate the following services: HDFS, HBase, and Yarn.
    • Associating existing tenants with HBase resources: In the tenant list on the left of the Tenant Management page, click the target tenant. Then, switch to the Service Association tab page and click Associated Service to associate the current tenant with HBase services.
    • Canceling the association between existing tenants and HBase resources: In the tenant list on the left of the Tenant Management page, click the target tenant. Then, switch to the Service Association tab page, click Delete, select I have read the information and understand the impact., and click OK to cancel the association with HBase.
    1. Click OK.

  5. Click OK. When Tenant created successfully. is displayed on the page, the tenant is added successfully.

Adding a Sub-Tenant

Scenario

Based on the resource consumption and isolation plan and requirements of services, administrators can create Sub-Tenants on FusionInsight Manager, and allocate resources of the current tenant to meet the actual application scenario.

Prerequisites
  • A parent tenant has been added, and belongs to a non-leaf tenant.
  • A tenant name has been planned based on service requirements. The name cannot be the same as that of a role, HDFS directory, or Yarn queue that exists in the current cluster.
  • Resources to be allocated to the current tenant have been planned to ensure that the sum of capacities of direct sub-tenants at every level cannot exceed the current tenant.
Procedure
  1. On FusionInsight Manager, click Tenant Resources.
  2. In the tenant list on the left, move the cursor to the tenant node to which the sub-tenant is added. Click . In the displayed window, configure the sub-tenant properties based on Table 9-12.

    Table 9-12 Sub-tenant parameters

    Parameter

    Description

    Parent Tenant Resource

    Specifies the name of the parent tenant.

    Name

    • Specifies the name of the current tenant. The value consists of 3 to 50 characters, which can be letters, digits, or underscores (_).
    • Plan a sub-tenant name based on service requirements. The name cannot be the same as that of a role, HDFS directory, or Yarn queue that exists in the current cluster.

    Type

    Specifies whether the specified tenant is a leaf tenant.

    • When Leaf is selected, the current tenant is a leaf tenant and no sub-tenant can be added.
    • When Non-leaf is selected, the current tenant is not a leaf tenant and sub-tenants can be added to the current tenant. However, the tenant depth cannot exceed 5 levels.

    Computing Resource

    Specifies the dynamic computing resources for the current tenant.

    • When Yarn is selected, the system automatically creates a task queue in Yarn and the queue is named the same as the name of the tenant.
      • A leaf tenant can directly submit tasks to the task queue.
      • A non-leaf tenant cannot directly submit tasks to the task queue. However, Yarn adds an extra task queue (hidden) named Default for the non-leaf tenant to record the remaining resource capacity of the tenant. Actual tasks do not run in this queue.
    • When dynamic resources are not Yarn resources, the system does not automatically create a task queue.

    Default Resource Pool Capacity (%)

    Specifies the computing resource usage of the current tenant. The base value is the total resources of the parent tenant.

    Default Resource Pool Max Capacity (%)

    Specifies the maximum computing resource usage of the current tenant. The base value is the total resources of the parent tenant.

    Storage Resource

    Specifies storage resources of the current tenant.

    • When HDFS is selected, the system automatically creates a file in the HDFS parent tenant directory. The file is named the same as the name of the sub-tenant.
    • When HDFS is not selected, the system does not automatically allocate storage resources.

    Quota

    Specifies the file and directory quantity quota.

    Space Quota Unit

    Specifies the storage unit of Space Quota, which can be MB or GB.

    Space Quota

    Specifies the used HDFS storage space quota of the current tenant.

    • When Space Quota Unit is set to MB, this parameter ranges from 1 to 8796093022208. When Space Quota Unit is set to GB, this parameter ranges from 1 to 8589934592. The maximum value of this parameter does not exceed the total storage quota of the parent tenant.
    • This parameter indicates the maximum HDFS storage space that can be used by the tenant, but does not indicate the actual space used.
    • If the value is greater than the size of the HDFS physical disk space, the maximum space that can be used is all the HDFS physical disk space.
    • If this quota is greater than the quota of the parent tenant, the actual storage space will be affected by the quota of the parent tenant.

    Storage Path

    Specifies the HDFS storage directory for a tenant.

    • The system creates a file folder named after the sub-tenant name in the directory of the parent tenant by default. For example, if the sub-tenant is ta1s and the parent directory is /tenant/ta1, the system sets the Storage Path for the sub-tenant to /tenant/ta1/ta1s.
    • The storage path is customizable in the parent directory.

    Description

    Configure the description of the current tenant.

    NOTE:

    During the creation of a tenant, the system automatically creates a corresponding role, the computing resources, and the storage resources.

    • The new role has the rights on the computing resources and storage resources. The role and its rights are controlled by the system automatically and cannot be controlled manually under System > Permission > Role.
    • When using this tenant, create a system user and bind the user to the role of the tenant. For details, see Adding a User and Binding the User to a Tenant Role.
    • The sub-tenant can further allocate the resources of the current tenant. The sum of the resource percentage of direct sub-tenants of a parent tenant cannot exceed 100%. The sum of the computing resource percentage of all level-1 tenants cannot exceed 100%.

  3. Whether the current tenant need to associate resources of other services.

  4. Click Associated Service to configure other service resources used by the current tenant.

    1. Select HBase in Service.
    2. Make a selection in Association Type:

      Exclusive indicates service resources used by the tenant exclusively. Other tenants cannot associate with this service.

      Share indicates shared service resources, which can be used by other tenants.

    NOTE:
    • When creating a tenant, you can only associate HBase with the tenant. For existing tenants, you can associate the following services: HDFS, HBase, and Yarn.
    • Associating existing tenants with HBase resources: In the tenant list on the left of the Tenant Management page, click the target tenant. Then, switch to the Service Association tab page and click Associated Service to associate the current tenant with HBase services.
    • Canceling the association between existing tenants and HBase resources: In the tenant list on the left of the Tenant Management page, click the target tenant. Then, switch to the Service Association tab page, click Delete, select I have read the information and understand the impact., and click OK to cancel the association with HBase.
    1. Click OK.

  5. Click OK. When Tenant created successfully. is displayed on the page, the tenant is added successfully.

Adding a User and Binding the User to a Tenant Role

Scenario

The created tenant cannot directly log in to the FusionInsight cluster to access resources. Administrators need to create a user for a tenant on FusionInsight Manager and bind the user to a tenant role to assign operation rights to the user.

Prerequisites

The system administrator has understood service requirements and created a tenant.

Procedure
  1. On FusionInsight Manager, click System > Permission > User.
  2. To add a user to the system, click Create User.

    To bind tenant rights to an existing user in the system, click Modify in the column where the user locates. The configuration page is displayed.

    For details about configuring parameters of a user, see Table 9-13.
    Table 9-13 User parameters

    Parameter

    Description

    Username

    Specifies the name of the current tenant. The value consists of 3 to 20 characters, which can be letters, digits, underscores (_), or hyphen (-).

    • Username cannot be the same as any username of the OS on each node in the cluster. Otherwise, the user account cannot be used properly.
    • Usernames of the same letters but different cases are not supported. For example, if User1 already exists, user user1 cannot be created. When using user User1, enter the correct username.

    Usertype

    Options include Human-Machine and Machine-Machine.

    • Human-Machine user: Used in FusionInsight Manager O&M scenarios and component client operation scenarios. If you select Human-Machine, you need to set Password and Confirm password.
    • Machine-Machine user: Used in FusionInsight HD application development scenarios. If you select Machine-Machine, the user password is generated randomly.

    Password

    If you select Human-Machine, set Password.

    The password must contain 8 to 64 characters, consisting at least 4 of uppercase letters, lowercase letters, digits, and special characters.

    Confirm Password

    Enter the password again.

    User Group

    In User Group, click Add to add the user to a user group.

    • If a role is added to a user group, users in the user group can obtain the rights of the role.
    • For example, assign Hive rights to the new user and add the user to the Hive group.

    Primary Group

    Select a group as the primary group of directories and files of the user. The drop-down list contains groups that are selected in User Group.

    Role

    Click And to add a role to the user as required.
    NOTE:
    • If a user wants to use resources allocated to tenant1 add sub-tenants to or delete sub-tenants from tenant1, bind the Manager_tenant and tenant1 roles to the user.

    Description

    Configure the description of the current user.

  3. Click OK.
Download
Updated: 2019-05-17

Document ID: EDOC1100074522

Views: 7356

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next