A cloud nest cluster remote control system

Abstract

This invention discloses a cloud-based remote control system for clusters, comprising: a cluster creation module for creating clusters in the cloud console; a cloud agent module for communicating with resources in the cloud and collecting cluster status information; a cluster connection module for connecting to a specific cluster; a cluster status viewing module for viewing cluster status information; a stateful service management module for managing stateful services in the cluster through the cloud console or command-line tools; a cluster remote control module for remotely executing commands, uploading files, and restarting services; and a monitoring and logging module for collecting cluster monitoring metrics and log information. This invention offers advantages such as unified management, flexible remote control, real-time monitoring and log display, automation and standardization, cross-platform compatibility, and scalability, providing users with a convenient and efficient cluster management and operation experience.

Description

Technical Field

[0001] This invention relates to the field of vehicle inspection technology, and in particular to a cloud-based remote control system for clusters. Background Technology

[0002] CloudNest is a cloud-native architecture based on Kubernetes, enabling unified management of stateful services such as databases and middleware. Based on CloudNest, it achieves unified software architecture and development and operation technology stacks, as well as unified public cloud / private cloud / distributed architecture, enabling one-time access and multi-environment operation, maximizing cost reduction and efficiency, and realizing the best platform and solution for cloud-native stateful services. However, existing remote control systems based on CloudNest clusters are extremely inefficient. Summary of the Invention

[0003] To address the above problems, this invention provides a cloud-nest cluster remote control system.

[0004] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0005] A cloud-nesting cluster remote control system, comprising: a cloud-nesting cluster remote control system, characterized in that it includes:

[0006] Cluster creation module: Used to create clusters in the CloudNest console and provide the required configuration parameters. CloudNest will automatically create the corresponding resources on the cloud based on the parameters.

[0007] Cloud Nest Agent Module: Used to communicate with resources in the cloud, collect cluster status information, and execute user operation commands;

[0008] Cluster connection module: used to connect to a specific cluster;

[0009] Cluster status viewing module: Used to view cluster status information;

[0010] Stateful service management module: Manage stateful services in the cluster through the CloudNest console or command-line tools;

[0011] Cluster remote control module: used for remotely executing commands, uploading files, and restarting services;

[0012] Monitoring and logging module: CloudNest collects monitoring metrics and log information of the cluster and displays them in the console. Users can view the cluster's operating status and performance metrics in real time to troubleshoot and optimize performance.

[0013] Furthermore: the cluster creation module includes:

[0014] Users select the option to create a cluster in the CloudNest console and provide the required configuration parameters, which can be provided through form input or configuration file.

[0015] After receiving the configuration parameters provided by the user, the CloudNest console passes the parameters to the underlying cluster management system.

[0016] The cluster management system automatically creates the corresponding resources in the cloud based on the received parameters;

[0017] The cluster management system configures and deploys the necessary components for the cluster's master node;

[0018] Once the master node is configured, the cluster management system will create a certain number of worker nodes. These nodes will be used to run containerized applications and services. The worker nodes will automatically join the cluster and establish communication and coordination with the master node.

[0019] During the cluster creation process, the cluster management system monitors the creation and configuration of resources to ensure that all components and nodes of the cluster are successfully created and running.

[0020] Once the cluster is created, the cluster management system will return a success message to the CloudNest console, where users can view the status and related information of the newly created cluster.

[0021] Furthermore: the CloudNest agent module includes:

[0022] After the cluster is created, the cluster management system automatically deploys a Cloud Nest agent for each node in the cluster based on the configuration and requirements.

[0023] The Cloud Nest agent runs as a container on each cluster node, or directly on the host operating system;

[0024] Before deploying the Cloud Nest agent, the cluster management system generates a unique identifier and key for each node to communicate and authenticate securely with the Cloud Nest agent;

[0025] The cluster management system distributes the installation package or container image of the Cloud Nest agent to each node and starts the agent program. The Cloud Nest agent automatically registers with the control plane of the cluster management system and establishes a communication channel with the cluster management system.

[0026] Once the Cloud Nest agent starts up and connects to the cluster management system, the agent begins to perform its duties, including communicating with resources in the cloud, collecting cluster status information, and sending the information to the cluster management system.

[0027] The CloudNest agent is also responsible for executing user commands. When a user sends a command in the CloudNest console or through a command-line tool, the CloudNest agent receives and parses the command and executes it on the corresponding node.

[0028] Furthermore: the cluster connection module includes:

[0029] Users can install the command-line tools provided by CloudNest or use the corresponding APIs in their local environment;

[0030] Users can establish a connection by specifying the cluster name and credentials using command-line tools or APIs in programming languages;

[0031] When a user specifies a cluster name, the CloudNest command-line tool or API will determine the location and related parameters of the cluster to be connected through the configuration information in the CloudNest console or configuration file.

[0032] The CloudNest command-line tool or API will send a connection request to the CloudNest agent module and provide the required credentials for authentication;

[0033] After receiving a connection request, the CloudNest proxy module verifies the user's credentials to confirm their identity. If the credentials are verified, the CloudNest proxy module will establish a connection with the user's local environment and return a success response.

[0034] Once the connection is successfully established, users can interact with the cluster through the CloudNest command-line tool or API;

[0035] The connection remains open, and the user continues to interact with the cluster for the duration of the connection until the user actively disconnects or the connection times out.

[0036] Furthermore: the cluster status viewing module includes:

[0037] After connecting to the cluster, users can use the command-line tools or APIs provided by CloudNest to obtain cluster status information.

[0038] Users can send requests to the CloudNest agent module using command-line tools or specific commands or interfaces in the API to request cluster status information;

[0039] After receiving the request, the CloudNest proxy module queries and summarizes the status information of each component and node in the cluster.

[0040] The CloudNest agent module will return the aggregated cluster status information to the user's local environment, which can be the output of command-line tools or the response of APIs.

[0041] Users can view cluster status information in their local environment. CloudNest will update the cluster status information in real time and display it accordingly based on user requests;

[0042] Cluster status information includes the number of nodes, node health status, resource utilization, and load status. The information is displayed in tabular form in the console or terminal for easy viewing and analysis by users.

[0043] Real-time updates to cluster status information are achieved by the CloudNest agent module periodically collecting information from components and nodes in the cluster and updating it to the cluster status storage.

[0044] Users can obtain real-time and historical status information about the cluster by periodically querying the cluster status information or by using the monitoring and alarm functions provided by CloudNest.

[0045] Furthermore: the stateful service management module includes:

[0046] Users connect to the target cluster using the console or command-line tools provided by CloudNest;

[0047] Users can use the command-line tools or APIs provided by CloudNest to perform management operations on stateful services by specifying commands or interfaces;

[0048] Users can perform specific management operations by entering corresponding commands through command-line tools or by sending corresponding requests through the API;

[0049] The CloudNest console or command-line tool sends the user's operation request to the CloudNest agent module; after receiving the user's operation request, the CloudNest agent module parses the request and executes the corresponding operation.

[0050] After completing the user's management operations, the CloudNest agent module will return the execution results to the CloudNest console or command-line tool, and the user can view the execution results and related information.

[0051] Furthermore: the cluster remote control module includes:

[0052] Users connect to the target cluster using the console or command-line tools provided by CloudNest;

[0053] Users can send specific remote control commands or requests through the command-line tools or APIs provided by CloudNest to specify the operations to be performed;

[0054] The CloudNest console or command-line tool sends the user's remote control request to the CloudNest agent module;

[0055] After receiving a remote control request, the CloudNest agent module parses the request and forwards it to the corresponding cluster node;

[0056] On the cluster nodes, the CloudNest agent module executes remote operations specified by the user;

[0057] After executing the user's remote control operation, the CloudNest agent module will return the execution result to the CloudNest console or command-line tool, and the user can view the execution result and related information.

[0058] Furthermore: the monitoring and logging module includes:

[0059] The CloudNest agent module periodically collects monitoring metrics and log information from the cluster, including application logs and system logs.

[0060] The CloudNest agent module sends the collected monitoring metrics and log information to the cluster state storage or log storage;

[0061] Cluster state storage or log storage processes and stores the collected data for subsequent querying and analysis;

[0062] The CloudNest console retrieves data from cluster state storage or log storage and displays it to users.

[0063] The technological advancements achieved by this invention compared to existing technologies are as follows:

[0064] CloudNest provides a one-stop cloud-native stateful service management platform that integrates cluster management, service management, remote control, monitoring, and logging. This allows users to complete various management and operational tasks through a unified platform, simplifying management complexity.

[0065] With CloudNest's remote control capabilities, users can manage and operate the cluster remotely from any location via command-line tools or API. This flexibility allows users to easily manage the cluster, whether in the office, at home, or on the go.

[0066] CloudNest provides real-time monitoring and log display capabilities, allowing users to view cluster status information, performance metrics, and application logs in real time. This helps in quickly identifying problems, troubleshooting, and optimizing performance, thereby improving cluster stability and performance.

[0067] CloudNest's cluster remote control method supports automated deployment and operation, enabling scripted operation processes via command-line tools or APIs. Furthermore, CloudNest provides standardized configuration and management methods to ensure cluster consistency and maintainability.

[0068] CloudNest's remote control method is applicable to various cloud platforms and cluster management systems, exhibiting good cross-platform compatibility and scalability. This means users can utilize similar management and operation methods across different cloud environments and clusters, enhancing flexibility and portability.

[0069] The cloud-based remote cluster control method simplifies cluster management and operation processes, improving work efficiency. Simultaneously, real-time monitoring and log display enable rapid problem identification and performance optimization, reducing the time and cost of troubleshooting and optimization.

[0070] In summary, the cloud-based cluster remote control system has advantages such as unified management, flexible remote control, real-time monitoring and log display, automation and standardization, cross-platform compatibility and scalability, providing users with a convenient and efficient cluster management and operation experience. Attached Figure Description

[0071] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used together with the embodiments of the invention to explain the invention and do not constitute a limitation thereof.

[0072] In the attached diagram:

[0073] Figure 1 This is a system structure diagram of the present invention. Detailed Implementation

[0074] The following specific embodiments are combined with each other. Concepts or processes that are the same or similar may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0075] like Figure 1 As shown, a cloud-nest cluster remote control system includes:

[0076] Cluster Creation Module: In the CloudNest console, users can create a new cluster, providing the necessary configuration parameters such as cluster name, region, and virtual machine type. CloudNest will automatically create the corresponding resources in the cloud based on these parameters.

[0077] CloudNest Proxy Module: After a cluster is created, CloudNest will automatically deploy the CloudNest Proxy for that cluster. The CloudNest Proxy is a lightweight software component responsible for communicating with resources in the cloud, collecting cluster status information, and executing user commands.

[0078] Cluster connection module: Users can use the command-line tools or API provided by CloudNest to connect to a specific cluster by specifying the cluster name and credentials.

[0079] Cluster Status Viewing Module: Once connected to the cluster, users can view cluster status information, including the number of nodes, health status, load, etc. CloudNest will update this information in real time and display it in the console.

[0080] Stateful Service Management Module: Through the CloudNest console or command-line tools, users can manage stateful services in the cluster, such as databases and middleware. Users can create, delete, and adjust service configurations, as well as monitor service runtime status.

[0081] Cluster Remote Control Module: CloudNest provides a range of remote control functions that users can use to perform specific operations. For example, users can remotely execute commands, upload files, restart services, etc. These operations are transmitted to the corresponding nodes in the cluster via the CloudNest agent for execution.

[0082] Monitoring and logging module: CloudNest collects cluster monitoring metrics and log information and displays them in the console. Users can view the cluster's operating status and performance metrics in real time to troubleshoot and optimize performance.

[0083] Specifically, the cluster creation module includes:

[0084] Users select the option to create a cluster in the CloudNest console and provide the required configuration parameters, such as cluster name, region, and virtual machine type. These parameters can be provided via form input or configuration file.

[0085] After receiving the configuration parameters provided by the user, the CloudNest console will pass these parameters to the underlying cluster management system, which is usually a Kubernetes-based cluster management platform.

[0086] The cluster management system automatically creates corresponding resources in the cloud based on the received parameters. This includes, but is not limited to, virtual machine instances, storage volumes, and network configurations. The resource creation process may involve API calls to cloud service providers, such as using the APIs of cloud service providers (e.g., AWS, Azure, GCP) to create virtual machine instances.

[0087] The cluster management system configures and deploys necessary components for the cluster's master node, such as Kubernetes control plane components (API Server, Scheduler, Controller Manager), etcd (used to store cluster state and configuration), etc.

[0088] Once the master node is configured, the cluster management system will create a number of worker nodes, which will be used to run containerized applications and services. The worker nodes will automatically join the cluster and establish communication and coordination with the master node.

[0089] During the cluster creation process, the cluster management system monitors the creation and configuration of resources to ensure that all components and nodes of the cluster are successfully created and running.

[0090] Once the cluster is created, the cluster management system will return a success message to the CloudNest console, where users can view the status and related information of the newly created cluster.

[0091] In summary, the process of creating a cluster involves the user-provided configuration parameters being passed to the underlying cluster management system via the CloudNest console. This system then automatically creates the corresponding resources in the cloud based on these parameters, configures and deploys the various components and nodes of the cluster, and finally returns a success message to the CloudNest console. This allows users to manage and operate the newly created cluster on CloudNest.

[0092] Specifically, the CloudNest agent module includes:

[0093] After the cluster is created, the cluster management system will automatically deploy a cloud agent for each node in the cluster based on the configuration and requirements.

[0094] CloudNest Proxy is a lightweight software component that can run as a container on each cluster node or directly on the host operating system, depending on the implementation and configuration of the cluster management system.

[0095] Before deploying the CloudNest agent, the cluster management system generates a unique identifier and key for each node, used for secure communication and authentication with the CloudNest agent. For example:

[0096] Unique Identifier Generation: When creating each node, the cluster management system can use a unique algorithm or method to generate a unique node identifier. This identifier can be a long string. The implementation steps are as follows:

[0097] Timestamp: Retrieves the current timestamp, accurate to the millisecond level. A timestamp is a number representing the current time, ensuring that the generated UUID is unique at different points in time.

[0098] Random number: Generating a random number is usually done using a random number generator inside a computer to obtain randomness.

[0099] Other information: Incorporate other information such as the node's MAC address into the generation process to ensure that the generated UUID is unique in a distributed environment.

[0100] Generating a UUID: Combine information such as timestamp, random number, and MAC address, and use a hash function or other algorithm to calculate a unique UUID.

[0101] This process can be represented by a simple formula:

[0102] UUID=Hash(TimeStamp+RandomNumber+MACAddress+OtherInfo)

[0103] For example:

[0104] Node 1:02f18d6a-8d35-4c68-95a1-eb1d3d942c4a

[0105] Node 2:6c4ef0b2-3c47-42e8-918b-27d75a9a64e7

[0106] Node 3:a7c82f9b-1e8f-4c32-8b45-ec3db8d5a6f9 ...

[0108] Key Generation: The cluster management system can also generate a key pair for each node, including a public key and a private key. The private key will be stored internally within the node, while the public key will be used for secure communication with the Cloud Nest agent. This method can use ElGamal to implement secure communication and authentication, and the implementation steps are as follows:

[0109] Key generation:

[0110] The cluster management system generates a pair of ElGamal keys for each node: one is a private key (usually denoted as d), and the other is a public key (usually denoted as Y).

[0111] The ElGamal key generation process requires selecting a large prime number p and a primitive root g. These two parameters need to be shared between the cluster management system and the CloudNest agent.

[0112] For each node, the cluster management system selects a private key d and calculates the public key Y = g^dmodp.

[0113] Secure communication and authentication:

[0114] When the CloudNest agent needs to communicate securely with a node, it selects a random number r and then calculates C1 = g^rmodp and C2 = M * Y^rmodp, where M is the message to be sent.

[0115] When the CloudNest agent sends C1 and C2 to the node, it is actually transmitting encrypted messages.

[0116] The node uses its private key d to calculate K = C1^d mod p, then calculates C2 / K to obtain the decrypted message M. This process can be represented by the following formula:

[0117] K = C1^dmodp

[0118] M = (C² * K^-1) mod p

[0119] In this way, secure communication can be established between the CloudNest agent and the node, because only the node holding the node's private key can decrypt C2.

[0120] Registration Process: Before deploying the CloudNest agent, the cluster management system associates a generated unique identifier or public key with each node and registers it with the cluster's control plane or key management service. This process ensures that each node has a unique identifier or public key for subsequent secure communication.

[0121] Deploying CloudNest Agent: The cluster management system will deploy the CloudNest Agent installation package or container image to each node and include the node's identifier or public key in the agent configuration.

[0122] Secure Communication and Authentication: Once the CloudNest agent starts up and attempts to connect to the cluster management system's control plane, it sends the node's identifier or public key as authentication credentials. The cluster management system verifies these credentials and matches them against registered identifiers or public keys to confirm the agent's legitimacy.

[0123] Generating unique identifiers or keys for secure communication and authentication with the CloudNest agent involves generating unique identifiers or keys on cluster nodes and associating them with node registration. This ensures secure and trusted communication between the agent and the cluster management system. This helps prevent unauthorized access and protects cluster security.

[0124] The cluster management system distributes the CloudNest agent's installation package or container image to each node and starts the agent program. The CloudNest agent automatically registers with the cluster management system's control plane, establishing a communication channel with the cluster management system.

[0125] Once the Cloud Nest agent is started and connected to the cluster management system, it can begin performing its duties. This includes communicating with resources in the cloud, collecting cluster status information such as node health status and resource utilization, and sending this information to the cluster management system.

[0126] The CloudNest agent is also responsible for executing user commands. When a user sends commands through the CloudNest console or command-line tools, the CloudNest agent receives and parses these commands, then executes them on the appropriate node. For example, users can remotely execute commands, upload files, restart services, and perform other operations through the CloudNest agent.

[0127] Communication between the CloudNest agent and the cluster management system typically uses a secure encrypted channel to ensure the confidentiality and integrity of the communication.

[0128] By following the steps above, CloudNest can deploy the CloudNest agent to each node in the cluster. The agent is responsible for communicating with resources in the cloud, collecting status information, and executing user commands. This enables cluster monitoring and remote control. The specific deployment process and implementation method may vary depending on the cluster management system.

[0129] Specifically, the cluster connection module includes:

[0130] Users can install the command-line tools provided by CloudNest or use the corresponding API in their local environment.

[0131] Users establish a connection using command-line tools or APIs in programming languages ​​by specifying the cluster name and credentials. Credentials can be authentication keys, usernames, passwords, etc., depending on the authentication method of the CloudNest platform.

[0132] When a user specifies a cluster name, the CloudNest command-line tool or API will determine the location and related parameters of the cluster to be connected through the configuration information in the CloudNest console or configuration file.

[0133] The CloudNest command-line tool or API sends a connection request to the CloudNest agent module and provides the required credentials for authentication.

[0134] After receiving a connection request, the CloudNest proxy module will verify the user's credentials to confirm the legitimacy of their identity.

[0135] If the credentials are verified, the CloudNest agent module will establish a connection with the user's local environment and return a success response.

[0136] Once the connection is successfully established, users can interact with the cluster through the CloudNest command-line tool or API. Users can perform various operations, such as viewing the cluster status, managing stateful services, and executing remote commands.

[0137] The connection remains open, allowing users to continue interacting with the cluster for the duration of the connection until the user actively disconnects or the connection times out.

[0138] In summary, connecting to the cluster involves using the command-line tools or API provided by CloudNest. Users establish a connection by specifying the cluster name and credentials. The CloudNest command-line tools or API send the connection request to the CloudNest agent module. After authentication, a connection is established, and users can then interact with the cluster using the CloudNest command-line tools or API. Secure authentication mechanisms are employed throughout the connection establishment and maintenance process to ensure the user's legitimacy.

[0139] Specifically, the cluster status viewing module includes:

[0140] After connecting to the cluster, users can use the command-line tools or APIs provided by CloudNest to obtain cluster status information.

[0141] Users can send requests to the CloudNest agent module using command-line tools or specific commands or interfaces in the API to request cluster status information.

[0142] After receiving the request, the CloudNest proxy module will query the status information of each component and node in the cluster and summarize it.

[0143] The CloudNest agent module will return the aggregated cluster status information to the user's local environment, which can be the output of command-line tools or the response of API.

[0144] Users can view cluster status information in their local environment. CloudNest will update the cluster status information in real time and display it accordingly based on user requests.

[0145] Cluster status information includes, but is not limited to, the number of nodes, node health status, resource utilization, and load. This information can be displayed in tables, graphs, or other formats in the console or terminal for easy viewing and analysis by users.

[0146] Real-time updates to cluster status information are achieved by the CloudNest agent module periodically collecting information from components and nodes in the cluster and updating it to the cluster status storage.

[0147] Users can periodically query cluster status information or use the monitoring and alarm functions provided by CloudNest to obtain real-time and historical status information about the cluster.

[0148] By following the steps above, users can send requests to the CloudNest agent module via the command-line tool or API provided by CloudNest to obtain cluster status information. The CloudNest agent module will collect and summarize the status information of various components and nodes in the cluster, update it in real time, and display it to the user so that the user can understand the overall health and operation of the cluster.

[0149] Specifically, the stateful service management module includes:

[0150] Users can connect to the target cluster using the console or command-line tools provided by CloudNest.

[0151] Users can use the command-line tools or APIs provided by CloudNest to perform management operations on stateful services by specifying commands or interfaces, such as creating, deleting, and adjusting configurations.

[0152] Users can perform specific management operations by entering corresponding commands through command-line tools or by sending corresponding requests through the API.

[0153] The CloudNest console or command-line tool will send the user's operation request to the CloudNest agent module.

[0154] After receiving a user's operation request, the CloudNest proxy module parses the request and executes the corresponding operation. The specific implementation of the operation depends on the functionality of the CloudNest platform and the capabilities of the cluster management system.

[0155] Management operations for stateful services can include the following:

[0156] Creating stateful services: Users can specify the type of service, configuration parameters, etc., and the CloudNest proxy module will create the corresponding stateful service based on the user's request, such as database, middleware, etc.

[0157] Deleting a stateful service: Users can specify the name or identifier of the stateful service to be deleted, and the CloudNest agent module will perform the corresponding deletion operation to remove the service from the cluster.

[0158] Adjusting service configurations: Users can modify configuration parameters for stateful services, such as changing the database memory size or adjusting the concurrent connection limit of middleware. The CloudNest proxy module will apply the modified configurations to the corresponding services.

[0159] Monitoring service operation status: Users can view information such as the operation status, resource utilization, and health status of stateful services. The CloudNest agent module collects and summarizes service status information and displays it to users.

[0160] After completing the user's management operations, the CloudNest agent module will return the execution results to the CloudNest console or command-line tool, and the user can view the execution results and related information.

[0161] By following the steps above, users can manage stateful services in the cluster using the console or command-line tools provided by CloudNest, via command line or API. Users can perform operations such as creating, deleting, and adjusting configurations, and monitor the running status of services. The CloudNest agent module is responsible for receiving and executing user operation requests and returning the results to the user, enabling the user to manage and operate stateful services in the cluster.

[0162] Specifically, the cluster remote control module includes:

[0163] Users can connect to the target cluster using the console or command-line tools provided by CloudNest.

[0164] Users can send specific remote control commands or requests through the command-line tools or APIs provided by CloudNest, specifying the operations to be performed. For example, executing commands, uploading files, restarting services, etc.

[0165] The CloudNest console or command-line tool sends the user's remote control requests to the CloudNest agent module.

[0166] After receiving a remote control request, the CloudNest agent module will parse the request and pass it to the corresponding cluster node.

[0167] On the cluster nodes, the CloudNest agent module executes user-specified remote operations. The specific implementation of these operations depends on the functionality of the CloudNest platform and the capabilities of the cluster management system.

[0168] Remote control operations can include the following:

[0169] Command execution: Users can specify commands to be executed on cluster nodes, such as running scripts or launching applications. The CloudNest agent module will execute the commands on the target nodes and return the execution results to the CloudNest console or command-line tool.

[0170] Upload Files: Users can upload local files to cluster nodes, such as configuration files and data files. The CloudNest proxy module will then transfer the files to the specified location on the target node.

[0171] Restart Service: Users can specify the service or application to restart. The CloudNest agent module will perform the corresponding restart operation to restart the service or application.

[0172] After executing the user's remote control operation, the CloudNest agent module will return the execution result to the CloudNest console or command-line tool, and the user can view the execution result and related information.

[0173] By following the steps above, users can use the console or command-line tools provided by CloudNest to send remote control requests to perform specific operations, such as executing commands, uploading files, or restarting services. The CloudNest agent module is responsible for forwarding the requests to the corresponding cluster nodes for execution and returning the results to the user, thereby achieving the purpose of remotely controlling the cluster.

[0174] Specifically, the monitoring and logging modules include:

[0175] The CloudNest agent module periodically collects monitoring metrics and log information from the cluster. Monitoring metrics may include node CPU utilization, memory utilization, network traffic, etc., while log information may include application logs, system logs, etc.

[0176] The CloudNest agent module sends the collected monitoring metrics and log information to the cluster state storage or log storage. These storage systems are typically dedicated to storing and analyzing monitoring and log data, such as Elasticsearch and Prometheus.

[0177] Cluster state storage or log storage processes and stores the collected data for subsequent querying and analysis. For example, monitoring metrics can be stored in a time-series database, and log information can be indexed and searched.

[0178] The CloudNest console retrieves data from the cluster state storage or log storage and displays it to the user. Users can view cluster monitoring metrics and log information through the console interface provided by CloudNest.

[0179] Users can view the cluster's operational status and performance metrics in real time, such as node resource utilization and service response time. Users can also view application logs for troubleshooting and performance optimization.

[0180] CloudNest consoles typically provide charts, dashboards, and query functions to facilitate users in visualizing and flexibly querying monitoring metrics and log information.

[0181] Users can perform troubleshooting, performance optimization, and resource planning based on monitoring metrics and log information to ensure the stability and performance of the cluster.

[0182] Through the above steps, CloudNest will periodically collect cluster monitoring metrics and log information, and store and display them to users. Users can view the cluster's operational status and performance metrics, as well as application log information, in real time through the CloudNest console, facilitating troubleshooting and performance optimization. The implementation of these functions relies on the cluster management system and related monitoring and log storage systems.

[0183] Finally, it should be noted that the above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the claims of the present invention.

Claims

1. A cloud-nest cluster remote control system, characterized in that, include: Cluster creation module: Used to create clusters in the CloudNest console and provide the required configuration parameters. CloudNest will automatically create the corresponding resources on the cloud based on the parameters. The cluster management system configures and deploys necessary components for the master node of the cluster and creates a certain number of worker nodes. These worker nodes are used to run containerized applications and services. The worker nodes automatically join the cluster and establish communication and coordination with the master node. The CloudNest agent module is used to communicate with resources in the cloud, collect cluster status information, and execute user operation commands. The CloudNest agent runs as a container on each cluster node or directly on the host operating system. The cluster management system distributes the installation package or container image of the Cloud Nest agent to each node and starts the agent program. The Cloud Nest agent automatically registers with the control plane of the cluster management system and establishes a communication channel with the cluster management system. Cluster Connection Module: Used to connect to a specific cluster; users install the command-line tool provided by CloudNest in their local environment or use the corresponding API to establish a connection by specifying the cluster name and credentials; the CloudNest command-line tool or API sends a connection request to the CloudNest agent module and provides the required credentials for authentication; after receiving the connection request, the CloudNest agent module verifies the user's credentials and confirms the legitimacy of their identity. If the credentials are verified, the CloudNest agent module establishes a connection with the user's local environment and returns a success response; Cluster status viewing module: Used to view cluster status information; Stateful Service Management Module: Manages stateful services in the cluster through the CloudNest console or command-line tools; users can execute management operations for stateful services by specifying commands or interfaces, including creating stateful services, deleting stateful services, adjusting service configurations, and monitoring service running status. Cluster remote control module: used for remotely executing commands, uploading files, and restarting services; Monitoring and logging module: CloudNest collects monitoring metrics and log information of the cluster and displays them in the console; The CloudNest agent module periodically collects monitoring metrics and log information from the cluster and sends the collected data to the cluster state storage or log storage. The cluster state storage or log storage processes and stores the collected data for subsequent querying and analysis. The CloudNest console retrieves the data from the cluster state storage or log storage and displays it to the user, allowing the user to view the cluster's operating status and performance metrics in real time for troubleshooting and performance optimization.

2. The cloud-nest cluster remote control system of claim 1, wherein, The cluster creation module includes: Users select the option to create a cluster in the CloudNest console and provide the required configuration parameters, which can be provided through form input or configuration file. After receiving the configuration parameters provided by the user, the CloudNest console passes the parameters to the underlying cluster management system. The cluster management system automatically creates the corresponding resources in the cloud based on the received parameters; The cluster management system configures and deploys the necessary components for the cluster's master node; Once the master node is configured, the cluster management system will create a certain number of worker nodes. These nodes will be used to run containerized applications and services. The worker nodes will automatically join the cluster and establish communication and coordination with the master node. During the cluster creation process, the cluster management system monitors the creation and configuration of resources to ensure that all components and nodes of the cluster are successfully created and running. Once the cluster is created, the cluster management system will return a success message to the CloudNest console, where users can view the status and related information of the newly created cluster.

3. The cloud-nest cluster remote control system of claim 2, wherein, The CloudNest agent module includes: After the cluster is created, the cluster management system automatically deploys a Cloud Nest agent for each node in the cluster based on the configuration and requirements. The Cloud Nest agent runs as a container on each cluster node, or directly on the host operating system; Before deploying the Cloud Nest agent, the cluster management system generates a unique identifier or key for each node to communicate and authenticate securely with the Cloud Nest agent; The cluster management system distributes the installation package or container image of the Cloud Nest agent to each node and starts the agent program. The Cloud Nest agent automatically registers with the control plane of the cluster management system and establishes a communication channel with the cluster management system. Once the Cloud Nest agent starts up and connects to the cluster management system, the agent begins to perform its duties, including communicating with resources in the cloud, collecting cluster status information, and sending the information to the cluster management system. The CloudNest agent is also responsible for executing user commands. When a user sends a command in the CloudNest console or through a command-line tool, the CloudNest agent receives and parses the command and executes it on the corresponding node.

4. The cloud-nest cluster remote control system of claim 3, wherein, The cluster connection module includes: Users can install the command-line tools provided by CloudNest or use the corresponding APIs in their local environment; Users can establish a connection by specifying the cluster name and credentials using command-line tools or APIs in programming languages; When a user specifies a cluster name, the CloudNest command-line tool or API will determine the location and related parameters of the cluster to be connected through the configuration information in the CloudNest console or configuration file. The CloudNest command-line tool or API will send a connection request to the CloudNest agent module and provide the required credentials for authentication; After receiving a connection request, the CloudNest proxy module verifies the user's credentials to confirm their identity. If the credentials are verified, the CloudNest proxy module will establish a connection with the user's local environment and return a success response. Once the connection is successfully established, users can interact with the cluster through the CloudNest command-line tool or API; The connection remains open, and the user continues to interact with the cluster for the duration of the connection until the user actively disconnects or the connection times out.

5. The cloud-nest cluster remote control system according to claim 4, wherein, The cluster status viewing module includes: After connecting to the cluster, users can use the command-line tools or APIs provided by CloudNest to obtain cluster status information. Users can send requests to the CloudNest agent module using command-line tools or specific commands or interfaces in the API to request cluster status information; After receiving the request, the CloudNest proxy module queries and summarizes the status information of each component and node in the cluster. The CloudNest agent module will return the aggregated cluster status information to the user's local environment, which can be the output of command-line tools or the response of APIs. Users can view cluster status information in their local environment. CloudNest will update the cluster status information in real time and display it accordingly based on the user's request. Cluster status information includes the number of nodes, node health status, resource utilization, and load status. The information is displayed in tabular form in the console or terminal for easy viewing and analysis by users. Real-time updates to cluster status information are achieved by the CloudNest agent module periodically collecting information from components and nodes in the cluster and updating it to the cluster status storage. Users can obtain real-time and historical status information about the cluster by periodically querying the cluster status information or by using the monitoring and alarm functions provided by CloudNest.

6. The cloud-nest cluster remote control system according to claim 5, wherein, The stateful service management module includes: Users connect to the target cluster using the console or command-line tools provided by CloudNest; Users can use the command-line tools or APIs provided by CloudNest to perform management operations on stateful services by specifying commands or interfaces; Users can perform specific management operations by entering corresponding commands through command-line tools or by sending corresponding requests through the API; The CloudNest console or command-line tool sends the user's operation request to the CloudNest agent module; after receiving the user's operation request, the CloudNest agent module parses the request and executes the corresponding operation. After completing the user's management operations, the CloudNest agent module will return the execution results to the CloudNest console or command-line tool, and the user can view the execution results and related information.

7. The cloud-nest cluster remote control system according to claim 6, wherein, The cluster remote control module includes: Users connect to the target cluster using the console or command-line tools provided by CloudNest; Users can send specific remote control commands or requests through the command-line tools or APIs provided by CloudNest to specify the operations to be performed; The CloudNest console or command-line tool sends the user's remote control request to the CloudNest agent module; After receiving a remote control request, the CloudNest agent module parses the request and forwards it to the corresponding cluster node; On the cluster nodes, the CloudNest agent module executes remote operations specified by the user; After executing the user's remote control operation, the CloudNest agent module will return the execution result to the CloudNest console or command-line tool, and the user can view the execution result and related information.

8. The cloud-nest cluster remote control system according to claim 7, wherein, The monitoring and logging module includes: The CloudNest agent module periodically collects monitoring metrics and log information from the cluster, including application logs and system logs. The CloudNest agent module sends the collected monitoring metrics and log information to the cluster state storage or log storage; Cluster state storage or log storage processes and stores the collected data for subsequent querying and analysis; The CloudNest console retrieves data from cluster state storage or log storage and displays it to users.

Images