Server-level computing power identification gateway

Abstract

The invention discloses a server-level computing power identification gateway, which relates to the technical field of Internet, and comprises an Agent agent program, a trusted springboard link, a data acquisition module, a computing power identification generation module and a data reporting module, the Agent agent program is deployed on a computing power enterprise intranet server and is responsible for establishing trusted connection with the gateway; and the trusted springboard link is used as a secure channel for data transmission and is responsible for ensuring that the data is not stolen or tampered in a transmission process. The server-level computing power identification gateway is realized through a lightweight Agent agent program deployed by an internal network server of a computing power enterprise, a trusted springboard link is established through SSH key authentication, and other servers authorized by the enterprise are skipped and logged in, so that the security of the gateway is enhanced through the mechanism, and bottom-layer resource data acquisition is realized in combination with an automatic script; and performing data summarization and resource coding on the acquired resource information, converting the resource information into a computing power identifier, and synchronously reporting the computing power identifier to a regional computing power identifier gateway.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a server-level computing power identification gateway. Background Art

[0002] A gateway is a network device or software used to connect two different networks or protocols and enable data exchange between them. It is a crucial component of network architecture, primarily enabling communication and interaction between different networks. A gateway receives data packets from one network, converts or processes them as needed, and ultimately forwards them to another network.

[0003] A server-level computing power identification gateway is a gateway device specifically designed to connect server networks with other networks. These gateways typically feature powerful data processing capabilities, rich network functionality, and a high level of security, meeting the needs of large or complex network environments. A server-level computing power identification gateway plays a key role in server networks, responsible for important tasks such as data forwarding, protocol conversion, and security testing, ensuring stable operation and efficient communication within the server network.

[0004] However, as networks expand and data traffic increases, traditional gateways face limitations in processing power and throughput. This makes them unable to effectively handle the large amounts of data in large or complex network environments, thus impacting overall server performance. In large-scale networks, data collection and management of resources is a complex and time-consuming process, prone to manual errors. Summary of the Invention

[0005] The purpose of the present invention is to provide a server-level computing power identification gateway to solve the problems raised in the above background technology.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a server-level computing power identification gateway, comprising: Agent program: Deployed on the computing power enterprise intranet server, it is responsible for establishing a trusted connection with the gateway. Each server needs to deploy an agent, one of which serves as the starting point and the end point for data aggregation. Specifically, a server-level identification gateway (lightweight agent) is deployed on each server in the enterprise. One of the servers serves as the connection point with the regional identification gateway and other servers, which is equivalent to a jump server. Starting from this server, the agent program is executed, which automatically scans the information of this server, such as the number of cores, memory chip model, and network bandwidth. Then, based on the scanned information, it calculates information such as the total computing capacity and total storage capacity. Static information such as the company name, city, and industry is hard-coded in the program through the configuration file. Finally, the information scanned by multiple servers is aggregated to the jump server for information integration, integrated into the computing power identification, and then reported to the regional identification gateway. Trusted springboard link: As a secure channel for data transmission, it is responsible for ensuring that data is not stolen or tampered with during transmission; Data collection module: collects underlying resource data through automated scripts; Computing power identification generation module: responsible for summarizing and processing the collected resource data, encoding and converting the resource information, and generating a computing power identification; Data reporting module: Synchronously reports the encoded computing power identification to the regional computing power identification gateway.

[0007] Furthermore, the Agent program is designed to be lightweight, that is, a lightweight software program is written to ensure minimal consumption of server resources. The program can run efficiently on the server without taking up too many resources, and at the same time use SSH key authentication to establish a secure connection with the gateway to ensure the security of communication.

[0008] Furthermore, the trusted springboard link is established through the SSH key authentication mechanism, specifically including the following steps: Step 1. Generate an SSH key pair: Use the ssh-keygen command on your local computer to generate a pair of SSH keys, including a private key (keep it secret) and a public key (which can be shared safely); Step 2: Deploy the public key to the jump server and target server: Use the ssh-copy-id command or manually copy the public key to copy the generated public key to the ~ / .ssh / authorized_keys file on the jump server and the target server so that these servers can recognize and allow SSH connections using the corresponding private key; Step 3. Configure the SSH client: Edit the ~ / .ssh / config file and add configuration information about the jump server and the target server. By configuring the SSH client (in the ~ / .ssh / config file), it is easier to connect to the target server through the jump server. Step 4: Verify the jumper link: Use the SSH command to try to connect to the target server, specifying the jump server (if not specified in the configuration file, you may need to use the -J option or the corresponding jump server directive in the command line). Successfully connect to the target server through the jump server to ensure that the jump server link is configured correctly. Step 5. Use SSH agent: Start an SSH agent and add your private key to the agent. Using an SSH agent (such as ssh-agent) simplifies the process of managing multiple private keys and connections.

[0009] Furthermore, the data collection module uses Shell script, Python or other programming languages suitable for the server environment to write automated scripts, and the scripts contain collection commands for various resource information such as server hardware (such as CPU, memory, disk, etc.) and network (such as IP address, network bandwidth, etc.).

[0010] Furthermore, each of the servers has an agent program, and the agent executes an automated collection script to achieve data collection.

[0011] Furthermore, the computing power identification generation module includes the following submodules: Data aggregation submodule: Receives resource data from different servers and aggregates them, including merging, sorting, and other operations, to merge data from multiple servers into a unified data set; Data processing submodule: Further processing of the aggregated data, including data cleaning (removing invalid or erroneous data), data conversion (converting data into a format suitable for encoding and conversion, such as converting numeric data into string data, or performing unit conversion), and data compression (reducing data size to improve transmission efficiency), etc., to ensure the accuracy, completeness, and readability of the data, so as to facilitate the subsequent generation and reporting of computing power identification; Resource encoding submodule: encodes the processed resource data according to the designed encoding rules. The encoding rules include the encoding character set, length, structure, etc. Conversion and generation submodule: Based on the resource encoding, further processing is performed to generate computing power identification.

[0012] Furthermore, the conversion generation submodule generates a computing power identifier based on the encoded resource data in combination with a specific algorithm or logic (the computing power identifier should be able to uniquely identify the corresponding resource information and facilitate subsequent management and scheduling), and verifies the generated computing power identifier to ensure its validity and correctness.

[0013] Furthermore, the verification includes verifying whether the format, length, character set, etc. of the computing power identifier are in line with expectations, and verifying the integrity of the computing power identifier through a check code (check code calculation: designing a check code for the computing power identifier, calculating the check code through a specific algorithm, and attaching it to the computing power identifier). Once the verification finds that there is a problem with the computing power identifier, such as duplication, format error, etc., corresponding error handling is immediately performed, such as regenerating the computing power identifier, recording error logs, etc.

[0014] Furthermore, the data reporting module sends the computing power identification to the regional computing power identification gateway through the network, which is specifically implemented through network protocols such as HTTP / HTTPS protocol, WebSocket, TCP / IP, etc.

[0015] Furthermore, the data reporting module supports the following reporting strategies: Real-time reporting: Once a new computing power ID is generated, it will be immediately reported to the regional computing power ID gateway; Batch reporting: To reduce network transmission overhead, multiple computing power identifiers are packaged and reported at once; Error handling: During the reporting process, if there are any abnormal situations such as network failure or unavailability of the regional computing power identification gateway, immediately perform corresponding error handling, such as retrying and recording error logs.

[0016] The present invention provides a server-level computing power identification gateway, which has the following beneficial effects: This gateway is implemented through a lightweight Agent program deployed on the computing power enterprise intranet server, which reduces the resource consumption and complexity of the gateway itself and can run efficiently without affecting other main tasks of the server. It establishes a trusted springboard link through SSH key authentication and jumps to log in to other servers authorized by the enterprise. This mechanism enhances the security of the gateway and combines with automated scripts to realize the underlying resource data collection. The collected resource information is aggregated and encoded, converted into computing power identification and synchronously reported to the regional computing power identification gateway, realizing efficient data communication and resource sharing, which helps to achieve optimal allocation and efficient utilization of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a logical block diagram of the server-level computing power identification gateway of the present invention; Figure 2A schematic diagram of the steps for establishing a trusted springboard link for the server-level computing power identification gateway of the present invention; Figure 3 This is a logical diagram of the Agent program running on the server-level computing power identification gateway of the present invention. DETAILED DESCRIPTION

[0018] The following embodiments of the present invention are described in further detail with reference to the accompanying drawings and examples. The following examples are used to illustrate the present invention but are not intended to limit the scope of the present invention.

[0019] like Figure 1-Figure 3 As shown, the server-level computing power identification gateway includes: Agent program: deployed on the computing power enterprise intranet server, responsible for establishing a trusted connection with the gateway. Each server needs to deploy an agent, one of which serves as the starting point and the end point for data aggregation. Each server has an agent program, and the agent executes the automated collection script to realize data collection. Specifically, a server-level identification gateway (lightweight agent) is deployed on each server in the enterprise, and one of the servers serves as a connection point with the regional identification gateway and other servers, which is equivalent to a jump server; starting from this server, the agent program is executed, which automatically scans the information of this server, such as the number of cores, memory chip model, network bandwidth, and then calculates information such as the total computing capacity and total storage capacity based on the scanned information. Static information such as company name, city, and industry is hard-coded in the program through the configuration file; finally, the information scanned by multiple servers is aggregated to the jump server for information integration, integrated into a computing power identification, and then reported to the regional identification gateway. The general process is as follows: Figure 3 In this embodiment, the Agent program is designed to be lightweight, i.e., a lightweight software program is written to ensure minimal consumption of server resources. The program can run efficiently on the server without occupying too many resources. At the same time, SSH key authentication is used to establish a secure connection with the gateway to ensure communication security.

[0020] Trusted springboard link: As a secure channel for data transmission, it is responsible for ensuring that data is not stolen or tampered with during transmission. In this embodiment, the trusted springboard link is established through the SSH key authentication mechanism, which specifically includes the following steps: Step 1. Generate an SSH key pair: Use the ssh-keygen command on your local computer to generate a pair of SSH keys, including a private key (keep it secret) and a public key (which can be shared safely); Step 2: Deploy the public key to the jump server and target server: Use the ssh-copy-id command or manually copy the public key to copy the generated public key to the ~ / .ssh / authorized_keys file on the jump server and the target server so that these servers can recognize and allow SSH connections using the corresponding private key; Step 3. Configure the SSH client: Edit the ~ / .ssh / config file and add configuration information about the jump server and the target server. By configuring the SSH client (in the ~ / .ssh / config file), it is easier to connect to the target server through the jump server. Step 4: Verify the jumper link: Use the SSH command to try to connect to the target server, specifying the jump server (if not specified in the configuration file, you may need to use the -J option or the corresponding jump server directive in the command line). Successfully connect to the target server through the jump server to ensure that the jump server link is configured correctly. Step 5. Use SSH agent: Start an SSH agent and add your private key to the agent. Using an SSH agent (such as ssh-agent) simplifies the process of managing multiple private keys and connections. Data Collection Module: This module collects underlying resource data through automated scripts. In practice, this module uses Shell scripts, Python, or other programming languages suitable for server environments to write automated scripts. These scripts contain commands for collecting resource information on various aspects of the server, including hardware (such as CPU, memory, and disk) and network (such as IP addresses and network bandwidth).

[0021] Computing power identification generation module: This module is responsible for summarizing and processing the collected resource data, encoding and converting the resource information, and generating a computing power identification. This module includes the following submodules: Data aggregation submodule: Receives resource data from different servers and aggregates them, including merging, sorting, and other operations, to merge data from multiple servers into a unified data set; Data processing submodule: Further processing of the aggregated data, including data cleaning (removing invalid or erroneous data), data conversion (converting data into a format suitable for encoding and conversion, such as converting numeric data into string data, or performing unit conversion), and data compression (reducing data size to improve transmission efficiency), etc., to ensure the accuracy, completeness, and readability of the data, so as to facilitate the subsequent generation and reporting of computing power identification; Resource encoding submodule: encodes the processed resource data according to the designed encoding rules. The encoding rules include the encoding character set, length, structure, etc. Conversion and Generation Submodule: Based on the resource encoding, further processing is performed to generate a computing power identifier. In this embodiment, the conversion and generation submodule generates a computing power identifier based on the encoded resource data in combination with a specific algorithm or logic (the computing power identifier should be able to uniquely identify the corresponding resource information and facilitate subsequent management and scheduling), and verifies the generated computing power identifier to ensure its validity and correctness. Among them, the verification includes verifying whether the format, length, character set, etc. of the computing power identifier meet the expectations, and verifying the integrity of the computing power identifier through a check code (check code calculation: designing a check code for the computing power identifier, calculating the check code through a specific algorithm, and attaching it to the computing power identifier). If the verification finds a problem with the computing power identifier, such as duplication or format error, the corresponding error handling is immediately performed, such as regenerating the computing power identifier and recording an error log.

[0022] Data reporting module: Synchronously reports the encoded computing power identifier to the regional computing power identifier gateway. This module sends the computing power identifier to the regional computing power identifier gateway via the network, specifically through HTTP / HTTPS, WebSocket, TCP / IP and other network protocols, and supports the following reporting strategies: Real-time reporting: Once a new computing power ID is generated, it will be immediately reported to the regional computing power ID gateway; Batch reporting: To reduce network transmission overhead, multiple computing power identifiers are packaged and reported at once; Error handling: During the reporting process, if there are any abnormal situations such as network failure or unavailability of the regional computing power identification gateway, immediately perform corresponding error handling, such as retrying and recording error logs.

[0023] In summary, the server-level computing power identification gateway is a lightweight agent program deployed on the computing power enterprise intranet server. It establishes a trusted springboard link through SSH key authentication, jumps to log in to other servers authorized by the enterprise, and realizes the underlying resource data collection through automated scripts. The collected resource information is aggregated and encoded, converted into computing power identification and synchronously reported to the regional computing power identification gateway.

[0024] The embodiments of the present invention are presented for purposes of illustration and description and are not intended to be exhaustive or to limit the invention to the disclosed forms. Many modifications and variations will be apparent to those skilled in the art. The embodiments are chosen and described in order to better illustrate the principles of the invention and its practical application and to enable those skilled in the art to understand the invention and design various embodiments with various modifications as suited for specific applications.

Claims

1. Server-level computing power identification gateway, characterized by: It includes Agent program, trusted springboard link, data collection module, computing power identification generation module and data reporting module; The agent program is deployed on the computing power enterprise intranet server and is responsible for establishing a trusted connection with the gateway. Each server needs to deploy an agent, one of which serves as the starting point and the end point for data aggregation; The trusted springboard link serves as a secure channel for data transmission and is responsible for ensuring that data is not stolen or tampered with during transmission; The data acquisition module collects underlying resource data through automated scripts; The computing power identification generation module is responsible for summarizing and processing the collected resource data, encoding and converting the resource information, and generating a computing power identification; The data reporting module synchronously reports the encoded computing power identification to the regional computing power identification gateway.

2. The server-level computing power identification gateway according to claim 1, characterized in that: The Agent program is designed to be lightweight, that is, a lightweight software program is written to ensure minimum consumption of server resources, and at the same time uses SSH key authentication to establish a secure connection with the gateway.

3. The server-level computing power identification gateway according to claim 1, characterized in that The trusted springboard link is established through the SSH key authentication mechanism, specifically including the following steps: Step 1. Generate an SSH key pair: Generate a pair of SSH keys on your local computer, including a private key and a public key; Step 2: Deploy the public key to the jump server and target server: Copy the generated public key to files on the jump server and the target server so that these servers can recognize and allow SSH connections using the corresponding private key; Step 3. Configure the SSH client: Edit the file to add configuration information about the jump server and the target server. Configure the SSH client to simplify the process of connecting to the target server through the jump server. Step 4: Verify the jumper link: Use the SSH command to try to connect to the target server and specify a jump server. Successfully connect to the target server through the jump server to ensure that the jump server link is configured correctly. Step 5. Use SSH agent: Start the SSH agent and add the private key to the agent. Using the SSH agent simplifies the process of managing multiple private keys and connections.

4. The server-level computing power identification gateway according to claim 1, characterized in that: The data collection module uses Shell scripts and Python to write automation scripts, and the scripts contain collection commands for server hardware and network resource information of various aspects.

5. The server-level computing power identification gateway according to claim 1, characterized in that: Each of the servers has an agent program, which executes the automated collection script to realize data collection.

6. The server-level computing power identification gateway according to claim 1, characterized in that: The computing power identification generation module includes the following submodules: Data aggregation submodule: Receives resource data from different servers and aggregates them, including merging, sorting, and sorting operations, to merge data from multiple servers into a unified data set; Data processing submodule: further processes the aggregated data, including data cleaning, data conversion, and data compression; Resource encoding submodule: encodes the processed resource data according to the designed encoding rules. The encoding rules include the encoding character set, length, and structure; Conversion and generation submodule: Based on the resource encoding, further processing is performed to generate computing power identification.

7. The server-level computing power identification gateway according to claim 6, characterized in that: The conversion and generation submodule generates a computing power identifier based on the encoded resource data in combination with a specific algorithm or logic, and verifies the generated computing power identifier.

8. The server-level computing power identification gateway according to claim 7, characterized in that: The verification includes verifying whether the format, length, and character set of the computing power identifier are as expected, and verifying the integrity of the computing power identifier through a check code. Once the verification finds that there is a problem with the computing power identifier, corresponding error handling is immediately performed.

9. The server-level computing power identification gateway according to claim 1, characterized in that: The data reporting module sends the computing power identification to the regional computing power identification gateway through the network, specifically through network protocols such as HTTP / HTTPS protocol, WebSocket, and TCP / IP.

10. The server-level computing power identification gateway according to claim 1, characterized in that: The data reporting module supports the following reporting strategies: Real-time reporting: Once a new computing power ID is generated, it will be immediately reported to the regional computing power ID gateway; Batch reporting: To reduce network transmission overhead, multiple computing power identifiers are packaged and reported at once; Error handling: During the reporting process, if any abnormal situation occurs, the corresponding error handling will be carried out immediately.

Images