Service Domain Upgrade Isolation via Segmented Download

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing software upgrades across multiple service domains in multi-cloud platform as a service systems is challenging due to susceptibility to network connectivity issues, leading to time-intensive or failed downloads and upgrades, and difficulties in handling partial updates.

Innovation Solution

The upgrade process is split into two phases: download and upgrade, with the download phase focusing on downloading only changed files and utilizing secure source locations like AWS S3 and ECR, and the upgrade phase occurring locally, allowing service domains to autonomously handle network issues and upgrade independently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the download and upgrade phases are interleaved, then the upgrade process can be performed continuously, but the upgrade process becomes susceptible to network connectivity failures and environmental issues

Engineering Contradiction:
Improveupgrade process continuityVSAvoidupgrade process reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The upgrade process is divided into two distinct phases: a download phase where upgrade packages are retrieved from remote locations, and an upgrade phase where the downloaded packages are installed locally. This segmentation isolates network dependency to only the download phase, allowing the upgrade phase to proceed reliably without network connectivity requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The download phase is completed in advance before the upgrade phase begins. By pre-downloading and validating upgrade packages during the download phase, the system ensures that all necessary files are available locally before initiating the upgrade, eliminating the risk of network failures during the critical upgrade operation.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple service domains are managed separately, then each service domain can be upgraded independently, but managing upgrades across multiple service domains becomes complex and time-consuming

Engineering Contradiction:
Improveindependent upgrade capabilityVSAvoidupgrade management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The cloud manager implements a universal upgrade management mechanism that can simultaneously coordinate upgrades across multiple service domains. It maintains a centralized state management database tracking all service domains and provides a unified interface for initiating, monitoring, and coordinating upgrades, reducing the complexity of managing multiple independent upgrade processes.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

Multiple individual upgrade operations are merged into a coordinated batch process. The cloud manager aggregates upgrade requests for multiple service domains and executes them in a coordinated manner, allowing simultaneous progress tracking and unified management of upgrades across the entire multi-cloud platform.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If downloads include files from multiple locations, then comprehensive upgrade packages can be obtained, but the download process becomes time-intensive and slows down the upgrade process

Engineering Contradiction:
Improveupgrade package completenessVSAvoiddownload time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-assembling and pre-validating upgrade packages during the download phase. Upgrade packages are prepared in advance with all necessary files from multiple locations already aggregated and validated, so that during the actual upgrade phase, the service domain only needs to extract and install the pre-prepared package rather than downloading from multiple locations in real-time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11726764B2Upgrade systems for service domains
Publication Date: 2023.08.15 NUTANIX INC
  • US11726764B2 patent drawing
  • US11726764B2 patent drawing
  • US11726764B2 patent drawing

AI summary

Non-transitory computer readable media are encoded with instructions which, when executed by one or more processors of a central computing system, cause the central computing system to connect with multiple service domains and determine that at least one service domain of the multiple service domains is eligible for upgrade. The instructions further cause the central computing system to store an upgrade package for the at least one service domain at a storage service separate from the central computing system and communicate access credentials to the storage service to the at least one service domain. The central computing system receives a communication from the at least one service domain indicative of upgrade status responsive to the at least one service domain having accessed the upgrade package at the storage service and updates a state management database based on the communication.