Cloud Server Volume Mount via Sub-Container Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In container-based cloud systems, dynamically adding or deleting volumes is cumbersome, requiring high-level authority and potentially disrupting other applications, and existing solutions lack efficient methods for user-friendly volume management.
Innovation Solution
A cloud server architecture that includes a communicator and processor to manage volume mount requests by generating sub-containers, allowing users to dynamically add or delete volumes without restarting containers, using APIs to control volume access and sharing host volumes securely between containers and sub-containers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a user directly mounts a volume on a container, then volume access is achieved, but high-level authority is required and system complexity increases
Solution Approach 1:
The patent introduces a sub-container as an intermediary component between the user's container and the host volume. The sub-container is created with appropriate privileges and acts as a mediator that handles volume mounting operations, allowing the user's container to access volumes without requiring direct high-level authority. This resolves the contradiction by enabling easy volume mounting while maintaining security through the intermediary sub-container.
Solution Approach 2:
The system segments the container architecture by creating a sub-container within the host that has specific permissions for volume management. This segmentation allows the user's container to remain isolated with limited privileges while the sub-container handles privileged operations, thus enabling ease of operation without compromising system reliability through unauthorized access.
2Adaptability or versatility
If volumes are dynamically added or deleted in container-based systems, then operational flexibility improves, but system stability may be compromised
Solution Approach 1:
The patent implements preliminary action by pre-creating the sub-container with all necessary permissions and configurations before the user needs to mount volumes. This preparation ensures that when dynamic volume operations are needed, they can be executed smoothly without disrupting the container's stability. The sub-container is ready to handle volume mount/unmount operations, providing adaptability while maintaining system stability.
Solution Approach 2:
The sub-container serves as a stable intermediary that handles all dynamic volume operations. By routing volume mount and unmount requests through this pre-established sub-container, the system achieves operational flexibility while the sub-container's stable presence ensures that these dynamic changes do not compromise the overall container runtime stability.
3Reliability
If sub-containers are created for volume management, then volume access control improves, but device complexity increases
Solution Approach 1:
The sub-container is designed as a universal component that can be created for any container that needs volume management. Rather than creating complex custom solutions for each container, the same sub-container pattern is universally applied, providing improved access control through a standardized mechanism. This multi-functionality approach reduces the perceived complexity by using a repeatable pattern rather than unique complex architectures for each case.
Solution Approach 2:
The system implements self-service by automatically creating and managing the sub-container when a container is instantiated with volume requirements. The cloud server automatically handles the sub-container lifecycle, including creation, permission configuration, and cleanup, without requiring manual intervention. This automation reduces device complexity by making the complexity invisible to users while still providing improved volume access control.
4Productivity
If users can dynamically manage volumes without restarting containers, then productivity improves, but security risks increase
Solution Approach 1:
The sub-container acts as a secure intermediary that enables users to dynamically manage volumes without restarting containers. It provides the necessary privileged access for volume operations while isolating the user's container from direct exposure to sensitive host resources. This resolves the contradiction by maintaining productivity through dynamic volume management while reducing security risks through the protective intermediary layer.
Solution Approach 2:
The system applies local quality by giving the sub-container specific, localized privileges only where needed for volume management, rather than granting broad permissions. The sub-container has precise control over which volumes can be mounted and by whom, enabling productivity through dynamic operations while limiting security risks through localized, minimal necessary permissions rather than widespread access.
Data Source
AI summary
A cloud server for providing a container-based cloud service, and a method thereof are provided. The cloud server includes a communicator configured to receive a volume mount request, a memory storing one or more instructions, and a processor configured to execute the one or more instructions stored in the memory to, when the processor receives a volume mount request from a first user of a first container among a plurality of containers, identify the first container, check a volume mount right of the first container, and mount a volume that is mountable on the first container.