Cloud system migration method and device, and hybrid cloud system

Abstract

The present disclosure relates to a cloud computing technical field, and to a cloud system migration method and device, and a hybrid cloud system, the method including: dividing each service system in a first cloud system into a plurality of modules; determining a relationship between a module to be migrated and other modules among the plurality of modules; copying the module among the plurality of modules to a second cloud system, where the type of the first cloud system is different from the type of the second cloud system; and establishing a relationship in the second cloud system to complete the migration of the first cloud system.

Description

Technical Field

[0001] Cross - reference to Related Applications This disclosure claims priority based on Chinese Patent Application No. 202010028201.8 filed on January 10, 2020, and the disclosure thereof is incorporated herein by reference in its entirety.

[0002] This disclosure relates to the technical field of cloud computing, and particularly to a migration method for a cloud system, a migration device for a cloud system, a hybrid cloud system, and a non - transitory computer - readable storage medium.

Background Art

[0003] Current cloud platforms are mainly divided into public clouds, private clouds, and hybrid clouds, etc. In industries such as media, education, and e - commerce, customers can choose to use a public cloud computing platform to improve system performance. In industries such as government, healthcare, and finance, customers can choose to use a private cloud computing platform to improve system security and controllability.

[0004] In related technologies, after determining the requirements of users, a cloud platform of the type required by the user, such as a public cloud or a private cloud, is directly constructed.

Summary of the Invention

Means for Solving the Problems

[0005] According to some embodiments of the present disclosure, there is provided a migration method for a cloud system, including: splitting a business system in a first cloud system into a plurality of modules; determining an association relation between a module to be migrated among the plurality of modules and other modules among the plurality of modules; replicating the module to be migrated among the plurality of modules to a second cloud system, wherein the first cloud system and the second cloud system are of different types; and establishing an association relation in the second cloud system to complete the migration of the first cloud system.

[0006] In some embodiments, the method further includes: determining a dependent environment of a 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.

[0007] In some embodiments, the method further includes: constructing a subnet corresponding to a topology structure related to a module to be migrated in the first cloud system in the second cloud system to complete the migration of the first cloud system.

[0008] In some embodiments, the step of replicating the module to be migrated among the plurality of modules to the second cloud system includes: 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 by using the association relation established in the test area; and replicating the module to be migrated in the first cloud system to the second cloud system when the first verification is passed.

[0009] In some embodiments, the method further includes re - determining the dependency relationship to re - perform the first operation verification if the first verification fails.

[0010] In some embodiments, the method includes replicating the dependent environment of the module to be migrated in the first cloud system and the resources related to the module to be migrated to a test area to perform the first operation verification, and re - determining the dependent environment to re - perform the first operation verification if the first verification fails.

[0011] In some embodiments, the method further includes constructing a subnet corresponding to the topology structure related to the module to be migrated in the first cloud system in the test area to perform the first operation verification.

[0012] In some embodiments, the method further includes performing a second operation verification on the module to be migrated in the second cloud system using the dependency relationship in a hybrid cloud system composed of the first cloud system and the second cloud system.

[0013] In some embodiments, the method further includes re - performing the first operation verification if the second verification fails.

[0014] In some embodiments, the first cloud system is a public cloud system, the second cloud system is a private cloud system, and the method includes verifying whether the protected data of the private cloud system is accessible through the public cloud system, and performing an isolation process on the protected data in the private cloud system if the protected data is accessible.

[0015] In some embodiments, the method further includes deleting the module to be migrated from the first cloud system when a hybrid cloud composed of the first cloud system and the second cloud system passes the operation test.

[0016] In some embodiments, the first cloud system is a private cloud system, the second cloud system is a public cloud system, and the method further includes isolating the protected data in the private cloud system from the public cloud system.

[0017] According to other embodiments of the present disclosure, a migration device for a cloud system is provided. The migration device includes a splitting unit for splitting a business system in a first cloud system into a plurality of modules, a determining unit for determining the relevance relationship between the module to be migrated among the plurality of modules and other modules among the plurality of modules, and a replication unit for replicating the module to be migrated among the plurality of modules to a second cloud system, wherein the first cloud system and the second cloud system are of different types, and an establishing unit for establishing a relevance relationship in the second cloud system to complete the migration of the first cloud system.

[0018] In some embodiments, the determining unit is used to determine the dependent environment of the module to be migrated in the first cloud system and to replicate the dependent environment to the second cloud system to complete the migration of the first cloud system.

[0019] In some embodiments, the establishing unit is used to construct a corresponding subnet for the second cloud system according to the related topology structure of the module to be migrated in the first cloud system to complete the migration of the first cloud system.

[0020] In some embodiments, the replication unit replicates the module to be migrated to the test area of the first cloud system. The apparatus further includes a verification unit for performing a first operation verification on the module to be migrated in the test area using the association relationship established in the test area. If the first verification passes, the replication unit replicates the module to be migrated in the first cloud system to the second cloud system.

[0021] In some embodiments, the determination unit is used to re-determine the association relationship in order to perform the first operation verification again when the first verification fails.

[0022] In some embodiments, for performing the first operation verification, the replication unit replicates the dependent environment and related resources of the module to be migrated in the first cloud system to the test area. When the first verification fails, the determination unit re-determines the dependent environment in order to perform the first operation verification again.

[0023] In some embodiments, the establishment unit is used to construct a subnet corresponding to the topology structure related to the module to be migrated in the first cloud system in the test area for performing the first operation verification.

[0024] In some embodiments, in a hybrid cloud system composed of the first cloud system and the second cloud system, the verification unit is used to perform a second operation verification on the module to be migrated in the second cloud system using the association relationship.

[0025] In some embodiments, the verification unit is used to perform the first operation verification again when the second verification fails.

[0026] In some embodiments, the first cloud system is a public cloud system, the second cloud system is a private cloud system, and the apparatus further comprises a verification unit for verifying whether the protected data of the private cloud system is accessible via the public cloud system, and a processing unit for performing an isolation process on the protected data in the private cloud system when the protected data is accessible.

[0027] In some embodiments, the apparatus further comprises a processing unit for deleting the module to be migrated from the first cloud system when the hybrid cloud composed of the first cloud system and the second cloud system passes the operation test.

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

[0029] According to still other embodiments of the present disclosure, a migration apparatus for a cloud system is provided. The migration apparatus comprises a memory and a processor coupled to the memory. The processor is configured to execute a migration method for a cloud system according to any one of the above embodiments based on instructions stored in the memory.

[0030] According to a further embodiment of the present disclosure, a hybrid cloud system comprising a migration apparatus for implementing a migration method for a cloud system according to any one of the above embodiments is provided.

[0031] According to still other embodiments of the present disclosure, there is provided a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements a migration method for a cloud system according to any one of the above embodiments.

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

[0033] The present disclosure will be more clearly understood from the following detailed description with reference to the accompanying drawings.

Brief Description of the Drawings

[0034]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

[0035] Next, various exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the relative arrangements, numerical expressions, and numerical values of the components and steps described in these examples do not limit the scope of the present invention.

[0036] At the same time, for the sake of simplicity of explanation, it should be understood that the dimensions of various parts shown in the drawings are not drawn at actual ratios.

[0037] The following description of at least one exemplary embodiment is, in fact, merely exemplary and is in no way intended as a limitation on the present invention, its applications, or its use.

[0038] Techniques, methods, and devices known to those skilled in the art may not be discussed in detail, but where appropriate, these techniques, methods, and devices should be regarded as part of this specification.

[0039] Any specific values in all the examples shown and discussed in this specification should be regarded merely as examples and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0040] It should be noted that similar reference numerals and characters are represented by similar ones in the accompanying drawings, and thus, once an article is defined in the drawings, it is not necessary to further explain it in the accompanying drawings.

[0041] As described above, as the business develops and the policy changes, the current needs of users will not be equal to the future needs of users. Therefore, the fixed-type cloud system in the related art cannot adapt to the changes in the business requirements of users.

[0042] The above related art has the following problems. The cloud system constructed as a fixed type cannot adapt to the changes in business requirements, resulting in a lack of flexibility of the cloud system. In view of this, the present disclosure provides a technical solution for cloud system migration, whereby the flexibility of the cloud system can be improved.

[0043] In some embodiments, the user may choose to expand the public cloud platform to a hybrid cloud platform due to a significant increase in the user's security requirements. For example, as the business develops and the industrial regulations and security requirements continue to increase, some powerful customers may choose to expand their public cloud platforms to hybrid cloud platforms.

[0044] For example, some media industries initially adopted a public cloud platform to meet the user requirements for a large number of simultaneous accesses. However, as intellectual property protection is strengthened and the requirements for user privacy and data security protection increase, some powerful media related to the national economy and people's lives have begun to build their own data centers. Moreover, the user may choose to replace the original platform architecture with a hybrid cloud, thereby not only protecting the security of core data but also being able to withstand extremely high peak-time network access traffic.

[0045] In some embodiments, due to the limited number of resources of the private cloud platform, the demands of some industries and sectors cannot be met by the private cloud or the private information system. In this case, the user may choose to expand the private cloud platform to a hybrid cloud platform.

[0046] For example, the 12306 China Railway website initially adopted a private cloud platform, and when the private cloud platform cannot withstand the service load during peak traffic hours, a hybrid cloud can be selected instead. In this way, not only can the security of core data be protected, but it is also possible to withstand extremely high peak network access traffic.

[0047] In view of the above problems, the technical solution of the present disclosure can realize the expansion of the cloud platform in the situation where a complex business / management system is built in the private cloud.

[0048] The present disclosure fully considers the technical risks that may be faced in the process of expanding a public cloud platform or a private cloud platform to a hybrid cloud platform, ensures that the cloud platform migration process is smooth and effective by a method including multiple state transition steps, ensures system security, and easily rolls back the steps with significant risks so that the business system can be ensured not to be damaged. For example, it can be realized by the following embodiments.

[0049] FIG. 1 shows a flowchart of some embodiments of the migration method for the cloud system of the present disclosure.

[0050] As shown in FIG. 1, the method includes step S10: splitting a plurality of modules, step S20: determining the relevance relationship, step S30: replicating the module to be migrated, and step S40: establishing the relevance relationship.

[0051] In step S10, the business system in the first cloud system is split into a plurality of modules. For example, the business system can be an office system, a financial management system, a personnel management system, a website, a resource inquiry system, and a resource management system, and each business system can be split into relatively independent functional modules.

[0052] In step S20, the relevance relationship between the module to be migrated and other modules among the plurality of modules is determined.

[0053] In step S30, the module to be migrated among the plurality of modules is replicated to the second cloud system, and the first cloud system and the second cloud system are of different types. For example, even if the first cloud system is a public cloud system, the second cloud system can be a private cloud system, or even if the first cloud system is a private cloud system, the second cloud system can be a public cloud system.

[0054] In this embodiment, step S30 may be executed as the step shown in FIG. 2.

[0055] FIG. 2 shows a flowchart of some embodiments of step S30 in FIG. 1.

[0056] As shown in FIG. 2, step S30 includes step S310: replicating the module to be migrated to the test area, step S320: performing the first verification, and step S330: replicating the module to be migrated to the second cloud system.

[0057] In step S310, the module to be migrated is replicated in the test area in the first cloud system.

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

[0059] In some embodiments, if the first verification fails, the association relationship is re-determined to perform the first operation verification again.

[0060] In some embodiments, the dependent environment and related resources of the module to be migrated in the first cloud system are replicated in the test area for the first verification, and if the first verification fails, the dependent environment is re-determined to perform the first operation verification again. For example, the related resources may be computing resources and data resources of the cloud system, etc.

[0061] In some embodiments, the dependent environment may include functional dependencies and data dependencies. For example, the functional dependency can be that the module itself does not have functions such as opening or sending files and needs to depend on the corresponding functions of another module.

[0062] In some embodiments, according to the related topology structure of the module to be migrated in the first cloud system, the corresponding subnet is constructed in the test area for the first operation verification. For example, the affiliation between the module to be migrated and the subnet in the second cloud system is the same as the affiliation between the module to be migrated and the subnet in the first cloud system.

[0063] In step S330, if the first verification is passed, the module to be migrated in the first cloud system is replicated to the second cloud system.

[0064] After the module to be migrated in the first cloud system is replicated to the second cloud system, the migration can continue through the remaining steps in FIG. 1.

[0065] In step S40, the association relationship is established in the second cloud system to complete the migration of the first cloud system.

[0066] In some embodiments, the dependent environment of the module to be migrated in the first cloud system is determined, and the dependent environment is replicated to the second cloud system to complete the migration of the first cloud system.

[0067] In some embodiments, the corresponding subnets are established for the second cloud system according to the related topology structure of the module to be migrated in the first cloud system to complete the migration of the first cloud system.

[0068] In some embodiments, the first cloud system is a public cloud system and the second cloud system is a private cloud system. In this case, it is verified whether the protected data of the private cloud system can be accessed through the public cloud system. If the protected data is accessible, isolation processing is performed on the protected data in the private cloud system.

[0069] In some embodiments, the first cloud system is a private cloud system and the second cloud system is a public cloud system, and the protected data in the private cloud system is isolated from the public cloud system.

[0070] In some embodiments, when a hybrid cloud composed of a first cloud system and a second cloud system passes an operation test, the module to be migrated is deleted from the first cloud system.

[0071] In some embodiments, in a hybrid cloud system composed of a first cloud system and a second cloud system, a second operation verification is performed on the module to be migrated in the second cloud system using a relevance relationship.

[0072] In some embodiments, if the second verification fails, the first operation verification is performed again.

[0073] FIG. 3 shows a schematic diagram of some embodiments of a migration device for the cloud system of the present disclosure.

[0074] As shown in FIG. 3, the migration device may include a base support module, a first cloud processing module, an extension support module, and a second cloud processing module.

[0075] In some embodiments, the main function of the base support module is to provide overall base support for the expansion from the first cloud architecture to the hybrid cloud architecture. The base support module may include a cloud platform status management module, a dynamic resource management tool, an operation / maintenance management module, and a security management module.

[0076] For example, the cloud platform status management module mainly checks the status of the cloud platform system, determines whether to proceed to the next expansion step, the dynamic resource management tool provides a multi-platform resource management function for cloud platform expansion, the operation / maintenance management module mainly undertakes the integrated operation and maintenance management before and after cloud platform expansion, and the security management module mainly undertakes the security of the cloud platform during and after cloud platform expansion.

[0077] In some embodiments, the main function of the first cloud processing module is to perform processing on each system in the first cloud before system architecture expansion so as to ensure that the expansion does not cause system problems. The first cloud processing module may include a system segmentation module, a dependency detection / analysis module, a relationship detection / analysis module, a decoupling / separation module, a computing resource separation management unit, a data resource separation management unit, a separation verification module, and an error handling module.

[0078] For example, the system segmentation module scans relatively independent application systems and services in the system, determines the boundaries of independent application systems, services, and their related resources, and formulates a system segmentation plan to determine which application systems and services will remain in the public cloud system platform and which application systems and services will be expanded to the private cloud platform.

[0079] For example, the dependency detection / analysis module scans the system dependencies of each independent module, including functional dependencies and data dependencies. Functional dependencies include the basic dependencies of application systems and services, such as operating system functions, system libraries, drivers, hardware functions, system basic components, and programming framework components that the module depends on. Data dependencies include data sources, data files, data storage, and data backups, etc.

[0080] For example, the relationship detection / analysis module scans the interrelationships between various independent modules, such as mutual data transmission, function calls, and processing sequences.

[0081] For example, after determining the dependencies and relationships, the decoupling / separation module reorganizes the system dependencies required for the modules to be separated so that the modules can operate independently, maintains the relationships between those modules and other modules, and updates the corresponding modules if the relationships need to be changed.

[0082] For example, the computing resource separation management unit is responsible for separating the computing resources (such as cloud hosts, containers, etc.) related to the original independent application system in the first cloud, replicating and migrating a part of the computing resources that need to be separated to a transition space (test area) separately allocated in the public cloud, and ensuring that the functions and data on which the computing resources depend are built together in the transition space.

[0083] For example, the data resource separation management unit is responsible for separating data resources (such as databases and block storage) related to the original independent application system in the first cloud, replicating and migrating a part of the data resources that need to be separated to a transition space separately allocated in the first cloud, and ensuring data consistency and integrity.

[0084] For example, the separation verification module is responsible for verifying whether the functions and performance of the system can meet the target requirements after the computing resources and data resources are separated into the transition space.

[0085] For example, the error handling module is responsible for rolling back the failed disconnection module to its initial error-free state.

[0086] In some embodiments, the extension support module is mainly used to provide extension support during the process of expanding the network of the first cloud to the second cloud, and to assist in completing the verification of the system. The extension support module includes a network topology conversion management module, a networking verification module, and a hybrid verification module.

[0087] For example, the network topology conversion management module is responsible for expanding the network topology to the second cloud according to the original network topology of the first cloud, and maintaining the data transmission of the related modules between the second cloud and the first cloud. When the first cloud is a private cloud and the second cloud is a public cloud, a part of the private cloud that requires security isolation can be separated from the private cloud, so that the public cloud resources can access the network transmission interface module of the private cloud for isolation.

[0088] For example, the networking verification module verifies the connectivity and network bandwidth of the newly formed hybrid cloud network, and verifies whether the data transmission between the isolated resources of the second cloud and the network connection module of the first cloud is normal.

[0089] For example, the hybrid verification module is mainly responsible for verifying the functions and performance of the systems related to the hybrid cloud, as well as verifying the effectiveness of the data isolation mechanism and the security mechanism.

[0090] In some embodiments, the main function of the second cloud processing module is to manage the dynamically changed resources of the second cloud. The second cloud processing module mainly includes a private cloud resource dynamic change management module. When the second cloud is a private cloud, the second cloud processing module further includes a data security verification module.

[0091] For example, the private cloud resource dynamic change management module is mainly responsible for gradually expanding the number of resources in the second cloud; and allocating on-demand private cloud resources to meet business requirements and business development.

[0092] For example, the data security verification module is mainly responsible for verifying whether the involved data security mechanism has the effect of security isolation after the private cloud is isolated from the public cloud interface module.

[0093] In some embodiments, during the transition from the first cloud to the hybrid cloud, the entire system is mainly divided into four states according to the distribution of system resources. For example, the states mainly include the original state, the separated state, the hybrid verification state, and the hybrid state. The transitions between the various states of the system can be shown as in Figure 4.

[0094] Figure 4 shows a schematic diagram of some embodiments of a migration method for a cloud system of the present disclosure.

[0095] As shown in Figure 4, the original state is a stable state of the first cloud before system expansion, and the separated state is a system state in which some resources of the first cloud are separated from the first cloud, but the data interaction between the separated first cloud resources and the original first cloud is maintained.

[0096] The hybrid verification state is a state in which the separated module has been migrated to the second cloud. As long as the number of resources can support the verification of system functions and performance, only a smaller amount of resources are left in the second cloud.

[0097] The hybrid state is the final state of the system in which the resources for the second cloud are expanded according to business requirements to achieve a stable state of the hybrid cloud system.

[0098] The original state of the first cloud can transition to the separated state through module separation processing. If a system error occurs during the verification of the separated state, the system can be restored to the original state through error rollback processing.

[0099] If the separated state is correctly verified, the system can transition to the hybrid verification state through module migration. The system is fully tested and verified in the hybrid verification state. If there are errors in the verification, the system can roll back to the separated state and be reprocessed according to the errors. If the verification is correct in the hybrid verification state, the resources for the second cloud will be expanded, that is, the scale of the system for the second cloud will be expanded to form the final hybrid state.

[0100] In this way, through the design of multiple states, the stability of the system expansion process can be ensured, and system problems caused by the original system being destroyed during the system expansion process can be prevented. In order to ensure that the system can be reliably rolled back, it is necessary to reserve the original system modules. When the system reaches the final stable state, the reserved resources can be gradually recycled.

[0101] In some embodiments, before expanding the first cloud system, it is necessary to know the basic situation of each system operating in the first cloud. In this way, as the basis for resource expansion for the second cloud, segmentation of independent modules can be performed. For example, the module segmentation of the system in the original state can be realized by the embodiment in FIG. 5.

[0102] FIG. 5 shows a schematic diagram of another embodiment of the migration method for the cloud system of the present disclosure.

[0103] As shown in FIG. 5, the process of system module segmentation is substantially as follows.

[0104] All business program systems in the first cloud system are scanned and analyzed. For example, the business program systems can be a transaction system, a financial management system, a personnel management system, a website, a resource inquiry system, and a resource management system, etc. The independent modules of the determined business program systems (the modules of the determined business program systems) are represented as m1 to m8. The related resources of independent modules such as computing resources, data resources, and network resources can be determined.

[0105] The relationships between various modules are analyzed. For example, the association relationships r1, r2, r3 between m1 to m8 can be determined. The association relationship is a relationship of interaction such as call, access, and control required between two or more modules.

[0106] The functional dependencies (dependencies of various modules) of various modules are analyzed. For example, the functional dependencies can be denoted as d1, d2, etc.

[0107] The data dependencies of various modules are analyzed. For example, the data dependencies can be denoted as d3, d4, etc.

[0108] According to the need for business expansion of the customers in the first cloud and the segmentation of the modules, the modules that need to be extended to the second cloud, such as m3, m6, and m8, are determined; the functional dependencies d1 and data dependencies d4 of these modules are determined; the association relationship r3 between these modules and the modules held in the first cloud environment is determined.

[0109] In some embodiments, before extending some modules to the second cloud, a transition area (test area) is created in the original first cloud to temporarily process the modules to be extended and facilitate the verification of module separation. For example, the transition from the original state to the separated state can be realized by the embodiment of FIG. 6.

[0110] FIG. 6 shows a schematic diagram of still another embodiment of the migration method for the cloud system of the present disclosure.

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

[0112] It can be determined that the modules to be extended to the second cloud are m3, m6, and m8 according to the user's requirements; their related functional dependencies and data dependencies are d1 and d4; and they have an association relationship r3 with the modules held in the public cloud.

[0113] A transition area where the network environment is relatively independent from the original area is created in the first cloud. The transition area is used to carry the modules to be extended. The functional dependency d1 and data dependency d4 of the modules to be extended (modules to be migrated) are established in the transition area. The related resources (such as computing resources and data resources) and network topology of the modules m3, m6, and m8 to be extended are replicated to the resources in the transition area. The association relationship (r3) between the modules to be extended and the modules in the original area is established.

[0114] The modules m3, m6, and m8 to be extended are activated and configured; operation tests and verifications are performed within the first cloud from the perspectives of function, performance, security, and reliability. If the tests and verifications are passed, this process is completed; if the tests and verifications fail, the problems are pursued and identified.

[0115] If the problems can be solved in a separated state, the problems are solved and this process is completed; if the problems cannot be solved in a separated state, the system is rolled back to the original state and the steps of analysis, evaluation, and processing are performed again.

[0116] In some embodiments, a system that has passed verification in a separated state serves as a basis for further expansion of the system. For safety and resource cost considerations, in the process of expanding to a hybrid cloud, the separated state is first transitioned to a hybrid verification state, where the validity of the expansion is verified using a small amount of resources. For example, the transition from the separated state to the hybrid verification state can be realized by the embodiment of FIG. 7.

[0117] FIG. 7 shows a schematic diagram of a further embodiment of a migration method for a cloud system of the present disclosure.

[0118] As shown in FIG. 7, the process of realizing the transition from the separated state to the hybrid verification state by expanding from the transition region to the second cloud system is substantially as follows.

[0119] A hybrid cloud management platform is constructed for the first cloud platform. A network path between the first cloud and the second cloud is established to verify the network connection between the first cloud and the second cloud.

[0120] A subnet similar to the subnet in the transition zone is constructed in the second cloud, and the subnet is ensured to be of a scale that can surely withstand future services. Using the hybrid cloud management platform, modules (m3, m6, m8), functional dependencies d1, data dependencies d3, and other related instances in the transition region are replicated to the subnet constructed for the second cloud according to the principle of minimum scale, migrated, and the association relationship r3 between the modules in the second cloud and the modules in the public cloud is reconstructed.

[0121] The entire system formed by the modules (m3, m6, m8) in the second cloud and the modules (such as m1 - m8) in the first cloud is verified. Tests and verifications are conducted from the perspectives of functions, performance, security, reliability, availability, scalability, and maintainability, etc., in order to comprehensively test the system state after resource migration. If the verification passes, this process is completed; if the verification fails, the cause is pursued to resolve the problem in the hybrid verification state.

[0122] If the problem can be resolved in the hybrid verification state, the problem is resolved and this process is completed. If the problem cannot be resolved in the hybrid verification state, the system is rolled back to a separate state to re - perform the processing on the system.

[0123] In some embodiments, if the system passes the tests and verifications in the hybrid verification state, the overall configuration of the hybrid cloud architecture is substantially successful. Next, the number of resources in the second cloud can be expanded to meet business needs. For example, the transition from the hybrid verification state to the hybrid state can be realized by the embodiment of FIG. 8.

[0124] FIG. 8 shows a schematic diagram of a further embodiment of the migration method for the cloud system of the present disclosure.

[0125] As shown in FIG. 8, the process of transitioning from the hybrid verification state to the hybrid state by resource expansion is substantially as follows.

[0126] If the system bandwidth is adjustable, the network bandwidth between the first cloud and the second cloud can be increased to meet the bandwidth requirements for business data transmission.

[0127] The amounts of resources of modules m3, m6, and m8 to be extended in the second cloud can be increased. For example, the number of cloud host instances, storage capacity, instance size, network bandwidth, etc. can be increased so that the processing capacity of the system can meet the design requirements of the hybrid cloud.

[0128] After the system has operated normally for a certain period without any problems, modules m3, m6, and m8 originally reserved for the first cloud are gradually removed, and then this process is completed.

[0129] In some embodiments, when the first cloud system is a public cloud system and the second cloud system is a private cloud system, the data security for the private cloud can be verified by the experimental access from the public cloud to the data to be protected in the private cloud.

[0130] For example, the access results can be viewed. If the data that needs to be protected is accessible from the public cloud, data isolation and protection measures should be added in the private cloud. After data isolation and successful security verification, if the bandwidth is adjustable, the network bandwidth between the public cloud and the private cloud is increased to meet the bandwidth requirements for business data transmission.

[0131] In the above embodiments, a complete and effective method for expanding from the first cloud platform to the hybrid cloud platform and expanding the system for the platform is proposed.

[0132] The process of expanding the entire system is controlled by the method of cloud platform state transition. Two verifiable cloud platform states, namely, the separated state and the hybrid verification state, are proposed. In this way, module expansion makes the implementation easier and ensures the convenience of processing when expansion problems occur.

[0133] The system for the cloud platform is divided into modules, dependencies, and relevance relationships, thereby making it easier to resolve complex systems and making system expansion more convenient and effective.

[0134] In the above embodiment, the migration of the module to be migrated in the first cloud system is completed by establishing the relevance relationship of the module to be migrated in the second cloud system. In this way, mutual migration can be realized between different types of cloud systems in order to meet different business requirements and improve the flexibility of the cloud system.

[0135] FIG. 9 shows a block diagram of some embodiments of a migration device for the cloud system of the present disclosure.

[0136] As shown in FIG. 9, the migration device for the cloud system includes a splitting unit 91, a determining unit 92, a replicating unit 93, and an establishing unit 94.

[0137] The splitting unit 91 is used to split the business system in the first cloud system into a plurality of modules.

[0138] The determining unit 92 is used to determine the relevance relationship between the module to be migrated among the plurality of modules and other modules among the plurality of modules.

[0139] The replication unit 93 is used to replicate the module to be migrated among a plurality of modules to the second cloud system, and the first cloud system and the second cloud system are of different types.

[0140] In some embodiments, the replication unit 93 replicates the module to be migrated to the test area of the first cloud system. The migration device 9 includes a verification unit 95 for performing a first operation verification on the module to be migrated in the test area using the relevance relationship established in the test area. When the first verification is passed, the replication unit 93 replicates the module to be migrated in the first cloud system to the second cloud system.

[0141] In some embodiments, the determination unit 92 is used to determine the dependent environment of the module to be migrated in the first cloud system, and the replication unit 93 is used to replicate the dependent environment to the second cloud system to complete the migration of the first cloud system.

[0142] In some embodiments, when the first verification fails, the determination unit 92 is used to re-determine the relevance relationship to perform the first operation verification again.

[0143] In some embodiments, the replication unit 93 replicates the dependent environment and related resources of the module to be migrated in the first cloud system to the test area to perform the first operation verification. When the first verification fails, the determination unit 92 re-determines the dependent environment to perform the first operation verification again.

[0144] The establishment unit 94 is used to establish a relevance relationship in the second cloud system to complete the migration of the first cloud system.

[0145] In some embodiments, the establishment unit 94 is used to construct a subnet corresponding to the topology structure related to the module to be migrated in the first cloud system in the second cloud system in order to complete the migration of the first cloud system.

[0146] In some embodiments, the establishment unit 94 is used to construct a subnet corresponding to the topology structure related to the module to be migrated in the first cloud system in the test area in order to perform the first operation verification.

[0147] In some embodiments, the verification unit 95 is used to perform a second operation verification on the module to be migrated in the second cloud system using the relevance relationship in a hybrid cloud system composed of the first cloud system and the second cloud system.

[0148] In some embodiments, the verification unit 95 is used to perform the first operation verification again when the second verification fails.

[0149] In some embodiments, the first cloud system is a public cloud system, the second cloud system is a private cloud system, the verification unit 95 is used to verify whether the protected data of the private cloud system is accessible through the public cloud system, and the migration device 9 further includes a processing unit 96 for performing an isolation process on the protected data in the private cloud system when the protected data is accessible.

[0150] In some embodiments, when the hybrid cloud composed of the first cloud system and the second cloud system passes the operation test, the processing unit 96 deletes the module to be migrated from the first cloud system.

[0151] In some embodiments, the first cloud system is a private cloud system, the second cloud system is a public cloud system, and the processing unit 96 is used to isolate the protected data in the private cloud system from the public cloud system.

[0152] In the above embodiments, the migration of the module to be migrated in the first cloud system is completed by establishing the relevance relationship of the module to be migrated in the second cloud system. In this way, mutual migration can be realized between different types of cloud systems in order to meet different business requirements and improve the flexibility of the cloud system.

[0153] FIG. 10 shows a block diagram of another embodiment of a migration device for the cloud system of the present disclosure.

[0154] As shown in FIG. 10, the device 10 for cloud system migration of the present embodiment includes a memory 101 and a processor 102 coupled to the memory 101. The processor 102 is configured to execute a migration method for a cloud system according to any one of the embodiments of the present disclosure based on instructions stored in the memory 101.

[0155] The memory 101 can include, for example, a system memory or a fixed non-transitory storage medium. The system memory stores, for example, an operating system, applications, a boot loader, a database, and other programs.

[0156] FIG. 11 shows a block diagram of yet another embodiment of a migration device for the cloud system of the present disclosure.

[0157] As shown in FIG. 11, the apparatus 11 for cloud system migration according to this embodiment includes a memory 1110 and a processor 1120 coupled to the memory 1110. The processor 1120 is configured to execute a migration method for a cloud system according to any one of the embodiments of the present disclosure based on instructions stored in the memory 1110.

[0158] The memory 1110 can include, for example, a system memory or a fixed non - volatile storage medium. The system memory stores, for example, an operating system, applications, a boot loader, a database, and other programs.

[0159] The apparatus 11 for cloud system migration can further include an input / output interface 1130, a network interface 1140, a storage interface 1150, etc. These interfaces 1130, 1140, 1150 and the memory 1110 and the processor 1120 may be connected via, for example, a bus 1160. The input / output interface 1130 provides a connection interface for input / output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 1140 provides a connection interface for various networked devices. The storage interface 1150 provides a connection interface for external storage devices such as an SD card and a USB flash drive.

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

[0161] As shown in FIG. 12, the hybrid cloud system 12 includes a migration device 121 for implementing a migration method for a cloud system according to any one of the above - mentioned embodiments.

[0162] Those skilled in the art should understand that embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Therefore, embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment including both hardware elements and software elements. Moreover, the present disclosure may take the form of a computer program product embodied in one or more computer-usable non-transitory storage media having computer-usable program code embodied therein.

[0163] So far in this specification, a migration method for a cloud system, a migration device for a cloud system, a hybrid cloud system, and a non-transitory computer-readable storage medium according to the present disclosure have been described in detail. To avoid obscuring the concepts of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can understand how to implement the technical solutions disclosed in this specification.

[0164] The methods and systems of the present disclosure can be implemented in many ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of the steps of the method is for illustrative purposes only, and the steps of the method of the present disclosure are not limited to the specific order described above unless otherwise specified. In addition, in some embodiments, the present disclosure may be implemented as a program recorded on a recording medium including machine-readable instructions for implementing the method according to the present disclosure. Therefore, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0165] Although some specific embodiments of the present disclosure have been described in detail by way of example, those skilled in the art should understand that the above examples are merely for illustrative purposes and are not intended to limit the scope of the present disclosure. It should be understood by those skilled in the art that the above embodiments can be modified without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the following claims.

Explanation of Signs

[0166] 10, 11 devices 91 splitting unit 92 decision unit 93 replication unit 94 establishment unit 95 verification unit 96 processing unit 101, 1110 memories 102, 1120 processors 1130 input / output interface 1140 network interface 1150 storage interface 1160 bus d1, d2 functional dependencies d3, d4 data dependencies m1~m8 modules r1, r2, r3 relevance relationships

Claims

1. A migration method for a cloud system executed by a computer, comprising: Dividing a business system in a first cloud system into a plurality of modules; Determining a relationship between a module to be migrated among the plurality of modules and other modules among the plurality of modules; Replicating the module to be migrated among the plurality of modules to a second cloud system, wherein the first cloud system and the second cloud system are of different types; Establishing the relationship in the second cloud system to complete the migration of the first cloud system; Including; The step of replicating the module to be migrated among the plurality of modules to the second cloud system is Replicating the module to be migrated to a test area of the first cloud system, wherein the test area is a separate transition space in 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 the relationship established in the test area; When the first operation verification is passed, replicating the module to be migrated in the first cloud system to the second cloud system. A migration method.

2. Determining a dependent environment of the module to be migrated in the first cloud system; Replicating the dependent environment in the second cloud system to complete the migration of the first cloud system; The migration method according to claim 1, further including.

3. To complete the migration of the first cloud system, constructing a subnet corresponding to a topology structure related to the module to be migrated in the first cloud system in the second cloud system; The migration method according to claim 1, further including.

4. When the first operation verification fails, re-determining the relationship between the module to be migrated and the other modules; Performing the first operation verification again according to the re-determined relationship; The migration method according to claim 1, further including.

5. To perform the first operation verification, a step of replicating the dependent environment of the module to be migrated and the resources related to the module to be migrated in the first cloud system to the test area; When the first operation verification fails, a step of re-determining the dependent environment of the module to be migrated; A step of performing the first operation verification again according to the re-determined dependent environment The migration method according to claim 1, further comprising.

6. To perform the first operation verification, a step of constructing a subnet corresponding to the topology structure related to the module to be migrated in the first cloud system in the test area The migration method according to claim 1, further comprising.

7. In a hybrid cloud system composed of the first cloud system and the second cloud system, a step of performing a second operation verification on the module to be migrated in the second cloud system using the relevance relationship The migration method according to claim 1, further comprising.

8. When the second operation verification fails, a step of performing the first operation verification again The migration method according to claim 7, further comprising.

9. The first cloud system is a public cloud system, and the second cloud system is a private cloud system, The migration method is A step of verifying whether the protected data of the private cloud system is accessible through the public cloud system; When the protected data is accessible, a step of performing an isolation process on the protected data in the private cloud system The migration method according to any one of claims 1 to 8, further comprising.

10. When the hybrid cloud composed of the first cloud system and the second cloud system passes the operation test, a step of deleting the module to be migrated from the first cloud system The migration method according to any one of claims 1 to 8, further comprising.

11. The first cloud system is a private cloud system, and the second cloud system is a public cloud system, The migration method is Isolating the protected data in the private cloud system from the public cloud system The migration method according to any one of claims 1 to 8, further comprising:

12. A migration device for a cloud system, comprising: A splitting unit for splitting a business system in a first cloud system into a plurality of modules; A determination unit for determining a relevance relationship between a module to be migrated among the plurality of modules and other modules among the plurality of modules; A replication unit for replicating the module to be migrated among the plurality of modules to a second cloud system, wherein the first cloud system and the second cloud system are of different types; An establishment unit for establishing the relevance relationship in the second cloud system in order to complete the migration of the first cloud system; And comprising: The replication unit: Replicating the module to be migrated to a test area of the first cloud system, wherein the test area is a separate transition space in the first cloud system; Performing a first operation verification on the module to be migrated in the test area of the first cloud system by using the relevance relationship established in the test area; When the first operation verification is passed, replicating the module to be migrated in the first cloud system to the second cloud system; A migration device configured to perform the above.

13. A migration device for a cloud system, comprising: A memory; A processor coupled to the memory; And the processor is configured to execute the migration method for a cloud system according to any one of claims 1 to 11 based on instructions stored in the memory.

14. A migration device for implementing the migration method for a cloud system according to any one of claims 1 to 11; A hybrid cloud system comprising the same.

15. A non-transitory computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the migration method for the cloud system according to any one of claims 1 to 11.

Images