Help Center > > User Guide> Test Resource Management> Creating a CCE Resource Group

Creating a CCE Resource Group

Updated at: Sep 11, 2019 GMT+08:00

During or after a pressure test, you need to create a resource group and select a node (ECS) you created if you want to view the pressure test data. This resource group serves as both the management node and execution node for the pressure test.

The management nodes used in the Cloud Container Engine (CCE) resource group are the virtual machine (VM) nodes in CCE.

Usage Suggestions

  • Do not run any applications or perform other functions on nodes of resource groups for pressure tests. Otherwise, applications may run abnormally.
  • Create nodes with proper specifications based on the number of concurrent users for a pressure test. Nodes must be created on CCE.

    Create at least two nodes. One is the management node of a resource group for the pressure test (node of the management executor). The other is the execution node of a resource group for the pressure test. In other word, it is a pressure target machine that can provide performance data during a pressure test. If pressure tests are required for external services, bind an elastic IP address (EIP) to the execution node.

    Table 1 Recommended specifications

    Concurrent User

    Specifications

    Quantity

    0–5,000

    Management node: 2U4G

    1

    Execution node: 4U8G

    1

    5,001–10,000

    Management node: 2U4G

    1

    Execution node: 8U16G

    1

    10,001–20,000

    Management node: 2U4G

    1

    Execution node: 8U16G

    2

    20,001–30,000

    Management node: 2U4G

    1

    Execution node: 8U16G

    3

    30,001–40,000

    Management node: 2U4G

    1

    Execution node: 8U16G

    4

    40,001–50,000

    Management node: 2U4G

    1

    Execution node: 8U16G

    5

    More than 50,001

    Management node: 2U4G

    1

    Execution node: 8U16G

    n

    NOTE:

    Each execution node of 8U16G supports 10,000 concurrent users.

    NOTE:
    • Specifications of the preceding resource nodes are for reference only. During a pressure test, the required resource specifications are affected by factors such as think time, protocol type of the pressure test, number of requests and responses, response time, and result verification. You can adjust the requirements according to the actual situation.
    • If you bind an EIP to an execution node, the test bandwidth depends on the EIP bandwidth you purchased.
    • If an application is deployed on a node in a cluster, the node cannot be used to create a private resource group.
    • Specifications above does not apply to the JMeter engine.

Adding a Node

Pressure tests must run on nodes that you created. You need to add nodes first, which are used as the management node and execution node in the pressure test resource group.

  1. Log in to the cloud container engine (CCE) console.
  2. Create a cluster and add at least two nodes. The number and specifications of nodes are based on your requirements.

    NOTE:

    If pressure tests are for external applications deployed offline, on public cloud, or on other VPCs, you should ensure that the execution node in the resource group have been bound to an EIP address.

Creating a CCE Resource Group

  1. Log in to the CPTS console, choose Test Resources in the navigation pane, and click Prepare CCE Resource.
  2. Set the basic information by referring to Table 2.

    Table 2 Creating a resource group for the pressure test

    Parameter

    Description

    Resource Group Name

    Name of the CCE resource group you created.

    Hybrid Cloud Mode

    • Yes: Use a VM node of CCE as the management node, and use your own node as the execution node.
    • No: The management node and execution node must be VM nodes of CCE.

    Engine

    CPTS engine: default engine for pressure tests.

    JMeter engine: JMeter is a Java-based pressure test tool developed by Apache. It is used in pressure tests of software. It is originally designed for Web application testing but later extended to other testing areas. It can be used to test static and dynamic resources, such as static files, serverlets, CGI scripts, Java objects, databases, and FTP servers.

    Management Node

    Management node that performs a pressure test.

    It cannot be modified once created.

    Connection IP Address Selection

    This parameter is required only when the hybrid cloud is used. The purpose is to ensure the communication between the management node and the execution node.

    • External IP address: If the management node communicates with the execution node using the elastic IP address of the management node, set this parameter to External IP Address.
    • Internal IP address: If the management node communicates with the execution node using the private IP address of the management node, set this parameter to Internal IP Address.
    • Manual input: If the management node and execution node communicate with each other using neither the elastic IP address nor the private IP address of the management node, enter an IP address manually.

    Connection IP Address

    This parameter is mandatory only when you select the hybrid cloud mode and input the connection IP address manually.

    Execution Node

    Execution node that performs a pressure test, that is, a pressure target machine that can provide performance data during a pressure test.

    • In non-hybrid cloud mode, select a CCE VM node.
    • In hybrid cloud mode, select Automatic for execution node installation. The management node installs the execution package required for the pressure test on the execution node. Select Manual for execution node installation. You need to copy the installation command to your node and run it.

    Password

    Set this parameter only when the execution node is automatically installed.

    Password for logging in to the execution node as user root.

    Execution Node IP Address

    Set this parameter only when the execution node is automatically installed.

    Enter the IP address of the execution node. You can add IP addresses of multiple execution nodes. Ensure that the passwords of these execution nodes are the same.

  3. Click Create.

    After the two nodes are successfully created, their stacks are deployed in Application Orchestration Service (AOS) for pressure tests.

  4. (Optional) Modify, delete, and upgrade the resource group, as well as add or delete execution nodes in the resource group manually.

    • Modify the resource group. In the resource group list, click Edit next to the resource group to be modified. Only the Service Group Name and Executor Node can be modified. Then click OK.
      NOTE:

      You can modify it only when it is in the Running status. You cannot modify it when it is in the following statuses, such as Deploying, Upgradable and Abnormal.

      Resource groups cannot be modified in the hybrid cloud mode.

    • Delete the resource group. In the resource group list, click Delete next to the resource group to be deleted and delete it as prompted.
      NOTE:

      When the resource group is deleted, stacks deployed on AOS are also deleted instead of the node. The node will not be used in pressure tests. To delete a node, go to the corresponding service to perform the deletion.

    • Upgrade the resource group. In the resource group list, click Upgrade next to the resource group to be upgraded and upgrade it as prompted.
    • Manually add execution nodes to the resource group. In the resource group of the node to be added, click generate installation instructions to copy the installation command. Run the copied command on the node to install the execution node.
      Figure 1 Copying an installation command
    • Manually delete execution nodes in the resource group. In the resource group of the node to be deleted, click generate installation instructions to copy the uninstallation command. Run the copied command on the node to uninstall the execution node.
      Figure 2 Copying an uninstallation command

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel