Fault drill method and device

Abstract

The present application discloses a fault drill method and apparatus, the method comprising: obtaining a set of fault drill pipelines determined based on a container management platform; determining the fault drill execution state type of the current fault drill pipeline in the system to be drilled in the fault drill pipeline set; and determining, based on the fault drill execution state type, the time when the current fault drill pipeline will next perform a fault drill on the system to be drilled; thereby making the fault drill process more resource-efficient and the drill deployment more flexible, and not being restricted by the platform on which the fault drill depends, avoiding self-dependence problems.

Description

Technical Field

[0001] The present application relates to cloud computing technology, and more particularly to a fault drill method and apparatus. The present application also relates to a computer storage medium and an electronic device. Background Art

[0002] Along with massive requests, holiday peak traffic, and increasing system complexity, there's a high probability of both expected and unexpected failures. Therefore, it's crucial to simulate any possible failures in advance to observe the system's response and verify intended strategies. Fault drills are crucial for evaluating application high availability. A complete fault drill consists of the drill target, the specific failures that occurred within the target, the application's expected fault response behavior, and actual observation and judgment of the application's performance. Fault drills can help improve the fault tolerance and recoverability of distributed systems. Summary of the Invention

[0003] The present application provides a fault drill method to solve the problems in the prior art of waste of resources and limitation of drill objects caused by fault drills.

[0004] This application provides a fault drill method, including:

[0005] Obtain a set of fault drill pipelines determined based on the container management platform;

[0006] Determining a fault drill execution state type of a current fault drill pipeline in the system to be drilled in the set of fault drill pipelines;

[0007] According to the fault drill execution state type, the time when the current fault drill pipeline performs the next fault drill on the system to be drilled is determined.

[0008] In some embodiments, obtaining a set of fault drill pipelines determined based on a container management platform includes:

[0009] Based on the container management platform, define a fault drill pipeline;

[0010] The fault drill pipeline set is determined according to the fault drill pipeline.

[0011] In some embodiments, defining a fault drill pipeline based on the container management platform includes:

[0012] Based on the container management platform, a fault drill image is pre-defined according to the fault drill requirements of the system to be drilled;

[0013] The fault drill pipeline is determined according to the fault drill information corresponding to the fault drill image.

[0014] In some embodiments, pre-defining a fault drill image based on the container management platform and according to the fault drill requirements of the system to be drilled includes:

[0015] Predefine a fault injection image according to the fault injection requirements of the system to be drilled;

[0016] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0017] The fault drill pipeline is determined according to the fault injection information corresponding to the fault injection image.

[0018] In some embodiments, pre-defining a fault drill image based on the container management platform and according to the fault drill requirements of the system to be drilled includes:

[0019] Predefine a fault alarm image according to the fault alarm requirements of the system to be drilled;

[0020] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0021] The fault drill pipeline is determined according to the fault alarm information corresponding to the fault alarm image.

[0022] In some embodiments, pre-defining a fault drill image based on the container management platform and according to the fault drill requirements of the system to be drilled includes:

[0023] Predefine a fault inspection image based on the fault inspection requirements of the system to be tested;

[0024] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0025] The fault drill pipeline is determined according to the fault inspection information corresponding to the fault inspection image.

[0026] In some embodiments, pre-defining a fault drill image based on the container management platform and according to the fault drill requirements of the system to be drilled includes:

[0027] Predefine a fault recovery image based on the fault recovery requirements of the system to be drilled;

[0028] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0029] The fault drill pipeline is determined according to the fault recovery information corresponding to the fault drill image.

[0030] In some embodiments, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0031] When the fault drill execution state type is the initial state, determining whether the current time of the system to be drilled is greater than or equal to a preset fault drill trigger time;

[0032] If so, trigger the fault drill to execute;

[0033] Setting the initial state to a running state;

[0034] According to the operating status, the time for the next fault drill to be performed on the system to be drilled under the current fault drill pipeline is determined.

[0035] In some embodiments, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0036] When the fault drill execution state type is a running state, determining whether the current fault pipeline has completed the fault drill;

[0037] If so, resetting the fault drill execution state type of the current fault pipeline to the end state;

[0038] According to the end state, a random execution time for the next execution of the fault drill on the current fault pipeline is determined.

[0039] In some embodiments, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0040] When the fault drill execution state is in the end state, determining a random execution time for the next execution of the fault drill under the current fault pipeline according to a time adjustment parameter in the container management platform;

[0041] Reset the end state to the initial state.

[0042] In some embodiments, obtaining a set of fault drill pipelines determined based on a container management platform includes:

[0043] According to the timing trigger configured in the container management platform, a set of fault drill pipelines determined based on the container management platform is obtained.

[0044] This application also provides a fault drill device, comprising:

[0045] An acquisition unit is used to obtain a set of fault drill pipelines determined based on the container management platform;

[0046] A first determining unit is configured to determine a fault drill execution state type of a current fault drill pipeline in the system to be drilled in the set of fault drill pipelines;

[0047] The second determining unit is configured to determine, according to the fault drill execution state type, the time when the current fault drill pipeline will next execute a fault drill on the system to be drilled.

[0048] The present application also provides a computer storage medium for storing data generated by a network platform and a program for processing the data generated by the network platform;

[0049] When the program is read and executed by the processor, the cloud-native-based fault drill method as described above is executed.

[0050] The present application also provides an electronic device, comprising:

[0051] processor;

[0052] The memory is used to store a program for processing data generated by the network platform. When the program is read and executed by the processor, it executes the cloud-native-based fault drill method as described above.

[0053] Compared with the prior art, this application has the following advantages:

[0054] The present application provides a fault drill method, on the one hand: obtaining a set of fault drill pipelines determined based on a container management platform, and determining the next fault drill time of the current fault drill pipeline according to different fault drill execution state types, so that the fault drill is based on cloud native execution, which saves more resources and makes the drill deployment more flexible. On the other hand: based on the set of fault drill pipelines determined by the container management platform, a fault drill can be performed on any system during the execution of the fault drill, that is, the system to be drilled can be any system, not limited to the platform on which the fault drill depends, avoiding self-dependence problems. On the other hand: the state flow of the fault drill pipeline can be realized according to the set random time, thereby further improving the chaos requirements. On the other hand: through customized various types of fault drill images, the fault drill process is made more flexible. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 This is a flowchart of an embodiment of a fault drill method provided by the present application;

[0056] Figure 2 This is a structural diagram of a fault drill task in an embodiment of a fault drill method provided by the present application;

[0057] Figure 3 This is a schematic diagram of traversing a fault drill pipeline set in an embodiment of a fault drill method provided by the present application;

[0058] Figure 4 This is a structural diagram of an embodiment of a fault drill device provided by the present application;

[0059] Figure 5 This is a schematic structural diagram of an electronic device embodiment provided by the present application. DETAILED DESCRIPTION

[0060] The following description sets forth many specific details to facilitate a thorough understanding of the present application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the scope of the present application. Therefore, the present application is not limited to the specific implementations disclosed below.

[0061] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. Descriptive terms such as "a," "a," "a first," and "a second," etc., used in this application and the appended claims, are not intended to limit quantity or sequence, but are used to distinguish information of the same type from one another.

[0062] As described above, various failures can occur at any time and in any location during system operation. Many of these failures are unavoidable, such as a sudden disk failure or a sudden network or power outage in the data center. These failures can cause significant losses, making improving the system's tolerance to failures a crucial issue. Therefore, understanding the system's fault tolerance or fault-tolerance capabilities is crucial. Fault drills are an effective means of improving the fault tolerance and recoverability of distributed systems.

[0063] Existing technologies can implement fault drills through Chaos Mesh, but Chaos Mesh has the following problems when performing fault drills:

[0064] 1. When implementing fault drills, ChaosMesh relies on a self-developed process engine, not a cloud-native approach;

[0065] 2. After the fault injection, recovery cannot be performed during the drill due to self-dependency issues;

[0066] 3. Does not support user-defined fault injection;

[0067] 4. Chaotic random triggering drills are not supported.

[0068] Based on the above, this application provides a cloud-native-based fault drill method that can solve the above-mentioned various defects, as follows:

[0069] like Figure 1 As shown, Figure 1 This is a flowchart of an embodiment of a fault drill method provided by the present application; the fault drill method embodiment includes:

[0070] Step S101: Obtain a fault drill pipeline set determined based on a container management platform.

[0071] The purpose of step S101 is to obtain a set of fault drill pipelines.

[0072] Before describing the specific implementation process of step S101, the technical terms involved are first explained.

[0073] In this embodiment, the container management platform can be a management platform based on a cloud-native open source framework for container cluster management. Cloud native can be understood as CloudNative, which is a combination of the words Cloud+Native. Cloud indicates that the application is located in the cloud, rather than a traditional data center; Native indicates that the application was designed with the cloud environment in mind from the outset, is natively designed for the cloud, and runs optimally on the cloud, fully leveraging the elasticity and distributed nature of the cloud platform.

[0074] The container cluster management open source framework can be understood as a platform for an open source system architecture for automatically deploying, scaling, and managing containerized applications, such as Kubernetes (k8s).

[0075] In this embodiment, the specific implementation process of step S101 may include:

[0076] Step S101 - 1 : Based on the container management platform, define a fault drill pipeline.

[0077] Step S101 - 2 : determining the fault drill pipeline set according to the fault drill pipeline.

[0078] like Figure 2 As shown, Figure 2It is a structural diagram of a fault drill task in an embodiment of a fault drill method provided by the present application. In this embodiment, the step S101-1 can define the tasks (Task), execution sequence (Step), etc. in the fault drill pipeline (pipeline) based on the native usage of Tekton in k8s; the Tekton is a powerful and flexible Kubernetes (k8s) native open source framework for creating a continuous integration and delivery (CI / CD) system. The Tekton can define a fault drill pipeline (pipeline) based on the CRD of k8s. Among them, in Tekton, each operation in the CI / CD workflow will be a Step, and then the Step is aggregated into a Task, and Steps is a series of commands executed sequentially by tasks. Task defines the work to be performed, and each task runs as a Pod on the k8s cluster, that is: Task runs in the form of a pod, where pod can be understood as a container for shared resources, and a pod can include one or more containers. In this embodiment, the runAfter parameter of Tekton can be used to define the execution order of the entire fault drill process. For example, within a Task, parameters such as Workspace and results can be used to convey contextual information about the fault drill process. TektonPipeline is a Kubernetes-native pipeline that runs tasks in pods and manages tasks and workflows through custom CRDs. A Pipeline can consist of one or more Tasks.

[0079] In order to quickly define the fault drill pipeline, in this embodiment, a fault drill image may be predefined. Therefore, the specific implementation process of step S101-1 may include:

[0080] Step S101-11: Based on the container management platform, pre-define a fault drill image according to the fault drill requirements of the system to be drilled;

[0081] Step S101 - 12 : determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image.

[0082] The step S101-11 may include defining a fault drill image in at least one of the following predefined ways:

[0083] The first includes:

[0084] Step S101-11-11: Predefine a fault injection image based on the fault injection requirements for the system to be tested. Specifically, the fault injection requirements may include, but are not limited to, at least one of: a full disk, high load (or overload), system downtime, process termination, and network failure. The above examples of defining the fault injection image may be one or a combination of multiple.

[0085] The step S102-12 may include:

[0086] Step S101 - 12 - 12: Determine the fault drill pipeline according to the fault injection information corresponding to the fault injection image.

[0087] The second category includes:

[0088] Step S101-11-21: Predefine a fault alarm image based on the fault alarm requirements of the system to be tested. Specifically, based on the fault alarm requirements, a database for obtaining open source monitoring, or a combination of monitoring, alarm, and time series databases, such as Prometheus monitoring, can be predefined. An image for obtaining custom monitoring of the system to be tested can also be predefined. An image for obtaining alarm information can also be defined by calling an interface. The above examples of fault alarm image definitions can include one or more combinations.

[0089] The step S101-12 may include:

[0090] Step S101-12-21: Determine the fault drill pipeline according to the fault alarm information corresponding to the fault alarm image.

[0091] The third category includes:

[0092] Step S101-11-31: Predefine a fault inspection image based on the fault inspection requirements for the system to be tested. Specifically, a inspection script can be predefine based on the fault inspection requirements; alternatively, a inspection module deployed in the cluster can be predefine, and the availability of the system to be tested can be obtained through the interface and / or events of the inspection module. The above examples of defining fault inspection images can be one or a combination of multiple ones.

[0093] The step S101-12 may include:

[0094] Step S101-12-32: Determine the fault drill pipeline according to the fault inspection information corresponding to the fault inspection image.

[0095] The fourth type includes:

[0096] Step S101-11-41: Predefine a fault recovery image based on the fault recovery requirements of the system to be tested. Specifically, based on the fault recovery requirements, a reset script, a machine restart, or at least one other recovery capability image may be predefine. The above examples of defining a fault recovery image may be one or a combination of multiple.

[0097] The step S101-12 may include:

[0098] Step S101-12-42: Determine the fault drill pipeline according to the fault recovery information corresponding to the fault drill image.

[0099] The fault drill image pre-defined in the above steps can be pulled up through the pod generated by scheduling during the Tekton pipeline execution, and the corresponding logic is executed to complete the fault injection process.

[0100] To flexibly configure the triggering of fault drills, step S101 can obtain a fault drill pipeline set based on the container management platform according to the timed trigger configured in the container management platform. For example, a Kubernetes cronjob can be used to implement flexible configuration of defined triggers, thereby traversing each fault drill pipeline in the fault drill pipeline set according to the timed scheduling trigger to perform a fault drill. Correspondingly, the fault drill pipeline traversal can also be terminated by setting a timed trigger to end.

[0101] Step S102: determining the fault drill execution state type of the current fault drill pipeline in the system to be drilled in the fault drill pipeline set.

[0102] In this embodiment, the fault drill execution state type in step S102 may include at least one of a running state, an initial state, and an end state. The running state indicates that the fault drill is in progress, and the initial state indicates that the fault drill has not yet been executed. Of course, the end state may also be included, and the end state may be understood as indicating that the fault drill has ended or that the fault drill has been exited due to a problem.

[0103] Step S103: Determine the time when the current fault drill pipeline will next execute a fault drill on the system to be drilled according to the fault drill execution state type.

[0104] like Figure 3 As shown, the specific implementation process of step S103 may include the following methods according to different fault drill execution status types:

[0105] Method 1:

[0106] Step S103-11: When the fault drill execution state type is the initial state, determining whether the current time of the system to be drilled is greater than or equal to a preset fault drill trigger time;

[0107] Step S103 - 12 : If yes, trigger the execution of the fault drill.

[0108] Step S103-13: resetting the initial state to the running state;

[0109] The step S103-14: determining the time when the current fault drill pipeline performs the next fault drill on the system to be drilled according to the operating status.

[0110] It is understandable that when the current time of the system to be drilled is greater than or equal to the fault drill trigger time, it means that the current fault drill pipeline has not been triggered for execution when the fault drill trigger time is reached. Therefore, it can be triggered for execution directly, or the random trigger time can be adjusted or calculated. For example, the current fault drill pipeline can be determined as the pipeline to be drilled, and wait for the random trigger time to arrive. At this time, the next fault drill pipeline in the fault drill pipeline set can be traversed and determined as the current fault drill pipeline to perform the above-mentioned fault drill execution state type judgment. Among them, the calculation method of random time includes but is not limited to pre-setting a maximum scheduling duration for each pipeline, and each time the random time is calculated, a random value is randomly selected from 0 to the maximum scheduling duration as the time interval for the next scheduling, thereby calculating the scheduling time for the next execution of the fault drill.

[0111] That is to say, in this embodiment, it is necessary to traverse the fault drill pipelines in the fault drill pipeline set to determine the time for executing the next fault drill.

[0112] When the current time of the system to be drilled is less than the fault drill trigger time, the next fault drill pipeline is executed, that is, the current fault drill pipeline is ended.

[0113] In this embodiment, performing the fault drill may also include:

[0114] Randomly calculate fault drill execution parameters; wherein the fault drill execution parameters may include a drill environment, a fault injection target, a fault injection range, etc., for example: a drill area range, an injection target, and a range of injection targets, etc., and the specific execution parameters are not limited to the above examples;

[0115] The fault drill is executed according to the fault drill execution parameters.

[0116] Method 2:

[0117] Step S103-21: When the fault drill execution state type is the running state, determining whether the current fault pipeline has completed the fault drill;

[0118] Step S103-22: If yes, reset the fault drill execution state type of the current fault pipeline to the end state;

[0119] Step S103-23: Determine the random execution time of the next execution of the fault drill on the current fault pipeline according to the end state.

[0120] Method 3:

[0121] Step S103-31: When the fault drill execution state is in the end state, determine the random execution time for the next execution of the fault drill under the current fault pipeline according to the time adjustment parameter in the container management platform;

[0122] Step S103-32: Reset the end state to the initial state.

[0123] In the above three methods, the execution time of the next fault drill is randomly determined, so chaos can be achieved in the fault drill process.

[0124] The above is a description of an embodiment of a cloud-native-based fault drill method provided by the present application. In this embodiment, on the one hand: a set of fault drill pipelines determined based on a container management platform is obtained, and according to different fault drill execution state types, the next fault drill time of the current fault drill pipeline is determined, so that the fault drill is based on cloud-native execution, thereby saving more resources and making the drill deployment more flexible. On the other hand: based on the set of fault drill pipelines determined by the container management platform, a fault drill can be performed on any system during the execution of the fault drill, that is, the system to be drilled can be any system, not limited to the platform on which the fault drill depends, avoiding self-dependence problems. On the other hand: the state flow of the fault drill pipeline can be realized according to the set random time, thereby further improving the chaos requirements. On the other hand: through customized various types of fault drill images, the fault drill process is made more flexible.

[0125] The above is a detailed description of an embodiment of a cloud-native fault drill method provided by this application. Corresponding to the aforementioned embodiment of a cloud-native fault drill method, this application also discloses an embodiment of a cloud-native fault drill device. Please refer to Figure 4 Since the device embodiment is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment. The device embodiment described below is only illustrative.

[0126] like Figure 4 As shown, Figure 4 : is a structural diagram of an embodiment of a fault drill device provided by the present application, the fault drill device embodiment includes:

[0127] The acquisition unit 401 is configured to acquire a set of fault drill pipelines determined based on a container management platform.

[0128] The acquisition unit 401 may specifically include: a definition subunit and a determination subunit;

[0129] The definition subunit is used to define a fault drill pipeline based on the container management platform;

[0130] The determining subunit is configured to determine the fault drill pipeline set according to the fault drill pipeline.

[0131] The definition subunit may include: an image definition subunit, configured to predefine a fault drill image based on the container management platform and according to a fault drill requirement for the system to be drilled.

[0132] The determining subunit may be specifically configured to determine the fault drill pipeline according to the fault drill information corresponding to the fault drill image.

[0133] The image definition subunit may include at least one of the following subunits: an injection image definition subunit, an alarm image definition subunit, an inspection image definition subunit, and a recovery image definition subunit.

[0134] The injection image definition subunit is used to predefine a fault injection image according to the fault injection requirements of the system to be drilled;

[0135] The determining subunit may be specifically configured to determine the fault rehearsal pipeline according to the fault injection information corresponding to the fault injection image.

[0136] The alarm image definition subunit is used to predefine the fault alarm image according to the fault alarm requirements of the system to be trained;

[0137] The determining subunit may be specifically configured to determine the fault drill pipeline according to the fault alarm information corresponding to the fault alarm image.

[0138] The inspection image definition subunit is used to predefine a fault inspection image according to the fault inspection requirements of the system to be trained;

[0139] The determining subunit may be specifically configured to determine the fault drill pipeline according to the fault inspection information corresponding to the fault inspection image.

[0140] The recovery image definition subunit is used to predefine a fault recovery image according to the fault recovery requirements of the system to be drilled;

[0141] The determining subunit may be specifically configured to determine the fault drill pipeline according to the fault recovery information corresponding to the fault drill image.

[0142] In this embodiment, the acquisition unit 401 may be specifically configured to acquire a fault drill pipeline set determined based on the container management platform according to a timing trigger configured in the container management platform.

[0143] The first determining unit 402 is configured to determine the fault drill execution state type of the current fault drill pipeline in the system to be drilled in the fault drill pipeline set.

[0144] The second determining unit 403 is configured to determine, according to the fault drill execution state type, the time when the current fault drill pipeline will next execute a fault drill on the system to be drilled.

[0145] The third determining unit 403 may include at least the following three methods:

[0146] Method 1 may include:

[0147] a trigger time determination subunit, configured to determine whether the current time of the system to be drilled is greater than the fault drill trigger time when the fault drill execution state type is the initial state;

[0148] a random time determination subunit, configured to determine a random trigger time according to a time adjustment parameter in the container management platform when a determination result of the trigger time determination subunit is yes;

[0149] The drill time determination subunit is used to determine the random trigger time as the time when the fault drill is next executed in the current fault drill pipeline.

[0150] This embodiment may also include:

[0151] a triggering subunit, configured to trigger the current fault drill pipeline to perform the fault drill according to the random trigger time;

[0152] The state resetting subunit is used to set the initial state to the running state.

[0153] Method 2 may include:

[0154] A drill completion determination subunit, configured to determine whether the current fault pipeline has completed the fault drill when the fault drill execution state type is a running state;

[0155] a first state resetting subunit, configured to reset the fault drill execution state type of the current fault pipeline to an end state when a determination result of the drill completion determination subunit is yes;

[0156] A drill time determination subunit, configured to determine a random execution time for the next execution of the fault drill on the current fault pipeline according to a time adjustment parameter in the container management platform;

[0157] The second state resetting subunit is configured to adjust the end state to the initial state.

[0158] Method three may include:

[0159] A state resetting subunit, configured to reset the fault drill execution state of the current fault drill pipeline to the end state when the fault drill execution state is the end state;

[0160] The drill time determination subunit is used to determine the random execution time of the next execution of the fault drill on the current fault pipeline according to the time adjustment parameter in the container management platform.

[0161] The above is a description of an embodiment of a cloud-native fault drill device provided in this application. For details of the device embodiment, please refer to the corresponding fault drill method embodiment above, and will not be repeated here.

[0162] Based on the above content, the present application also provides a computer storage medium for storing data generated by a network platform and a program for processing the data generated by the network platform;

[0163] When the program is read and executed by the processor, the steps in the above-mentioned cloud-native fault drill method are performed, specifically:

[0164] Obtain a set of fault drill pipelines determined based on the container management platform;

[0165] Determining a fault drill execution state type of a current fault drill pipeline in the system to be drilled in the set of fault drill pipelines;

[0166] According to the fault drill execution state type, the time when the current fault drill pipeline performs the next fault drill on the system to be drilled is determined.

[0167] In this embodiment, obtaining a set of fault drill pipelines determined based on a container management platform includes:

[0168] Based on the container management platform, define a fault drill pipeline;

[0169] The fault drill pipeline set is determined according to the fault drill pipeline.

[0170] In this embodiment, the fault drill pipeline is defined based on the container management platform, including:

[0171] Based on the container management platform, a fault drill image is pre-defined according to the fault drill requirements of the system to be drilled;

[0172] The fault drill pipeline is determined according to the fault drill information corresponding to the fault drill image.

[0173] In this embodiment, based on the container management platform, a fault drill image is predefined according to the fault drill requirements of the system to be drilled, including:

[0174] Predefine a fault injection image according to the fault injection requirements of the system to be drilled;

[0175] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0176] The fault drill pipeline is determined according to the fault injection information corresponding to the fault injection image.

[0177] In this embodiment, based on the container management platform, a fault drill image is predefined according to the fault drill requirements of the system to be drilled, including:

[0178] Predefine a fault alarm image according to the fault alarm requirements of the system to be drilled;

[0179] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0180] The fault drill pipeline is determined according to the fault alarm information corresponding to the fault alarm image.

[0181] In this embodiment, based on the container management platform, a fault drill image is predefined according to the fault drill requirements of the system to be drilled, including:

[0182] Predefine a fault inspection image based on the fault inspection requirements of the system to be tested;

[0183] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0184] The fault drill pipeline is determined according to the fault inspection information corresponding to the fault inspection image.

[0185] In this embodiment, based on the container management platform, a fault drill image is predefined according to the fault drill requirements of the system to be drilled, including:

[0186] Predefine a fault recovery image based on the fault recovery requirements of the system to be drilled;

[0187] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0188] The fault drill pipeline is determined according to the fault recovery information corresponding to the fault drill image.

[0189] In this embodiment, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0190] When the fault drill execution state type is the initial state, determining whether the current time of the system to be drilled is greater than the fault drill trigger time;

[0191] If so, determining a random trigger time based on a time adjustment parameter in the container management platform;

[0192] The random trigger time is determined as the time when the fault drill is next executed in the current fault drill pipeline.

[0193] In this embodiment, it also includes:

[0194] Triggering the current fault drill pipeline to perform the fault drill according to the random trigger time;

[0195] The initial state is reset to the running state.

[0196] In this embodiment, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0197] When the fault drill execution state type is a running state, determining whether the current fault pipeline has completed the fault drill;

[0198] If so, resetting the fault drill execution state type of the current fault pipeline to the end state;

[0199] Determining, according to the time adjustment parameter in the container management platform, a random execution time for the next execution of the fault drill under the current fault pipeline;

[0200] The end state is adjusted to the initial state.

[0201] In this embodiment, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0202] When the fault drill execution state is the end state, resetting the fault drill execution state of the current fault drill pipeline to the end state;

[0203] The random execution time of the next execution of the fault drill on the current fault pipeline is determined according to the time adjustment parameter in the container management platform.

[0204] In this embodiment, obtaining a set of fault drill pipelines determined based on a container management platform includes:

[0205] According to the timing trigger configured in the container management platform, a set of fault drill pipelines determined based on the container management platform is obtained.

[0206] Based on the above content, the present application also provides an electronic device, such as Figure 5 As shown, the electronic device embodiment may include:

[0207] Processor 501;

[0208] The memory 505 is used to store a program for processing data generated by the network platform. When the program is read and executed by the processor, the program performs the steps of the above-mentioned cloud-native-based fault drill method, which may specifically be:

[0209] Obtain a set of fault drill pipelines determined based on the container management platform;

[0210] Determining a fault drill execution state type of a current fault drill pipeline in the system to be drilled in the set of fault drill pipelines;

[0211] According to the fault drill execution state type, the time when the current fault drill pipeline performs the next fault drill on the system to be drilled is determined.

[0212] In this embodiment, obtaining a set of fault drill pipelines determined based on a container management platform includes:

[0213] Based on the container management platform, define a fault drill pipeline;

[0214] The fault drill pipeline set is determined according to the fault drill pipeline.

[0215] In this embodiment, the fault drill pipeline is defined based on the container management platform, including:

[0216] Based on the container management platform, a fault drill image is pre-defined according to the fault drill requirements of the system to be drilled;

[0217] The fault drill pipeline is determined according to the fault drill information corresponding to the fault drill image.

[0218] In this embodiment, based on the container management platform, a fault drill image is predefined according to the fault drill requirements of the system to be drilled, including:

[0219] Predefine a fault injection image according to the fault injection requirements of the system to be drilled;

[0220] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0221] The fault drill pipeline is determined according to the fault injection information corresponding to the fault injection image.

[0222] In this embodiment, based on the container management platform, a fault drill image is predefined according to the fault drill requirements of the system to be drilled, including:

[0223] Predefine a fault alarm image according to the fault alarm requirements of the system to be drilled;

[0224] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0225] The fault drill pipeline is determined according to the fault alarm information corresponding to the fault alarm image.

[0226] In this embodiment, based on the container management platform, a fault drill image is predefined according to the fault drill requirements of the system to be drilled, including:

[0227] Predefine a fault inspection image based on the fault inspection requirements of the system to be tested;

[0228] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0229] The fault drill pipeline is determined according to the fault inspection information corresponding to the fault inspection image.

[0230] In this embodiment, based on the container management platform, a fault drill image is predefined according to the fault drill requirements of the system to be drilled, including:

[0231] Predefine a fault recovery image based on the fault recovery requirements of the system to be drilled;

[0232] The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes:

[0233] The fault drill pipeline is determined according to the fault recovery information corresponding to the fault drill image.

[0234] In this embodiment, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0235] When the fault drill execution state type is the initial state, determining whether the current time of the system to be drilled is greater than the fault drill trigger time;

[0236] If so, determining a random trigger time based on a time adjustment parameter in the container management platform;

[0237] The random trigger time is determined as the time when the fault drill is next executed in the current fault drill pipeline.

[0238] In this embodiment, it also includes:

[0239] Triggering the current fault drill pipeline to perform the fault drill according to the random trigger time;

[0240] The initial state is reset to the running state.

[0241] In this embodiment, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0242] When the fault drill execution state type is a running state, determining whether the current fault pipeline has completed the fault drill;

[0243] If so, resetting the fault drill execution state type of the current fault pipeline to the end state;

[0244] Determining, according to the time adjustment parameter in the container management platform, a random execution time for the next execution of the fault drill under the current fault pipeline;

[0245] The end state is adjusted to the initial state.

[0246] In this embodiment, determining the time of the next fault drill execution on the to-be-drilled system under the current fault drill pipeline according to the fault drill execution state type includes:

[0247] When the fault drill execution state is the end state, resetting the fault drill execution state of the current fault drill pipeline to the end state;

[0248] The random execution time of the next execution of the fault drill on the current fault pipeline is determined according to the time adjustment parameter in the container management platform.

[0249] In this embodiment, obtaining a set of fault drill pipelines determined based on a container management platform includes:

[0250] According to the timing trigger configured in the container management platform, a set of fault drill pipelines determined based on the container management platform is obtained.

[0251] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0252] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0253] 1. Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include non-transitory media such as modulated data signals and carrier waves.

[0254] 2. Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0255] Although the present application is disclosed as above with the preferred embodiments, it is not intended to limit the present application. Any person skilled in the art may make possible changes and modifications without departing from the spirit and scope of the present application. Therefore, the scope of protection of the present application shall be based on the scope defined by the claims of the present application.

Claims

1. A fault drill method, characterized in that: include: Obtain a set of fault drill pipelines determined based on the container management platform; Determining a fault drill execution state type of a current fault drill pipeline in the system to be drilled in the fault drill pipeline set, wherein the fault drill execution state type includes at least one state type of a running state, an initial state, and an end state; Determining, according to the fault drill execution state type, the time when the current fault drill pipeline will next execute a fault drill on the system to be drilled; When the fault drill execution state is the initial state, the step of determining the time when the current fault drill pipeline will next execute the fault drill on the system to be drilled comprises: Determine whether the current time of the system to be drilled is greater than or equal to a preset fault drill trigger time; If so, trigger the fault drill to execute, and set the initial state to the running state; According to the operating status, the time for the next fault drill to be performed on the system to be drilled under the current fault drill pipeline is determined.

2. The fault drill method according to claim 1, characterized in that: The acquisition of a fault drill pipeline set determined based on the container management platform includes: Based on the container management platform, define a fault drill pipeline; The fault drill pipeline set is determined according to the fault drill pipeline.

3. The fault drill method according to claim 2, characterized in that: Defining a fault drill pipeline based on the container management platform includes: Based on the container management platform, a fault drill image is pre-defined according to the fault drill requirements of the system to be drilled; The fault drill pipeline is determined according to the fault drill information corresponding to the fault drill image.

4. The fault drill method according to claim 3, characterized in that: The method of predefining a fault drill image based on the container management platform and according to the fault drill requirements of the system to be drilled includes: Predefine a fault injection image according to the fault injection requirements of the system to be drilled; The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes: The fault drill pipeline is determined according to the fault injection information corresponding to the fault injection image.

5. The fault drill method according to claim 3, characterized in that: The method of predefining a fault drill image based on the container management platform and according to the fault drill requirements of the system to be drilled includes: Predefine a fault alarm image according to the fault alarm requirements of the system to be drilled; The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes: The fault drill pipeline is determined according to the fault alarm information corresponding to the fault alarm image.

6. The fault drill method according to claim 3, characterized in that: The method of predefining a fault drill image based on the container management platform and according to the fault drill requirements of the system to be drilled includes: Predefine a fault inspection image based on the fault inspection requirements of the system to be tested; The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes: The fault drill pipeline is determined according to the fault inspection information corresponding to the fault inspection image.

7. The fault drill method according to claim 3, characterized in that: The method of predefining a fault drill image based on the container management platform and according to the fault drill requirements of the system to be drilled includes: Predefine a fault recovery image based on the fault recovery requirements of the system to be drilled; The determining the fault drill pipeline according to the fault drill information corresponding to the fault drill image includes: The fault drill pipeline is determined according to the fault recovery information corresponding to the fault drill image.

8. The fault drill method according to claim 1, characterized in that: When the fault drill execution state is the running state, the step of determining the time when the current fault drill pipeline will next execute the fault drill on the system to be drilled comprises: Determining whether the current fault drill pipeline has completed the fault drill; If so, resetting the fault drill execution state type of the current fault drill pipeline to the end state; According to the end state, a random execution time for the next execution of the fault drill in the current fault drill pipeline is determined.

9. The fault drill method according to claim 1, characterized in that: When the fault drill execution state is in the end state, the step of determining the time for the next fault drill execution on the system to be drilled under the current fault drill pipeline includes: Determining, according to the time adjustment parameter in the container management platform, a random execution time for the next execution of the fault drill in the current fault drill pipeline; Reset the end state to the initial state.

10. The fault drill method according to claim 1, characterized in that: The acquisition of a fault drill pipeline set determined based on the container management platform includes: According to the timing trigger configured in the container management platform, a set of fault drill pipelines determined based on the container management platform is obtained.

11. A fault drill device, characterized in that: include: An acquisition unit is used to obtain a set of fault drill pipelines determined based on the container management platform; A first determining unit is configured to determine a fault drill execution state type of a current fault drill pipeline in the fault drill pipeline set in the system to be drilled, wherein the fault drill execution state type includes at least one state type of a running state, an initial state, and an end state; A second determining unit is configured to determine, according to the fault drill execution state type, a time when the current fault drill pipeline will next execute a fault drill on the system to be drilled; When the fault drill execution state is the initial state, the second determination unit is specifically used to: determine whether the current time of the system to be drilled is greater than or equal to the preset fault drill trigger time; if so, trigger the fault drill execution and set the initial state to the running state; according to the running state, determine the time when the current fault drill pipeline will next perform a fault drill on the system to be drilled.

Images