Managing Agent

Prerequisites

• You have installed and deployed the Kunpeng DevKit.
• Before adding a local node, check that the sshd service is enabled. Otherwise, the agent node will fail to be added.

Procedure

• A maximum of 101 nodes can be added, including the root node on which the Kunpeng DevKit is installed. After the root node is added, it can only be modified or deleted.

• A Docker container created in port mapping mode cannot be added as an agent, while a Docker container created in host mode can be added as an agent.
• The network between the node where the Kunpeng DevKit is installed and the agent node must be connected. Otherwise, the agent node will fail to be added.

1. Click in the upper right corner of the page. Then choose General Settings > Agent Management. The agent node management page is displayed.
2. You can add an Agent node in either of the following methods:
   • Batch import information about multiple nodes using a template.
     1. On the Batch Import page, click the template table link to download the template.

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

        Figure 1 Batch import
        
        Figure 2 Template table
        
        

        • Fill in the table according to the template. Do not upload an empty, incorrect, or non-standard table.
        • If a batch import includes incorrect node information, an error message is displayed and the batch import fails.
     2. After entering the node information, click Select File and confirm the Notes for Adding Nodes. Use the selected file to batch import nodes.
        Figure 3 Notes for Adding Nodes
        
   • Add information about a single node.

     On the add node page, set parameters based on Table 1 and click OK.

     Figure 4 Add Node
     
     

     If you failed to add a node as a common user, run the usermod -aG wheel userName command to add the common user to the wheel group.

     Table 1 Parameters for adding a node

     Parameter	Description
     (Optional) Node Name	Name of the node to be added. It is Node plus the node ID by default. The name must meet the following requirements: Contain only letters, digits, and special characters (including @#$ %^&*()[]<>._-!-+ and spaces). A string of 1 to 32 characters.
     (Optional) Installation Path	Absolute path to the node to be added, which contains 1 to 4096 characters and defaults to /opt. NOTE: The entered 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 devkit user group, user devkit 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.
     Node Authorization	To ensure that the DevKit runs properly on the remote node and prevent task interruption or failure due to an insufficient permission, grant the root permission for the node (so as to compress and decompress the uploaded packages on the agent, and scan and replace the file content). Please be aware of security risks and authorize this operation.
     Select Server	Select Existing Server or New Server. NOTE: You can select a node included in Target Server Management for Existing Server. 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	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 Kunpeng DevKit is installed. For details, see Configuring SSH Authentication Information on a Node Server.
     Password	Password for logging in to the node server, which contains a maximum of 64 characters. NOTE: This parameter is displayed when Authentication Mode is set to Password authentication. 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. However, to ensure your account security, do not select Remember password when logging in using a public network or public computer.
     Private Key File	Absolute path of the SSH private key file, for example, /home/devkit/id_rsa, for logging in to the node server. NOTE: 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. NOTE: This parameter is displayed when Authentication Mode is set to Key authentication.

3. The following uses adding a single node for fingerprint verification as an example. After the tool verifies the imported node information, the node fingerprint verification page is displayed. Check that the node fingerprint is correct, and click Add.
   Figure 5 Fingerprint verification
   
   

   • If the fingerprint fails to be obtained, the node fails to be added. In this case, install the ssh-keyscan tool on the web server.
   • If a node fails to be added, view the log file named after the IP address in the /opt/DevKit/logs/agent_logs/ directory on the web server. If the following information is displayed, manually disable SELinux on the node:

     1	"The SELinux enforcing mode is enabled on the server, which will cause a tool installation failure".

   • If a node fails to be added and an error message similar to "yum install -y xxx failed" is displayed, rectify the fault by following instructions in Configuring the OS Yum, APT, or Zypper Source.
4. After a node is added, you can modify or delete the node or view installation logs in the Operation column. You can also click Batch Delete to delete multiple nodes at a time.
   • Modify: Change the node name.
   • View installation logs: You can view the missing components and provided handling suggestions. Log files can be copied and downloaded. You can view installation logs only when multiple nodes are added.
   • Delete: You are required to enter the password of the DevKit installation user. 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.
   • Batch Delete: If a batch deletion includes incorrect node information, an error message is displayed and the batch deletion fails.