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

FusionCloud 6.3.1.1 Solution Description 04

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).
VDC Tenant Model

VDC Tenant Model

A VDC is a unit used by the ManageOne operation plane to allocate resources in the multi-level operation scenario. For example, a multinational carrier or trans-provincial company has multiple subsidiaries or provincial companies (first-level VDCs), and a provincial company or subsidiary includes multiple departments (lower-level VDCs). When a multinational carrier or trans-provincial company allocates resources, all the virtual resources used by a provincial company or subsidiary can be grouped into a first-level VDC and all the resources used by each department can be grouped into a lower-level VDC. A VDC can include multiple lower-level VDCs. Currently, a maximum of five levels of VDCs can be created. If multi-level operation does not apply, only one first-level VDC is needed. The VDC administrator of the first-level VDC can manage all resources.

VDC Tenant Model

Figure 7-13 shows the VDC tenant model.

Figure 7-13 VDC tenant model

The VDC tenant model is described as follows:

  • A VDC tree consists of multi-level VDCs. The VDC tree is a group which has hierarchical relationship with the first-level VDC (root node) and multiple lower-level VDCs.
  • A VDC can contain a maximum of five levels of VDCs. Each level of second- and lower-level VDCs can contain multiple VDCs. A first-level VDC is managed by operation administrators, and the second- and lower-level VDCs are managed by VDC administrators at an upper level.
  • An agent administrator can manage multiple first-level VDCs, which is convenient for delegating third-party users to manage operation. A third-party user can use an agent administrator account to manage one or more first-level VDCs. You can create, delete and modify agent administrators. Agent administrators, in place of VDC administrators, can manage multiple first-level VDCs on which they have agent maintenance permissions and users and resources in the VDCs. Agent maintenance management is described as follows:
    • An agent administrator sets departments based on the enterprise organization structure and sets resource quotas for each department.
    • An agent administrator switches to different department, applies for resources for each department, and notifies end users of the resource information offline.
    • End users of resources do not log in to ManageOne.
    • Resources applied for by agent administrators during agent maintenance in a department occupy the quotas of the department.
  • Projects are used to group resources so that resources in different projects are isolated. Projects correspond to project teams in actual application scenarios. Resources in the same project can be shared. A VDC can include multiple projects, but a project can belong to only one VDC. When a user applies for a resource and switches to an associated project in the upper left corner of the page, the resource applied for belongs to the project. In this way, resources can be grouped.

    For example, if the VDCuser1 user switches to the associated project Project 1 in the upper left corner of the page and applies for ECS 1, and the VDCuser2 user switches to the associated project Project 2 in the upper left corner of the page and applies for ECS 2, ECS 1 and ECS 2 belong to different projects.

  • A user group is a group of users with the same customized role permissions. You can add users to a user group in batches. If you select projects to which users belong for the users, the users have permissions of their own roles. If you select projects of user groups to which users belong for the users, the users have permissions of the user group roles.
    To use a user group, perform the following steps:
    1. Creates a role and a project.
    2. Associate the role with a user group to be created.
    3. Add the project to the user group.
    4. Add users to the user group in batches so that the users have the operation rights on resources in the project associated with the user group.
  • A user in the previous figure can be a VDC administrator, a VDC operator, a VDC read-only administrator, or a user with a customized role. An operation administrator can create multiple VDCs. Each VDC can include multiple lower-level VDCs, projects, VDC administrators, VDC operators, VDC read-only administrators.

Model Instance

This section describes the organization structure, quotas, roles, and projects of the XX company based on the VDC tenant model, as shown in Figure 7-14.

Figure 7-14 VDC tenant model instance

The instance is described as follows:

  • An operation administrator creates two first-level VDCs (VDC_Chengdu and VDC_Shenzhen) for two enterprises (Chengdu Corporation and Shenzhen Corporation) and two first-level VDC administrators (VDC_admin_Chengdu and VDC_admin_Shenzhen).
  • An operation administrator allocates 100 CPUs and 50 GB memory to Chengdu Corporation and 200 CPUs and 100 GB memory to Shenzhen Corporation.
  • The Shenzhen Corporation has two departments: service department (second-level VDC) and marketing department (second-level VDC). VDC_admin_Shenzhen allocates 100 CPUs, memory size of 50 GB, employee 1, employee 2, employee 3, maintenance project 1, maintenance project 2, and operator group 1 to the service department and allocates 100 CPUs, memory size of 50 GB, employee 4, employee 5, employee 6, innovation project 1, innovation project 2, and operator group 2 to the marketing department. The employees can be VDC administrators, VDC operators, VDC read-only administrators, and users with customized roles.
  • The first-level VDC administrator (VDC_admin_Shenzhen) can associate projects with employees. One employee can manage or use multiple projects. One project can be managed or used by multiple employees. However, a user cannot manage or use a project that belongs to a different department.
Table 7-2 Organization and roles of the tenant model instance

Enterprise Organization

VDC Level

Sub-Organization (Example)

Quota (Example)

Role (Example)

Description of User and Project in VDC (Example)

Enterprises

N/A

N/A

N/A

Operation administrator

N/A

Subsidiary

First-level VDC

Chengdu Corporation

Quota 1:

  • CPU: 100
  • Memory: 50 GB

First-level VDC administrator (VDC_admin_Chengdu)

N/A

Shenzhen Corporation

Quota 2:

  • CPU: 200
  • Memory: 100 GB

First-level VDC administrator (VDC_admin_Shenzhen)

N/A

Level-1 department

Second-level VDC

Shenzhen Corporation-the marketing department

Quota 2.1:

  • CPU: 100
  • Memory: 50 GB

First-level VDC administrator (VDC_admin_Shenzhen)

VDC administrator/VDC operator/VDC read-only administrator/User with customized role:

  • Employee 1
  • Employee 2
  • Employee 3

Projects:

  • Maintenance project 1
  • Maintenance project 2

User group:

Operator group 1

Shenzhen Corporation-the marketing department

Quota 2.2:

  • CPU: 100
  • Memory: 50 GB

First-level VDC administrator (VDC_admin_Shenzhen)

VDC administrator/VDC operator/VDC read-only administrator/User with customized role:

  • Employee 4
  • Employee 5
  • Employee 6

Projects:

  • Innovation project 1
  • Innovation project 2

User group:

Operator group 2

Translation
Download
Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 73430

Downloads: 192

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