Host Isolation Manager for Cloud Resource Capacity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing the removal of computing resources from service in a web-based computing system without disrupting service to users is challenging, as it affects computing capacity and resource availability, especially when resources degrade or need maintenance, upgrades, or when newer resources are introduced.

Innovation Solution

Implementing an isolation manager that analyzes the provider network to determine whether removing a computing device or host from service will impact computing capacity, by evaluating demand and supply of resource instances across different pools and availability zones, and making informed decisions to grant or deny requests based on capacity needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If computing resources are removed from service for maintenance or upgrades, then resource reliability and system health are improved, but computing capacity and service availability deteriorate

Engineering Contradiction:
Improveresource reliabilityVSAvoidcomputing capacity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The isolation manager performs preliminary analysis before removing resources from service. It evaluates demand and supply metrics, identifies isolated resources that can be removed without impacting user workloads, and prepares migration plans in advance. This allows maintenance activities to be scheduled proactively while ensuring service continuity through pre-planned resource redistribution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The isolation manager acts as an intermediary between resource maintenance needs and user workload requirements. It analyzes the provider network to identify which resources can be isolated for maintenance without affecting users, and which resources must remain online to support active workloads. This mediation enables selective maintenance that preserves computing capacity where needed.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If computing resources are removed from service, then resource availability for maintenance is improved, but service continuity to users deteriorates

Engineering Contradiction:
Improveresource availability for maintenanceVSAvoidservice continuity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The isolation manager applies different maintenance strategies to different resources based on their local characteristics and workload dependencies. It identifies isolated resources that can be taken offline for maintenance without affecting any users, while keeping critical resources online. This localized approach allows maintenance activities on non-critical resources while preserving service continuity on critical resources.

Inventive Principle:
Principle #3Local quality

3Reliability

If resource instances are distributed across multiple pools and availability zones, then service continuity is improved, but system complexity increases

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

Solution Approach 1:

The isolation manager continuously monitors resource usage, demand, and supply metrics across pools and availability zones. It uses this feedback to dynamically identify isolated resources that can be removed without impacting service continuity. The system adjusts its isolation decisions based on real-time conditions, enabling complex multi-zone architectures to be managed automatically without proportionally increasing operational complexity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10164897B1System and method for host isolation in a web-based computing system
Publication Date: 2018.12.25 AMAZON TECH INC
  • US10164897B1 patent drawing
  • US10164897B1 patent drawing
  • US10164897B1 patent drawing

AI summary

A method for removing computing assets from service in a provider network includes receiving, from a requestor, identification for selected ones of the computing assets requested to be removed from service. Each of the computing assets is a computing device or a slot of a computing device. A pool in which each of the computing assets requested to be removed from service is located is identified. For each identified pool: which of the computing assets requested to be removed from service is approved for removal from service is determined based on a number of resource instances available for allocation to users after the computing devices are removed from service exceeding a predetermined number of resource instances. The requestor is notified as to which of the computing assets is approved for removal from service.