Plugin Wrapper for Container Driver Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing container orchestration systems require manual configuration of driver plugins for new container deployment models, which is inefficient and complex, especially when deploying containers to unsupported environments like virtual machines.
Innovation Solution
A plugin wrapper intercepts and modifies allocation requests to match the specifications of unsupported container deployment models, allowing existing driver plugins to allocate resources to containerized applications without manual modification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If driver plugins are manually configured for new container deployment models, then compatibility with unsupported environments is achieved, but operational complexity and time consumption increase
Solution Approach 1:
The patent introduces a wrapper plugin as an intermediary layer between the container orchestration system and the driver plugin. This wrapper intercepts allocation requests, translates them into the appropriate format for unsupported deployment models, and forwards them to the driver plugin. This mediator approach enables compatibility with new container deployment models without requiring modifications to the existing driver plugin code, thereby resolving the contradiction between adaptability and complexity.
2Adaptability or versatility
If driver plugins are manually updated to support new container deployment models, then support for unsupported environments is enabled, but time consumption and operational overhead increase
Solution Approach 1:
The wrapper plugin is pre-configured with knowledge of multiple container deployment models and their specifications. When a new deployment model is introduced, the wrapper automatically adapts by translating allocation requests into the appropriate format, eliminating the need for manual updates. This preliminary preparation of the translation layer resolves the contradiction between adaptability and time consumption.
3Reliability
If existing driver plugins are used without modification, then system stability is maintained, but support for new container deployment models is lost
Solution Approach 1:
The patent segments the system into three distinct layers: the container orchestration system, the wrapper plugin (translation layer), and the existing driver plugin. This segmentation allows each layer to maintain its original functionality while the wrapper layer provides the necessary translation. The driver plugin remains unchanged, preserving system stability, while the wrapper enables support for new deployment models, resolving the contradiction between reliability and adaptability.
Data Source
AI summary
Described are techniques for modifying existing driver plugin behavior using a plugin wrapper to enable driver compatibility with an unsupported container deployment model. The techniques include intercepting, by a plugin wrapper operating as part of a container orchestration system, an allocation request intended for a driver plugin, where the allocation request is for allocating a computing resource to a containerized application deployed using a container deployment model not supported by the driver plugin. The techniques further include modifying, by the plugin wrapper, the allocation request to correspond to specifications of the container deployment model, thereby forming a modified request to allocate the computing resource to the containerized application. The techniques further include sending, by the plugin wrapper, the modified request to the driver plugin to allow the driver plugin to allocate the computing resource to the containerized application using the specifications of the container deployment model.