Container Instance Network Recovery via Progressive Data Recording
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud computing resource management tools, such as OpenStack's Nova, face performance challenges during reboot due to the large inventory of virtual machines they manage, resulting in prolonged downtime and inefficiency.
Innovation Solution
A method that progressively records data modifications to virtual resources or containers in an in-memory resource and writes them to non-volatile storage upon system failure or reboot, enabling rapid recovery by applying these modifications to the hypervisor during reboot.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional cloud computing resource management tools (e.g., OpenStack Nova) are used to manage large inventories of virtual machines, then comprehensive resource management capability is improved, but system reboot time increases significantly
Solution Approach 1:
The patent applies preliminary action by progressively recording data modifications to container instance networks in an in-memory resource before system failure or reboot occurs. This pre-recording of modification data enables the system to rapidly recover and apply changes after reboot without needing to reprocess everything from scratch, thus reducing reboot time while maintaining comprehensive resource management capability.
2Reliability
If all virtual machine data is managed centrally during reboot operations, then complete resource recovery is ensured, but system performance and boot speed deteriorate
Solution Approach 1:
The patent segments the recovery process by separating container instance network data modifications from other virtual machine data. It specifically targets and records modifications to container instance networks in an in-memory resource, allowing this critical subset to be rapidly recovered and applied after reboot. This segmentation enables faster boot speeds while ensuring complete recovery of essential networking resources.
Solution Approach 2:
The patent applies local quality by using an in-memory resource specifically for storing container instance network modification data, rather than treating all data uniformly. This localized approach allows the system to optimize recovery for the most critical networking data while maintaining overall system reliability, thereby improving boot speed without sacrificing recovery completeness.
3Reliability
If data modifications are written to non-volatile storage frequently, then data integrity is improved, but system performance during operation decreases
Solution Approach 1:
The patent implements periodic action by progressively recording data modifications in an in-memory resource and then writing to non-volatile storage based on receiving an indication of system failure or reboot. Rather than continuously writing to non-volatile storage during normal operation, the system accumulates modifications in memory and performs batch writes triggered by specific events, thus maintaining data integrity while preserving system performance during operation.
Data Source
AI summary
A method, computer program product, and system includes a processor(s) progressively recording data modifications to an object (e.g., a virtual resource or a container), in an in-memory resource of the shared computing environment. Based on receiving an indication of a system failure or a system reboot, the processor(s) writes the data modifications to a non-volatile storage resource, where the non-volatile storage resource is readable by an object manager communicatively coupled to the non-volatile storage resource, and where the object manager utilizes the data modifications to recover the object at reboot following the system failure.