Using MRS Multi-Tenancy
Scenarios
Tenants are used in resource control and service isolation scenarios. You need to determine the service scenarios of cluster resources and then plan tenants.
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 assigned the Manager_administrator or System_administrator role. A user to manage or delete a sub-tenant needs to be assigned 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 assigned the Manager_administrator or System_administrator role. |
Creating Tenants and Sub-Tenants
Administrators need to determine the service scenarios of cluster resources and then plan tenants. After that, administrators add tenants and configure dynamic resources, storage resources, and associated services for the tenants on MRS.
Table 2 shows the process for creating a tenant.
Operation |
Description |
---|---|
Creating a tenant |
You can configure the compute resources, storage resources, and associated services of the tenant. |
Creating a sub-tenant |
You can configure the compute resources, storage resources, and associated services of the sub-tenant. |
Adding a user and assigning the tenant role to the user |
If a user wants to use the resources of tenant tenant1 or add or delete sub-tenants for tenant1, the user must be bound to both the Manager_tenant and tenant1_Cluster ID roles. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot