Cluster deployment method and computing device

Abstract

This application provides a cluster deployment method and computing device, relating to the field of cluster technology, that can reduce the complexity of cluster deployment and improve its efficiency. The method includes: obtaining node information of at least one node to be added to the cluster; determining a cluster deployment policy based on the node information, the cluster deployment policy being used to instruct the configuration of the node information; and performing cluster deployment based on the cluster deployment policy. This application can be used during cluster deployment.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of computing devices, and in particular to a cluster deployment method and computing device. Background Art

[0002] With the widespread adoption of container technology, more and more applications can now run within containers. To fully leverage the advantages of flexible container deployment and dynamic resource allocation, container deployment can be achieved by building clusters. For example, Kubernetes (K8S) clusters automate container deployment, expansion, maintenance, and rolling upgrades to fully leverage container performance.

[0003] However, the current K8S cluster deployment process involves many manual intervention steps. This deployment method is cumbersome and affects the cluster deployment efficiency. Summary of the Invention

[0004] The embodiments of the present application provide a cluster deployment method and computing device, which can reduce the complexity of cluster deployment and improve the efficiency of cluster deployment.

[0005] In a first aspect, an embodiment of the present application provides a cluster deployment method, the method comprising: obtaining node information of at least one node to be added to the cluster; determining a cluster deployment strategy based on the node information, the cluster deployment strategy being used to indicate configuration of the node information; and performing cluster deployment based on the cluster deployment strategy.

[0006] An embodiment of the present application provides a cluster deployment method. First, node information of at least one node to be added to the cluster is obtained. Second, a cluster deployment policy is determined based on the node information. The cluster deployment policy is used to instruct the configuration of the node information. Finally, the cluster is deployed based on the cluster deployment policy. As can be seen, the cluster deployment policy enables automatic configuration of node information, thereby effectively reducing the number of manual steps in the cluster deployment process and improving cluster deployment efficiency.

[0007] In a possible implementation, the node information includes a host name, and the cluster deployment policy is used to indicate that the host name of each node is configured according to the node type of each node; different nodes have different configured host names.

[0008] In another possible implementation, the node information includes a node type, and the cluster deployment strategy is used to indicate that the node type of each node is configured according to a preset number or ratio of control nodes; the node type includes a control node and a working node.

[0009] In another possible implementation, the node information includes an international interconnection protocol IP address, and the cluster deployment policy is used to indicate that when the target node is not configured with an IP address, an IP address is allocated to the target node based on the Dynamic Host Configuration Protocol DHCP; the target node is one of the at least one node.

[0010] In another possible implementation, the cluster deployment strategy is determined based on the node information, including: providing an interactive interface for display on the terminal, the interactive interface containing the node information of each node; obtaining the configuration information entered by the user in the interactive interface, the configuration information is used to indicate the configuration of the node information; and determining the cluster deployment strategy based on the configuration information.

[0011] In another possible implementation, after obtaining the configuration information of the node set through network discovery, the method further includes: verifying the configuration information of the node set; deploying each node in the node set into the cluster based on the configuration information of the node set, including: after the verification is passed, deploying each node in the node set into the cluster based on the configuration information of the node set; wherein the verification is passed includes at least one of the following: the host name of each node in the node set is not repeated, the number of control nodes in the node set meets a preset threshold, and each node in the node set is configured with an international interconnection protocol IP address.

[0012] In another possible implementation, obtaining node information of at least one node to be joined to the cluster includes: sending a network discovery message to multiple nodes to be discovered; the network discovery message is used to request discovery of the node to be joined to the cluster; receiving response messages from multiple nodes; determining at least one node to be joined to the cluster from the multiple nodes based on the response messages; and determining the node information of at least one node to be joined to the cluster based on the response message of at least one node to be joined to the cluster.

[0013] In another possible implementation, at least one node to be joined to the cluster is determined from multiple nodes based on the response message, including: for each node among the multiple nodes, when the response message of the node includes an agent identifier, the node is determined to be the node to be joined to the cluster; the agent identifier is used to characterize that agent software is running in the node, and the node running the agent software is the node to be joined to the cluster.

[0014] In yet another possible implementation, the method further includes: for each of the at least one node, if the node has joined the cluster, stopping the running of the agent software in the node.

[0015] In another possible implementation, the above method is applied to the first node; cluster deployment is performed based on the cluster deployment strategy, including: determining the node type of the first node based on the host name of the first node; when the node type is a control node, the first node is cluster deployed based on the cluster deployment strategy; otherwise, the second node is instructed to perform cluster deployment based on the cluster deployment strategy; the second node is a node among at least one node, whose node type is a control node.

[0016] In a second aspect, the present application provides a cluster deployment device, comprising an acquisition module, a determination module, and a deployment module. The acquisition module is configured to acquire node information of at least one node to be added to the cluster; the determination module is configured to determine a cluster deployment strategy based on the node information, the cluster deployment strategy being configured to indicate the configuration of the node information; and the deployment module is configured to perform cluster deployment based on the cluster deployment strategy.

[0017] In a possible implementation, the node information includes a host name, and the cluster deployment policy is used to indicate that the host name of each node is configured according to the node type of each node; different nodes have different configured host names.

[0018] In another possible implementation, the node information includes a node type, and the cluster deployment strategy is used to indicate that the node type of each node is configured according to a preset number or ratio of control nodes; the node type includes a control node and a working node.

[0019] In another possible implementation, the node information includes an international interconnection protocol IP address, and the cluster deployment policy is used to indicate that when the target node is not configured with an international interconnection protocol IP address, an IP address is allocated to the target node based on the Dynamic Host Configuration Protocol DHCP; the target node is one of the at least one node.

[0020] In another possible implementation, the determination module is specifically used to provide an interactive interface for display on the terminal, the interactive interface containing node information of each node; obtain configuration information entered by the user in the interactive interface, the configuration information is used to indicate the configuration of the node information; and determine the cluster deployment strategy based on the configuration information.

[0021] In another possible implementation, the acquisition module is specifically used to send a network discovery message to multiple nodes to be discovered; the network discovery message is used to request the discovery of nodes to be added to the cluster; receive response messages from multiple nodes; determine at least one node to be added to the cluster from the multiple nodes based on the response messages; and determine the node information of at least one node to be added to the cluster based on the response message of at least one node to be added to the cluster.

[0022] In another possible implementation, the acquisition module is specifically used to, for each of multiple nodes, determine that the node is a node to be joined to the cluster when the node's response message includes an agent identifier; the agent identifier is used to represent that the node has agent software running in it, and the node running the agent software is the node to be joined to the cluster.

[0023] In another possible implementation, the apparatus further includes an operation module configured to, for each of the at least one node, stop the operation of the agent software in the node if the node has joined the cluster.

[0024] In another possible implementation, the deployment module is specifically used to determine the node type of the first node based on the host name of the first node; when the node type is a control node, the first node is cluster deployed based on the cluster deployment strategy; otherwise, the second node is instructed to be cluster deployed based on the cluster deployment strategy; the second node is a node among at least one node, whose node type is a control node.

[0025] In a third aspect, an embodiment of the present application provides a computing device comprising a processor and a memory; the processor is coupled to the memory; the memory is used to store computer instructions, which are loaded and executed by the processor to enable the computing device to implement the method of the first aspect above.

[0026] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which includes: computer software instructions; when the computer software instructions are executed in a computing device, the computing device implements the method of the first aspect above.

[0027] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on a computing device, the computing device executes the steps of the related method described in the first aspect above to implement the method of the first aspect above.

[0028] The beneficial effects of the second to fifth aspects mentioned above can be referred to the corresponding description of the first aspect and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 A schematic diagram of an application scenario provided in an embodiment of the present application;

[0030] Figure 2 A schematic diagram of the architecture of a K8S cluster provided in an embodiment of the present application;

[0031] Figure 3 A schematic diagram of the module composition of an agent software provided in an embodiment of the present application;

[0032] Figure 4A schematic diagram of the system architecture of a computing device provided in an embodiment of the present application;

[0033] Figure 5 A schematic diagram of a cluster deployment method provided in an embodiment of the present application;

[0034] Figure 6 A schematic diagram of an interactive interface provided in an embodiment of the present application;

[0035] Figure 7 A schematic diagram of a flow chart of another cluster deployment method provided in an embodiment of the present application;

[0036] Figure 8 A schematic diagram of another interactive interface provided in an embodiment of the present application;

[0037] Figure 9 A schematic diagram of another interactive interface provided in an embodiment of the present application;

[0038] Figure 10 A schematic diagram of a process for automatically generating node information based on a cluster deployment strategy provided in an embodiment of the present application;

[0039] Figure 11 A schematic diagram of a complete cluster deployment process provided in an embodiment of the present application;

[0040] Figure 12 A schematic diagram of the composition of a cluster deployment device provided in an embodiment of the present application;

[0041] Figure 13 A schematic diagram of the composition of a computing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0043] It should be noted that in the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described in the embodiments of this application as "exemplarily" or "for example" should not be interpreted as being more preferred or advantageous than other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

[0044] In order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order.

[0045] The following is an explanation of the technical terms involved in the embodiments of this application.

[0046] 1. Container: A virtualization technology in computer operating systems. This technology allows application processes to run in a relatively independent and isolated environment (including independent file systems, namespaces, resource views, etc.). This simplifies application deployment, enhances application portability and security, and improves system resource utilization. Container technology is widely used in service-oriented scenarios in cloud computing. The object resulting from packaging an application and its corresponding dependencies (such as the runtime environment) using container technology is called a containerized application.

[0047] 2. Kubernetes: K8S for short, is an open-source container orchestration system used to automate the deployment, scaling, and management of containerized applications. The platform provided by Kubernetes makes it easier for developers and operations personnel to deploy and maintain distributed applications.

[0048] 3. Kubernetes Cluster: A Kubernetes cluster (hereinafter referred to as a cluster) consists of multiple nodes, which can be physical computing devices or virtual machines running on computing devices. Each node in a Kubernetes cluster runs Kubernetes components, including the kubelet (node ​​agent) and kube-proxy (network agent). Nodes in a Kubernetes cluster can be categorized as control nodes or worker nodes. A Kubernetes cluster contains at least one control node.

[0049] 4. Control Node: Also known as the control-plane or master node, it manages the state and operation of the entire cluster and controls communications across the cluster, such as deciding which application to run and what container to use.

[0050] 5. Worker node: A node that deploys containerized applications and provides workloads.

[0051] 6. Kubernetes Appliance: This device integrates the hardware and software of the Kubernetes platform. In other words, it integrates Kubernetes components with specialized hardware to create a computing device that allows containerized applications to run more efficiently. To simplify deploying Kubernetes components on nodes during the construction of a Kubernetes cluster, you can use the Kubernetes Appliance as a node in the cluster.

[0052] 7. Kubespray: It is a container hybrid cloud management system for cloud-native applications built on Kubernetes. It is also a cluster deployment tool for automated deployment of K8S clusters.

[0053] An embodiment of the present application provides a cluster deployment method, which determines a cluster deployment strategy for instructing configuration of node information, thereby achieving automatic cluster deployment based on the cluster deployment strategy and improving cluster deployment efficiency.

[0054] In some embodiments, the method provided in the embodiments of the present application first obtains node information for at least one node to be added to the cluster. Secondly, based on the node information, a cluster deployment policy is determined, which instructs the configuration of the node information. Finally, the cluster is deployed based on the cluster deployment policy. As can be seen, the cluster deployment policy enables automatic configuration of node information, thereby effectively reducing the number of manual steps involved in the cluster deployment process and improving cluster deployment efficiency.

[0055] The embodiments provided in this application are described in detail below with reference to the accompanying drawings.

[0056] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of the present application. Figure 1 As shown, it includes multiple nodes 101. Each node 101 can be a physical computing device or a virtual machine running on a computing device. Multiple nodes 101 are connected through a network (such as the Internet, a local area network, etc.), and the nodes 101 can communicate with each other.

[0057] In an embodiment of the present application, each node 101 includes an agent software (agent), and the agent software runs after the node 101 is powered on. When cluster deployment is required, the agent software can obtain the node information of each node 101 in the network through network discovery, and determine the cluster deployment strategy based on the node information, and finally realize the automatic deployment of the cluster based on the cluster deployment strategy. In an embodiment of the present application, each node 101 can specifically be a K8S all-in-one machine, that is, an operating system is pre-deployed in each node 101, and K8S components are deployed. It should be understood that the use of a K8S all-in-one machine for cluster deployment can effectively save the process of deploying K8S components in the node 101, so as to speed up the deployment progress.

[0058] In addition, when Figure 1 After the multiple nodes 101 shown in the figure form a cluster, some of the nodes 101 serve as control nodes in the cluster, while the other nodes serve as working nodes. There are some differences between the functions of control nodes and working nodes. Figure 2 The following is a schematic diagram of the K8S cluster architecture, which introduces the control node and the working node respectively.

[0059] The technical solution provided in the embodiment of this application can be applied to Figure 1 In any node 101, the node 101 that executes this solution is referred to as the first node below.

[0060] The architecture of the K8S cluster is described below with reference to the accompanying drawings.

[0061] Figure 2 This is a schematic diagram of the architecture of a K8S cluster provided in an embodiment of the present application. Figure 2 As mentioned above, at the hardware level, a K8S cluster includes multiple nodes. Typically, a K8S cluster includes at least one control node (one is shown in the figure as an example) and multiple working nodes (two are shown in the figure as an example).

[0062] At the software level, the control node includes etcd component 201, K8S application program interface service (kube-api-server) component 202, scheduler component 203, control management (controller-manaer) component 204 and flannel component 205.

[0063] Among them, the kube-api-server component 202 is the entry point for operating and managing the K8S cluster, providing a standardized interface so that users can query and manage the cluster status. The etcd component 201 is a highly available distributed key-value storage system for storing the operating data of the K8S cluster. The scheduler component 203 is responsible for allocating the newly created container group 206 (pod206) to the appropriate working node for operation according to the preset scheduling strategy and the current status of the K8S cluster. Among them, pod206 is the smallest deployment unit and the smallest and simplest basic unit for operation and management in the K8S cluster. A pod206 can contain one or more closely related containers, which share runtime environments such as storage, network, and process namespace.

[0064] The control ler-manager component 204 is a combination of multiple control modules in K8S, which are responsible for managing and maintaining the status of the cluster.

[0065] The flannel component 505 is used to provide cross-node container network functions for the K8S cluster, enabling containers on different nodes to communicate within the same network.

[0066] In addition, the control node also includes a cloud-controller-manager component 207, which is used to connect to the cloud and provide business services for computing devices in the cloud.

[0067] Among them, the working node includes a kubelet component 208, a K8S proxy (kube-proxy) component 209 and a container runtime component (container runtime interface, CRI) (not shown in the figure), and one or more pods 206 are running in each working node.

[0068] The kubelet component 208 is a node agent running on a worker node and is responsible for managing the operation cycle of pods 206 and containers.

[0069] The kube-proxy component 209 is a network proxy running on the working node, which is used to implement network forwarding of K8S services between nodes.

[0070] CRI is responsible for the communication between the container and K8S components when the container is running.

[0071] In addition, to enable communication between pods 206 in different nodes, each worker node can also deploy a container network interface (CNI) plug-in. The main functions of the CNI plug-in include assigning IP addresses to containers, configuring network routing, and implementing network isolation and security policies. By using the CNI plug-in, containers can run in a variety of different network environments, and users can easily perform network management and configuration.

[0072] The following describes the functions supported by the agent software. Figure 3 This is a schematic diagram of the module composition of an agent software provided in an embodiment of the present application. Figure 3 As shown, it includes an interactive interface module, an application programming interface (API) sub-module, a cluster deployment sub-module, a storage sub-module, a node configuration management sub-module and an automatic discovery sub-module.

[0073] The interactive interface submodule provides an interactive interface for cluster deployment. Users can access this interface through a terminal. This interactive interface can be displayed via a web page or a command line. It can provide interfaces for viewing discovered node information, configuring policies, and providing an overview of node information. The interactive interface submodule uses the API submodule's interface to implement the display functions of these interfaces.

[0074] The API submodule provides APIs corresponding to all functions required during cluster deployment. The API can be understood as the access address of each functional module. By calling the API, you can access the corresponding functional module to implement the corresponding function. Among them, the API can be a hypertext transfer protocol (HTTP) interface (corresponding to the web display method) or a command line interface (corresponding to the command line display method). Table 1 below is an example of an interface definition:

[0075] Table 1

[0076]

[0077]

[0078] When the user initiates the automatic discovery process through the interactive interface, the interactive interface submodule sends instructions to the API submodule, so that the API submodule accesses the Figure 3 The automatic discovery submodule in the cluster automatically discovers the node information of at least one node to be added to the cluster.

[0079] When the user initiates the node information query process through the interactive interface, the interactive interface sub-module sends instructions to the API sub-module, so that the API sub-module accesses the node configuration management sub-module through the node information query interface in Table 1. The node configuration management sub-module can generate node information and return it to the interactive interface to display it to the user.

[0080] When the user initiates the process of node information modification through the interactive interface, the interactive interface sub-module sends instructions to the API sub-module, so that the API sub-module accesses the node configuration management sub-module through the node information modification interface in Table 1. The node configuration management sub-module can generate node information and display it on the interactive interface, and modify and update the node information based on the user's modification operation.

[0081] When the user initiates the cluster deployment process through the interactive interface, the interactive interface sub-module sends instructions to the API sub-module, so that the API sub-module accesses the cluster deployment sub-module through the cluster deployment startup interface in Table 1. The cluster deployment sub-module can perform cluster deployment according to the node information and output the cluster deployment result (deployment success or deployment failure).

[0082] The storage submodule is used to store node information. The present embodiment does not limit the specific form of configuration information storage. After acquiring node information through network discovery, the automatic discovery submodule can interact with the storage submodule to store the node information. The node configuration management submodule can obtain and display node information from the storage submodule, as well as update and modify the node information.

[0083] The following is for Figure 1 The system architecture of a computing device is described using a computing device in which each node is a physical entity as an example. Specifically, the computing device is a server. Formally, the server can be a blade server, a high-density server, a rack server, or a whole-cabinet server. Functionally, the server can be a general-purpose server, a graphics processing unit (GPU) server, an artificial intelligence (AI) server, or the like. Figure 4 A schematic diagram of the system architecture of a computing device, such as Figure 4 As shown, the hardware of the computing device includes a processor, a baseboard management controller, a hard disk, and a memory. The software includes a management control module and an operating system (OS).

[0084] The management control module runs in the baseboard management controller, and the OS runs on the processor (such as Figure 4 shown).

[0085] The management control module may be a management unit of a non-business module. For example, the management control module may remotely maintain and manage a computing device through a dedicated data channel, and the management control module may communicate with a basic input and output system (BIOS) and an operating system (OS) through an out-of-band management interface of the computing device.

[0086] Exemplarily, the management control module may include a management unit for managing the operating status of the computing device, a management system in a management chip, a baseboard management controller (BMC) of the computing device, a system management module (SMM), etc. It should be noted that the embodiments of the present application do not limit the specific form of the out-of-band management module, and the above description is merely an example.

[0087] Memory, also known as internal memory or main memory, is installed in the memory slots on the motherboard of a computing device. The memory communicates with the memory controller through a memory channel.

[0088] A hard disk can be a plug-in hard disk equipped on a computing device, a smart media card (SMC), a secure digital (SD) card, a flash card, etc., or an external storage device such as a USB flash drive.

[0089] In the embodiment of the present application, the memory stores a cluster deployment tool and agent software. The processor can execute the technical solution provided by the embodiment of the present application by running the agent software.

[0090] It should be noted that the system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0091] It should be noted that, in order to facilitate the deployment of the cluster, the computing devices used to participate in the cluster deployment in the embodiment of the present application are pre-installed with an operating system when leaving the factory, and the cluster deployment tools (such as the aforementioned kubespray) and agent software are preset. At the same time, the network port of the computing device is pre-configured to open the Internet Protocol Version 6 (internet protocol version 6, IPv6) configuration to support the secure shell protocol (secure shell, SSH). In addition, the SSH default account password is configured for the computing device (the SSH default account passwords of multiple computing devices can be the same) and the SSH function is enabled (to facilitate the modification of the node's host name, IP address, etc. through the SSH function during subsequent cluster deployment). In addition, optionally, the node type (i.e., whether the computing device is used as a control node or a working node) can be preset according to the customer's order requirements.

[0092] Figure 5 A flow chart of a cluster deployment method provided in an embodiment of the present application. For example, the cluster deployment method provided in an embodiment of the present application can be applied to Figure 1 In any node shown (such as the first node), or Figure 1 In the computing device shown.

[0093] like Figure 5 As shown, the cluster deployment method provided in the embodiment of the present application may specifically include the following steps:

[0094] S501: Obtain node information of at least one node to be added to a cluster.

[0095] In the embodiment of the present application, the first node can obtain the node information of at least one node to be added to the cluster through user input or network discovery. The network discovery mentioned here refers to the technology of querying other device related information through the network. The specific process of network discovery can be found in the following Figure 7 Corresponding description of the embodiment.

[0096] Optionally, the first node may automatically execute S501 after being powered on.

[0097] Optionally, the first node may execute the above S501 after receiving the cluster deployment instruction. Exemplarily, in the scenario of on-site cluster deployment, when the operation and maintenance personnel wait for all nodes in the network to be powered on, the operation and maintenance personnel can select any node as the first node and use the user-side device (such as a mobile phone terminal, a personal computer, etc.) to access the interactive interface through the IPv6 link-local address of the first node (the interactive interface is provided by the agent software running in the first node). When the operation and maintenance personnel access the interactive interface, it can be regarded as the first node receiving the cluster deployment instruction. Among them, the link-local address is a special address used for communication between devices in the network. In the network, each device has a unique corresponding link-local address.

[0098] In one embodiment, the node information may include one or more of the following: the node's host name (generally localhost by default), the node's network port identifier (configured by the operating system running the node), the node's IP address (null value if the node is not configured in advance), and the node type of the node (null value if not configured in advance).

[0099] Optionally, the node information also includes a media access control address (MAC) of the node, a serial number (SN) of the node (SN is used to uniquely identify the node), a model of the node, and the like.

[0100] For example, Figure 6 This is a schematic diagram of an interactive interface provided in an embodiment of the present application. Figure 6 As shown, after the first node obtains the node information of at least one node, it can display the node list on the interactive interface. The node list is used to display the node information of each node, including fields such as node MAC, node SN, model, host name, network port and IP address, node type, etc. Figure 6 The figure shows the node information of four nodes. It can be seen that for the IP address field, the last three nodes have no IP addresses configured and are null. For the node type field, the first node is pre-configured as a control node, while the last three nodes have no node type configured and are null.

[0101] It should be understood that when the number of nodes is large, Figure 6 The node list can be displayed in pages.

[0102] S502: Determine a cluster deployment strategy based on the node information. The cluster deployment strategy here is used to indicate how to configure the node information. The cluster deployment strategy may include at least one of the following: a host name configuration strategy, a node type configuration strategy, and an IP address configuration strategy.

[0103] If the cluster deployment strategy is a host name configuration strategy, the node information includes the host name. The cluster deployment strategy is used to instruct that the host name of each node be configured separately according to the node type of each node, and different nodes have different configured host names.

[0104] For cluster deployment policies that use a node type configuration policy, the node information includes the node type. The cluster deployment policy is used to instruct the node type of each node to be configured based on a preset number or ratio of control nodes. Node types include control nodes and worker nodes.

[0105] If the cluster deployment policy is an IP address configuration policy, the node information includes an IP address. The cluster deployment policy indicates that, if the target node does not have an IP address configured, an IP address is assigned to the target node based on the Dynamic Host Configuration Protocol (DHCP); the target node is one of the at least one node. DHCP is a network protocol that allows devices on a network to automatically obtain IP addresses and other related configuration information.

[0106] In one implementation, the above S502 may be implemented as the following steps a to c:

[0107] Step a: providing an interactive interface for displaying on a terminal, wherein the interactive interface includes node information of each node.

[0108] Step b: obtaining configuration information input by the user in the interactive interface, where the configuration information is used to indicate configuration of the node information.

[0109] Step c: Determine the cluster deployment strategy based on the configuration information.

[0110] For the above steps a to c, the first node may provide an interactive interface (such as Figure 6 As described) to display the node information of each node. The user can view the interactive interface through the terminal, and input configuration information through the interface interaction to configure the node information (such as adding node information, modifying node information, deleting node information, etc.). Finally, the first node determines the cluster deployment strategy based on the configuration information. If it is determined according to the configuration information that the host names of the two nodes conflict, the host name configuration strategy is determined, and the host names are automatically assigned to the two nodes. If it is determined according to the configuration information that there are more control nodes in the node, the node type configuration strategy is determined, and the appropriate number of control nodes is automatically configured. If it is determined according to the configuration information that there are more control nodes in a certain node, the node type configuration strategy is determined, and the appropriate number of control nodes is automatically configured.

[0111] S503: Perform cluster deployment based on the cluster deployment strategy.

[0112] After determining the cluster deployment strategy, the first node can be deployed based on the cluster deployment strategy. The cluster deployment strategy can automatically configure node information during the deployment process to ensure that the node information meets the cluster deployment requirements (such as unique host names and IP addresses for each node), ensuring the smooth completion of the cluster deployment.

[0113] It should be noted that in order to ensure the security of the cluster and the high performance of the cluster, the execution subject of the cluster deployment step is the pre-configured control node (the control node has high performance and has good security and confidentiality measures). Therefore, in the related art, when the operation and maintenance personnel deploy the cluster on site, they generally first determine the control node from multiple nodes, and then start the cluster deployment process on the control node. This adds extra work to the operation and maintenance personnel and affects the efficiency of cluster deployment. The technical solution provided in the embodiment of the present application can remove the restriction that the node executing the deployment is the control node, that is, the above S503 can be implemented as:

[0114] S5031. Determine the node type of the first node according to the host name of the first node.

[0115] Generally, a node can be configured with a hostname before shipment to indicate whether it is a control node or a worker node. For example, if the hostname is "master1," the node is designated as a control node. Other names, such as "work" or "localhost," indicate that the node is not a control node.

[0116] S5032: When the node type is a control node, the first node performs cluster deployment based on a cluster deployment policy.

[0117] When the node type of the first node is a control node, the first node can run its pre-configured cluster deployment tool (such as kubespray) based on the cluster deployment strategy, start the automated cluster deployment process until the cluster deployment is completed, and deploy each node into the cluster.

[0118] It should be noted that the process of initiating cluster deployment generally involves the transmission of cluster deployment instructions / tools between multiple nodes. Therefore, in this solution, the first node can establish an SSH channel with other nodes via SSH to transmit cluster deployment instructions / tools through the SSH channel. Of course, other transmission methods can also be used, and this embodiment of the application does not specifically limit this.

[0119] S5033: Otherwise, instruct the second node to perform cluster deployment based on the cluster deployment policy. The second node is a node of the at least one node whose node type is a control node.

[0120] If the first node's node type is not a control node, the first node can determine a second node whose node type is a control node (if there are multiple control nodes, it can select any one, such as the one with the smallest MAC address), send the cluster deployment policy to the second node, and instruct the second node to start the cluster deployment process. In this way, the second node can run its pre-configured cluster deployment tool (such as kubespray) based on the cluster deployment policy, start the automated cluster deployment process, and complete the cluster deployment until each node is deployed to the cluster.

[0121] As can be seen, during the deployment process, operators do not need to determine the control node; they can execute the cluster deployment process on any node. The selected node automatically determines the control node and instructs the control node to complete the subsequent cluster deployment process, saving operators time in determining the control node and improving cluster deployment efficiency.

[0122] The following describes the process of obtaining node information of at least one node to be added to the cluster through network discovery in the aforementioned S501 in conjunction with specific embodiments and drawings. Figure 7 As shown, the above S501 can be implemented as follows:

[0123] S5011. Send a network discovery message to multiple nodes to be discovered.

[0124] The multiple nodes to be discovered may be nodes that belong to the same network (such as a local area network) as the first node. The network discovery message is used to request discovery of nodes to be added to the cluster.

[0125] The first node may broadcast the network discovery message to the network, so as to respectively send the network discovery message to a plurality of nodes to be discovered in the network.

[0126] For example, the network discovery message can be a Simple Service Discovery Protocol (SSDP) m-search message. SSDP is an Internet Protocol-based network protocol used to discover and describe available devices within a network. m-search is a message format used for network discovery, used to broadcast messages to the network to discover available devices.

[0127] S5012. Receive response messages from multiple nodes.

[0128] S5013. Determine at least one node to be added to the cluster from the multiple nodes according to the response message.

[0129] It should be understood that some of the multiple nodes may not be nodes to be added to the cluster (for example, they do not need to join the cluster, or they have already joined the cluster). However, the network discovery message is sent to each node, that is, each node may respond to the network discovery message. Therefore, the first node can determine the node set from the multiple nodes based on the content of the response message (for example, checking whether the response message carries a specific identifier).

[0130] In one possible implementation, for each of the multiple nodes, if the node's response message includes an agent identifier, the node is determined to be a node to be added to the cluster. The agent identifier is used to indicate that the node is running agent software, and the node running the agent software is the node to be added to the cluster.

[0131] S5014: Determine node information of the at least one node to be added to the cluster according to the response message of the at least one node to be added to the cluster.

[0132] After determining at least one node to be added to the cluster, the first node may obtain node information (such as host name, node type, IP address, etc.) of the at least one node according to a response message of the at least one node.

[0133] As can be seen, the embodiments of the present application use network discovery technology to replace manual configuration solutions, automatically obtaining node information for each node, eliminating the need for manual input of node information for each node, and effectively improving cluster deployment efficiency. In addition, obtaining node information through network discovery can reduce the possibility of errors during manual configuration and ensure the correct deployment of the cluster.

[0134] In a possible implementation, after the above S503, the technical solution provided in the embodiment of the present application further includes the following steps: for each node in at least one node, if the node has joined the cluster, stopping the operation of the agent software in the node.

[0135] It should be understood that the node running the agent software is the node to be added to the cluster. When the cluster deployment process is completed, it means that each node has joined the cluster, and the first node or the second node mentioned above can send an instruction message to each node to instruct to stop the operation of the agent software in the node. Similarly, the first node or the second node can also stop the operation of the agent software in the node. In this way, when the cluster is deployed again in the same network later, the agent software in the node that has joined the cluster this time has stopped running, and will not monitor the network discovery message, thereby ensuring that when the cluster is deployed again, the new first node can accurately determine the node to be added to the cluster in the network, and avoid the nodes that have joined the cluster from joining the cluster repeatedly.

[0136] In some scenarios, the first node may also listen for and respond to network discovery messages. That is, if a third node (a node other than the first node) is the node that receives cluster deployment instructions, the first node may receive the network discovery message from the third node. Accordingly, the first node responds to the network discovery message and sends its own node information to the third node. In addition, if the first node is currently running agent software, the first node's response message will include an agent identifier.

[0137] The above cluster deployment strategy is described below with examples in conjunction with specific embodiments and the accompanying drawings.

[0138] It should be understood that the hostname identifies the node within the cluster, so different nodes in the cluster must have unique hostnames. A cluster requires at least one or more control nodes to manage the entire cluster, so the number of control nodes must meet a predetermined number or ratio. The IP address indicates the node's location within the network, making it easier to access each node in the cluster. Therefore, each node must be configured with a corresponding IP address.

[0139] The node information of at least one node obtained in S501 may not meet the cluster deployment conditions (for example, two nodes have the same host name, a node is not configured with an IP address, etc.), which may make the cluster deployment process difficult. In this case, a cluster deployment strategy can be determined and the node information can be configured so that the node information meets the cluster deployment conditions.

[0140] There are two ways to configure a cluster: manual modification and automatic modification.

[0141] Manual modification is done by the operation and maintenance personnel through the aforementioned interactive interface. Figure 5 Modify the host name of each node on the interface shown to ensure that there is no duplication, and configure the IP address of each node, the node type of each node, etc. After the modification is completed, the user can click Figure 5 Then the first node re-verifies the modified configuration information. If the verification is correct, it will be displayed Figure 8 The interactive interface shown, from Figure 8 As you can see, each node has a unique host name and is configured with an IP address and node type. Click Start to start the cluster deployment.

[0142] Automatic modification can be divided into modification based on host name allocation policy, modification based on node type allocation policy, and modification based on IP address allocation policy.

[0143] Regarding hostnames, if a node doesn't have a hostname configured, or if two nodes have duplicate hostnames after a hostname is configured, cluster deployment will be affected. Therefore, the first node can configure the hostname of each node based on its type, ensuring that different nodes have different hostnames. For example, for control nodes, you can sequentially configure master1, master2, and so on as the hostname of each node. For worker nodes, you can sequentially configure work1, work2, and so on as the hostname of each node to avoid duplicate hostnames.

[0144] It should be noted that modifying a node's hostname generally takes effect by modifying the node's / etc / hosts configuration file. The / etc / hosts configuration file specifies the mapping between a node's hostname and IP address. Therefore, when a node's hostname is modified, the first node can establish an SSH tunnel with the node, access the node's / etc / hosts configuration file through the SSH tunnel, and modify the hostname.

[0145] For node types, users can enter a preset number of control nodes (generally an odd number such as 1, 3, or 5) or a ratio (e.g., one-third of the total number of nodes as control nodes). Furthermore, since working nodes are nodes that provide business services, the node type configuration process can prioritize the allocation of working nodes. For example, if network discovery reveals two control nodes, four working nodes, and three nodes with unconfigured node types, if the preset number of control nodes is 3, the first node will configure one of the three unconfigured node types as a control node and the other two as working nodes. If the preset number of control nodes is 5, all three unconfigured node types will be configured as control nodes. If the preset number of control nodes is 1, all three unconfigured node types will be configured as working nodes, and one of the two currently configured control nodes will be modified to a working node, ensuring the required number of control nodes is met. If the preset number of control nodes is 7, even if all three nodes that are not configured as node types are configured as control nodes, the number of control nodes still does not meet the preset threshold. In this case, the first node will prompt the user to modify the preset number of control nodes.

[0146] Regarding IP addresses, if a node does not have an IP address configured in advance (pre-configured IP addresses are generally static IP addresses, i.e., IP addresses that remain unchanged for a long time), the IP address in the node information obtained by the first node through network discovery will be null. The first node can then automatically assign an IP address (dynamic IP address) to the node that does not have an IP address configured in advance based on DHCP.

[0147] It should be noted that if a node (such as the target node) has a static IP address configured in the / etc / hosts configuration file in advance, and the user subsequently modifies the IP address of the target node, the modification of the IP address will cause the network between the first node and the target node to be disconnected. Therefore, when the network is interrupted, the first node re-establishes a connection with the target node and queries the target node's IP address through the SSH channel to see if the modification is successful. If the modification is successful, it means that the user's modification is effective and the subsequent steps can be continued. If the modification is not successful, repeat the above process.

[0148] For example, Figure 9 This is a schematic diagram of another interactive interface provided in an embodiment of the present application. Figure 9 As shown, cluster deployment policies are divided into automatic and custom. If the user selects automatic, the hostname configuration policy and node type configuration policy are automatically executed to implement node information modification. If the user selects custom, the user can choose automatic or manual configuration for both the hostname configuration policy and the node type configuration policy.

[0149] Figure 10 This is a flow chart of automatically generating node information based on cluster deployment strategy provided by the embodiment of the present application. Figure 10 As shown, first, the total number of nodes discovered in the network is obtained, and it can be divided into two branches according to whether the node type configuration policy is automatic configuration or a custom preset threshold. First, the branch of automatic configuration is explained. If it is determined that the total number of nodes is <= 3, then one control node is retained, and the others are configured as working nodes, and the host name configuration policy is determined. Otherwise, 3 control nodes are retained, and the others are configured as working nodes, and the host name configuration policy is determined. Furthermore, when the host name configuration policy is manual, the node host name is kept unchanged (that is, the first node will not automatically modify the node configuration information), and the end is ended. When the host name configuration policy is automatic, non-repeating host names are automatically generated according to the node type, and the end is ended.

[0150] Next, the branch of the customized preset threshold (i.e., the number of control nodes preset as mentioned above) is explained. First, obtain the information (including identification, number, etc.) of the control nodes, working nodes, and unconfigured nodes (nodes of unconfigured node type), and compare the number of control nodes with the preset threshold. If the number of control nodes is greater than the preset threshold, the unconfigured nodes are configured as working nodes, and after the redundant control nodes are configured as working nodes, the host name configuration policy is determined. If the number of control nodes is equal to the preset threshold, all the unconfigured nodes are configured as working nodes, and the host name configuration policy is determined. If the number of control nodes is less than the preset threshold, it is determined whether the number of configured nodes meets the preset threshold. If it does, the host name configuration policy is determined after the difference number of unconfigured nodes are configured as control nodes. If it does not meet, an error is prompted, indicating to reconfigure the preset threshold, and the process ends.

[0151] Figure 11 This is a schematic diagram of a complete cluster deployment process provided by an embodiment of the present application. Figure 11 As shown, 1. Receive the cluster deployment instruction and obtain the node information of at least one node to be added to the cluster. 2. Modify the IP address and host name of the node through the SSH channel. 3. Determine whether this node is a control node. If so, 4. This node starts cluster deployment, 5. Generates node information for each node on the control node (the control node is itself at this time), 6. Use the cluster deployment tool to deploy the cluster, 7. Wait for the cluster deployment to complete. After the deployment is complete, 8. Stop the operation of the agent software on the node. If step 3 is judged as no, then 9. Select a control node (you can select the control node with the smallest MAC address), 5. After the control node generates the node information for each node, continue to execute steps 6-8.

[0152] The cluster deployment method provided in an embodiment of the present application first obtains node information for at least one node to be added to the cluster. Secondly, based on the node information, a cluster deployment policy is determined, which is used to instruct the configuration of the node information. Finally, the cluster is deployed based on the cluster deployment policy. As can be seen, the cluster deployment policy enables automatic configuration of node information, thereby effectively reducing the number of manual steps in the cluster deployment process and improving cluster deployment efficiency.

[0153] Furthermore, this technical solution can improve cluster deployment efficiency by obtaining node information through network discovery. In addition, there is no need to manually enter node information, reducing the possibility of manual configuration errors and ensuring correct cluster deployment.

[0154] It can be seen that the above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. In order to achieve the above functions, the embodiment of the present application provides a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily appreciate that, in combination with the modules and algorithm steps of each example described in the embodiment disclosed herein, the embodiment of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0155] In an exemplary embodiment, the present application further provides a cluster deployment device. The cluster deployment device can be the aforementioned computing device or a processor in the computing device. The cluster deployment device can include one or more functional modules for implementing the cluster deployment method of the above method embodiment.

[0156] For example, Figure 12 This is a schematic diagram of a cluster deployment device provided in an embodiment of the present application. Figure 12 As shown, the cluster deployment device includes: an acquisition module 1201 , a determination module 1202 and a deployment module 1203 .

[0157] The acquisition module 1201 is used to obtain node information of at least one node to be added to the cluster;

[0158] The determination module 1202 is used to determine a cluster deployment strategy based on the node information, where the cluster deployment strategy is used to instruct configuration of the node information;

[0159] The deployment module 1203 is used to perform cluster deployment based on the cluster deployment strategy.

[0160] In a possible implementation, the node information includes a host name, and the cluster deployment policy is used to indicate that the host name of each node is configured according to the node type of each node; different nodes have different configured host names.

[0161] In another possible implementation, the node information includes a node type, and the cluster deployment strategy is used to indicate that the node type of each node is configured according to a preset number or ratio of control nodes; the node type includes a control node and a working node.

[0162] In another possible implementation, the cluster deployment policy is used to indicate that, when the target node is not configured with an International Internet Protocol IP address, an IP address is allocated to the target node based on a Dynamic Host Configuration Protocol (DHCP); the target node is one of the at least one node.

[0163] In another possible implementation, the determination module 1202 is specifically used to provide an interactive interface for display on the terminal, the interactive interface containing node information of each node; obtain configuration information entered by the user in the interactive interface, the configuration information is used to indicate the configuration of the node information; and determine the cluster deployment strategy based on the configuration information.

[0164] In another possible implementation, the acquisition module 1201 is specifically used to send a network discovery message to multiple nodes to be discovered; the network discovery message is used to request the discovery of nodes to be added to the cluster; receive response messages from multiple nodes; determine at least one node to be added to the cluster from the multiple nodes based on the response messages; and determine the node information of at least one node to be added to the cluster based on the response message of at least one node to be added to the cluster.

[0165] In another possible implementation, the acquisition module 1201 is specifically used to, for each of the multiple nodes, determine that the node is a node to be joined to the cluster when the node's response message includes an agent identifier; the agent identifier is used to characterize that agent software is running in the node, and the node running the agent software is the node to be joined to the cluster.

[0166] In another possible implementation, the apparatus further includes: an operation module 1204. The operation module 1204 is configured to, for each of the at least one node, stop the operation of the agent software in the node if the node has joined the cluster.

[0167] In another possible implementation, the deployment module 1203 is specifically used to determine the node type of the first node based on the host name of the first node; when the node type is a control node, the first node is cluster deployed based on the cluster deployment strategy; otherwise, the second node is instructed to be cluster deployed based on the cluster deployment strategy; the second node is a node among at least one node, whose node type is a control node.

[0168] In an exemplary embodiment, the present application also provides a computing device. Figure 13 This is a schematic diagram of the composition of the computing device provided in the embodiment of the present application. Figure 13 As shown, the computing device may include: a processor 1301 and a memory 1302; the memory 1302 stores instructions executable by the processor 1301; when the processor 1301 is configured to execute the instructions, the computing device implements the method described in the aforementioned method embodiment.

[0169] The embodiment of the present application also provides a computer-readable storage medium. All or part of the processes in the above-mentioned method embodiment can be completed by computer instructions to instruct the relevant hardware, and the program can be stored in the above-mentioned computer-readable storage medium. When the program is executed, it may include the processes of the above-mentioned method embodiments. The computer-readable storage medium can be the memory of any of the aforementioned embodiments. The above-mentioned computer-readable storage medium can also be an external storage device of the deployment device of the above-mentioned cluster, such as a plug-in hard disk, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc. equipped on the deployment device of the above-mentioned cluster. Furthermore, the above-mentioned computer-readable storage medium can also include both the internal storage unit of the deployment device of the above-mentioned cluster and an external storage device. The above-mentioned computer-readable storage medium is used to store the above-mentioned computer program and other programs and data required by the deployment device of the above-mentioned cluster. The above-mentioned computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.

[0170] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program product is run on a computer, the computer is enabled to execute any one of the cluster deployment methods provided in the above embodiments.

[0171] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0172] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

[0173] The above are only specific embodiments of the present application, but the scope of protection of the present application is not limited thereto. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A cluster deployment method, characterized in that: The method comprises: Sending a network discovery message to multiple nodes to be discovered; the network discovery message is used to request discovery of nodes to be added to the cluster; receiving response messages from the multiple nodes; For each of the multiple nodes, if the response message of the node includes an agent identifier, determining that the node is a node to be added to the cluster; the agent identifier is used to indicate that agent software is running in the node, and the node running the agent software is the node to be added to the cluster; Determining node information of the at least one node to be added to the cluster according to a response message of the at least one node to be added to the cluster; Determining a cluster deployment strategy based on the node information, where the cluster deployment strategy is used to instruct configuration of the node information; Cluster deployment is performed based on the cluster deployment strategy.

2. The method according to claim 1, characterized in that The node information includes a host name, and the cluster deployment strategy is used to indicate that the host name of each node is configured according to the node type of each node; different nodes have different configured host names.

3. The method according to claim 1, characterized in that The node information includes a node type, and the cluster deployment strategy is used to indicate that the node type of each node is configured according to a preset number or ratio of control nodes; the node type includes a control node and a working node.

4. The method according to claim 1, wherein The node information includes an international interconnection protocol IP address, and the cluster deployment policy is used to indicate that, when the target node is not configured with an IP address, an IP address is allocated to the target node based on the Dynamic Host Configuration Protocol DHCP; The target node is one of the at least one node.

5. The method according to claim 1, characterized in that The determining of the cluster deployment strategy based on the node information includes: Providing an interactive interface for display on a terminal, wherein the interactive interface includes node information of each of the nodes; Acquire configuration information input by the user on the interactive interface, where the configuration information is used to indicate configuration of the node information; Determine a cluster deployment strategy based on the configuration information.

6. The method according to claim 1, wherein The method further comprises: For each node of the at least one node, if the node has joined the cluster, stop running the agent software in the node.

7. The method according to any one of claims 1 to 6, characterized in that The method is applied to a first node; The performing cluster deployment based on the cluster deployment strategy includes: Determining a node type of the first node according to the host name of the first node; In a case where the node type is a control node, the first node performs cluster deployment based on the cluster deployment strategy; Otherwise, instruct a second node to perform cluster deployment based on the cluster deployment strategy; the second node is a node of the at least one node whose node type is a control node.

8. A computing device, characterized in that The computing device includes a processor and a memory; the processor is coupled to the memory; the memory is used to store computer instructions, and the computer instructions are loaded and executed by the processor to enable the computing device to implement the cluster deployment method according to any one of claims 1 to 7.

Images