Container Storage Driver Snapshot Cloning for Startup Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Container startup times are slow due to file-system provisioning bottlenecks, which hinder instant scalability, frequent rebalancing of nodes, rapid software upgrades, and interactive development, despite being lightweight alternatives to hypervisor-based virtualization.
Innovation Solution
Implementing a containerization storage driver that utilizes snapshot and clone capabilities, such as those provided by Tintri's VMstore, to reduce network I/O by lazily pulling image data and using snapshot identifiers instead of full data, along with lazy cloning and caching techniques to optimize container creation and distribution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional file-system provisioning methods are used to initialize containers, then containers receive complete file systems with all necessary components, but container startup time increases significantly (median 25 seconds)
Solution Approach 1:
The patent pre-provisions storage resources and creates storage templates in advance before containers are actually needed. By preparing the storage infrastructure beforehand with all necessary file system structures, templates, and configurations, the system eliminates the time-consuming file system provisioning step during container startup, reducing latency from 25 seconds to near-instantaneous activation.
Solution Approach 2:
The patent uses storage templates that can be rapidly copied and instantiated for multiple containers. Instead of creating complete file systems from scratch for each container, the system uses pre-defined templates that can be quickly replicated, providing complete file systems without the overhead of traditional provisioning methods.
2Reliability
If complete file systems are copied over the network for each container, then containers have all necessary application binaries and dependencies, but network I/O and storage requirements increase
Solution Approach 1:
The patent extracts the file system provisioning step from the container startup process. By separating file system preparation (done in advance as templates) from container activation (instantaneous), the system eliminates the need to copy complete file systems over the network at startup, reducing network I/O while maintaining full application functionality through pre-prepared storage templates.
3Reliability
If traditional container distribution methods are used, then containers can be deployed with complete file systems, but storage provisioning time and costs increase
Solution Approach 1:
The patent performs storage provisioning and file system template creation in advance, before containers are deployed. This preliminary preparation ensures that all storage resources are ready and configured beforehand, allowing containers to be instantiated immediately without waiting for storage setup, thus reducing deployment time while maintaining container readiness.
Solution Approach 2:
The patent uses pre-created storage templates that can be rapidly copied and assigned to containers. Instead of provisioning storage dynamically for each container deployment, the system copies references to pre-prepared templates, dramatically reducing storage provisioning time and enabling faster container distribution.
Data Source
AI summary
Storage system accelerated techniques to distribute and run containerized applications are disclosed. In various embodiments, an indication to run a container is received. A snapshot identifier comprising an image data associated with the container is used to create a clone based on a snapshot with which the snapshot identifier is associated. The clone is used to store data associated with at least a topmost layer of the container.