Upgrade Infrastructure Integration Points for Non-Disruptive Storage Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems face complexities in performing non-disruptive upgrades (NDUs) due to the need for uninterrupted service and the management of complex dependencies between different software versions, leading to potential runtime errors and instability during the upgrade process.
Innovation Solution
The implementation of defined upgrade integration points within an upgrade infrastructure framework that guides the upgrade process, allowing for customized processing and rollback/recovery mechanisms to manage feature, facility, or service upgrades across a data storage system, ensuring high availability and minimizing downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If non-disruptive upgrades are performed to maintain uninterrupted service, then system availability is improved, but upgrade complexity and risk of runtime errors increase
Solution Approach 1:
The upgrade process is divided into distinct integration points (pre-upgrade, upgrade, post-upgrade phases) with defined workflow processing points at each stage. This segmentation allows the system to manage complexity by handling upgrades in controlled increments rather than as a monolithic process, enabling uninterrupted service while reducing runtime errors through staged execution.
Solution Approach 2:
The system performs preliminary actions by defining integration points and executing pre-upgrade workflows before the actual upgrade occurs. This includes preparing the system state, validating dependencies, and setting up rollback mechanisms in advance, which reduces risks during the upgrade while maintaining system availability.
2Adaptability or versatility
If customized processing is implemented for each upgrade task, then upgrade flexibility and adaptability are improved, but system complexity increases
Solution Approach 1:
The upgrade infrastructure provides a universal framework with standardized integration points and workflow processing points that can accommodate customized processing for different upgrade tasks. The system uses a common architecture with configurable code entities that perform specialized functions, allowing flexibility without proportionally increasing overall system complexity.
Solution Approach 2:
The patent introduces intermediary components including the upgrade infrastructure framework, workflow processing points, and code entities that act as mediators between upgrade tasks and the core system. These intermediaries handle the complexity of customized processing while presenting a simplified interface to the overall system, enabling adaptability without direct complexity propagation.
3Productivity
If multiple code entities are invoked for customized processing, then processing capability is improved, but risk of runtime failures increases
Solution Approach 1:
The system implements feedback mechanisms through defined integration points that monitor the execution state of multiple code entities. The workflow processing points track progress and detect failures, enabling the system to respond to runtime conditions by executing rollback procedures or adjusting execution flow, thereby maintaining stability while utilizing multiple processing entities.
Solution Approach 2:
The patent employs beforehand cushioning by establishing rollback mechanisms and error handling procedures at each integration point before executing customized processing. This preparatory protection allows the system to safely invoke multiple code entities for enhanced processing capability while having pre-configured safeguards to mitigate runtime failures.
Data Source
AI summary
Techniques for performing an upgrade can include: defining integration points each associated with a workflow processing point included in an upgrade workflow; receiving command lists each include commands of an integration point; associating each command of a command list with a code entity; performing processing that performs an upgrade workflow to upgrade a system, wherein the processing includes: executing code corresponding to the upgrade workflow, wherein a workflow processing point of the workflow is associated with a first integration point; and in response to said executing reaching the workflow processing point corresponding to the first integration point, performing second processing including: executing commands of a command list associated with the first integration point; and for each command executed, invoking a corresponding code entity that performs customized processing in connection with upgrading a first feature, facility or service in the system.