CN114764379A - Access switching method and device for application software and computer readable storage medium - Google Patents

Abstract

Embodiments of the present invention disclose an access switching method, device, and computer-readable storage medium for application software, so as to solve the problem of excessive time-consuming access switching in the prior art, resulting in an increase in abnormal time; in this application, if the target deployment unit is abnormal, the Query the running status of the disaster recovery deployment unit corresponding to the target deployment unit; if the running status of the disaster recovery deployment unit is normal, switch the access request to the target network address corresponding to the disaster recovery deployment unit; this application queries the operation status of the disaster recovery deployment unit by querying the operation status of the disaster recovery deployment unit. Status to determine whether to perform access switching of application software, simplify switching operations, reduce abnormal time, and ensure that switching operations can restore normal application access; and by judging whether the target deployment unit has deployed the corresponding disaster recovery deployment unit, only the corresponding The target deployment unit of the disaster recovery deployment unit provides the access switching service of the application software, and provides guarantee for the access switching of the application software.

Description

Application software access switching method, device and computer-readable storage medium

technical field

The present invention relates to the technical field of service cluster containers, in particular to an access switching method, device and computer-readable storage medium for application software.

Background technique

In large-scale Internet applications, applications are stored in server clusters, and users obtain application services by accessing applications in the server clusters.

When a server in the server cluster fails, the application will be inaccessible. If the failure time is relatively long, the application will not be able to provide the corresponding application service, which will make the application-related business abnormal and bring huge losses to the company. Therefore, it is necessary to establish Disaster recovery system to ensure the normal access of applications; the existing disaster recovery establishment technology usually deploys cloud platform component containers for data backup through the kubernetes container orchestration framework. After the server cluster crashes, start a new kubernetes container to read the backup data, Then, the application is rebuilt on the spot, and after the application is rebuilt, the user's access request is switched to the rebuilt application, so that the application response time is longer due to the longer application rebuilding time.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide an access switching method, device, and computer-readable storage medium for application software, which solve the technical problems of long application recovery time and slow access request response speed when a service cluster fails in the prior art.

On the one hand, the present application provides an access switching method for application software, the method comprising:

Receive an access request, and obtain the initial access address associated with the access request;

If the target deployment unit corresponding to the initial access address is abnormal, determine whether the target deployment unit has deployed the corresponding disaster recovery deployment unit;

If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the running status of the disaster recovery deployment unit;

If the running state of the disaster recovery deployment unit is normal, the access request is switched to the target network address corresponding to the disaster recovery deployment unit.

In some embodiments of the present application, before the receiving an access request and acquiring the initial access address associated with the access request, the method includes:

receiving a disaster recovery deployment request, and determining application software corresponding to the disaster recovery deployment request, and a set of deployment units associated with the application software;

Obtaining the deployment unit identifiers to be deployed in the deployment unit set, and the operation information of the deployment units corresponding to the deployment unit identifiers;

According to the operation information of each deployment unit, the disaster recovery deployment unit of each deployment unit is deployed, and the device corresponding to each disaster recovery deployment unit is used as the disaster recovery cluster corresponding to the application software.

In some embodiments of the present application, according to the operation information of each deployment unit, the disaster recovery deployment unit of each deployment unit is deployed, and the device corresponding to each disaster recovery deployment unit is used as the corresponding device of the application software. Disaster recovery cluster, including:

Obtain configuration information associated with each deployment unit according to the operation information of each deployment unit;

Extracting dependencies and environment variables corresponding to each deployment unit from the configuration information associated with each deployment unit, and determining whether the dependencies corresponding to each deployment unit include disaster tolerance dependencies;

If the dependencies corresponding to each deployment unit include disaster tolerance dependencies, create a disaster tolerance deployment unit of each deployment unit according to the disaster tolerance dependencies corresponding to each deployment unit, The device corresponding to the disaster recovery deployment unit is used as the disaster recovery cluster corresponding to the application software;

If the dependencies corresponding to the deployment units do not include disaster tolerance dependencies, configure the disaster tolerance dependencies corresponding to the dependencies through the environment variables corresponding to the deployment units, and configure the disaster tolerance dependencies according to the environment variables corresponding to the deployment units. The disaster recovery dependency creates a disaster recovery deployment unit of each of the deployment units, and uses the device corresponding to each of the disaster recovery deployment units as a disaster recovery cluster corresponding to the application software.

In some embodiments of the present application, according to the operation information of each deployment unit, the disaster recovery deployment unit of each deployment unit is deployed, and the device corresponding to each disaster recovery deployment unit is used as the corresponding device of the application software. After the disaster recovery cluster, the method includes:

Detecting the operation information of each of the deployment units, and determining the target deployment unit whose operation information is updated;

According to the operation information of the target deployment unit, the operation information of the disaster recovery deployment unit corresponding to the target deployment unit is updated.

In some embodiments of the present application, if the target deployment unit corresponding to the initial access address is abnormal, determining whether the target deployment unit has deployed the corresponding disaster recovery deployment unit includes:

If the target deployment unit corresponding to the initial access address is abnormal, determine whether the target deployment unit has a corresponding disaster recovery deployment unit;

If the target deployment unit has a corresponding disaster recovery deployment unit, comparing the dependency of the target deployment unit with the disaster recovery dependency of the disaster recovery deployment unit;

If the dependency of the target deployment unit matches the disaster recovery dependency of the disaster recovery deployment unit, it is determined that the target deployment unit has deployed the corresponding disaster recovery deployment unit;

If the target deployment unit does not have a corresponding disaster recovery deployment unit, and/or the dependency of the target deployment unit does not match the disaster recovery dependency of the disaster recovery deployment unit, it is determined that the target deployment unit is not deployed The corresponding disaster recovery deployment unit.

In some embodiments of the present application, if the target deployment unit has deployed a corresponding disaster recovery deployment unit, querying the running status of the disaster recovery deployment unit includes:

If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the status of the disaster recovery deployment unit corresponding to the target deployment unit;

If the status of the disaster recovery deployment unit is activated, query the running status of the disaster recovery deployment unit according to the operation information of the disaster recovery deployment unit;

If the status of the disaster recovery deployment unit is not started, the disaster recovery deployment unit is started, and the running information of the disaster recovery deployment unit is updated.

In some embodiments of the present application, if the target deployment unit has deployed the corresponding disaster recovery deployment unit, querying the startup status of the disaster recovery deployment unit corresponding to the target deployment unit includes:

If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query whether the disaster recovery deployment unit corresponding to the target deployment unit has completed scheduling to determine the startup state of the disaster recovery deployment unit;

If the target deployment unit corresponding to the disaster recovery deployment unit completes the scheduling, it is determined that the startup status of the disaster recovery deployment unit is started;

If the disaster recovery deployment unit corresponding to the target deployment unit has not completed the scheduling, it is determined that the startup state of the disaster recovery deployment unit is not started;

If the startup status of the disaster recovery deployment unit is started, querying the running status of the disaster recovery deployment unit according to the operation information of the disaster recovery deployment unit includes:

If the status of the disaster recovery deployment unit is activated, acquiring the operation information of the disaster recovery deployment unit;

Perform a health check on the running information through a probe, and query the running status of the disaster recovery deployment unit;

If the health check of the operation information is passed, it is determined that the operation state of the disaster recovery deployment unit is normal;

If the health check of the operation information fails, it is determined that the operation state of the disaster recovery deployment unit is abnormal.

In some embodiments of the present application, before the receiving an access request and acquiring the initial access address associated with the access request, the method includes:

Receive an application deployment request, define an environment variable of the application according to the deployment request, and create an image based on the environment variable;

A dependency is made based on the image, and a deployment unit of the application is deployed according to the dependency.

On the other hand, the present application provides an access switching device for application software, and the access switching device for application software includes:

one or more processors;

memory; and

One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement an access switching method of application software.

On the other hand, the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program is loaded by a processor to execute the access switching method of the application software. A step of.

In the technical solution of the present application, an access request is received, and an initial access address associated with the access request is obtained; if the target deployment unit corresponding to the initial access address is abnormal, it is determined whether the target deployment unit has deployed the corresponding disaster recovery deployment unit, and if the target deployment unit has Deploy the corresponding disaster recovery deployment unit, by querying the running status of the disaster recovery deployment unit, if the running status of the disaster recovery deployment unit is normal, then switch the access request to the target network address corresponding to the disaster recovery deployment unit, so as to realize the application software. The access request is quickly switched from the target deployment unit to the disaster recovery deployment unit, which simplifies the switching operation, reduces the abnormal time, and ensures that the normal access of the application can be restored after the switching operation, so that the access request can be responded quickly.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained from these drawings without creative effort.

1 is a schematic diagram of a scenario of access switching of application software provided by an embodiment of the present invention;

2 is a schematic flowchart of an embodiment of an access switching method for application software provided by an embodiment of the present invention;

3 is a schematic flowchart of an embodiment of the establishment of a disaster tolerance cluster in the switching access method for application software provided by an embodiment of the present invention;

4 is a schematic flowchart of an embodiment of deploying a disaster tolerance deployment unit in access switching of application software provided by an embodiment of the present invention;

5 is a schematic flowchart of an embodiment of determining whether a corresponding disaster tolerance deployment unit has been deployed in an access switching method for application software provided by an embodiment of the present invention;

6 is a schematic flowchart of an embodiment of querying the running state of the disaster tolerance deployment unit in the access switching method for application software provided by the embodiment of the present invention;

7 is a schematic flowchart of an embodiment of deployment unit deployment in an access switching method for application software provided by an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of an embodiment of an access switching device for application software provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of the present invention.

In the description of this application, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", " The orientation or positional relationship indicated by "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc. is based on the orientation shown in the drawings Or the positional relationship is only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the indicated device or element must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on the present application. In addition, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as indicating or implying relative importance or implying the number of indicated technical features. Thus, features defined as "first", "second" may expressly or implicitly include one or more features. In the description of the present application, "plurality" means two or more, unless otherwise expressly and specifically defined.

In this application, the word "exemplary" is used to mean "serving as an example, illustration, or illustration." Any embodiment described in this application as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The following description is presented to enable any person skilled in the art to make and use the present application. In the following description, details are set forth for the purpose of explanation. It is to be understood that one of ordinary skill in the art can realize that the present application may be practiced without the use of these specific details. In other instances, well-known structures and procedures have not been described in detail so as not to obscure the description of the present application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown but is to be accorded the widest scope consistent with the principles and features disclosed herein.

Embodiments of the present invention provide an access switching method, device, and computer-readable storage medium for application software.

The application software access switching method in the embodiment of the present application is applied to an application software access switching device. The application software access switching device is provided with a memory and a processor, the memory stores an application program, and the processor is used for running the application stored in the memory. A program is used to implement the access switching of the application software; the access switching device of the application software can be a server, such as a single server or a server cluster composed of multiple servers.

As shown in FIG. 1 , FIG. 1 is a schematic diagram of a scenario of access switching of application software provided by an embodiment of the present application. In the embodiment of the present application, the access switching scenario of application software includes an access switching device of application software, and the access switching device of application software runs The computer-readable storage medium corresponding to the access switching of the application software is used to perform the steps of the access switching of the application software.

It can be understood that the access switching device of the application software in the access switching of the application software shown in FIG. 1, or the device included in the access switching device of the application software does not constitute a restriction to the embodiment of the present application, that is, the access switching of the application software. The number of devices and types of devices included in the scene, or the number and types of devices included in each device do not affect the overall implementation of the technical solutions of the embodiments of the present application, and can be regarded as equivalent replacements of the technical solutions claimed in the embodiments of the present application or derivative.

The access switching device of the application software in the embodiment of the present application is mainly used for:

Receive an access request, and obtain the initial access address associated with the access request;

If the target deployment unit corresponding to the initial access address is abnormal, determine whether the target deployment unit has deployed the corresponding disaster recovery deployment unit;

If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the running status of the disaster recovery deployment unit;

If the running state of the disaster recovery deployment unit is normal, the access request is switched to the target network address corresponding to the disaster recovery deployment unit.

In the embodiment of the present application, the access switching device of the application software may be an independent application software access switching device, or may be an application software access switching device network composed of application software access switching devices, or an application software access switching device cluster, For example, the access switching device for application software described in the embodiments of this application includes, but is not limited to, a computer, a server, a server cluster composed of multiple servers, an access switching device for a single network application software, a set of access switching devices for multiple application software, or multiple Access switching devices for cloud application software composed of access switching devices for each application software. The access switching device for cloud application software is composed of a large number of cloud computing-based computers, servers or access switching devices for network application software.

Those skilled in the art can understand that the application scenario shown in FIG. 1 is only one application scenario of the solution of the present application, and does not constitute a limitation on the application scenario of the solution of the present application. Other application scenarios may also include more than that shown in FIG. 1 . There are more or less application software access switching devices, or the network connection relationship of application software access switching devices. For example, only one application software access switching device is shown in FIG. 1. It can be understood that the application software access switching device The scenario may also include one or more access switching devices for application software, which is not specifically limited here; the application software access switching device may also include a memory for storing data, such as running information of the target deployment unit.

In addition, the access switching device of the application software of the present application may be provided with the display device 200, or the access switching device 100 of the application software does not set the display device 200 to communicate with an external display device, and the display device 200 is used for The result of the execution of the access switching method of the application software in the access switching device 100 of the application software is output. The access switching device 100 of the application software can access the background database 300 (the background database 300 can be the local memory of the application software access switching device 100), and the background database 300 stores the information related to the access switching of the application software, for example, in the background database. Save the running information of the target deployment unit, the running status of the disaster recovery deployment unit, and the dependencies of the target deployment unit.

It should be noted that the schematic diagram of the access switching scenario of the application software shown in FIG. 1 is only an example, and the scenario of the access switching of the application software described in the embodiments of the present application is for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly. , which does not constitute a limitation on the technical solutions provided in the embodiments of the present application.

As shown in FIG. 2, FIG. 2 is a schematic flowchart of an embodiment of an access switching method for application software provided by an embodiment of the present application. The access switching method for application software includes:

101. Receive an access request, and obtain an initial access address associated with the access request.

The access switching method for application software in the embodiment of the present application is applied to an access switching device for application software, and the type and number of devices in the access switching device for application software are not limited. The access switching device of the application software in this embodiment is described by taking the production availability zone as an example (wherein, the production availability zone is a collection of one or more physical data centers with redundant power supplies, networking and connections, including application software accessed by users daily ). The production availability zone receives the client's access request through the port, obtains the domain name requested in the access request, uses the load balancer to resolve the domain name to obtain the initial access address associated with the access request, and queries the target deployment unit corresponding to the initial access address through the initial access address (wherein The target deployment unit is the smallest application unit of the production application in the production availability zone), and establishes a communication connection between the target deployment unit and the client based on the initial access address. If the communication connection fails to be established, it means that the target deployment unit access times out, and the initial access address is determined. The corresponding target deployment unit is abnormal.

In this embodiment, a production availability zone can be established based on the Kubernetes (Chinese: open source container orchestration engine) container management platform, and the NodePort service (Chinese: node port), LoadBalancer (Chinese: load balancer) or Kubernetes can be deployed by setting Ingress (Chinese: access to the cluster from outside the kubernetes cluster) container so that the client can access the application software through the port or Ingress mode, you can use DNS (full name: DomainName Server, Chinese: Domain Name System) to resolve the domain name to obtain the associated access request Initial access address. Based on the Kubernetes container management platform, containers are combined into deployment units that are mutually dependent. Related containers are combined into deployment units and then deployed and scheduled together to form services, simplifying the complexity of deployment and scheduling deployment units.

102. If the target deployment unit corresponding to the initial access address is abnormal, determine whether the target deployment unit has deployed the corresponding disaster recovery deployment unit.

In the embodiment of the present application, if the target deployment unit corresponding to the initial access address is abnormal, the disaster recovery availability zone corresponding to the production availability zone is queried to determine whether the target deployment unit has deployed the corresponding disaster recovery deployment unit (where the disaster recovery deployment unit is Disaster Recovery Availability Zone is the smallest application unit of disaster recovery application. Disaster recovery availability zone is the spare area of production availability zone established based on Kubernetes container management platform). If the target deployment unit does not deploy the corresponding disaster recovery deployment unit, the output cannot be applied. The prompt message of the access switching of the software; if the target deployment unit has deployed the corresponding disaster recovery deployment unit, execute the operation of querying the running status of the disaster recovery deployment unit if the target deployment unit has deployed the corresponding disaster recovery deployment unit.

103. If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the running status of the disaster recovery deployment unit.

In the embodiment of the present application, if the target deployment unit has already deployed the corresponding disaster recovery deployment unit, the production availability zone queries the operation information of the disaster recovery deployment unit corresponding to the target deployment unit in the disaster recovery availability zone (the operation information includes the configuration of the disaster recovery deployment unit) information and running status, etc.), obtain the running status of the disaster recovery deployment unit through the running information, and analyze the running status to determine whether the running status is normal; if the running status of the disaster recovery deployment unit is abnormal, it means that the disaster recovery deployment unit cannot be switched and the production The availability zone outputs a message indicating that the access switching of the application software fails; if the running state of the disaster recovery deployment unit is normal, it means that the switching of the disaster recovery deployment unit can be performed, and the production availability zone executes the switch of the access request to the disaster recovery deployment. The target network address operation corresponding to the unit.

104. If the running state of the disaster recovery deployment unit is normal, switch the access request to a target network address corresponding to the disaster recovery deployment unit.

In the embodiment of the present application, if the running state of the disaster recovery deployment unit is normal, the production availability zone will stop the operation of the target deployment unit, switch the access request to the target network address corresponding to the disaster recovery deployment unit, and transfer the application software in the production availability zone to the target network address. Data is migrated to the disaster recovery availability zone, and the corresponding disaster recovery application in the disaster recovery availability zone provides application services to realize the access switching of application software.

In this embodiment, stopping the operation of the target deployment unit in the production availability zone includes: querying the operation information of the target deployment unit, analyzing whether the target deployment unit is in the activated state according to the operational information, and querying the target deployment unit if the target deployment unit is in the inactive state The status of the unit (where the status of the target deployment unit includes suspended, successfully terminated, failed to terminate, and unknown, etc.), if the target deployment unit is successfully terminated, it means that the target deployment unit is in a normal stop state, and outputs a message indicating that the stop is successful; if If the target deployment unit fails to terminate, it means that the stop state of the target deployment unit is abnormal, and outputs a prompt message that the operation of the target deployment unit fails to stop, and indicates that the access switching of the application software fails; if the target deployment unit is in the started state, the target deployment unit The deployment unit is marked as "terminating", and the access request is switched to the target network address corresponding to the disaster recovery deployment unit, the running process of the target deployment unit is stopped, and the status of the target deployment unit is checked by querying the status of the target deployment unit. Whether the stop state is normal.

In this embodiment, after the production availability zone stops the running of the target deployment unit, the abnormal cause of the production application in the production availability zone is checked, and the fault repair of the production availability zone is performed. Query the DR availability zone to obtain the DR deployment unit of the production application corresponding to the DR application, and query whether the status of the corresponding target deployment unit in the production availability zone is terminated according to the DR deployment unit. If the status of the target deployment unit is terminated by failure , the production availability zone will restart the target deployment unit; if the status of the target deployment unit is not terminated, the production availability zone will create the target deployment unit according to the disaster recovery deployment unit, and start the target deployment unit; after the target deployment unit is restarted/started, query The running status of the target deployment unit. If the running status is normal, the production availability zone will send the access switching request of the application software to the disaster recovery zone, receive the access request from the client, and switch the access request to the corresponding network address of the target deployment unit. Access switching of application software.

In this embodiment, after stopping the operation of the target deployment unit, the production availability zone queries the disaster recovery availability zone to obtain the operation information of the corresponding disaster recovery deployment unit, and updates the operation information of the target deployment unit according to the operation information of the disaster recovery deployment unit. Restart/start the target deployment unit using the updated running information of the target deployment unit.

In the embodiment of the present application, by querying the running status of the disaster recovery deployment unit, if the running status of the disaster recovery deployment unit is normal, the access request is switched to the target network address corresponding to the disaster recovery deployment unit, so as to realize the access switching of the application software, from The target deployment unit is quickly switched to the disaster recovery deployment unit, which simplifies the switching operation, reduces abnormal time, and ensures that the switching operation can restore the normal access of the application; and after receiving the access switching request, it determines whether the target deployment unit has deployed the corresponding disaster recovery deployment unit , the access switching service of the application software is only provided to the target deployment unit of the corresponding disaster recovery deployment unit that has been deployed, so as to provide guarantee for the access switching of the application software.

As shown in FIG. 3 , FIG. 3 is a schematic flowchart of an embodiment of establishing a disaster tolerance cluster in the switching access method for application software provided by the embodiment of the present application.

In some embodiments of the present application, a method for establishing a disaster recovery cluster in a switching access method for application software is described in detail, including:

201. Receive a disaster recovery deployment request, and determine application software corresponding to the disaster recovery deployment request and a set of deployment units associated with the application software.

In the embodiment of the present application, before the production availability zone receives a client access request, the production availability zone needs to deploy a disaster recovery deployment unit that provides running services for application software in the corresponding disaster recovery availability zone to establish a disaster recovery cluster. Specifically, the production availability zone receives the disaster recovery deployment request of the disaster recovery availability zone, obtains the application software identifier included in the disaster recovery deployment request according to the disaster recovery deployment request, and obtains the detailed information of the application software (the detailed information of the application software) according to the application software identification query. The information includes service information required for running the application software), and according to the detailed information of the application software, a plurality of deployment units that provide services for the operation of the application software are acquired, and a deployment unit set is formed according to the plurality of deployment units.

202: Acquire an identifier of a deployment unit to be deployed in the set of deployment units, and operation information of a deployment unit corresponding to each of the deployment unit identifiers.

In the embodiment of the present application, the production availability zone obtains the deployment unit identifier to be deployed from the deployment unit set (wherein the deployment unit identifier includes the name and IP address of the deployment unit (full name: Internet Protocol, Chinese: Internet Interconnection Protocol)), according to The deployment unit identifier to be deployed obtains the operation information of the deployment unit, traverses the entire deployment unit set, and obtains the operation information of the deployment unit corresponding to each deployment unit identifier in the deployment unit collection one by one (the operation information includes configuration information, health information, image information, etc.) .

203. Deploy a disaster recovery deployment unit of each deployment unit according to the operation information of each deployment unit, and use a device corresponding to each disaster recovery deployment unit as a disaster recovery cluster corresponding to the application software.

After acquiring the operation information of the deployment units corresponding to the deployment unit identifiers in the deployment unit set one by one, according to the operation information of each deployment unit, deploy the disaster recovery deployment units corresponding to each deployment unit in the disaster recovery availability zone one by one. After the deployment of the disaster recovery deployment unit corresponding to the deployment unit is completed, the production availability zone determines the association relationship between each to-be-deployed unit in the deployment unit set according to the detailed information of the application software, and establishes a disaster recovery by synchronizing each disaster recovery deployment unit based on the association relationship. A set of deployment units is used, and the devices corresponding to the set of disaster recovery deployment units in the disaster recovery availability zone are used as a disaster recovery cluster, and the operation of the application software is provided through the disaster recovery cluster.

In the embodiment of the present application, before receiving the disaster tolerance deployment request, the production availability zone obtains the set of deployment units by using the detailed information of the application software, and obtains the set of disaster tolerance units supporting the operation of the application software by deploying the set of disaster tolerance deployment units corresponding to the set of disaster tolerance units The cluster provides data protection for the access switching of application software.

As shown in FIG. 4 , FIG. 4 is a schematic flowchart of an embodiment of deploying a disaster tolerance deployment unit in access switching of application software provided by an embodiment of the present application.

In some embodiments of the present application, a method for deploying a disaster tolerance deployment unit in access switching of application software is described in detail, including:

301. Acquire configuration information associated with each deployment unit according to the operation information of each deployment unit.

302. Extract dependencies and environment variables corresponding to each deployment unit from the configuration information associated with each deployment unit, and determine whether the dependencies corresponding to each deployment unit include disaster tolerance dependencies.

In this embodiment of the present application, the production availability zone acquires configuration information associated with the deployment unit identifier according to the operation information of each deployment unit (wherein the configuration information may be configuration data used when the deployment unit is created, including configuration files and environment variables, etc.) , extract the configuration file associated with the deployment unit identifier from the configuration information, and determine the dependencies of the deployment unit according to the configuration file (where the configuration file is the data file generated by creating the dependencies of the deployment unit, and the dependencies provide support for the startup and operation of the deployment unit , including configuration items, storage volumes and service items, etc.), after obtaining the dependencies of the deployment unit, determine whether the dependencies corresponding to the deployment unit include disaster tolerance dependencies by judging whether there is a configuration file in the disaster tolerance availability zone; if disaster tolerance is available If there is a configuration file in the zone, it means that the dependency corresponding to the configuration file has a DR dependency, and the corresponding DR dependency has been established in the DR availability zone, that is, the dependency corresponding to the deployment unit includes the DR dependency; if the DR is available If there is no configuration file in the zone, it means that the dependency corresponding to the configuration file does not have a DR dependency, and there is no corresponding DR dependency established in the DR availability zone, that is, the dependency corresponding to the deployment unit does not contain the DR dependency.

303. If the dependencies corresponding to each deployment unit include disaster tolerance dependencies, create a disaster tolerance deployment unit of each deployment unit according to the disaster tolerance dependencies corresponding to each deployment unit, and store the The equipment corresponding to each of the disaster recovery deployment units is used as a disaster recovery cluster corresponding to the application software.

If the dependencies corresponding to the deployment unit include disaster tolerance dependencies, create a disaster tolerance deployment unit through the Kubernetes container management platform according to the disaster tolerance dependencies and combined with the operation information of the deployment unit. In the completed deployment unit set, each deployment unit corresponds to the disaster tolerance After the deployment unit is created, the equipment of each disaster recovery deployment unit is used as a disaster recovery cluster that supports application software running services.

304. If the dependencies corresponding to the deployment units do not include disaster tolerance dependencies, configure the disaster tolerance dependencies corresponding to the dependencies through the environment variables corresponding to the deployment units, and configure the disaster tolerance dependencies according to the environment variables corresponding to the deployment units. The disaster recovery dependency creates a disaster recovery deployment unit of each of the deployment units, and uses the device corresponding to each of the disaster recovery deployment units as a disaster recovery cluster corresponding to the application software.

If the dependencies corresponding to the deployment unit do not contain disaster tolerance dependencies, based on the environment variables (where the environment variables include basic information such as the name of the deployment unit, namespace, IP address, and computing resource limits of the container, and the service created before the deployment unit runs) Information) configure the disaster recovery dependencies corresponding to the dependencies, and create a disaster recovery deployment unit according to the disaster recovery dependencies, so as to obtain a disaster recovery cluster, specifically, including:

According to the configuration file, the dependencies are divided into pre-dependencies and post-dependencies. The pre-dependencies include configuration items (ConfigMap, Chinese: application configuration management) and storage volumes (Volume, Chinese: hanging volumes) (where the configuration items It is used to deploy the configuration information required for the operation of the application software, and the storage volume is used to store the data generated during the creation and operation of the deployment unit. The post-dependency includes the service item (service, Chinese: service, where the service item is mainly used for the deployment unit The external access interface of the collection);

If the data file of the ConfigMap pre-dependencies corresponding to the deployment unit does not exist in the DR availability zone, that is, the dependencies corresponding to the deployment unit do not contain the DR ConfigMap pre-dependencies, configure the configuration files required to create the ConfigMap dependencies through environment variables , create a ConfigMap in the DR availability zone according to the configuration file, and record the data files generated by deploying ConfigMap dependencies in the DR availability zone through the DR environment variable; Data file; if the data file of the volume pre-dependency corresponding to the deployment unit does not exist in the disaster-tolerant availability zone, that is, the dependency corresponding to the deployment unit does not contain the disaster-tolerant Volume pre-dependency, the Volume pre-dependency is created through the environment variable configuration The configuration file required by the item, create a Volume in the DR availability zone according to the configuration file, and store the DR environment variables in the Volume after the Volume pre-dependencies are created;

If the data file of the pre-dependencies corresponding to the deployment unit exists in the DR availability zone, the DR deployment unit is created through the Kubernetes container management platform. After the DR deployment unit corresponding to each deployment unit in the deployment unit set is created, the Variables and service post-dependencies, create disaster-tolerant service post-dependencies, and determine whether the disaster-tolerant service post-dependencies can access the disaster-tolerant deployment unit, and determine whether the disaster-tolerant service post-dependencies are successfully constructed; If the post-disaster dependency can access the DR deployment unit, it means that the post-disaster dependency is created successfully; if the post-disaster dependency cannot access the DR deployment unit, it means that the post-disaster dependency creation fails. In this embodiment, if the creation of the post-disaster tolerance dependency fails, the created disaster tolerance deployment unit is deleted.

In this embodiment, the configuration file can be written through YAML (Chinese: format for expressing data serialization) or directly using kubectl create configmap (Chinese: create application configuration management, kubectl, Chinese: command line interface, for running the Kubernetes cluster Command) command line method to create a ConfigMap; you can create a disaster recovery Volume pre-dependency in the way of shared storage, synchronize the data in the Volume pre-dependency to the disaster-tolerant Volume pre-dependency, and ensure that the disaster recovery Volume Pre-dependencies are named the same as Volume pre-dependencies; they can be created via the expose command (a fundamental command in Kubernetes, used to expose a resource as a new Kubernetes service) or by creating a service from a YAML file.

In this embodiment, before performing the operation of obtaining the configuration information associated with each deployment unit according to the operation information of each deployment unit, the production availability zone can query whether the corresponding disaster recovery availability zone has the same name according to the deployment unit identifier of each deployment unit If there is a disaster recovery deployment unit with the same name, it will output a prompt message for retry, prompting to delete the previously deployed disaster recovery deployment unit with the same name, and then redeploy the disaster recovery deployment unit; if not If a disaster recovery deployment unit with the same name exists, the operation of obtaining the configuration information associated with each deployment unit according to the operation information of each deployment unit is performed to complete the creation of the disaster recovery deployment unit. In this embodiment, before creating a corresponding disaster recovery deployment unit according to the operation information of each deployment unit, the production availability zone needs to query whether there is a disaster recovery deployment unit with the same name in the corresponding disaster recovery availability zone, so as to ensure that the created disaster recovery deployment unit is It is created according to the operation information of the deployment unit, and ensures the consistency between the disaster recovery deployment unit and the deployment unit.

In this embodiment of the present application, after the disaster recovery deployment units of each deployment unit are deployed according to the operation information of each deployment unit, and the equipment corresponding to each disaster recovery deployment unit is used as the disaster recovery cluster corresponding to the application software, the production availability zone detects the set of deployment units in the production availability zone. The operation information of each deployment unit determines the target deployment unit whose operation information is updated, and updates the operation information of the disaster recovery deployment unit corresponding to the target deployment unit according to the operation information of the target deployment unit.

In the embodiment of the present application, the production availability zone obtains configuration information associated with the identifier of the deployment unit according to the operation information of each deployment unit, and creates a disaster recovery deployment unit according to the configuration information, so as to ensure the consistency of the deployment unit and the corresponding disaster recovery deployment unit, and After the establishment of the disaster recovery cluster is completed, the operation information of the corresponding disaster recovery deployment unit is updated according to the operation information of the target disaster recovery deployment unit, so as to further ensure the consistency of the deployment unit and the corresponding disaster recovery deployment unit.

As shown in FIG. 5 , FIG. 5 is a schematic flowchart of an embodiment of determining whether a corresponding disaster tolerance deployment unit has been deployed in the access switching method for application software provided by an embodiment of the present application.

In some embodiments of the present application, the method for determining whether the corresponding disaster recovery deployment unit has been deployed in the access switching method of the application software is specifically described, which specifically includes:

401. If the target deployment unit corresponding to the initial access address is abnormal, determine whether the target deployment unit has a corresponding disaster recovery deployment unit.

In the embodiment of the present application, if the target deployment unit corresponding to the initial access address is abnormal, the production availability zone will query whether there is a disaster recovery deployment unit with the same deployment unit ID in the disaster recovery availability zone according to the deployment unit ID of the target deployment unit, Determine whether the target deployment unit has a corresponding disaster recovery deployment unit; if there is a disaster recovery deployment unit with the same deployment unit ID in the disaster recovery availability zone, explain that the target deployment unit has a corresponding disaster recovery deployment unit; if there is no disaster recovery deployment unit in the disaster recovery availability zone If there are DR deployment units with the same deployment unit ID, it means that there is no corresponding DR deployment unit in the target deployment unit.

402. If the target deployment unit has a corresponding disaster recovery deployment unit, compare the dependency of the target deployment unit with the disaster recovery dependency of the disaster recovery deployment unit.

If the target deployment unit has a corresponding disaster recovery deployment unit, the production availability zone will obtain the configuration information of the target deployment unit according to the deployment unit identifier, and obtain the dependencies associated with the target deployment unit according to the configuration information; obtain the disaster recovery deployment unit in the same way. Disaster tolerance dependencies, match the dependencies of the target deployment unit with the disaster tolerance dependencies of the disaster tolerance deployment unit; if the configuration file of the dependencies of the target deployment unit and the configuration file of the disaster tolerance dependencies of the If the data information is not the same, it means that the dependency of the target deployment unit is inconsistent with the configuration of the disaster recovery dependency of the disaster recovery deployment unit, and the dependency of the target deployment unit does not match the disaster recovery dependency of the disaster recovery deployment unit; if the target deployment If the data information in the configuration file of the dependency of the unit is the same as the configuration file of the configuration file of the DR dependency of the DR deployment unit, it means that the dependency of the target deployment unit is configured in the same way as the DR dependency configuration of the DR deployment unit. The dependencies of the DR match the DR dependencies of the DR deployment unit.

403. If the dependency of the target deployment unit matches the disaster recovery dependency of the disaster recovery deployment unit, determine that the target deployment unit has deployed the corresponding disaster recovery deployment unit.

If the dependency of the target deployment unit matches the disaster tolerance dependency of the disaster recovery deployment unit, the production availability zone determines that the target deployment unit has deployed the corresponding disaster recovery deployment unit, and performs an operation of querying the running status of the disaster recovery deployment unit.

404. If the target deployment unit does not have a corresponding disaster recovery deployment unit, or the dependency of the target deployment unit does not match the disaster recovery dependency of the disaster recovery deployment unit, determine that the target deployment unit is not deployed The corresponding disaster recovery deployment unit.

In this embodiment of the present application, if the target deployment unit does not have a corresponding disaster recovery deployment unit, or the dependencies of the target deployment unit do not match the disaster recovery dependencies of the disaster recovery deployment unit, the production availability zone will determine that the target deployment unit is not deployed The corresponding disaster recovery deployment unit, and output the prompt information that the access switching of the application software cannot be performed.

In the embodiment of the present application, the production availability zone uses the uniqueness of the deployment unit identifier to determine whether the target deployment unit has a corresponding disaster recovery deployment unit, and to determine whether the dependency configurations of the target deployment unit and the corresponding disaster recovery deployment unit are consistent. The round judgment determines whether the target deployment unit has deployed the corresponding disaster recovery deployment unit, so as to provide data guarantee for the access switching of the application software.

As shown in FIG. 6 , FIG. 6 is a schematic flowchart of an embodiment of querying the running state of the disaster tolerance deployment unit in the access switching method of the application software provided by the embodiment of the present application.

In some embodiments of the present application, the method for querying the running state of the disaster tolerance deployment unit in the access switching method of the application software is described in detail, which specifically includes:

501. If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the status of the disaster recovery deployment unit corresponding to the target deployment unit.

In the embodiment of the present application, if the target deployment unit has already deployed the corresponding disaster recovery deployment unit, the production availability zone will query the status of the disaster recovery deployment unit in the corresponding disaster recovery availability zone, and determine the corresponding disaster recovery deployment unit according to the status of the disaster recovery deployment unit Whether it has been started; if the status of the disaster recovery deployment unit is suspended, it indicates that the disaster recovery deployment unit has not been started, and the status of the disaster recovery deployment unit is determined to be not started; if the status of the disaster recovery deployment unit is running, it indicates that the The disaster recovery deployment unit has been started, and the status of the disaster recovery deployment unit is determined to be started.

502. If the status of the disaster recovery deployment unit is activated, query the running status of the disaster recovery deployment unit according to the operation information of the disaster recovery deployment unit.

If the status of the disaster recovery deployment unit is Started, the production availability zone will obtain the operation information of the corresponding disaster recovery deployment unit, perform a health check on the operation information, and check the running status of the disaster recovery deployment unit according to the result of the health check to determine the disaster recovery deployment. Whether the running state of the unit is normal; if the result of the health check shows that the DR deployment unit passes the health check, it means that the running state of the DR deployment unit is normal; if the result of the health check shows that the DR deployment unit fails the health check or the health check If the result is unknown, it means that the running state of the disaster recovery deployment unit is abnormal.

503. If the status of the disaster recovery deployment unit is not started, start the disaster recovery deployment unit, and update the operation information of the disaster recovery deployment unit.

If the status of the DR deployment unit is not started, the production AZ will send a request to start the DR deployment unit to the corresponding DR AZ, so that the DR AZ starts the DR deployment unit, completes the DR deployment unit scheduling, and The operation information of the disaster recovery deployment unit is updated, and the operation of querying the operation status of the disaster recovery deployment unit is performed according to the operation information of the disaster recovery deployment unit.

In the embodiment of the present application, the status of the disaster recovery deployment unit can be determined by querying whether the corresponding disaster recovery deployment unit of the target deployment unit has completed the scheduling, and specifically by checking the phase of the corresponding disaster recovery deployment unit (where the phase is related to the life cycle of the deployment unit) A simple macro overview, the values of the phase include Pending (Chinese: Suspended), Running (Chinese: Running), Success (Succeeded, Chinese: Successfully terminated), Failed (Failed, Chinese: Failed to terminate) and Unknown (Unknown, Chinese: Unknown), according to the value of the phase to determine whether the corresponding disaster recovery deployment unit has completed the scheduling; if the value of the phase is suspended, it means that the corresponding disaster recovery deployment unit has not completed the scheduling, and determine whether the disaster recovery deployment unit has completed the scheduling. The status is not started; if the phase value is running, it means that the disaster recovery deployment unit should complete the scheduling, and the status of the disaster recovery deployment unit is determined to be started.

In this embodiment of the present application, a container probe may be used to perform a health check on the running information to obtain a health status, and according to the health status, it may be determined whether the running status of the disaster recovery deployment unit is normal. Specifically, the IP address and port of the disaster recovery deployment unit may be used. TCP (full name: Transfer Control Protocol, Chinese: Transmission Control Protocol) check; if a TCP connection can be established with the disaster recovery deployment unit through the port, a prompt message indicating that the disaster recovery deployment unit has passed the health check will be output, indicating that the disaster recovery deployment unit has passed the health check; If the TCP connection cannot be established, a message indicating that the health check fails is output, indicating that the health check of the disaster recovery deployment unit fails; if the disaster recovery deployment unit cannot be found through the IP address and port number of the disaster recovery deployment unit, the health check is output. The message of failure indicates that the result of the health check of the disaster recovery deployment unit is unknown. In this embodiment of the present application, a liveness probe (Chinese: survivability probe) and a readness probe (Chinese: readiness probe) container probes may be used to perform health checks on the running information.

In the embodiment of the present application, if the target deployment unit has already deployed the corresponding disaster recovery deployment unit, the operation information of the disaster recovery deployment unit is used to query the running status of the disaster recovery deployment unit, so as to ensure that the access of the application software is switched to the corresponding disaster recovery availability zone After that, the application software can be accessed normally.

As shown in FIG. 7 , FIG. 7 is a schematic flowchart of an embodiment of deployment unit deployment in an access switching method for application software provided by an embodiment of the present application.

In some embodiments of the present application, the method for deploying the deployment unit in the access switching method of the application software is described in detail, which specifically includes:

601. Receive an application deployment request, define an environment variable of the application according to the deployment request, and create an image based on the environment variable.

In the embodiment of the present application, the production availability zone receives the application deployment request, and determines the basic image, the installation package, configuration file and related script files required for preparing the deployment application according to the deployment request. Configuration item quantification; define the environment variables of the application, and quantify one or more configuration items that need to be modified in the configuration file and related script files; make images based on environment variables, installation packages, configuration files and related script files.

602. Create a dependency based on the image, and deploy a deployment unit of the application according to the dependency.

According to the environment variables in the image and the configuration file, the development warehouse is associated, and the template file that supports the application running service is created according to the application (the template file includes the pre-dependency template file and the post-dependency template file,) in the Kubernetes container management platform In the above, modify the corresponding configuration items in the template file based on the environment variables to make dependencies, determine the data files required for the deployment unit of the application deployment through the dependencies, and configure the data files through the environment variables to complete the deployment unit of the application. deployment.

In the embodiment of the present application, by creating images and configuration files, deployment unit deployment can be completed according to the application program, and dependencies can be created by modifying corresponding configuration items in the template file according to the application program through environment variables, thereby providing efficient and convenient deployment unit deployment.

An embodiment of the present application further provides an access switching device for application software. As shown in FIG. 8 , FIG. 8 is a schematic structural diagram of an embodiment of the access switching device for application software provided by an embodiment of the present application.

The access switching device of the application software runs the computer-readable storage medium corresponding to the access switching of the application software to perform the steps of the access switching of the application software, the access switching device of the application software includes: one or more processors; a memory; and One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor as an application in any one of the embodiments of the access switching method for the above application software Steps in the software's access switching method.

Specifically, the access switching device for application software includes one or more core processors 801 , one or more computer-readable storage media memory 802 , power supply 803 , and input unit 804 and other components. Those skilled in the art can understand that the structure of the access switching device of the application software shown in FIG. 8 does not constitute a limitation on the access switching device of the application software, and may include more or less components than those shown in the figure, or combine some components , or a different component arrangement. in:

The processor 801 is the control center of the access switching device of the application software, uses various interfaces and lines to connect various parts of the access switching device of the application software, and calls the storage by running or executing the software programs and/or modules in the memory 802. The data in the memory 802 executes various functions of the access switching device of the application software and processes data, so as to perform overall monitoring of the access switching device of the application software. Optionally, the processor 801 may include one or more processing cores; preferably, the processor 802 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc. , the modem processor mainly deals with wireless communication. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 801.

The memory 802 can be used to store software programs and modules, and the processor 801 executes various functional applications and data processing by running the software programs and modules stored in the memory 802 . The memory 802 may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required for at least one function (such as an access request receiving function, a running state query function of a disaster recovery deployment unit, an access request Switching function, etc.), etc.; the storage data area may store data etc. created according to the use of the switching device accessed by the application software. Additionally, memory 802 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 802 may also include a memory controller to provide processor 801 access to memory 802 .

The access switching device of the application software also includes a power supply 803 for supplying power to each component. Preferably, the power supply 803 can be logically connected to the processor 801 through a power management system, so as to manage charging, discharging, and power consumption management functions through the power management system. . Power source 802 may also include one or more DC or AC power sources, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, and any other components.

The access switching device of the subscription application software may also include an input unit 804, which can be used to receive input numerical or character information, and generate keyboard, mouse, joystick, optical or trackball related to user settings and function control signal input.

Although not shown, the access switching device of the application software may also include a display unit and the like, which will not be described herein again. Specifically in this embodiment, the processor 801 in the access switching device of the application software loads the executable files corresponding to the processes of one or more application programs into the memory 802 according to the following instructions, and the processor 801 to run the application program stored in the memory 1002, thereby realizing various functions, as follows: receiving an access request, obtaining the initial access address associated with the access request; if the target deployment unit corresponding to the initial access address is abnormal, then determine the whether the target deployment unit has deployed the corresponding disaster recovery deployment unit; if the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the running status of the disaster recovery deployment unit; if the operation of the disaster recovery deployment unit If the status is normal, the access request is switched to the target network address corresponding to the disaster recovery deployment unit.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods in the above embodiments can be completed by instructions, or by instructions that control relevant hardware, and the instructions can be stored in a computer-readable storage medium, and Loaded or executed by the processor.

To this end, an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium may include: read-only memory (ROM, full name: Read Only Memory, Chinese: read-only memory), random access memory ( RAM, full name: Random Access Memory, Chinese: random access memory), magnetic disk or CD, etc. A computer program is stored thereon, and the computer program is loaded by the processor to execute the steps in any of the application software access switching methods provided by the embodiments of the present invention. For example, when the computer program is loaded by the processor, the following steps may be performed: receiving an access request, and obtaining an initial access address associated with the access request; if the target deployment unit corresponding to the initial access address is abnormal, judging the target deployment Whether the unit has deployed the corresponding disaster recovery deployment unit; if the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the running status of the disaster recovery deployment unit; if the running status of the disaster recovery deployment unit is normal, Then, the access request is switched to the target network address corresponding to the disaster recovery deployment unit. In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to the above detailed description of other embodiments, and details are not repeated here.

During specific implementation, the above units or structures can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of the above units or structures, reference may be made to the foregoing method embodiments. No longer.

The method, device, and computer-readable storage medium for accessing and switching application software provided by the embodiments of the present invention have been described above in detail. In this paper, specific examples are used to illustrate the principles and implementations of the present invention. The above embodiments The description is only used to help understand the method of the present invention and its core idea; at the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific implementation and application scope. , the contents of this specification should not be construed as limiting the invention.

Claims (10)

1. an access switching method for application software, characterized in that the method comprises: Receive an access request, and obtain the initial access address associated with the access request; If the target deployment unit corresponding to the initial access address is abnormal, determine whether the target deployment unit has deployed the corresponding disaster recovery deployment unit; If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the running status of the disaster recovery deployment unit; If the running state of the disaster recovery deployment unit is normal, the access request is switched to the target network address corresponding to the disaster recovery deployment unit. 2. The access switching method of application software according to claim 1, wherein, before the receiving an access request and acquiring the initial access address associated with the access request, the method comprises: receiving a disaster recovery deployment request, and determining application software corresponding to the disaster recovery deployment request, and a set of deployment units associated with the application software; Obtaining the deployment unit identifiers to be deployed in the deployment unit set, and the operation information of the deployment units corresponding to the deployment unit identifiers; According to the operation information of each deployment unit, the disaster recovery deployment unit of each deployment unit is deployed, and the device corresponding to each disaster recovery deployment unit is used as the disaster recovery cluster corresponding to the application software. 3. The method for accessing and switching application software according to claim 2, wherein the disaster recovery deployment unit of each deployment unit is deployed according to the operation information of each deployment unit, and the disaster recovery deployment unit of each deployment unit is The equipment corresponding to the deployment unit is used as the disaster recovery cluster corresponding to the application software, including: Obtain configuration information associated with each deployment unit according to the operation information of each deployment unit; Extracting dependencies and environment variables corresponding to each deployment unit from the configuration information associated with each deployment unit, and determining whether the dependencies corresponding to each deployment unit include disaster tolerance dependencies; If the dependencies corresponding to each deployment unit include disaster tolerance dependencies, create a disaster tolerance deployment unit of each deployment unit according to the disaster tolerance dependencies corresponding to each deployment unit, The device corresponding to the disaster recovery deployment unit is used as the disaster recovery cluster corresponding to the application software; If the dependencies corresponding to the deployment units do not include disaster tolerance dependencies, configure the disaster tolerance dependencies corresponding to the dependencies through the environment variables corresponding to the deployment units, and configure the disaster tolerance dependencies according to the environment variables corresponding to the deployment units. The disaster recovery dependency creates a disaster recovery deployment unit of each of the deployment units, and uses the device corresponding to each of the disaster recovery deployment units as a disaster recovery cluster corresponding to the application software. 4 . The access switching method of application software according to claim 2 , wherein the disaster recovery deployment unit of each deployment unit is deployed according to the operation information of each deployment unit, and the disaster recovery deployment unit of each deployment unit is deployed. 5 . After the device corresponding to the deployment unit is used as the disaster recovery cluster corresponding to the application software, the method includes: Detecting the operation information of each of the deployment units, and determining the target deployment unit whose operation information is updated; According to the operation information of the target deployment unit, the operation information of the disaster recovery deployment unit corresponding to the target deployment unit is updated. 5. The access switching method of application software according to claim 1, wherein, if the target deployment unit corresponding to the initial access address is abnormal, it is determined whether the target deployment unit has deployed the corresponding disaster recovery deployment units, including: If the target deployment unit corresponding to the initial access address is abnormal, determine whether the target deployment unit has a corresponding disaster recovery deployment unit; If the target deployment unit has a corresponding disaster recovery deployment unit, comparing the dependency of the target deployment unit with the disaster recovery dependency of the disaster recovery deployment unit; If the dependency of the target deployment unit matches the disaster recovery dependency of the disaster recovery deployment unit, it is determined that the target deployment unit has deployed the corresponding disaster recovery deployment unit; If the target deployment unit does not have a corresponding disaster recovery deployment unit, and/or the dependency of the target deployment unit does not match the disaster recovery dependency of the disaster recovery deployment unit, it is determined that the target deployment unit is not deployed The corresponding disaster recovery deployment unit. 6. The access switching method of application software according to claim 1, wherein, if the target deployment unit has deployed a corresponding disaster recovery deployment unit, querying the running state of the disaster recovery deployment unit comprises: If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query the status of the disaster recovery deployment unit corresponding to the target deployment unit; If the status of the disaster recovery deployment unit is activated, query the running status of the disaster recovery deployment unit according to the operation information of the disaster recovery deployment unit; If the status of the disaster recovery deployment unit is not started, the disaster recovery deployment unit is started, and the running information of the disaster recovery deployment unit is updated. 7. The access switching method of application software according to claim 6, wherein, if the target deployment unit has deployed a corresponding disaster recovery deployment unit, query the corresponding disaster recovery deployment unit of the target deployment unit. Startup states include: If the target deployment unit has deployed the corresponding disaster recovery deployment unit, query whether the disaster recovery deployment unit corresponding to the target deployment unit has completed scheduling to determine the startup state of the disaster recovery deployment unit; If the target deployment unit corresponding to the disaster recovery deployment unit completes the scheduling, it is determined that the startup status of the disaster recovery deployment unit is started; If the disaster recovery deployment unit corresponding to the target deployment unit has not completed the scheduling, it is determined that the startup state of the disaster recovery deployment unit is not started; If the startup status of the disaster recovery deployment unit is started, querying the running status of the disaster recovery deployment unit according to the operation information of the disaster recovery deployment unit includes: If the status of the disaster recovery deployment unit is activated, acquiring the operation information of the disaster recovery deployment unit; Perform a health check on the running information through a probe, and query the running status of the disaster recovery deployment unit; If the health check of the operation information is passed, it is determined that the operation state of the disaster recovery deployment unit is normal; If the health check of the operation information fails, it is determined that the operation state of the disaster recovery deployment unit is abnormal. 8. The access switching method of application software according to any one of claims 1 to 7, characterized in that, before the receiving an access request and acquiring an initial access address associated with the access request, the method comprises: Receive an application deployment request, define an environment variable of the application according to the deployment request, and create an image based on the environment variable; A dependency is made based on the image, and a deployment unit of the application is deployed according to the dependency. 9. An access switching device for application software, wherein the device comprises: one or more processors; memory; and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the application software of any one of claims 1 to 8 Access toggle methods. 10. A computer-readable storage medium, wherein a computer program is stored thereon, and the computer program is loaded by a processor to execute the access switching method of the application software according to any one of claims 1 to 8 steps in .

Images