Containerized Service Manager Isolating Critical Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computing systems that require functional safety, critical applications cannot be interfered with by less critical applications to prevent failures that could cause injury or damage.
Innovation Solution
Implementing a kernel-based operating system with service and system managers that use containers to isolate critical and less critical applications during the boot process, creating a restricted container environment where less critical applications run, preventing interference with critical applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple applications run in the same computing system without isolation, then resource utilization improves, but interference between critical and less critical applications occurs
Solution Approach 1:
The computing system is segmented into multiple isolated environments using containerization technology. Critical applications run in a first environment while less critical applications run in a second environment, allowing resource sharing at the system level while preventing interference through environmental isolation. The segmentation is implemented through separate namespace contexts that divide system resources into distinct allocable sets.
Solution Approach 2:
A service manager acts as an intermediary between the host operating system and containerized applications. It manages the creation, configuration, and lifecycle of container environments, allocating resources appropriately to each application type while maintaining isolation boundaries. The service manager coordinates resource distribution without allowing direct interference between applications.
2Device complexity
If critical and less critical applications share the same environment, then system complexity decreases, but critical applications may be interfered with by less critical applications
Solution Approach 1:
The system divides the execution environment into segmented containers with defined boundaries. Critical applications are isolated in protected environments while less critical applications run in separate containers, preventing harmful interference while maintaining a unified system architecture. The segmentation creates logical separation without requiring physical system duplication.
Solution Approach 2:
Different quality levels of isolation are applied to different application types. Critical applications receive enhanced protection with stricter isolation boundaries, while less critical applications operate with standard containerization. This local differentiation of isolation quality allows appropriate protection levels without uniformly complicating the entire system.
Data Source
AI summary
A computing device executing a kernel-based operating system, during a boot process of the operating system, can start a first system and service manager that is configured to start processes from unit files stored in a predetermined directory on a first root volume. The computing device can start, by the first system and service manager, a process from a first unit file that causes generation of a first restricted container environment that includes a second system and service manager, and a second root volume can be mounted to the first restricted container environment. The computing device can start, by the second system and service manager, a process from a second unit file stored in a predetermined directory on the second root volume and the process can execute inside the first restricted container environment.