Host Upgrade Method via Service Group Constraints

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current server upgrade methods in cloud services face inefficiencies due to the need for redundant host configuration and sequential upgrades, which interrupt service continuity and reduce upgrade speed.

Innovation Solution

A host upgrade method that selects target hosts based on service groups or anti-affinity groups, allowing for simultaneous upgrades without migration, by determining the maximum shutdown quantity and maintaining service continuity through load balancing parameters and task scheduling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If live migration technology is used to ensure service continuity during host upgrade, then service continuity is maintained, but upgrade efficiency is reduced due to sequential upgrades and redundant host configuration

Engineering Contradiction:
Improveservice continuityVSAvoidupgrade efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments virtual machines into different service groups with defined maximum shutdown quantities. This allows selective upgrading of hosts based on service group constraints, enabling parallel upgrades across multiple hosts while maintaining required service availability. Instead of upgrading hosts sequentially, multiple hosts can be upgraded simultaneously as long as the shutdown constraints for each service group are satisfied.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically determines upgrade eligibility by evaluating current service group states and maximum shutdown quantities. The upgrade device can adaptively select which hosts to upgrade based on real-time service requirements, allowing flexible parallel upgrading strategies that maintain service continuity while maximizing upgrade throughput.

Inventive Principle:
Principle #15Dynamics

2Reliability

If redundant host configuration is used to maintain service continuity, then service availability is ensured, but system complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Hosts in the system serve multiple functions: they can be actively providing service, standby for failover, or undergoing upgrade simultaneously. The same host pool is used for both service delivery and upgrade operations, eliminating the need for dedicated redundant hosts. The system universally manages all hosts through a unified constraint-based framework that handles service continuity and upgrades without requiring separate redundant infrastructure.

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

Solution Approach 2:

The system uses parameter-based control through maximum shutdown quantities for each service group. By dynamically adjusting these parameters based on service requirements, the system can flexibly manage host availability without hard-coded redundant configurations. This parameter-driven approach simplifies system complexity by replacing physical redundancy with logical constraint management.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If sequential host upgrades are performed to maintain service continuity, then service interruption is avoided, but upgrade time increases

Engineering Contradiction:
Improveservice continuityVSAvoidupgrade time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements periodic parallel upgrade cycles across multiple hosts. Instead of strictly sequential upgrades, hosts are upgraded in periodic batches that respect service group constraints. Multiple hosts can be upgraded in parallel within each cycle, and multiple cycles can run sequentially, significantly reducing total upgrade time while maintaining service continuity through the maximum shutdown quantity constraints.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11886905B2Host upgrade method and device
Publication Date: 2024.01.30 HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
  • US11886905B2 patent drawing
  • US11886905B2 patent drawing
  • US11886905B2 patent drawing

AI summary

A host upgrade method and a device include selecting at least one target host from a plurality of hosts for an upgrade. After the at least one target host is selected, a service running on all virtual machines that are in one or more target service groups and that are deployed on the at least one target host is stopped, and a service running on a virtual machine that is in the one or more target service groups and that is not deployed on the at least one target host is maintained. Then, the at least one target host is upgraded.