VMware virtual machine dynamic migration method and system based on cloud platform

Abstract

The invention provides a VMware virtual machine dynamic migration method and system based on a cloud platform, and belongs to the technical field of cloud computing and virtualization operation and maintenance. The cloud platform accesses a vCenter Server and completes authentication, and synchronously obtains virtual machine, storage and network information; whether migration is supported or not is evaluated based on the compatibility list, if not, nano-management is conducted for centralized management, and if yes, a migration task is created. The cloud platform side creates a target virtual machine through a configuration template and closes the target virtual machine to enter a migration preparation state; the migration tool adopts a staged strategy of first full quantity and then incremental quantity to transmit data so as to ensure integrity and consistency, after migration is completed, the VMware Tools are unloaded, a cloud platform adaptive virtualization tool is installed, and a new virtual machine is automatically started according to nodes to complete switching; binding an EIP and configuring a routing rule when external access is needed; the migration log is used for checking the progress and locating problems in real time, and batch migration is supported.

Description

Technical Field

[0001] This invention belongs to the field of cloud computing and virtualization operation and maintenance technology, and in particular relates to a method and system for dynamic migration of VMware virtual machines based on a cloud platform. Background Technology

[0002] Enterprise-level data centers commonly use VMware virtualization platforms to support core business operations. As enterprises increasingly seek to migrate to the cloud, integrate resources, and optimize costs, they often need to migrate existing VMware virtual machines to the target cloud platform for unified operation and management.

[0003] Existing migration practices typically suffer from the following problems: high levels of manual intervention, numerous migration steps relying on experience, making it difficult to adapt to scenarios involving frequent migrations of large-scale virtual machines, and insufficient automation; a lack of unified standards in the migration process, leading to inconsistent execution methods among different personnel, poor migration consistency and repeatability, resulting in increased failure risks and subsequent maintenance costs; significant differences in VMware versions, virtual hardware versions, and operating system types at the source, and the fact that the target cloud platform does not support direct migration of all versions, which can easily lead to migration interruptions or increased complexity in cross-platform management if there is a lack of prior assessment and alternative solutions; and the need to balance data integrity and consistency, migration window control, migration progress visualization, and anomaly traceability while ensuring business continuity, otherwise business interruptions and data risks may be introduced.

[0004] Therefore, it is necessary to provide a tool-based, standardized, and monitorable VMware virtual machine dynamic migration solution for cloud platforms to reduce labor costs and migration risks, and improve migration efficiency and stability. Summary of the Invention

[0005] In view of this, the present invention aims to propose a method and system for dynamic migration of VMware virtual machines based on a cloud platform, so as to at least solve one of the problems in the background art.

[0006] To achieve the above objectives, the technical solution of the present invention is implemented as follows: A method for dynamic migration of VMware virtual machines based on a cloud platform is applied to a migration management system of the cloud platform. The migration management system is communicatively connected to the source VMware environment and the virtualization resource pool of the target cloud platform. The source VMware environment includes vCenter Server. The method includes: S1. Receive connection information from the source VMware environment, perform authentication and authorization on vCenter Server through the cloud platform interface, synchronously obtain the list of source virtual machines and their computing configuration, storage configuration and network configuration, and generate asset information of the virtual machines to be migrated; S2. Based on the compatibility list, the virtual hardware version, operating system type, and virtualization tool status of the virtual machine to be migrated are matched and evaluated with the virtualization capabilities of the target cloud platform to obtain the evaluation results. When the evaluation results show that migration is not supported, management processing is performed to include the source VMware resources into the cloud platform computing management system and display the source virtual machine information on the cloud platform side. When the evaluation results show that migration is supported, a migration task is generated and proceeds to S3. S3. Generate a virtual machine configuration template based on the asset information, and create a target virtual machine on the target cloud platform according to the virtual machine configuration template, and set the target virtual machine to the migration preparation state. S4. Transfer the source virtual machine data in stages according to the full data migration stage and the incremental data migration stage. In the full data migration stage, copy the basic disk data of the source virtual machine to the destination virtual machine. In the incremental data migration stage, copy the incremental data generated during the migration to ensure data consistency. S5. After completing the phased transmission, perform virtualization tool adaptation processing on the target virtual machine, uninstall VMware Tools and install the virtualization tool adapted to the target cloud platform, and start the target virtual machine to complete the service switch. S6. Record migration logs during the migration process. The migration logs shall include at least step status, progress information and exception information, and shall be used for monitoring, fault location and handling of migration tasks.

[0007] Furthermore, the compatibility list includes at least the combination information of VMware platform version and virtual machine operating system type. The matching evaluation includes verifying the combination information against the target cloud platform's support range, and allowing the migration task creation process to proceed when the verification is successful.

[0008] Furthermore, the management process includes: adding the address information and authentication information of vCenter Server to the cloud platform management interface, establishing an access relationship with the source VMware environment through the cloud platform interface, and performing resource synchronization to obtain the source virtual machine, storage and network resource information, thereby forming a managed resource view on the cloud platform side.

[0009] Furthermore, the virtual machine configuration template includes at least the parameters of specified user, number of CPU cores, memory size, disk capacity, and network address, and supports adjusting the parameters based on business needs to generate different target virtual machine configurations.

[0010] Furthermore, the migration preparation state includes shutting down the destination virtual machine or setting the destination virtual machine to a write-prohibited preparation mode for subsequent data writing and consistency verification.

[0011] Furthermore, the full data migration stage and the incremental data migration stage obtain the incremental data range through a snapshot mechanism or change block tracking mechanism, and transmit it in the form of data blocks or file fragments to reduce the risk of data inconsistency within the migration window.

[0012] Furthermore, the phased transmission includes performing verification processing on the transmitted data, the verification processing including at least a checksum-based integrity check; when the verification fails, the failed fragment is retransmitted and the reason for failure and the retry result are recorded in the migration log.

[0013] Furthermore, the virtualization tool adaptation process includes: uninstalling VMware Tools in the target virtual machine and then installing the virtualization tool adapted to the target cloud platform, and performing driver loading verification and network connectivity verification after installation to ensure the stability of the target virtual machine on the target cloud platform.

[0014] Furthermore, the migration log is archived according to the migration task identifier, and at least records the start time, end time, execution result and exception code of each step, and supports breakpoint resumption or failure rollback based on the migration log.

[0015] Furthermore, the method also includes batch migration scheduling: generating multiple migration tasks for multiple virtual machines to be migrated, adding the migration tasks to a task queue, and scheduling and executing them according to concurrency thresholds and resource constraints.

[0016] Furthermore, this solution discloses a VMware virtual machine dynamic migration system based on a cloud platform, including: The access and synchronization module is used to receive connection information from the source VMware environment and establish an access relationship with vCenter Server, obtain a list of virtual machines and their computing, storage and network configurations, and generate asset information. The compatibility assessment module is used to match and assess the capabilities of the virtual machine to be migrated with the target cloud platform based on the compatibility list, and to trigger management processing when migration is not supported, and to generate a migration task when migration is supported. The template and creation module is used to generate virtual machine configuration templates based on asset information and create the target virtual machine on the target cloud platform. The data migration module is used to perform phased transmission according to the full data migration phase and the incremental data migration phase, and to ensure data consistency. The tool adaptation and switching module is used to uninstall VMware Tools and install virtualization tools adapted to the target cloud platform after the migration is completed, and start the target virtual machine to complete the business switching. The logging module is used to record migration logs and support the monitoring and fault location of migration tasks.

[0017] Furthermore, this solution discloses a computer-readable storage medium having a computer program stored thereon, the computer program implementing the method when executed by a processor.

[0018] Compared with existing technologies, the VMware virtual machine dynamic migration method and system based on a cloud platform described in this invention has the following advantages: (1) Before migration, the present invention evaluates whether the target cloud platform supports the target version of VMware virtual machine based on the compatibility list; when the evaluation does not support migration, the migration is not forced, but instead the management path is switched to include VMware resources in the cloud platform computing management system for centralized management, thereby avoiding failure in the migration due to platform incompatibility and reducing the complexity and risk of cross-platform management. (2) The cloud platform side of the present invention generates a default template and creates a target virtual machine according to the template, which clearly specifies the creation parameters (specifying the user, number of CPU cores, memory size, disk capacity, network IP address, etc.), which can ensure that the virtual machine configuration after migration is consistent with the preset requirements, and also make the migration preparation steps consistent and repeatable, reducing errors caused by different personnel configuring based on experience. (3) The present invention adopts a phased migration strategy of full migration followed by incremental migration: first complete the full data migration to ensure the integrity of the basic data, and then migrate the incremental data generated during the migration to ensure the integrity and consistency of the overall data migration; this mechanism can reduce the probability of data inconsistency, missing files and other problems during business switching. (4) After the migration is completed, this solution uninstalls VMware Tools and installs virtualization tools that are compatible with the cloud platform, so that the target virtual machine can be adapted and run on the target cloud platform, avoiding performance abnormalities, device recognition abnormalities and other running problems caused by tool / driver incompatibility; (5) After the migration step is advanced to the corresponding node, the system can automatically start a new virtual machine, reducing the waiting time for manual intervention and helping to achieve rapid business recovery and continuous operation; (6) After the migration is completed and the conditions for use are met, if the business needs to access the outside world, the administrator can bind the Elastic Public IP (EIP) to the virtual machine in the cloud platform management interface. The cloud platform will bind the EIP to the virtual machine network interface and configure the corresponding network routing rules so that the virtual machine can communicate with the external network through the EIP, thereby reducing the additional configuration cost and waiting time of network access after migration. (7) During the migration process of this invention, the migration progress is displayed in real time through the migration log and used to grasp the problems that occur during the migration; combined with the design of recording operation status and abnormal information, supporting problem location and dynamic adjustment, the migration process is more controllable and the location is more direct, which is conducive to rapid handling and review of operations and maintenance. (8) This invention supports batch migration of virtual machines and, together with the mechanism of recording operation status and abnormal information in migration logs, enables the migration of multiple virtual machines to be carried out using a unified process, reducing the pressure of manual operation and monitoring of each machine, and adapting to the large-scale migration needs of enterprises. Attached Figure Description

[0019] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings: Figure 1 This is a schematic diagram of the method described in an embodiment of the present invention; Figure 2 This is a screenshot of the VMware virtual machine migration log interface as described in an embodiment of the present invention. Detailed Implementation

[0020] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0021] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0022] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art will understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0023] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0024] Example 1: Overall System and Module Composition As described in this solution, the cloud platform provides a tool-based implementation path for VMware virtual machine migration: first, connect to the source VMware environment and form a resource view; then, decide whether to migrate or manage the virtual machine based on compatibility assessment; then, complete the creation of the target virtual machine, data migration, tool adaptation, startup, and network access according to unified steps; and finally, monitor the entire process through migration logs.

[0025] In a feasible system architecture, the migration management system should include at least the following functional modules (module names can be adjusted according to implementation, but it is recommended to retain the corresponding relationships to facilitate mutual support between methods / systems in the future): 1. Access and Management Module: This module receives connection information from the source VMware environment in the cloud platform management interface and completes access, authentication, and authorization between the cloud platform and the source VMware environment via API. Connection information may include the vCenter Server's IP address, username, and password.

[0026] 2. Resource Synchronization and Display Module: This module performs manual synchronization, retrieves resource information such as virtual machines, storage, and networks from the source VMware environment, and displays virtual machine information within the managed node in real time on the cloud platform interface. This includes information such as virtual machine name, IP address, operating system type, CPU and memory usage, providing a clear and accurate resource view for migration.

[0027] 3. Compatibility Assessment and Path Selection Module: This module assesses whether the cloud platform supports the migration of the target version of VMware virtual machines based on the compatibility list. If not, it will be transferred to management; if it is supported, a migration task will be generated and the migration implementation steps will begin.

[0028] 4. Template Management and Target Virtual Machine Creation Module: This module is used to create virtual machine configuration templates on the cloud platform and create target virtual machines according to the templates. Template parameters must include at least the specified user, number of CPU cores, memory size, disk capacity, and network IP address.

[0029] 5. Migration Execution Module: Used to perform data migration, completing data transmission and ensuring consistency in a phased strategy of full and incremental migration.

[0030] 6. Tool Adaptation and Switching Module: This module is used to uninstall VMware Tools and install cloud platform-compatible virtualization tools after the migration is complete, so that the target virtual machine can run on the cloud platform.

[0031] 7. Automated Startup Module: Used to automatically start new virtual machines when the migration process progresses to the corresponding node, in order to support rapid business recovery.

[0032] 8. Network Access Module: Used to bind an Elastic Public IP (EIP) to a virtual machine when external access is required, and to configure network routing rules to enable external network communication.

[0033] 9. Log and Monitoring Module: Used to display migration progress in real time through migration logs and expose problems during the migration process, making it easier to locate and handle them.

[0034] Example 2: Compatibility Check and Subsidiary Path for Management Before migration, the system assesses whether the cloud platform supports the migration of the target version of VMware virtual machines based on the compatibility list; this assessment is used to improve the success rate of migration tasks.

[0035] When the evaluation results show that migration is not supported, this solution does not directly proceed to the migration step. Instead, it uses management technology to incorporate VMware resources into the cloud platform computing management system, thereby achieving centralized management of VMware resources on the cloud platform side and avoiding the complexity and potential risks brought about by cross-platform management.

[0036] In a workable implementation of managed access, the administrator adds the source VMware environment connection information (such as the IP address, username, and password of the vCenter Server) in the cloud platform management interface, and completes access, authentication, and authorization through the cloud platform API to ensure that only authorized nodes can be managed.

[0037] The cloud platform supports manual synchronization to obtain information on virtual machines, storage, and network resources, and displays virtual machine names, IP addresses, operating system types, CPU and memory usage in real time on the interface, providing a basis for subsequent migration decisions and resource planning.

[0038] Example 3: Templated Creation and Migration Preparation of the Target Virtual Machine Once the compatibility assessment is passed and the migration path is initiated, the system creates a virtual machine configuration template on the cloud platform side. Administrators can configure parameters such as specified users, number of CPU cores, memory size, disk capacity, and network IP address in the template.

[0039] The use of templates serves two purposes: firstly, to maintain consistent virtual machine configurations during migration, ensuring the standardization and repeatability of the migration process; secondly, to allow for personalized configurations based on business needs, adapting to different business scenarios.

[0040] The system then creates a new virtual machine in the cloud platform according to the pre-configured template, which serves as the destination virtual machine for the migration of the source VMware virtual machine, ensuring that the configuration after migration is consistent with the preset requirements.

[0041] During the migration preparation phase, the newly created target virtual machine may be running by default. To ensure that the subsequent data migration is carried out efficiently and in an orderly manner, it is necessary to shut down the virtual machine to put it into a migration-ready state and create stable conditions for the subsequent data migration.

[0042] Example 4: Phased Data Migration and Consistency Guarantee During the initial migration phase, the migration tool follows a migration strategy of migrating all data first, followed by migrating incremental data: first, all virtual machine data is completely migrated to ensure that the basic data is completely migrated to the target environment; after the full migration is completed, incremental data generated during the migration is then migrated to ensure the integrity and consistency of the data migration.

[0043] In a preferred implementation, to enhance migration reliability and reduce redundant work, the following engineering measures can be configured in the migration execution module (these are optional enhancements and do not change the basic strategy of full and incremental migration): 1. Fragmented transmission and retry on failure: Full / incremental data is transmitted in fragments according to disk blocks or file segments, and the status of each fragment is recorded; when encountering network jitter or single fragment failure, only the failed fragment is retransmitted, reducing the probability of rerunning the entire task.

[0044] 2. Phased verification: After the full phase is completed, an integrity verification is performed before entering the incremental phase; after the incremental phase is completed, a consistency verification is performed to reduce failures caused by data loss or inconsistency after the switch.

[0045] 3. Breakpoint recovery: The migration task saves the progress of each stage (e.g., the completed interval of the full stage, the start and end time of the incremental stage). If the task is interrupted due to an exception, it can continue execution from the most recent successful point, reducing recovery costs.

[0046] The above measures all serve the goal of this solution to ensure the integrity and consistency of data migration, and are implemented in conjunction with the migration log monitoring mechanism.

[0047] Example 5: Virtualization Tool Adaptation, Automatic Startup, and Service Switching Once the data migration is complete, the target virtual machine will undergo virtualization tool adaptation: VMware Tools will be uninstalled and cloud platform-compatible virtualization tools will be installed to enable the virtual machine to run on the cloud platform.

[0048] To improve migration efficiency, the migration process is set up with an automated operation mechanism: when the migration steps progress to the corresponding node, the system automatically starts a new virtual machine to ensure seamless business continuity and rapid restoration of normal operation.

[0049] Example 6: EIP Binding and Routing Configuration After completing the above migration operations, if the business requires external access, the administrator can bind an Elastic Public IP (EIP) to the virtual machine in the cloud platform management interface; the cloud platform will bind the EIP to the virtual machine's network interface and configure the corresponding network routing rules so that the virtual machine can communicate with the external network through the EIP.

[0050] Example 7: Migration Log Monitoring and Batch Migration During the migration process, users can view the migration progress in real time through the migration log and be aware of any problems that may arise.

[0051] In one implementation that supports batch migration, the system generates multiple migration tasks for multiple virtual machines and manages them uniformly. The migration log records the operation status and abnormal information of each task to support rapid problem localization and on-demand adjustments.

[0052] Preferably, to adapt to the resource constraints of large-scale migration, batch tasks can be placed in a task list with a concurrency limit set, and executed in batches according to the availability of cloud platform resources. When a task encounters an anomaly, only that task is paused or retried without affecting the progress of other tasks. Simultaneously, the task-level status is reflected in the migration log for centralized monitoring and handling. This implementation aims to alleviate engineering problems stemming from background deficiencies such as high labor costs, difficulty in automated management, and lack of unified standards.

[0053] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for dynamic migration of VMware virtual machines based on a cloud platform, characterized in that, A migration management system applied to a cloud platform, wherein the migration management system is communicatively connected to a source VMware environment and a target cloud platform virtualization resource pool, the source VMware environment including vCenter Server, the method comprising: S1. Receive connection information from the source VMware environment, perform authentication and authorization on vCenter Server through the cloud platform interface, synchronously obtain the list of source virtual machines and their computing configuration, storage configuration and network configuration, and generate asset information of the virtual machines to be migrated; S2. Based on the compatibility list, the virtual hardware version, operating system type, and virtualization tool status of the virtual machine to be migrated are matched and evaluated with the virtualization capabilities of the target cloud platform to obtain the evaluation results. When the evaluation results show that migration is not supported, management processing is performed to include the source VMware resources into the cloud platform computing management system and display the source virtual machine information on the cloud platform side. When the evaluation results show that migration is supported, a migration task is generated and proceeds to S3. S3. Generate a virtual machine configuration template based on the asset information, and create a target virtual machine on the target cloud platform according to the virtual machine configuration template, and set the target virtual machine to the migration preparation state. S4. Transfer the source virtual machine data in stages according to the full data migration stage and the incremental data migration stage. In the full data migration stage, copy the basic disk data of the source virtual machine to the destination virtual machine. In the incremental data migration stage, copy the incremental data generated during the migration to ensure data consistency. S5. After completing the phased transmission, perform virtualization tool adaptation processing on the target virtual machine, uninstall VMware Tools and install the virtualization tool adapted to the target cloud platform, and start the target virtual machine to complete the service switch. S6. Record migration logs during the migration process. The migration logs shall include at least step status, progress information and exception information, and shall be used for monitoring, fault location and handling of migration tasks.

2. The method according to claim 1, characterized in that, The compatibility list includes at least the combination information of VMware platform version and virtual machine operating system type. The matching evaluation includes verifying the combination information against the target cloud platform's support range, and allowing the migration task creation process to proceed when the verification is successful.

3. The method according to claim 1, characterized in that, The management process includes: adding the vCenter Server's address information and authentication information to the cloud platform management interface, establishing an access relationship with the source VMware environment through the cloud platform interface, and performing resource synchronization to obtain the source virtual machine, storage, and network resource information, thereby forming a managed resource view on the cloud platform side.

4. The method according to claim 1, characterized in that, The migration preparation state includes shutting down the destination virtual machine or setting the destination virtual machine to a write-prohibited preparation mode for subsequent data writing and consistency verification.

5. The method according to claim 1, characterized in that, The full data migration phase and the incremental data migration phase obtain the incremental data range through a snapshot mechanism or change block tracking mechanism, and transmit it in the form of data blocks or file fragments to reduce the risk of data inconsistency within the migration window.

6. The method according to claim 1, characterized in that, The phased transmission includes performing verification processing on the transmitted data, which includes at least a checksum-based integrity check; when the verification fails, the failed fragment is retransmitted and the reason for failure and the retry result are recorded in the migration log.

7. The method according to claim 1, characterized in that, The virtualization tool adaptation process includes: uninstalling VMware Tools in the target virtual machine and then installing the virtualization tool adapted to the target cloud platform. After installation, driver loading verification and network connectivity verification are performed to ensure the stability of the target virtual machine on the target cloud platform.

8. The method according to claim 1, characterized in that, The method also includes batch migration scheduling: generating multiple migration tasks for multiple virtual machines to be migrated, adding the migration tasks to a task queue, and scheduling and executing them according to concurrency thresholds and resource constraints.

9. A VMware virtual machine dynamic migration system based on a cloud platform, characterized in that, include: The access and synchronization module is used to receive connection information from the source VMware environment and establish an access relationship with vCenter Server, obtain a list of virtual machines and their computing, storage and network configurations, and generate asset information. The compatibility assessment module is used to match and assess the capabilities of the virtual machine to be migrated with the target cloud platform based on the compatibility list, and to trigger management processing when migration is not supported, and to generate a migration task when migration is supported. The template and creation module is used to generate virtual machine configuration templates based on asset information and create the target virtual machine on the target cloud platform. The data migration module is used to perform phased transmission according to the full data migration phase and the incremental data migration phase, and to ensure data consistency. The tool adaptation and switching module is used to uninstall VMware Tools and install virtualization tools adapted to the target cloud platform after the migration is completed, and start the target virtual machine to complete the business switching. The logging module is used to record migration logs and support the monitoring and fault location of migration tasks.

10. A computer-readable storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing the method of any one of claims 1 to 8.

Images