Agent Management

Procedure

1. Click in the upper right corner of the page. Then choose General Settings > Agent Management. The agent management page is displayed.
2. Click Add Node.

   The root user is used as an example to log in, as shown in Figure 1. Table 1 describes the parameters.

   

   To add or delete a node as a common user, run the usermod -G wheel userName command to add the common user to the wheel group.

   Figure 1 Adding a node
   

   Table 1 Parameters for adding a node

   Parameter	Description
   (Optional) Node Name	Name of the node to be added. The value defaults to Node N, with N starting from 1 and increasing in ascending order. The name must meet the following requirements: Contain only letters, digits, and special characters (including @#$ %^&*()[]<>._-!-+ and spaces). Contain 1 to 32 characters.
   (Optional) Installation Path	Absolute path where the node is installed. The default value is /opt. NOTE: The path cannot be /home. If the entered path belongs to the root user group, common users must have the read (r) and execute (x) permissions on the paths of all levels. If the entered path belongs to the devkitwork1 user group, user devkitwork1 must have the read (r) and execute (x) permissions on the paths of all levels.
   SSH Transmission Note	Certificate management uses the default SSH transmission channel of the server. To ensure data security and integrity, you are advised to use a secure SSH service, such as a secure SSH version configured with a secure encryption algorithm.
   Select Server	Select Existing Server or New Server. NOTE: This parameter is available in the Kunpeng DevKit plugin.
   Node IP Address	IP address of the server where the node is to be installed.
   Port	SSH port of the server where the node is to be installed. The default value is 22. The value ranges from 1 to 65535.
   User Name	User name for logging in to the node server. The default value is root. NOTE: To ensure SSH channel security, it is recommended that you log in as a common user.
   Authentication Mode	Authentication mode. The options are: Password authentication Key authentication NOTE: If you select Key authentication, you need to set SSH authentication information on the server where the System Profiler is installed. For details, see Configuring SSH Authentication Information on a Node Server.
   Password	Password for logging in to the node server. It is required if you have selected Password authentication. NOTE: If the node is installed by the root user, you need to enter the password of the root user. If the node is installed by a common user, you need to enter the passwords of both the common user and root user. The Remember password option is available in the VS Code plugin.
   Private Key File	Absolute path of the SSH private key file, for example, /home/devkit/id_rsa, for logging in to the node server. This parameter is displayed when Authentication Mode is set to Key authentication.
   (Optional) Passphrase	Password of the SSH private key file for logging in to the node server. If the SSH private key password is not configured, you do not need to set this parameter. This parameter is displayed when Authentication Mode is set to Key authentication.

3. Set node parameters according to Table 1 and click OK.

   You can perform the following operations on a specified node:

   • Changing the node name
   • Viewing installation logs: You can view the components that are not installed in the system and the handling suggestions. The log content can be copied and downloaded.
     

     You can view installation logs only when multiple nodes are added.

   • Deleting the node
     

     • The default node installed on the web server cannot be deleted.
     • After a node is deleted, any new analysis task will not apply to this node. However, you can still view the historical analysis report of this node.
     • For a node installed by the root user, enter the password of the root user when deleting the node. For a node installed by a common user, enter the passwords of both the common user and root user when deleting the node.
   • Monitoring the capacity of the run directory and run log directory: You can view the alarm and recovery information about the drive space capacity of the node.
     

     • When the remaining drive space is less than 10% of the maximum drive space, the space used by the tool reaches 90%, or the remaining drive space of the server is less than 5 GB, the background stops the tasks running on the node. If a task does not contain the node, or a task contains the node but the task is being analyzed, the task is not stopped. If a new task contains the node, the task fails to be created.
     • When the remaining drive space is less than 20% of the maximum drive space or the space used by the tool reaches 80% of the maximum drive space, an alarm is generated.
     • When the remaining drive space is greater than 25% of the maximum drive space and the space used by the tool is less than 75% of the maximum drive space, you will be prompted that the alarm is cleared.
4. Import nodes in a batch.

   Click Batch Import, and then click the template table link to download the template.

   Figure 2 Importing nodes in a batch
   
   Figure 3 Template
   

   Fill in the information of the nodes to be imported, and upload the template table on the page as shown in Figure 2 to add the nodes.

   

   Fill in the table according to the template. Do not upload an empty, incorrect, or non-standard table.

5. Delete nodes in a batch.

   Click Batch Delete and then select the nodes to be deleted or click Delete Using Template File to download the template.

   Figure 4 Deleting nodes in a batch
   
   Figure 5 Template
   

   Fill in the information of nodes to be deleted following instructions on the template, and upload the template on the page as shown in Figure 4 to delete the nodes.