SDDC Upgrade Path Management via Version-Compliance Matrix

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing component dependencies and upgrades in a software-defined data center (SDDC) is complex, often leading to decreased efficiency and compatibility issues due to the need for careful administration to avoid breaking system functionality.

Innovation Solution

The implementation of an upgrade-path manifest and version-compliance configuration matrix allows direct upgrades to a desired version, skipping intermediate steps, and provides a mechanism for retracting faulty patches through a graphical user interface and customized upgrade packages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional manual upgrade management is used, then administrators can control the upgrade process, but the complexity of managing component dependencies increases significantly

Engineering Contradiction:
Improveupgrade compatibilityVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically manages upgrade paths and component dependencies without requiring administrator intervention. The SDDC manager autonomously determines upgrade sequences, validates compatibility, and executes upgrades based on predefined policies, eliminating the need for manual dependency management while ensuring system reliability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-calculates and stores multiple upgrade paths before they are needed. By anticipating future upgrade scenarios and pre-validating compatibility matrices, the system prepares upgrade sequences in advance, reducing on-demand complexity and ensuring reliable upgrades when executed

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple intermediate upgrade steps are required, then compatibility between components is maintained, but the upgrade time and administrative workload increase

Engineering Contradiction:
Improvecomponent compatibilityVSAvoidupgrade duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system identifies and executes direct upgrade paths that skip unnecessary intermediate versions. By analyzing the compatibility matrix and component dependencies, the system determines when components can be upgraded directly without requiring intermediate stabilization steps, reducing upgrade duration while maintaining compatibility

Inventive Principle:
Principle #21Skipping (Rushing through)

Solution Approach 2:

The system dynamically adjusts upgrade paths based on real-time system state and component interdependencies. Upgrade sequences are optimized on-the-fly to take the most efficient path while ensuring compatibility constraints are met, balancing speed and reliability adaptively

Inventive Principle:
Principle #15Dynamics

3Measurement precision

If administrators manually manage component dependencies, then upgrade accuracy can be controlled, but the administrative workload becomes overwhelming

Engineering Contradiction:
Improveupgrade control accuracyVSAvoidadministrative ease
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The SDDC manager autonomously performs dependency analysis, compatibility validation, and upgrade execution. The system self-manages the complex task of tracking component relationships and determining safe upgrade sequences, providing precise control without requiring administrator effort

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors system state, component versions, and compatibility constraints during the upgrade process. Real-time feedback mechanisms validate each upgrade step and automatically adjust subsequent actions based on system responses, ensuring precise control while automating the operational burden

Inventive Principle:
Principle #23Feedback

4Stability of the object's composition

If outdated software components are maintained, then system stability is preserved, but security vulnerabilities and functionality gaps increase

Engineering Contradiction:
Improvesystem stabilityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
Stability of the object's compositionVSObject-affected harmful factors

Solution Approach 1:

The system proactively identifies and prepares security patches and updates before they become critical issues. By continuously monitoring for available upgrades and pre-validating their compatibility through the stored upgrade paths, the system can apply updates during planned maintenance windows rather than reacting to security threats

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically balances stability and security by allowing selective upgrading of components based on risk assessment and operational requirements. Critical security patches can be prioritized and applied through validated upgrade paths while non-critical components maintain their stable configurations

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10838712B1Lifecycle management for software-defined datacenters
Publication Date: 2020.11.17 VMWARE INC
  • US10838712B1 patent drawing
  • US10838712B1 patent drawing
  • US10838712B1 patent drawing

AI summary

Examples described herein include systems and methods for efficiently and effectively managing upgrades to an SDDC. More specifically, examples described herein relate to allowing various upgrade paths that can upgrade an SDDC directly to a desired version, without the need for intermediate upgrades. The upgrades can be selected by a user through a graphical user interface (“GUI”) described herein. The examples further describe a version-compliance configuration matrix that identifies various acceptable combinations of software components and versions. The examples also describe a process for providing a customized upgrade package suited to a particular customer or user. Additional examples describe a mechanism for retracting and correcting bad patches or upgrades after they have been released.