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.0 Solution Description 05

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 provincial companies or subsidiaries (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.

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 6-12 shows the VDC tenant model.

Figure 6-12 VDC tenant model

The VDC tenant model is described as follows:

  • An operation administrator can create multiple VDCs. Each VDC can include multiple lower-level VDCs, projects, VDC administrators, and VDC operators.
  • 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 in the previous figure can be a VDC administrator, a VDC operator, or a user with a customized role.
  • A VDC can contain a maximum of five levels of VDCs. Each level of second- and lower-level VDCs can contain multiple VDCs.
  • 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 first-level VDC is managed by operation administrators, and the second- and lower-level VDCs are managed by VDC administrators at an upper level.
  • User roles in VDCs at each level include VDC administrators, VDC operators, and multiple user-defined roles.
  • 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.
Table 6-2 Roles and their responsibilities in the VDC tenant model

Enterprise Organization

VDC Level

Quota

Role

Responsibility

Enterprises

N/A

N/A

Operation administrator

  • An operation administrator has the highest permissions, including:
    • Creating other operation administrators
    • Creating multiple first-level VDCs and setting their quotas
    • Creating first-level VDC administrators
    • Managing VDC tenants
    • Managing cloud resource pools
  • An operation administrator is also a system administrator of Service OM and has highest permissions for Service OM.

Subsidiary/Provincial company

First-level VDC

An operation administrator sets the quotas for first-level VDCs during VDC creation.

First-level VDC administrator

  • Creates users and projects in the first-level VDC.
  • Creates lower-level VDCs as well as users and projects in lower-level VDCs.
  • Associates VDC administrators or VDC operators with projects.
  • Applies for and manages cloud services.

VDC operator in a first-level VDC

Applies for and manages cloud services.

Level-1 department

(Optional) Second-level VDC

A VDC administrator sets the quotas for lower-level VDCs during VDC creation.

Second-level or lower-level VDC administrator

  • Manages second-level and lower-level VDCs.
  • Associates VDC administrators or VDC operators in second-level and lower-level VDCs with projects.
  • Applies for and manages cloud services.
  • Views and exports information of the current-level VDC and lower-level VDCs.

Level-2 department

(Optional) Third-level VDC

Level-3 department

(Optional) Fourth-level VDC

Level-4 department

(Optional) Fifth-level VDC

Level-2 or lower-level department

Second-level or lower-level VDC

N/A

Second-level or lower-level VDC operator

Applies for and manages cloud services.

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 6-13.

Figure 6-13 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, and maintenance project 2 to the service department and allocates 100 CPUs, memory size of 50 GB, employee 4, employee 5, employee 6, innovation project 1, and innovation project 2 to the marketing department.
  • 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 6-3 Organization and roles of the tenant model instance

Enterprise Organization

VDC Level

Sub-Organization (Example)

Quota (Example)

Role (Example)

Description of VDC Administrators/VDC Operators and Projects in a 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 administrators/VDC operators:

  • Employee 1
  • Employee 2
  • Employee 3

Projects:

  • Maintenance project 1
  • Maintenance project 2

Shenzhen Corporation-the marketing department

Quota 2.2:

  • CPU: 100
  • Memory: 50 GB

First-level VDC administrator (VDC_admin_Shenzhen)

VDC administrators/VDC operators:

  • Employee 4
  • Employee 5
  • Employee 6

Projects:

  • Innovation project 1
  • Innovation project 2
Translation
Download
Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 161953

Downloads: 263

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