Workload management method and system, computer equipment and storage medium

Abstract

The invention relates to a workload management method and system, computer equipment and a storage medium. The method comprises the following steps: any management object only needs to configure a management plan corresponding to a target workload through a workload management system; according to the embodiment of the invention, the to-be-updated expected configuration rules of the target workload are read from the database according to the updating scheme corresponding to the triggering mode to form the target to-be-updated list, and the target workload is automatically updated by executing each expected configuration rule in the target to-be-updated list, so that the workload does not need to be manually adjusted; even if a plurality of different management objects have different management plans for the same workload, the related expected configuration rules are automatically read according to the update schemes corresponding to different trigger modes for unified update, so that repeated update of the workload in a change time window is avoided.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a workload management method, system, computer device, and storage medium. Background Art

[0002] Kubernetes is an open-source container orchestration system for automating the deployment, scaling, and management of containerized applications. Currently, workloads in Kubernetes clusters are often managed manually using different management objects. This involves manually identifying and adjusting workloads, and changes are typically implemented in batches. This manual effort, coupled with the effort required to schedule and implement changes, results in low workload management efficiency and high costs.

[0003] In addition, different management objects have different management plans for the same workload. For example, the business operation and maintenance party and the cluster operation and maintenance party have their own change adjustment plans, and each party wants to monopolize the change time window. When both parties perform operation and maintenance management on the same workload at the same time, there may be multiple continuous rolling updates within the change time window, which may extend the update time and cause problems such as application crashes, service interruptions, or performance degradation. Summary of the Invention

[0004] The present application provides a workload management method, system, computer device and storage medium to solve the problems of low workload management efficiency caused by manual workload adjustment, and the problems of extended update time, application crashes, service interruptions or performance degradation caused by multiple parties operating the same workload at the same time.

[0005] In order to solve the above technical problems or at least partially solve the above technical problems, the present application provides a workload management method, system, computer device and storage medium.

[0006] In one aspect, the present application provides a workload management method, the method further comprising:

[0007] Upon receiving management plans for target workload configurations from different management objects, saving the management plans corresponding to the target workloads into a database, wherein the management plans include at least one expected configuration rule, and the expected configuration rule is used to adjust operating parameters of the corresponding workloads;

[0008] When an update condition corresponding to the target workload is triggered within a change time window, the desired configuration rules related to the target workload are read from the database according to an update scheme corresponding to the triggering method to form a target to-be-updated list;

[0009] Each expected configuration rule in the target to-be-updated list is merged with the current configuration rule of the target workload and then implemented.

[0010] In another aspect, the present application provides a workload management system, comprising:

[0011] a storage module configured to, upon receiving a management plan for configuring a target workload from different management objects, save the management plan corresponding to the target workload into a database, wherein the management plan includes at least one expected configuration rule, and the expected configuration rule is used to adjust an operating parameter of the corresponding workload;

[0012] a processing module configured to, when an update condition corresponding to the target workload is triggered within a change time window, read expected configuration rules related to the target workload from the database according to an update scheme corresponding to the triggering method to form a target to-be-updated list;

[0013] The updating module is used to merge and implement each expected configuration rule in the target to-be-updated list with the current configuration rule of the target workload.

[0014] On the other hand, a computer device is provided, comprising a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0015] Memory for storing computer programs;

[0016] The processor is configured to implement the workload management method described above when executing a program stored in the memory.

[0017] On the other hand, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the workload management method described above is implemented.

[0018] On the other hand, a computer program product is provided, comprising a computer program / instruction, which implements the workload management method described above when executed by a processor.

[0019] The above technical solution provided by the embodiment of the present application has the following advantages compared with the prior art:

[0020] The method provided in an embodiment of the present application saves the management plan corresponding to the target workload into a database when receiving a management plan for configuring a target workload from different management objects, wherein the management plan includes at least one expected configuration rule, and the expected configuration rule is used to adjust the operating parameters of the corresponding workload; when the update condition corresponding to the target workload is triggered within the change time window, the expected configuration rules related to the target workload are read from the database according to the update scheme corresponding to the triggering method to form a target list to be updated; each expected configuration rule in the target list to be updated is merged with the current configuration rule of the target workload and then implemented.

[0021] Based on the above method, any management object only needs to configure the management plan corresponding to the target workload through the workload management system. When the update condition corresponding to the target workload is triggered, the expected configuration rules to be updated of the target workload will be read from the database according to the update scheme corresponding to the triggering method to form a target list to be updated, and the target workload will be automatically updated by executing each expected configuration rule in the target list to be updated. There is no need to manually adjust the workload. Even if multiple different management objects have different management plans for the same workload, as long as the relevant expected configuration rules are automatically read according to the update scheme corresponding to different triggering methods, they can be updated uniformly, thereby avoiding multiple updates to the workload within the change time window. This solves the problems of low workload management efficiency caused by manual adjustment of the workload, and the problems of extended update time, application crashes, service interruptions or performance degradation caused by multiple parties operating and maintaining the same workload at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0023] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0024] Figure 1 A schematic diagram of the structure of a workload management system provided in an embodiment of the present application;

[0025] Figure 2 A flowchart of a workload management method provided in an embodiment of the present application;

[0026] Figure 3 A flowchart of a workload management method provided in an embodiment of the present application;

[0027] Figure 4 A flowchart of a workload management method provided in an embodiment of the present application;

[0028] Figure 5 A flowchart of a workload management method provided in an embodiment of the present application;

[0029] Figure 6 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0031] Figure 1 FIG. 1 is a schematic diagram of the structure of a workload management system in one embodiment. Figure 1 The workload management method is applied to a workload management system. The workload management system includes a configuration maintenance system 110, an admission controller 120, a maintenance terminal 130, a database 140, and a Kubernetes cluster 150. The Kubernetes cluster 150 includes at least one workload. The maintenance terminal 130 is a terminal used by maintenance personnel (different management objects), wherein:

[0032] The configuration maintenance system 110 is configured to, upon receiving a management plan for configuring a target workload from different management objects, save the management plan corresponding to the target workload to the database 140, wherein the management plan includes at least one desired configuration rule, and the desired configuration rule is used to adjust the operating parameters of the corresponding workload;

[0033] A management module is used to read out the expected configuration rules related to the target workload from the database 140 according to the update scheme corresponding to the triggering method to form a target list to be updated when the update condition corresponding to the target workload is triggered within the change time window; each expected configuration rule in the target list to be updated is merged with the current configuration rules of the target workload and then implemented, wherein the management module is the configuration maintenance system 110 or the admission controller 120 under different triggering methods.

[0034] Specifically, if the update condition corresponding to the target workload is externally triggered, the admission controller 120 reads the desired configuration rules related to the target workload from the database 140 according to the corresponding update plan to form a target list to be updated. If the update condition corresponding to the target workload is not externally triggered, the configuration maintenance system 110 reads the desired configuration rules related to the target workload from the database 140 according to the corresponding update plan to form a target list to be updated.

[0035] The configuration maintenance system 110 can be implemented using an independent server or a server cluster consisting of multiple servers, that is, it has the data entry function of saving the management plan to the database 140, and also has the workload update function when the workload update is triggered externally.

[0036] In one embodiment, Figure 2 A flowchart of a workload management method in one embodiment is shown in FIG. Figure 2 , provides a workload management method. This embodiment mainly uses the method applied to a workload management system as an example to illustrate, and the workload management method specifically includes the following steps:

[0037] Step S210, when receiving the management plan for configuring the target workload by different management objects, the management plan corresponding to the target workload is saved in the database 140, wherein the management plan includes at least one expected configuration rule, and the expected configuration rule is used to adjust the operating parameters of the corresponding workload.

[0038] Specifically, different management objects have different management requirements for the same workload. Different management objects include at least the business operation and maintenance party and the cluster operation and maintenance party of the Kubernetes cluster 150. Different management objects configure the management plan for the workload by logging into the configuration maintenance system 110. The management plan includes expected configuration rules, implementation conditions and implementation methods. The expected configuration rules define how the workload (such as Deployment, StatefulSet, etc.) should run. These rules cover many aspects, such as the image version of the container, resource requests and restrictions, environment variables, mounted storage volumes, etc. In this embodiment, the expected configuration rules specifically include workload definition modification, workload selection conditions, rule publishers, and modification-related remarks information, where the workload selection conditions include workload type, label conditions, and target state conditions.

[0039] Implementation conditions are the basis for determining whether a desired configuration rule can be applied. These conditions may be based on time, resource availability, dependencies, and more. For example, you might set a desired configuration rule to be implemented only within a specific time window or when the available resources in the cluster meet a certain threshold. Alternatively, the update rule for a workload must be implemented only after the dependent services have been successfully deployed and running. In this embodiment, the implementation conditions specifically include the allowed or prohibited time window and whether the workload is currently in a grayscale version.

[0040] The implementation methods are divided into active implementation, passive implementation, and hybrid implementation. The implementation methods are used to indicate whether the triggering method for implementing the expected configuration rules is active triggering or passive triggering. Hybrid implementation is passive triggering when the preset trigger conditions are not met, and active triggering when the preset trigger conditions are met.

[0041] Step S220: When the update condition corresponding to the target workload is triggered within the change time window, the expected configuration rules related to the target workload are read from the database 140 according to the update scheme corresponding to the triggering method to form a target to-be-updated list.

[0042] Specifically, the triggering methods for triggering the update conditions corresponding to the target workload include active triggering and passive triggering. Different triggering methods correspond to different update schemes and different execution objects. In the case of passive triggering, the execution object used to generate the target list to be updated is the access controller 120, and in the case of active triggering, the execution object used to generate the target list to be updated is the configuration maintenance system 110. Different execution objects use different update schemes to read different expected configuration rules from the database 140 to form the target list to be updated, that is, different execution objects generate different target lists to be updated. Based on different triggering methods, the expected configuration rules configured for the same target workload by different management objects can be implemented and judged to form a unified target list to be updated, that is, multiple expected configuration rules in the target list to be updated may come from the business operation and maintenance party configuration, or may come from the cluster operation and maintenance party configuration. Within the same change time window, multiple expected configuration rules of different workloads are uniformly updated according to the target list to be updated, avoiding multiple updates to the same workload within the change time window.

[0043] Step S230: Merge and implement each desired configuration rule in the target to-be-updated list with the current configuration rule of the target workload.

[0044] Specifically, each expected configuration rule in the target list to be updated is merged into the current configuration rule of the target workload, and the merged current configuration rule is executed to achieve an automatic update of the target workload. In the above process, there is no need for operation and maintenance personnel to manually update the workload, thereby improving the management efficiency of the workload and reducing the management cost of the workload. In addition, when multiple parties have different management plans for the same workload, the expected configuration rules configured by each management object are read from the database 140 according to the update scheme corresponding to the trigger method to form a target list to be updated, and then a unified update is performed based on the target list to be updated, avoiding different management objects wanting to seize the change time window or the need to negotiate the allocation of the change time window, and also avoiding multiple changes to the same workload within the same change time window, thereby solving the problem of low workload management efficiency caused by manual adjustment of the workload, and the problem of extended update time, application crash, service interruption or performance degradation caused by multiple parties operating the same workload at the same time.

[0045] In one embodiment, the management plan further includes an implementation method and implementation conditions. The implementation method is passive implementation, active implementation, or mixed implementation. When the update condition corresponding to the target workload is triggered within the change time window, the expected configuration rules related to the target workload are read from the database 140 according to the update scheme corresponding to the triggering method to form a target to-be-updated list, including:

[0046] When an update request corresponding to the target workload is received within the change time window, the expected configuration rules related to the target workload, whose implementation conditions are met and whose implementation method is passive implementation or hybrid implementation are read from the database 140 according to the passive update scheme to form a first list to be updated, wherein the target list to be updated is the first list to be updated.

[0047] Specifically, when an update request corresponding to the target workload is received within the change time window, the admission controller 120 intercepts the update request and reads the expected configuration rules corresponding to the target workload, which meet the implementation conditions and are implemented passively, from the database 140. The read expected configuration rules form a first list to be updated. The first list to be updated is the target list to be updated in the externally triggered workload update scenario. At this time, the first list to be updated also includes expected configuration rules from different management object configurations, that is, when reading the expected configuration rules, only the implementation methods and implementation conditions are used, and no screening is performed on the management objects. Therefore, the expected configuration rules of multiple different management object configurations can be uniformly updated when the above-mentioned screening conditions are met. There is no need for different management objects to occupy the change time window separately to update the same workload separately, which saves the communication cost of negotiating the change time window occupancy of different management objects, reduces the number of updates of the same workload, shortens the workload change time, avoids the risk of business downtime caused by multiple continuous updates of the workload, and improves the operation stability of the Kubernetes cluster 150.

[0048] In one embodiment, when an update request corresponding to the target workload is received within the change time window, the first to-be-updated list is formed by reading from the database 140 according to the passive update scheme the desired configuration rules related to the target workload, for which implementation conditions are met and the implementation method is passive implementation or hybrid implementation, including:

[0049] When an update request corresponding to the target workload is received within the change time window, desired configuration rules related to the target workload, having implementation conditions satisfied and implemented in a passive implementation or a hybrid implementation mode are read from the database 140 to form a first rule list;

[0050] Conflict merging is performed on multiple expected configuration rules in the first rule list to obtain the first list to be updated.

[0051] Specifically, refer to Figure 3The injection controller intercepts the update request corresponding to the target workload, reads multiple expected configuration rules that meet the implementation conditions from the database 140 to form a first candidate list, and then traverses and judges the implementation method of each expected configuration rule in the first candidate list, that is, takes out the expected configuration rules in the first candidate list to judge whether the implementation method is passive implementation or mixed implementation. If there are still expected configuration rules remaining in the first candidate list, it means that the traversal has not ended yet, then the expected configuration rules are taken out from the first candidate list to judge the implementation method. If the implementation method of the expected configuration rule taken out from the first candidate list is passive implementation or mixed implementation, the expected configuration rule is added to the first rule list until the traversal is completed. The multiple expected configuration rules in the first rule list are merged for conflict processing. Because multiple expected configuration rules may come from different sources, such as the strategy of the operation and maintenance team, the needs of the development team, etc., these different expected configuration rules need to be merged into a unified expected configuration.

[0052] During an implementation process, multiple expected configuration rules in the first rule list are merged according to a preset priority scheme, wherein the preset priority is determined according to the priority of the management object, the number of applications of the expected configuration rule, or the implementation importance level of the expected configuration rule.

[0053] During the merging process, it is necessary to deal with possible conflicts, such as different expected configuration rules having different requirements for the same configuration item. Usually, conflicts are resolved according to a preset priority scheme, such as giving priority to more specific or more important rules. The preset priority scheme includes a variety of different priority setting methods, such as giving priority to the expected configuration rules configured for management objects with higher priorities according to the priority of the management object, or giving priority to the expected configuration rules with more applications according to the number of applications of different expected configuration rules, or giving priority to the expected configuration rules with higher importance levels. Conflict merging processing is used to ensure that each expected configuration rule in the first list to be updated can be successfully implemented, so as to improve the update success rate of the workload.

[0054] In one embodiment, the management plan further includes an implementation method and implementation conditions. The implementation method is passive implementation, active implementation, or mixed implementation. When the update condition corresponding to the target workload is triggered within the change time window, the expected configuration rules related to the target workload are read from the database 140 according to the update scheme corresponding to the triggering method to form a target to-be-updated list, including:

[0055] When the active update condition corresponding to the target workload is triggered within the change time window, the expected configuration rules related to the target workload, whose implementation conditions are met and the implementation method is active implementation or mixed implementation are read from the database 140 according to the active update scheme to form a second list to be updated corresponding to the target workload, wherein the target list to be updated is the second list to be updated for the target workload pair.

[0056] Specifically, when the active update condition corresponding to the target workload is triggered within the change time window, the configuration maintenance system 110 reads the expected configuration rules related to the target workload, whose implementation conditions are met and whose implementation methods are passive implementation, active implementation or mixed implementation from the database 140 according to the active update plan to form a second list to be updated. The second list to be updated is the target list to be updated in the non-externally triggered workload update scenario. At this time, the second list to be updated also includes the expected configuration rules from different management object configurations, that is, when reading the expected configuration rules, only the implementation method and implementation conditions are used, and no screening is performed on the management object. Therefore, the expected configuration rules of multiple different management object configurations can be uniformly updated when the above-mentioned screening conditions are met. There is no need for different management objects to occupy the change time window separately to update the same workload separately, which saves the communication cost of negotiating the change time window occupancy of different management objects, reduces the number of updates of the same workload, shortens the workload change time, avoids the risk of business downtime caused by multiple continuous updates of the workload, and improves the operation stability of the Kubernetes cluster 150.

[0057] In one embodiment, when the active update condition corresponding to the target workload is triggered within the change time window, the desired configuration rules related to the target workload, for which the implementation conditions are met and the implementation method is active implementation or hybrid implementation, are read from the database 140 according to the active update scheme to form a second to-be-updated list corresponding to the target workload, including:

[0058] When a preset update time is reached within the change time window, the desired configuration rules whose implementation conditions are met and whose implementation mode is active implementation or hybrid implementation are read from the database 140 to form a second rule list, wherein the second rule list includes the desired configuration rules corresponding to the target workload;

[0059] Merging each desired configuration rule corresponding to the same workload in the second rule list to obtain a workload update list, wherein the workload update list includes desired configuration rules corresponding to a plurality of workloads to be updated, and the plurality of workloads to be updated include the target workload;

[0060] The expected configuration rules corresponding to each workload to be updated in the workload update list, whose implementation conditions are met and the implementation method is passive implementation, are read from the database 140 and added to the workload update list to obtain a merged update list, wherein the merged update list includes a second list to be updated corresponding to multiple workloads to be updated.

[0061] Specifically, the configuration maintenance system 110 reads out the expected configuration rules whose implementation conditions are met and whose implementation methods are active implementation or mixed implementation from the database 140 according to the active update scheme to form a second rule list, aggregates the expected configuration rules corresponding to the same workload in the second rule list to count multiple workloads to be updated, that is, identifies the corresponding workloads to be updated according to the multiple expected configuration rules to be updated, and forms a workload update list based on the multiple workloads to be updated. In order to reduce the number of changes of the workload to be updated within the change time window, the expected configuration rules corresponding to the workload to be updated, whose implementation conditions are met and whose implementation method is passive implementation, continue to be read from the database 140, and are added to the workload update list to obtain a merged update list.

[0062] The merged update list includes a second list to be updated corresponding to multiple workloads to be updated. The second list to be updated includes multiple expected configuration rules that need to be implemented for the workload to be updated in this change. The multiple workloads to be updated include the target workload. Therefore, the merged update list includes the second list to be updated corresponding to the target workload, that is, the target workload can be any workload to be updated.

[0063] Reference Figure 4The configuration maintenance system 110 first reads the configuration rule list from the database 140, and then traverses and judges the implementation method of each expected configuration rule in the configuration rule list, that is, takes out the expected configuration rule in the configuration rule list to judge whether the implementation method is passive implementation or mixed implementation. If there are still expected configuration rules left in the configuration rule list, it means that the traversal has not ended yet, then the expected configuration rule is taken out from the configuration rule list to judge the implementation method. If the implementation method of the expected configuration rule taken out from the configuration rule list is active implementation or mixed implementation, then continue to judge whether the implementation condition of the expected configuration rule is met. If the implementation condition of the expected configuration rule is met, If the implementation conditions of the expected configuration rule are met, the expected configuration rule will be written into the workload update list, and the various workloads to be updated in the workload update list will be traversed until the traversal of the configuration rule list is completed, that is, the workloads to be updated are taken out from the workload update list in turn, and the expected configuration rule corresponding to the workload to be updated and whose implementation conditions are met is read from the configuration rule list. If the workload to be updated cannot be taken out from the workload update list, it means the traversal is completed. Similarly, if the expected configuration rule related to the workload to be updated and whose implementation conditions are met cannot be read from the configuration rule list, it means the traversal is completed. When the expected configuration rule corresponding to the workload to be updated and whose implementation conditions are met is read from the configuration rule list, the expected configuration rule will continue to be judged whether the implementation method is passive implementation or mixed implementation. If so, the expected configuration rule will be added to the workload update list until the traversal is completed to obtain the merged update list.

[0064] By first screening out the expected configuration rules whose implementation conditions are met and whose implementation methods are active or mixed, and then determining the workload to be updated based on the screened expected configuration rules, and then adding the expected configuration rules whose implementation conditions are met and whose implementation methods are passive based on the workload to be updated, the number of expected configuration rules for the workload to be updated in this change is increased, and the passively implemented expected configuration rules related to the workload to be changed are implemented together in this change, thereby reducing the number of changes to the workload to be changed, shortening the workload change time, avoiding the risk of business downtime caused by multiple consecutive updates of the workload, and improving the operating stability of the Kubernetes cluster 150.

[0065] In one embodiment, reading from the database 140 the desired configuration rules corresponding to each workload to be updated in the workload update list, for which implementation conditions are satisfied and the implementation method is passive implementation, and adding them to the workload update list to obtain a merged update list includes:

[0066] Reading from the database 140 the desired configuration rules corresponding to the workloads to be updated in the workload update list, the desired configuration rules having implementation conditions satisfied and the implementation mode being passive implementation, and adding the rules to the workload update list to obtain the updated workload update list;

[0067] Conflict merging is performed on multiple expected configuration rules corresponding to each of the workloads to be updated in the updated workload update list to obtain a merged update list.

[0068] Specifically, the configuration maintenance system 110 reads out the expected configuration rules corresponding to each workload to be updated in the workload update list from the database 140, the implementation conditions of which are met and the implementation method is passive implementation, and adds them to the workload update list to obtain the updated workload update list, that is, the updated workload update list now includes the expected configuration rules corresponding to multiple workloads to be updated, the implementation conditions of which are met and the implementation method is active implementation, passive implementation or mixed implementation.

[0069] Because multiple expected configuration rules may come from different sources, such as the strategies of the operation and maintenance team, the needs of the development team, etc., these different expected configuration rules need to be merged into a unified expected configuration. During the merging process, it is necessary to deal with possible conflicts, such as different expected configuration rules having different requirements for the same configuration item. Usually, conflicts are resolved according to a preset priority scheme, such as giving priority to more specific or more important rules. The preset priority scheme includes a variety of different priority setting methods, such as giving priority to the expected configuration rules configured for management objects with higher priorities according to the priority of the management object, or giving priority to the expected configuration rules with more applications according to the number of applications of different expected configuration rules, or implementing expected configuration rules with higher importance levels according to the importance level. Conflict merge processing is used to ensure that each expected configuration rule in the merged update list can be successfully implemented to improve the update success rate of the workload.

[0070] In one embodiment, the merging and implementing of each desired configuration rule in the target to-be-updated list with the current configuration rule of the target workload includes:

[0071] Merging each desired configuration rule in the target to-be-updated list with the current configuration rule of the target workload to obtain an updated configuration rule;

[0072] The update configuration rules are rolled over.

[0073] Specifically, each expected configuration rule in the target to-be-updated list is merged into the current configuration rules of the target workload to obtain the merged update configuration rules. The update configuration rules are implemented in a rolling update manner, and the workload is updated in a gradual replacement manner, rather than updating all at once. This ensures that there are always some instances of the old version running during the update process, thereby maintaining service continuity and reducing or even avoiding obvious service interruptions to users. Once a problem is found in the new version, the update can be stopped immediately and rolled back to the last stable version. This method can control the scope of the problem's impact to a smaller range and avoid the risk of the entire service being unavailable due to a one-time full update.

[0074] Reference Figure 5 The workload management system also includes an external client, which is a client used to initiate update requests. The following provides an implementation process of a workload management method:

[0075] a1. When the maintainer of Kubernetes cluster 150 (developer / operator of the basic system) plans to adjust the workload, he or she enters the management plan into configuration maintenance system 110 through maintenance terminal 130. The management plan includes the configuration rules, implementation conditions, and implementation methods corresponding to the target workload;

[0076] a2 configuration maintenance system 110 enters the management plan into the database 140 to complete the information entry / modification;

[0077] b1. The external client activates the admission controller 120 by sending an update request to implement an externally triggered workload update. At this time, the admission controller 120 intercepts the update request for the target workload.

[0078] b2. The admission controller 120 reads the target workload corresponding to the implementation conditions from the database 140, and the desired configuration rules are implemented passively or hybridly, and the target workload with the desired configuration rules is deployed to the Kubernetes cluster 150.

[0079] c1. When there is no externally triggered workload update, the configuration maintenance system 110 reads from the database 140 the implementation method for hybrid implementation / active implementation, the implementation conditions are met, the desired configuration rules;

[0080] c2 based on the expected configuration rules read out to determine the need to actively adjust the workload to be updated;

[0081] c3. Implement the desired configuration rules that are passively implemented for the workload to be updated to achieve workload adjustment.

[0082] Figures 2 to 5 FIG. 1 is a flow chart of a workload management method in one embodiment. It should be understood that although Figures 2 to 5 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. In addition, Figures 2 to 5 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0083] like Figure 6 As shown, an embodiment of the present application provides a computer device, including a processor 711, a communication interface 712, a memory 713 and a communication bus 714, wherein the processor 711, the communication interface 712, and the memory 713 communicate with each other through the communication bus 714;

[0084] Memory 713, for storing computer programs;

[0085] The processor 711 is configured to implement the workload management control method provided by any one of the aforementioned method embodiments when executing the program stored in the memory 713 .

[0086] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0087] In one embodiment, the workload management system provided by the present application can be implemented in the form of a computer program. Figure 6 The computer device is run on the computer device shown. The memory of the computer device can store various program modules that constitute the workload management system. The computer program composed of each program module enables the processor to execute the steps of the workload management method of each embodiment of the present application described in this specification.

[0088] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the workload management method provided by any of the aforementioned method embodiments is implemented.

[0089] An embodiment of the present application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the workload management method provided by any of the aforementioned method embodiments.

[0090] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0091] The foregoing is merely a list of specific embodiments of the present application, intended to enable those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the broadest scope consistent with the principles and novel features of the present application.

Claims

1. A workload management method, characterized in that: The method further comprises: Upon receiving management plans for target workload configurations from different management objects, saving the management plans corresponding to the target workloads into a database, wherein the management plans include at least one expected configuration rule, and the expected configuration rule is used to adjust operating parameters of the corresponding workloads; When an update condition corresponding to the target workload is triggered within the change time window, the desired configuration rules related to the target workload are read from the database according to the update scheme corresponding to the triggering method to form a target to-be-updated list; Each expected configuration rule in the target to-be-updated list is merged with the current configuration rule of the target workload and then implemented.

2. The workload management method according to claim 1, wherein: The management plan also includes implementation methods and implementation conditions, and the implementation methods are passive implementation, active implementation or mixed implementation; When the update condition corresponding to the target workload is triggered within the change time window, the expected configuration rules related to the target workload are read from the database according to the update scheme corresponding to the triggering method to form a target to-be-updated list, including: When an update request corresponding to the target workload is received within the change time window, the expected configuration rules related to the target workload, whose implementation conditions are met and whose implementation method is passive implementation or hybrid implementation are read from the database according to the passive update scheme to form a first list to be updated, wherein the target list to be updated is the first list to be updated.

3. The workload management method according to claim 2, wherein: When an update request corresponding to the target workload is received within the change time window, according to the passive update scheme, desired configuration rules related to the target workload, for which implementation conditions are met and the implementation method is passive implementation or hybrid implementation, are read from the database to form a first list to be updated, including: When an update request corresponding to the target workload is received within the change time window, desired configuration rules related to the target workload, having implementation conditions satisfied and implemented in a passive implementation or a hybrid implementation mode are read from the database to form a first rule list; Conflict merging is performed on multiple expected configuration rules in the first rule list to obtain the first list to be updated.

4. The workload management method according to claim 1, wherein: The management plan also includes implementation methods and implementation conditions, and the implementation methods are passive implementation, active implementation or mixed implementation; When the update condition corresponding to the target workload is triggered within the change time window, the expected configuration rules related to the target workload are read from the database according to the update scheme corresponding to the triggering method to form a target to-be-updated list, including: When the active update condition corresponding to the target workload is triggered within the change time window, the expected configuration rules related to the target workload, whose implementation conditions are met and the implementation method is active implementation or mixed implementation are read from the database according to the active update plan to form a second list to be updated corresponding to the target workload, wherein the target list to be updated is the second list to be updated for the target workload pair.

5. The workload management method according to claim 4, wherein: When the active update condition corresponding to the target workload is triggered within the change time window, the desired configuration rules related to the target workload, for which the implementation conditions are satisfied and the implementation method is active implementation or hybrid implementation, are read from the database according to the active update scheme to form a second to-be-updated list corresponding to the target workload, including: When a preset update time is reached within the change time window, the expected configuration rules whose implementation conditions are met and whose implementation mode is active implementation or hybrid implementation are read from the database to form a second rule list, wherein the second rule list includes the expected configuration rules corresponding to the target workload; Merging each desired configuration rule corresponding to the same workload in the second rule list to obtain a workload update list, wherein the workload update list includes desired configuration rules corresponding to a plurality of workloads to be updated, and the plurality of workloads to be updated include the target workload; The expected configuration rules corresponding to each workload to be updated in the workload update list, whose implementation conditions are met and the implementation method is passive implementation, are read from the database and added to the workload update list to obtain a merged update list, wherein the merged update list includes the second list to be updated corresponding to the target workload.

6. The workload management method according to claim 5, characterized in that: The step of reading from the database the desired configuration rules corresponding to each workload to be updated in the workload update list, the implementation conditions of which are satisfied and the implementation method is passive implementation, and adding the rules to the workload update list to obtain a merged update list includes: Reading from the database the desired configuration rules corresponding to each workload to be updated in the workload update list, the desired configuration rules having implementation conditions satisfied and the implementation method being passive implementation, and adding them to the workload update list to obtain the updated workload update list; Conflict merging is performed on multiple expected configuration rules corresponding to each of the workloads to be updated in the updated workload update list to obtain a merged update list.

7. The workload management method according to claim 1, wherein: The step of merging and implementing each desired configuration rule in the target to-be-updated list with the current configuration rule of the target workload includes: Merging each desired configuration rule in the target to-be-updated list with the current configuration rule of the target workload to obtain an updated configuration rule; The update configuration rules are rolled over.

8. A workload management system, characterized in that: The workload management system includes a configuration maintenance system and an admission controller, wherein: The configuration maintenance system is configured to, upon receiving a management plan for configuring a target workload by different management objects, save the management plan corresponding to the target workload into a database, wherein the management plan includes at least one expected configuration rule, and the expected configuration rule is used to adjust the operating parameters of the corresponding workload; A management module is used to read out the expected configuration rules related to the target workload from the database according to the update scheme corresponding to the triggering method to form a target list to be updated when the update condition corresponding to the target workload is triggered within the change time window; each expected configuration rule in the target list to be updated is merged with the current configuration rules of the target workload and then implemented, wherein the management module is the configuration maintenance system or the admission controller under different triggering methods.

9. A computer device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory for storing computer programs; A processor, configured to implement the workload management method according to any one of claims 1 to 7 when executing a program stored in a memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the workload management method according to any one of claims 1 to 7 is implemented.

11. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instruction is executed by a processor, the workload management method according to any one of claims 1 to 7 is implemented.

Images