A scalable and highly available containerization method and server architecture

Through automation tools and intelligent configuration, the lack of adaptability and management complexity of the server architecture under dynamic workloads is solved, efficient resource utilization and system stability are achieved, and the operation process is simplified.

CN118672733BActive Publication Date: 2024-11-26四川华鲲振宇智能科技有限责任公司
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202411162989.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-23
Publication Date
2024-11-26
Estimated Expiration
2044-08-23

AI Technical Summary

Technical Problem

The existing server architecture is insufficiently adaptable, complex configuration, cumbersome management, and cumbersome service deployment and updates when facing dynamic workloads, resulting in waste of resources and performance bottlenecks.

Method used

Design a scalable and highly available containerization method, use automation tools to initialize server clusters and node management, realize dynamic resource allocation and self-healing mechanisms, monitor communication requirements and resource utilization in real time, automatically configure networks and storage, and provide Smart user interface to simplify operations.

Benefits of technology

It improves system resource utilization, reduces costs, enhances communication efficiency between containers, reduces network latency, improves system stability and availability, reduces the burden on administrators, and realizes optimized resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118672733B_ABST
    Figure CN118672733B_ABST
Patent Text Reader

Abstract

The present invention belongs to the technical field of computer system design, and specifically relates to a scalable and highly available containerization method and server architecture. First, the user interface automation tools are designed; the server cluster is initialized and the nodes are automatically managed, and the health check and self-healing mechanism of each node are deployed, and each node is actively or passively checked for health; intelligent container orchestration is performed, and dynamic resource allocation is performed during the automatic management process; the communication needs of the server are detected in real time, and the network rules are automatically and dynamically configured; the server resource utilization and the operation status of the server are monitored in real time, and the status of the container instance is tracked. If an abnormality is found, the type of abnormality is determined, and the abnormality is automatically handled. The resource configuration is dynamically adjusted through the adaptive and dynamic scaling mechanism to improve the resource utilization, and the automatic network planning improves the communication efficiency between containers and reduces network delay. Through automated recovery, the system stability and availability are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of computer system design, and in particular relates to a scalable and highly available containerization method and server architecture. Background Art

[0002] In today's digital and information age, the development of cloud computing, containerization technology, and distributed systems has brought new challenges and opportunities to building flexible, efficient, and scalable server architectures. First, cloud computing, as a network-based service model, has undergone revolutionary changes at the business and technical levels. It allows users to access and use computing resources through the Internet without directly managing hardware devices. This facilitates the flexible deployment and efficient management of applications, while providing strong support for coping with changing workloads. Secondly, containerization technology provides a more portable, scalable, and consistent environment by packaging applications and their dependencies into lightweight containers. Containerization platforms such as Docker make it easier for developers to build, deliver, and run applications while reducing environmental differences and dependency issues. As the number of containers increases, managing and orchestrating these containers becomes critical. Container orchestration systems (such as Kubernetes and Docker Swarm) have emerged to automate and simplify the deployment, scaling, and management of containers. This provides the basis for building a scalable and highly available containerization method and server architecture. High availability is also an important indicator of a server. Therefore, in this context, the above technologies need to be used to achieve flexibility, efficiency, and reliability of the server architecture.

[0003] In this technical background, existing implementation solutions include Docker Swarm and Mesos, but they may have some restrictions or limitations. The following is a brief introduction to Docker Swarm and Mesos.

[0004] Docker Swarm: Docker Swarm is a container orchestration tool provided by Docker for managing and orchestrating Docker containers. It supports functions such as automated deployment, load balancing, and health checks, but in some scenarios, Docker Swarm is not adaptable enough to dynamic workloads.

[0005] Mesos: Apache Mesos is an open source cluster management system that supports scheduling and resource isolation of distributed applications. It can be integrated with container technology, but requires more configuration and customization to achieve the goals of high availability and automation.

[0006] Current mainstream container orchestration systems, such as Kubernetes, are quite complex, including numerous configuration options and concepts, resulting in a steep learning curve, making it difficult for small teams or novice users to quickly master and effectively apply these systems.

[0007] In addition, in the above-mentioned prior art, firstly, its configuration files and options are complex. Container orchestration systems usually need to use complex configuration files to define settings for services, networks, storage, etc. These configuration files may contain a large number of parameters and options, and the configuration syntax may be relatively obscure, requiring users to have an in-depth understanding of the system and orchestration tools. Secondly, cluster initialization and node management are cumbersome, requiring the entire cluster to be initialized and each node to be managed. This includes installing and configuring the container runtime, the container orchestration system, and ensuring the connectivity and consistency of the nodes. This process requires a lot of manual intervention, which is prone to configuration errors and inconsistencies. Thirdly, the deployment and update of services are cumbersome. Deploying and updating services may require modifying configuration files, manually executing commands, or using specific tools. This process involves multiple steps, including building container images, stopping and starting services, version management, etc., requiring users to perform detailed operations and monitoring. Finally, the configuration of networks and storage is cumbersome. Containerized architectures usually involve complex network and storage configurations, including defining communication rules between services, configuring load balancing, setting storage volumes, etc. These configuration items involve multiple components and need to be set carefully, otherwise it is easy to cause service unavailability or performance problems. The fifth is that the monitoring and logging settings are inconvenient. Setting up the monitoring and logging system requires users to define which indicators should be monitored and how logs should be collected and stored. These settings usually need to be performed in different tools and systems, which increases the complexity of the overall configuration.

[0008] Therefore, how to improve the existing server architecture to solve the technical problems of the existing server architecture, such as insufficient adaptability to dynamic workloads, complex configuration, cumbersome management, and cumbersome service deployment and update. Summary of the invention

[0009] The purpose of the present invention is to solve the technical problems existing in the existing server architecture, such as insufficient adaptability to dynamic workloads, complex configuration, cumbersome management, and cumbersome deployment and updating of services.

[0010] In order to solve the above technical problems, the technical solution adopted by the present invention is as follows:

[0011] In a first aspect, a scalable and highly available containerization method is provided, comprising the following steps:

[0012] S1: Design and deploy various automation tools for the server's user interface;

[0013] S2: Use automated tools in the server to initialize the server cluster and automatically manage the nodes, deploy health checks and self-healing mechanisms for each node, perform active or passive health checks on each node, and automatically migrate services from failed nodes to other available nodes.

[0014] S3: Perform intelligent container orchestration and dynamic resource allocation during automatic management, so that container instances can dynamically adjust the resources they occupy during runtime;

[0015] S4: Detects the communication needs of servers in real time and automatically and dynamically configures network rules based on service mesh, microservice proxy, or cloud native network.

[0016] S5: monitor the server resource utilization and server operation status in real time, track the status of the container instance, and if an abnormality is found, execute step S6;

[0017] S6: Determine the type of exception, which includes automatically processed exceptions and manually processed exceptions. Automatically process the automatically processed exceptions, output processing suggestions for manually processed exceptions, and inform the administrator to process through the early warning module.

[0018] Preferably, step S2 includes the following specific processes:

[0019] S21: Initialize the server cluster;

[0020] S22: monitor in real time whether there is a new server node request, and if so, add the new server node to the cluster;

[0021] S23: Monitor the operation status of each node in the service cluster based on the HTTP protocol, the TCP protocol, or the UDP protocol to determine whether there is an abnormality. If so, execute step S24. If not, each node keeps running continuously.

[0022] S24: Migrate the services on the abnormal node to other adjacent available nodes to automatically replace the faulty node and perform automatic or manual maintenance on the abnormal node.

[0023] Preferably, in step S24, the following specific processes are included:

[0024] S241: saving and synchronizing the status information and related data in the service on the abnormal node;

[0025] S242: Detect resource occupancy and operation status of adjacent nodes in real time, and select a node to be migrated based on the resource occupancy and operation status and the corresponding service type in the abnormal node;

[0026] S243: Migrate the service of the abnormal node to the selected node of the migrated service, and continuously process the migrated service by selecting the node of the migrated service.

[0027] Preferably, in step S242, the node to be migrated is selected using a scoring mechanism, and the specific process is as follows:

[0028] S2421: Analyze the service content of the abnormal node;

[0029] S2422: Score each neighboring node of the abnormal node. The scoring mechanism adopts a weighted approach. The scoring function of a specific node is:

[0030] F=Aa+Bb+Cc+···+Nn;

[0031] Among them, F is the scoring function of a node, A represents the first parameter of a node, a is the weight ratio of A; B represents the second parameter of a node, b is the weight ratio of B; C represents the third parameter of a node, c is the weight ratio of C; N represents the Nth parameter of a node, n is the weight ratio of N;

[0032] The first parameter is resource utilization, the second parameter is network latency, the third parameter is service dependency, and the Nth parameter is the service type of the abnormal node;

[0033] S2423: According to the score value of each node in step S2422, the node with the highest score value is selected as the node to be migrated.

[0034] Preferably, step S4 includes the following specific process:

[0035] S41: Perform intelligent network partitioning, monitor network status and load in real time, and intelligently adjust the location of container instances;

[0036] S42: elastically configure the network to monitor network requirements, and dynamically adjust network resources on the container instance. The dynamic adjustment process includes adjusting bandwidth or allocating IP addresses.

[0037] S43: Pool the storage resources in the cluster to form a storage pool, which includes a distributed file system, a distributed database, and object storage. According to the preset storage strategy, the stored data is divided into different storage levels based on access frequency and importance. The storage levels include hot and cold data separation, a cache layer, and persistent storage. The storage volume is mounted or unmounted as needed to perform dynamic storage management.

[0038] Preferably, the design of various automated tools for the user interface of the server in step S1 includes the following process:

[0039] S11: Graphically display the topology, service status, and resource utilization of the entire containerized server architecture;

[0040] S12: Provides interactive interface elements to enable starting or stopping container instances or adjusting resource quotas by clicking icons or buttons;

[0041] S13: Acquire system status information in real time and update the data of the user interface in real time;

[0042] S14: Analyze the real-time status information and historical data of the system and provide configuration suggestions for the user interface;

[0043] S15: Set up different roles, including administrators, developers, and operation and maintenance personnel, and assign different operation permissions to different roles.

[0044] In the second aspect, a scalable and highly available containerized server architecture is provided, including a cluster management and automation module, a resource dynamic adjustment module, a network configuration module, a storage configuration module, a data acquisition module, and a user interface design module;

[0045] The cluster management and automation module is used to initialize the server cluster and automatically manage the nodes, deploy health checks and self-healing mechanisms for each node, perform active or passive health checks on each node, and automatically migrate the services of the failed node to other available nodes;

[0046] The resource dynamic adjustment module performs intelligent container orchestration and dynamic resource allocation during the automatic management process, so that the container instance can dynamically adjust the resources it occupies during runtime;

[0047] The network configuration module is used to automatically and dynamically configure network rules based on a service grid or a microservice proxy or a cloud native network;

[0048] The storage configuration module is used to specify storage policies according to application requirements and dynamically adjust storage capacity based on the storage policies;

[0049] The data collection module is used to collect various parameters and operation status data of the server system and container instance in real time;

[0050] The user interface design module is used to design the user interface, graphically display the topology, service status and resource utilization of the entire containerized server architecture, and provide interactive interface elements and automated deployment tools.

[0051] Preferably, the various parameters in the operation of the server system include CPU usage, memory usage, and disk I / O, the operation status data of the service includes service availability, response time, and error rate, and the status data of the container instance includes operation status, start time, and stop time.

[0052] The beneficial effects of the present invention include:

[0053] The present invention provides a scalable and highly available containerization method and server architecture. First, through adaptability and dynamic scaling mechanisms, resource configuration is dynamically adjusted according to real-time workload requirements, thereby improving the resource utilization of the system and reducing costs. Second, through intelligent network planning, the container instance can intelligently select the optimal network path, improve the efficiency of communication between containers, and reduce network latency. Third, through high availability and self-healing mechanisms, through real-time monitoring, automated recovery and other means, the stability and availability of the system are improved, and the risk of service interruption is reduced. Fourth, through intelligent analysis and suggestion mechanisms, monitoring data is analyzed to provide administrators with performance optimization suggestions, which speeds up problem location and resolution. Fifth, through automated operation and maintenance tasks, the system can regularly perform key tasks, reduce the burden on administrators, and improve the maintainability and stability of the system. Sixth, through dynamic scaling mechanisms, intelligent network planning and other technologies, optimal utilization of resources is achieved, costs are reduced, and the economy of the system is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 The figure is a flow chart of a scalable and highly available containerization method of the present invention. DETAILED DESCRIPTION

[0055] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0056] The following is combined with Figure 1 The present invention is further described in detail:

[0057] See also Figure 1 , a scalable and highly available containerization method, comprising the following steps:

[0058] S1: Design and deploy various automation tools for the server's user interface;

[0059] S2: Use automated tools in the server to initialize the server cluster and automatically manage the nodes, deploy health checks and self-healing mechanisms for each node, perform active or passive health checks on each node, and automatically migrate services from failed nodes to other available nodes.

[0060] S3: Perform intelligent container orchestration and dynamic resource allocation during automatic management, so that container instances can dynamically adjust the resources they occupy during runtime;

[0061] S4: Detects the communication needs of servers in real time and automatically and dynamically configures network rules based on service mesh, microservice proxy, or cloud native network.

[0062] S5: monitor the server resource utilization and server operation status in real time, track the status of the container instance, and if an abnormality is found, execute step S6;

[0063] S6: Determine the type of exception, which includes automatically processed exceptions and manually processed exceptions. Automatically process the automatically processed exceptions, output processing suggestions for manually processed exceptions, and inform the administrator to process through the early warning module.

[0064] Traditional server architectures usually use static resource configurations, which are difficult to cope with dynamic changes in workloads, resulting in resource waste or performance bottlenecks. Therefore, this application sets up an adaptive and dynamic scaling mechanism to dynamically adjust resource configuration according to real-time workload requirements, thereby improving system resource utilization and reducing costs.

[0065] Traditional network configurations are relatively static, and inter-container communications may have performance bottlenecks or inefficiencies. The present invention uses intelligent network planning to enable container instances to intelligently select the optimal network path, improve the efficiency of inter-container communication, and reduce network latency. Through high availability and self-healing mechanisms, real-time monitoring, automated recovery and other means, the stability and availability of the system are improved, and the risk of service interruption is reduced. Through the intelligent analysis and suggestion mechanism, the monitoring data is analyzed through machine learning algorithms to provide administrators with performance optimization suggestions, which accelerates the speed of problem location and resolution. Through automated operation and maintenance tasks, the system can regularly perform key tasks, reduce the burden on administrators, and improve the maintainability and stability of the system. Traditional architectures may have problems with resource waste, such as over-configuration or inefficient utilization. The present invention uses technologies such as dynamic scaling mechanisms and intelligent network planning to achieve optimal utilization of resources, reduce costs, and improve the economy of the system.

[0066] Step S2 includes the following specific processes:

[0067] S21: Initialize the server cluster;

[0068] S22: monitor in real time whether there is a new server node request, and if so, add the new server node to the cluster;

[0069] S23: Monitor the operation status of each node in the service cluster based on the HTTP protocol, the TCP protocol, or the UDP protocol to determine whether there is an abnormality. If so, execute step S24. If not, each node keeps running continuously.

[0070] S24: Migrate the services on the abnormal node to other adjacent available nodes to automatically replace the faulty node and perform automatic or manual maintenance on the abnormal node.

[0071] In step S24, the following specific processes are included:

[0072] S241: saving and synchronizing the status information and related data in the service on the abnormal node;

[0073] S242: Detect resource occupancy and operation status of adjacent nodes in real time, and select a node to be migrated based on the resource occupancy and operation status and the corresponding service type in the abnormal node;

[0074] S243: Migrate the service of the abnormal node to the selected node of the migrated service, and continuously process the migrated service by selecting the node of the migrated service.

[0075] In step S242, the node to be migrated is selected using a scoring mechanism, and the specific process is as follows:

[0076] S2421: Analyze the service content of the abnormal node;

[0077] S2422: Score each neighboring node of the abnormal node. The scoring mechanism adopts a weighted approach. The scoring function of a specific node is:

[0078] F=Aa+Bb+Cc+···+Nn;

[0079] Among them, F is the scoring function of a node, A represents the first parameter of a node, a is the weight ratio of A; B represents the second parameter of a node, b is the weight ratio of B; C represents the third parameter of a node, c is the weight ratio of C; N represents the Nth parameter of a node, n is the weight ratio of N;

[0080] The first parameter is resource utilization, the second parameter is network latency, the third parameter is service dependency, and the Nth parameter is the service type of the abnormal node;

[0081] S2423: According to the score value of each node in step S2422, the node with the highest score value is selected as the node to be migrated.

[0082] Through the node health check mechanism, regular health checks are performed to monitor the availability of nodes. Active or passive health checks of nodes are performed using protocols such as HTTP, TCP, and UDP. Fast fault detection time is set to ensure that node failures can be discovered and processed as early as possible. Shorter detection time can reduce the system's response time to failures. Through the coordination of container orchestration tools, services are ensured to be uninterrupted during the migration process and users are unaware. Before service migration, ensure that relevant status information is saved and synchronized to prevent data loss or service interruption.

[0083] Once a node failure is detected, the system automatically migrates the affected services to other available nodes to ensure the continuous availability of the services. Automatically replace damaged nodes. When a node is determined to be unavailable, it is automatically replaced with a new node to maintain the normal operation of the entire cluster. And use intelligent load balancing algorithms to ensure that requests are evenly distributed among various container instances to avoid resource waste and performance degradation caused by overload of some instances. Implement dynamic load balancing and dynamically adjust the load balancing strategy according to real-time node status and performance indicators to adapt to the ever-changing environment. Through the anomaly detection mechanism, monitor the abnormal conditions during system operation, such as increased error rate and extended service response time. The system can automatically respond to the detected abnormal conditions, including service migration and restart of container instances.

[0084] The system automatically attempts to repair failed components without manual intervention, including restarting container instances, redeploying services, etc. Integrate a real-time monitoring system to monitor the status of clusters, nodes, and services. Monitoring data can include resource utilization, service response time, node health, etc. Set alarm thresholds to trigger alarms when monitoring data exceeds preset thresholds. Alarms can notify administrators or automatically trigger corresponding self-healing operations to prevent fault escalation. Save key status information of container instances before they fail. This may involve snapshots of storage volumes, backups of database status, etc. After a failure, restore the status as much as possible. Automatically apply the saved status information to new container instances to minimize the interruption time of system services. Finally, log and audit.

[0085] Step S4 includes the following specific processes:

[0086] S41: Perform intelligent network partitioning, monitor network status and load in real time, and intelligently adjust the location of container instances;

[0087] S42: elastically configure the network to monitor network requirements, and dynamically adjust network resources on the container instance. The dynamic adjustment process includes adjusting bandwidth or allocating IP addresses.

[0088] S43: Pool the storage resources in the cluster to form a storage pool, which includes a distributed file system, a distributed database, and object storage. According to the preset storage strategy, the stored data is divided into different storage levels based on access frequency and importance. The storage levels include hot and cold data separation, a cache layer, and persistent storage. The storage volume is mounted or unmounted as needed to perform dynamic storage management.

[0089] Based on the communication requirements between services, network rules are dynamically configured by using service mesh technology, microservice proxy or cloud native network solutions. Combined with intelligent load balancing algorithms, it ensures that requests are evenly distributed among available container instances to improve system performance. Through intelligent network partitioning processing, the location of container instances is intelligently adjusted according to real-time network status and load conditions to ensure normal operation within the partition. Through elastic network configuration, container instances can dynamically adjust their network resources according to demand, including dynamic adjustment of bandwidth, IP address allocation, etc., to adapt to changing network needs.

[0090] Implement a storage pool management mechanism to pool storage resources in the cluster, realize flexible sharing of storage resources, and improve the overall efficiency of storage. Storage pools can include distributed file systems, distributed databases, object storage, etc. Support dynamic storage allocation and dynamically adjust storage capacity according to application needs. Container instances mount or unmount storage volumes according to needs during runtime to achieve dynamic storage management. Formulate storage strategies to divide data into different storage levels, including hot and cold data separation, cache layer, and persistent storage, based on factors such as data access frequency and importance, to optimize storage performance and cost. Through intelligent backup and recovery mechanisms, ensure that critical data can be quickly restored in the event of a failure, reduce the need for manual intervention, and improve data reliability. Use container network and storage orchestration tools to automatically handle network communication between containers and simplify the configuration process. For inter-container communication, select protocols that support multiplexing and binary transmission, such as gRPC and HTTP / 2, to reduce network overhead. Through intelligent routing mechanisms, dynamically adjust network routes according to real-time network conditions and the location of container instances to ensure that data can be transmitted through the optimal path. Use TLS / SSL encryption protocol communication mechanisms to ensure the security of data during network transmission.

[0091] The design of various automation tools for the user interface of the server in step S1 includes the following processes:

[0092] S11: The topology, service status, and resource utilization of the entire containerized server architecture are graphically displayed, allowing administrators to quickly understand the overall status of the system;

[0093] S12: Provides interactive interface elements to enable starting or stopping container instances or adjusting resource quotas by clicking icons or buttons;

[0094] S13: Obtain system status information in real time and update the data in the user interface in real time so that administrators can obtain the latest system status in a timely manner. This helps with real-time monitoring and problem tracking;

[0095] S14: Analyzes the real-time status information and historical data of the system, provides configuration suggestions for the user interface, reduces configuration complexity, and provides automated deployment tools, allowing administrators to complete complex deployment tasks through simple interface operations;

[0096] S15: Set up different roles, including administrators, developers, and operation and maintenance personnel, and assign different operation permissions to different roles.

[0097] A scalable and highly available containerized server architecture, including a cluster management and automation module, a resource dynamic adjustment module, a network configuration module, a storage configuration module, a data acquisition module, and a user interface design module;

[0098] The cluster management and automation module is used to initialize the server cluster and automatically manage the nodes, deploy health checks and self-healing mechanisms for each node, perform active or passive health checks on each node, and automatically migrate the services of the failed node to other available nodes;

[0099] The resource dynamic adjustment module performs intelligent container orchestration and dynamic resource allocation during the automatic management process, so that the container instance can dynamically adjust the resources it occupies during runtime;

[0100] The network configuration module is used to automatically and dynamically configure network rules based on a service grid or a microservice proxy or a cloud native network;

[0101] The storage configuration module is used to specify storage policies according to application requirements and dynamically adjust storage capacity based on the storage policies;

[0102] The data collection module is used to collect various parameters and operation status data of the server system and container instance in real time;

[0103] The user interface design module is used to design the user interface, graphically display the topology, service status and resource utilization of the entire containerized server architecture, and provide interactive interface elements and automated deployment tools.

[0104] Preferably, the various parameters in the operation of the server system include CPU usage, memory usage, and disk I / O, the operation status data of the service includes service availability, response time, and error rate, and the status data of the container instance includes operation status, start time, and stop time.

[0105] In summary, the present invention provides a scalable and highly available containerization method and server architecture, which first designs various automation tools for the user interface; initializes the server cluster and automatically manages the nodes, deploys health checks and self-healing mechanisms for each node, and performs active or passive health checks on each node; performs intelligent container orchestration, and dynamically allocates resources during the automatic management process; detects the communication needs of the server in real time, and automatically and dynamically configures network rules; monitors the server resource utilization and the operation of the server in real time, tracks the status of the container instance, and if an abnormality is found, determines the type of abnormality, and automatically handles the abnormality. Dynamically adjust resource configuration through adaptability and dynamic scaling mechanisms to improve resource utilization, and automatic network planning improves communication efficiency between containers and reduces network latency. Through automated recovery, system stability and availability are improved.

[0106] Through adaptive and dynamic scaling mechanisms, resource configuration is dynamically adjusted according to real-time workload requirements, which improves the system's resource utilization and reduces costs. Through intelligent network planning, container instances can intelligently select the optimal network path, improve the efficiency of communication between containers, and reduce network latency. Through high availability and self-healing mechanisms, through real-time monitoring, automated recovery and other means, the stability and availability of the system are improved, and the risk of service interruption is reduced. Through intelligent analysis and suggestion mechanisms, monitoring data is analyzed to provide administrators with performance optimization suggestions, which speeds up problem location and resolution. Through automated operation and maintenance tasks, the system can perform critical tasks regularly, reduce the burden on administrators, and improve the maintainability and stability of the system. Through dynamic scaling mechanisms, intelligent network planning and other technologies, optimal utilization of resources is achieved, costs are reduced, and the economy of the system is improved.

[0107] The above-mentioned embodiments only express the specific implementation method of the present application, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the protection scope of the present application. It should be pointed out that, for ordinary technicians in this field, several variations and improvements can be made without departing from the technical solution concept of the present application, and these all belong to the protection scope of the present application.

Claims

1. A scalable and highly available containerization method, characterized in that: The following steps are involved: S1: Design and deploy various automation tools for the server's user interface; S2: Use automated tools in the server to initialize the server cluster and automatically manage the nodes, deploy health checks and self-healing mechanisms for each node, perform active or passive health checks on each node, and automatically migrate services from failed nodes to other available nodes. S3: Perform intelligent container orchestration and dynamic resource allocation during automatic management, so that container instances can dynamically adjust the resources they occupy during runtime; S4: Detects the communication needs of servers in real time and automatically and dynamically configures network rules based on service mesh, microservice proxy, or cloud native network. S5: monitor the server resource utilization and server operation status in real time, track the status of the container instance, and if an abnormality is found, execute step S6; S6: Determine the type of exception, which includes automatic processing exceptions and manual processing exceptions, automatically process the automatic processing exceptions, output processing suggestions for manual processing exceptions, and inform the administrator through the early warning module to handle them; Step S2 includes the following specific processes: S21: Initialize the server cluster; S22: monitor in real time whether there is a new server node request, and if so, add the new server node to the cluster; S23: Monitor the operation status of each node in the service cluster based on the HTTP protocol, the TCP protocol, or the UDP protocol to determine whether there is an abnormality. If so, execute step S24. If not, each node keeps running continuously. S24: Migrate the services on the abnormal node to other adjacent available nodes to automatically replace the faulty node and perform automatic or manual maintenance on the abnormal node; In step S24, the following specific processes are included: S241: saving and synchronizing the status information and related data in the service on the abnormal node; S242: Detect resource occupancy and operation status of adjacent nodes in real time, and select a node to be migrated based on the resource occupancy and operation status and the corresponding service type in the abnormal node; S243: Migrate the service of the abnormal node to the selected node of the migrated service, and continuously process the migrated service by selecting the node of the migrated service; In step S242, the node to be migrated is selected using a scoring mechanism, and the specific process is as follows: S2421: Analyze the service content of the abnormal node; S2422: Score each neighboring node of the abnormal node. The scoring mechanism adopts a weighted approach. The scoring function of a specific node is: F=Aa+Bb+Cc+···+Nn; Among them, F is the score value of a node, A represents the first parameter of a node, a is the weight ratio of A; B represents the second parameter of a node, b is the weight ratio of B; C represents the third parameter of a node, and c is the weight ratio of C; N represents the Nth parameter of a node, and n is the weight ratio of N; The first parameter is resource utilization, the second parameter is network latency, the third parameter is service dependency, and the Nth parameter is the service type of the abnormal node; S2423: According to the score of each node in step S2422, select the node with the highest score as the node to be migrated; Step S4 includes the following specific processes: S41: Perform intelligent network partitioning, monitor network status and load in real time, and intelligently adjust the location of container instances; S42: elastically configure the network to monitor network requirements, and dynamically adjust network resources on the container instance. The dynamic adjustment process includes adjusting bandwidth or allocating IP addresses. S43: Pool the storage resources in the cluster to form a storage pool, which includes a distributed file system, a distributed database, and object storage. According to the preset storage strategy, the stored data is divided into different storage levels based on access frequency and importance. The storage levels include hot and cold data separation, a cache layer, and persistent storage. The storage volume is mounted or unmounted as needed to perform dynamic storage management.

2. A scalable and highly available containerization method according to claim 1, characterized in that: The design of various automation tools for the user interface of the server in step S1 includes the following processes: S11: Graphically display the topology, service status, and resource utilization of the entire containerized server architecture; S12: Provides interactive interface elements to enable starting or stopping container instances or adjusting resource quotas by clicking icons or buttons; S13: Acquire system status information in real time and update the data of the user interface in real time; S14: Analyze the real-time status information and historical data of the system and provide configuration suggestions for the user interface; S15: Set up different roles, including administrators, developers, and operation and maintenance personnel, and assign different operation permissions to different roles.

3. A scalable and highly available containerized server, characterized in that: It includes cluster management and automation module, resource dynamic adjustment module, network configuration module, storage configuration module, data acquisition module and user interface design module; The cluster management and automation module is used to initialize the server cluster and automatically manage the nodes, deploy health checks and self-healing mechanisms for each node, perform active or passive health checks on each node, and automatically migrate the services of the failed node to other available nodes; The resource dynamic adjustment module performs intelligent container orchestration and dynamic resource allocation during the automatic management process, so that the container instance can dynamically adjust the resources it occupies during runtime; The network configuration module is used to automatically and dynamically configure network rules based on a service grid or a microservice proxy or a cloud native network; The storage configuration module is used to specify storage policies according to application requirements and dynamically adjust storage capacity based on the storage policies; The data collection module is used to collect various parameters and operation status data of the server system and container instance in real time; The user interface design module is used to design the user interface, to graphically display the topology, service status and resource utilization of the entire containerized server architecture, and to provide interactive interface elements and automated deployment tools; The specific process of the cluster management and automation module initializing the server cluster and automatically managing the nodes, deploying the health check and self-healing mechanism of each node, performing active or passive health check on each node, and automatically migrating the services of the failed node to other available nodes is as follows: Initialize the server cluster; Monitor in real time whether there are new server node requests. If so, add the new server node to the cluster; Based on the HTTP protocol, the TCP protocol, or the UDP protocol, the operation status of each node in the service cluster is monitored to determine whether there is an abnormality. If so, step S24 is executed. If not, each node keeps running continuously. Migrate services on abnormal nodes to other adjacent available nodes to automatically replace faulty nodes and perform automatic or manual maintenance on abnormal nodes; Migrate the services on the abnormal node to other adjacent available nodes to automatically replace the faulty node. The specific process of automatic or manual maintenance of the abnormal node is as follows: Save and synchronize the status information and related data of the services on the abnormal nodes; Real-time detection of the resource occupancy and operating status of adjacent nodes, and selection of nodes to be migrated based on the resource occupancy and operating status, and the corresponding service types in the abnormal nodes; Migrate the service of the abnormal node to the selected node of the migrated service, and continuously process the migrated service by selecting the node of the migrated service; The nodes to be migrated are selected using a scoring mechanism. The specific process is as follows: Analyze the service content of abnormal nodes; Each adjacent node of the abnormal node is scored. The scoring mechanism adopts a weighted approach. The scoring function of a specific node is: F=Aa+Bb+Cc+···+Nn; Among them, F is the score value of a node, A represents the first parameter of a node, a is the weight ratio of A; B represents the second parameter of a node, b is the weight ratio of B; C represents the third parameter of a node, c is the weight ratio of C; N represents the Nth parameter of a node, n is the weight ratio of N; The first parameter is resource utilization, the second parameter is network latency, the third parameter is service dependency, and the Nth parameter is the service type of the abnormal node; According to the score of each node, the node with the highest score is selected as the node to be migrated. Real-time detection of server communication requirements and automatic dynamic configuration of network rules based on service mesh, microservice proxy, or cloud native network include the following specific processes: Perform intelligent network partitioning, monitor network status and load in real time, and intelligently adjust the location of container instances; Flexible network configuration to monitor network requirements. Container instances dynamically adjust network resources, including bandwidth adjustment or IP address allocation. The storage resources in the cluster are pooled to form a storage pool, which includes a distributed file system, a distributed database, and object storage. According to the preset storage strategy, the stored data is divided into different storage levels based on access frequency and importance. The storage levels include hot and cold data separation, cache layer, and persistent storage. Storage volumes are mounted or unmounted as needed for dynamic storage management.

4. A scalable and highly available containerized server according to claim 3, characterized in that: The various parameters in the operation of the server system include CPU usage, memory usage, and disk I / O; the operation status data of the service include service availability, response time, and error rate; and the status data of the container instance includes operation status, start time, and stop time.

Citation Information

Patent Citations

  • Automatic scaling and migration scheduling method, system and device for containerization micro-service

    CN106330576A

  • Service credible providing system and method for decentralized network resources

    CN116016550A

  • MySQL database containerization cluster management platform and electronic equipment

    CN117215717A

  • Automated Elastic Resource Management of a Container System by a Distributed Storage System

    US20240220109A1