Containerized Cluster Snapshot Recovery for Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In software testing, recovering from a non-operational state or reverting to a previous version of a containerized cluster is complex and time-consuming, requiring re-provisioning of the cluster, which can take over an hour, limiting the number of upgrade versions that can be tested.
Innovation Solution
A method for recovering a containerization platform cluster by initiating individual snapshots of each computing node upon initialization, allowing for the saving of different versions of the platform, and enabling revertion to a previous version quickly, either manually or automatically, using these snapshots.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If re-provisioning is used to recover from a non-operational state or revert to a previous version, then the cluster can be restored, but the process takes over an hour and is complex
Solution Approach 1:
The system creates snapshots of the cluster state at predetermined points during initialization and operation. These snapshots are stored in advance, so when recovery is needed, the system can quickly restore to a previous state without performing time-consuming re-provisioning operations. The snapshot mechanism prepares recovery data beforehand, enabling fast restoration.
Solution Approach 2:
The invention creates and stores copies of the cluster state through snapshots. Instead of re-provisioning the entire cluster from scratch during recovery, the system copies the saved snapshot data back to restore the cluster to a previous operational state. This copying approach is much faster than re-provisioning.
2Adaptability or versatility
If re-provisioning is performed to test multiple upgrade versions, then different versions can be tested, but the process is time-consuming and limits the number of versions that can be tested
Solution Approach 1:
The system captures snapshots at different upgrade versions during the initialization and testing process. These snapshots are stored in advance, allowing rapid switching between different version states for testing purposes. This eliminates the need to re-provision the cluster for each version test, significantly increasing testing throughput.
Solution Approach 2:
The snapshot mechanism creates copies of the cluster at different upgrade versions. Testers can quickly switch between these copied states to evaluate multiple versions without performing time-consuming re-provisioning operations, thereby increasing the number of versions that can be tested within a given time frame.
3Reliability
If manual or automated re-provisioning is used for cluster recovery, then the cluster can be restored, but the complexity of handling recovery increases
Solution Approach 1:
The system implements automated snapshot creation and restoration capabilities that reduce the need for manual intervention in cluster recovery processes. The snapshot mechanism automatically captures cluster states and can restore them without complex manual re-provisioning operations, simplifying the recovery process while maintaining reliability.
Data Source
AI summary
A method includes deploying a containerized execution environment on a cluster of virtual machines and performing a snapshot on each virtual machine in the cluster of virtual machines to save a first version of the containerized execution environment on the cluster. The method further includes performing a test on the containerized execution environment and reverting each virtual machine of the cluster of virtual machines to the first version of the cluster saved by the snapshot in view of the test.