System fault-tolerant test method, electronic device, and storage medium

Abstract

The application relates to the computer technical field, in particular to a system fault-tolerant test method, an electronic device and a storage medium. In the system fault-tolerant test method, the function characteristic type information and the disaster simulation program are acquired first, then the cloud platform system to be tested is divided into levels based on the function characteristic type information, a cloud system hierarchical model corresponding to the cloud platform system is obtained, further, a data disaster environment is simulated in the cloud system hierarchical model based on the disaster simulation program, finally, the cloud system hierarchical model in the data disaster environment is tested for fault tolerance, and fault-tolerant indexes corresponding to the cloud platform system are obtained. Through the system fault-tolerant test method, the data disaster of the cloud platform system is simulated based on the cloud system hierarchical model, so that the fault-tolerant indexes of the cloud platform system are obtained through the fault-tolerant test, and the fault-tolerant indexes of the cloud platform system can be more accurately measured.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, in particular to a system fault-tolerant testing method, an electronic device and a storage medium. BACKGROUND

[0002] With the development of cloud computing technology, more and more infrastructures can be compatible with cloud platforms, and more and more cloud computing technologies can be selected by users. In order to promote the openness of technology and prevent technology binding, users tend to use hybrid cloud technology, and hope that cloud platform technology can be compatible with different infrastructure technologies.

[0003] Kubernetes (K8S) is a portable container orchestration technology for container services. Kubernetes provides a series of functions such as deployment and running of containerized applications, resource scheduling, service discovery and dynamic scaling on the basis of Docker technology. At present, container platforms based on Kubernetes are widely used in production environments due to their portability, availability and scalability. Although Kubernetes itself has complete high-availability capabilities, if an irresistible data disaster occurs, the high availability of the cluster itself loses its effect. Therefore, how to accurately determine the fault-tolerant indicators of a cloud platform system has become a major problem to be solved in the industry. SUMMARY

[0004] The present application aims to at least solve one of the technical problems existing in the prior art. To this end, the present application provides a system fault-tolerant testing method, an electronic device and a storage medium, which can accurately determine the fault-tolerant indicators of a cloud platform system.

[0005] The system fault-tolerant testing method according to the first aspect of the present application comprises:

[0006] obtaining function characteristic type information and a disaster simulation program;

[0007] dividing the cloud platform system to be tested into levels based on the function characteristic type information to obtain a cloud system hierarchical model corresponding to the cloud platform system;

[0008] simulating a data disaster environment in the cloud system hierarchical model based on the disaster simulation program;

[0009] performing fault-tolerant testing on the cloud system hierarchical model in the data disaster environment to obtain fault-tolerant indicators corresponding to the cloud platform system.

[0010] According to some embodiments of the present application, the cloud platform system to be tested is divided into levels based on the function characteristic type information to obtain a cloud system hierarchical model corresponding to the cloud platform system, which comprises:

[0011] perform hierarchical division on the cloud platform system based on the function characteristic type information, to obtain a computing resource layer, a system control layer, a network layer, and an application layer, wherein the computing resource layer is configured to provide computing resources for the cloud platform system, the system control layer includes a control plane of the cloud platform system, the network layer is configured to manage network data communication of the cloud platform system, and the application layer is configured to enable the cloud platform system to provide a running environment for an application program;

[0012] The computing resource layer, the system control layer, the network layer, and the application layer are integrated to obtain the cloud system hierarchical model.

[0013] According to some embodiments of the present application, based on the disaster simulation program, a data disaster environment is simulated in the cloud system hierarchical model, which comprises:

[0014] Based on the disaster simulation program, a firewall is configured to intercept resource interaction data between the computing resource layer and the system control layer.

[0015] According to the intercepted resource interaction data, the computing resource layer in the data disaster environment is simulated in the cloud system hierarchical model.

[0016] According to some embodiments of the present application, the cloud system hierarchical model in the data disaster environment is subjected to fault tolerance testing, to obtain a fault tolerance index corresponding to the cloud platform system, which comprises:

[0017] When the cloud platform system is in a first fault running state, a resource adjustment index of the computing resource layer is configured to enable the cloud platform system to escape from the first fault running state.

[0018] When the cloud platform system is switched from the first fault running state to a normal running state, the configured resource adjustment index is included in the fault tolerance index.

[0019] According to some embodiments of the present application, based on the disaster simulation program, a data disaster environment is simulated in the cloud system hierarchical model, which comprises:

[0020] Based on the disaster simulation program, a communication blocking operation is performed on an application programming interface server, and the communication blocking operation is configured to interrupt all or part of communication data of the application programming interface server.

[0021] According to the communication blocking operation, the system control layer in the data disaster environment is simulated in the cloud system hierarchical model.

[0022] According to some embodiments of the present application, the fault-tolerant test on the cloud system hierarchical model in the data disaster environment obtains a fault-tolerant index corresponding to the cloud platform system, and the fault-tolerant test comprises:

[0023] When the cloud platform system is in a second fault operating state, a control adjustment index of the system control layer is configured to make the cloud platform system leave the second fault operating state;

[0024] When the cloud platform system switches from the second fault operating state to a normal operating state, the configured control adjustment index is included in the fault-tolerant index.

[0025] According to some embodiments of the present application, the data disaster environment is simulated in the cloud system hierarchical model based on the disaster simulation program, and the simulation comprises:

[0026] Based on the disaster simulation program, the traffic distribution of the network layer is controlled by an elastic load balancing control.

[0027] According to the traffic distribution of the network layer based on the elastic load balancing, the network layer in the cloud system hierarchical model is simulated in the data disaster environment.

[0028] According to some embodiments of the present application, the data disaster environment is simulated in the cloud system hierarchical model based on the disaster simulation program, and the simulation comprises:

[0029] Based on the disaster simulation program, the disabling or enabling of the application program in the application layer is controlled by a chaos test tool.

[0030] According to the disabling or enabling of the application program, the application layer in the cloud system hierarchical model is simulated in the data disaster environment.

[0031] In a second aspect, the embodiments of the present application provide an electronic device, comprising a memory and a processor, the memory stores a computer program, and the processor implements the system fault-tolerant test method according to any one of the embodiments of the first aspect of the present application when executing the computer program.

[0032] In a third aspect, the embodiments of the present application provide a computer readable storage medium, the storage medium stores a program, and the program is executed by a processor to implement the system fault-tolerant test method according to any one of the embodiments of the first aspect of the present application.

[0033] The system fault-tolerant test method, the electronic device, and the storage medium according to the embodiments of the present application have at least the following beneficial effects:

[0034] The system fault tolerance test method provided in the embodiments of the present application comprises the following steps: obtaining function characteristic type information and a disaster simulation program; performing hierarchical division on a cloud platform system to be tested based on the function characteristic type information, to obtain a cloud system hierarchical model corresponding to the cloud platform system; simulating a data disaster environment in the cloud system hierarchical model based on the disaster simulation program; and finally performing fault tolerance test on the cloud system hierarchical model in the data disaster environment, to obtain fault tolerance indexes corresponding to the cloud platform system. Through the system fault tolerance test method provided in the embodiments of the present application, the cloud platform system is simulated in a data disaster environment based on the cloud system hierarchical model, so that fault tolerance test is performed to obtain the fault tolerance indexes of the cloud platform system, and the fault tolerance indexes of the cloud platform system can be more accurately determined.

[0035] Additional aspects and advantages of the present application will be made apparent by the following description and the appended claims. BRIEF DESCRIPTION OF DRAWINGS

[0036] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description, taken in conjunction with the accompanying drawings, in which:

[0037] Figure 1 A system fault tolerance test method flowchart provided in the embodiments of the present application;

[0038] Figure 2 Another system fault tolerance test method flowchart provided in the embodiments of the present application;

[0039] Figure 3 Another system fault tolerance test method flowchart provided in the embodiments of the present application;

[0040] Figure 4 Another system fault tolerance test method flowchart provided in the embodiments of the present application;

[0041] Figure 5 Another system fault tolerance test method flowchart provided in the embodiments of the present application;

[0042] Figure 6 Another system fault tolerance test method flowchart provided in the embodiments of the present application;

[0043] Figure 7 Another system fault tolerance test method flowchart provided in the embodiments of the present application;

[0044] Figure 8 Another system fault tolerance test method flowchart provided in the embodiments of the present application;

[0045] Figure 9 An electronic device schematic diagram for performing the system fault tolerance test method provided in the embodiments of the present application; DETAILED DESCRIPTION

[0046] Embodiments of the present application are described below in detail with reference to the accompanying drawings, wherein the same or similar components are denoted by the same or similar reference numerals throughout the drawings. The embodiments described below are exemplary and are only intended to explain the present application, and should not be understood as limiting the present application.

[0047] In the description of the present application, the meaning of one or more is one or more, the meaning of multiple is two or more, greater than, less than, more than, etc. are understood as not including the number, above, below, within, etc. are understood as including the number. If it is described as first, second, it is only for the purpose of distinguishing technical features, and should not be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features or the order of indicated technical features.

[0048] In the description of the present application, it should be understood that the description of the position, such as up, down, left, right, front, back, etc. indicates the position or location relationship based on the position or location relationship shown in the drawings, which is only for the purpose of describing the present application and simplifying the description, and does not indicate or imply that the device or element indicated must have a specific position, be constructed and operated in a specific position, and therefore should not be understood as limiting the present application.

[0049] In the description of the present application, the description of the terms "one embodiment", "some embodiments", "exemplary embodiment", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the exemplary description of the above terms does not necessarily mean the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0050] In the description of the present application, it should be noted that, unless otherwise explicitly limited, the words such as setting, installing, connecting, etc. should be broadly understood, and those skilled in the art can reasonably determine the specific meaning of the above words in the present application in combination with the specific content of the technical solution. In addition, the identification of the specific steps in the following does not represent the limitation of the order and execution logic of the steps, and the execution order and execution logic between the steps should be understood and inferred with reference to the content expressed in the embodiments.

[0051] With the development of cloud computing technology, more and more infrastructures are compatible with cloud platforms, and users have more and more choices of cloud computing technologies. In order to promote the openness of technology and prevent technology binding, users tend to use hybrid cloud technology, hoping that cloud platform technology can be compatible with different infrastructure technologies.

[0052] It should be noted that the Kubernetes cloud platform is a container cluster management system that provides a container-centric infrastructure for simple and efficient deployment of containerized applications. The Kubernetes cloud platform supports automated deployment, large-scale scalability, and application container management. When deploying an application in a production environment, multiple instances of the application are usually deployed to balance the application request. In the Kubernetes cloud platform, we can create multiple containers, each running an application instance, and then use the built-in load balancing strategy to manage, discover, and access the group of application instances without the need for complex manual configuration and processing by the operation and maintenance personnel. The Kubernetes cloud platform has the advantages of portability, scalability, and automation. Among them, portability means that the Kubernetes cloud platform supports public cloud, private cloud, hybrid cloud, and multiple clouds; scalability means that the Kubernetes cloud platform supports modularity, plug-in, mountable, and combinable; automation means that the Kubernetes cloud platform supports automatic deployment, automatic restart, automatic replication, and automatic scaling / extension. The Kubernetes cloud platform provides deployment, planning, updating, and maintenance mechanisms for applications. It should be understood that the traditional application deployment method is to install the application through a plug-in or script, which has the disadvantage that the running, configuration, management, and entire life cycle of the application are bound to the current operating system, which is not conducive to application upgrade / update / rollback operations. Some functions can also be implemented by creating virtual machines, but virtual machines are very heavy and not conducive to portability. The Kubernetes cloud platform implements application deployment and orchestration through container deployment, each container is isolated from each other, each container has its own file system, and the processes between containers do not affect each other, and can distinguish computing resources. Compared with virtual machines, containers can be quickly deployed, and since containers are decoupled from the underlying infrastructure and machine file system, they can be migrated between different clouds and different versions of operating systems.

[0053] In the related art, there are two main modes for users to use Kubernetes: the first mode is a hosting mode, that is, a user purchases a ready-made Kubernetes service from a cloud service provider, hosts the entire Kubernetes platform to the cloud service provider for maintenance, and the user only serves as an application power user; the second mode is a self-hosting mode, that is, a user maintains a Kubernetes platform by himself / herself on a bare metal server or by using computing resources provided by a cloud service provider. The two modes have advantages and disadvantages and are suitable for different scenarios. The hosting mode is more suitable for application services of public clouds and has the advantages of being convenient and agile and having ready-made supporting services, and the disadvantage is that it is limited by the services provided by the cloud service provider. The self-hosting mode is more suitable for enterprises to build their own private cloud native services, and has the advantages of being able to build cloud services suitable for the characteristics of the user's own application and having the advantages of a private cloud, and the disadvantage is that the supporting services of the platform need to be provided and maintained by the user himself / herself, such as high availability and disaster recovery functions required by the production running environment, which need to be maintained by the user himself / herself. It should be noted that the system fault tolerance test method, the electronic device, and the storage medium provided by the embodiments of the present application are suitable for Kubernetes system fault tolerance test of the cloud service provider in the hosting mode and Kubernetes system fault tolerance test of the user himself / herself in the self-hosting mode. It should be understood that the application scenarios corresponding to the various embodiments of the present application can include, but are not limited to, the specific embodiments mentioned above.

[0054] Kubernetes (K8S) is a portable container orchestration management tool for container services. Kubernetes provides a series of functions such as deployment and running, resource scheduling, service discovery, and dynamic scaling for containerized applications on the basis of Docker technology, and improves the convenience and high availability of large-scale container cluster management. At present, the container platform based on Kubernetes is widely used in production environments due to its portability, availability, and scalability. Although Kubernetes itself has complete high availability capabilities, if an irresistible data disaster occurs, the high availability of the cluster itself loses its effect. Therefore, how to accurately determine the fault tolerance index of the cloud platform system has become a major problem to be solved in the industry.

[0055] The present application aims to at least solve one of the technical problems in the prior art. To this end, the present application provides a system fault tolerance test method, an electronic device, and a storage medium, which can accurately determine the fault tolerance index of the cloud platform system.

[0056] Further description is made below with reference to the accompanying drawings.

[0057] Reference Figure 1 The system fault tolerance test method according to the first aspect embodiment of the present application comprises:

[0058] Step S101, obtaining function characteristic type information and disaster simulation program;

[0059] According to some embodiments provided in the present application, the function characteristic type information reflects the function types implemented by different module components in the cloud platform system. For example, A1 module and A2 component in the cloud platform system jointly provide support for computing resource of the cloud platform system, A1 module and A2 component jointly implement the function of providing computing resource, and therefore the function characteristic type can reflect that the function types implemented by A1 module and A2 component are resource supply type; for another example, B1 module and B2 component in the cloud platform system jointly provide support for the control plane of the cloud platform system, B1 module and B2 component jointly implement the function of controlling or managing the cloud platform system, and therefore the function characteristic type can reflect that the function types implemented by B1 module and B2 component are system control type; for another example, C1 module and C2 component in the cloud platform system jointly provide support for network data interaction of the cloud platform system, C1 module and C2 component jointly implement the function of adjusting network data of the cloud platform system, and therefore the function characteristic type can reflect that the function types implemented by C1 module and C2 component are network interaction type; for another example, D1 module and D2 component in the cloud platform system jointly provide support for application program, D1 module and D2 component jointly implement the function of providing running environment for the application program, and therefore the function characteristic type can reflect that the function types implemented by D1 module and D2 component are application environment type. Therefore, the function characteristic type information can reflect various function types that can be implemented by various module components in the cloud platform system. It should be understood that the function types implemented by different module components in the cloud platform system can include, but are not limited to, the specific embodiments mentioned above.

[0060] It should be noted that the disaster simulation program refers to a pre-set program for simulating a data disaster environment. It should be understood that in order to test the fault tolerance of the cloud platform system when facing a data disaster and determine the fault tolerance index of the cloud platform system when facing a data disaster, it is necessary to simulate a data disaster by using a disaster simulation program, and further perform fault tolerance test on the cloud platform system based on the simulated data disaster environment.

[0061] Step S102, hierarchically dividing the cloud platform system to be tested based on the function characteristic type information, to obtain a cloud system hierarchical model corresponding to the cloud platform system;

[0062] According to some embodiments provided in the present application, since the cloud platform system has the characteristics of design layering, modularization, and interface abstraction, if the cloud platform system to be tested is hierarchically divided based on the functional characteristic type information, the complexity of the cloud platform system will be reduced, and the fault tolerance analysis of the cloud platform system will be facilitated, so that the fault tolerance test of the cloud platform system can be more accurate, and the fault tolerance index corresponding to the cloud platform system can be obtained. Therefore, in order to more accurately measure the fault tolerance index of the cloud platform system, in some embodiments of the present application, before simulating the data disaster environment and performing the fault tolerance test, the cloud platform system to be tested needs to be hierarchically divided based on the functional characteristic type information, and the cloud system hierarchical model corresponding to the cloud platform system is obtained.

[0063] It should be emphasized that the functional characteristic type information can reflect various types of functions that can be achieved by the collaboration of various module components in the cloud platform system. Therefore, some embodiments provided in the present application can hierarchically divide the cloud platform system to be tested based on the functional characteristic type information, and obtain the cloud system hierarchical model corresponding to the cloud platform system. It should be noted that the various levels of the cloud system hierarchical model can be distinguished based on the differences in the function types. For example, if the functional characteristic type information can reflect that the function types implemented by different module components in the cloud platform system include resource supply type, system control type, network interaction type, and application environment type, then the cloud platform system can be hierarchically divided based on the resource supply type, system control type, network interaction type, and application environment type, and the cloud platform system can be correspondingly divided into computing resource layer, system control layer, network layer, and application layer, and the computing resource layer, system control layer, network layer, and application layer jointly constitute the cloud system hierarchical model corresponding to the cloud platform system. According to some more specific embodiments of the present application, the cloud platform system can include, but is not limited to, a Kubernetes container cluster management system.

[0064] In step S103, a data disaster environment is simulated in the cloud system hierarchical model based on the disaster simulation program.

[0065] It should be emphasized that the disaster simulation program refers to a pre-set program for simulating a data disaster environment. It should be understood that in order to test the fault tolerance of the cloud platform system in the face of a data disaster, and to determine the fault tolerance index of the cloud platform system in the face of a data disaster, a disaster simulation program is needed to simulate a data disaster, and further fault tolerance testing of the cloud platform system based on the simulated data disaster environment. It should be noted that since the cloud system hierarchical model includes multiple levels divided based on functional characteristic type information, the functions implemented by each level of the cloud system hierarchical model are different. In some embodiments of the present application, multiple types of disaster simulation codes are pre-set in the disaster simulation program for the multiple functions implemented by each level of the cloud system hierarchical model. Among them, the multiple types of disaster simulation codes are respectively applied to create a data disaster environment in each level of the cloud system hierarchical model. Since the functions implemented by each level are different, the ways in which the multiple types of disaster simulation codes create a data disaster environment for each level will also be different.

[0066] Step S104, fault tolerance testing of the cloud system hierarchical model in the data disaster environment is performed to obtain the fault tolerance index corresponding to the cloud platform system.

[0067] According to some embodiments provided by the present application, after simulating a data disaster environment in the cloud system hierarchical model, fault tolerance testing of the cloud system hierarchical model in the data disaster environment can be performed to obtain the fault tolerance index corresponding to the cloud platform system. It should be noted that fault tolerance testing of the cloud system hierarchical model in the data disaster environment often requires multi-aspect testing of the cloud system hierarchical model in the data disaster environment, which can include, but is not limited to, testing the intensity of the data disaster environment in which the cloud system hierarchical model will be paralyzed, testing the compensation conditions required for the cloud system hierarchical model to recover after being paralyzed, the sensitivity of each data node in the cloud system hierarchical model to the data disaster environment, and other types of testing. It should be understood that after fault tolerance testing of the cloud system hierarchical model in the data disaster environment, the fault tolerance index corresponding to the cloud platform system can be obtained.

[0068] It should be emphasized that, since the cloud system hierarchical model includes multiple levels divided based on the function characteristic type information, the functions implemented by each level of the cloud system hierarchical model are different. In some embodiments of the present application, the fault tolerance test on the cloud system hierarchical model in the data disaster environment can be a fault tolerance test on each level of the cloud system hierarchical model in the data disaster environment. It should be understood that, since each level of the cloud system hierarchical model is obtained by hierarchical division of the cloud platform system to be tested based on the function characteristic type information, the fault tolerance test on each level of the cloud system hierarchical model in the data disaster environment can reduce the complexity of the cloud platform system, and thus can more accurately test the fault tolerance of the cloud platform system and obtain the fault tolerance indicators corresponding to the cloud platform system.

[0069] In the system fault tolerance test method of the embodiments of the present application, the function characteristic type information and the disaster simulation program are first obtained, then the cloud platform system to be tested is hierarchically divided based on the function characteristic type information to obtain the cloud system hierarchical model corresponding to the cloud platform system, further, the data disaster environment is simulated in the cloud system hierarchical model based on the disaster simulation program, and finally the fault tolerance test is performed on the cloud system hierarchical model in the data disaster environment to obtain the fault tolerance indicators corresponding to the cloud platform system. Through the system fault tolerance test method of the embodiments of the present application, the data disaster of the cloud platform system is simulated based on the cloud system hierarchical model, and thus the fault tolerance indicators of the cloud platform system are obtained by fault tolerance test, which can more accurately determine the fault tolerance indicators of the cloud platform system.

[0070] Referring to Figure 2 According to some embodiments of the present application, the cloud platform system to be tested is hierarchically divided based on the function characteristic type information to obtain the cloud system hierarchical model corresponding to the cloud platform system, which includes:

[0071] In step S201, the cloud platform system is hierarchically divided based on the function characteristic type information to obtain the computing resource layer, the system control layer, the network layer, and the application layer, wherein the computing resource layer is used to provide computing resources for the cloud platform system, the system control layer includes the control plane of the cloud platform system, the network layer is used to manage the network data communication of the cloud platform system, and the application layer is used to provide a running environment for the cloud platform system to run the application program.

[0072] In step S202, the computing resource layer, the system control layer, the network layer, and the application layer are integrated to obtain the cloud system hierarchical model.

[0073] According to some embodiments provided in the present application, since the cloud platform system has the characteristics of design layering, modularization and interface abstraction, if the cloud platform system to be tested is hierarchically divided based on the function characteristic type information, the complexity of the cloud platform system will be reduced, the fault tolerance analysis of the cloud platform system will be facilitated, and thus the fault tolerance test of the cloud platform system can be more accurately performed and the fault tolerance index corresponding to the cloud platform system can be obtained. Therefore, in order to more accurately determine the fault tolerance index of the cloud platform system, in some embodiments of the present application, before simulating the data disaster environment and performing the fault tolerance test, the cloud platform system to be tested needs to be hierarchically divided based on the function characteristic type information, and the cloud system hierarchical model corresponding to the cloud platform system is obtained.

[0074] According to some specific embodiments provided in the present application, the A1 module and the A2 component in the cloud platform system jointly provide support for computing power resources of the cloud platform system, so that the A1 module and the A2 component jointly function to provide computing power resources, and therefore the function characteristic type can reflect that the function type realized by the A1 module and the A2 component is a resource supply type. Further, based on the resource supply type, the cloud platform system is hierarchically divided, and the computing power resource layer can be correspondingly divided from the cloud platform system. For another example, the B1 module and the B2 component in the cloud platform system jointly provide support for the control plane of the cloud platform system, so that the B1 module and the B2 component jointly function to control or manage the cloud platform system, and therefore the function characteristic type can reflect that the function type realized by the B1 module and the B2 component is a system control type. Further, based on the system control type, the cloud platform system is hierarchically divided, and the system control layer can be correspondingly divided from the cloud platform system. For another example, the C1 module and the C2 component in the cloud platform system jointly provide support for the network data interaction of the cloud platform system, so that the C1 module and the C2 component jointly function to deploy the network data of the cloud platform system, and therefore the function characteristic type can reflect that the function type realized by the C1 module and the C2 component is a network interaction type. Further, based on the network interaction type, the cloud platform system is hierarchically divided, and the network layer can be correspondingly divided from the cloud platform system. For another example, the D1 module and the D2 component in the cloud platform system jointly provide support for the application program to provide a running environment, so that the D1 module and the D2 component jointly function to provide the cloud platform system to provide a running environment for the application program, and therefore the function characteristic type can reflect that the function type realized by the D1 module and the D2 component is an application environment type. Further, based on the application environment type, the cloud platform system is hierarchically divided, and the application layer can be correspondingly divided from the cloud platform system. It should be noted that the computing power resource layer is used to provide computing power resources for the cloud platform system, the system control layer includes the control plane of the cloud platform system, the network layer is used to manage the network data communication of the cloud platform system, and the application layer is used to make the cloud platform system provide a running environment for the application program. Therefore, the function characteristic type information can reflect various function types that can be realized by the division and cooperation of various modules and components in the cloud platform system. It should be understood that after the cloud platform system is hierarchically divided based on the function characteristic type information to obtain the computing power resource layer, the system control layer, the network layer and the application layer, the computing power resource layer, the system control layer, the network layer and the application layer can be integrated to obtain the cloud system hierarchical model.

[0075] With reference to Figure 3 According to some embodiments of the present application, based on the disaster simulation program, a data disaster environment is simulated in the cloud system hierarchical model, including:

[0076] Step S301, based on the disaster simulation program, configure the firewall to intercept the resource interaction data between the computing resource layer and the system control layer;

[0077] It should be emphasized that the disaster simulation program refers to a pre-set program for simulating a data disaster environment. It should be understood that in order to test the fault tolerance of the cloud platform system when facing a data disaster, and to determine the fault tolerance index of the cloud platform system when facing a data disaster, a disaster simulation program is needed to simulate a data disaster, and further fault tolerance testing of the cloud platform system based on the simulated data disaster environment. It should be noted that since the cloud system hierarchical model includes multiple levels divided based on functional characteristic type information, the functions implemented by each level of the cloud system hierarchical model are different. In some embodiments of the present application, multiple types of disaster simulation codes are pre-set in the disaster simulation program for the multiple functions implemented by each level of the cloud system hierarchical model. Among them, the multiple types of disaster simulation codes are respectively applied to create a data disaster environment in each level of the cloud system hierarchical model. Since the functions implemented by each level are different, the ways in which the multiple types of disaster simulation codes create a data disaster environment for each level will also be different. In the embodiments shown in steps S301 to S302, a way of simulating a data disaster simulation code for the computing resource layer is provided.

[0078] Step S302, according to the intercepted resource interaction data, simulate the computing resource layer in a data disaster environment in the cloud system hierarchical model.

[0079] According to some specific embodiments of the present application, the A1 module and the A2 component in the cloud platform system jointly provide support for computing power resources of the cloud platform system, so that the A1 module and the A2 component jointly act to provide computing power resources, and therefore the function characteristic type can reflect that the function type realized by the A1 module and the A2 component is a resource supply type. Further, based on the resource supply type, the cloud platform system is hierarchically divided, and the computing power resource layer can be divided from the cloud platform system. It should be noted that the computing power resource layer needs to rely on the resource interaction data between the system control layer to normally provide computing power resources to the cloud platform system, wherein the resource interaction data refers to the interaction data between the computing power resource layer and the system control layer for coordinating and deploying computing power resources. Therefore, when the resource interaction data between the computing power resource layer and the system control layer is intercepted, part or all of the computing nodes in the computing power resource layer can be simulated to fail, so as to simulate that the computing power resource layer is in a data disaster environment in the cloud system hierarchical model. It should be understood that the resource interaction data between the computing power resource layer and the system control layer can be intercepted in various ways. In some embodiments of the present application, the resource interaction data is intercepted by configuring a firewall. In some specific embodiments of the present application, the cloud platform system can include, but is not limited to, a Kubernetes container cluster management system. In order to simulate that the computing power resource layer is in a data disaster environment in the cloud system hierarchical model corresponding to the Kubernetes container cluster management system, the iptables command can be used to intercept the port traffic of Kubelet and Kube-proxy on the INPUT chain and the OUTPUT chain, so that the Kubelet service and the Kube-proxy service cannot normally operate, that is, part or all of the computing nodes in the computing power resource layer can be simulated to fail, and the computing power resource layer can be simulated in a data disaster environment. It should be noted that the iptables command is a firewall configuration command. The iptables can be directly configured, or configured through a front end or a graphical interface. The iptables command works with a packet filtering mechanism, so it analyzes the packet header of the requested packet, and matches according to the rules we set to decide whether it can enter the host. The INPUT chain and the OUTPUT chain are rule chain names in the iptables command, also known as hook functions. The INPUT chain is used to process input packets, and the OUTPUT chain is used to process output packets.In addition, Kubelet is a proxy component on the Kubernetes worker node, running on each node, Kubelet is the main service on the worker node, periodically receiving new or modified Pod specifications from the Kube-Apiserver component, and ensuring that the Pod and its containers run under the expected specification, while the component acts as a monitoring component of the worker node, reporting the health of the host to the Kube-Apiserver. Kube-proxy is a network proxy component on the Kubernetes worker node, running on each node. Kube-proxy is used to maintain network rules on the node, so that traffic to Service (through ClusterIP and port) is load balanced to the correct backend Pod. It should be understood that there are many ways to simulate the way the computing resource layer in the cloud system hierarchical model is in the data disaster environment, which can include, but is not limited to, the specific embodiments mentioned above.

[0080] Referring to Figure 4 According to some embodiments of the present application, the cloud system hierarchical model in the data disaster environment is fault-tolerant tested, and the fault-tolerant index corresponding to the cloud platform system is obtained, including:

[0081] Step S401, when the cloud platform system is in a first fault running state, the resource adjustment index of the computing resource layer is configured to make the cloud platform system leave the first fault running state;

[0082] According to some embodiments provided in the present application, after simulating the data disaster environment in the cloud system hierarchical model, the cloud system hierarchical model in the data disaster environment can be tested for fault tolerance to obtain the fault tolerance index corresponding to the cloud platform system. It should be noted that the cloud system hierarchical model in the data disaster environment often needs to be tested in multiple aspects, which can include, but is not limited to: testing how much intensity of the data disaster environment the cloud system hierarchical model will be paralyzed in, testing what compensation conditions are needed to make the system return to operation after the cloud system hierarchical model is paralyzed, the sensitivity of each data node in the cloud system hierarchical model to the data disaster environment, and other types of tests. It should be understood that after the cloud system hierarchical model in the data disaster environment is tested for fault tolerance, the fault tolerance index corresponding to the cloud platform system can be obtained. According to some more specific embodiments provided in the present application, the first fault operating state refers to the fault operating state of the cloud platform system after the data disaster environment of the computing resource layer of the cloud system hierarchical model. The resource adjustment index refers to the adjustment index configured to make the cloud platform system switch from the first fault operating state to the normal operating state. Therefore, when the cloud platform system is in the first fault operating state, the resource adjustment index of the computing resource layer needs to be configured to make the cloud platform system escape from the first fault operating state. For example, when too many simulated failed computing nodes in the computing resource layer, the cloud platform system immediately enters the first fault operating state, and then the resource adjustment index of the computing resource layer (such as newly supplementing computing nodes in the computing resource layer) is configured in this case to make the cloud platform system escape from the first fault operating state and switch to the normal operating state.

[0083] In step S402, when the cloud platform system switches from the first fault operating state to the normal operating state, the configured resource adjustment index is included in the fault tolerance index.

[0084] According to some embodiments provided in the present application, during the process of testing the cloud system hierarchical model in the data disaster environment for fault tolerance, if the cloud platform system switches from the first fault operating state to the normal operating state, it indicates that the corresponding configured resource adjustment index can accurately reflect the fault tolerance of the cloud platform system, and then in this case, the configured resource adjustment index can be included in the fault tolerance index.

[0085] Reference Figure 5 According to some embodiments of the present application, based on the disaster simulation program, the data disaster environment is simulated in the cloud system hierarchical model, which includes:

[0086] In step S501, based on the disaster simulation program, a communication blocking operation is performed on the application programming interface server, and the communication blocking operation is used to interrupt all or part of the communication data of the application programming interface server;

[0087] At step S502, according to the communication blocking operation, simulate the system control layer in the cloud system hierarchical model in a data disaster environment.

[0088] It should be emphasized that the disaster simulation program refers to a pre-set program for simulating a data disaster environment. It should be understood that in order to test the fault tolerance of the cloud platform system when facing a data disaster, and to determine the fault tolerance index of the cloud platform system when facing a data disaster, a disaster simulation program is needed to simulate a data disaster, and further fault tolerance testing of the cloud platform system based on the simulated data disaster environment. It should be noted that since the cloud system hierarchical model includes multiple levels divided based on functional characteristic type information, the functions implemented by each level of the cloud system hierarchical model are different. In some embodiments of the present application, multiple types of disaster simulation codes are pre-set in the disaster simulation program for the multiple functions implemented by the multiple levels of the cloud system hierarchical model. Among them, the multiple types of disaster simulation codes are respectively applied to create a data disaster environment in each level of the cloud system hierarchical model. Since the functions implemented by each level are different, the ways in which the multiple types of disaster simulation codes create a data disaster environment for each level will also be different. In the embodiments shown in steps S501 to S502, a way of simulating a data disaster simulation code for the system control layer is provided.

[0089] According to some specific embodiments of the present application, the B1 module and the B2 component in the cloud platform system jointly provide support for the control plane of the cloud platform system, and the B1 module and the B2 component jointly function to control or manage the cloud platform system, so the function feature type can reflect that the function type realized by the B1 module and the B2 component is a system control type, and further, based on the system control type, the cloud platform system is hierarchically divided, and the system control layer can be divided from the cloud platform system, wherein the system control layer includes the control plane of the cloud platform system. It should be noted that the application programming interface server (Apiserver) provides a data bus and a data center for the cloud platform system, and it should be clear that the system control layer delivers control instructions to each module component in the cloud platform system via the application programming interface server, so that the cloud platform system can normally operate. The communication blocking operation refers to an operation for blocking or stalling the normal communication between the application programming interface server and each module component of the cloud platform system, and it should be understood that the communication blocking operation is used to interrupt all or part of the communication data of the application programming interface server. In some specific embodiments of the present application, the cloud platform system can include, but is not limited to, a Kubernetes container cluster management system. Since Kube-Apiserver, Kube-Controller, and Etcd in the Kubernetes container cluster management system all participate in forming the data bus or data center of the Kubernetes container cluster management system, in some embodiments of the present application, in order to simulate that the system control layer is in a data disaster environment in the cloud system hierarchical model corresponding to the Kubernetes container cluster management system, the communication blocking operation can be performed on Kube-Apiserver, Kube-Controller, and Etcd to make the control plane of the Kubernetes container cluster management system unable to normally operate, that is, part or all of the control nodes in the system control layer can be simulated to fail, and the system control layer can be simulated in a data disaster environment. It should be understood that the iptables command is a firewall configuration command, and therefore the iptables command can also perform the communication blocking operation in the manner of intercepting the control instructions of the system control layer. It should be understood that there are various ways to simulate that the system control layer is in a data disaster environment in the cloud system hierarchical model, which can include, but is not limited to, the specific embodiments described above.

[0090] Referring to Figure 6 According to some embodiments of the present application, the cloud system hierarchical model in the data disaster environment is tested for fault tolerance to obtain fault tolerance indicators corresponding to the cloud platform system, including:

[0091] Step S601, when the cloud platform system is in the second fault running state, configuring a control adjustment index of the system control layer to make the cloud platform system out of the second fault running state.

[0092] According to some embodiments provided in the present application, after simulating the data disaster environment in the cloud system hierarchical model, the cloud system hierarchical model in the data disaster environment can be tested for fault tolerance to obtain the fault tolerance index corresponding to the cloud platform system. It should be noted that the cloud system hierarchical model in the data disaster environment often needs to be tested in multiple aspects, which can include, but is not limited to: testing how much intensity of the data disaster environment the cloud system hierarchical model can fall into paralysis, testing what compensation conditions are needed to make the system return to operation after the cloud system hierarchical model falls into paralysis, the sensitivity of each data node in the cloud system hierarchical model to the data disaster environment, and other types of tests. It should be understood that after the cloud system hierarchical model in the data disaster environment is tested for fault tolerance, the fault tolerance index corresponding to the cloud platform system can be obtained. According to some more specific embodiments provided in the present application, the second fault running state refers to the fault running state of the cloud platform system after the system control layer of the cloud system hierarchical model faces the data disaster environment. The control adjustment index refers to the adjustment index configured to make the cloud platform system switch from the second fault running state to the normal running state. Therefore, when the cloud platform system is in the second fault running state, the control adjustment index of the system control layer needs to be configured to make the cloud platform system out of the second fault running state.

[0093] Step S602, when the cloud platform system switches from the second fault running state to the normal running state, the configured control adjustment index is included in the fault tolerance index.

[0094] According to some embodiments provided in the present application, during the process of testing the cloud system hierarchical model in the data disaster environment for fault tolerance, if the cloud platform system switches from the second fault running state to the normal running state, it indicates that the corresponding configured control adjustment index can accurately reflect the fault tolerance of the cloud platform system. Therefore, in this case, the configured control adjustment index can be included in the fault tolerance index.

[0095] Reference Figure 7 According to some embodiments of the present application, the data disaster environment in the cloud system hierarchical model is simulated based on the disaster simulation program, which includes:

[0096] Step S701, based on the disaster simulation program, the traffic distribution of the network layer is controlled by the elastic load balancing control.

[0097] Step S702, according to the traffic distribution of the network layer by the elastic load balancing, the network layer in the cloud system hierarchical model is simulated in the data disaster environment.

[0098] It is emphasized that the disaster simulation program refers to a pre-set program for simulating a data disaster environment. It should be understood that in order to test the fault tolerance of the cloud platform system when facing a data disaster, and to determine the fault tolerance index of the cloud platform system when facing a data disaster, a disaster simulation program is needed to simulate a data disaster, and further fault tolerance testing of the cloud platform system based on the simulated data disaster environment. It should be noted that since the cloud system hierarchical model includes multiple levels divided based on functional characteristic type information, the functions implemented by each level of the cloud system hierarchical model are different. In some embodiments of the present application, multiple types of disaster simulation codes are pre-set in the disaster simulation program for the multiple functions implemented by each level of the cloud system hierarchical model. Among them, the multiple types of disaster simulation codes are respectively used to create a data disaster environment in each level of the cloud system hierarchical model. Since the functions implemented by each level are different, the ways in which the multiple types of disaster simulation codes create a data disaster environment for each level will also be different. In the embodiments shown in steps S701 to S702, a way of simulating a data disaster simulation code for the network layer is provided.

[0099] According to some more specific embodiments of the present application, the C1 module and the C2 component in the cloud platform system are jointly responsible for deploying the network data interaction of the cloud platform system. Therefore, the C1 module and the C2 component jointly act to implement the deployment of the network data of the cloud platform system, and thus the functional characteristic type can reflect that the functional type implemented by the C1 module and the C2 component is a network interaction type. Further, based on the network interaction type, the cloud platform system is divided into levels, and the network layer can be divided from the cloud platform system. The network layer is used to manage the network data communication of the cloud platform system. It should be noted that elastic load balancing (Elastic Load Balance, ELB) refers to a traffic distribution control service that distributes access traffic to multiple backend servers according to distribution strategies. The elastic load balancing can expand the service capability of the application system to the outside through traffic distribution, and at the same time, it can improve the availability of the application system by eliminating single point of failure. In some more specific embodiments of the present application, the cloud platform system can include, but is not limited to, a Kubernetes container cluster management system. In order to simulate that the network layer is in a data disaster environment in the cloud system hierarchical model corresponding to the Kubernetes container cluster management system, the traffic distribution of the cloud platform system can be controlled through the elastic load balancing, so that the network communication of the cloud platform system cannot normally operate, that is, the network layer can be simulated to be partially or completely disabled, and further to simulate the data disaster environment of the network layer.

[0100] Reference Figure 8According to some embodiments of the present application, based on the disaster simulation program, a data disaster environment is simulated in the cloud system hierarchical model, including:

[0101] In step S801, based on the disaster simulation program, the disabling or enabling of the application program in the application layer is controlled by the chaos test tool.

[0102] In step S802, according to the disabling or enabling of the application program, the application layer is simulated in the data disaster environment in the cloud system hierarchical model.

[0103] It should be emphasized that the disaster simulation program refers to a pre-set program for simulating a data disaster environment. It should be understood that in order to test the fault tolerance of the cloud platform system when facing a data disaster and determine the fault tolerance index of the cloud platform system when facing a data disaster, a disaster simulation program is needed to simulate a data disaster, and further fault tolerance testing of the cloud platform system is based on the simulated data disaster environment. It should be noted that since the cloud system hierarchical model includes multiple levels divided based on functional characteristic type information, the functions implemented by each level of the cloud system hierarchical model are different. In some embodiments of the present application, multiple types of disaster simulation codes are pre-set in the disaster simulation program for the multiple functions implemented by the multiple levels of the cloud system hierarchical model. Among them, the multiple types of disaster simulation codes are respectively applied to create a data disaster environment in each level of the cloud system hierarchical model. Since the functions implemented by each level are different, the ways in which the multiple types of disaster simulation codes create a data disaster environment for each level will also be different. In the embodiments shown in steps S801 to S802, a way of simulating a data disaster simulation code for the application layer is provided.

[0104] According to some specific embodiments of the present application, the D1 module and the D2 component in the cloud platform system jointly provide a running environment for the application program, and the D1 module and the D2 component jointly provide the running environment for the application program in the cloud platform system, so the function feature type can reflect that the function type realized by the D1 module and the D2 component is an application environment type, and further, based on the application environment type, the cloud platform system is hierarchically divided, and the application layer can be correspondingly divided from the cloud platform system, wherein the application layer is used to provide a running environment for the application program by the cloud platform system. It should be noted that the chaos test refers to verifying whether the system has corresponding monitoring alarm, preplan processing, targeted reinforcement and prevention when encountering various exceptions, so as to avoid serious consequences caused by faults, and the anti-interference of the system is enhanced by monitoring alarm and preplan processing in advance. The chaos test tool refers to a tool used for chaos test. In some specific embodiments of the present application, the cloud platform system can include, but is not limited to, a Kubernetes container cluster management system. In order to simulate the application layer in the data disaster environment in the cloud system hierarchical model corresponding to the Kubernetes container cluster management system, the application layer can be simulated in the data disaster environment by Kube-monkey, PowerfulSeal or other types of Kube-monkey. It should be noted that Kube-monkey is a tool following the principle of chaos engineering, which can randomly delete pods in the Kubernetes container cluster management system, check whether the service has fault recovery capability, and help to improve the health of the system. Kube-monkey is configured by a TOML file, and the application program to be disabled and when to practice the recovery strategy can be specified in the file. PowerfulSeal is a tool similar to Kube-monkey, also following the principle of chaos engineering, wherein PowerfulSeal can delete pods and delete / add virtual machines from the cluster. Compared with Kube-monkey, PowefulSeal has an interactive mode, which allows to interrupt specific cluster components. It should be understood that there are various ways to simulate the application layer in the data disaster environment in the cloud system hierarchical model, which can include, but are not limited to, the specific embodiments mentioned above.

[0105] Figure 9 The electronic device 900 provided by the embodiments of the present application is shown. The electronic device 900 includes a processor 901, a memory 902, and a computer program stored in the memory 902 and executable on the processor 901, and the computer program is used to execute the system fault tolerance test method described above when running.

[0106] The processor 901 and the memory 902 can be connected by a bus or other means.

[0107] The memory 902, as a non-transitory computer readable storage medium, can be used to store non-transitory software programs and non-transitory computer executable programs, such as the system fault tolerance test method described in the embodiments of the present application. The processor 901 implements the system fault tolerance test method described above by running the non-transitory software programs and instructions stored in the memory 902.

[0108] The memory 902 can include a program storage area and a data storage area, wherein the program storage area can store an operating system and at least one application required by a function. The data storage area can store the system fault tolerance test method described above. In addition, the memory 902 can include a high-speed random access memory 902, and can also include a non-transitory memory 902, such as at least one storage device, a flash memory device, or other non-transitory solid-state memory device. In some embodiments, the memory 902 can optionally include a memory 902 remotely arranged with respect to the processor 901, and these remote memories 902 can be connected to the electronic device 900 through a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0109] The non-transitory software programs and instructions required to implement the system fault tolerance test method described above are stored in the memory 902, and when executed by one or more processors 901, the system fault tolerance test method described above is executed, for example, the method steps S101 to S104 in Figure 1 , the method steps S201 to S202 in Figure 2 , the method steps S301 to S302 in Figure 3 , the method steps S401 to S402 in Figure 4 , the method steps S501 to S502 in Figure 5 , the method steps S601 to S602 in Figure 6 , the method steps S701 to S702 in Figure 7 , and the method steps S801 to S802 in Figure 8 .

[0110] The embodiments of the present application also provide a computer readable storage medium storing computer executable instructions for executing the system fault tolerance test method described above.

[0111] In an embodiment, the computer readable storage medium stores computer executable instructions executed by one or more control processors, for example, the method steps S101 to S104 in Figure 1 , the method steps S201 to S202 in Figure 2 , the method steps S301 to S302 in Figure 3the method steps S301-S302 in the method of Figure 4 the method steps S401-S402 in the method of Figure 5 the method steps S501-S502 in the method of Figure 6 the method steps S601-S602 in the method of Figure 7 the method steps S701-S702 in the method of Figure 8 the method steps S801-S802 in the method of

[0112] The device embodiments described above are merely illustrative, wherein the units described as separate components can or can not be physically separate, i.e., can be located in one place, or can also be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment.

[0113] Those skilled in the art can understand that all or some steps in the above disclosed method, system can be implemented as software, firmware, hardware and appropriate combinations thereof. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software can be distributed on a computer readable medium, which can include computer storage media (or non-transitory media) and communication media (or transitory media). As known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, storage device storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. In addition, as known to those skilled in the art, communication media generally includes computer readable instructions, data structures, program modules or other data in modulated data signals such as carriers or other transmission mechanisms, and can include any information delivery medium. It should also be understood that the various embodiments provided by the present application can be combined in any manner to achieve different technical effects.

[0114] The above is a specific description of the preferred embodiments of the present application, but the present application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or replacements without departing from the spirit of the present application, and these equivalent modifications or replacements are all included in the scope defined by the claims of the present application.

Claims

1. A system fault-tolerant testing method, characterized by, The application comprises the following steps: acquiring function characteristic type information and a disaster simulation program; dividing the cloud platform system to be tested into layers based on the function characteristic type information, to obtain a computing resource layer, a system control layer, a network layer, and an application layer, wherein the computing resource layer is configured to provide computing resources for the cloud platform system, the system control layer comprises a control plane of the cloud platform system, the network layer is configured to manage network data communication of the cloud platform system, and the application layer is configured to enable the cloud platform system to provide a running environment for an application program; integrating the computing resource layer, the system control layer, the network layer, and the application layer to obtain a cloud system hierarchical model corresponding to the cloud platform system; simulating a data disaster environment in the cloud system hierarchical model based on the disaster simulation program; performing fault tolerance testing on the cloud system hierarchical model in the data disaster environment to obtain a fault tolerance index corresponding to the cloud platform system; wherein the step of simulating a data disaster environment in the cloud system hierarchical model based on the disaster simulation program comprises the following steps: based on the disaster simulation program, performing a communication blocking operation on an application programming interface server, wherein the communication blocking operation is configured to interrupt all or part of the communication data of the application programming interface server; based on the communication blocking operation, simulating that the system control layer is in the data disaster environment in the cloud system hierarchical model; and based on the disaster simulation program, controlling the disabling or enabling of the application program in the application layer by using a chaos testing tool; based on the disabling or enabling of the application program, simulating that the application layer is in the data disaster environment in the cloud system hierarchical model. The step of simulating a data disaster environment in the cloud system hierarchical model based on the disaster simulation program comprises the following steps:

2. The method of claim 1, wherein, based on the disaster simulation program, configuring a firewall to intercept resource interaction data between the computing resource layer and the system control layer; based on the intercepted resource interaction data, simulating that the computing resource layer is in the data disaster environment in the cloud system hierarchical model. The step of performing fault tolerance testing on the cloud system hierarchical model in the data disaster environment to obtain a fault tolerance index corresponding to the cloud platform system comprises the following steps:

3. The method of claim 2, wherein, when the cloud platform system is in a first fault running state, configuring a resource adjustment index of the computing resource layer to enable the cloud platform system to escape from the first fault running state; when the cloud platform system switches from the first fault running state to a normal running state, incorporating the configured resource adjustment index into the fault tolerance index. The step of performing fault tolerance testing on the cloud system hierarchical model in the data disaster environment to obtain a fault tolerance index corresponding to the cloud platform system comprises the following steps:

4. The method of claim 1, wherein, when the cloud platform system is in a second fault running state, configuring a control adjustment index of the system control layer to enable the cloud platform system to escape from the second fault running state; when the cloud platform system switches from the second fault running state to a normal running state, incorporating the configured control adjustment index into the fault tolerance index. ​ 5. The method of claim 1, wherein, The disaster simulation program is used to simulate a data disaster environment in the cloud system hierarchical model, including: Based on the disaster simulation program, the traffic distribution of the network layer is controlled by the elastic load balancing; According to the traffic distribution of the network layer by the elastic load balancing, the network layer in the cloud system hierarchical model is simulated in the data disaster environment.

6. An electronic device, comprising: Comprising: A memory storing a computer program, and a processor, wherein the processor executes the computer program to realize the system fault tolerance test method according to any one of claims 1 to 5.

7. A computer-readable storage medium, characterized in that, The storage medium stores a program, and the program is executed by the processor to realize the system fault tolerance test method according to any one of claims 1 to 5.

Images