Node information processing system and method

Abstract

The present invention provides a node information processing system and method. In this system, a client collects node information of the resource pool node in which it is located, and upon receiving a report request from a load balancing component, sends the collected node information to the load balancing component. The load balancing component sends the received node information to the server. The server is configured to write the received node information into a preset database. The calling component sends a data request to the server. Upon receiving the data request, the server obtains the target node information corresponding to the data request from the node information stored in the database and sends the target node information to the calling component. By using the system provided by the embodiments of the present invention, information about each resource pool node can be obtained in a timely manner.

Description

Technical Field

[0001] The present invention relates to the technical field of cloud computing, and in particular to a node information processing system and method. Background Art

[0002] With the continuous development of information technology, more and more enterprises are choosing cloud servers, which offer advantages such as convenience, stability, reliability, and cost-effectiveness, to replace local servers. Consequently, the demand for cloud servers is increasing. Currently, to ensure the stable operation of cloud servers, manual collection of information about cloud server resource pool nodes is required to assist in operation and maintenance. However, due to the large number of cloud server resource pool nodes, manual collection cannot collect information from each resource pool node in a timely manner, thus failing to effectively ensure the stable operation of cloud servers. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a node information processing system and method that can obtain the information of each resource pool node in a timely manner. The specific solution is as follows:

[0004] A node information processing system, comprising:

[0005] A server, a load balancing component, and at least one client of the calling component, each of which is deployed on a different resource pool node;

[0006] Each of the clients is configured to collect node information of the resource pool node where it is located, and upon receiving a report request from the load balancing component, send the collected node information to the load balancing component; the node information includes host information, slave information, and network information;

[0007] The load balancing component is configured to send the received node information to the server;

[0008] The server is configured to write the received node information into a preset database;

[0009] The calling component is used to send a data request to the server;

[0010] The server is configured to, upon receiving the data request, obtain target node information corresponding to the data request from each node information stored in the database, and send the target node information to the calling component.

[0011] In the above-mentioned node information processing system, optionally, the calling component is further used to:

[0012] The running status of the resource pool node to which the target node information belongs is determined based on the target node information.

[0013] In the above-mentioned node information processing system, optionally, the calling component is further used to:

[0014] When the running status of the resource pool node to which the target node information belongs indicates that the resource pool node has a cluster-out failure or a network failure occurs, an alarm message is output.

[0015] In the above-mentioned node information processing system, optionally, the server is used to:

[0016] Parsing the data request to obtain index information included in the data request;

[0017] The target node information corresponding to the data request is obtained from each node information of the database according to the index information.

[0018] In the above-mentioned node information processing system, optionally, the load balancing component is used to:

[0019] The node information is sent to the server via the User Datagram Transport Protocol (UDP).

[0020] A node information processing method is applied to a node information processing system, wherein the node information processing system includes a server, a load balancing component, a calling component, and at least one client, each of which is deployed on a different resource pool node. The method includes:

[0021] Each client collects node information of the resource pool node where it is located, and sends the collected node information to the load balancing component upon receiving a report request from the load balancing component; the node information includes host information, slave information, and network information;

[0022] The load balancing component sends the received node information to the server;

[0023] Upon receiving the node information, the server writes the node information into a preset database;

[0024] The calling component sends a data request to the server;

[0025] When receiving the data request, the server obtains target node information corresponding to the data request from each node information stored in the database, and sends the target node information to the calling component.

[0026] Optionally, in the above method, after the server sends the target node information to the calling component, the method further includes:

[0027] The calling component determines the running status of the resource pool node to which the target node information belongs based on the target node information.

[0028] Optionally, the above method further comprises, after the calling component determines the operating status of the resource pool node to which the target node information belongs based on the target node information:

[0029] When the running status of the resource pool node to which the target node information belongs indicates that the resource pool node has a cluster-out failure or a network failure occurs, an alarm message is output.

[0030] In the above method, optionally, the server is configured to:

[0031] Parsing the data request to obtain index information included in the data request;

[0032] The target node information corresponding to the data request is obtained from each node information of the database according to the index information.

[0033] In the above method, optionally, the load balancing component sends the received node information to the server, including:

[0034] The load balancing component sends the node information to the server via the User Datagram Transport Protocol (UDP).

[0035] Compared with the prior art, the embodiments of the present invention have the following advantages:

[0036] The embodiment of the present invention provides a node information processing system and method, which includes a server, a load balancing component, a calling component and at least one client, each of which is deployed on a different resource pool node; each client is used to collect node information of the resource pool node where it is located, and when receiving a report request from the load balancing component, sends the collected node information to the load balancing component; the node information includes host information, sub-machine information and network information; the load balancing component is used to send the received node information to the server; the server is used to write the node information into a preset database when receiving the node information; the calling component is used to send a data request to the server; the server is used to obtain the target node information corresponding to the data request from the node information stored in the database when receiving the data request, and send the target node information to the calling component. By applying the system provided by the embodiment of the present invention, the server can obtain the node information of each resource node in a timely manner, and when receiving a data request from the calling component, send the target node information to the calling component, which can meet the node information requirements of the calling component, thereby ensuring the operation stability of the cloud server. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0038] Figure 1 A schematic diagram of the structure of a node information processing system provided by an embodiment of the present invention;

[0039] Figure 2 A flowchart of a method for processing node information provided by an embodiment of the present invention;

[0040] Figure 3 A flowchart of another method for processing node information provided by an embodiment of the present invention;

[0041] Figure 4 A flowchart of another method for processing node information provided by an embodiment of the present invention;

[0042] Figure 5 A schematic diagram of data transmission in a node information processing system provided by an embodiment of the present invention. DETAILED DESCRIPTION

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

[0044] In this application, the terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0045] At present, in order to ensure the stable operation of cloud servers, it is necessary to manually collect information about cloud server resource pool nodes to assist in operation and maintenance. However, the number of cloud server resource pool nodes is huge, and manual collection cannot collect information about each resource pool node in a timely manner, thus failing to effectively ensure the stable operation of cloud servers.

[0046] In order to solve the problem of not being able to collect information from each resource pool node in a timely manner, in one feasible way, a global collection server is connected to each resource pool node to realize information collection. However, if each resource pool node is connected to the global collection server, it will cause a lot of network load pressure. Especially when the node scale is large, it will greatly waste the server's system and network resources, causing the system to respond too slowly. In addition, its centralized architecture determines that once a problem occurs in the global collection server, the entire system will be paralyzed.

[0047] Based on this, see Figure 1 , is a schematic diagram of the structure of a node information processing system provided by an embodiment of the present invention, the node information processing system includes:

[0048] A server 101, a load balancing component 102, a calling component 103 and a client 104, wherein the number of resource pool nodes may be n, where n is an integer greater than 1, and each client 104 is deployed on a different resource pool node;

[0049] Each of the clients 104 is used to collect node information of the resource pool node where it is located, and upon receiving a report request from the load balancing component, sends the collected node information to the load balancing component; the node information includes host information, sub-machine information and network information.

[0050] In this embodiment, the host machine information may include one or more of the cloud hard disk status, CPU basic information and status, NUMA information, local disk usage, memory usage, virtualization tools, operating system information, collection and reporting time, etc.; the sub-machine information may include one or more of the sub-machine ID, sub-machine start and stop status, collection and reporting time, etc.; the network information may include one or more of the network card status, IPv4 and IPv6 addresses, subnet masks, network card packet sending and receiving status, collection and reporting time, etc.

[0051] Optionally, the report request is used to instruct the resource pool node to send node information to the load balancing component.

[0052] The load balancing component in this embodiment can send a reporting request to each resource pool node in sequence at a preset time interval, so that the client on each resource pool node sends the collected node information to the load balancing component.

[0053] Optionally, the resource pool node may be a cloud server host, and each resource pool node may manage at least one sub-machine.

[0054] The load balancing component 102 is configured to send the received node information to the server 101 .

[0055] The server 101 is configured to write the received node information into a preset database.

[0056] In this embodiment, the database can store the node information collected by the client of each resource pool node at each collection time point. The server can be obtained by the cloud server based on the multi-copy deployment of the container. When the cloud server detects that the server has a failure, it can start the alternative server of the server and use the alternative server as the new server.

[0057] The calling component 103 is used to send a data request to the server 101.

[0058] In this embodiment, the calling component may generate a data request according to the node information requirement, and then send the data request to the server to instruct the server to feedback the target node information corresponding to the data request.

[0059] The server 101 is configured to, upon receiving the data request, obtain target node information corresponding to the data request from each node information stored in the database, and send the target node information to the calling component 103 .

[0060] In this embodiment, the calling component may monitor the resource pool node to which the target node information belongs according to the target node information.

[0061] By using the system provided by the embodiments of the present invention, the server can promptly obtain node information for each resource node. Upon receiving a data request from a calling component, the server can send the target node information to the calling component, satisfying the calling component's node information requirements and thus ensuring the operational stability of the cloud server. A load-balancing connection is employed between resource pool nodes and the server, reducing server resource usage and significantly improving network reliability.

[0062] In an embodiment provided by the present invention, based on the above solution, specifically, the calling component 103 is further used to:

[0063] The running status of the resource pool node to which the target node information belongs is determined based on the target node information.

[0064] In this embodiment, the operating status of the resource pool node can be determined based on the host information, sub-machine information and network information in the target node information. The operating status can be a normal state or a fault state. The fault state can include at least one of a cluster failure and a network failure.

[0065] In an embodiment provided by the present invention, based on the above solution, specifically, the calling component 104 is further configured to:

[0066] When the running status of the resource pool node to which the target node information belongs indicates that the resource pool node has a cluster-out failure or a network failure occurs, an alarm message is output.

[0067] In this embodiment, the alarm information may be output and displayed on a preset display interface, or the alarm information may be sent to a preset operation and maintenance object terminal so that the operation and maintenance object corresponding to the operation and maintenance object terminal processes the fault.

[0068] In an embodiment of the present invention, based on the above solution, specifically, the server is configured to:

[0069] Parsing the data request to obtain index information included in the data request;

[0070] The target node information corresponding to the data request is obtained from each node information of the database according to the index information.

[0071] In this embodiment, the index information may include the node identifier, acquisition time range, etc. of the resource pool node to be monitored. The index information can be matched with the information of each node in the database, and the node information that successfully matches the index information can be determined as the target node information corresponding to the data request.

[0072] In an embodiment provided by the present invention, based on the above solution, specifically, the load balancing component is used to:

[0073] The node information is sent to the server via the User Datagram Transport Protocol (UDP).

[0074] The embodiment of the present invention provides a node information processing method, which is applied to a node information processing system. The node information processing system includes a server, a load balancing component, a calling component and at least one client. Each of the clients is deployed in a different resource pool node. The method flow chart of the method is as follows: Figure 2 As shown, specifically including:

[0075] S201: Each client collects node information of the resource pool node where it is located, and upon receiving a report request from the load balancing component, sends the collected node information to the load balancing component; the node information includes host information, sub-machine information and network information.

[0076] S202: The load balancing component sends the received node information to the server.

[0077] S203: Upon receiving the node information, the server writes the node information into a preset database.

[0078] S204: The calling component sends a data request to the server.

[0079] S205: When receiving the data request, the server obtains target node information corresponding to the data request from each node information stored in the database, and sends the target node information to the calling component.

[0080] In an embodiment provided by the present invention, based on the above implementation process, optionally, after the server sends the target node information to the calling component, Figure 3 As shown, the method further includes the following steps:

[0081] S206: The calling component determines the running status of the resource pool node to which the target node information belongs based on the target node information.

[0082] In an embodiment of the present invention, based on the above implementation process, optionally, after the calling component determines the running status of the resource pool node to which the target node information belongs based on the target node information, Figure 4 As shown, the following steps are also included:

[0083] S207: The calling component outputs alarm information when the running status of the resource pool node to which the target node information belongs indicates that the resource pool node has a cluster-out failure or a network failure occurs.

[0084] In an embodiment of the present invention, based on the above implementation process, optionally, the process of the server obtaining the target node information corresponding to the data request from each node information stored in the database includes:

[0085] Parsing the data request to obtain index information included in the data request;

[0086] The target node information corresponding to the data request is obtained from each node information of the database according to the index information.

[0087] In an embodiment of the present invention, based on the above implementation process, optionally, the load balancing component sends the received node information to the server, including:

[0088] The load balancing component sends the node information to the server via the User Datagram Transport Protocol (UDP).

[0089] See also Figure 5 , a schematic diagram of data transmission in a node information processing system provided by an embodiment of the present invention. A client is deployed on a resource pool node, responsible for collecting and reporting information. The agent has four processes: a main process, an information collection process, a port monitoring process, and an information reporting process. The information collection process collects three types of information from resource pool nodes:

[0090] 1. Host information, including cloud hard disk status, basic CPU information and status, NUMA information, local disk usage, memory usage, virtualization tools, operating system information, and collection and reporting time.

[0091] 2. Sub-unit information, mainly including sub-unit ID, sub-unit start and stop status, collection and reporting time, etc.

[0092] 3. Network information, mainly including the status of each network card, IPv4 and IPv6 addresses, subnet mask, network card packet sending and receiving status, collection and reporting time, etc.

[0093] In this embodiment, a load balancing component is set between the client and server of the resource pool node. Each resource pool node can be used as a back-end server of the load balancing component. The node information is reported to the load balancing component through polling. The load balancing component uniformly sends the information to the server through the UDP protocol. This method avoids the delay caused by layer-by-layer reporting and greatly reduces the network load on the server. The load balancing component can be implemented through software and / or hardware.

[0094] The server uses Kubernetes container technology and is deployed in the cloud with multiple copies. The virtual address (VIP) is exposed through the service. After data is reported to the VIP, it is forwarded to the backend container via the kube-proxy proxy for processing. After receiving the data, the container first synchronizes it to the database for storage. When other components need to access the information, the container retrieves the information from the database for use. Because the server is deployed using containers, it is more lightweight than existing deployment methods. Multiple copies also ensure high availability. If a container fails, Kubernetes will restart another container to ensure normal operation of the cluster.

[0095] In this embodiment, fixed time intervals are set to collect node information from each resource pool node to determine whether the node has left the cluster or whether a network failure has occurred, thereby facilitating the administrator to quickly understand the resource pool status and handle the failure immediately.

[0096] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similarities between the various embodiments can be referred to in conjunction with each other. For device embodiments, since they are generally similar to method embodiments, their description is relatively simple, and for relevant details, reference can be made to the description of the method embodiments.

[0097] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0098] For the convenience of description, the above device is described as being divided into various units according to their functions. Of course, when implementing the present invention, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0099] From the above description of the embodiments, it can be seen that those skilled in the art can clearly understand that the present invention can be implemented by means of software plus the necessary general-purpose hardware platform. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium such as ROM / RAM, a magnetic disk, or an optical disk, and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present invention or certain parts of the embodiments.

[0100] The above is a detailed introduction to a node information processing system provided by the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core ideas. At the same time, for those skilled in the art, according to the ideas of the present invention, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A node information processing system, characterized in that: include: A server, a load balancing component, a calling component and at least one client, each of the clients being deployed on a different resource pool node; Each of the clients is configured to collect node information of the resource pool node where it is located, and upon receiving a report request from the load balancing component, send the collected node information to the load balancing component; the node information includes host information, slave information, and network information; The load balancing component is configured to send the received node information to the server; The server is configured to write the received node information into a preset database; The calling component is used to send a data request to the server; The server is configured to, upon receiving the data request, obtain target node information corresponding to the data request from each node information stored in the database, and send the target node information to the calling component; The calling component is further used to: Determining, based on the target node information, an operating status of a resource pool node to which the target node information belongs; When the running status of the resource pool node to which the target node information belongs indicates that the resource pool node has a cluster-out failure or a network failure occurs, an alarm message is output.

2. The node information processing system according to claim 1, characterized in that: The server is used to: Parsing the data request to obtain index information included in the data request; The target node information corresponding to the data request is obtained from each node information of the database according to the index information.

3. The node information processing system according to claim 1, characterized in that The load balancing component is used to: The node information is sent to the server via the User Datagram Transport Protocol (UDP).

4. A node information processing method, characterized in that: Applied to a node information processing system, the node information processing system includes a server, a load balancing component, a calling component, and at least one client, each of the clients being deployed on a different resource pool node. The method includes: Each client collects node information of the resource pool node where it is located, and sends the collected node information to the load balancing component upon receiving a report request from the load balancing component; the node information includes host information, slave information, and network information; The load balancing component sends the received node information to the server; Upon receiving the node information, the server writes the node information into a preset database; The calling component sends a data request to the server; When receiving the data request, the server obtains target node information corresponding to the data request from each node information stored in the database, and sends the target node information to the calling component; The calling component determines, based on the target node information, the running status of the resource pool node to which the target node information belongs; When the running status of the resource pool node to which the target node information belongs indicates that the resource pool node has a cluster-out failure or a network failure occurs, an alarm message is output.

5. The information processing method according to claim 4, characterized in that The process of the server obtaining the target node information corresponding to the data request from each node information stored in the database includes: Parsing the data request to obtain index information included in the data request; The target node information corresponding to the data request is obtained from each node information of the database according to the index information.

6. The method according to claim 4, characterized in that The load balancing component sends the received node information to the server, including: The load balancing component sends the node information to the server via the User Datagram Transport Protocol (UDP).

Images