Overlay Optimizer for Application Deployment Without Reboot
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing write filter technologies, such as Unified Write Filter (UWF) and File Based Write Filter (FBWF), require rebooting the client terminal to install, update, or reconfigure applications, which is a tedious and time-consuming process, even for minor changes.
Innovation Solution
An overlay optimizer is used to manage I/O requests, allowing for the creation of a session overlay to redirect and store changes during the deployment of a package without disabling the write filter, enabling the installation, update, or reconfiguration of applications without rebooting the system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the write filter is enabled to prevent modifications to the protected volume, then the operating system image is protected from being changed at runtime, but the installation, update, or reconfiguration of applications requires disabling the write filter and rebooting the system
Solution Approach 1:
The patent segments the overlay storage into multiple separate overlays (first overlay and second overlay) that can be independently managed. This allows the write filter to protect the protected volume while enabling application installation by directing writes to appropriate overlays without requiring system-wide disabling of the write filter or rebooting.
Solution Approach 2:
The patent introduces an intermediary mechanism (the overlay manager and multiple overlays) between the write filter and the protected volume. This intermediary layer enables application installation and configuration by temporarily utilizing the second overlay for package deployment while the write filter remains enabled, eliminating the need to disable the write filter or reboot the system.
2Ease of operation
If the write filter is disabled to install or update applications, then application deployment can proceed, but the system must be rebooted to re-enable the write filter
Solution Approach 1:
By segmenting overlay storage into multiple independent overlays, the system allows application deployment to occur in the second overlay while the write filter remains enabled and the first overlay continues to function. This eliminates the need to reboot the system to switch overlay states or re-enable the write filter.
Solution Approach 2:
The patent enables continuous operation of the write filter and protected volume while application installation proceeds in the second overlay. The write filter remains enabled throughout the deployment process, maintaining continuous protection of the operating system image without interruption or reboot.
3Device complexity
If a single overlay is used to store write redirections, then the write filter functions simply, but the overlay may become full during application installation requiring write filter disabling
Solution Approach 1:
The patent divides the overlay storage into multiple segments (first overlay and second overlay) that can be independently managed. This segmentation allows the system to handle large application installations by utilizing multiple overlays instead of a single overlay, preventing any single overlay from becoming full and requiring write filter disabling.
Solution Approach 2:
The patent changes the parameter of overlay capacity by introducing multiple overlays with different size configurations. This allows the system to accommodate large application packages by distributing writes across multiple overlays, thereby maintaining adequate free space in each overlay without requiring disabling of the write filter.
Data Source
AI summary
An application can be installed, updated or reconfigured without disabling a write filter. When a package is to be deployed to a client terminal to install, update or reconfigure an application, an overlay optimizer can be instructed to start a session. During the session, the overlay optimizer can analyze I/O requests to identify any I/O request that pertains to the deployment of the package. The overlay optimizer can then redirect the identified I/O requests to a session overlay that the overlay optimizer has created for the session rather than passing the I/O requests to the write filter. As a result, the artifacts that are affected by the deployment of the package will be stored in the session overlay rather than the write filter's overlay. Once the session is completed, the overlay optimizer can copy the artifacts from the session overlay to the write filter's overlay and commit them.