Cloud Network Migration Between Multi-Cloud Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Migrating cloud networks between multi-cloud management platforms often results in data and policy loss, leading to manual re-creation of policies, downtime for virtual machines, and increased administrative effort, due to the lack of data transfer and policy implementation in the destination platform.

Innovation Solution

A method for migrating cloud networks that involves receiving a migration request, identifying the cloud network, obtaining management platform information from the source platform, registering and deregistering the network, and transferring management platform information to the destination platform, allowing for seamless data and policy transfer and reducing manual efforts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If cloud networks are migrated between multi-cloud management platforms using conventional methods, then the migration process is simple, but data and policy loss occurs requiring manual re-creation

Engineering Contradiction:
Improveease of migrationVSAvoiddata and policy loss
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The system performs preliminary actions by exporting and storing management platform information (policies and data) from the source platform before migration occurs. This pre-prepared information is then automatically imported to the destination platform, eliminating the need for manual re-creation and preventing information loss during migration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the management platform information including policies and data from the source platform. This copy is then transferred and applied to the destination platform, ensuring that the migrated cloud network retains all necessary configurations without manual intervention.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If cloud networks are migrated between multi-cloud management platforms, then network relocation is achieved, but downtime for virtual machines occurs

Engineering Contradiction:
Improvenetwork relocation capabilityVSAvoidvirtual machine downtime
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by exporting and preparing management platform information before the actual migration. This includes collecting policies and data from the source platform and preparing them for transfer, so that when migration occurs, the destination platform is already configured and ready to immediately assume control, minimizing downtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system ensures continuity by maintaining the availability of management platform information throughout the migration process. The information is exported, stored, and transferred in a continuous workflow that allows the destination platform to be ready immediately upon migration completion, eliminating gaps where virtual machines would be unavailable.

Inventive Principle:
Principle #20Continuity of useful action

3Device complexity

If cloud networks are migrated without automated data transfer, then migration setup is simple, but administrative effort increases due to manual policy re-creation

Engineering Contradiction:
Improvemigration process complexityVSAvoidautomated data transfer
Core Design Contradiction:
Device complexityVSExtent of automation

Solution Approach 1:

The system automates the process by performing preliminary actions of exporting, storing, and preparing management platform information from the source platform. This automated preparation eliminates the need for manual policy re-creation at the destination platform, reducing administrative effort while maintaining manageable system complexity through structured automation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service migration by automatically exporting, transferring, and applying management platform information without requiring manual administrative intervention. The destination platform automatically receives and applies the transferred policies and data, eliminating repetitive manual work while keeping the overall system complexity manageable through automated workflows.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11902382B2Cloud migration between cloud management platforms
Publication Date: 2024.02.13 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11902382B2 patent drawing
  • US11902382B2 patent drawing
  • US11902382B2 patent drawing

AI summary

Example techniques of migration of cloud networks between different multi-cloud management platforms, are described. In an example, a migration request is received. The migration request is indicative of a source multi-cloud management platform from which a cloud network is to be migrated to a destination multi-cloud management platform. The cloud network to be migrated from the source multi-cloud management platform to the destination multi-cloud management platform is identified based on a user input. Management platform information from the source multi-cloud management platform is obtained. The management platform information is representative of policies and data associated with the cloud network stored in databases of the source multi-cloud management platform. The cloud network is registered at the destination multi-cloud management platform. The management platform information is associated with the cloud network based on a unique identification number of the cloud network. The cloud network is deregistered from the source multi-cloud management platform.