Cloud Module Migration via Test Area Association
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud systems built as fixed types lack flexibility to adapt to changing business requirements, leading to poor performance and security issues, especially when industries need to transition from public to hybrid cloud platforms to meet increased security and resource demands.
Innovation Solution
A migration method that divides business systems into modules, determines association relations, replicates modules to different cloud types, and establishes association relations in a test area for verification, allowing for smooth expansion from public or private cloud systems to hybrid cloud systems while ensuring system security and easy rollback in case of errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a cloud system is built as a fixed type (public or private cloud), then the system structure is simple and easy to implement, but the system lacks flexibility to adapt to changing business requirements
Solution Approach 1:
The patent segments the cloud system into multiple independent modules (first cloud system, second cloud system, test area) that can be independently managed and migrated. This modular structure enables flexible adaptation to different business requirements while maintaining manageable system complexity through clear separation of functions.
Solution Approach 2:
The patent implements a dynamic cloud system that can transition between different states (public cloud, private cloud, hybrid cloud) based on business needs. The system structure evolves from a fixed single-cloud architecture to a flexible multi-cloud architecture with configurable association relations, allowing the system to adapt its complexity level according to requirements.
2Adaptability or versatility
If modules are replicated to a second cloud system of different type, then the system becomes more flexible and adaptable, but the risk of migration errors and system instability increases
Solution Approach 1:
The patent performs preliminary actions by first replicating modules to a test area within the first cloud system before migrating to the second cloud system. Association relations are pre-established and verified in the test environment, allowing potential issues to be detected and resolved before actual migration, thus maintaining system stability.
Solution Approach 2:
The test area serves as an intermediary environment between the first cloud system and the second cloud system. It provides a safe transition zone where modules can be replicated and verified before final migration, reducing the risk of direct migration errors and ensuring system reliability during the transition process.
3Adaptability or versatility
If association relations are established between modules in different cloud systems, then the system achieves seamless integration and functionality, but the complexity of verifying system correctness increases
Solution Approach 1:
The verification process is segmented into distinct stages: first verifying association relations in the test area, then verifying functionality in the hybrid cloud environment. This staged verification approach breaks down the complex verification task into manageable steps, reducing overall verification complexity while achieving comprehensive integration validation.
Solution Approach 2:
The patent implements feedback mechanisms where verification results from the test area guide the migration process, and functionality verification results in the hybrid cloud system guide further optimization. This feedback loop ensures systematic verification and reduces complexity by addressing issues incrementally based on observed results.
4Reliability
If verification is performed in a test area before migration, then the risk of migration failure is reduced, but the time and resources required for the migration process increase
Solution Approach 1:
The patent performs verification on a partial scale first in the test area with a subset of modules and association relations, rather than verifying the entire system at once. This partial verification approach reduces the time and resources required for each verification cycle while still ensuring migration reliability through iterative testing.
Data Source
AI summary
The migration method includes dividing each service system in a first cloud system into a plurality of modules; determining the relation between a module to be migrated among the plurality of modules and other modules; copying said module among the plurality of modules to a second cloud system, the type of the first cloud system being different from that of the second cloud system; and establishing a relation in the second cloud system to complete the migration of the first cloud system. The nature and gist of the present disclosure is that the migration of a module to be migrated in the first cloud system is completed by establishing the association relation of the module to be migrated in the second cloud system.