Overview

Tenants are used in resource control and service isolation scenarios. Administrators need to confirm the service scenarios of cluster resources, and then plan tenants.

By default, the Yarn component of the newly installed cluster uses the Superior scheduler. For details, see Using the Superior Scheduler in Multi-Tenant Scenarios.

Multi-tenant involves three types of operations: creating a tenant, managing tenants, and managing resources. Table 1 describes the operations.

**Table 1** Operations involved in multi-tenant
Operation	Action	Description
Creating a tenant	Adding a tenant Adding a sub-tenant Creating a user and binding the user to the role of a tenant	During the creation of a tenant, you can configure its computing resources, storage resources, and associated services based on service requirements. In addition, you can add users to the tenant and bind necessary roles to these users. A user who creates level-1 tenants must be bound to the Manager_administrator or System_administrator role. A user who creates sub-tenants must be bound to the role of the parent tenant at least.
Managing tenants	Managing tenant directories Restoring tenant data Clearing unassociated queues of a tenant Deleting a tenant	Modifies tenants as the services change. A user who manages or deletes level-1 tenants and restores tenants' data must be bound to the Manager_administrator or System_administrator role. A user who manages or deletes sub-tenants must be bound to the role of the parent tenant at least.
Managing resources	Adding a resource pool Modifying a resource pool Deleting a resource pool Configuring a queue Configuring the queue capacity policy of a resource pool Clearing queue configurations	Reconfigure resources for tenants as the services change. A user who manages resources must be bound to the Manager_administrator or System_administrator role.