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 User Guide (Region Type II) 09

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).
Creating a VPC Peering Connection for Interworking Between VPCs in the Same Region

Creating a VPC Peering Connection for Interworking Between VPCs in the Same Region

Scenario

A user applies for multiple ECSs to provide applications to public networks. VPCs in different virtual data centers (VDCs) in the same region need to communicate with each other. Figure 13-88 shows VPC peering connection network.

  • Two VPCs are applied for creating ECSs. One VPC is for the production environment and the other one is for the pre-release environment.
  • Subnet applications in the pre-release environment need to communicate with those in the production environment.
    Figure 13-88 Service deployment

Requirement Analysis

Analyze user requirements as follows:

  • A VPC peering connection is a networking connection between two VPCs that enables ECSs in two VPCs in the same region can communicate with each other just as if they were in the same VPC.
  • To create a VPC peering connection, first create a request to peer with another VPC. You can request a VPC peering connection with another VPC of your own in the same region. The system automatically accepts the request.

Based on the preceding analysis, a peering connection can be set up between subnet applications in the production environment and those in the pre-release environment.

Configuration Plan

In the initial installation and deployment stage, an external network has been created and configured. The same user only needs to create VPCs in the production environment and pre-release environment, respectively, in the same region. The configuration plan is as follows:

  1. Apply for a VPC for the production environment and pre-release environment, respectively.
  2. Create security groups in the two VPCs and add security group rules.
  3. Create an ECS and select the created VPC in the production environment and pre-release environment, respectively.
  4. Apply for EIPs and bind them to the ECSs in the production environment and pre-release environment so that they can connect to the public network.
  5. Apply for a VPC peering connection to enable the subnet applications in the user production environment to communicate with those in the pre-release environment. If the VPC subnets are overlapped, the peering connection does not take effect. To create a VPC peering connection, ensure that the VPCs do not contain overlapped subnets.

Figure 13-89 shows the configuration flow based on the preceding analysis.

Figure 13-89 Creating a VPC peering connection

Procedure

Creating a VPC

  1. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

    Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

  2. Select a region and a project from the drop-down box in the upper left corner of the page.
  3. On the console homepage, choose Network > Virtual Private Cloud. On the VPC console, click Apply for VPC.
  4. Select a product, and click Apply Now. On the Apply for VPC page, set parameters as prompted. The configuration of the VPC that you are applying for is displayed in the Current Configuration area on the lower part of the page. Click Apply Now if the configuration is correct.

    Figure 13-90 Applying for a VPC

  5. On the Virtual Private Cloud page, locate the VPC for which a subnet is to be created and click the VPC name. Click the Subnet tab, and then click Create Subnet. On the Create Subnet page, set parameters as prompted.
  6. In the navigation pane on the left, choose Security Group. On the Security Group page, click Create Security Group. In the displayed dialog box, enter the security group name and description.

    Figure 13-91 Creating a security group

  7. Locate the row containing the newly created security group and click Add Rule. Add a security group rule as prompted.

    Figure 13-92 Adding a security group rule

Applying for ECSs

  1. On the home page. choose Computing > Elastic Cloud Server. On the ECS console, click Create ECS. On the Select Product page, select a product and click Apply Now.
  2. Enter the basic information about the ECS to be created.

    Figure 13-93 Basic Information

  3. Enter network information and select the VPC that has been applied for.
  4. Enter the login information and select the password login mode.

    Figure 13-94 Login information
    • Key Pair

      A key pair is used for authenticating the ECS. You can select an existing key pair, or click View Key Pair and create one.

    • Password

      The initial password of user root (for Linux) or user Administrator (for Windows) is used for authentication. You can log in to an ECS using the username and its initial password.

  5. Enable the high availability (HA) function.

    After HA is enabled, if the ECS or the host on which the ECS is running is faulty, the system automatically recreates an ECS on other hosts to ensure service continuity.

  6. Set the number of ECSs to 2 and click Assign Now. On the page for confirming specifications, confirm that the specifications are correct and click Submit to apply for two ECS for the application services.
  7. Repeat Step 8 to Step 13 to apply for an ECS for the database.

Applying for and binding an EIP

  1. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

    Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

  2. Select a region and a project from the drop-down box in the upper left corner of the page.
  1. On the home page, choose Network > Elastic IP Address > Apply for EIP. In the Select Product dialog box, select a product and click Apply Now.
  2. On the Apply for EIP page, configure the parameters of the basic information and bandwidth, and click Apply Now. Confirm the specifications and click Confirm Application.
  1. On the Elastic IP Address page, locate the row that contains the target EIP, and click Bind.
  2. On the page for binding an elastic IP address, select the APP ECS that has been applied for.
  3. Click OK.

Creating a VPC peering connection

  1. In the navigation pane on the left, choose VPC Peering.
  2. In the right pane displayed, click Create VPC Peering Connection.
  3. Set the parameters as prompted.

    Figure 13-95 Creating a VPC peering connection
    Table 13-55 Parameter description

    Parameter

    Description

    Example Value

    Name

    Specifies the name of the VPC peering connection.

    The name contains a maximum of 64 characters, which consist of letters, digits, hyphens (-), and underscores (_).

    peering-001

    Local VPC

    Specifies the local VPC. You can select one from the drop-down list.

    vpc_002(0a396cff-8bc1-4509-98b9-267cae5ac460)

    Project Name

    Specifies the project name. The project name of the current project is used by default.

    -

    Peer VPC

    Specifies the peer VPC. You can select one from the drop-down list if the VPC peering connection is created between two VPCs of your own.

    vpc_fab1(65d062b3-40fa-4204-8181-3538f527d2ab)

  4. Click OK.

Adding routes for a VPC peering connection

If you request a VPC peering connection with a VPC of your own, the system automatically accepts the request. To enable communication between the two VPCs, you need to add routes for the VPC peering connection.

  1. On the console homepage, under Network, click Virtual Private Cloud.
  2. In the navigation pane on the left, choose VPC Peering.
  3. Locate the target VPC peering connection in the connection list.
  4. Click the name of the VPC peering connection to switch to the page showing details about the connection.
  5. On the displayed page, click the Local Route tab.
  6. In the displayed Local Route area, click Add Local Route. In the displayed dialog box, add a local route.
  7. Click OK to switch to the page showing the VPC peering connection details.
  8. On the displayed page, click the Peer Route tab.
  9. In the displayed Peer Route area, click Add Peer Route and add a route.
  10. Click OK in the displayed dialog box.

    After a VPC peering connection is created, the two VPCs can communicate with each other through private IP addresses.

Remotely logging in to the ECSs to deploy services

  1. After applying for the APP ECSs and DB ECS, you can remotely log in to the ECSs and deploy applications and DB software. After the deployment is complete, you need to save the database configuration information in the template of the database ECS to the APP ECSs.
Translation
Download
Updated: 2019-04-23

Document ID: EDOC1100026810

Views: 176222

Downloads: 49

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