Automatically configuring boot sequence of container systems for disaster recovery
Embodiments for systems and methods of providing a boot order for containers in a cloud native application environment by collecting container environment data from a first container site; determining dependencies and connections between the containers and applications executed within the containers based on a number of system parameters; calculating a recommended order for booting or rebooting the containers during a disaster recovery process; and communicating the recommended order to a system administrator through a graphical user interface (GUI) for acceptance or modification by the system administrator.
1. A computer-implemented method of providing a boot order for containers in a cloud native application environment, comprising:
collecting container environment data from a first container site;
determining dependencies and connections between the containers and applications executed within the containers based on a number of system parameters comprising container type, network configuration and traffic, manual restarts of containers, and container management system configuration;
assigning weighting values to each system parameter indicating a relative importance of a parameter relative to other parameters of the system parameters to produce weighted parameters;
calculating a recommended order for booting or rebooting the containers during a disaster recovery process by combining the weighted parameters; and
communicating the recommended order to a system administrator through a graphical user interface (GUI) for acceptance or modification by the system administrator.
2. The method of claim 1 wherein the container type of each container is detected based on application activity, and include containers using or exposing a storage service such as a file system, containers using database services, stateless containers will boot later, and user-exposed containers.
3. The method of claim 1 wherein the network configuration and traffic for each container is determined by automatic detection of dependencies among the containers using network and API (application programming interface) configurations.
4. The method of claim 1 wherein the manual restarts of containers is determined by monitoring the order in which containers are restarted through the use of system logs indicating container operation during normal start and shutdown procedures.
5. The method of claim 1 wherein the container management system configuration is determined through a container management system configuration database.
6. The method of claim 1 wherein a cloud native application environment includes a container management system comprising a Kubernetes system.
7. The method of claim 6 wherein the first site comprises a Kubernetes production site.
8. The method of claim 7 wherein the disaster recovery process comprises writing the data of the containers to target containers of a disaster recovery site coupled to the production site over a network and invoking failover or failback data replication operations in event of failure or compromise of the production site.
9. The method of claim 8 wherein target containers of the disaster recovery site are booted in the recommended order as accepted or modified by the system administrator.
10. A computer-implemented method of providing disaster recovery in a cloud native application environment, comprising:
collecting, from a production site, container environment data comprising container types, network configuration and traffic, manual restarts of containers, and container management system configuration as respective system parameters;
assigning weighting values to each system parameter indicating a relative importance of a parameter relative to other parameters of the system parameters to produce weighted parameters;
determining a recommended order for booting or rebooting the containers during a disaster recovery process based on the collected container environment data by combining the weighted parameters;
writing the data of the containers to target containers of a disaster recovery site coupled to the production site over a network;
invoking a failover or failback data replication operation in event of failure or compromise of the production site; and
booting the target containers of the disaster recovery site in the recommended order.
11. The method of claim 10 further comprising determining dependencies and connections between the containers and applications executed within the containers based on the container environment data.
12. The method of claim 11 further comprising communicating the recommended order to a system administrator through a graphical user interface (GUI) for acceptance or modification by the system administrator.
13. The method of claim 12 further comprising booting the target containers in the recommended order as modified by the system administrator.
14. The method of claim 10 wherein the container management system comprises a Kubernetes system.
15. A system comprising a processor-based executable module configured to provide a boot order for containers in a cloud native application environment, comprising:
a hardware processor-based boot order auto-configurator collecting container environment data from a first container site, determining dependencies and connections between the containers and applications executed within the containers based on a number of system parameters comprising container type, network configuration and traffic, manual restarts of containers, and container management system configuration, assigning weighting values to each system parameter indicating a relative importance of a parameter relative to other parameters of the system parameters to produce weighted parameters, and calculating a recommended order for booting or rebooting the containers during a disaster recovery process by combining the weighted parameters; and
a hardware processor-based recommendation engine coupled to memory storing executable programming instructions and further coupled to the boot order auto-configurator and communicating the recommended order to a system administrator through a graphical user interface (GUI) for acceptance or modification by the system administrator.
16. The system of claim 15 wherein a cloud native application environment includes a container management system comprising a Kubernetes system, and wherein the first site comprises a Kubernetes production site.
17. The system of claim 16 further comprising a disaster recovery component writing the data of the containers to target containers of a disaster recovery site coupled to the production site over a network and invoking failover or failback data replication operations in event of failure or compromise of the production site, and wherein target containers of the disaster recovery site are booted in the recommended order as accepted or modified by the system administrator.
18. The system of claim 17 wherein:
the container type of each container is detected based on application activity, and include containers using or exposing a storage service such as a file system, containers using database services, stateless containers will boot later, and user-exposed containers;
the network configuration and traffic for each container is determined by automatic detection of dependencies among the containers using network and API (application programming interface) configurations;
the manual restarts of containers is determined by monitoring the order in which containers are restarted through the use of system logs indicating container operation during normal start and shutdown procedures; and
the container management system configuration is determined through a container management system configuration database.