Chaotic engineering experiment plan transmission method and device, electronic equipment and medium

Abstract

The application discloses a method and device for transferring a chaos engineering experiment plan, electronic equipment and a medium. The method and device are applied to the electronic equipment, specifically, a system topology diagram is generated according to system deployment and a calling relationship; experiment plan information input by an applicant is received, an experiment level is determined according to the experiment plan information and the system topology diagram; and the transfer of the experiment plan information is performed according to the experiment level. Through the above scheme, the offline mode can be replaced, and based on the characteristics of electronic information, efficient transfer of the chaos engineering experiment plan is realized, and the time requirement of the system is met.

Description

Technical Field

[0001] This application relates to the field of chaos engineering technology, and more specifically, to a method, apparatus, electronic device, and medium for transmitting chaos engineering experimental plans. Background Technology

[0002] With the widespread application of IT technology in traditional industries, including finance, software system stability has become a crucial factor in supporting enterprise transformation and development, ensuring product and service quality, improving customer satisfaction, and controlling risks. Chaos engineering, as an important method for improving system stability, is gradually gaining attention from domestic enterprises.

[0003] However, as an emerging discipline, chaos engineering is still in its early stages of application in China. First, its adoption rate is low, with most domestic technology companies unfamiliar with or having never used chaos engineering-related technologies. Second, it accounts for a small proportion of business operations within enterprises and is used infrequently, mainly for trial use or sporadic pilot projects. Third, its application is still in its early stages, and for enterprise-level applications, most have not yet established technical and management support systems to continuously identify system problems and improve system stability through regular and periodic experiments.

[0004] For general testing methods, multiple systems can be tested simultaneously without interfering with each other. However, chaos engineering tests a system's response to faults and verifies its resilience by simulating fault scenarios. The injection of faults can affect the entire system, and if the scope of the impact is not well controlled, it can easily affect the normal operation of other systems. Therefore, in small-scale pilot projects, each system can operate in a relatively independent environment with relatively independent time and resources, resulting in minimal impact. However, large-scale deployment inevitably leads to resource reuse and scheduling conflicts. For example, systems A and B both depend on system C, and both need to perform link-level experiments with system C within the same time period.

[0005] Therefore, controlling the impact range, or blast radius, is a key focus of current research. From a time perspective, impact range control is generally divided into two stages: pre-event control and in-event control. Pre-event control typically involves an experimental plan application, where the organizer needs to explain the scope of the designed fault's impact and whether it will affect related systems. This usually requires informing and assessing related parties to avoid inadequate response due to last-minute notification after the fault occurs. However, current information transmission relies on offline communication, resulting in low efficiency and failing to meet the system's timeliness requirements. Summary of the Invention

[0006] In view of this, this application provides a method, apparatus, electronic device and medium for transmitting chaos engineering experimental plans, so as to achieve efficient transmission of chaos engineering experimental plans and meet the system's timeliness requirements.

[0007] To achieve the above objectives, the following solution is proposed:

[0008] A method for transmitting chaotic engineering experimental plans, applied to electronic devices, is shown, comprising the following steps:

[0009] Generate a system topology diagram based on system deployment and call relationships;

[0010] Receive experimental plan information input by the applicant, and determine the experimental level based on the experimental plan information and the system topology diagram;

[0011] The transmission of the experimental plan information is performed according to the experimental level.

[0012] Optionally, the experiment levels include system-level experiments, link-level experiments, and platform-level experiments.

[0013] Optionally, the step of transmitting the experimental plan information according to the experimental level includes the following steps:

[0014] For the aforementioned system-level experiment, the experiment plan information will be sent to the overall management for approval.

[0015] For the aforementioned link-level experiment, the experiment plan information will be sent to the experiment platform administrator for approval.

[0016] For the aforementioned platform-level experiment, the experiment plan information will be sent to the platform administrator for approval.

[0017] Optionally, after the overall management party or the platform management party approves the application, the applicant, related parties, fault scenarios, and fault times are marked on the system topology diagram.

[0018] A transfer device for a chaos engineering experiment plan, applied to an electronic device, is shown, comprising:

[0019] The topology generation module is configured to generate a system topology diagram based on the system deployment and call relationships;

[0020] The level determination module is configured to receive the experimental plan information input by the applicant and determine the experimental level based on the experimental plan information and the system topology diagram;

[0021] The information transmission module is configured to transmit the experimental plan information according to the experimental level.

[0022] Optionally, the experiment levels include system-level experiments, link-level experiments, and platform-level experiments.

[0023] Optionally, the information transmission module includes:

[0024] The first approval unit is configured to send the experiment plan information to the overall management for approval in response to the system-level experiment.

[0025] The second approval unit is configured to send the experiment plan information to the experiment platform management for approval in the case of the link-level experiment.

[0026] The third approval unit is configured to send the experiment plan information to the platform administrator for approval in response to the platform-level experiment.

[0027] Optionally, when the second approval unit or the third approval unit shown is further configured to mark the applicant and related parties, as well as the fault scenario and fault time, on the system topology diagram after the overall management party or the platform management party approves the application.

[0028] An electronic device includes at least one processor and a memory connected to the processor, wherein:

[0029] The memory is used to store computer programs or instructions;

[0030] The processor is used to execute real-time computer programs or instructions to enable the illustrated electronic device to implement the transmission method as described above.

[0031] A computer-readable medium is applied to an electronic device, the medium carrying one or more computer programs, the one or more computer programs being executable by the electronic device to enable the electronic device to perform the transmission method as described above.

[0032] As can be seen from the above technical solution, this application discloses a method, apparatus, electronic device, and medium for transmitting chaos engineering experimental plans. The method and apparatus are applied to electronic devices, specifically involving generating a system topology diagram based on system deployment and calling relationships; receiving experimental plan information input by the applicant; determining the experimental level based on the experimental plan information and the system topology diagram; and executing the transmission of the experimental plan information according to the experimental level. This solution can replace offline methods and, based on the characteristics of electronic information, achieves efficient transmission of chaos engineering experimental plans, meeting the system's timeliness requirements. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1This is a flowchart illustrating a method for transmitting a chaos engineering experiment plan according to an embodiment of this application.

[0035] Figure 2 This is a block diagram of a device for transmitting a chaos engineering experiment plan according to an embodiment of this application;

[0036] Figure 3 This is a block diagram of a transfer device for another chaotic engineering experiment plan according to an embodiment of this application;

[0037] Figure 4 This is a block diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0039] Example 1

[0040] Figure 1 A flowchart illustrating a method for transmitting a chaos engineering experiment plan, provided as an embodiment of this application.

[0041] like Figure 1 As shown, the transmission method provided in this embodiment is applied to an electronic device to transmit experimental plan information within the system, enabling relevant approvers to receive the experimental plan information in a timely and efficient manner. The electronic device can be understood as a computer, server, or a network information system composed of computers and / or servers with information processing and data computing capabilities. The transmission method includes the following steps:

[0042] S1. Generate a system topology diagram based on the system deployment and call relationships.

[0043] First, a system topology diagram is generated based on the system deployment and calling relationships. The system deployment refers to the device list, actual deployment location, and functions of each piece of hardware in the system.

[0044] S2. Determine the experiment level based on the experimental plan information and system topology diagram.

[0045] Before initiating an experiment, the applicant will input experiment plan information, including filling in the experiment plan, specifying the fault scenario, fault scope, fault time, and fault plan. After receiving the above experiment plan information from the applicant, the experiment level is determined. The experiment level can be determined as a system-level experiment, a link-level experiment, or a platform-level experiment, depending on the impact of the fault scope.

[0046] S3. Execute the transmission of experimental plan information according to the experimental level.

[0047] Specifically, for system-level experiments, only the host system itself is tested. During the experiment, there will be no interaction with related systems or isolation using barriers, and the overall experimental environment will not be affected. The experimental plan does not need to be sent to related systems for evaluation, but can be directly approved by the overall management of the Chaos Project. After approval, it will be published on the experimental platform in the form of a bulletin board.

[0048] For link-level experiments, the host system and systems in the call chain are tested. The experiment will affect systems that are time-coupled and have call relationships. When conducting link-level experiments, the applicant needs to select the affected systems in the system topology diagram. The experiment plan is pushed to the related systems by the experimental platform based on the selected related parties. After the evaluation and confirmation that there are no problems, it is submitted to the Chaos Engineering Experiment Platform Management for approval. The Experiment Platform Management evaluates and supplements the related systems based on the call relationships in the topology diagram and the fault scenario. After the supplemented related parties are confirmed to be in good condition, the approval is granted and published on the experimental platform in the form of a bulletin board. The application and related systems are marked with fault scenario, time and other information in the topology diagram.

[0049] For platform-level experiments, testing the host system and the entire cloud platform (such as Kubernetes) will affect all systems on the platform that are time-coupled. Therefore, the experiment plan is automatically pushed by the experiment platform to all systems running on the platform during the same time period for evaluation and confirmation. After confirming that there are no problems, it is submitted to the Chaos Engineering Experiment Platform Management for approval. After approval, it is published on the experiment platform in the form of a bulletin board. The application and associated systems are marked with experimental scenario, time and other information in the topology diagram.

[0050] In case of disputes, the experimental platform management will adjust the experimental plan based on the existing experimental information in the topology diagram and the information in this application, taking into account factors such as time urgency, failure scenario, and scope of impact.

[0051] After the test plan is released, especially for link-level experiments, if other systems identify this system as a related system, the applicant can be contacted for evaluation and then added to the related systems of the test plan before it is re-released.

[0052] As can be seen from the above technical solution, this embodiment provides a method for transmitting chaos engineering experiment plans. This method is applied to electronic devices and specifically involves generating a system topology diagram based on system deployment and calling relationships; receiving experiment plan information input by the applicant; determining the experiment level based on the experiment plan information and the system topology diagram; and transmitting the experiment plan information according to the experiment level. This solution can replace offline methods and, based on the characteristics of electronic information, achieves efficient transmission of chaos engineering experiment plans, meeting the system's timeliness requirements.

[0053] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0054] Although the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous.

[0055] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0056] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer.

[0057] Example 2

[0058] Figure 2 A block diagram of a transfer device for a chaos engineering experiment plan provided in an embodiment of this application.

[0059] like Figure 2As shown, the transmission device provided in this embodiment is applied to an electronic device to transmit experimental plan information in the system so that relevant approvers can receive the experimental plan information in a timely and efficient manner. The electronic device can be understood as a computer, server or network information system composed of a computer and / or server with information processing and data computing capabilities. The transmission device includes a topology map generation module 10, a level determination module 20 and an information transmission module 30.

[0060] The topology generation module is used to generate a system topology diagram based on the system deployment and call relationships.

[0061] First, a system topology diagram is generated based on the system deployment and calling relationships. The system deployment refers to the device list, actual deployment location, and functions of each piece of hardware in the system.

[0062] The level determination module is used to determine the experiment level based on the experiment plan information and the system topology diagram.

[0063] Before initiating an experiment, the applicant will input experiment plan information, including filling in the experiment plan, specifying the fault scenario, fault scope, fault time, and fault plan. After receiving the above experiment plan information from the applicant, the experiment level is determined. The experiment level can be determined as a system-level experiment, a link-level experiment, or a platform-level experiment, depending on the impact of the fault scope.

[0064] The information transmission module is used to transmit experimental plan information according to the experimental level. This module includes a first approval unit, a second approval unit, and a third approval unit.

[0065] The first approval unit is specifically used for system-level experiments. It only tests the host system itself. During the experiment, there will be no interaction with related systems or isolation using barriers. It will not affect the overall experimental environment. The experimental plan does not need to be sent to related systems for evaluation. It can be directly approved by the overall management of the Chaos Project. After approval, it will be published on the experimental platform in the form of a bulletin board.

[0066] The second approval unit is specifically used for link-level experiments to test the host system and systems in the call chain. The experiment will affect systems that are time-coupled and have call relationships. When conducting a link-level experiment, the applicant needs to select the affected systems in the system topology diagram. The experiment plan is pushed to the related systems by the experimental platform based on the selected related parties for evaluation and confirmation. After confirmation that there are no problems, it is submitted to the Chaos Engineering Experiment Platform Management for approval. The Experiment Platform Management evaluates and supplements the related systems based on the call relationships in the topology diagram and the current failure scenario. After confirming that there are no problems with the supplemented related parties, the approval is published on the experimental platform in the form of a bulletin board. The application and related systems are marked with information such as failure scenario and time in the topology diagram.

[0067] The third approval unit is specifically used for platform-level experiments. It tests the host system and the entire cloud platform (such as Kubernetes), which will affect all systems on the platform that are coupled in time. Therefore, the experiment plan is automatically pushed by the experiment platform to all systems running on the platform in the same time period for evaluation and confirmation. After confirming that there are no problems, it is submitted to the Chaos Engineering Experiment Platform Management for approval. After approval, it is published on the experiment platform in the form of a bulletin board. The application and associated systems are marked with experimental scenarios, time and other information in the topology diagram.

[0068] In case of disputes, the experimental platform management will adjust the experimental plan based on the existing experimental information in the topology diagram and the information in this application, taking into account factors such as time urgency, failure scenario, and scope of impact.

[0069] After the test plan is released, especially for link-level experiments, if other systems identify this system as a related system, the applicant can be contacted for evaluation and then added to the related systems of the test plan before it is re-released.

[0070] As can be seen from the above technical solution, this embodiment provides a device for transmitting chaos engineering experiment plans. This device is applied to electronic devices and specifically generates a system topology diagram based on system deployment and calling relationships; receives experiment plan information input by the applicant; determines the experiment level based on the experiment plan information and the system topology diagram; and executes the transmission of the experiment plan information according to the experiment level. This solution can replace offline methods and, based on the characteristics of electronic information, achieves efficient transmission of chaos engineering experiment plans, meeting the system's timeliness requirements.

[0071] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0072] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0073] Example 3

[0074] This embodiment provides an electronic device, referenced... Figure 4The diagram illustrates a structural schematic suitable for implementing the electronic device in the embodiments of this disclosure. The terminal device in the embodiments of this disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 4 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0075] like Figure 4 As shown, the electronic device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 606 into a random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the electronic device 600. The processing unit 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0076] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 606 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 4 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have instead.

[0077] Example 4

[0078] This embodiment provides a computer-readable medium carrying one or more programs. When these programs are executed by an electronic device, the electronic device enables the transmission of a chaos engineering experiment plan. This device, applied to the electronic device, specifically generates a system topology diagram based on system deployment and calling relationships; receives experiment plan information input by the applicant; determines the experiment level based on the experiment plan information and the system topology diagram; and transmits the experiment plan information according to the experiment level. This solution can replace offline methods and, based on the characteristics of electronic information, achieves efficient transmission of chaos engineering experiment plans, meeting the system's timeliness requirements.

[0079] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0080] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0081] Although preferred embodiments of the present invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present invention.

[0082] Finally, 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, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0083] The technical solution provided by the present invention has been described in detail above. Specific examples have been used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core idea of ​​the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation and application scope based on the idea of ​​the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for transmitting chaotic engineering experimental plans, applied to electronic devices, characterized in that, The transmission method shown includes the following steps: Generate a system topology diagram based on system deployment and call relationships; The system receives experimental plan information input by the applicant, determines the experimental level based on the experimental plan information and the system topology diagram, and classifies different experimental levels according to the degree of impact of the fault scope. The experimental levels include: system-level experiments, link-level experiments and platform-level experiments. For the system-level experiment, only the host system itself is tested. There is no need to interact with related systems or use barriers for isolation during the experiment, so as not to affect the overall experimental environment. The experimental plan information is sent to the overall management for approval. For the aforementioned link-level experiment, the host system and the systems in the call chain are tested. The experiment will affect systems that are time-coupled and have call relationships. The experiment plan information is pushed by the experiment platform to the associated system for evaluation and confirmation that there are no problems before being submitted to the experiment platform management for implementation approval. For the aforementioned platform-level experiment, testing is conducted on the host system and the entire cloud platform, which will affect all systems on the platform that are time-coupled. The experiment plan information is automatically pushed by the experiment platform to all systems running on the platform during the same time period for evaluation and confirmation. After confirming that there are no problems, it is submitted to the platform management for implementation and approval. Once the overall management party or the platform management party approves the application, the applicant, related parties, fault scenarios, and fault times are marked on the system topology diagram.

2. A device for transmitting chaotic engineering experimental plans, applied to electronic equipment, characterized in that, The conveying device shown includes: The topology generation module is configured to generate a system topology diagram based on the system deployment and call relationships; The level determination module is configured to receive the experiment plan information input by the applicant, and determine the experiment level based on the experiment plan information and the system topology diagram. Different experiment levels are divided according to the degree of impact of the fault range. The experiment levels include: system-level experiment, link-level experiment and platform-level experiment. The information transmission module is configured to test only the host system itself for the system-level experiment. During the experiment, there is no need to interact with related systems or use barriers for isolation, so as not to affect the overall experimental environment. The experiment plan information is sent to the overall management for approval. For the aforementioned link-level experiment, the host system and the systems in the call chain are tested. The experiment will affect systems that are time-coupled and have call relationships. The experiment plan information is pushed by the experiment platform to the associated system for evaluation and confirmation that there are no problems before being submitted to the experiment platform management for implementation approval. For the aforementioned platform-level experiment, testing is conducted on the host system and the entire cloud platform, which will affect all systems on the platform that are time-coupled. The experiment plan information is automatically pushed by the experiment platform to all systems running on the platform during the same time period for evaluation and confirmation. After confirming that there are no problems, it is submitted to the platform management for implementation and approval. Once the overall management party or the platform management party approves the application, the applicant, related parties, fault scenarios, and fault times are marked on the system topology diagram.

3. An electronic device, characterized in that, It includes at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs or instructions; The processor is used to execute real-time computer programs or instructions to enable the electronic device shown to implement the transmission method as described in claim 1.

4. A computer-readable medium for use in electronic devices, characterized in that, The medium carries one or more computer programs, which can be executed by the electronic device, enabling the electronic device to implement the transmission method as described in claim 1.

Images