Method for expanding edge nodes based on container arrangement system

Abstract

The invention discloses a method for expanding edge nodes based on a container arrangement system. The method comprises the following steps: S1, deploying the container arrangement system; s2, edge nodes are selected, and related information of the edge nodes needing to be expanded is filled in; s3, detecting the connectivity between the edge node to be expanded and the current cluster; and S4, finishing installation and addition of the edge nodes. According to the method, the rapid and automatic deployment and management of the edge nodes are realized in a mode of combining the KubeEdge and the container arrangement system, so that the edge computing resources can be efficiently utilized, and the stability and reliability of the system are ensured at the same time.

Description

Technical Field

[0001] The present invention relates to the technical field of software operation and maintenance, and specifically provides a method for expanding edge nodes based on a container orchestration system. Background Art

[0002] An edge node refers to a computing device or node distributed at the edge of a network, usually located near the user side or data source, and is used to process data, execute computing tasks, and provide services. An edge node can be a physical device, a virtual machine, a containerized application, or other forms of computing units. The deployment of edge nodes can help reduce the transmission delay of data in the network, improve data processing efficiency, and support computing and services closer to the user or data source.

[0003] In the process of expanding edge nodes based on a container orchestration system, the current edge computing technology still faces many challenges: 1. The management complexity of edge nodes is relatively high. Traditional methods usually rely on manual configuration and lack a unified management and scheduling mechanism, resulting in high operation and maintenance difficulty and low expansion efficiency. 2. Since edge nodes are usually located in scenarios with complex network environments and limited bandwidth (such as 5G base stations or industrial Internet of Things), existing container orchestration systems have deficiencies in adapting to heterogeneous networks, which may lead to node access failures or unstable management. 3. Most solutions lack the ability of automatic detection and adaptation. The software and hardware environments of edge nodes often need to be manually checked, and the deployment process is cumbersome and error-prone. At the same time, due to relatively limited edge computing resources, traditional data center-level scheduling strategies are difficult to be efficiently applied in the edge environment, which may lead to resource waste or unreasonable task allocation. In terms of security, since edge nodes are widely distributed, they face challenges such as data transmission security, remote access control, and malicious attack prevention, and existing security mechanisms are often not perfect enough to ensure the credibility and stable operation of edge nodes. Summary of the Invention

[0004] To solve the above problems, the present invention provides a method for expanding edge nodes based on a container orchestration system, including the following steps: S1. Deploy a container orchestration system; S2. After selecting an edge node and filling in the relevant information of the edge node to be expanded, detect the relevant information of the edge node; S3. Detect the connectivity between the edge node to be expanded and the current cluster; S4. Complete the installation and addition of the edge node.

[0005] Further, the relevant information of the edge node in step S2 specifically includes: node name, node IP, SSH port, username, password, and selection of the edge node container runtime.

[0006] Further, the detection of the information related to the edge node in step S2 specifically includes the following sub-steps: S21. Detect whether the edgecore service has been running and determine whether the name of the node to be added already exists; S22. Detect whether the directory ' / etc / kubeedge / ' exists in the node IP.

[0007] Further, step S4 specifically includes the following sub-steps: S41. Check the installation progress of the edge node through the log; S42. Determine whether the edge node has been successfully added.

[0008] Further, step S42 is specifically as follows: Check whether 'KubeEdge edgecore is running' appears in the log. If it appears, it is regarded that the edge node has been successfully added and installed.

[0009] Further, it also includes the edge node replication and export step: Copy the existing edge node configuration command, and after executing the copied edge node configuration command on the corresponding terminal device, execute step S3.

[0010] The present invention provides a method for expanding edge nodes based on a container orchestration system, which has the following beneficial effects: The present invention combines KubeEdge with a container orchestration system to achieve fast and automated deployment and management of edge nodes, enabling efficient utilization of edge computing resources while ensuring the stability and reliability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on the structures shown in these drawings without creative efforts.

[0012] Figure 1 It is the flowchart of the method provided by the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0013] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0014] The following will detail the implementation method of the present invention with reference to the drawings. The described are only some embodiments, not all embodiments. For the purpose of clarity, the representations and descriptions unrelated to the present invention are omitted in the drawings and the description.

[0015] For a clearer understanding of the technical features, objectives, and beneficial effects of the present invention, the following provides a detailed description of the technical solution of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all embodiments, and should not be construed as a limitation on the scope of implementation of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work belong to the protection scope of the present invention.

[0016] By integrating edge nodes with the container orchestration system, the present invention enables the system to better adapt to various complex application scenarios, reduces the dependence on the central cloud, and provides strong support for application programs distributed at the network edge.

[0017] As Figure 1 shown, the present invention provides a method for expanding edge nodes based on a container orchestration system, including the following steps: S1. Deploy a container orchestration system; S2. After selecting an edge node and filling in the relevant information of the edge node to be expanded, detect the relevant information of the edge node; S3. Detect the connectivity between the edge node to be expanded and the current cluster; S4. Complete the installation and addition of the edge node.

[0018] The relevant information of the edge node in step S2 specifically includes: node name, node IP, SSH port, username, password, and select the edge node container runtime. Among them, detecting the relevant information of the edge node specifically includes the following sub-steps: S21. Detect whether the edgecore service is already running and determine whether the name of the node to be added already exists; S22. Detect whether the directory ' / etc / kubeedge / ' is contained in the node IP.

[0019] Step S4 specifically includes the following sub-steps: S41. View the installation progress of the edge node through the log; S42. Determine whether the edge node is successfully added: Check whether 'KubeEdge edgecore is running' appears in the log. If it appears, it is considered that the edge node is successfully added and installed.

[0020] It also includes an edge node replication and export step: Copy the existing edge node configuration commands, and after executing the copied edge node configuration commands on the corresponding terminal device, execute step S3.

[0021] Embodiment: A method for expanding edge nodes based on a container orchestration system, including the following steps: ① Deploy a container orchestration system.

[0022] ② On the container orchestration system console, click on the node.

[0023] ③ Under the node navigation bar, select the edge node.

[0024] ④ After entering the Edge Node Overview page, click Add.

[0025] Obtain the command to add an edge node joinCode, joinCommand := e.EdgeNodeJoin(node.NodeName, node.NodeIP,node.RunTimeType) if joinCode != status_code.SUCCESS { msg := joinCommand.(string) results.Items[index].Status = "Failure" results.Items[index].Detail = msg errMsg := "Failed to generate the command to add an edge node. Failure message: " + msg installLogger += fmt.Sprintf(time.Now().Format(time.RFC3339) + " " +errMsg + "\n") middleware.Logger.Error(installLogger) config.InMemoryCache.SetDefault(cacheKey, installLogger) return } Msg = ">>>>>>" + "Successfully generated the command to add an edge node. Add command: " + joinCommand.(string) + "<<<<<<" installLogger += fmt.Sprintf(time.Now().Format(time.RFC3339) + " " +Msg + "\n") config.InMemoryCache.SetDefault(cacheKey, installLogger).

[0026] ⑤ On the page for adding edge nodes, relevant information about the edge node needs to be filled in [including: node name, node IP, SSH port, username, password, and selection of the edge node container runtime]; (Note: The node name cannot be the name of a node already in use in the current cluster, and the same applies to the IP, and the IP address must comply with the standard regulations).

[0027] Verify the node information: if valid, d := e.EdgeNodeValid(nodeName, nodeIP); valid != status_code.SUCCESS { return valid, d }。

[0028] ⑥ Detection function: It can detect the connectivity between the node to be added and the current cluster.

[0029] Judge the node architecture: outArch, err := cli.Command("arch") if err != nil { results.Items[index].Status = "Failure" results.Items[index].Detail = err.Error() errMsg := "step2: Detection of the current node architecture failed, failure information: " + err.Error() installLogger += fmt.Sprintf(time.Now().Format(time.RFC3339) + " " +errMsg + "\n") middleware.Logger.Error(installLogger) config.InMemoryCache.SetDefault(cacheKey, installLogger) return } var arch string switch outArch { case "x86_64": arch = "amd64" case "aarch64": arch = "arm64" default: msg := "The current host architecture does not match: " + outArch results.Items[index].Status = "Failure" results.Items[index].Detail = msg errMsg := "step2: Failed to detect the architecture of the current node. Failure message: " + msg installLogger += fmt.Sprintf(time.Now().Format(time.RFC3339) + " " + errMsg + "\n") middleware.Logger.Error(installLogger) config.InMemoryCache.SetDefault(cacheKey, installLogger) return } Msg = ">>>>>>step2: The architecture detection of the current node is completed! Host architecture: " + arch + "<<<<<<" installLogger += fmt.Sprintf(time.Now().Format(time.RFC3339) + " " + Msg + "\n") config.InMemoryCache.SetDefault(cacheKey, installLogger).

[0030] Verify the SSH connection connectivity of multiple hosts: func (s *sshClient) VerifyConnection(hosts *config.RequestBodyItems)(int, interface{}) { if len(hosts.Items) == 0 { middleware.Logger.Error("The annotation list information for SSH verification of host connectivity is empty!") return status_code.SshConnectionVerifyHostIsNull, nil } var ( / / Response return structure hostVerifyResult config.ResponseBodyItems / / Response return items structure hostVerifyResultItems = make([]config.NodeResult, len(hosts.Items)) ) for idx, host := range hosts.Items { hostVerifyResultItems[idx] = s.verifySingleHost(&host) } hostVerifyResult.Items = hostVerifyResultItems return status_code.SUCCESS,&hostVerifyResult }。

[0031] Verify the SSH connection connectivity of a single host: func (s *sshClient) verifySingleHost(host *config.Node)config.NodeResult { hostVerifyResult := config.NodeResult{ NodeIP: host.NodeIP, NodeName: host.NodeName, Port: host.Port, Status: "Success", Detail: "SSH Connection Succeeded!", }。

[0032] ⑦ Export command: You can view the configuration of the copied edge nodes. Add command: You can log in to the terminal through tools such as JumpServer and execute the exported configuration command.

[0033] ⑧ Create: One-click installation of edge nodes.

[0034] Execute the installation command: command, err := cli.Command(joinCommand.(string)) if err != nil { results.Items[index].Status = "Failure" results.Items[index].Detail = err.Error() errMsg := "step5: The node failed to execute the `keadm` installation command. Failure message: " + err.Error() + ";Please Login EdgeNode,For logs visit: journalctl -u edgecore.service-xe" installLogger += fmt.Sprintf(time.Now().Format(time.RFC3339) + " " +errMsg + "\n") middleware.Logger.Error(installLogger) config.InMemoryCache.SetDefault(cacheKey, installLogger) return } Msg = ">>>>>>step5: The node successfully executed the `keadm` installation command!<<<<<<" installLogger += fmt.Sprintf(time.Now().Format(time.RFC3339) + " " +Msg + "\n") config.InMemoryCache.SetDefault(cacheKey, installLogger).

[0035] ⑨ View logs: You can view the installation progress of the edge nodes.

[0036] ⑩ Check whether the execution result / log shows `KubeEdge edgecore is running`. If it appears, it means that the addition of the edge node is successful.

[0037] The present invention combines KubeEdge with a container orchestration system to achieve fast and automated deployment and management of edge nodes, enabling efficient utilization of edge computing resources while ensuring the stability and reliability of the system.

[0038] The above are only the preferred embodiments of the present invention. It should be understood that the present invention is not limited to the form disclosed herein, should not be regarded as excluding other embodiments, but can be used in various other combinations, modifications, and environments, and can be changed within the scope of the concept described herein through the above teachings or the techniques or knowledge in related fields. Any changes and variations made by those skilled in the art without departing from the spirit and scope of the present invention shall fall within the protection scope of the appended claims of the present invention.

Claims

1. A method for expanding edge nodes based on a container orchestration system, characterized in that It includes the following steps: S1. Deploy a container orchestration system; S2. Select edge nodes, fill in the relevant information of the edge nodes to be expanded, and then detect the relevant information of the edge nodes; S3. Detect the connectivity between the edge nodes to be expanded and the current cluster; S4. Complete the installation and addition of edge nodes.

2. The method for expanding edge nodes based on a container orchestration system according to claim 1, wherein In step S2, the relevant information of the edge nodes specifically includes: node name, node IP, SSH port, username, password, and select the edge node container runtime.

3. The method for expanding edge nodes based on a container orchestration system according to claim 2, wherein In step S2, the detection of the relevant information of the edge nodes specifically includes the following sub-steps: S21. Detect whether the edgecore service is already running and judge whether the name of the node to be added already exists; S22. Detect whether the directory ' / etc / kubeedge / ' exists in the node IP.

4. The method for expanding edge nodes based on a container orchestration system according to claim 1, wherein In step S4, it specifically includes the following sub-steps: S41. Check the installation progress of the edge node through the log; S42. Judge whether the edge node is successfully added.

5. The method for expanding edge nodes based on a container orchestration system according to claim 3, wherein Step S42 is specifically: check whether 'KubeEdge edgecore is running' appears in the log. If it appears, it is regarded as the successful addition and installation of the edge node.

6. The method for expanding edge nodes based on a container orchestration system according to claim 1, wherein It also includes the edge node copy and export step: copy the existing edge node configuration commands, execute the copied edge node configuration commands on the corresponding terminal device, and then execute step S3.

Images