Process Containers Isolate Software Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software update processes can inadvertently impact ongoing production processes due to scripts that may shut down, modify, or interfere with running instances, even when using Dynamic Root Disk (DRD) software, which aims to minimize downtime.
Innovation Solution
The use of process containers to isolate installation processes from production processes, preventing scripts from detecting, stopping, or modifying production processes during updates, thereby ensuring uninterrupted operation of production processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If Dynamic Root Disk software is used to update software while production processes continue running, then downtime is minimized, but production processes can still be inadvertently impacted by installation scripts
Solution Approach 1:
The system is divided into two separate process spaces: production processes and installation processes. This segmentation prevents installation scripts from interfering with production processes while allowing updates to proceed. The production processes continue running in their original process space, while installation scripts execute in an isolated process space, eliminating the risk of unintended interference.
Solution Approach 2:
A process space isolation mechanism acts as an intermediary between installation scripts and production processes. This intermediary prevents direct interaction that could cause harm, while still allowing the installation to proceed. The isolation mechanism ensures that scripts cannot detect, stop, or modify production processes, thereby protecting system reliability during updates.
2Ease of operation
If production processes are shut down during software updates, then installation scripts can execute without interference, but downtime increases and productivity decreases
Solution Approach 1:
The system separates production processes and installation processes into distinct process spaces. This allows installation scripts to execute freely in their isolated environment without needing to shut down production processes. The segmentation enables both installation execution and production continuity to coexist without conflict.
Solution Approach 2:
Production processes continue to run continuously during the software update process. The isolation mechanism ensures that installation activities do not interrupt production operations, maintaining continuous useful action in the production environment while updates proceed in the isolated process space.
3Ease of manufacture
If installation scripts are allowed to access running processes, then scripts can perform necessary modifications, but production processes risk being stopped or modified unintentionally
Solution Approach 1:
The system divides the computer processes into separate process spaces: production processes in one space and installation processes in another. This segmentation prevents installation scripts from accessing or interfering with production processes while still allowing updates to be installed. Each process space operates independently, eliminating unintended interference.
Solution Approach 2:
The process space isolation mechanism serves as an intermediary that blocks harmful interactions between installation scripts and production processes. This intermediary prevents scripts from detecting, stopping, or modifying production processes, thereby eliminating unintended harmful factors while allowing necessary update installations to proceed.
Data Source
AI summary
Process containment is used to block at least some communications between installation processes and production processes.