Server-level computing power identification gateway

Abstract

This invention discloses a server-level computing power identification gateway, relating to the field of internet technology. It includes an Agent program, a trusted jump server link, a data collection module, a computing power identification generation module, and a data reporting module. The Agent program is deployed on the computing power enterprise's intranet server and is responsible for establishing a trusted connection with the gateway. The trusted jump server link serves as a secure channel for data transmission, ensuring that data is not stolen or tampered with during transmission. This server-level computing power identification gateway is implemented through a lightweight Agent program deployed on the computing power enterprise's intranet server. It establishes a trusted jump server link through SSH key authentication, redirecting users to other authorized servers within the enterprise. This mechanism enhances the gateway's security. Combined with automated scripts, it collects underlying resource data, aggregates and encodes the collected resource information, converts it into computing power identification, and synchronously reports it to the regional computing power identification gateway.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, specifically to a server-level computing power identification gateway. Background Technology

[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 responsible for facilitating communication and interaction between different networks. A gateway receives data packets from one network, then transforms or processes them as needed, ultimately forwarding these packets to another network.

[0003] Server-grade computing power identification gateways are gateway devices specifically designed to connect server networks to other networks. These gateways typically possess powerful data processing capabilities, rich network functions, and high security, meeting the needs of large or complex network environments. Server-grade computing power identification gateways play a critical role in server networks, responsible for important tasks such as data forwarding, protocol conversion, and security detection, ensuring the stable operation and efficient communication of the server network.

[0004] However, with the expansion of network scale and the increase in data traffic, traditional gateways face limitations in processing capacity and throughput, making it difficult to handle large amounts of data in large or complex network environments, thus affecting the overall performance of the server. Especially in large network environments, resource data collection and management is a complex and time-consuming process, and is prone to human error. Summary of the Invention

[0005] The purpose of this invention is to provide a server-level computing power identification gateway to solve the problems mentioned in the background art.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a server-level computing power identification gateway, comprising:

[0007] Agent program: Deployed on the enterprise's intranet servers, responsible for establishing a trusted connection with the gateway. Each server needs to deploy an agent, with one server serving as both the starting point and the endpoint for data aggregation. Specifically, each server in the enterprise deploys a server-level identification gateway (lightweight agent agent), with one server acting as a connection point to the regional identification gateway and other servers, essentially a jump server. Starting from this server, the agent program executes, automatically scanning the server's information, such as the number of cores, memory chip model, and network bandwidth. Based on the scanned information, it calculates information such as total computing power and total storage capacity. Static information such as the enterprise name, city, and industry is hardcoded into the program through configuration files. Finally, the information scanned by multiple servers is aggregated at the jump server for information integration, forming a computing power identifier, which is then reported to the regional identification gateway.

[0008] Trusted jump board link: As a secure channel for data transmission, it is responsible for ensuring that data is not stolen or tampered with during transmission;

[0009] Data acquisition module: Collects underlying resource data through automated scripts;

[0010] Computing power identifier generation module: responsible for summarizing and processing the collected resource data, encoding and converting the resource information, and generating computing power identifiers;

[0011] Data reporting module: Synchronously reports the encoded computing power identifier to the regional computing power identifier gateway.

[0012] Furthermore, the Agent program is designed with lightweight features, meaning it uses lightweight software to ensure minimal consumption of server resources. The program can run efficiently on the server without consuming excessive resources, and it uses SSH key authentication to establish a secure connection with the gateway, ensuring the security of communication.

[0013] Furthermore, the trusted jump host link is established through an SSH key authentication mechanism, specifically including the following steps:

[0014] Step 1: Generate an SSH key pair:

[0015] Use the ssh-keygen command on your local computer to generate a pair of SSH keys, including a private key (to keep secret) and a public key (to be shared securely).

[0016] Step 2: Deploy the public key to the jump host and the target server:

[0017] 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 host and the target server so that these servers can recognize and allow SSH connections using the corresponding private key;

[0018] Step 3: Configure the SSH client:

[0019] Edit the ~ / .ssh / config file to add configuration information about the jump host and the target server. By configuring the SSH client (in the ~ / .ssh / config file), you can simplify the process of connecting to the target server through the jump host.

[0020] Step 4: Verify the jump server link:

[0021] Try connecting to the target server using the SSH command, while specifying the jump host (if not specified in the configuration file, you may need to use the -J option or the corresponding jump host command in the command line). If you successfully connect to the target server through the jump host, ensure that the jump host link is configured correctly.

[0022] Step 5: Use an SSH proxy:

[0023] 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.

[0024] Furthermore, the data acquisition module uses Shell scripts, Python, or other programming languages ​​suitable for the server environment to write automated scripts, and the scripts contain commands for collecting resource information from various aspects such as server hardware (e.g., CPU, memory, disk, etc.) and network (e.g., IP address, network bandwidth, etc.).

[0025] Furthermore, each of the servers has an agent program that executes automated data collection scripts to collect data.

[0026] Furthermore, the computing power identifier generation module includes the following sub-modules:

[0027] Data aggregation submodule: Receives resource data from different servers and aggregates it, including operations such as merging, classifying, and sorting, merging data from multiple servers into a unified dataset;

[0028] The data processing submodule further processes the aggregated data, including data cleaning (removing invalid or erroneous data), data transformation (converting data into a format suitable for encoding and conversion, such as converting numerical data into string data, or performing unit conversion), and data compression (reducing data size to improve transmission efficiency), to ensure the accuracy, integrity, and readability of the data for subsequent generation and reporting of computing power identifiers.

[0029] Resource encoding submodule: Encodes the processed resource data according to the designed encoding rules, including the character set, length, structure, etc.

[0030] The conversion generation submodule further processes and generates computing power identifiers based on resource encoding.

[0031] Furthermore, the conversion generation submodule generates a computing power identifier based on the encoded resource data and in conjunction 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.

[0032] Furthermore, the verification includes verifying whether the format, length, character set, etc. of the computing power identifier meet expectations, and verifying the integrity of the computing power identifier through a check code (check code calculation: design a check code for the computing power identifier, calculate the check code through a specific algorithm, and attach it to the computing power identifier). Once the verification finds a problem with the computing power identifier, such as duplication or incorrect format, the corresponding error handling is immediately performed, such as regenerating the computing power identifier or recording an error log.

[0033] Furthermore, the data reporting module sends the computing power identifier to the regional computing power identifier gateway via the network, specifically through network protocols such as HTTP / HTTPS, WebSocket, and TCP / IP.

[0034] Furthermore, the data reporting module supports the following reporting strategies:

[0035] Real-time reporting: Once a new computing power identifier is generated, it is immediately reported to the regional computing power identifier gateway;

[0036] Batch reporting: In order to reduce network transmission overhead, multiple computing power identifiers are packaged and reported at once;

[0037] Error handling: If network failures or unavailability of the regional computing power identification gateway are encountered during the reporting process, appropriate error handling should be performed immediately, such as retrying or logging errors.

[0038] This invention provides a server-level computing power identification gateway, which has the following beneficial effects:

[0039] This gateway is implemented through a lightweight agent program deployed on the enterprise's intranet server, reducing the gateway's resource consumption and complexity. It can operate efficiently without affecting other major tasks of the server. It establishes a trusted jump link through SSH key authentication, redirecting users to other authorized servers of the enterprise. This mechanism enhances the gateway's security. Combined with automated scripts, it collects underlying resource data, summarizes and encodes the collected resource information, converts it into computing power identifiers, and synchronously reports it to the regional computing power identifier gateway. This achieves efficient data communication and resource sharing, which helps to optimize resource configuration and efficient utilization. Attached Figure Description

[0040] Figure 1 This is a logical block diagram of the server-level computing power identification gateway of the present invention;

[0041] Figure 2 This is a schematic diagram illustrating the steps for establishing a trusted jump board link in the server-level computing power identification gateway of the present invention.

[0042] Figure 3 This is a schematic diagram of the Agent program operation logic of the server-level computing power identification gateway of the present invention. Detailed Implementation

[0043] The embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and should not be construed as limiting the scope of the invention.

[0044] like Figures 1-3 As shown, the server-level computing power identification gateway includes:

[0045] Agent program: Deployed on the enterprise's intranet servers, responsible for establishing a trusted connection with the gateway. Each server needs to deploy an agent, with one server serving as both the starting point and the endpoint for data aggregation. Each server has an agent program that executes automated data collection scripts to achieve data collection. Specifically, each server in the enterprise deploys a server-level identification gateway (lightweight agent). One server acts as a connection point to the regional identification gateway and other servers, essentially a jump server. Starting from this server, the agent program executes, automatically scanning the server's information, such as the number of cores, memory chip model, and network bandwidth. Based on the scanned information, it calculates information such as total computing power and total storage capacity. Static information such as enterprise name, city, and industry is hardcoded into the program through configuration files. Finally, the information scanned by multiple servers is aggregated at the jump server for information integration, forming a computing power identifier, which is then reported to the regional identification gateway. The general process is as follows. Figure 3As shown. In this embodiment, the Agent program adopts a lightweight design, that is, it is written as a lightweight software program to ensure minimal consumption of server resources. The program can run efficiently on the server without consuming too many resources, and at the same time, it uses SSH key authentication to establish a secure connection with the gateway to ensure the security of communication.

[0046] Trusted jump server link: Serving 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 jump server link is established through an SSH key authentication mechanism, specifically including the following steps:

[0047] Step 1: Generate an SSH key pair:

[0048] Use the ssh-keygen command on your local computer to generate a pair of SSH keys, including a private key (to keep secret) and a public key (to be shared securely).

[0049] Step 2: Deploy the public key to the jump host and the target server:

[0050] 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 host and the target server so that these servers can recognize and allow SSH connections using the corresponding private key;

[0051] Step 3: Configure the SSH client:

[0052] Edit the ~ / .ssh / config file to add configuration information about the jump host and the target server. By configuring the SSH client (in the ~ / .ssh / config file), you can simplify the process of connecting to the target server through the jump host.

[0053] Step 4: Verify the jump server link:

[0054] Try connecting to the target server using the SSH command, while specifying the jump host (if not specified in the configuration file, you may need to use the -J option or the corresponding jump host command in the command line). If you successfully connect to the target server through the jump host, ensure that the jump host link is configured correctly.

[0055] Step 5: Use an SSH proxy:

[0056] 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.

[0057] Data Acquisition Module: This module collects underlying resource data through automated scripts. In practice, it uses Shell scripts, Python, or other programming languages ​​suitable for server environments to write automated scripts. These scripts contain commands for collecting resource information from various aspects of the server, such as hardware (e.g., CPU, memory, disk) and network (e.g., IP address, network bandwidth).

[0058] Computing power identifier generation module: This module is responsible for summarizing and processing the collected resource data, encoding and converting the resource information, and generating computing power identifiers. This module includes the following sub-modules:

[0059] Data aggregation submodule: Receives resource data from different servers and aggregates it, including operations such as merging, classifying, and sorting, merging data from multiple servers into a unified dataset;

[0060] The data processing submodule further processes the aggregated data, including data cleaning (removing invalid or erroneous data), data transformation (converting data into a format suitable for encoding and conversion, such as converting numerical data into string data, or performing unit conversion), and data compression (reducing data size to improve transmission efficiency), to ensure the accuracy, integrity, and readability of the data for subsequent generation and reporting of computing power identifiers.

[0061] Resource encoding submodule: Encodes the processed resource data according to the designed encoding rules, including the character set, length, structure, etc.

[0062] The conversion and generation submodule further processes and generates computing power identifiers based on the resource encoding. In this embodiment, the conversion and generation submodule generates computing power identifiers (the computing power identifier should uniquely identify the corresponding resource information and facilitate subsequent management and scheduling) based on the encoded resource data and a specific algorithm or logic. It then verifies the generated computing power identifiers to ensure their validity and correctness. Verification includes checking whether the format, length, and character set of the computing power identifier meet expectations, and verifying the integrity of the computing power identifier through a checksum (checksum calculation: designing a checksum for the computing power identifier, calculating the checksum using 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 incorrect format, appropriate error handling is immediately performed, such as regenerating the computing power identifier or recording an error log.

[0063] 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 network protocols such as HTTP / HTTPS, WebSocket, and TCP / IP, and supports the following reporting strategies:

[0064] Real-time reporting: Once a new computing power identifier is generated, it is immediately reported to the regional computing power identifier gateway;

[0065] Batch reporting: In order to reduce network transmission overhead, multiple computing power identifiers are packaged and reported at once;

[0066] Error handling: If network failures or unavailability of the regional computing power identification gateway are encountered during the reporting process, appropriate error handling should be performed immediately, such as retrying or logging errors.

[0067] In summary, the lightweight Agent program deployed on the internal network server of the computing power enterprise by this server-level computing power identification gateway establishes a trusted jump link through SSH key authentication, jumps to log in to other servers authorized by the enterprise, realizes the collection of underlying resource data through automated scripts, summarizes and encodes the collected resource information, converts it into computing power identification, and synchronously reports it to the regional computing power identification gateway.

[0068] The embodiments of the present invention are given for illustrative and descriptive purposes only, and are not intended to be exhaustive or to limit the invention to the forms disclosed. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described in order to better illustrate the principles and practical application of the invention, and to enable those skilled in the art to understand the invention and to design various embodiments with various modifications suitable for a particular purpose.

Claims

1. A server-level computing power identification gateway, characterized in that, This includes an Agent program, a trusted jump board link, a data acquisition module, a computing power identifier generation module, and a data reporting module; The Agent program is deployed on the internal network server of the computing power enterprise and is responsible for establishing a trusted connection with the gateway. Each server needs to deploy the agent, with one server serving as both the starting point and the endpoint for data aggregation. The trusted jump board link serves as a secure channel for data transmission, 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 identifier generation module is responsible for summarizing and processing the collected resource data, encoding and converting the resource information, and generating computing power identifiers. The data reporting module synchronously reports the encoded computing power identifier to the regional computing power identifier gateway; The Agent program is designed with lightweight features, meaning it uses lightweight software to ensure minimal consumption of server resources, while using SSH key authentication to establish a secure connection with the gateway. The trusted jump host link is established through an 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 host and the target server: Copy the generated public key to the 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, and simplify the process of connecting to the target server through the jump server by configuring the SSH client; Step 4: Verify the jump server link: Try connecting to the target server using the SSH command, while specifying the jump server. If you successfully connect to the target server through the jump server, ensure that the jump server link is configured correctly. Step 5: Use an SSH proxy: Start the SSH agent and add your private key to the agent. Using the SSH agent simplifies the process of managing multiple private keys and connections.

2. The server-level computing power identification gateway according to claim 1, characterized in that, The data acquisition module uses Shell scripts and Python to write automated scripts, and the scripts contain commands for collecting resource information on server hardware and network aspects.

3. The server-level computing power identification gateway according to claim 1, characterized in that, Each of the servers has an agent program that executes automated data collection scripts to collect data.

4. The server-level computing power identification gateway according to claim 1, characterized in that, The computing power identifier generation module includes the following sub-modules: Data aggregation submodule: Receives resource data from different servers and aggregates it, including merging, classifying, and sorting operations, merging data from multiple servers into a unified dataset; Data processing submodule: performs further processing on the aggregated data, including data cleaning, data transformation, and data compression; Resource encoding submodule: Encodes the processed resource data according to the designed encoding rules, which include the character set, length, and structure of the encoding. The conversion generation submodule further processes and generates computing power identifiers based on resource encoding.

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

6. The server-level computing power identification gateway according to claim 5, characterized in that, The verification includes verifying whether the format, length, and character set of the computing power identifier meet expectations, and verifying the integrity of the computing power identifier through a checksum. Once the verification finds a problem with the computing power identifier, the corresponding error handling is immediately performed.

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

8. 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 identifier is generated, it is immediately reported to the regional computing power identifier gateway; Batch reporting: In order to reduce network transmission overhead, multiple computing power identifiers are packaged and reported at once; Error handling: If any abnormal situation is encountered during the reporting process, the corresponding error handling shall be carried out immediately.

Images