Compute Instance Migration with Parallel Copying

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Customers using legacy compute instances are hesitant to migrate to newer types due to concerns about downtime and potential service disruptions during the transition process, which can be time-consuming and inefficient.

Innovation Solution

A compute instance migration system that allows customers to switch from one compute instance type to another while minimizing downtime and ensuring a seamless user experience, by copying data from local to remote block-based storage and converting server images as needed, thereby enabling the use of more powerful or efficient compute resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If customers migrate from legacy compute instances to newer types, then computing efficiency and cost savings are improved, but downtime and service disruption increase

Engineering Contradiction:
Improvecomputing efficiencyVSAvoidservice availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by creating a copy of the legacy compute instance and migrating it to the new compute instance type before the original instance is decommissioned. This includes copying block-based storage resources and converting server images in advance, ensuring the new instance is ready and tested before switching over, thereby minimizing service disruption and downtime.

Inventive Principle:
Principle #10Preliminary action

2Loss of energy

If compute instances are migrated to newer types, then cost efficiency is improved, but migration time and complexity increase

Engineering Contradiction:
Improvecost efficiencyVSAvoidmigration time
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The system creates a copy of the legacy compute instance and migrates it to the new compute instance type. This copying approach allows parallel operation of old and new instances, enabling validation and testing before full migration, thereby reducing overall migration time and complexity while ensuring cost efficiency through newer, more efficient hardware.

Inventive Principle:
Principle #26Copying

3Power

If compute instances are migrated to newer types, then computing performance is improved, but service disruption increases

Engineering Contradiction:
Improvecomputing performanceVSAvoidservice disruption
Core Design Contradiction:
PowerVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by creating and configuring the new compute instance with copied storage resources and converted server images before decommissioning the legacy instance. This allows validation of the new instance's performance and functionality, ensuring computing performance improvement while minimizing service disruption through a controlled transition.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If migration process is simplified, then ease of operation is improved, but migration completeness may be compromised

Engineering Contradiction:
Improvemigration simplicityVSAvoidmigration completeness
Core Design Contradiction:
Ease of operationVSManufacturing precision

Solution Approach 1:

The system copies block-based storage resources and converts server images during the migration process, ensuring data integrity and completeness. This automated copying approach simplifies the migration operation for customers while maintaining migration completeness through systematic resource replication and validation.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10728169B1Instance upgrade migration
Publication Date: 2020.07.28 AMAZON TECH INC
  • US10728169B1 patent drawing
  • US10728169B1 patent drawing
  • US10728169B1 patent drawing

AI summary

A system comprising a computing node comprising a processor and a non-transitory memory and an application stored in the non-transitory memory. When executed by the processor, the application causes the processor to receive an input requesting that a first compute instance of a first compute instance type be instantiated as a second compute instance of a second compute instance type, where a mix of compute resources associated with the second compute instance type is different from a mix of compute resources associated with the first compute instance type; create the second compute instance of the second compute instance type based on the first compute instance; deactivate the first compute instance; and instantiate the second compute instance.