Cloud Migration Orchestrator for Server Application Version Upgrades

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual migration of server applications between servers is complex and not feasible, especially when multiple software components are involved, such as monitoring servers and agents running on different endpoints, making it difficult to upgrade and modify server and agent applications efficiently.

Innovation Solution

A cloud-based Migration as a Service (MaaS) system and a migration orchestrator service automate the migration of server applications between servers by providing an application migration component that includes server, configuration, and data migration components, along with an agent migration component to upgrade corresponding agent applications, facilitating seamless version changes and rollback processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual migration of server applications is performed, then migration can be completed, but the process becomes complex and not feasible when multiple software components are involved

Engineering Contradiction:
Improveautomation of migration processVSAvoidcomplexity of migration process
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent introduces a migration orchestrator service as an intermediary component that coordinates the migration process between the source and target servers. This orchestrator manages the complex interactions between multiple software components (server applications, agent applications, configuration files) by providing a centralized control mechanism that automates the migration steps, thereby reducing manual intervention complexity while maintaining comprehensive control over the migration process.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The migration process is segmented into distinct components: server application migration, agent application migration, configuration migration, and data migration. Each component is handled by a specialized migration module within the orchestrator, allowing the complex overall process to be broken down into manageable, automated segments that can be executed independently and coordinated systematically.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If server applications are migrated between servers with version changes, then new features and security improvements can be incorporated, but ensuring version compatibility and seamless operation becomes difficult

Engineering Contradiction:
Improveversion compatibilityVSAvoidseamless operation during migration
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The migration orchestrator performs preliminary actions by first assessing the source server configuration, identifying compatible target server versions, and preparing the migration environment before actual migration begins. This includes validating version compatibility between server and agent applications, pre-configuring the target server, and preparing rollback mechanisms in advance, thereby ensuring reliability during the migration process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the migration orchestrator continuously monitors the migration process, validates version compatibility at each step, and adjusts the migration plan based on real-time status. If compatibility issues are detected during migration, the system provides feedback to halt the process and initiate rollback procedures, ensuring that version compatibility is maintained and operational reliability is preserved.

Inventive Principle:
Principle #23Feedback

3Productivity

If multiple software components (server and agent applications) are migrated simultaneously, then the process is comprehensive, but coordination and synchronization become extremely complex

Engineering Contradiction:
Improvecomprehensiveness of migrationVSAvoidcoordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges the migration of multiple software components (server applications, agent applications, configurations, and data) into a single coordinated process managed by the migration orchestrator. Instead of handling each component separately, the orchestrator combines them into an integrated migration workflow where all components are migrated together in a synchronized manner, improving productivity while managing coordination complexity through centralized control.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The migration orchestrator serves as a universal platform that handles multiple types of software components through a single interface and unified process. It can migrate server applications, agent applications, configuration files, and data simultaneously, providing multi-functionality that consolidates what would otherwise require multiple separate migration tools and processes, thereby improving comprehensiveness without proportionally increasing coordination complexity.

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

Data Source

PatentUS11089098B2Migration as a service-based server and agent applications migration
Publication Date: 2021.08.10 VMWARE INC
  • US11089098B2 patent drawing
  • US11089098B2 patent drawing
  • US11089098B2 patent drawing

AI summary

In one example, a request to migrate a server application running on a first server to a second server with a change in a version of the server application may be received. Migration information may be provided to a cloud-based Migration as a Service provider based on the request. An application migration component may be received from the cloud-based Migration as a Service provider upon validation of the migration information. The server application may be migrated from the first server to the second server with the change in the version of the server application using the application migration component and the cloud-based Migration as a Service provider. A first version of an agent application in a client may be upgraded with a modified version of the agent application using the application migration component.