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

FusionAccess V100R006C20 on FusionCloud V100R006C10 Software Installation Guide 11 (Microsoft AD)

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).
Defining Computing Instance Flavors (KVM)

Defining Computing Instance Flavors (KVM)

Scenarios

This section describes how to create computing instance flavors required by cloud desktop services on the cascading FusionSphere OpenStack management console (Region Type I scenario) or FusionSphere OpenStack management console (Region Type II scenario).

Prerequisites

  • Region Type I scenario
    • You have obtained the address, username, and password for logging in to the cascading FusionSphere OpenStack management console.

      Login address: https://Cascading-OM-externalAPI-Float-IP

      Default username: cloud_admin; default password: FusionSphere123

    • You have obtained the address, username, and password for logging in to cascading Service OM.

      Login address: https://Cascading-OM-externalAPI-Float-IP:553

      Default username: admin; default password: IaaS@PORTAL-CLOUD8!

  • Region Type II scenario
    • You have obtained the address, username, and password for logging in to the FusionSphere OpenStack management console.

      Login address: https://OM-externalAPI-Float-IP

      Default username: cloud_admin; default password: FusionSphere123

    • You have obtained the address, username, and password for logging in to Service OM.

      Login address: https://OM-externalAPI-Float-IP:553

      Default username: admin; default password: IaaS@PORTAL-CLOUD8!

Procedure

Creating a flavor

  1. Select an operating platform based on the region type scenario.

    • In the Region Type I scenario, log in to the cascading FusionSphere OpenStack management console.
    • In the Region Type II scenario, log in to the FusionSphere OpenStack management console.

  2. Choose Resources > Computing > Flavors, as shown in Figure 4-1.

    Figure 4-1 Flavors

  3. Click Create Flavor to create the flavors listed in Table 4-1. Retain the default values for the parameters that are not involved. These flavors are used to make infrastructure VM images and user desktop images.

    Table 4-1 Parameter configuration

    Flavor

    Parameter

    Description

    vdi-linux-image

    Type

    VM

    Boot Device

    Local Disk

    Name

    vdi-linux-image

    vCPUs

    4

    Memory (MB)

    8192

    Root Disk (GB)

    60

    Temporary Disk (GB)

    Leave it blank.

    Tag

    Tag name: Customize a tag. For example, ims:blankVolume; tag value: true

    NOTE:

    If this tag is not set, the image creation function on FusionSphere OpenStack Management Console cannot be used.

    vdi-windows-image

    Type

    VM

    Boot Device

    Local Disk

    Name

    vdi-windows-image

    vCPUs

    4

    Memory (MB)

    8192

    Root Disk (GB)

    You are advised to set this parameter to 60 or any other value based on site requirements.

    Temporary Disk (GB)

    Leave it blank.

    Tag

    Tag name: Customize a tag. For example, ims:blankVolume; tag value: true

  4. Repeat Step 3 to create flavors whose boot device is the cloud disk. The flavors are used to create a public license and pubic backup server on the Service OM. Create the flavors listed in Table 4-2.

    Table 4-2 Parameter configuration

    Flavor

    Parameter

    Description

    vdi-license

    Type

    VM

    Boot Device

    Local Disk

    Name

    vdi-license

    vCPUs

    4

    Memory (MB)

    8192

    Root Disk (GB)

    60

    display_name

    vdi-license

    availability_zone

    manage-az

    vdi-backupserver

    Type

    VM

    Boot Device

    Local Disk

    Name

    vdi-backupserver

    vCPUs

    4

    Memory (MB)

    4096

    Root Disk (GB)

    60

    display_name

    vdi-backupserver

    availability_zone

    manage-az

  5. Repeat Step 3 to create compute instance flavors whose boot device is the cloud disk.

    Create the flavors listed in Table 4-3 according to the actual situation. Retain the default values for the parameters that are not involved.

    If you need other desktop flavors, see vdi-desktop-2u4g in the following table for creation.

    Table 4-3 Parameter configuration

    Flavor

    Parameter

    Description

    vdi-mgr

    Type

    VM

    Boot Device

    Cloud Disk

    Name

    vdi-mgr

    vCPUs

    4

    Memory (MB)

    16,384

    System Volume (GB)

    60

    Tag

    Add the following two tags:

    Customize a tag. For example,

    Tag name: resource_type; tag value: You are advised to set the value to IOoptimized. You can also set this parameter based on the site requirements.

    Tag name: ecs:performancetype; tag value: normal

    vdi-ad-dns

    Type

    VM

    Boot Device

    Cloud Disk

    Name

    vdi-ad-dns

    vCPUs

    4

    Memory (MB)

    8192

    System Volume (GB)

    60

    Tag

    Add the following two tags:

    Customize a tag. For example,

    Tag name: resource_type; tag value: You are advised to set the value to IOoptimized. You can also set this parameter based on the site requirements.

    Tag name: ecs:performancetype; tag value: normal

    vdi-desktop-2u4g

    Type

    VM

    Boot Device

    Cloud Disk

    Name

    vdi-desktop-2u4g

    vCPUs

    2

    Memory (MB)

    4096

    System Volume (GB)

    60

    Tag

    Add the following two tags:

    Customize a tag. For example,

    Tag name: resource_type; tag value: You are advised to set the value to IOoptimized. You can also set this parameter based on the site requirements.

    Tag name: ecs:performancetype; tag value: normal

Synchronizing flavor information

  1. Select an operating platform based on the Region Type scenario.

    • In the Region Type I scenario, log in to cascading Service OM.
    • In the Region Type II scenario, log in to Service OM.

  2. Under Management and Deployment, click CCS.
  3. On the Cloud System Parameter page, click ECS Flavor. Click Add in the upper right corner.
  4. Set related information and click OK.

    • Default name: Select the flavor created in Step 5 from the drop-down list.
    • display_name: flavor name displayed on the ServiceCenter tenant portal. The value is user-defined and is recommended to be the same as the default name.
    • availability_zone: Select AZs based on site requirements.

  5. Repeat Step 8 to Step 9 to add all flavor information.
Translation
Download
Updated: 2019-07-01

Document ID: EDOC1100021785

Views: 46344

Downloads: 100

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