Upgrade Infrastructure Integration Points Dynamic Callbacks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems lack a specific infrastructure or framework for coordinating the upgrade of different components during a non-disruptive upgrade (NDU), leading to potential runtime errors, upgrade collisions, and complex dependencies between software versions.
Innovation Solution
The implementation of defined upgrade integration points within an upgrade infrastructure or framework, which guides the upgrade process by associating these integration points with specific workflow processing points, allowing for dynamic injection of upgrade tasks and rollback processing, thereby simplifying the upgrade process and managing dependencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If an upgrade infrastructure framework with defined integration points is implemented, then the reliability of the upgrade process is improved by reducing runtime errors and managing dependencies, but the device complexity increases due to the structured framework and workflow processing points
Solution Approach 1:
The upgrade process is divided into discrete integration points (e.g., pre-upgrade, during-upgrade, post-upgrade) with associated workflow processing points. Each integration point handles specific upgrade tasks independently, making the complex upgrade process manageable and reliable through segmented control.
Solution Approach 2:
The upgrade infrastructure framework acts as an intermediary layer between the upgrade workflow and the actual code entities. It dynamically determines and invokes appropriate code entities at each integration point, coordinating upgrades across multiple components without requiring direct complex interactions between them.
2Adaptability or versatility
If dynamic determination of code entities at runtime is performed, then the adaptability of the upgrade process is improved by allowing flexible invocation of customized processing, but the ease of operation deteriorates due to the complexity of dynamic code entity selection and invocation
Solution Approach 1:
Code entities are pre-registered and associated with specific integration points before the upgrade process executes. The upgrade infrastructure framework maintains a predefined mapping between integration points and available code entities, enabling runtime determination without requiring complex dynamic selection logic from operators.
Solution Approach 2:
The upgrade infrastructure framework automatically determines which code entities should be invoked at each integration point based on the upgrade context and workflow state. This self-service mechanism eliminates the need for manual code entity selection while maintaining adaptability to different upgrade scenarios.
Data Source
AI summary
Techniques for performing an upgrade can include: defining integration points, each associated with a workflow processing point of an upgrade workflow of an upgrade infrastructure or framework; and performing processing by code of the upgrade infrastructure or framework that performs the upgrade workflow to upgrade a system, wherein the upgrade includes upgrading a first feature, facility or service of the system from a current version to a new version. The processing can include: dynamically determining, at runtime during execution of the upgrade workflow by the code of the upgrade infrastructure or framework, a set of code entities associated with a first of the integration points; executing code corresponding to workflow processing points, wherein a first of the workflow processing points is associated with the first integration point; and in response to said executing reaching the first workflow processing point, invoking each code entity of the set for upgrade processing.