Cloud system migration method and device, and hybrid cloud system

IN606981BActive Publication Date: 2026-10-26BEIJING JINGDONG SHANGKE INFORMATION TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
IN202237045591
Authority / Receiving Office
IN · IN
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-01-10
Filing Date
2022-08-10
Publication Date
2026-10-26
Estimated Expiration
2040-12-29

AI Technical Summary

Technical Problem

Existing cloud systems lack flexibility to adapt to changing business requirements, leading to poor performance and security issues, particularly as users transition from public to hybrid cloud platforms to meet increased security and traffic demands.

Method used

A method and apparatus for cloud system migration that divides business systems into modules, replicates and verifies these modules across different cloud types, establishing association relations and dependent environments to ensure smooth transition and security, allowing for easy rollback in case of errors.

Benefits of technology

This approach enhances the flexibility and security of cloud systems by enabling seamless expansion from public to hybrid cloud platforms, ensuring system stability and adaptability to changing business needs while maintaining data protection and performance.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

The present disclosure relates to the technical field of cloud computing, and to a cloud system migration method and device, and a hybrid cloud system. The method comprises: 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.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0002] The present disclosure relates to the technical field ofcloud computing, and in particular, to a migration method for cloudsystem, a migration apparatus for cloud system, a hybrid cloudsystem, and a non-transitory computer-readable storage medium.BACKGROUND

[0003] The current cloud platform is mainly divided into publiccloud, private cloud, hybrid cloud and so on. In media, education,e-commerce and other industries, customers can choose to use publiccloud computing platforms to improve system performance; ingovernment, medical, financial and other industries, customers canchoose to use private cloud computing platforms to improve systemsecurity and controllability.

[0004] In the related art, after determining the requirements ofa user, a cloud platform of a type required by the user, such asa public cloud, a private cloud, etc., is directly built.SUMMARY

[0005] According to some embodiments of the present disclosure, amigration method for cloud system is provided, comprising:dividing a business system in a first cloud system into multiplemodules; determining an association relation between a module tobe migrated of the multiple modules and other modules of themultiple modules; replicating the module to be migrated of themultiple modules to a second cloud system, wherein the first cloudsystem and the second cloud system are of different types;establishing association relation in the second cloud system tocomplete the migration of the first cloud system.

[0006] In some embodiments, the method further comprises:determining a dependent environment of the module to be migratedin the first cloud system; and replicating the dependentenvironment in the second cloud system to complete the migrationof the first cloud system.

[0007] In some embodiments, the method further comprises: building,in the second cloud system, a subnet corresponding to a topologystructure relating to the module to be migrated in the first cloudsystem, to complete the migration of the first cloud system.

[0008] In some embodiments, replicating the module to be migratedof the multiple modules to the second cloud system comprises:replicating the module to be migrated to a test area of the firstcloud system; using association relation established in the testarea, performing a first operation verification on the module tobe migrated in the test area of the first cloud system;

[0009] replicating the module to be migrated in the first cloudsystem to the second cloud system, in the case that the firstverification is passed.

[0010] In some embodiments, the method further comprises: if thefirst verification fails, re-determining the association relation,so as to re-perform the first operation verification.

[0011] In some embodiments, the method further comprises:replicating a dependent environment of the module to be migratedand resources relating to the module to be migrated in the firstcloud system to the test area for performing the first operationverification; if the first verification fails, re-determining thedependent environment, so as to re-perform the first operationverification.

[0012] In some embodiments, the method further comprises: building,in the test area, a subnet corresponding to a topology structurerelating to the module to be migrated in the first cloud system,to perform the first operation verification.

[0013] In some embodiments, the method further comprises: usingthe association relation, in a hybrid cloud system composed of thefirst cloud system and the second cloud system, performing a secondoperation verification on module to be migrated in the second cloudsystem.

[0014] In some embodiments, the method further comprises: reperforming the first operation verification, in the case that thesecond verification fails.

[0015] In some embodiments, the first cloud system is a publiccloud system, and the second cloud system is a private cloud system;the method further comprises: verifying whether protected data ofthe private cloud system are accessible through the public cloudsystem; performing an isolation process on the protected data inthe private cloud system in the case that the protected data areaccessible.

[0016] In some embodiments, the method further comprises: deletingthe module to be migrated from the first cloud system, in the casethat a hybrid cloud composed of the first cloud system and thesecond cloud system passes an operation test.

[0017] In some embodiments, the first cloud system is a privatecloud system, and the second cloud system is a public cloud system;the method further comprises: isolating, from the public cloudsystem, protected data in the private cloud system.

[0018] According to other embodiments of the present disclosure,there is provided A migration apparatus for cloud system,comprising: a division unit for dividing a business system in afirst cloud system into multiple modules; a determination unit fordetermining an association relation between a module to be migratedof the multiple modules and other modules of the multiple modules;a replication unit for replicating the module to be migrated ofthe multiple modules to a second cloud system, wherein the firstcloud system and the second cloud system are of different types;an establishment unit for establishing association relation in thesecond cloud system to complete the migration of the first cloudsystem.

[0019] In some embodiments, the determination unit is used fordetermining a dependent environment of the module to be migratedin the first cloud system; and replicating the dependentenvironment to the second cloud system to complete the migrationof the first cloud system.

[0020] In some embodiments, the establishment unit is used forbuilding a corresponding subnet on the second cloud systemaccording to a related topology structure of the module to bemigrated in the first cloud system, so as to complete the migrationof the first cloud system.

[0021] In some embodiments, the replication unit replicates themodule to be migrated to a test area of the first cloud system.The apparatus further comprises a verification unit for usingassociation relation established in the test area, performing afirst operation verification on the module to be migrated in thetest area; wherein if the first verification is passed, thereplication unit replicates the module to be migrated in the firstcloud system to the second cloud system.

[0022] In some embodiments, the determination unit is used for,if the first verification fails, re-determining the associationrelation, so as to re-perform the first operation verification.

[0023] In some embodiments, the replication unit replicates thedependent environment and related resources of the module to bemigrated in the first cloud system to the test area for performingthe first operation verification; if the first verification fails,the determination unit re-determines the dependent environment, soas to re-perform the first operation verification.

[0024] In some embodiments, the establishment unit is used forbuilding, in the test area, a subnet corresponding to a topologystructure relating to the module to be migrated in the first cloudsystem, to perform the first operation verification.

[0025] In some embodiments, the verification unit is used for, ina hybrid cloud system composed of the first cloud system and thesecond cloud system, performing a second operation verification onmodule to be migrated in the second cloud system using theassociation relation.

[0026] In some embodiments, the verification unit is used for,re-performing the first operation verification, in the case thatthe second verification fails.

[0027] In some embodiments, the first cloud system is a publiccloud system, and the second cloud system is a private cloud system;the apparatus further comprises a verification unit for verifyingwhether protected data of the private cloud system are accessiblethrough the public cloud system; a processing unit for performingan isolation process on the protected data in the private cloudsystem in the case that the protected data are accessible.

[0028] In some embodiments, the apparatus further comprises aprocessing unit for, deleting the module to be migrated from thefirst cloud system, in the case that a hybrid cloud composed ofthe first cloud system and the second cloud system passes anoperation test.

[0029] In some embodiments, the first cloud system is a privatecloud system, and the second cloud system is a public cloud system;the apparatus further comprises a processing unit for isolating,from the public cloud system, protected data in the private cloudsystem.

[0030] According to still other embodiments of the presentdisclosure, there is provided A migration apparatus for cloudsystem, comprising: a memory; a processor coupled to the memory,the processor configured to, based on instructions stored in thememory, carry out the migration method for cloud system accordingto any one of the above embodiments.

[0031] According to still further embodiments of the presentdisclosure, there is provided a hybrid cloud system, comprising:a migration apparatus for implementing the migration method forcloud system according to any one of the above embodiments.

[0032] According to still other embodiments of the presentdisclosure, there is provided a nonvolatile computer readablestorage medium having stored thereon a computer program that, whenexecuted by a processor, implements the migration method for cloudsystem according to any one of the above embodiments.BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The accompanying drawings, which are incorporated in andconstitute a portion of this specification, illustrate embodimentsof the present disclosure and, together with the description, serveto explain the principles of the present disclosure.

[0034] The present disclosure will be more clearly understood fromthe following detailed description with reference to theaccompanying drawings, in which:

[0035] FIG. 1 shows a flowchart of some embodiments of a migrationmethod for cloud system of the present disclosure;

[0036] FIG. 2 shows a flowchart of some embodiments of step 30 inFIG. 1;

[0037] FIG. 3 shows a schematic diagram of some embodiments of amigration apparatus for cloud system of the present disclosure;

[0038] FIG. 4 shows a schematic diagram of some embodiments of amigration method for cloud system of the present disclosure;

[0039] FIG. 5 shows a schematic diagram of other embodiments ofthe migration method for cloud system of the present disclosure;

[0040] FIG. 6 shows a schematic diagram of still other embodimentsof the migration method for cloud system of the present disclosure;

[0041] FIG. 7 shows a schematic diagram of further embodiments ofthe migration method for cloud system of the present disclosure;

[0042] FIG. 8 shows a schematic diagram of further embodiments ofthe migration method for cloud system of the present disclosure;

[0043] FIG. 9 shows a block diagram of some embodiments of amigration apparatus for cloud system of the present disclosure;

[0044] FIG. 10 shows a block diagram of other embodiments of themigration apparatus for cloud system of the present disclosure;

[0045] FIG. 11 shows a block diagram of still other embodimentsof the migration apparatus for cloud system of the presentdisclosure;

[0046] FIG. 12 shows a block diagram of some embodiments of ahybrid cloud system of the present disclosure.DETAILED DESCRIPTION

[0047] Various exemplary embodiments of the present disclosurewill now be described in detail with reference to the accompanyingdrawings. Notice that, Unless otherwise specified, the relativearrangement, numerical expressions and numerical values of thecomponents and steps set forth in these examples do not limit thescope of the invention.

[0048] At the same time, it should be understood that, for easeof description, the dimensions of the various parts shown in thedrawings are not drawn to actual proportions.

[0049] The following description of at least one exemplaryembodiment is in fact merely illustrative and is in no way intendedas a limitation to the invention, its application or use.

[0050] Techniques, methods, and apparatus known to those ofordinary skill in the relevant art may not be discussed in detail,but where appropriate, these techniques, methods, and apparatusesshould be considered as part of the specification.

[0051] Of all the examples shown and discussed herein, anyspecific value should be construed as merely illustrative and notas a limitation. Thus, other examples of exemplary embodiments mayhave different values.

[0052] Notice that, similar reference numerals and letters aredenoted by the like in the accompanying drawings, and therefore,once an article is defined in a drawing, there is no need forfurther discussion in the accompanying drawings.

[0053] As mentioned above, with the development of businesses andpolicy changes, current needs of users are not equal to futureneeds of users. Therefore, the fixed-type cloud systems in therelated art cannot adapt to changes in user business requirements.

[0054] The above related technologies have the following problem:a cloud system built as a fixed type cannot adapt to changes inbusiness requirements, resulting in poor flexibility of the cloudsystem. In view of this, the present disclosure provides atechnical solution for cloud system migration, which can improvethe flexibility of the cloud system.

[0055] In some embodiments, users may choose to expand a publiccloud platform into a hybrid cloud platform due to substantiallyincreased security requirements of users. For example, with thedevelopment of business and the continuous improvement of industryregulatory and security requirements, some powerful customers maychoose to expand their public cloud platforms into hybrid cloudplatforms.

[0056] For example, some media industries initially adopted publiccloud platforms to meet the requirements of users for a largenumber of concurrent accesses. However, with the strengthening ofintellectual property protection and the increasing requirementsfor user privacy and data security protection, some important mediarelated to the national economy and people's livelihood have begunto build their own data centers. Moreover, a user may choose toreplace an original platform architecture with a hybrid cloud,which can not only protect the security of core data, but alsowithstand network access traffic at extremely high peaks.

[0057] In some embodiments, due to the limited number of resourcesof private cloud platforms, the demand of some industries anddepartments cannot be met by means of private cloud or privateinformation systems. In this case, users may choose to expand aprivate cloud platform into a hybrid cloud platform.

[0058] For example, a private cloud platform is initially adoptedfor the 12306 China Railway website; when the private cloudplatform cannot withstand the service load during peak traffichours, a hybrid cloud can be chosen instead. In this way, it ispossible to not only protect the security of core data, but alsowithstand network access traffic at extremely high peaks.

[0059] In view of the above problem, the technical solution ofthe present disclosure can realize the expansion of a cloudplatform under the condition that a complex business and managementsystem has been built on a private cloud.

[0060] The present disclosure fully considers the technical risksthat may be encountered in the process of expanding a public cloudplatform or a private cloud platform to a hybrid cloud platform,and ensures that the cloud platform migration process is smoothand effective through a method comprising multiple statetransition steps; while ensuring system security, steps withsignificant risks can be rolled back easily to ensure that thebusiness system cannot not damaged. For example, it can be realizedby the following embodiments.

[0061] FIG. 1 shows a flowchart of some embodiments of a migrationmethod for cloud system of the present disclosure.

[0062] As shown in FIG. 1, the method comprises: step S10: divisionof a plurality of modules; step S20: determination of associationrelation; step S30: replication of module to be migrated; and stepS40: establishment of association relation.

[0063] In step S10, a business system in a first cloud system isdivided into multiple modules. For example, the business systemcan be an office system, a financial management system, a personnelmanagement system, a website, a resource query system, and aresource management system; each business system can be dividedinto relatively independent functional modules.

[0064] In step S20, association relation between module to bemigrated and other modules of the multiple modules are determined.

[0065] In step S30, the module to be migrated of the multiplemodules are replicated to a second cloud system, wherein the firstcloud system and the second cloud system are of different types.For example, the first cloud system may be a public cloud system,and the second cloud system may be a private cloud system; thefirst cloud system may be a private cloud system, and the secondcloud system may be a public cloud system.

[0066] In this embodiment, step S30 may be executed as steps shownin FIG.2.

[0067] FIG. 2 shows a flowchart of some embodiments of step 30 inFIG. 1.

[0068] As shown in FIG. 2, step S30 comprises: step S310:replicating the module to be migrated to a text area; step S320:performing a first verification; and step S330: replicating themodule to be migrated to a second cloud system.

[0069] In step S310, the module to be migrated are replicated toa test area in the first cloud system.

[0070] In step S320, a first operation verification is performed,in the first cloud system, on the module to be migrated in thetest area using association relation established in the test area.

[0071] In some embodiments, if the first verification fails, theassociation relation are re-determined, so as to re-perform thefirst operation verification.

[0072] In some embodiments, a dependent environment and relatedresources of the module to be migrated in the first cloud systemare replicated to the test area for performing the first operationverification; if the first verification fails, the dependentenvironment is re-determined, so as to re-perform the firstoperation verification. For example, the related resources may becomputing resources, data resources and the like of the cloudsystem.

[0073] In some embodiments, the dependent environment may comprisefunctional dependency, and data dependency. For example, afunctional dependency may be that a module itself does not have afunction such as file opening or sending, and needs to depend onthe corresponding function of another module.

[0074] In some embodiments, according to the related topologystructure of the module to be migrated in the first cloud system,a corresponding subnet is built in the test area to perform thefirst operation verification. For example, the affiliation betweenthe module to be migrated and the subnet in the second cloud systemis the same as the affiliation between the module to be migratedand the subnet in the first cloud system.

[0075] In step S330, if the first verification is passed, themodule to be migrated in the first cloud system are replicated tothe second cloud system.

[0076] After the module to be migrated in the first cloud systemare replicated to the second cloud system, the migration can becontinued through the remaining steps in FIG. 1.

[0077] In step S40, association relation are established in thesecond cloud system to complete the migration of the first cloudsystem.

[0078] In some embodiments, a dependent environment of the moduleto be migrated in the first cloud system is determined; thedependent environment is replicated to the second cloud system tocomplete the migration of the first cloud system.

[0079] In some embodiments, a corresponding subnet is establishedon the second cloud system according to a related topologystructure of the module to be migrated in the first cloud system,so as to complete the migration of the first cloud system.

[0080] In some embodiments, the first cloud system is a publiccloud system, and the second cloud system is a private cloud system.In this case, it is verified whether protected data of the privatecloud system can be accessed through the public cloud system; anisolation process is performed on the protected data in privatecloud systems in the case that the protected data are accessible.

[0081] In some embodiments, the first cloud system is a privatecloud system, and the second cloud system is a public cloud system;and protected data in the private cloud system is isolated fromthe public cloud system.

[0082] In some embodiments, if the hybrid cloud composed of thefirst cloud system and the second cloud system passes the operationtest, the module to be migrated are deleted from the first cloudsystem.

[0083] In some embodiments, in a hybrid cloud system composed ofthe first cloud system and the second cloud system, a secondoperation verification is performed on module to be migrated inthe second cloud system using the association relation.

[0084] In some embodiments, if the second verification fails, thefirst operation verification is re-performed.

[0085] FIG. 3 shows a schematic diagram of some embodiments of amigration apparatus for cloud system of the present disclosure.

[0086] As shown in FIG. 3, the migration apparatus may comprisean underlying support module, a first cloud processing module, anexpansion support module, and a second cloud processing module.

[0087] In some embodiments, the main function of the underlyingsupport module is to provide overall underlying support for theexpansion from the first cloud architecture to a hybrid cloudarchitecture. The underlying support module may comprise a cloudplatform state management module, dynamic resource managementtools, an operation and maintenance management module, and asecurity management module.

[0088] For example, the cloud platform state management modulemainly checks the state of a cloud platform system and decideswhether to proceed with a next expansion step; the dynamic resourcemanagement tools provide multi-platform resource managementfunctions for the cloud platform expansion; the operation andmaintenance management module is mainly responsible for theunified operation and maintenance management before and after thecloud platform expansion; the security management module is mainlyresponsible for the security of the cloud platform during and afterthe cloud platform extension.

[0089] In some embodiments, the main function of the first cloudprocessing module is to perform processing on each system on thefirst cloud before system architecture expansion, so as to ensurethat the expansion will not cause system problems. The first cloudprocessing module may comprise a system segmentation module, adependency detection and analysis module, a relation detection andanalysis module, a decoupling and separation module, computingresources separation management, data resources separationmanagement, a separation verification module, and an errorhandling module.

[0090] For example, the system segmentation module scansrelatively independent application systems and services in thesystem, determines the boundaries of independent applicationsystems, services and their related resources; formulates a systemsegmentation plan to determine which application systems andservices will be remained on the public cloud platform and whichapplications systems and services will be expanded to a privatecloud platform.

[0091] For example, the dependency detection and analysis modulescans system dependencies of each independent module, comprisingfunctional dependencies and data dependencies. Functionaldependencies comprise basic dependencies of the applicationsystems and services, such as operating system functions, systemlibraries, drivers, hardware functions, system basic components,programming framework components and the like on which the moduledepends; data dependencies comprise data sources, data files, datastorage, and data backup, and the like.

[0092] For example, the relation detection and analysis modulescans interrelationship between various independent modules, suchas mutual data transmission, function invocation, process sequence,etc.

[0093] For example, after determining the dependencies andrelations, the decoupling and separation module reconstructs thesystem dependencies required by the modules to be separated toensure that the modules can operate independently; preserves therelations between the modules and other modules; when the relationsneeds to be changed, updates corresponding modules.

[0094] For example, the computing resources separation managementis responsible for separating computing resources (such as cloudhosts, containers, etc.) related to the independent applicationsystems in the original first cloud; replicating and migrating aportion of computing resources that need to be separated to atransition space (test area) separately assigned in the publiccloud; and ensuring that the functions and data on which thecomputing resources depend are built together in the transitionspace.

[0095] For example, the data resources separation management isresponsible for separating data resources (such as databases,block storage, etc.) related to the independent applicationsystems in the original first cloud; replicating and migrating aportion of the data resources that need to be separated to thetransition space separately assigned in the first cloud, andensuring the consistency and integrity of the data.

[0096] For example, the separation verification module isresponsible for verifying whether the functions and performance ofthe system can meet the target requirements after the computingand data resources are separated to the transition space.

[0097] For example, the error handling module is responsible forrolling back a failed severing module to its initial error-freestate.

[0098] In some embodiments, the expansion support module is mainlyused for: providing expansion support during the process ofexpanding the network of the first cloud to a second cloud, andassisting in completing the verification of the system. Theexpansion support module comprises a network topology conversionmanagement module, a networking verification module, and a hybridverification module.

[0099] For example, the network topology conversion managementmodule is responsible for, according to the network topology ofthe original first cloud, extending the network topology to thesecond cloud, and maintaining data transmission of related modulesbetween the second cloud and the first cloud. In the case wherethe first cloud is a private cloud and the second cloud is a publiccloud, a portion of the private cloud that needs security isolationcan be separated from the private cloud, so that the public cloudresources access a network transmission interface module of theprivate cloud for isolation.

[00100] For example, the networking verification module verifiesthe connectivity and network bandwidth of the newly formed hybridcloud network; and verifies whether the data transmission betweenthe separated resources of the second cloud and the networkconnection module of the first cloud is normal.

[00101] For example, the hybrid verification module is mainlyresponsible for functional and performance verification of relatedsystems of the hybrid cloud, and for effectiveness verification ofdata isolation and security mechanisms.

[00102] In some embodiments, the main function of the second cloudprocessing module is to manage dynamically changed resources ofthe second cloud. The second cloud processing module mainlycomprises a private cloud resource dynamic change managementmodule. When the second cloud is a private cloud, the second cloudprocessing module further comprises a data security verificationmodule.

[00103] For example, the private cloud resource dynamic changemanagement module is mainly responsible for gradually expandingthe number of resources in the second cloud; allocating privatecloud resources on demand to adapt to business requirements andbusiness development.

[00104] For example, the data security verification module ismainly responsible for verifying whether the involved datasecurity mechanisms have an effect of security isolation after theprivate cloud has been isolated from the public cloud interfacemodule.

[00105] In some embodiments, during the transition from the firstcloud to the hybrid cloud, the overall system is mainly dividedinto four states according to the distribution of system resources.For example, the states mainly comprise an original state, aseparated state, a hybrid verification state, and a hybrid state.The transition between various states of the system can be shownas FIG. 4.

[00106] FIG. 4 shows a schematic diagram of some embodiments of amigration method for cloud system of the present disclosure.

[00107] As shown in FIG. 4, the original state is a stable stateof the first cloud before system expansion; the separated state isa system state in which some resources of the first cloud areseparated from the first cloud, while maintaining the datainteraction between the separated first cloud resources and theoriginal first cloud.

[00108] The hybrid verification state is a state in which theseparated modules are migrated to the second cloud. Only a smalleramount of resources are kept for the second cloud, so long as thenumber of resources can support the verification of systemfunctions and performance.

[00109] The hybrid state is a final state of the system, in whichresources on the second cloud are expanded according to businessrequirements to achieve a stable state of the hybrid cloud system.

[00110] The original state of the first cloud can be transitionedto the separated state through a module separation process; if asystem error occurs during the verification of the separated state,the system can be returned to the original state through an errorrollback process.

[00111] If the separated state is verified correctly, the systemcan be transitioned to the hybrid verification state through modulemigration. The system is fully tested and verified in the hybridverification state. If there is an error in the verification, thesystem can be rolled back to the separated state and reprocessedaccording to the error; if the verification is correct in thehybrid verification state, the resources on the second cloud willbe expanded, that is, the scale of the system on the second cloudwill be expanded to form the final hybrid state.

[00112] In this way, through the design of the multiple states,the stability of the system expansion process can be ensured, andsystem problems caused by the destruction of the original systemduring the system expansion process can be prevented. To ensurethat the system can be rolled back, the original system modulesneed to be reserved. When the system reaches the final stablestate, the reserved resources can be gradually recycled.

[00113] In some embodiments, before expanding the first cloudsystem, it is necessary to know the basic situation of each systemrunning on the first cloud. In this way, segmentation ofindependent modules can be performed as the basis for resourceexpansion on the second cloud. For example, the module segmentationof the original state system can be realized by the embodiment inFIG. 5.

[00114] FIG. 5 shows a schematic diagram of other embodiments ofthe migration method for cloud system of the present disclosure.

[00115] As shown in FIG. 5, the process of system modulesegmentation is substantially as follows.

[00116] All business program systems in the first cloud system arescanned and analyzed. For example, the business program systemscomprise an office system, a financial management system, apersonnel management system, a website, a resource query system,and a resource management system, etc. Independent modules(Modules) of the determined business program systems arerepresented as m1 to m8. Relevant resources of the independentmodules, such as computing resources, data resources, and networkresources, can be determined.

[00117] Relations between the various modules are analyzed. Forexample, association relation r1, r2, r3 between m1 to m8 may bedetermined. An association relation is a relationship ofinteraction such as invocation, access, and control that isrequired between two or more modules.

[00118] Functional dependencies (Dependency) of various modules areanalyzed. For example, the functional dependencies can be d1, d2,etc.

[00119] Data dependencies of various modules are analyzed. Forexample, the data dependencies can be d3, d4, etc.

[00120] According to the needs of business expansion of a firstcloud's customer and the segmentation of modules, modules thatneed to be expanded to the second cloud such as m3, m6, and m8 aredetermined; Functional dependency d1 and data dependency d4 ofthese modules are determined; An association relation r3 betweenthese modules and modules retained in the first cloud environmentis determined.

[00121] In some embodiments, before expanding some modules to thesecond cloud, a transition area (test area) is created in theoriginal first cloud to temporarily process the modules to beexpanded and facilitate the verification of module separation. Forexample, the transition from the original state to the separatedstate can be realized by the embodiment of FIG. 6.

[00122] FIG. 6 shows a schematic diagram of still other embodimentsof the migration method for cloud system of the present disclosure.

[00123] As shown in FIG. 6, the transition process from the originalstate to the separated state is substantially as follows.

[00124] According to a user's requirements, it can be determinedthat the modules to be expanded to the second cloud are m3, m6,and m8; their related functional dependency and data dependencyare d1 and d4; they have an association relation r3 with modulesretained on the public cloud.

[00125] A transition area, whose network environment is relativelyindependent from the original area, is created in the first cloud.The transition area is used for carrying the modules to be expanded.The function dependency d1 and the data dependency d4 of themodules to be expanded (module to be migrated) are established inthe transition area. Relevant resources (such as computingresources and data resources) and network topology of the modulesto be expanded m3, m6, and m8 are replicated to the resources inthe transition area. An association relation (r3) between themodules to be expanded and the modules in the original area isestablished.

[00126] The modules to be expanded m3, m6, and m8 are activatedand configured; An operation test and verification in terms offunction, performance, security, and reliability is performedwithin the first cloud. If the test and verification is passed,this process is completed; if the test and verification fail,problems are searched and located.

[00127] If the problems can be solved in the separated state, theproblems are solved and this process is completed; if the problemscannot be solved in the separated state, the system is rolled backto the original state to re-perform the analysis, evaluation andprocessing steps.

[00128] In some embodiments, the system which passes theverification in the separated state is the basis for the furtherexpansion of the system. For the sake of safety and consideringthe cost of resources, in the process of expansion to a hybridcloud, the separated state is first transitioned to a hybridverification state, in which a small amount of resources are usedto verify the validity of the expansion. For example, thetransition from the separated state to the hybrid verificationstate can be realized by the embodiment of FIG. 7.

[00129] FIG. 7 shows a schematic diagram of further embodiments ofthe migration method for cloud system of the present disclosure.

[00130] As shown in FIG. 7, the process of realizing the transitionfrom the separated state to the hybrid verification state throughthe expansion of the transition area to the second cloud system issubstantially as follows.

[00131] A hybrid cloud management platform is built on the firstcloud platform. A network path between the first cloud and thesecond cloud is established to verify the network connectionbetween the first cloud and the second cloud.

[00132] A subnet similar to that in the transition zone is builtin the second cloud whiling ensuring that the subnet is on a scalethat can withstand future services. Using the hybrid cloudmanagement platform, the modules (m3, m6, m8), function dependencyd1, data dependency d3 and other related instances in thetransition area are replicated and migrated to the subnet built onthe second cloud according to the principle of minimum scale; Theassociation relation r3 between the modules in the second cloudand the modules in the public cloud is rebuilt.

[00133] The overall system formed by modules (m3, m6, m8) in thesecond cloud and modules (m1 to m8, etc.) in the first cloud isverified; a test and verification is performed in terms of function,performance, security, reliability, availability, scalability,maintainability and the like to comprehensively test the systemstatus after resource migration. If the verification is passed,this process is completed; if the verification fails, causes aresearched to solve the problems in the hybrid verification state.

[00134] If the problems can be solved in the hybrid verificationstate, the problems are solved and this process is completed; ifthe problems cannot be solved in the hybrid verification state,the system is rolled back to the separated state to re-perform theprocesses on the system.

[00135] In some embodiments, if the system passes the test andverification in the hybrid verification state, the construction ofthe overall hybrid cloud architecture is substantially successful.Next, the number of resources in the second cloud can be expandedto meet business needs. For example, the transition from the hybridverification state to the hybrid state can be realized by theembodiment of FIG. 8.

[00136] FIG. 8 shows a schematic diagram of further embodiments ofthe migration method for cloud system of the present disclosure.

[00137] As shown in FIG. 8, the process of transitioning from thehybrid verification state to the hybrid state through resourceexpansion is substantially as follows.

[00138] If the bandwidth of the system is adjustable, the networkbandwidth between the first cloud and the second cloud can beincreased to meet the bandwidth requirements of business datatransmission.

[00139] The amount of the resources of modules to be expanded m3,m6, and m8 in the second cloud can be increased. For example, thenumber of cloud host instances, the storage capacity, the instancesize, the network bandwidth, etc. can be increased, so that theprocessing capacity of the system can meet the design requirementsof the hybrid cloud.

[00140] After the system operates normally for a period of timewithout any problems, the modules m3, m6, and m8 originallyreserved on the first cloud will be gradually removed, and thenthis process is completed.

[00141] In some embodiments, if the first cloud system is a publiccloud system and the second cloud system is a private cloud system,data security on the private cloud can be verified throughexperimental access to data to be protected in the private cloudfrom the public cloud.

[00142] For example, access results can be viewed. If the data thatneeds to be protected can be accessed from the public cloud, dataisolation and protection measures should be added on the privatecloud. After data isolation and successful security verification,if the bandwidth is adjustable, the network bandwidth between thepublic cloud and the private cloud is increased to meet thebandwidth requirements for business data transmission.

[00143] In the above embodiment, a complete and effective methodfor expanding a first cloud platform to a hybrid cloud platformand expanding the system on the platform is proposed.

[00144] The process of expanding the entire system is controlledby the method of cloud platform state transition. Two cloudplatform states that can be verified, namely a separated state anda hybrid verification state, are proposed. In this way, moduleexpansion is easier to implement, and it also ensures theconvenience of processing when expansion problems occur.

[00145] The system on the cloud platform is divided into modules,dependencies, and association relation, which is easy to untanglethe complex system and make the system expansion more convenientand effective.

[00146] In the above embodiment, the migration of module to bemigrated in the first cloud system is completed by establishingthe association relation of the module to be migrated in the secondcloud system. In this way, mutual migration can be realized betweendifferent types of cloud systems, so as to meet different businessrequirements and improve the flexibility of the cloud system.

[00147] FIG. 9 shows a block diagram of some embodiments of amigration apparatus for cloud system of the present disclosure.

[00148] As shown in FIG. 9, the migration apparatus for cloud systemcomprises a division unit 91, a determination unit 92, areplication unit 93, and an establishment unit 94.

[00149] The division unit 91 is used for dividing a business systemin a first cloud system into multiple modules.

[00150] The determination unit 92 is used for determining anassociation relation between a module to be migrated of themultiple modules and other modules of the multiple modules.

[00151] The replication unit 92 is used for replicating the moduleto be migrated of the multiple modules to a second cloud system,wherein the first cloud system and the second cloud system are ofdifferent types.

[00152] In some embodiments, the replication unit 93 replicatesthe module to be migrated to a test area of the first cloud system.The migration apparatus 9 further comprises a verification unit 95for, using association relation established in the test area,performing a first operation verification on the module to bemigrated in the test area; wherein if the first verification ispassed, the replication unit 93 replicates the module to bemigrated in the first cloud system to the second cloud system.

[00153] In some embodiments, the determination unit 92 is used fordetermining a dependent environment of the module to be migratedin the first cloud system; and the replication unit 93 is used forreplicating the dependent environment to the second cloud systemto complete the migration of the first cloud system.

[00154] In some embodiments, the determination unit 92 is used for,if the first verification fails, re-determining the associationrelation, so as to re-perform the first operation verification.

[00155] In some embodiments, the replication unit 93 replicatesthe dependent environment and related resources of the module tobe migrated in the first cloud system to the test area forperforming the first operation verification; if the firstverification fails, the determination unit 92 re-determines thedependent environment, so as to re-perform the first operationverification.

[00156] The establishment unit 94 is used for establishingassociation relation in the second cloud system to complete themigration of the first cloud system.

[00157] In some embodiments, the establishment unit 94 is used forbuilding, in the second cloud system, a subnet corresponding to atopology structure relating to the module to be migrated in thefirst cloud system, to complete the migration of the first cloudsystem.

[00158] In some embodiments, the establishment unit 94 is used forbuilding, in the test area, a subnet corresponding to a topologystructure relating to the module to be migrated in the first cloudsystem, to perform the first operation verification.

[00159] In some embodiments, the verification unit 95 is used for,in a hybrid cloud system composed of the first cloud system andthe second cloud system, performing a second operationverification on module to be migrated in the second cloud systemusing the association relation.

[00160] In some embodiments, the verification unit 95 is used for,re-performing the first operation verification, in the case thatthe second verification fails.

[00161] In some embodiments, the first cloud system is a publiccloud system, and the second cloud system is a private cloud system;the verification unit 95 is used for verifying whether protecteddata of the private cloud system are accessible through the publiccloud system; the migration apparatus 9 further comprises aprocessing unit 96 for performing an isolation process on theprotected data in the private cloud system in the case that theprotected data are accessible.

[00162] In some embodiments, if the hybrid cloud composed of thefirst cloud system and the second cloud system passes the operationtest, a processing unit 96 deletes the module to be migrated fromthe first cloud system.

[00163] In some embodiments, the first cloud system is a privatecloud system, and the second cloud system is a public cloud system;the processing unit 96 is used for isolating, from the public cloudsystem, protected data in the private cloud system.

[00164] In the above embodiment, the migration of module to bemigrated in the first cloud system is completed by establishingthe association relation of the module to be migrated in the secondcloud system. In this way, mutual migration can be realized betweendifferent types of cloud systems, so as to meet different businessrequirements and improve the flexibility of the cloud system.

[00165] FIG. 10 shows a block diagram of other embodiments of themigration apparatus for cloud system of the present disclosure.

[00166] As shown in FIG. 10, the apparatus 10 for cloud systemmigration of this embodiment comprises: a memory 101 and aprocessor 102 coupled to the memory 101, the processor 102configured to, based on instructions stored in the memory 101,carry out the migration method for cloud system according to anyone of the embodiments of the present disclosure.

[00167] Wherein, the memory 101 may comprise, for example, systemmemory, a fixed non-transitory storage medium, or the like. Thesystem memory stores, for example, an operating system,applications, a boot loader, a database, and other programs.

[00168] FIG. 11 shows a block diagram of still other embodimentsof the migration apparatus for cloud system of the presentdisclosure.

[00169] As shown in FIG. 11, the apparatus 11 for cloud systemmigration of this embodiment comprises: a memory 1110 and aprocessor 1120 coupled to the memory 1110, the processor 1120configured to, based on instructions stored in the memory 1110,carry out the migration method for cloud system according to anyone of the embodiments of the present disclosure.

[00170] The memory 1110 may comprise, for example, system memory,a fixed non-transitory storage medium, or the like. The systemmemory stores, for example, an operating system, applications, aboot loader, a database, and other programs.

[00171] The apparatus 11 for cloud system migration may furthercomprise an input-output interface 1130, a network interface 1140,a storage interface 1150, and the like. These interfaces 1130,1140, 1150 and the memory 1110 and the processor 1120 may beconnected through a bus 1160, for example. The input-outputinterface 1130 provides a connection interface for input-outputdevices such as a display, a mouse, a keyboard, and a touch screen.The network interface 1140 provides a connection interface forvarious networked devices. The storage interface 1150 provides aconnection interface for external storage devices such as an SDcard and a USB flash disk.

[00172] FIG. 12 shows a block diagram of some embodiments of ahybrid cloud system of the present disclosure.

[00173] As shown in FIG. 12, the hybrid cloud system 12 comprisesa migration apparatus 121 for implementing the migration methodfor cloud system according to any one of the above embodiments.

[00174] Those skilled in the art should understand that theembodiments of the present disclosure may be provided as a method,a system, or a computer program product. Therefore, embodiments ofthe present disclosure can take the form of an entirely hardwareembodiment, an entirely software embodiment or an embodimentcontaining both hardware and software elements. Moreover, thepresent disclosure may take the form of a computer program productembodied on one or more computer-usable non-transitory storagemedia having computer-usable program code embodied therein.

[00175] Heretofore, the migration method for cloud system, themigration apparatus for cloud system, the hybrid cloud system andthe non-transitory computer-readable storage medium according tothe present disclosure have been described in detail. In order toavoid obscuring the concepts of the present disclosure, somedetails known in the art are not described. Based on the abovedescription, those skilled in the art can understand how toimplement the technical solutions disclosed herein.

[00176] The method and system of the present disclosure may beimplemented in many ways. For example, the method and system ofthe present disclosure may be implemented by software, hardware,firmware, or any combination of software, hardware, and firmware.The above sequence of steps of the method is merely for the purposeof illustration, and the steps of the method of the presentdisclosure are not limited to the above-described specific orderunless otherwise specified. In addition, in some embodiments, thepresent disclosure may also be implemented as programs recorded ina recording medium, which comprise machine-readable instructionsfor implementing the method according to the present disclosure.Thus, the present disclosure also covers a recording medium storingprograms for executing the method according to the presentdisclosure.

[00177] Although some specific embodiments of the presentdisclosure have been described in detail by way of example, thoseskilled in the art should understand that the above examples areonly for the purpose of illustration and are not intended to limitthe scope of the present disclosure. It should be understood bythose skilled in the art that the above embodiments may be modifiedwithout departing from the scope and spirit of the presentdisclosure. The scope of the disclosure is defined by the followingclaims.

Claims

1. A migration method for cloud system, comprising: dividing a business system in a first cloud system into multiple modules; determining an association relation between a module to be migrated of the multiple modules and other modules of the multiple modules; replicating the module to be migrated of the multiple modules to a second cloud system, wherein the first cloud system and the second cloud system are of different types; and establishing the association relation in the second cloud system to complete migration of the first cloud system.

2. The migration method as claimed in claim 1, comprising: determining a dependent environment of the module to be migrated in the first cloud system; and replicating the dependent environment in the second cloud system to complete the migration of the first cloud system.

3. The migration method as claimed in claim 1, comprising: building, in the second cloud system, a subnet corresponding to a topology structure relating to the module to be migrated in the first cloud system, to complete the migration of the first cloud system.

4. The migration method as claimed in claim 1, wherein replicating the module to be migrated of the multiple modules to the second cloud system comprises: replicating the module to be migrated to a test area of the first cloud system; performing a first operation verification on the module to be migrated in the test area of the first cloud system, using association relation established in the test area; and replicating the module to be migrated in the first cloud system to the second cloud system, in the case that the first verification is passed.

5. The migration method as claimed in claim 4, comprising: re-determining an association relation between the module to be migrated and the other modules, in the case that the first verification fails; and re-performing the first operation verification according to a re-determined association relation.

6. The migration method as claimed in claim 4, comprising: replicating a dependent environment of the module to be migrated and resources relating to the module to be migrated in the first cloud system to the test area for performing the first operation verification; re-determining a dependent environment of the module to be migrated, in the case that the first verification fails; and re-performing a first operation verification according to a redetermined dependent environment.

7. The migration method as claimed in claim 4, comprising: building, in the test area, a subnet corresponding to a topology structure relating to the module to be migrated in the first cloud system, to perform the first operation verification.

8. The migration method as claimed in claim 4, comprising: performing a second operation verification on a module to be migrated in the second cloud system, using the association relation, in a hybrid cloud system composed of the first cloud system and the second cloud system.

9. The migration method as claimed in claim 8, comprising: re-performing the first operation verification, in the case that the second verification fails.

10. The migration method according to any one of claims 1 to 9, wherein the first cloud system is a public cloud system, and the second cloud system is a private cloud system, the migration method comprising: verifying whether protected data of the private cloud system are accessible through the public cloud system; and performing an isolation process on the protected data in the private cloud system, in the case that the protected data are accessible.

11. The migration method according to any one of claims 1 to 9, comprising: deleting the module to be migrated from the first cloud system, in the case that a hybrid cloud composed of the first cloud system and the second cloud system passes an operation test.

12. The migration method according to any one of claims 1 to 9, wherein the first cloud system is a private cloud system, and the second cloud system is a public cloud system, the migration method comprising: isolating, from the public cloud system, protected data in the private cloud system.

13. A migration apparatus for cloud system, comprising: a division unit for dividing a business system in a first cloud system into multiple modules; a determination unit for determining an association relation between a module to be migrated of the multiple modules and other modules of the multiple modules; a replication unit for replicating the module to be migrated of the multiple modules to a second cloud system, wherein the first cloud system and the second cloud system are of different types; and an establishment unit for establishing the association relation in the second cloud system to complete migration of the first cloud system.

14. A migration apparatus for cloud system, comprising: a memory; and a processor coupled to the memory, the processor configured to, based on instructions stored in the memory, carry out the migration method for cloud system according to any one of claims 1 to 12.

15. A hybrid cloud system, comprising: a migration apparatus for implementing the migration method for cloud system according to any one of claims 1 to 12.

16. A non-transitory computer-readable storage medium on which a computer program is stored, which when executed by a processor implements the migration method for cloud system according to any one of claims 1 to 12.