Customized service management method and device for power station server

Abstract

The embodiment of the invention provides a customized service management method and device for a power station server, and relates to the technical field of containerization operation and maintenance, and the method comprises the steps: obtaining the actual operation condition and demands of the power station server; determining the service operation type of each container in the power station server by using a pre-constructed three-dimensional container classification matrix and the actual operation condition and demand of the power station server; and realizing customized service management according to the service operation type of each container in the power station server.

Description

Technical Field

[0001] This application relates to the field of containerized operation and maintenance technology, and in particular to a customized service management method and apparatus for a power plant server. Background Technology

[0002] With the continuous development of power plant data synchronization services, containerization technology has been widely used in power plant data processing and management. However, in actual operation, due to various reasons such as system failures and data updates, it is necessary to restart services within containers. Most existing container service restart methods lack specificity and cannot customize restarts based on the characteristics and needs of different containers, resulting in low restart efficiency and potentially affecting the accuracy and stability of power plant data synchronization. In existing power plant data synchronization systems, servers face numerous severe technical challenges:

[0003] Multi-container service startup order dependency issue: Multiple container services in a power plant server have complex startup order dependencies. Traditional unified restart methods often ignore these dependencies, which can easily lead to data loss, affect the accuracy and integrity of power plant data, and thus adversely affect the power plant's operational decisions.

[0004] Synchronization process remnants can lead to duplicate data collection, increasing server load and reducing data processing efficiency. Furthermore, duplicate data may interfere with data analysis results, causing deviations in power plant monitoring and management.

[0005] Alarm service and data acquisition service conflict: The startup sequence of alarm service and data acquisition service may conflict, which may result in important alarm information not being delivered in a timely manner or data acquisition being incomplete, affecting the power plant's timely detection and handling of potential risks.

[0006] The challenge of regionally differentiated container cluster configuration: Power plant servers in different regions have varying configuration requirements for container clusters. Traditional technologies lack the ability to provide differentiated configurations for regional container clusters, failing to meet the specific needs of different power plants and reducing the system's adaptability and flexibility. Summary of the Invention

[0007] In view of this, embodiments of this application provide a customized service management method for a power plant server. One or more embodiments of this application also relate to a customized service management device for a power plant server, a computing device, a computer-readable storage medium, and a computer program, to address the technical deficiencies existing in the prior art.

[0008] According to a first aspect of the embodiments of this application, a customized service management method for a power station server is provided, comprising:

[0009] Obtain the actual operating status and requirements of the power station server;

[0010] Using a pre-constructed three-dimensional container classification matrix and the actual operation and requirements of the power station server, the service operation type of each container in the power station server is determined;

[0011] Customized service management is implemented based on the service operation type of each container in the power plant server.

[0012] Preferably, the pre-constructed three-dimensional container classification matrix includes:

[0013] By classifying containers in the power station server from the dimensions of function, region, and service level, a three-dimensional container classification matrix of the power station server is constructed.

[0014] Preferably, it also includes service stop, start, and restart operations for a single container, specifically including:

[0015] After the script starts, it checks if any command-line arguments have been passed in.

[0016] If command-line arguments are passed in, the corresponding single-container operation is performed according to the type of the argument in the command line;

[0017] If no command-line arguments are passed, the menu interface is displayed, and the corresponding single-container operation is executed by receiving the user's operation on the menu interface.

[0018] Preferably, it further includes:

[0019] By monitoring the start / stop status, service process status, and data channel status of each container in the power station server in real time, it is determined whether any of the start / stop status, service process status, and data channel status of each container in the power station server is abnormal.

[0020] If any abnormality is detected in the start / stop status, service process status, or data channel status of each container in the power plant server, a time-sequential alarm service will be activated to ensure the stable operation of the power plant server.

[0021] Preferably, it further includes:

[0022] When the service operation type of any container in the power plant server is to stop service, before stopping the container service, the auxiliary programs that include process cleanup and system tool state freezing are stopped first, and then the core program is stopped.

[0023] Preferably, it further includes:

[0024] When the service operation type of any container in the power plant server is a restart service, the restart service is performed using a layered restart and dynamic command injection method.

[0025] The layered restart method involves restarting Docker first, followed by restarting the container service.

[0026] The dynamic command injection method involves extending and customizing a pre-built, extensible command template library to adjust the startup command according to container requirements.

[0027] According to a second aspect of the embodiments of this application, a customized service management device for a power station server is provided, comprising:

[0028] The acquisition module is configured to acquire the actual operating status and requirements of the power station server.

[0029] The determination module is configured to determine the service operation type of each container in the power station server using a pre-built three-dimensional container classification matrix and the actual operation and requirements of the power station server.

[0030] The service management module is configured to implement customized service management based on the service operation type of each container in the power plant server.

[0031] Preferably, the pre-constructed three-dimensional container classification matrix includes:

[0032] By classifying containers in the power station server from the dimensions of function, region, and service level, a three-dimensional container classification matrix of the power station server is constructed.

[0033] According to a third aspect of the embodiments of this application, a computing device is provided, comprising:

[0034] Memory and processor;

[0035] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement any of the steps of the customized service management method of the power station server.

[0036] According to a fourth aspect of the embodiments of this application, a computer-readable storage medium is provided that stores computer-executable instructions, which, when executed by a processor, implement the steps of any of the customized service management methods for a power plant server.

[0037] According to a fifth aspect of the embodiments of this application, a computer program is provided, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the customized service management method for the power plant server described above.

[0038] The customized service management scheme for power plant servers provided in this application embodiment obtains the actual operating status and requirements of the power plant server; utilizes a pre-constructed three-dimensional container classification matrix and the actual operating status and requirements of the power plant server to determine the service operation type of each container in the power plant server; and implements customized service management based on the service operation type of each container in the power plant server. The customized service management scheme for power plant servers provided in this application embodiment can flexibly manage services within containers by stopping, restarting, and starting them according to the needs of different containers, improving the efficiency and accuracy of service restarts and ensuring the stable operation of power plant data synchronization. Attached Figure Description

[0039] Figure 1 This is a flowchart illustrating a customized service management method for a power station server according to one embodiment of this application;

[0040] Figure 2 This is an overall flowchart of a customized service management method for a power station server provided in one embodiment of this application;

[0041] Figure 3 This is a schematic diagram of a customized service management device for a power station server provided in one embodiment of this application;

[0042] Figure 4 This is a structural block diagram of a computing device provided in one embodiment of this application. Detailed Implementation

[0043] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0044] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” used in one or more embodiments of this application and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” used in one or more embodiments of this application refers to and includes any or all possible combinations of one or more associated listed items.

[0045] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this application, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0046] This application provides a customized service management method for a power station server. This application also relates to a customized service management device for a power station server, a computing device, a computer-readable storage medium, and a computer program, which will be described in detail in the following embodiments.

[0047] Figure 1 A flowchart is shown of a customized service management method for a power station server according to an embodiment of this application, which specifically includes the following steps.

[0048] Step S101: Obtain the actual operating status and requirements of the power station server;

[0049] The actual operating conditions mentioned above include at least the geographical region where the power station server is located, the functional type and service level of the frequency regulation data or peak regulation data, and the power station meter data.

[0050] Step S102: Using the pre-constructed three-dimensional container classification matrix and the actual operation and requirements of the power station server, determine the service operation type of each container in the power station server;

[0051] In one embodiment of this application, the pre-constructed three-dimensional container classification matrix includes: classifying the containers in the power station server from functional dimensions, geographical dimensions, and service level dimensions to construct a three-dimensional container classification matrix for the power station server.

[0052] In other words, a dynamic grouping and coupling mechanism is provided to establish a three-dimensional container classification matrix, comprehensively classifying containers from functional, geographical, and service level dimensions. This classification method fully considers the diversity and complexity of power station servers, and can more accurately meet the needs of different servers. Specifically, the dynamic matrix grouping can flexibly group according to function, region, and service level. Each power station generates a separate electricity meter upon initial deployment. When the program runs, it reads the corresponding electricity meter, automatically groups the devices by function and region based on the meter values, and generates different management commands for each power station, improving the system's adaptability and flexibility.

[0053] Grouping strategies, such as `specific_containers`, are dynamically loaded through configuration files. This allows the system to flexibly adjust grouping strategies based on the actual operating conditions and needs of the power plant, improving system adaptability and scalability. Furthermore, cascading control of groups is implemented; for example, when the `tpBinhai*` group is linked, it inherits the region configuration parameters. This cascading control method ensures that containers in the same region have consistent configuration and management strategies, improving the overall stability and management efficiency of the system.

[0054] Step S103: Implement customized service management based on the service operation type of each container in the power station server.

[0055] In one embodiment of this application, the method further includes stopping, starting, and restarting services for a single container. Specifically, this includes: after the script starts, determining whether command-line arguments are passed in; if command-line arguments are passed in, performing the corresponding single container operation according to the parameter type in the command line; if no command-line arguments are passed in, displaying a menu interface, and selecting to perform the corresponding single container operation by receiving the user's operation on the menu interface.

[0056] After the script starts, it first checks if any command-line arguments have been passed in;

[0057] If no parameters are provided, a menu interface will be displayed, allowing users to select different operations, including stopping the service, restarting Docker, starting the service, restarting all services, or exiting.

[0058] If there are parameters, perform the corresponding single-container operation based on the parameter type.

[0059] Service stopped: auto_recontain-s name

[0060] Stop the power plant data acquisition program named name and shut down the container.

[0061] Service startup: auto_recontain -o name

[0062] Start the power plant data acquisition program named name and automatically generate a container.

[0063] Service startup: auto_recontain -r name

[0064] First, stop the power plant data acquisition program named 'name' and close the container. After confirming that the shutdown is complete and there are no program remnants, start the power plant data acquisition program named 'name' and automatically create the container.

[0065] Error checking is performed at each step of the operation. If the operation is successful, a success message is output; otherwise, a failure message is output and the script exits.

[0066] The system employs a "stack-based shutdown" mechanism when stopping services, stopping auxiliary programs first and then shutting down the core program. Successful service exit is only confirmed after the core program has exited, ensuring a normal exit for the core program. Conversely, a "transactional startup" mechanism is used when starting services, starting the core program first and then the auxiliary programs. Completion is only confirmed after all programs have started successfully; otherwise, it fails and all operations are rolled back. This ingenious design maintains the atomicity of the power station's edge services, preventing situations where data generation fails to write or data writing results in alarms due to partial service startup failures, thus ensuring high stability of the power station's data.

[0067] In one embodiment of this application, the method further includes: real-time monitoring of the start / stop status, service process status, and data channel status of each container in the power plant server to determine whether any of the start / stop status, service process status, and data channel status of each container in the power plant server is abnormal; if any of the start / stop status, service process status, and data channel status of each container in the power plant server is determined to be abnormal, a time-sequential alarm service is initiated to ensure the stable operation of the power plant server.

[0068] By designing a three-level status verification system, comprehensive monitoring is achieved from container start / stop status and service process status to data channel status (Redis). This hierarchical status verification can promptly detect and handle anomalies in the system, ensuring the stable operation of the power plant server. By capturing anomalies, fault isolation is achieved, preventing anomalies from impacting the entire system. Fault isolation improves system reliability and stability, reducing the impact of faults on power plant operation.

[0069] In one embodiment of this application, it further includes: when the service operation type of any container in the power plant server is to stop service, before stopping the container service, the auxiliary programs including process cleanup and system tool state freezing are stopped first, and then the core program is stopped.

[0070] In other words, the pre-stop double-insurance mechanism employs a "reverse cleanup" process and double-insurance to remove residual processes, ensuring the rational use of server resources. Specifically, process termination → state freezing → resource release → container shutdown ensures that residual processes are thoroughly removed when container services are stopped, avoiding duplicate data collection and resource waste, while improving the reliability and effectiveness of process cleanup.

[0071] In one embodiment of this application, the method further includes: when the service operation type of any container in the power plant server is to restart the service, the service is restarted using a layered restart and dynamic command injection method; wherein the layered restart method is to restart Docker first, and then restart the container service; the dynamic command injection method is to extend and customize the system through a pre-built extensible command template library, thereby adjusting the startup command according to the container requirements.

[0072] This includes building an extensible command template library, such as the `start_warning` function. The command template library can be extended and customized according to different needs, providing a rich selection for dynamic command injection. Dynamic template injection allows for flexible adjustment of the startup command based on container requirements, enabling customized service restarts.

[0073] This system enables dynamic binding of commands to containers by parsing the entry array and applying the appropriate command to the corresponding container. This dynamic binding method allows for flexible adjustment of the startup command based on the actual needs of the container, improving the accuracy of service restarts. Runtime parameter replacement is supported, such as dynamic assignment of `--station` and `--name` parameters. This enables commands to be dynamically adjusted according to actual conditions, further enhancing the system's flexibility and adaptability.

[0074] The customized service management solution for the power plant server provided in this application embodiment can flexibly manage the services within the container by stopping, restarting, and starting them according to the needs of different containers, thereby improving the efficiency and accuracy of service restart and ensuring the stable operation of power plant data synchronization.

[0075] In one embodiment of this application, the power station server mainly consists of the following parts:

[0076] The container information management module stores and manages information related to power plant data synchronization containers, including container names and corresponding service startup commands. It stores container information using arrays `containers` and `specific_containers`. The `containers` array stores the names of all containers that need to be managed, while the `specific_containers` array stores the service startup command for each container.

[0077] The service operation module is responsible for stopping, restarting, and starting services within the container. This module contains several functions: `stop_service` to stop services within the container, `restart_docker` to restart the Docker service, `start_service` to start services within the container, `start_redis` to start Redis-related services within the container, and `start_warning` to start specific warning services.

[0078] Menu interaction module: Provides users with an interactive menu to facilitate the selection of different operations. Users can choose to stop the service, restart Docker, start the service, restart all services, or exit as needed.

[0079] It also provides a hybrid restart mode, including full mode (stop_service → restart_docker → start_service) and incremental mode (single container cascading operation, via -s / -o / -r parameters). Full mode is suitable for system-wide restarts, while incremental mode allows for flexible operation on individual containers, improving system operation and maintenance efficiency.

[0080] Establish a restart transaction log to support breakpoint resumption. The restart transaction log can record key information during the restart process, ensuring that execution can continue from the breakpoint if an exception occurs during restart, thus improving system reliability and operational efficiency.

[0081] Single container operation module: Supports stopping, starting, and restarting services for a single container. The command-line parameters -s, -o, and -r are used to stop, start, and restart services for a single container, respectively.

[0082] This invention also constructs a complete intelligent management and control system architecture for implementing containerized services on power plant servers, specifically including the following modules:

[0083] The dynamic container grouping management module groups containers by function type (e.g., frequency regulation data, peak regulation data) and geographical region (e.g., Guizhou, coastal areas, etc.). This fully considers the actual operating characteristics of power plant servers, as different functional containers and servers in different regions have different operational requirements and characteristics. Grouping management allows for more precise configuration and management of containers. Containers of different functional types and in different regions typically have different parameters configured; for example, peak regulation data needs to be stored in Redis1 database, frequency regulation data in Redis2 database, and Guizhou power plants require separate scheduled tasks, thus improving the system's adaptability and flexibility.

[0084] Pre-stop processing engine: Before stopping the container service, process cleanup (removing Python synchronization remnants) and system tool state freezing (systool) are performed. This "reverse cleanup" process effectively avoids synchronization process remnants, ensures the rational use of server resources, reduces the risk of duplicate data collection, and improves the accuracy and efficiency of data processing.

[0085] The intelligent restart control module employs layered restart (restarting Docker first, then the service) and dynamic command injection. Layered restart ensures the stable startup of the server's basic environment and services, avoiding data loss and service conflicts caused by improper startup order. Dynamic command injection allows for flexible adjustment of startup commands based on the needs of different containers, enabling customized service restarts. For example, ordinary containers in coastal areas only need to have their startup data stored in the database (corresponding to the customized startup command `start_service`). Special container groups in Guizhou require frequency regulation and peak shaving data to be stored separately in the database, followed by starting scheduled tasks and alarm programs (corresponding to the customized startup commands `start_service`, `start_redis`, and `start_warning`).

[0086] Status monitoring and alarm integration: This includes Redis cache preheating and the startup of time-series alarm services. By performing three-level status verification on container start / stop status, service process status, and data channel status (Redis), abnormal situations can be detected and handled promptly. Simultaneously, the startup of time-series alarm services ensures that important alarm information is delivered in a timely manner, improving the power plant's responsiveness to potential risks.

[0087] Figure 2 The diagram illustrates a process flow of a customized service management method for a power station server according to an embodiment of this application, which specifically includes the following steps.

[0088] 1. Automatically retrieve the latest electricity meter readings from each power station server at 1:00 AM every day.

[0089] 2. Based on the electricity meters of each power station server, automatically group and initialize the scheduled task array and alarm array. For example, frequency regulation is initialized to the Redis1 database, peak regulation is initialized to the Redis2 database, and special data is initialized to the Redis0 database. Guizhou initializes the alarm array, while Binhai does not need customized alarms, so the corresponding alarms are not initialized.

[0090] 3. Control individual containers for individual power station servers according to requirements, or control all power station containers in batches according to business needs.

[0091] 4. The control logic is based on the meter initialization function. Each container gracefully stops its service first. The stopping is done in a stack manner, with the program that starts first stopping last. This ensures that the core program stops last, avoiding the core program stopping first, which could cause a false crash and lead to incorrect data transmission by the synchronous program, resulting in missing or incorrect data.

[0092] 5. Determine if the program exited correctly and record the log.

[0093] 6. After the program exits, restart the Docker service and refresh the network and configuration.

[0094] 7. Based on the electricity meters of each power station server, initialize the scheduled task array and alarm array, perform customized startup of each power station server container and service program, and record the startup log.

[0095] Figure 3 This illustration shows a schematic diagram of the structure of a customized service management device for a power station server according to an embodiment of this application. Figure 3 As shown, the device includes:

[0096] The acquisition module is configured to acquire the actual operating status and requirements of the power station server.

[0097] The determination module is configured to determine the service operation type of each container in the power station server using a pre-built three-dimensional container classification matrix and the actual operation and requirements of the power station server.

[0098] The service management module is configured to implement customized service management based on the service operation type of each container in the power plant server.

[0099] In one embodiment of this application, the pre-constructed three-dimensional container classification matrix includes:

[0100] By classifying containers in the power station server from the dimensions of function, region, and service level, a three-dimensional container classification matrix of the power station server is constructed.

[0101] In summary, this application offers the following beneficial effects: 1) Significantly improved operational efficiency: Through innovative mechanisms such as dynamic group management, layered restart, and incremental restart control, the time required for a single full operation is reduced to 3-5 minutes. This greatly shortens server downtime, reduces the impact on the normal operation of the power plant, and improves operational efficiency. 2) Significantly improved data integrity: Through a pre-stop processing engine and a hierarchical status monitoring system, employing a "reverse cleanup" process and three-level status verification, the data loss rate is reduced to 0.05%. This ensures the accuracy and integrity of power plant data, providing a reliable basis for power plant operational decisions. 3) Greatly enhanced system reliability: Through a hierarchical status monitoring system and fault isolation mechanism, the anomaly detection coverage is increased to 99.3%. Simultaneously, the establishment of a restart transaction log supports breakpoint resumption, effectively avoiding the impact of abnormal situations on the system and improving system reliability and stability. 4) Significantly optimized resource utilization: By clearing residual processes through the pre-stop processing engine, memory leaks and peak CPU load are reduced, improving server resource utilization and lowering operating costs.

[0102] Figure 4 A structural block diagram of a computing device 400 according to an embodiment of this application is shown. The components of the computing device 400 include, but are not limited to, a memory 410 and a processor 420. The processor 420 is connected to the memory 410 via a bus 430, and a database 450 is used to store data.

[0103] The computing device 400 also includes an access device 440, which enables the computing device 400 to communicate via one or more networks 460. Examples of these networks include a Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 440 may include one or more of any type of wired or wireless network interface (e.g., a Network Interface Card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) interface, a Wi-MAX interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0104] In one embodiment of this application, the aforementioned components of the computing device 400 and Figure 4 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 4 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0105] The computing device 400 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs. The computing device 400 can also be a mobile or stationary server.

[0106] The processor 420 is used to execute the following computer-executable instructions, which, when executed by the processor, implement the steps of the customized service management method for the power plant server described above.

[0107] An embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the customized service management method for the power plant server described above.

[0108] An embodiment of this application also provides a computer program, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the customized service management method for the power plant server described above.

[0109] The preferred embodiments of the present invention have been described above with reference to the accompanying drawings, but this does not limit the scope of the invention. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of the present invention should be within the scope of the present invention.

Claims

1. A customized service management method for a power station server, characterized in that, include: Obtain the actual operating status and requirements of the power station server; Using a pre-constructed three-dimensional container classification matrix and the actual operation and requirements of the power station server, the service operation type of each container in the power station server is determined; Customized service management is implemented based on the service operation type of each container in the power plant server.

2. The method according to claim 1, characterized in that, The pre-constructed three-dimensional container classification matrix includes: By classifying containers in the power station server from the dimensions of function, region, and service level, a three-dimensional container classification matrix of the power station server is constructed.

3. The method according to claim 1, characterized in that, It also includes stopping, starting, and restarting services for a single container, specifically including: After the script starts, it checks if any command-line arguments have been passed in. If command-line arguments are passed in, the corresponding single-container operation is performed according to the type of the argument in the command line; If no command-line arguments are passed, the menu interface is displayed, and the corresponding single-container operation is executed by receiving the user's operation on the menu interface.

4. The method according to claim 1, characterized in that, Also includes: By monitoring the start / stop status, service process status, and data channel status of each container in the power station server in real time, it is determined whether any of the start / stop status, service process status, and data channel status of each container in the power station server is abnormal. If any abnormality is detected in the start / stop status, service process status, or data channel status of each container in the power plant server, a time-sequential alarm service will be activated to ensure the stable operation of the power plant server.

5. The method according to claim 1, characterized in that, Also includes: When the service operation type of any container in the power plant server is to stop service, before stopping the container service, the auxiliary programs that include process cleanup and system tool state freezing are stopped first, and then the core program is stopped.

6. The method according to claim 1, characterized in that, Also includes: When the service operation type of any container in the power plant server is a restart service, the restart service is performed using a layered restart and dynamic command injection method. The layered restart method involves restarting Docker first, followed by restarting the container service. The dynamic command injection method involves extending and customizing a pre-built, extensible command template library to adjust the startup command according to container requirements.

7. A customized service management device for a power station server, characterized in that, include: The acquisition module is configured to acquire the actual operating status and requirements of the power station server. The determination module is configured to determine the service operation type of each container in the power station server using a pre-built three-dimensional container classification matrix and the actual operation and requirements of the power station server. The service management module is configured to implement customized service management based on the service operation type of each container in the power plant server.

8. The apparatus according to claim 7, characterized in that, The pre-constructed three-dimensional container classification matrix includes: By classifying containers in the power station server from the dimensions of function, region, and service level, a three-dimensional container classification matrix of the power station server is constructed.

9. A computing device, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, they implement the steps of the customized service management method of the power station server according to any one of claims 1 to 6.

10. A computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the customized service management method of the power station server according to any one of claims 1 to 6.

Images