Disaster tolerance using initialized containers
By using initialized containers and persistent storage in a container environment, establishing replication pairs and automating container backups, the complex and time-consuming problems of data protection and disaster recovery in the container network are solved, and fast and efficient disaster recovery recovery is achieved.
Patent Information
- Application Number
- CN202280093963.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-24
- Publication Date
- 2024-11-05
Smart Images

Figure CN118901059A_ABST
Abstract
Description
Technical Field
[0001] The present invention generally relates to disaster recovery for containerized applications executing on computing devices. Background Art
[0002] Container technology is increasingly used in computing and has become a popular way to virtualize applications. In addition, containers are a lightweight, agile, and powerful technology solution for deploying software applications. However, data protection and disaster recovery can be challenging and time-consuming for container-based networks. Summary of the invention
[0003] Some concepts are briefly introduced by describing various examples, and these concepts will be further described in the detailed description. The summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.
[0004] According to a first aspect of the present invention, a system with disaster recovery capability is provided. The system includes a memory storing instructions and one or more processors communicating with the memory. The one or more processors execute the instructions to retrieve configuration information, and the configuration information is associated with a containerized application executed as a first instance in a first container environment. The configuration information includes a binary file of the containerized application. A group of containers is configured in a second container environment. The group of containers includes an initialization container and an application container, and the application container has a binary file of the containerized application. A network event associated with the first container environment is detected. Based on the detection of the network event, the execution state of the initialization container is changed. Based on the change of the execution state of the initialization container, the execution of the second instance of the containerized application is started. The second instance uses the application container in the second container environment.
[0005] According to the first aspect, in a first implementation of the system, the one or more processors execute the instructions to configure a replication pair. The replication pair includes a first storage system associated with the first container environment and a second storage system associated with the second container environment.
[0006] According to the first aspect or any implementation of the first aspect, in a second implementation of the system, in order to configure the replication pair, the one or more processors execute the instructions to configure the configuration information and the data associated with the execution of the containerized application to be stored in the first storage system, and configure the configuration information and the data to be replicated from the first storage system to the second storage system.
[0007] According to the first aspect or any implementation of the first aspect, in a third implementation of the system, the one or more processors execute the instructions to retrieve the configuration information from the second storage system.
[0008] According to the first aspect or any implementation of the first aspect, in a fourth implementation of the system, the one or more processors execute the instructions to restore the configuration information from the second storage system to the functional components of the second container environment.
[0009] According to the first aspect or any implementation of the first aspect, in a fifth implementation of the system, the one or more processors execute the instructions to create at least one persistent volume claim (PVC) in the second container environment according to the configuration information.
[0010] According to the first aspect or any implementation of the first aspect, in a sixth implementation of the system, the one or more processors execute the instructions to map the group of containers to the second storage system by using the PVC to establish a communication link between the group of containers and a persistent volume (PV) in the second storage system, retrieve the data from the PV in the second storage system through the communication link, and further start the execution of the second instance of the containerized application based on the retrieved data.
[0011] According to the first aspect or any implementation of the first aspect, in a seventh implementation of the system, in order to configure the group of containers, the one or more processors execute the instructions to: configure the initialization container to an event waiting state.
[0012] According to the first aspect or any implementation of the first aspect, in an eighth implementation of the method, the execution state of the initialization container is the event waiting state. In order to change the execution state of the initialization container, the one or more processors execute the instructions to cause the initialization container to exit the event waiting state according to the detection of the network event, and further to start the execution of the second instance of the containerized application according to the initialization container exiting the event waiting state.
[0013] According to the first aspect or any implementation manner of the first aspect, in a ninth implementation manner of the system, the network event is a failure of at least one computing node that hosts the first container environment.
[0014] According to a second aspect of the present invention, a method is provided. The method includes retrieving configuration information associated with a containerized application executed as a first instance in a first container environment. The configuration information includes a binary file of the containerized application. A set of containers is configured in a second container environment. The set of containers includes an initialization container and an application container, and the application container has a binary file of the containerized application. A network event associated with the first container environment is detected. Based on the detection of the network event, the execution state of the initialization container is changed. Based on the change of the execution state of the initialization container, the execution of a second instance of the containerized application is started. The second instance uses the application container in the second container environment.
[0015] According to the second aspect, in a first implementation of the method, a replication pair is configured. The replication pair includes a first storage system associated with the first container environment and a second storage system associated with the second container environment.
[0016] According to the second aspect or any implementation of the second aspect, in a second implementation of the method, configuring the replication pair includes configuring to store the configuration information and the data associated with the execution of the containerized application in the first storage system, and configuring to replicate the configuration information and the data from the first storage system to the second storage system.
[0017] According to the second aspect or any implementation manner of the second aspect, in a third implementation manner of the method, the method further includes retrieving the configuration information from the second storage system.
[0018] According to the second aspect or any implementation manner of the second aspect, in a fourth implementation manner of the method, the configuration information is restored from the second storage system to a functional component of the second container environment.
[0019] According to the second aspect or any implementation of the second aspect, in a fifth implementation of the method, at least one persistent volume claim (PVC) is created in the second container environment according to the configuration information.
[0020] According to the second aspect or any implementation of the second aspect, in a sixth implementation of the method, the set of containers is mapped to the second storage system by using the PVC to establish a communication link between the set of containers and a persistent volume (PV) in the second storage system. The data is retrieved from the PV in the second storage system through the communication link. The execution of the second instance of the containerized application is further started based on the retrieved data.
[0021] According to the second aspect or any implementation manner of the second aspect, in a seventh implementation manner of the method, configuring the group of containers includes: configuring the initialization container to be in an event waiting state.
[0022] According to the second aspect or any implementation of the second aspect, in an eighth implementation of the method, the execution state of the initialization container is the event waiting state. Changing the execution state of the initialization container further includes: causing the initialization container to exit the event waiting state based on the detection of the network event; and further starting the execution of the second instance of the containerized application based on the initialization container exiting the event waiting state.
[0023] According to a third aspect of the present invention, a non-transitory computer-readable medium storing computer instructions is provided. When executed by one or more processors of a computing device, the instructions cause the one or more processors to perform operations including retrieving configuration information associated with a containerized application executed as a first instance in a first container environment. The configuration information includes a binary file of the containerized application. A group of containers is configured in a second container environment. The group of containers includes an initialization container and an application container, and the application container has a binary file of the containerized application. A network event associated with the first container environment is detected. Based on the detection of the network event, the execution state of the initialization container is changed. Based on the change of the execution state of the initialization container, the execution of a second instance of the containerized application is started. The second instance uses the application container in the second container environment.
[0024] According to the third aspect, in a first implementation of the computer-readable medium, the operation further comprises configuring a replication pair. The replication pair comprises a first storage system associated with the first container environment and a second storage system associated with the second container environment.
[0025] According to the third aspect or any implementation of the third aspect, in a second implementation of the computer-readable medium, the operation for configuring the replication pair further includes configuring to store the configuration information and the data associated with the execution of the containerized application in the first storage system. The operation further includes configuring to replicate the configuration information and the data from the first storage system to the second storage system.
[0026] According to the third aspect or any implementation of the third aspect, in a third implementation of the computer-readable medium, the operation further includes retrieving the configuration information from the second storage system.
[0027] According to the third aspect or any implementation of the third aspect, in a fourth implementation in the computer-readable medium, the operation further includes restoring the configuration information from the second storage system to a functional component of the second container environment.
[0028] According to the third aspect or any implementation of the third aspect, in a fifth implementation in the computer-readable medium, the operation also includes creating at least one persistent volume claim (PVC) in the second container environment according to the configuration information.
[0029] According to the third aspect or any implementation of the third aspect, in a sixth implementation in the computer-readable medium, the operation further includes mapping the set of containers to the second storage system by using the PVC to establish a communication link between the set of containers and a persistent volume (PV) in the second storage system. The operation further includes retrieving the data from the PV in the second storage system through the communication link. The operation further includes starting the execution of the second instance of the containerized application based on the retrieved data.
[0030] According to the third aspect or any implementation of the third aspect, in a seventh implementation in the computer-readable medium, the operation for configuring the set of containers further includes configuring the initialization container to be in an event waiting state.
[0031] According to the third aspect or any implementation of the third aspect, in an eighth implementation in the computer-readable medium, the execution state of the initialization container is the event waiting state. The operation for changing the execution state of the initialization container also includes, based on the detection of the network event, causing the initialization container to exit the event waiting state. The operation also includes, based on the initialization container exiting the event waiting state, starting the execution of the second instance of the containerized application.
[0032] Any of the foregoing examples may be combined with any one or more of the other foregoing examples to create new embodiments within the scope of the invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In the drawings, which are not necessarily drawn to scale, like numerals in different views may describe similar components.The drawings generally illustrate, by way of example and not limitation, various embodiments described herein.
[0034] Figure 1 A block diagram of a system including a container environment for automated container backup using init containers and persistent storage is provided for an exemplary embodiment.
[0035] Figure 2 For example embodiments provided Figure 1 Block diagram of a more detailed view of a container environment for automated container backups using initialization containers and persistent storage.
[0036] Figure 3 A flowchart of a method for performing disaster recovery using an initialization container is provided for an exemplary embodiment.
[0037] Figure 4 A flowchart of another method for performing disaster recovery using an initialization container is provided for an exemplary embodiment.
[0038] Figure 5 A block diagram of a representative software architecture is provided for an exemplary embodiment, which may be used in conjunction with the various device hardware described herein.
[0039] Figure 6 Block diagrams of circuits implementing algorithms and devices for executing methods are provided for exemplary embodiments. DETAILED DESCRIPTION
[0040] First, it should be understood that even though the following provides exemplary implementations of one or more embodiments, Figures 1 to 6The disclosed systems and methods described may be implemented using any number of techniques, whether currently known or not yet in existence. The present invention should in no way be limited to the illustrative implementations, drawings, and techniques discussed below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
[0041] In the following description, reference is made to the accompanying drawings which form a part of this specification, in which specific embodiments that may be implemented are illustrated by way of illustration. These embodiments are described in sufficient detail to enable those skilled in the art to practice the subject matter of the present invention, it being understood that other embodiments may be utilized, and structural, logical, and electrical changes may be made without departing from the scope of the present invention. Therefore, the following description of exemplary embodiments should not be understood in a restrictive sense, and the scope of the present invention is defined by the appended claims.
[0042] As discussed herein, the term "module" includes hardware and / or software designed to perform one or more functions discussed herein.
[0043] As discussed herein, the phrase “container image” refers to a software package (e.g., a static image) that includes configuration information for deploying an application and dependencies such as software components, frameworks, or libraries required to deploy and execute the application.
[0044] As discussed herein, the term "container" refers to an instance of a container image, and an application executes in the execution environment provided by the container. In some aspects, a container is a form of encapsulation used to restrict resources and limit access to processes, which may involve packaging software code and all its dependencies so that it can run uniformly and consistently on any infrastructure. In addition, multiple instances of an application can be deployed from the same container image (e.g., each application instance executes within its container). The goal of containerization is to decouple applications and the associated structures that run the applications from the infrastructure that runs the applications. In some embodiments, containers can use persistent storage that can be delivered in a variety of ways, such as, but not limited to, software-defined in a container orchestrator and external systems.
[0045] As discussed herein, the term “initialization container” (or init container) refers to a container that must run to completion before any application container can execute.
[0046] As discussed herein, the term "persistent storage" refers to a data storage device that retains data after the device is powered off. As discussed herein, the terms "volume" and "persistent volume" (or PV) are used interchangeably to indicate a directory (e.g., hosted in persistent storage or another type of storage device) that includes data accessible to containers (e.g., containers in a Pod). As discussed herein, the term "persistent volume call" (or PVC) indicates a user's request for storage. In some aspects, a PVC may request a specific size and access method to access configuration and data stored in one or more PVs.
[0047] As discussed herein, the term "Pod" refers to a group of containers (e.g., executing on a cluster) that access shared resources (e.g., network, storage), and one or more Pods may be executed by a given compute node.
[0048] As discussed herein, the terms "cluster" and "container environment" are used interchangeably to refer to a group of computing nodes (eg, worker machines or worker nodes) that run containerized applications. In some aspects, a cluster has at least one worker node.
[0049] As discussed herein, the term "namespace" refers to a container environment abstraction that supports isolation of computing resources within a cluster. In some aspects, a namespace refers to a virtual cluster that can be run within a (hardware) cluster. In some aspects, a PVC can be configured as a data object of a namespace.
[0050] Storage replication in a container environment can be used in conjunction with atomic application (app) consistent backups that generate multiple PVCs to cover protection and disaster recovery of application configurations and application-related data. However, the recovery of configurations and data can be time-consuming. For example, after a source container environment (also referred to as a source cluster or primary cluster) goes down due to a network event (e.g., a network failure or other type of network disaster event), a target container environment (also referred to as a target cluster or secondary cluster) has to perform some time-consuming tasks. Such tasks include, for example, creating a PV for storing application-related data and configurations of a containerized application executed as an instance in a first container environment; creating a namespace in a second container environment; creating a PVC to obtain access to the PV; and creating a Pod in the second container environment that uses the PVC as a volume to execute another instance of the containerized application. Creating a PVC can include configuring functional components (e.g., cluster information, services, workloads, and configuration storage functional components) in the second container environment, which can be used in conjunction with the execution of the application instance.
[0051] In an implementation of the subject technology discussed herein, disaster recovery is performed using initialization containers to improve efficiency and reduce execution time. For example, after establishing a replication pair (e.g., by configuring a first storage system associated with a first container environment and a second storage system associated with a second container environment), PVs are created in the two storage systems to store application data and configurations. PVCs are created to access PVs, and the PVCs may include configuring functional components in a container environment to be in a ready-to-serve state. A Pod including an initialization container and an application container (with a binary file of a containerized application) is created in the second container environment. The initialization container can be placed in an event waiting state to wait for a triggering event associated with the first container environment (e.g., a network failure event or other type of network disaster event). Upon detecting a triggering event, the initialization container exits the event waiting state (e.g., based on a command from a replication manager module) and triggers the execution of a containerized application instance using the binary file in the application container.
[0052] Figure 1 A block diagram of a system 100 provided for an exemplary embodiment includes a container environment for automated container backup using an initialization container and persistent storage. As shown, system 100 includes clusters 110 and 130, each of which includes hardware resources (e.g., one or more processors, memories, storage units, etc.) that provide a container environment to execute applications deployed from container images (also referred to as containerized applications). Clusters 110 and 130 can be understood to represent a group of (hardware) computing nodes, which are working machines, and each cluster can include at least one computing node-to execute and perform operations of one or more applications deployed from container images.
[0053] In one embodiment, a given cluster (e.g., cluster 110 or cluster 130) includes namespaces, such as namespace 112 and namespace 132. Each namespace refers to a virtual cluster that can be run within a (hardware) cluster (e.g., cluster 110 or cluster 130). It should be understood that more than one virtual cluster (e.g., namespace) can be provided and executed using the hardware components of a given cluster. In a given namespace, specific computing resources provided by the hardware cluster can be assigned to a namespace. In addition, specific resources can be isolated (e.g., provided exclusively) to the same namespace and not assigned to another namespace. By using namespaces, resources can be divided, thereby facilitating the isolation of resources between different user groups accessing each namespace.
[0054] As further described, namespace 112 and namespace 132 include various functional components that implement at least a portion of a control plane that controls the allocation of tasks and operations associated with containers. In some aspects, the functional components can be configured as part of a Pod associated with a namespace. Figure 1 In the example, each namespace includes the following functional components: cluster information (or information (info)) components (e.g., cluster information component 114 and cluster information component 134), service components (e.g., service component 116 and service component 136), workload components (e.g., workload component 118 and workload component 138), configuration (or configuration (config)) storage components (e.g., configuration storage component 120 and configuration storage component 140), and container writable layer components (e.g., container writable layer component 122 and container writable layer component 142).
[0055] The following discussion describes embodiments of each of the foregoing components included in each namespace, such as namespace 112 and namespace 132. The cluster information component provides information about the corresponding cluster, such as information about configuration information of the cluster, nodes in the cluster, Pods included in the nodes or cluster, applications running in Pods or containers, names of persistent volumes, services currently running and accessible (e.g., by providing appropriate credentials) in the cluster, and other types of information.
[0056] The service component allows access to services provided by the cluster (e.g., based on information provided by the cluster information component). In one example, a service can provide a mechanism for accessing applications executed on a set of Pods.
[0057] The workload component manages the cluster's tasks and jobs, which can be performed by applications executing in the cluster.
[0058] The configuration storage component provides the ability to store, maintain, and modify configuration information for Pods, containers, and clusters. For example, a request to store or update confirmation information can be made, which can be processed and executed by the configuration storage component.
[0059] The container writable layer component provides functionality for managing the writable layers of a file system (e.g., a directory that can include a set of files) and facilitating write operations to these layers. As further discussed herein, a given file system can include writable and readable layers, or it can include read-only layers.
[0060] In one embodiment, the above-described components included in namespace 112 and namespace 132 utilize volatile memory (eg, non-persistent memory) provided by cluster 110 or cluster 130 , respectively.
[0061] As further shown, cluster 110 and cluster 130 are communicatively coupled to storage system 150 and storage system 160, respectively. In some examples, such as during replication process 106, storage system 150 and storage system 160 communicate with each other (eg, send and receive messages and requests, etc.).
[0062] Storage system 150 and storage system 160 provide non-volatile storage for storing a set of configuration volumes and persistent volumes in a persistent manner. For example, storage system 150 includes configuration volume 151 and persistent volume (PV) 153, and storage system 160 includes configuration volume 151' and PV 153'. Configuration volumes store configuration information for containers (e.g., container images and applications therein). PV represents a specific number of storage units that have been allocated for use in a cluster, and the specific number of storage units can be used by calling PVC discussed further herein. In some aspects, PV is used to store application data, such as data 104 and 104'. In some embodiments, the configuration information of the above-mentioned containers includes application binaries, such as binary files 102 and 102' associated with containerized applications.
[0063] Figure 1 Each cluster in also includes a container storage interface (CSI) (e.g., CSI 180 and CSI 190) and a backup and restore orchestrator (e.g., backup and restore orchestrator 182 and backup and restore orchestrator 192).
[0064] The backup and restore orchestrator (or orchestrator) 182 may be implemented to perform a backup of a containerized application (e.g., an application executed as a first application instance 111 in the cluster 110) through the container writable layer 122 to track the state of the application. An exemplary backup operation may include configurations such as data 104 and binary files 102. The orchestrator 182 may also operate to assist in restore operations, such as, but not limited to, disaster recovery.
[0065] CSI 180 may provide an interface to storage system 150 during replication process 106 that supports creation and configuration of persistent storage external to orchestrator 182, input / output (I / O) of orchestrator 182, and advanced functionality of orchestrator 182, such as, but not limited to, performing any of the disaster recovery functions discussed herein. Additional (or extended) container storage interface (CSI EXT) 124 may be implemented to interface orchestrator 182 with storage system 150.
[0066] The orchestrator 192 may be implemented in the execution of a replay (or restore) operation of executing a second application instance 113 in the cluster 130 using the replicated data 104' and configuration (e.g., binary file 102') stored in the storage system 160. The CSI 190 may provide an interface to the storage system 160 that supports the creation and configuration of persistent storage external to the orchestrator 192, input / output (I / O) of the orchestrator 192, and advanced functions of the orchestrator 192, such as, but not limited to, performing any disaster recovery functions discussed herein. The CSI EXT 126 may be implemented to interface with the orchestrator 192 of the storage system 160.
[0067] In one embodiment, container writable layer component 122 utilizes CSI 180 to retrieve configuration information from configuration volume 151 provided by storage system 150. Similarly, container writable layer component 142 utilizes CSI 190 to retrieve configuration information (e.g., binary file 102') from a configuration volume provided by storage system 160. Each CSI provides a mechanism for accessing arbitrary block and file storage systems, associated with the disclosed disaster recovery functionality.
[0068] In one embodiment, backup and restore orchestrators 182 and 192 may be implemented as separate containers that are provided to perform operations in conjunction with another (e.g., primary) container. In one example, each backup and restore orchestrator 182 and 192 may be used to perform operations involving backing up and restoring a specific application running as an application instance in a container (or Pod) (e.g., after a disaster event in cluster 110, an application executing as application instance 111 is restored to application instance 113). In another embodiment, a given backup and restore orchestrator may be implemented as an independent process or service that runs on a cluster but not within a container, or runs in a different environment such as a sandbox environment or runs within a virtual machine.
[0069] In an exemplary embodiment, the system 100 also includes a replication manager module (RMM) 108 for performing public functions associated with disaster recovery of containerized applications. In some embodiments, the RMM 108 configures a replication pair, which may include storage systems 150 and 160 associated with corresponding clusters (or container environments) 110 and 130. During the execution of the first instance of a containerized application (e.g., application instance 111) in cluster 110, application data 104 and application binary files 102 are stored in storage system 150 (e.g., configuration volume 151 and PV 153). During the replication process 106, application data 104 and application binary files 102 are replicated and stored in storage system 160 (e.g., in PV 153' and configuration volume 151') as corresponding application data 104' and binary files 102'. When a network event associated with cluster 110 is detected, RMM 108 further configures initialization containers 144 and application containers 146 related to disaster recovery functions. More specifically, when a network event is detected, RMM 108 uses initialization container 144 and application container 146 to execute second application instance 113 of the containerized application. Figures 2 to 4 A more detailed description of the disaster recovery functions performed by RMM 108 is discussed.
[0070] even though Figure 1 RMM 108 is shown as a separate module within system 100, the present disclosure is not limited in this regard. More specifically, RMM 108 can be implemented as part of orchestrator 182, orchestrator 192, or another module hosted by a node within cluster 110 or cluster 130.
[0071] Figure 2 For example embodiments provided Figure 1 A block diagram 200 of a more detailed view of a container environment for automated container backup using init containers and persistent storage. Figure 2 , FIG. 200 illustrates functions performed by RMM 108 related to disaster recovery using initialization container 144 (eg, Figure 3 Method 300 and Figure 4 Function of method 400).
[0072] In some embodiments, functional components 134, 136, 138, and 140 of cluster 130 are configured in corresponding Pods of namespace 132. For example, cluster information component 134 and configuration storage component 140 are configured in Pod 202. Service component 136 is configured in Pod 204. Workload component 138 is configured in multiple Pods, such as Pods 206 to 208.
[0073] Figure 3 A flowchart of a method for performing disaster recovery using an initialization container is provided for an exemplary embodiment. Method 300 includes operations 302, 304, 306, 308, 310, 312, and 314. By way of example and not limitation, method 300 may be performed by, for example Figure 6 The device 600 or the like is executed by one or more processors of the RMM 108 in a computing device.
[0074] In some aspects, RMM 108 establishes a replication pair associated with a first container environment (e.g., cluster 110) and a second container environment (e.g., cluster 130) before the disaster recovery function of method 600 is initiated. More specifically, RMM 108 establishes a backup of binary files 102 and data 104 associated with an application instance 111 of a containerized application executed in cluster 110. RMM 108 also configures replication process 106 to periodically replicate binary files 102 and data 104 in a storage system 160 associated with cluster 130 as binary files 102' and data 104'. In this regard, in operation 302, RMM 108 creates PVs (e.g., configuration volume 151' and persistent volume 153') for binary files 102' and data 104'.
[0075] In operation 304, RMM 108 creates namespaces and PVCs. More specifically, RMM 108 creates namespace 132 and Pods 202 to 208 to host corresponding functional components 134 to 140. Creating PVCs also enables communication between Pods within namespace 132 and storage system 160 (e.g., via communication links 194 and 196 between storage system 160 and container writable layer 142).
[0076] In operation 306, RMM 108 creates Pod 210 to host initialization container 144 and application container 146. In addition, RMM 108 configures initialization container 144 to an event wait state. In some aspects, initialization container 144 configures application container 146 to a ready-to-serve state for executing a containerized application (e.g., a containerized application having application instance 111 executing on cluster 110). For example, initialization container 144 stores binary file 102' of the containerized application (which can be retrieved from storage system 160 in operation 212) in application container 146. In operation 308, initialization container 144 is in an event wait state (e.g., waiting for an event trigger).
[0077] In operation 310, it is determined whether an event trigger 214 is detected. In some embodiments, the event trigger 214 may include a network event associated with the cluster 110, such as a network failure event, a computing node failure event, a container failure event, or other types of network disasters associated with the application instance 111 of the containerized application. If the event trigger is not detected, the process continues at operation 308. If the event trigger 214 is detected, then in operation 312, the initialization container 144 exits the event wait state. For example, the RMM 108 may detect the event trigger 214 and send a command to the initialization container 144 to exit the event wait state. In operation 314, the application instance 113 of the containerized application is executed in the Pod 210 according to the initialization container 144 exiting the event wait state.
[0078] Figure 4 A flowchart of another method 400 for performing disaster recovery using an initialization container is provided for an exemplary embodiment. The method 400 includes operations 402, 404, 406, 408, and 410. By way of example and not limitation, the method 400 may be performed by, for example Figure 6 The device 600 or the like is executed by one or more processors of the RMM 108 in a computing device.
[0079] In operation 402, configuration information is retrieved, the configuration information being associated with a containerized application executing as a first instance in a first container environment. For example, RMM 108 retrieves configuration information associated with a containerized application executing as application instance 111 in cluster 110. The configuration information includes a binary file of the containerized application (e.g., binary file 102' retrieved from storage system 160).
[0080] In operation 404, a set of containers is configured in a second container environment. The set of containers includes an initialization container and an application container, the application container having a binary file of a containerized application. For example, RMM108 configures namespace 132 in cluster 130 and configures functional components 134 to 140 in corresponding Pods. RMM 108 further configures initialization container 144 and application container 146 using binary file 102' in Pod 210 within namespace 132. In addition, application container 146 is prepared (e.g., by RMM 108 or initialization container 144) and is in a ready-to-service state with an available connection to configuration volume 151' and PV 153' through container writable layer 142. When application container 146 is in a ready-to-service state, initialization container 144 is placed in an event waiting state (e.g., waiting for an event trigger associated with a network event in cluster 110).
[0081] In operation 406, a network event associated with the first container environment is detected. For example, RMM 108 detects event trigger 214 associated with cluster 110. More specifically, event trigger 214 may include a notification of a network event associated with a containerized application executing as application instance 111 in cluster 110. Exemplary network events may include an application instance failure associated with executing application instance 111, such as a failure of a container, Pod, or compute node.
[0082] In operation 408, the execution state of the initialization container is changed according to the detection of the network event. For example, RMM 108 can generate a command to initialization container 144, which causes the initialization container to exit the event waiting state.
[0083] In operation 410, execution of a second instance of the containerized application is initiated according to the change in the execution state of initialization container 410. The second instance is used to use the application container in the second container environment. For example, after RMM 108 transmits a command to initialization container 144 to exit the event wait state, initialization container 144 exits the event wait state and triggers execution of the containerized application as second application instance 113 within application container 146. After the containerized application is executed as second application instance 113, initialization container 144 is closed.
[0084] In some embodiments, RMM 108 configures a replication pair as part of the above process. More specifically, the replication pair includes a first storage system (e.g., storage system 150) associated with the first container environment (e.g., cluster 110) and a second storage system (e.g., storage system 160) associated with the second container environment (e.g., cluster 130). In some embodiments, to configure the replication pair, RMM 108 configures storage of configuration information (e.g., binary file 102) and data (e.g., data 104) associated with the execution of the containerized application in the first storage system (e.g., storage system 150). RMM 108 also configures a replication process 106 for replicating the configuration information and data (e.g., as binary file 102' and data 104') from the first storage system to the second storage system (e.g., storage system 160).
[0085] In some aspects, configuration of the replication pair by RMM 108 results in retrieving configuration information (e.g., binary file 102') from a second storage system (e.g., storage system 160) and restoring the configuration information from the second storage system to functional components of the second container environment. For example, RMM 108 creates namespace 132 and restores the configuration information to one or more functional components 134 to 140 in namespace 132. RMM 108 further creates at least one persistent volume claim (PVC) in the second container environment based on the configuration information. Creation of the at least one PVC enables RMM 108 to map the set of containers (e.g., containers of Pods 202 to 210) to storage system 160 using the PVC to establish a communication link between the set of containers and the PV in storage system 160 (e.g., through container writable layer 142).
[0086] In some embodiments, RMM 108 retrieves data 104' from PV 153' in storage system 160 via the established communication link, and further initiates execution of a second instance of the containerized application (e.g., application instance 113) based on the retrieved data 104' (which may include application data associated with the containerized application).
[0087] In some embodiments, configuring the set of containers includes configuring initialization container 144 to an event wait state. In some aspects, RMM 108 causes initialization container 144 to exit the event wait state based on detection of a network event (e.g., based on detecting event trigger 214). RMM 108 waits for execution of a second instance of a containerized application (e.g., application instance 113) to be started further based on the initialization container exiting the event wait state.
[0088] Figure 5 A block diagram of a representative software architecture is provided for an exemplary embodiment, which may be used in conjunction with the various device hardware described herein. Figure 5 The software architecture 502 is merely a non-limiting example, and it should be understood that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 502 may be implemented in hardware (e.g., with Figure 1 100) is executed on a network node associated with the system 100 in Figure 6 The device 600 is the same as the device 600, which includes a processor 605, a memory 610, a storage unit 615 and / or 620, and I / O interfaces 625 and 630.
[0089] A representative hardware layer 504 is shown, which may represent Figure 6 The representative hardware layer 504 includes one or more processing units 506 with associated executable instructions 508. The executable instructions 508 represent executable instructions of the software architecture 502, including implementing Figures 1 to 4 The hardware layer 504 also includes a memory or storage module 510, which can store executable instructions 508. The hardware layer 504 can also include other hardware 512, which represents any other hardware of the hardware layer 504, such as other hardware shown as part of the device 600.
[0090] The memory or storage module 510 may include a storage device having firmware implementing the RMM 560. In some aspects, the RMM 560 includes suitable circuits, logic, interfaces, or code and may be used to perform the functions described herein. Figures 1 to 4 In an exemplary embodiment, the RMM 560 may be an operating system 514 (e.g., Figure 5 504) or as part of the application 520 of the software architecture 502. In yet another embodiment, the RMM 560 may be implemented in a distributed manner, wherein different components of the RMM 560 are implemented in hardware (e.g., as part of the hardware layer 504) or in software (as part of the operating system 514 or the application 520).
[0091] exist Figure 5In the exemplary architecture of FIG. 5 , the software architecture 502 can be conceptualized as a stack of layers, each of which has a specific function. For example, the software architecture 502 can include layers such as an operating system 514, a library 516, a framework / middleware 518, an application 520, and a presentation layer 544. In operation, the application 520 or other components within the layer can call an application programming interface (API) call 524 through the software stack, and receive a response, a return value, etc. shown as a message 526 in response to the API call 524. Figure 5 The layers shown are representative in nature, and not all software architectures 502 have all layers. For example, some mobile or dedicated operating systems may not provide framework / middleware 518, while other operating systems may provide such layers. Other software architectures may include additional or different layers.
[0092] The operating system 514 can manage hardware resources and provide public services. The operating system 514 can include, for example, a kernel 528, services 530, and drivers 532. The kernel 528 can be used as an abstraction layer between the hardware and other software layers. For example, the kernel 528 can be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, etc. The service 530 can provide other public services for other software layers. The driver 532 can be responsible for controlling the underlying hardware or connecting to the underlying hardware. For example, depending on the hardware configuration, the driver 532 can include a display driver, a camera driver, a Bluetooth driver, a flash driver, a serial communication driver (e.g., a Universal Serial Bus (USB) driver), Drivers, audio drivers, power management drivers, etc.
[0093] The library 516 may provide a common infrastructure that may be used by the application 520 or other components or layers. The function of the library 516 is generally to enable other software modules to perform tasks in a more convenient manner than directly connecting to the functions of the underlying operating system 514 (e.g., kernel 528, service 530, or driver 532). The library 516 may include a system library 534 (e.g., C standard library), which may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 516 may include an API library 536, such as a media library (e.g., a library that supports the presentation and operation of various media formats (e.g., MPEG4, H.264, MP3, AAC, AMR, JPGPNG)), a graphics library (e.g., an OpenGL framework that may be used to present 2D and 3D graphics content on a display), a database (e.g., SQLite that may provide various relational database functions), a webpage library (e.g., WebKit that may provide web browsing functions), etc. The library 516 may also include a variety of other libraries 538 to provide many other APIs to the application 520 and other software components / modules.
[0094] Framework / middleware 518 (sometimes also referred to as middleware) can provide a high-level common infrastructure that can be used by applications 520 or other software components / modules. For example, framework / middleware 518 can provide various graphical user interface (GUI) functions, advanced resource management, advanced location services, etc. Framework / middleware 518 can provide various other APIs that can be used by applications 520 or other software components / modules, some of which can be specific to a particular operating system 514 or platform.
[0095] Applications 520 include built-in applications 540 and third-party applications 542. Examples of representative built-in applications 540 may include, but are not limited to, contact applications, browser applications, reader applications, location applications, media applications, messaging applications, or game applications. Third-party applications 542 may include any of built-in applications 540 as well as various other applications. In a specific example, third-party applications 542 (e.g., applications developed by entities other than the vendor of a particular platform using Android TM or iOS TM Software development kit (SDK) applications can be developed on platforms such as iOS TM 、Android TM , Mobile software running on mobile operating systems such as Windows Phone or other mobile operating systems. In this example, third-party application 542 can call API call 524 provided by mobile operating system (such as operating system 514) to facilitate the implementation of the functions described herein.
[0096] Applications 520 may utilize built-in operating system functionality (e.g., kernel 528, services 530, and drivers 532), libraries (e.g., system libraries 534, API libraries 536, and other libraries 538), and framework / middleware 518 to create a user interface to interact with a user of the system. Alternatively or additionally, in some systems, interaction with the user may be performed through a presentation layer (e.g., presentation layer 544). In these systems, the application / module "logic" may be separated from aspects of the application / module that interact with the user.
[0097] Some software architectures use virtual machines. Figure 5 In the example of FIG. 5 , a virtual machine is shown by virtual machine 548. A virtual machine creates a software environment in which an application / module can be run as if it were on a hardware machine (e.g., Figure 6 The virtual machine 548 is hosted by a host operating system (e.g., operating system 514) and typically (although not always) has a virtual machine monitor 546 that manages the operation of the virtual machine 548 and the connection with the host operating system (i.e., operating system 514). The software architecture 502 is executed in the virtual machine 548, such as an operating system (OS) 550, a library 552, a framework / middleware 554, an application 556, and / or a presentation layer 558. These software architecture layers executed in the virtual machine 548 can be the same as the corresponding layers described above, or they can be different.
[0098] Figure 6 A block diagram of circuitry for devices implementing algorithms and execution methods provided for exemplary embodiments. Not all components need to be used in various embodiments. For example, a client, server, and cloud-based network device may each use a different set of components, or, in the case of a server, a larger storage device.
[0099] An exemplary computing device in the form of a computer 600 (also referred to as computing device 600, computing node 600, computer system 600, or computer 600) may include a processor 605, a memory 610, a removable storage unit 615, a non-removable storage unit 620, an input interface 625, an output interface 630, and a communication interface 635, all connected via a bus 640. Although the exemplary computing device is shown and described as a computer 600, the computing device may take different forms in different embodiments.
[0100] The memory 610 may include volatile memory 645 and nonvolatile memory 650, and may store programs 655. The computing device 600 may include or have access to a computing environment that includes various computer-readable media, such as the volatile memory 645, the nonvolatile memory 650, the removable storage unit 615, and the non-removable storage unit 620. Computer memory includes random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium capable of storing computer-readable instructions.
[0101] Computer readable instructions stored in a computer readable medium (e.g., a program 655 stored in memory 610) can be executed by a processor 605 of the computing device 600. Hard drives, CD-ROMs, and RAM are some examples of items including non-transitory computer readable media (e.g., storage devices). The terms "computer readable medium" and "storage devices" do not include carrier waves that are considered too transient. "Computer readable non-transitory media" include all types of computer readable media, including magnetic storage media, optical storage media, flash media, and solid-state storage media. It should be understood that the software can be installed in a computer and sold with the computer. Alternatively, the software can be obtained and loaded into the computer, including obtaining the software through a physical medium or distribution system, including, for example, obtaining the software from a server owned by the software creator or from a server that the software creator does not own but uses. For example, the software can be stored on a server for distribution over a network. As used herein, the terms "computer readable medium" and "machine readable medium" are interchangeable.
[0102] The program 655 may utilize the RMM 660. In some aspects, the RMM 660 includes suitable circuits, logic, interfaces, or code and may be used to perform the operations described herein. Figures 1 to 4 Any of the functions of the RMM 108 discussed.
[0103] Any one or more modules described herein may be implemented using hardware (e.g., a processor of a machine, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or any suitable combination thereof). In addition, any two or more of these modules may be combined into a single module, and the functionality of a single module described herein may be subdivided between multiple modules. In addition, according to various exemplary embodiments, the modules described herein as being implemented within a single machine, database, or device may be distributed to multiple machines, databases, or devices.
[0104] Although several embodiments are described in detail above, other modifications may be made. For example, the logic flow described in the figure does not require the specific order or sequential order shown to achieve the desired result. Other steps may be provided to the described flow or steps may be deleted from the described flow, and other components may be added to the described system or components may be removed from the described system. Other embodiments may be within the scope of the appended claims.
[0105] It should also be understood that software including one or more computer executable instructions that facilitate the processing and operations described above with respect to any or all of the steps of the present invention may be installed in and sold with one or more computing devices consistent with the present invention. Alternatively, the software may be acquired and loaded into one or more computing devices, including acquiring the software via a physical medium or distribution system, including, for example, acquiring the software from a server owned by the creator of the software or from a server not owned by the creator of the software but used by the creator of the software. For example, the software may be stored on a server for distribution over a network.
[0106] In addition, it will be appreciated by those skilled in the art that the present invention is not limited in its application to the construction and arrangement details of the components set forth in the specification or illustrated in the drawings. The embodiments herein can be applied to other embodiments and can be practiced or executed in various ways. In addition, it will be appreciated that the wording and terminology used herein are for description and should not be considered restrictive. The use of "include", "comprise" or "have" and its variants herein is intended to cover the items listed thereafter and their equivalents and other items. Unless otherwise limited, the terms "connect", "couple" and "install" and their variants are widely used herein and cover direct and indirect connections, couplings and installations. In addition, and its variants are not limited to physical or mechanical connections or couplings. In addition, terms such as "upper", "lower", "bottom" and "top" are relative and are used to help illustrate, but are not restrictive.
[0107] The components of the illustrative devices, systems, and methods used in accordance with the described embodiments may be implemented at least in part in digital electronic circuitry, analog electronic circuitry, or in computer hardware, firmware, software, or a combination thereof. For example, these components may be implemented as a computer program product (such as a computer program, program code, or computer instructions) tangibly embodied in an information carrier, or in a machine-readable storage device, for execution by a data processing apparatus (such as a programmable processor, a computer, or multiple computers), or for controlling the operation of a data processing apparatus.
[0108] The computer program can be written in any form of programming language (including compiled or interpreted languages) and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. The computer program can be deployed to be executed in one computer or in multiple computers at one site, or it can be distributed at multiple sites and interconnected through a communication network. In addition, the functional programs, codes, and code segments used to implement the technology described herein are easily understood by programmers in the field of the technology described herein as being within the scope of the claims. The method steps associated with the illustrative embodiments can be performed by one or more programmable processors, thereby executing computer programs, codes, or instructions to perform functions (e.g., operating on input data and / or generating output). For example, the method steps can also be performed by a dedicated logic circuit (e.g., a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)), and the device for performing the method can be implemented as the dedicated logic circuit.
[0109] The various illustrative logical blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or executed using a general purpose processor, a digital signal processor (DSP), an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, and optionally, the processor may also be any processor, controller, microcontroller, or state machine. A processor may also be implemented by a combination of computing devices, such as a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other similar configuration.
[0110] For example, processors suitable for executing computer programs include general and special microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, the computer also includes one or more mass storage devices (such as magnetic disks, magneto-optical disks, or optical disks) for storing data, or is operably coupled to one or more mass storage devices for storing data to receive data from the mass storage device and / or transmit data to the mass storage device. Information carriers suitable for embodying computer program instructions and data include various forms of non-volatile memory, for example, semiconductor storage devices, such as electrically programmable read-only memory or electrically programmable ROM (electrically programmable read-only memory, EPROM), electrically erasable programmable ROM (electrically erasable programmable ROM, EEPROM), flash memory devices, or data storage disks (for example, magnetic disks, built-in hard disks, or removable disks, magneto-optical disks, CD-ROMs, and DVD-ROM disks). The processor and memory can be supplemented by or incorporated into a dedicated logic circuit.
[0111] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips described above may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0112] As used herein, "machine-readable medium (or computer-readable medium)" includes devices capable of temporarily or permanently storing instructions and data, and may include, but are not limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of memory (e.g., Erasable Programmable Read-Only Memory (EEPROM)), or any suitable combination thereof. The term "machine-readable medium" should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) that can store processor instructions. The term "machine-readable medium" should also be understood to include any medium or combination of multiple media that can store instructions executed by one or more processors, and when one or more processors execute the instructions, one or more processors perform any one or more methods described herein. Accordingly, "machine-readable medium" refers to a single storage device or device, as well as a "cloud"-based storage system or storage network including multiple storage devices or devices. The term "machine-readable medium" used herein does not include the signal itself.
[0113] In an exemplary embodiment, the computing device 600 includes an edge detection module for detecting edge information of a previous frame, the detection being based on rendered graphics data associated with the previous frame; a hint determination module for determining hint information from the previous frame, the determination being based on the edge information, the hint information indicating the amount of high frequency information along a horizontal (X) axis and a vertical (Y) axis of an XY coordinate system in the rendered graphics data; a parameter value determination module for determining expected parameter values of a parameter set associated with a plurality of sampler data structures using the hint information; a selection module for selecting a sampler data structure from the plurality of sampler data structures based on the expected parameter values; and a rendering module for rendering a current frame using the selected sampler data structure, the current frame being continuous with the previous frame. In an exemplary embodiment, the above modules are implemented as part of a TBSS rendering module for processing 3D graphics data.
[0114] In addition, without departing from the scope of the present invention, the techniques, systems, subsystems and methods described and illustrated as discrete or separate in the various embodiments may be combined or integrated with other systems, modules, techniques or methods. Other items shown or discussed as coupled or directly coupled or communicating with each other may also be indirectly coupled or communicated via an interface, device or intermediate component using electrical, mechanical or other means. Other variations, substitutions and altered examples may be determined by those skilled in the art without departing from the scope disclosed herein.
[0115] Although the present invention has been described with reference to specific features and embodiments, it is apparent that various modifications and combinations may be made thereto without departing from the scope of the invention. For example, other components may be added to or removed from the described system. Therefore, the specification and drawings should be viewed simply as an illustration of the invention as defined by the appended claims, and any modifications, variations, combinations or equivalents that fall within the scope of the invention are contemplated. Other aspects may be within the scope of the appended claims. Finally, the conjunction "or" as used herein refers to a non-exclusive "or" unless otherwise specifically stated.
Claims
1. A system with disaster recovery capability, characterized in that: The system comprises: a memory storing instructions; and One or more processors in communication with the memory, the one or more processors executing the instructions to: retrieving configuration information associated with a containerized application executing as a first instance in a first container environment, the configuration information including a binary file of the containerized application; configuring a group of containers in a second container environment, the group of containers comprising an initialization container and an application container, the application container having the binary file of the containerized application; detecting a network event associated with the first container environment; According to detecting the network event, changing the execution state of the initialization container; and Based on the change in the execution state of the initialization container, execution of a second instance of the containerized application is initiated, the second instance using the application container in the second container environment.
2. The system according to claim 1, characterized in that The one or more processors execute the instructions to: A replication pair is configured, the replication pair including a first storage system associated with the first container environment and a second storage system associated with the second container environment.
3. The system according to claim 2, characterized in that To configure the replication pair, the one or more processors execute the instructions to: configuring to store the configuration information and data associated with the execution of the containerized application in the first storage system; as well as The configuration information and the data are copied from the first storage system to the second storage system.
4. The system according to claim 3, characterized in that The one or more processors execute the instructions to: The configuration information is retrieved from the second storage system.
5. The system according to claim 3 or 4, characterized in that: The one or more processors execute the instructions to: The configuration information is restored from the second storage system to the functional components of the second container environment.
6. The system according to any one of claims 3 to 5, characterized in that The one or more processors execute the instructions to: At least one persistent volume claim (PVC) is created in the second container environment according to the configuration information.
7. The system according to claim 6, characterized in that The one or more processors execute the instructions to: Mapping the set of containers to the second storage system by using the PVC to establish a communication link between the set of containers and a persistent volume (PV) in the second storage system; retrieving the data from the PV in the second storage system via the communication link; as well as The execution of the second instance of the containerized application is initiated further based on the retrieved data.
8. The system according to any one of claims 1 to 7, characterized in that To configure the set of containers, the one or more processors execute the instructions to: The initialization container is configured to be in an event waiting state.
9. The system according to claim 8, characterized in that The execution state of the initialization container is the event waiting state. In order to change the execution state of the initialization container, the one or more processors execute the instructions to: According to the detection of the network event, causing the initialization container to exit the event waiting state; and Further based on the initialization container exiting the event waiting state, starting the execution of the second instance of the containerized application.
10. The system according to any one of claims 1 to 9, characterized in that The network event is a failure of at least one computing node hosting the first container environment.
11. A method, characterized in that include: retrieving configuration information associated with a containerized application executing as a first instance in a first container environment, the configuration information including a binary file of the containerized application; configuring a group of containers in a second container environment, the group of containers comprising an initialization container and an application container, the application container having the binary file of the containerized application; detecting a network event associated with the first container environment; According to detecting the network event, changing the execution state of the initialization container; as well as Based on the change in the execution state of the initialization container, execution of a second instance of the containerized application is initiated, the second instance using the application container in the second container environment.
12. The method according to claim 11, characterized in that Also includes: A replication pair is configured, the replication pair including a first storage system associated with the first container environment and a second storage system associated with the second container environment.
13. The method according to claim 12, characterized in that Configuring the replication pair includes: configuring to store the configuration information and data associated with execution of the containerized application in the first storage system; and The configuration information and the data are copied from the first storage system to the second storage system.
14. The method according to claim 13, characterized in that Also includes: The configuration information is retrieved from the second storage system.
15. The method according to claim 13 or 14, characterized in that Also includes: The configuration information is restored from the second storage system to the functional components of the second container environment.
16. The method according to any one of claims 13 to 15, characterized in that Also includes: At least one persistent volume claim (PVC) is created in the second container environment according to the configuration information.
17. The method according to claim 16, characterized in that Also includes: Mapping the set of containers to the second storage system by using the PVC to establish a communication link between the set of containers and a persistent volume (PV) in the second storage system; retrieving the data from the PV in the second storage system via the communication link; as well as The execution of the second instance of the containerized application is initiated further based on the retrieved data.
18. The method according to any one of claims 11 to 17, characterized in that Configuring the set of containers includes: The initialization container is configured to be in an event waiting state.
19. The method according to claim 18, characterized in that The execution state of the initialization container is the event waiting state, and changing the execution state of the initialization container further includes: According to the detection of the network event, causing the initialization container to exit the event waiting state; and Further based on the initialization container exiting the event waiting state, starting the execution of the second instance of the containerized application.
20. A non-transitory computer readable medium storing computer instructions, characterized in that: When executed by one or more processors of a computing device, the instructions cause the one or more processors to perform operations including: retrieving configuration information associated with a containerized application executing as a first instance in a first container environment, the configuration information including a binary file of the containerized application; configuring a group of containers in a second container environment, the group of containers comprising an initialization container and an application container, the application container having the binary file of the containerized application; detecting a network event associated with the first container environment; According to detecting the network event, changing the execution state of the initialization container; as well as Based on the change in the execution state of the initialization container, execution of a second instance of the containerized application is initiated, the second instance using the application container in the second container environment.
21. The non-transitory computer readable medium of claim 20, wherein: The operations also include: A replication pair is configured, the replication pair including a first storage system associated with the first container environment and a second storage system associated with the second container environment.
22. The non-transitory computer readable medium of claim 21, wherein: The operations for configuring the replication pair further include: configuring to store the configuration information and data associated with execution of the containerized application in the first storage system; and The configuration information and the data are copied from the first storage system to the second storage system.
23. The non-transitory computer readable medium of claim 22, wherein: The operations also include: The configuration information is retrieved from the second storage system.
24. The non-transitory computer readable medium according to claim 22 or 23, wherein: The operations also include: The configuration information is restored from the second storage system to the functional components of the second container environment.
25. The non-transitory computer readable medium according to any one of claims 22 to 24, wherein: The operations also include: At least one persistent volume claim (PVC) is created in the second container environment according to the configuration information.
26. The non-transitory computer readable medium of claim 25, wherein: The operations also include: Mapping the set of containers to the second storage system by using the PVC to establish a communication link between the set of containers and a persistent volume (PV) in the second storage system; retrieving the data from the PV in the second storage system via the communication link; and The execution of the second instance of the containerized application is initiated further based on the retrieved data.
27. The non-transitory computer readable medium according to any one of claims 20 to 26, wherein: The operations for configuring the set of containers also include: The initialization container is configured to be in an event waiting state.
28. The non-transitory computer readable medium of claim 27, wherein: The execution state of the initialization container is the event waiting state, and the operation for changing the execution state of the initialization container further includes: According to the detection of the network event, causing the initialization container to exit the event waiting state; and Further based on the initialization container exiting the event waiting state, starting the execution of the second instance of the containerized application.
