Creating a CCE Resource Group

Use 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 specifications based on the number of concurrent users for pressure tests. The nodes must be created in CCE. CCE clusters of v1.19 and earlier versions are supported. You are advised to select Tunnel network as the cluster network model. When you create nodes, select EulerOS as the OS.

  Create at least two nodes. One is the management node (the node used to manage an execution node). The other is the execution node, that is, a pressure target machine that can provide performance data during a pressure test. If you want to perform pressure tests on external services, bind an elastic IP address (EIP) to the execution node. If you want to debug external services, bind EIPs to both the management node and execution node.

  Table 1 Recommended specifications

  Number of Concurrent Users	Specifications	Quantity
  0–5000	Management node: 4 vCPUs | 8 GB	1
  	Execution node: 4 vCPUs | 8 GB	1
  5001–10,000	Management node: 4 vCPUs | 8 GB	1
  	Execution node: 8 vCPUs | 16 GB	1
  10,001–20,000	Management node: 4 vCPUs | 8 GB	1
  	Execution node: 8 vCPUs | 16 GB	2
  20,001–30,000	Management node: 4 vCPUs | 8 GB	1
  	Execution node: 8 vCPUs | 16 GB	3
  30,001–40,000	Management node: 4 vCPUs | 8 GB	1
  	Execution node: 8 vCPUs | 16 GB	4
  40,001–50,000	Management node: 4 vCPUs | 8 GB	1
  	Execution node: 8 vCPUs | 16 GB	5
  50,001 and above	Management node: 4 vCPUs | 8 GB	1
  	Execution node: 8 vCPUs | 16 GB	n NOTE: Each execution node (8 vCPUs | 16 GB) 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 a pressure test, number of requests and responses, response time, and result verification. Adjust the specifications according to the actual situation.
  • You need to bind an EIP to an execution node to perform a pressure test on an external service. The test bandwidth depends on the EIP bandwidth you created.
  • If an application is deployed on a node in a cluster, the node cannot be used to create a private resource group.
  • The preceding specifications do not apply to the JMeter engine.

Adding a Node

1. Log in to the CCE console.
2. Create a cluster and add at least two nodes that run the EulerOS. Clusters of v1.19 and earlier versions are supported. You are advised to select Tunnel network as the cluster network model. The number and specifications of nodes are based on your requirements.
   • If there is an available cluster in CCE, add a management node and an execution node. For details about how to add a node, see Help Center > Cloud Container Engine > Cloud Container Engine User Guide > Node Management > Creating a Node .
   • If no cluster is available in CCE, create a cluster first. For details about how to create a cluster, see Help Center > Cloud Container Engine > Cloud Container Engine User Guide > Cluster Management > Creating a Hybrid Cluster. After creating a cluster, add a management node and an execution node for the pressure test.
   Note

   If the pressure test will be performed on external applications deployed offline, on other public clouds, or on other Virtual Private Clouds (VPCs), ensure that the execution node has been bound to an EIP.

Creating a Private CCE Resource Group

1. Log in to the CPTS console, choose Resource Groups in the navigation pane, and click Create Resource Group.
2. (Optional) If this is the first time you create a private resource group, grant CPTS permissions necessary for creating private CCE resource groups.
3. Set the basic information by referring to Table 2.

   Table 2 Creating a resource group

   Parameter	Description
   Resource Group Name	Name of the private CCE resource group to be created.
   Debugging Cluster	Select a CCE cluster from the drop-down list box.
   Debugging Node	Node used for debugging. The debugging node cannot be changed after the resource group is created.
   Execution Node	Target machine that a pressure test will be performed on and can provide performance data during testing.

4. Click Create.

   When the resource group is created, stacks for pressure tests will be deployed for the debugging and execution nodes in AOS.

5. (Optional) Scale in or out, delete, or upgrade the resource group.
   • Scale out the resource group: Click Scale under the resource group, select the original execution nodes and execution nodes to be added, and click OK.
   • Scale in the resource group: Click Scale under the resource group, select the execution nodes you want to keep, and click OK.
   • Delete the resource group: Click Delete under the resource group and delete it as prompted.
     Note

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

   • Upgrade the resource group: Click Upgrade under the resource group and upgrade it as prompted.