Containerized Automation Apps With Kernel-Mode Software Loading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current container technologies cannot effectively encapsulate applications that require kernel-mode software due to limitations in abstracting kernel-mode software, leading to the need for resource-intensive traditional OS virtualization, which is costly and inefficient.
Innovation Solution
A method where a host extender loads and integrates kernel-mode software from a database into the automation system's kernel based on metadata, allowing kernel-mode software to be packaged within containers, and manages compatibility to avoid incompatibilities, dynamically creating virtual machines if needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional OS virtualization is used to encapsulate applications requiring kernel-mode software, then the application can be executed, but resource consumption increases significantly and distribution becomes costly
Solution Approach 1:
The system segments the virtualization approach by separating container management from kernel-mode software management. The host extender component specifically handles kernel-mode software installation and configuration, while the container runtime manages application execution. This segmentation allows lightweight containerization for user-mode applications while providing on-demand kernel-mode support only when needed, reducing overall resource consumption compared to full VM virtualization.
Solution Approach 2:
The host extender acts as an intermediary component between the container runtime and the host operating system kernel. It mediates the installation, loading, and configuration of kernel-mode software modules when containers require them, enabling seamless integration without requiring full OS virtualization. This intermediary approach maintains the efficiency of container technology while adding the necessary kernel-mode capabilities.
2Use of energy by moving object
If container technology is used for lightweight virtualization, then resource efficiency is improved, but kernel-mode software cannot be packaged in containers
Solution Approach 1:
The system performs preliminary actions by pre-installing and pre-configuring kernel-mode software modules on the host system before container execution. The host extender proactively manages the availability of required kernel-mode drivers and modules, so when a container needs them, they are already present and can be loaded efficiently. This preliminary preparation eliminates the need for full VM bootstrapping while maintaining the ability to run kernel-mode applications.
Solution Approach 2:
The host extender implements self-service mechanisms by automatically detecting when a container requires kernel-mode software, locating the appropriate modules from local or remote repositories, installing them, and configuring them for the specific container's needs. This automated self-service approach enables the system to dynamically adapt to kernel-mode requirements without manual intervention or full virtualization overhead.
3Adaptability or versatility
If kernel-mode software is installed locally on the automation system, then application execution is enabled, but system compatibility issues may arise
Solution Approach 1:
The system applies local quality by installing and configuring specific kernel-mode software modules locally on the host system based on the specific requirements of each container. Rather than installing generic kernel-mode software, the host extender identifies the exact drivers and modules needed for each application and configures them with appropriate parameters. This localized, demand-driven approach ensures compatibility while maintaining system stability.
Solution Approach 2:
The host extender manages parameter changes by dynamically adjusting kernel-mode software configuration parameters based on container requirements. It can modify driver parameters, module loading options, and system configuration settings to ensure compatibility between the containerized application and the host system. This parameter-based adaptability allows the system to accommodate different applications without compromising overall system stability.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
The invention relates to a method for operating an automation system and automation system operating according to the method, wherein an application (16) to be executed on the automation system is available in an encapsulated form in a container (14) and wherein in the event that the application (16) encapsulated in the container (14) requires kernel mode software (22), a host extender (30) executed on the automation system uses metadata (32) included in the container (14) to load the required kernel mode software (22) from a database (34) having kernel mode software (22) and install said software locally on the automation system, wherein the host extender (30), in the event of an identified incompatibility on the automation system, installs a virtual machine (26), loads the container (14), which led to the incompatibility, onto the virtual machine (26) and loads the kernel mode software (22) required by the application (16) contained by the container (14) into the kernel (38) of the virtual machine (26).