Container Storage Optimization via Shared Read-Only Namespace

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing container technologies consume excessive storage resources due to the need for separate namespaces and fully populated files for each container, limiting storage density and efficiency.

Innovation Solution

Implementing a read-only namespace that shares files across multiple containers, using placeholder files and directories within each container's namespace to redirect access and isolate modifications, while loading shared files into a shared memory execution area.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate container namespaces with fully populated files are used for each container, then container isolation and execution reliability are improved, but storage resource consumption increases significantly

Engineering Contradiction:

Improvecontainer execution reliabilityVSAvoidstorage resource consumption

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

Multiple container namespaces share a common read-only namespace that contains fully populated files. The placeholder files in individual container namespaces point to files in the shared read-only namespace, allowing multiple containers to share the same file data while maintaining namespace isolation. This merging approach reduces storage consumption while preserving container reliability.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

Placeholder files serve as intermediaries between container namespaces and the shared read-only namespace. When a container needs to access a file, the placeholder file redirects the access to the corresponding file in the shared read-only namespace. This intermediary mechanism enables storage sharing while maintaining the illusion of separate namespaces for each container.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Quantity of substance

If shared read-only namespace is used across multiple containers, then storage density is improved, but container isolation capability is reduced

Engineering Contradiction:

Improvestorage densityVSAvoidcontainer isolation capability

Core Design Contradiction:

Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The namespace is segmented into two distinct parts: a shared read-only namespace containing fully populated files, and individual container namespaces containing placeholder files. This segmentation allows the system to simultaneously achieve storage density through sharing and isolation through separate namespace structures. Each container maintains its own namespace boundary while sharing underlying file data.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Different parts of the namespace structure have different qualities: the read-only namespace provides shared, read-only access to fully populated files for storage efficiency, while individual container namespaces provide isolated, writable access through placeholder files. This local quality differentiation enables both high storage density and maintained container isolation where needed.

Inventive Principle:

Principle #3Local quality

3Quantity of substance

If placeholder files are created in container namespace to redirect to shared files, then storage resource consumption is reduced, but system complexity increases

Engineering Contradiction:

Improvestorage resource consumptionVSAvoidsystem complexity

Core Design Contradiction:

Quantity of substanceVSDevice complexity

Solution Approach 1:

The system automatically manages placeholder file creation and file redirection without requiring manual intervention. When a container is created or files are accessed, the system automatically creates placeholder files in the container namespace that point to the appropriate files in the shared read-only namespace. This self-service approach reduces storage consumption while minimizing the operational complexity burden on users.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS10140461B2Reducing resource consumption associated with storage and operation of containers

Publication Date: 2018.11.27 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

The techniques and systems described herein reduce the amount of storage resources consumed by containers by creating placeholder files in container namespaces. The placeholder files are associated with read-only access to corresponding shared files stored in a read-only namespace. The read-only namespace can be accessible to multiple different containers. This increases the storage density for a storage unit because more containers can be executed from the same storage unit. The techniques and systems described herein further reduce the amount of storage resources consumed by containers by creating placeholder directories. The techniques and systems described herein also reduce the amount of memory storage resources consumed by containers to execute files by using a shared execution memory area.