CN111782336A

CN111782336A - Cloud migration method and device of hybrid cloud and computer-storable medium

Info

Publication number: CN111782336A
Application number: CN202010028204.1A
Authority: CN
Inventors: 白石
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Jingdong Shangke Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Jingdong Shangke Information Technology Co Ltd
Priority date: 2020-01-10
Filing date: 2020-01-10
Publication date: 2020-10-16

Abstract

The disclosure relates to a cloud migration method and device of a hybrid cloud and a computer storage medium, and relates to the field of cloud computing. The mixed cloud comprises a first cloud and a second cloud which are different in cloud type, and the cloud migration method of the mixed cloud comprises the following steps: dividing each first service system in the first cloud into a plurality of migration modules; dividing each second service system in the second cloud into a plurality of original modules; determining the incidence relation between each migration module and other migration modules and a plurality of original modules; copying the plurality of migration modules into the second cloud; and in the second cloud, reestablishing the association relationship between each migration module and the other migration modules and the plurality of original modules according to the determined association relationship between each migration module and the other migration modules and the plurality of original modules. According to the method and the device, the flexibility of the hybrid cloud system is improved, and the reliability and effectiveness of cloud migration are guaranteed.

Description

Cloud migration method and device of hybrid cloud and computer-storable medium

Technical Field

The present disclosure relates to the field of cloud computing, and in particular, to a cloud migration method and apparatus for a hybrid cloud, and a computer-readable storage medium.

Background

In government, medical, financial and other industries, customers sometimes choose to adopt a hybrid cloud to carry business in order to take into account system security and performance.

In the related art, after determining a service requirement, a customer directly builds a cloud platform corresponding to the service requirement, such as a hybrid cloud, a private cloud or a public cloud.

Disclosure of Invention

The inventor thinks that: with the change of the customer service requirement, the customer usually wants to convert the manner of adopting the hybrid cloud bearer service into the manner of adopting the private cloud or public cloud bearer service. In the related art, a fixed cloud platform is built, and the different cloud platforms cannot be flexibly migrated and switched in an alkaline manner according to the change of service requirements, so that the different cloud platforms can be flexibly selected to bear services.

In order to solve the technical problems, the method and the system improve the flexibility of the hybrid cloud system and ensure the reliability and effectiveness of cloud migration.

According to a first aspect of the present disclosure, there is provided a cloud migration method of a mixed cloud including a first cloud and a second cloud having different cloud types, the cloud migration method including: dividing each first service system in the first cloud into a plurality of migration modules; dividing each second service system in the second cloud into a plurality of original modules; determining the incidence relation between each migration module and other migration modules and a plurality of original modules; copying the plurality of migration modules into the second cloud; and in the second cloud, reestablishing the association relationship between each migration module and the other migration modules and the plurality of original modules according to the determined association relationship between each migration module and the other migration modules and the plurality of original modules.

In some embodiments, the cloud migration method further comprises: determining environment dependency information of the migration module in the first cloud; and copying the environment dependency information into the second cloud.

In some embodiments, the second cloud is divided into a transition region and an original region, the transition region including the plurality of migrated modules, the original region including the plurality of legacy modules.

In some embodiments, the cloud migration method further comprises: performing first operation verification on each migration module by using the incidence relation reconstructed in the second cloud; and under the condition that the first operation verification fails, re-determining the association relationship among each migration module, other migration modules and a plurality of original modules, and re-performing the first operation verification on each migration module.

In some embodiments, the cloud migration method further comprises: copying environment dependency information and related resources of each migration module in the first cloud to the transition region; performing first operation verification on each migration module by using the environment dependence information and related resources; and under the condition that the first operation verification fails, re-determining the environment dependence information of each migration module, and re-performing the first operation verification on each migration module.

In some embodiments, the first cloud is a private cloud, the second cloud is a public cloud, desensitization processing is performed on the relevant resources, and the desensitized relevant resources are copied to the second cloud.

In some embodiments, the first cloud is a public cloud, the second cloud is a private cloud, and the migration module in the transition area is copied to the original area if the first operation verification passes.

In some embodiments, the first cloud is a private cloud, the second cloud is a public cloud, and a security mechanism of the transition area is established according to security requirements of the first cloud when the first operation verification passes; and establishing network connection between the transition region and the original region.

In some embodiments, the cloud migration method further comprises: performing second operation verification on a second cloud formed by the plurality of migration modules and the plurality of original modules by utilizing the association relationship between each migration module and other migration modules and the plurality of original modules; and under the condition that the second operation verification is failed, performing the first operation verification on each migration module again.

In some embodiments, the cloud migration method further comprises: performing stability verification on a second cloud consisting of a plurality of migration modules and a plurality of original modules under the condition that the second operation verification is passed; and deleting the migration module in the first cloud under the condition that the stability verification is passed.

In some embodiments, the first cloud is a public cloud, the second cloud is a private cloud, and the migration module in the transition area is deleted if the stability verification passes. According to a second aspect of the present disclosure, there is provided a cloud migration apparatus of a mixed cloud including a first cloud and a second cloud having different cloud types, including: a first dividing unit configured to divide each first business system in the first cloud into a plurality of migration modules; a second dividing unit configured to divide each second service system in the second cloud into a plurality of original modules; a determining unit configured to determine an association relationship between each migration module and the other migration modules and the plurality of original modules; a replication unit configured to replicate the plurality of migration modules into the second cloud; a rebuilding unit configured to rebuild, in the second cloud, an association relationship between each migration module and the other migration modules and the plurality of original modules according to the determined association relationship between each migration module and the other migration modules and the plurality of original modules.

According to a third aspect of the present disclosure, there is provided a cloud migration apparatus for a hybrid cloud, including: a memory; and a processor coupled to the memory, the processor configured to perform the cloud migration method of the hybrid cloud of any of the above embodiments based on the instructions stored in the memory.

According to a fourth aspect of the present disclosure, a computer-storable medium has stored thereon computer program instructions which, when executed by a processor, implement the cloud migration method of a hybrid cloud as described in any of the embodiments above.

In the embodiment, the flexibility of the hybrid cloud system is improved, and the reliability and effectiveness of cloud migration are ensured.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.

The present disclosure may be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:

fig. 1 illustrates a flow diagram of a method of cloud migration for a hybrid cloud in accordance with some embodiments of the present disclosure;

fig. 2 illustrates a system block diagram of a cloud migration apparatus of a hybrid cloud in accordance with some embodiments of the present disclosure;

fig. 3 illustrates a schematic diagram of hybrid cloud system state transitions in a cloud migration method of a hybrid cloud in accordance with some embodiments of the present disclosure;

fig. 4 illustrates a schematic diagram of module partitioning of a business system of a hybrid cloud in a cloud migration method of the hybrid cloud according to some embodiments of the present disclosure;

FIG. 5 illustrates a schematic diagram of a hybrid cloud transitioning from a hybrid state to a separate state in a cloud migration method of a hybrid cloud in accordance with some embodiments of the present disclosure;

fig. 6A illustrates a schematic diagram of a hybrid cloud transitioning from a detached state to a verified state in a cloud migration method for a hybrid cloud in accordance with some embodiments of the present disclosure where a first cloud is a public cloud and a second cloud is a private cloud;

fig. 6B illustrates a schematic diagram of a hybrid cloud transitioning from a detached state to a verified state in a cloud migration method for a hybrid cloud in accordance with some embodiments of the present disclosure where a first cloud is a private cloud and a second cloud is a public cloud;

fig. 7A illustrates a schematic diagram of a hybrid cloud transitioning from a verification state to a final state in a cloud migration method for a hybrid cloud in accordance with some embodiments of the present disclosure where a first cloud is a public cloud and a second cloud is a private cloud;

FIG. 7B illustrates a schematic diagram of a hybrid cloud transitioning from a verification state to a final state in a cloud migration method for a hybrid cloud in accordance with some embodiments of the present disclosure where a first cloud is a private cloud and a second cloud is a public cloud;

fig. 8 illustrates a block diagram of a cloud migration apparatus of a hybrid cloud corresponding to the cloud migration method of the hybrid cloud illustrated in fig. 1, according to some embodiments of the present disclosure;

FIG. 9 illustrates a block diagram of a cloud migration apparatus for a hybrid cloud in accordance with further embodiments of the present disclosure;

FIG. 10 illustrates a block diagram of a computer system for implementing some embodiments of the present disclosure.

Detailed Description

Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.

The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses.

Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.

In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

The cloud migration method of the hybrid cloud in some embodiments will be described in detail below in conjunction with fig. 1 and 2.

Fig. 1 illustrates a flow diagram of a method of cloud migration for a hybrid cloud in accordance with some embodiments of the present disclosure.

Fig. 2 illustrates a system block diagram of a cloud migration apparatus of a hybrid cloud according to some embodiments of the present disclosure.

As shown in fig. 1, the cloud migration method of the hybrid cloud includes steps S110 to S150. The hybrid cloud includes a first cloud and a second cloud that are different in cloud type.

In step S110, each first business system in the first cloud is divided into a plurality of migration modules. For example, the migration module is a separate functional module in the first business system.

In step S120, each second service system in the second cloud is divided into a plurality of original modules. For example, the original module is an independent functional module in the second service system.

The functional modules in the above steps S110 and S120 may include a storage module, a query module, and the like.

For example, in step S110 and step S120, the business system in the hybrid cloud is scanned by using the system partitioning component in the hybrid cloud processing unit shown in fig. 2, and the business system is partitioned into a plurality of migration modules and original modules. The business system can be a relatively independent application system and a relatively independent service system. And determining which application systems and services are on a private cloud platform and which application systems and services are on a public cloud platform through the system planning sub-unit, and determining each independent function module of each business system.

Returning to fig. 1, in step S130, the association relationship between each migration module and other migration modules and a plurality of original modules is determined. For example, a dynamic library analysis tool dependency walker is utilized to determine associations between each migrated module and other migrated modules and multiple legacy modules.

In the above step S130, the relationship detection and analysis subunit scans the relationship between the independent modules, such as the mutual data transmission, function call, and flow sequence, to determine the relationship between each migration module and other migration modules and the plurality of original modules.

Further, in the case that the environment dependency information of the migration module is not present in the second cloud, the environment dependency information of the migration module in the first cloud is determined.

For example, with the dependency detection and analysis subunit shown in FIG. 2, the environment dependency information of the migration module in the first cloud is determined. Specifically, the environment dependency information of each independent module is scanned by using the dependency detection and analysis subunit, so that the environment dependency information of the migration module in the first cloud is determined. For example, environment dependency information can be divided into functional dependencies and data dependencies. Functional dependencies include, but are not limited to, module-dependent operating system functions, system libraries, drivers, hardware functions, system infrastructure components, programming framework components, and the like, and application system and service infrastructure dependencies. Data dependencies include, but are not limited to, data sources, data files, data stores, data backups.

Returning to fig. 1, in step S140, the plurality of migration modules are copied into the second cloud. In step S140 described above, the plurality of migration modules are copied into the second cloud, for example, using the migration module replication sub-unit shown in fig. 2.

Further, in the absence of environment dependency information for the migration module in the second cloud, the environment dependency information is copied into the second cloud.

Further, the second cloud is divided into a transition region and an original region. The transition zone includes a plurality of migration modules and the original zone includes a plurality of original modules. For example, after copying the plurality of migration modules into the second cloud, the environment dependency information and related resources of each migration module in the first cloud are copied into the transition area. For example, the related resources include at least one of computing resources and data resources. For example, the computing resources include, but are not limited to, cloud hosts, containers associated with business systems in a hybrid cloud. Data resources include, but are not limited to, databases, block stores associated with business systems in a hybrid cloud.

For example, the environment dependency information and related resources of each migration module in the first cloud are copied to the transition area using the environment dependency information migration subunit and related resource migration subunit shown in fig. 2. The principle of replication is to keep the relevant resources of the functional module to a minimum. For example, 10 instances are originally needed to complete the same data calculation operation, only 2 instances are migrated for verifying the function and concurrency, the scale is expanded as required after the verification is passed, and the data consistency and integrity of related resources are guaranteed by the copying process.

Further, when the first cloud is a private cloud and the second cloud is a public cloud, desensitizing the relevant resources, and copying the desensitized relevant resources to the second cloud. Desensitization processing may include, but is not limited to, encryption processing or performing deletion operations on sensitive data in the associated resource. For example, desensitization processing is performed on the relevant resources using a desensitization subunit as shown by the dashed box in fig. 2. And the safety of data is ensured through desensitization treatment.

Returning to fig. 1, in step S150, in the second cloud, the association relationship between each migration module and the other migration modules and the plurality of original modules is reestablished according to the association relationship between each migration module and the other migration modules and the plurality of original modules.

In the step S150, the dependency and relationship rebuilding subunit shown in fig. 2 is used to rebuild the association relationship between each migration module and other migration modules and the plurality of original modules.

Further, after the incidence relation between each migration module and other migration modules and among the plurality of original modules is reestablished, the incidence relation reestablished in the second cloud is used for carrying out first operation verification on each migration module.

For example, a first run verification is performed using the reconstruction verification subunit as shown in FIG. 2. For example, by designing a test case, a functional verification is performed on each migration module, and whether the function of each migration module is complete and correct is verified, so as to implement a first operation verification.

And under the condition that the first operation verification fails, re-determining the association relationship among each migration module, other migration modules and a plurality of original modules, and re-performing the first operation verification on each migration module.

For example, when the first operation verification fails, the operation and maintenance management subunit in the underlying support unit shown in fig. 2 is used to notify the error processing subunit of the hybrid cloud processing unit that the first operation verification fails, so that the error processing subunit rolls back the migration module that fails in the first operation verification to the state before the association relationship is reestablished according to the notification, and notifies the relationship detection and analysis subunit to redetermine the association relationship between each migration module and other migration modules and the plurality of original modules, and further, the reestablishment verification subunit is used to perform the first operation verification on each migration module again.

Further, in the case that the environment dependency information of the migration module is not present in the second cloud, after the environment dependency information and the related resources of each migration module in the first cloud are copied to the transition area, the environment dependency information and the related resources are utilized to perform the first operation verification on each migration module.

And in the case that the first operation verification fails, re-determining the environment dependence information of each migration module, and re-performing the first operation verification on each migration module.

For example, in the case that the first operation verification fails, the operation and maintenance management subunit in the underlying support unit as shown in fig. 2 is used to notify the error processing subunit that the first operation verification fails, so that the error processing subunit rolls back the migration module that the first operation verification fails to the state before copying the environment dependency information and the related resources according to the notification, notifies the dependency detection and analysis subunit to redetermine the environment dependency information of each migration module, and further uses the reconstruction verification subunit to perform the first operation verification again on each migration module.

Further, when the first cloud is a public cloud, the second cloud is a private cloud, and the first operation verification passes, copying the module to be migrated in the transition area to the original area.

Further, under the condition that the first cloud is a private cloud, the second cloud is a public cloud, and the first operation verification passes, a security mechanism of the transition area is established according to the security requirement of the first cloud. For example, the security requirements include network security requirements, data security requirements, access control security requirements, and the like. Specifically, a firewall tool, an intrusion detection tool, an access control server, a data encryption device, etc. are utilized to establish a security mechanism for the transition zone.

After the security mechanism of the transition area is established, the network connection between the transition area and the original area is established. For example, the network topology conversion management subunit of the second cloud processing unit shown in fig. 2 is used to convert the network topology of the hybrid cloud to the second cloud, and establish a network connection between the transition area and the original area, so as to maintain data transmission of each module of the private cloud.

For example, after the first operation verification, the virus and Trojan horse killing is performed on the transition region by using the virus and Trojan horse killing subunit shown in FIG. 2. Because the internal system is usually isolated from the outside for a long time, the versions of system viruses and Trojan horse libraries can be old, viruses and Trojan horses can exist in the system, and the viruses, the Trojan horses and the like are searched and killed to prevent the risk from being brought into a new platform.

And after the first operation verification is passed, performing second operation verification on a second cloud formed by the plurality of migration modules and the plurality of original modules by utilizing the association relation among each migration module, other migration modules and the plurality of original modules.

For example, a second run verification is performed using the reconstruction verification subunit as shown in FIG. 2. For example, the second operation verification includes, but is not limited to, a functional verification and a performance verification. Specifically, the test case is used to determine whether the function and performance of the second cloud composed of the plurality of migration modules and the plurality of original modules meet the target requirements.

And in the case that the second operation verification fails, performing the first operation verification on each migration module again. For example, the operation and maintenance management subunit shown in fig. 2 is used to notify the error processing subunit that the second operation verification fails, so that the error processing subunit rolls back each migration module to the state during the first operation verification according to the notification, and notifies the rebuild verification subunit to perform the first operation verification on each migration module again.

And under the condition that the second operation verification is passed, performing stability verification on a second cloud formed by the plurality of migration modules and the plurality of original modules. For example, the stability verification is performed by using the networking verification subunit and the second cloud verification subunit of the second cloud processing unit shown in fig. 2.

And deleting the migration module in the first cloud under the condition that the stability verification is passed. For example, the first cloud is a public cloud, the second cloud is a private cloud, and in the case that the stability verification passes, the migration module in the transition area is deleted. For example, the migration module in the first cloud and the transition zone is deleted using the deletion subunit shown in fig. 2.

Further, the dynamic resource management subunit shown in fig. 2 may also be used to provide a multi-platform resource management function for migration, for example, to manage computing resources, data resources, and network resources of each cloud. In particular, the affiliations between different clouds and computing resources, data resources, network resources are managed.

Further, the security management subunit shown in fig. 2 may also be used to perform security check on the hybrid cloud platform during the migration process and after the migration, so as to ensure the security of the platform during the migration process and after the migration.

Further, the number of related resources in the second cloud can be increased by using the resource dynamic change management subunit of the second cloud processing unit shown in fig. 2, so as to adapt to the service operation requirement and the service development of the second cloud.

Further, during the cloud migration process, the mixed cloud system can be marked as 4 states of a mixed state, a separated state, a verification state and a final state.

The mixed state is a stable state of the mixed cloud before cloud migration is performed.

The separation state is a system state for migrating the migration module and the association relation on the first cloud in the mixed cloud and the environment dependence to the transition region established in the second cloud and performing first operation verification. And the migration module and each original module of the second cloud in the original mixed cloud keep a data interaction relationship.

And the verification state is a system state for further fusing the related resources of the transition region and the second cloud and performing second operation verification. For example, the second operation verification can be performed by using a smaller number of related resources transferred from the first cloud, and the number of the related resources can support verification of system functions, performance and security, so that the situation of high error rollback complexity caused by a large number of transferred related resources can be avoided.

And the final state is the final state of the hybrid cloud system, and related resources on the second cloud are expanded according to the service requirements and subjected to stability verification to achieve the stable state of the second cloud. For example, the final states include a private state and a public state.

For example, the cloud platform state management subunit shown in fig. 2 may be used to check the status of the hybrid cloud platform system and decide whether to perform the next state transition step of cloud migration. For example, a decision is made whether the hybrid cloud system is to enter from one state to another.

The specific process of the state transition of the hybrid cloud system will be described in detail below with reference to fig. 3.

Fig. 3 illustrates a schematic diagram of hybrid cloud system state transitions in a cloud migration method of a hybrid cloud according to some embodiments of the present disclosure.

As shown in fig. 3, the mixed state of the mixed cloud may transition to the separated state through a module migration process. If a system error occurs while performing the first operation verification in the split state, the system error can be returned to the mixed state through an error rollback process. If the first operation verification is carried out in the separation state, the transition state is transited to the verification state by carrying out safe communication on the transition region and the original region or carrying out partition combination on the transition region and the original region. And performing second operation verification in the verification state, namely performing all-around detection and verification on the system, returning the hybrid cloud system to the separation state through an error rollback process if the second operation verification has errors, and performing the first operation verification again according to the error condition. And if the second operation verification is carried out in the verification state, the resources on the second cloud are expanded and the stability verification is carried out, so that the mixed cloud reaches the final state.

Through the design of carrying out a plurality of states to mixed cloud system, guaranteed to carry out the steady of cloud migration process in mixed cloud system, prevent to carry out the in-process of cloud migration and destroy former mixed cloud system in mixed cloud system, reduce a series of system problems that the cloud migration in-process leads to. In order to ensure that the mixed cloud system can roll back, the original migration module needs to be reserved, and when the mixed cloud system reaches the final stable state, the reserved migration module, the environment dependence information, the related resources and the like are deleted step by step.

A specific process of module division of the service system of the hybrid cloud in the cloud migration method of the hybrid cloud will be described in detail below with reference to fig. 4.

Fig. 4 illustrates a schematic diagram of module partitioning of a business system of a hybrid cloud in a cloud migration method of the hybrid cloud according to some embodiments of the present disclosure.

As shown in fig. 4, the main flow of module division of all business systems of the hybrid cloud is as follows.

First, all business systems of the hybrid cloud are scanned and parsed. For example, the business system may be an office system, a financial management system, a personnel management system, a website system, a resource query system, a resource management system, and the like. For example, the business system in the first cloud is a financial management system, and the business system in the second cloud is an office system. The office systems in the second cloud are divided into independent function modules (modules) m1, m2, m3 and m4, which serve as original modules. The financial management system in the first cloud is divided into independent functional modules m5, m6 and m7 as migration modules.

Next, the association (relationship) between the individual modules is analyzed. For example, the associations between the original module m1 and the other original and migrated modules in the second cloud include, but are not limited to, r1, r2, and the associations between the migrated module m5 and the other migrated and original modules in the first cloud include, but are not limited to, r 3. The association relationship between the modules is only schematically shown in the figure, and the association relationship corresponding to the other original modules m2, m3, m4 and the other migration modules m6, m7 is not shown in the figure, but is similar to the case of the original module m1 and the migration module m 5.

For example, an associative relationship is a relationship between two or more modules that require interaction for their calls, accesses, controls, etc. For example, a dynamic library analysis tool dependency walker is utilized to determine associations between each migrated module and other migrated modules and multiple legacy modules.

Then, the functional dependence (Dependency) of each module is analyzed. For example, the functional dependency of the original module m1 in the second cloud includes, but is not limited to, d2, and the functional dependency of the migrated module m5 in the first cloud includes, but is not limited to, d 1. The functional dependencies of the modules are only schematically shown in the figure, and the functional dependencies corresponding to the other original modules m2, m3, m4 and the other migration modules m6, m7 are not shown in the figure, but are similar to the case of the original module m1 and the migration module m 5. For example, the functional dependency is determined using the dynamic library analysis tool dependency walker.

Finally, the data dependencies of the respective modules are analyzed, for example, the data dependency of the original module m1 in the second cloud includes but is not limited to d3, and the data dependency of the migrated module m5 in the first cloud includes but is not limited to d 4. The data dependencies of the modules are only schematically shown in the figure, and the data dependencies corresponding to the other original modules m2, m3, m4 and the other migrated modules m6, m7 are not shown in the figure, but are similar to the case of the original module m1 and the migrated module m 5. For example, the functional dependency is determined using the dynamic library analysis tool dependency walker.

So far, the mixed cloud is still in a mixed state.

A specific process of converting the mixed cloud from the mixed state to the separated state in the cloud migration method of the mixed cloud will be described in detail below with reference to fig. 5.

Fig. 5 illustrates a schematic diagram of a hybrid cloud transitioning from a hybrid state to a separate state in a cloud migration method of the hybrid cloud in accordance with some embodiments of the present disclosure.

As shown in fig. 5, the main steps of the hybrid cloud transition from the hybrid state to the separate state are as follows.

First, a transition zone with a relatively independent network environment is created on the second cloud for carrying the migration module. And under the condition that the second cloud is the public cloud, the network of the transition area is temporarily not communicated with the original area.

Then, the functional dependence of the migration module, e.g., d1, and the data dependence, e.g., d4, are established in the transition zone.

Under the condition that the first cloud is a private cloud and the second cloud is a public cloud, desensitization processing is performed on data of resources related to the migration module, and then the computing resources, the data resources and the network topology related to the migration module such as m5, m6 and m7 are copied and migrated to the transition area by using the hybrid cloud management platform.

And finally, performing first operation verification on each migration module in the transition area, and eliminating possible intrusion security threats and security risks of viruses, trojans, worms and the like in each migration module in the transition area. And if the first operation passes the verification and the security threat and risk removal is successful, completing the partial flow. If the first operation passes the verification or the security threat and risk removal are unsuccessful, the problem is searched and positioned, and if the problem can be solved in a separated state, the problem is solved and the partial flow is completed. And if the problem cannot be solved in the separated state, rolling back the mixed cloud system to the mixed state, and performing the first operation verification again, and evaluating and eliminating the security risk.

A specific process of converting the hybrid cloud from the detached state to the verified state in the cloud migration method of the hybrid cloud in the case that the first cloud is the public cloud and the second cloud is the private cloud will be described in detail below with reference to fig. 6A.

Fig. 6A illustrates a schematic diagram of a hybrid cloud transitioning from a detached state to a verified state in a cloud migration method of the hybrid cloud according to some embodiments of the present disclosure in a case where a first cloud is a public cloud and a second cloud is a private cloud.

As shown in fig. 6A, in the case where the first cloud is a public cloud and the second cloud is a private cloud, the main steps of the hybrid cloud converting from the detached state to the verified state are as follows.

Firstly, the network of an original region on the private cloud is expanded, and the original region and the transition region are partitioned and merged, so that the original region can bear newly added migration modules and related resources.

Then, transferring each migration module in the transition area to the original area, and keeping the architecture design of high availability, elasticity and the like of resources in the migration module unchanged. And copying and migrating related instances such as a migration module, a function dependence, a data dependence and the like of the transition area to a subnet of the private cloud according to a minimum scale principle, and combining repeated function dependence and data dependence.

And then, reconstructing the association relationship between each migration module and other migration modules and the original modules on the private cloud.

And finally, carrying out second operation verification on an integral second cloud system formed by each migration module and the original module in the private cloud, testing and verifying functions, performance, safety, reliability, usability, expandability, maintainability and the like, and comprehensively checking the system condition after resource partition combination. And if the second operation passes the verification, finishing the flow of the part. And if the second operation verification fails, finding the reason in the verification state and solving the problem. If the problem can be solved in the verification state, the problem is solved and the partial flow is completed. And if the problem can not be solved in the verification state, rolling the system state back to the separation state, and reprocessing the system.

A specific process of converting the hybrid cloud from the detached state to the verified state in the cloud migration method of the hybrid cloud in the case that the first cloud is the private cloud and the second cloud is the public cloud will be described in detail below with reference to fig. 6B.

Fig. 6B illustrates a schematic diagram of a hybrid cloud transitioning from a detached state to a verified state in a cloud migration method of the hybrid cloud according to some embodiments of the present disclosure in a case where a first cloud is a private cloud and a second cloud is a public cloud.

As shown in fig. 6B, in the case where the first cloud is a private cloud and the second cloud is a public cloud, the main steps of the hybrid cloud converting from the detached state to the verified state are as follows.

Firstly, establishing a required safety mechanism in a transition area to form a safety area, and verifying the validity of the safety mechanism.

And secondly, establishing network connection between the original area and the safety area.

Then, the association relation r3 between each migration module and other migration modules and original modules on the public cloud is rebuilt.

And finally, carrying out second operation verification on an integral second cloud system formed by each migration module and the original module in the public cloud, testing and verifying functions, performance, safety, reliability, usability, expandability, maintainability and the like, and comprehensively checking the system condition after the safe communication is carried out on the transition area and the original area.

And if the second operation passes the verification, finishing the flow of the part. And if the second operation verification fails, finding the reason in the public verification state and solving the problem. If the problem can be solved in the verification state, the problem is solved and the partial flow is completed. And if the problem can not be solved in the verification state, rolling the system state back to the separation state, and reprocessing the system.

A specific process of the hybrid cloud converting from the verification state to the final state in the cloud migration method of the hybrid cloud in the case that the first cloud is a public cloud and the second cloud is a private cloud will be described in detail below with reference to fig. 7A.

Fig. 7A illustrates a schematic diagram of a hybrid cloud transitioning from a verification state to a final state in a cloud migration method of the hybrid cloud in a case where a first cloud is a public cloud and a second cloud is a private cloud, according to some embodiments of the present disclosure.

As shown in fig. 7A, in the case where the first cloud is a public cloud and the second cloud is a private cloud, the main steps of the hybrid cloud converting from the verification state to the final state are as follows. At this time, the final state is a private state.

First, the amount of resources of migration modules m5, m6, m7, etc. on the second cloud (i.e., the private cloud) is increased. For example, the number of cloud host instances is increased, the storage capacity is increased, the instance specification is increased, the network bandwidth is increased, and the like, so that the processing capacity of the second cloud system meets the design requirements of the private cloud.

And then, performing stability verification on a second cloud system consisting of a plurality of migration modules and a plurality of original modules. For example, after a second cloud system composed of a plurality of migration modules and a plurality of original modules operates for a period of time, if the system operates normally and no problem occurs, the original reserved migration modules m5, m6 and m7 on the transition area and the hybrid cloud are gradually cleared.

A specific process of the hybrid cloud converting from the verification state to the final state in the cloud migration method of the hybrid cloud in the case that the first cloud is a private cloud and the second cloud is a public cloud will be described in detail below with reference to fig. 7B.

Fig. 7B illustrates a schematic diagram of a hybrid cloud transitioning from a verification state to a final state in a cloud migration method for a hybrid cloud in accordance with some embodiments of the present disclosure in which a first cloud is a private cloud and a second cloud is a public cloud.

As shown in fig. 7B, in the case where the first cloud is a private cloud and the second cloud is a public cloud, the main steps of the hybrid cloud converting from the verification state to the final state are as follows. At this time, the final state is the public state.

First, the amount of resources of migration modules m5, m6, m7, etc. on the second cloud (i.e., public cloud) is increased. For example, the number of cloud host instances is increased, the storage capacity is increased, the instance specification is increased, the network bandwidth is increased, and the like, so that the processing capacity of the system can meet the design requirements of public clouds.

And then, performing stability verification on a second cloud system consisting of a plurality of migration modules and a plurality of original modules. For example, after a second cloud system composed of a plurality of migration modules and a plurality of original modules operates for a period of time, if the system operates normally and no problem occurs, the original reserved migration modules on the hybrid cloud, such as m5, m6 and m7, are gradually cleared.

Fig. 8 illustrates a block diagram of a cloud migration apparatus of a hybrid cloud corresponding to the cloud migration method of the hybrid cloud of fig. 1, according to some embodiments of the present disclosure.

As shown in fig. 8, the cloud migration apparatus 8 of the mixed cloud includes a first dividing unit 81, a second dividing unit 82, a determining unit 83, a copying unit 84, and a reconstructing unit 85. The hybrid cloud includes a first cloud and a second cloud that are different in cloud type.

The first dividing unit 81 is configured to divide each first business system in the first cloud into a plurality of migration modules, for example, to execute step S110 shown in fig. 1.

The second dividing unit 82 is configured to divide each second business system in the second cloud into a plurality of original modules, for example, perform step S120 shown in fig. 1.

For example, the first and second division units described above correspond to the system division sub-units shown in fig. 2.

The determining unit 83 is configured to determine the association relationship between each migrated module and other migrated modules and the plurality of original modules, for example, to execute step S130 shown in fig. 1.

The above-described determination unit 83 corresponds to, for example, the relationship detection and analysis subunit shown in fig. 2.

The copying unit 84 is configured to copy the plurality of migration modules into the second cloud, for example, to perform step S140 shown in fig. 1.

For example, the copy unit 84 described above corresponds to the migration module copy subunit shown in fig. 2.

The rebuilding unit 85 is configured to rebuild the association relationship between each migration module and the other migration modules and the plurality of original modules according to the association relationship between each migration module and the other migration modules and the plurality of original modules in the second cloud, for example, execute step S150 shown in fig. 1.

The reconstruction unit 85 described above corresponds to, for example, the dependency and relation reconstruction subunit shown in fig. 2.

Fig. 9 illustrates a block diagram of a cloud migration apparatus for a hybrid cloud according to further embodiments of the present disclosure.

As shown in fig. 9, the cloud migration apparatus 9 of the hybrid cloud includes a memory 91; and a processor 92 coupled to the memory 91, wherein the memory 91 is used for storing instructions for executing a corresponding embodiment of the cloud migration method of the hybrid cloud. The processor 92 is configured to perform a cloud migration method of a hybrid cloud in any of the embodiments of the present disclosure based on instructions stored in the memory 91.

As shown in FIG. 10, computer system 100 may be embodied in the form of a general purpose computing device. Computer system 100 includes a memory 1010, a processor 1020, and a bus 1000 that couples various system components.

The memory 1010 may include, for example, system memory, non-volatile storage media, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), and other programs. The system memory may include volatile storage media such as Random Access Memory (RAM) and/or cache memory. The non-volatile storage medium, for example, stores instructions to perform corresponding embodiments of at least one of the cloud migration methods of the hybrid cloud. Non-volatile storage media include, but are not limited to, magnetic disk storage, optical storage, flash memory, and the like.

The processor 1020 may be implemented as discrete hardware components, such as a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gates or transistors, or the like. Accordingly, each of the modules, such as the judging module and the determining module, may be implemented by a Central Processing Unit (CPU) executing instructions in a memory for performing the corresponding step, or may be implemented by a dedicated circuit for performing the corresponding step.

Bus 1000 may use any of a variety of bus architectures. For example, bus structures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, and Peripheral Component Interconnect (PCI) bus.

The computer system 100 may also include an input-output interface 1030, a network interface 1040, a storage interface 1050, and the like. These

interfaces

1030, 1040, 1050 and the memory 1010 and the processor 1020 may be connected by a bus 1000. The input/output interface 1030 may provide a connection interface for input/output devices such as a display, a mouse, and a keyboard. Network interface 1040 provides a connection interface for various networking devices. The storage interface 1050 provides a connection interface for external storage devices such as a floppy disk, a usb disk, and an SD card.

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable apparatus to produce a machine, such that the execution of the instructions by the processor results in an apparatus that implements the functions specified in the flowchart and/or block diagram block or blocks.

These computer-readable program instructions may also be stored in a computer-readable memory that can direct a computer to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart and/or block diagram block or blocks.

The present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects.

By the cloud migration method and device of the hybrid cloud and the computer storage medium in the embodiment, the flexibility of the hybrid cloud system is improved, and the reliability and effectiveness of cloud migration are guaranteed.

Thus far, a cloud migration method and apparatus, a computer-storable medium, of a hybrid cloud according to the present disclosure have been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.

Claims

1. A cloud migration method of a mixed cloud, the mixed cloud including a first cloud and a second cloud different in cloud type, the cloud migration method comprising:

dividing each first service system in the first cloud into a plurality of migration modules;

dividing each second service system in the second cloud into a plurality of original modules;

determining the incidence relation between each migration module and other migration modules and a plurality of original modules;

copying the plurality of migration modules into the second cloud; and

and in the second cloud, reestablishing the association relationship between each migration module and the other migration modules and the plurality of original modules according to the determined association relationship between each migration module and the other migration modules and the plurality of original modules.

2. The cloud migration method of claim 1, further comprising:

determining environment dependency information of the migration module in the first cloud; and

copying the environment dependency information into the second cloud.

3. The cloud migration method of claim 1,

the second cloud is divided into a transition region and an original region, the transition region including the plurality of migration modules, the original region including the plurality of original modules.

4. The cloud migration method of claim 3, further comprising:

performing first operation verification on each migration module by using the incidence relation reconstructed in the second cloud;

5. The cloud migration method of claim 4, further comprising:

copying environment dependency information and related resources of each migration module in the first cloud to the transition region;

performing first operation verification on each migration module by using the environment dependence information and related resources;

and under the condition that the first operation verification fails, re-determining the environment dependence information of each migration module, and re-performing the first operation verification on each migration module.

6. The cloud migration method according to claim 5, wherein the first cloud is a private cloud, the second cloud is a public cloud, desensitization processing is performed on the relevant resources, and the relevant resources after desensitization processing are copied to the second cloud.

7. The cloud migration method according to claim 4, wherein the first cloud is a public cloud, the second cloud is a private cloud, and the migration module in the transition area is copied to the original area if the first operation verification passes.

8. The cloud migration method according to claim 4, wherein the first cloud is a private cloud, the second cloud is a public cloud, and if the first operation verification passes, a security mechanism of the transition zone is established according to security requirements of the first cloud;

and establishing network connection between the transition region and the original region.

9. The cloud migration method of claim 7 or 8, further comprising:

performing second operation verification on a second cloud formed by the plurality of migration modules and the plurality of original modules by utilizing the association relationship between each migration module and other migration modules and the plurality of original modules;

and under the condition that the second operation verification is failed, performing the first operation verification on each migration module again.

10. The cloud migration method of claim 9, further comprising:

performing stability verification on a second cloud consisting of a plurality of migration modules and a plurality of original modules under the condition that the second operation verification is passed;

and deleting the migration module in the first cloud under the condition that the stability verification is passed.

11. The cloud migration method according to claim 10, wherein the first cloud is a public cloud, the second cloud is a private cloud, and in the case that the stability verification passes, the migration module in the transition area is deleted.

12. A cloud migration apparatus of a hybrid cloud, the hybrid cloud including a first cloud and a second cloud having different cloud types, comprising:

a first dividing unit configured to divide each first business system in the first cloud into a plurality of migration modules;

a second dividing unit configured to divide each second service system in the second cloud into a plurality of original modules;

a determining unit configured to determine an association relationship between each migration module and the other migration modules and the plurality of original modules;

a replication unit configured to replicate the plurality of migration modules into the second cloud;

a rebuilding unit configured to rebuild, in the second cloud, an association relationship between each migration module and the other migration modules and the plurality of original modules according to the determined association relationship between each migration module and the other migration modules and the plurality of original modules.

13. A cloud migration apparatus of a hybrid cloud, comprising:

a memory; and

a processor coupled to the memory, the processor configured to perform the method of cloud migration of the hybrid cloud of any of claims 1-11 based on instructions stored in the memory.

14. A computer-storable medium having stored thereon computer program instructions which, when executed by a processor, implement the method of cloud migration of a hybrid cloud according to any of claims 1 to 11.