Creating a test agent
Preparing an infrastructure
-
Create a service account for test agent:
- Create a service account named
sa-loadtest
in the folder to host the agent that will generate the load. - Assign the following roles to the service account:
loadtesting.generatorClient
: Allows running the agent, performing tests on the agent, and uploading the results to storage.compute.admin
: Allows managing VMs in Compute Cloud.vpc.user
: Allows connecting to Virtual Private Cloud network resources and using them.
- Create a service account named
-
Set up the test agent's security group.
Creating a test agent
-
If you do not have an SSH key pair yet, create one.
-
Create an agent.
Management consoleCLI-
In the management console
, select the folder where you want to create the agent. -
From the list of services, select Load Testing.
-
In the Agents tab, click Create agent.
-
Enter a name for the agent, e.g.,
agent-008
. -
Specify the same availability zone where the test target is located.
-
Under Agent:
- Select the appropriate agent type. For more information, see Agent performance.
- Specify the subnet where the test target is located. Make sure you created and set up a NAT gateway in the subnet.
- If security groups are available to you, select a security group preset for the agent.
-
Under Access, specify the information required to access the agent:
-
Select the
sa-loadtest
service account. -
Under Login, enter a username.
Alert
Do not use
root
or other reserved usernames. To perform operations requiring root privileges, use thesudo
command. -
In the SSH key field, paste the contents of the public key file.
-
-
Click Create.
-
Wait for the VM instance to create. Make sure the agent status has changed to
Ready for test
.Note
If the agent creation process has stopped at
Initializing connection
, make sure the following conditions are met:- The agent has a public IP address and access to
loadtesting.api.cloud.yandex.net:443
. - A NAT gateway is set up in the target subnet.
- The service account assigned to the agent has the required roles.
- The agent has a public IP address and access to
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the
--folder-name
or--folder-id
parameters.-
See the description of the CLI command for creating an agent:
yc loadtesting agent create --help
-
Select the same availability zone where the test target is located.
-
Select the subnet where the test target is located. Make sure you created and set up a NAT gateway in the subnet.
To get a list of available subnets using the CLI, run this command:
yc vpc subnet list
Result:
+----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+ | ID | NAME | NETWORK ID | ROUTE TABLE ID | ZONE | RANGE | +----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+ | e2lfkhps7bol******** | default-ru-central1-b | enpnf7hajqmd******** | | ru-central1-b | [10.129.0.0/24] | | e9bgnq1bggfa******** | default-ru-central1-a | enpnf7hajqmd******** | | ru-central1-a | [10.128.0.0/24] | | fl841n5ilklr******** | default-ru-central1-d | enpnf7hajqmd******** | | ru-central1-d | [10.130.0.0/24] | +----------------------+---------------------------+----------------------+----------------+-------------------+-----------------+
-
Select the security group. Make sure to configure the security group in advance.
To get a list of available security groups using the CLI, run this command:
yc vpc security-group list
Result:
+----------------------+---------------------------------+--------------------------------+----------------------+ | ID | NAME | DESCRIPTION | NETWORK-ID | +----------------------+---------------------------------+--------------------------------+----------------------+ | enp414a2tnnp******** | default-sg-enpnf7hajqmd******** | Default security group for | enpnf7hajqmd******** | | | | network | | | enpctpve7951******** | sg-load-testing-agents | | enpnf7hajqmd******** | | enpufo9ms0gi******** | sg-load-testing-targets | | enpnf7hajqmd******** | +----------------------+---------------------------------+--------------------------------+----------------------+
-
Find out the
sa-loadtest
service account ID using its name:yc iam service-account get sa-loadtest
Result:
id: ajespasg04oc******** folder_id: b1g85uk96h3f******** created_at: "2024-12-04T17:38:57Z" name: sa-loadtest last_authenticated_at: "2024-12-12T19:10:00Z"
-
Create an agent in the default folder:
yc loadtesting agent create \ --name agent-008 \ --labels origin=default,label-key=label-value \ --zone default-ru-central1-a \ --network-interface subnet-id=e9bgnq1bggfa********,security-group-ids=enpctpve7951******** \ --cores 2 \ --memory 2G \ --service-account-id ajespasg04oc******** --metadata-from-file user-data=metadata.yaml
Where:
--name
: Agent name.--labels
: Agent labels.--zone
: Availability zone to host the agent.--network-interface
: Agent network interface settings:subnet-name
: ID of the selected subnet.security-group-ids
: Security group IDs.
--cores
: Number of CPU cores the agent can use.--memory
: Amount of RAM allocated to the agent.--service-account-id
: Service account ID.--metadata-from-file
:<key>=<value>
pair with the name of the file containing the public SSH key path. For an example of themetadata.yaml
configuration file, see VM metadata.
For more information on how to create an agent with CLI, see the Yandex Cloud Examples repository
.
-
-
Assign a public IP to the agent to enable access over SSH:
Management consoleCLI- In the management console
, select the folder where the agent is located. - Select Compute Cloud.
- Select the VM named
agent-008
. - Under Network interface, in the top-right corner, click
and select Add public IP address. - In the window that opens:
- In the Public address field, select obtaining a Auto address.
- Click Add.
To assign a public IP address to an agent, run the following CLI command:
yc compute instance add-one-to-one-nat \ --id=<VM_ID> \ --network-interface-index=<VM_network_interface_number> \ --nat-address=<IP_address>
Where:
-
--id
: VM ID. You can get a list of available VM IDs in a folder using theyc compute instance list
CLI command. -
--network-interface-index
: VM network interface number. The default value is0
. To get a list of VM network interfaces and their numbers, run the following command:yc compute instance get <VM_ID>
. -
--nat-address
: Public IP address to assign to the VM. This is an optional parameter. If you omit it, a public IP address will be assigned to the VM automatically.You can get a list of reserved public IP addresses available in a folder using the
yc vpc address list
CLI command. The IP address and the VM must be in the same availability zone.
Usage example:
yc compute instance add-one-to-one-nat \ --id=fhmsbag62taf******** \ --network-interface-index=0 \ --nat-address=51.250.*.***
Result:
id: fhmsbag62taf******** folder_id: b1gv87ssvu49******** created_at: "2022-05-06T10:41:56Z" ... network_settings: type: STANDARD placement_policy: {}
For more information about the
yc compute instance add-one-to-one-nat
command, see the CLI reference. - In the management console