Virtual System Run-Level Transition for Maintenance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During maintenance of a virtual system (vSystem), active user sessions and applications can disrupt the process, leading to operational errors, system failures, and data loss due to incompatible versions or incomplete upgrades.
Innovation Solution
A controller manages the transition of the vSystem from a running to a maintenance run-level by terminating appropriate applications and user sessions, and restricting access to ensure only administrators can access the system during maintenance, thereby preventing disruptions and ensuring smooth maintenance processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the vSystem allows active user sessions and applications during maintenance, then system availability and user access are maintained, but maintenance operations are disrupted causing operational errors and system failures
Solution Approach 1:
The system performs preliminary actions by terminating applications and user sessions before maintenance operations begin. The controller identifies and stops running applications, then terminates associated user sessions in advance, ensuring the system is in a clean state before maintenance starts, which prevents disruptions during critical maintenance tasks
Solution Approach 2:
The system segments the operational state into distinct phases: normal operation mode and maintenance mode. During maintenance mode, the system separates maintenance operations from user operations by restricting access and terminating non-essential applications, allowing maintenance to proceed without interference from user activities
2Reliability
If the vSystem terminates applications and user sessions during maintenance, then maintenance operations proceed without disruption, but system functionality and user access are reduced
Solution Approach 1:
The system extracts and removes interfering elements (applications and user sessions) from the system during maintenance. The controller identifies applications that are not required for maintenance operations and terminates them, along with their associated user sessions, thereby eliminating potential sources of disruption while maintaining essential maintenance functionality
Solution Approach 2:
The system dynamically adjusts its operational state based on the maintenance phase. During maintenance, the system terminates applications and restricts user sessions to ensure maintenance completion. After maintenance succeeds, the system dynamically restores full functionality by allowing applications to restart and user access to be resumed
3Reliability
If the vSystem restricts access to administrators only during maintenance, then unauthorized disruptions are prevented, but user access and system usability are limited
Solution Approach 1:
The system applies different access control policies to different user roles during maintenance. Administrators maintain full access to perform and monitor maintenance operations, while regular user access is restricted or terminated. This localized differentiation of access rights ensures maintenance security while allowing necessary administrative functions to proceed
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for transitioning virtual systems from one run-level to a next run-level. In an embodiment, a controller may receive a run-level request to transition a computing cluster (e.g., vSystem) from a first run-level to a second run-level. The controller persists a current run-level of the computing cluster as the second run-level in a configuration file. The controller executes a set of actions corresponding to the second run-level to transition the computing cluster from the first run-level to the second-level. A gateway of the computing cluster receives a request to access the computing cluster. The request includes a user's authentication details. The gateway grants or restricts access to the computing cluster based on the type of user attempting to access the computing cluster and the current run-level of the computing cluster as indicated in the configuration file.