Overview
Tenants are used in resource control and service isolation scenarios. Administrators need to determine the service scenarios of cluster resources and then plan tenants.
- Yarn in a new cluster uses the Superior scheduler by default. For details, see Using the Superior Scheduler.
Multi-tenancy involves three types of operations: creating a tenant, managing tenants, and managing resources. Table 1 describes these operations.
Operation |
Action |
Description |
---|---|---|
Creating 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 to create a level-1 tenant needs to be bound to the Manager_administrator or System_administrator role. A user to create a sub-tenant needs to be bound to the role of the parent tenant at least. |
Managing tenants |
|
You can edit tenants as services change. A user to manage or delete a level-1 tenant or restore tenant data needs to be bound to the Manager_administrator or System_administrator role. A user to manage or delete a sub-tenant needs to be bound to the role of the parent tenant at least. |
Managing resources |
|
You can reconfigure resources for tenants as the services change. A user to manage resources needs to be bound to the Manager_administrator or System_administrator role. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.