Upgrade migration method, device and equipment and computer readable storage medium

The upgrade migration method addresses the challenge of cross-version migration in cloud platforms by installing drivers, using customized scripts to migrate data and configure nodes, ensuring data integrity and continuity across different versions of OpenStack and VMware.

CN119088409APending Publication Date: 2024-12-06JINAN INSPUR DATA TECH CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202411368068.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-27
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Current cloud management platforms cannot perform version migration, such as migrating from a lower version of OpenStack to a newer version or from a lower version of VMware to a higher version while ensuring data integrity.

Method used

An upgrade migration method involving installing a driver on a source node, obtaining a startup image with source and target node scripts, migrating data using a source node migration script, and configuring the target node with a target node script to achieve cross-version migration.

Benefits of technology

Enables seamless migration across different versions of OpenStack and VMware, ensuring data integrity and continuity by customizing the startup image and configuring the target node to support the old and new versions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088409A_ABST
    Figure CN119088409A_ABST
Patent Text Reader

Abstract

The invention discloses an upgrade migration method, device and equipment and a computer readable storage medium, and is applied to the technical field of migration, and the upgrade migration method comprises the following steps: installing a driver to a source node to obtain a to-be-migrated source node; obtaining a starting mirror image of the to-be-migrated source node under the condition of determining network intercommunication between the to-be-migrated source node and the target node; migrating data of basic software related to a source node to a target node by utilizing a source node migration script in the starting mirror image; and when it is determined that migration is completed, automatically configuring the source node migrated to the target node by using the target node script to obtain a configured target migration node, and managing the target migration node by using the cloud management platform. Under the condition of network intercommunication between the to-be-migrated source node and the target node, the source node migration script is executed, after the source migration script is executed, the target node script is used for automatically configuring the source node migrated to the target node, and migration of the nodes in different environments is achieved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of migration technology, and in particular to an upgrade migration method, device, equipment and computer-readable storage medium. Background Art

[0002] Currently, the cloud management platform only performs migration within the existing version. It can migrate from node A to node B in an environment, or from an openstack environment (an open source cloud computing management platform project) to VMware (virtual machine software), and vice versa. However, it cannot migrate from a lower version of openstack to a newer version of openstack, or from a lower version of VMware to a higher version of VMware.

[0003] It can be seen that how to achieve version migration while ensuring the integrity of business data is a problem that technical personnel in this field need to solve. Summary of the invention

[0004] In view of this, the purpose of the present invention is to provide an upgrade migration method, device, equipment and computer-readable storage medium, which solves the problem that it is impossible to implement an upgrade from a lower version in the prior art.

[0005] In order to solve the above technical problems, the present invention provides an upgrade migration method, comprising:

[0006] Install the driver to the source node to obtain the source node to be migrated;

[0007] When it is determined that the network between the source node to be migrated and the target node is interconnected, the startup image of the source node to be migrated is obtained; wherein the information in the startup image includes the basic software of the source node, the source node migration script and the target node script; the basic software is software set according to the requirements; the source node migration script is the information of the source node configured according to the destination node of the migration; the target node script is the script for configuring the target node information; the migration from the source node to the target node is a cross-version migration;

[0008] Migrating the data of the basic software related to the source node to the target node using the source node migration script in the startup image;

[0009] When it is determined that the migration is completed, the target node script is used to automatically configure the source node migrated to the target node to obtain a configured target migration node, and the target migration node is managed by the cloud management platform.

[0010] On the one hand, before obtaining the startup image of the source node to be migrated, the method further includes:

[0011] Obtaining the operating system, memory size, and disk capacity information of the source node to be migrated;

[0012] The startup image is created according to the operating system, the memory size and the disk capacity information.

[0013] On the one hand, using the source node migration script in the startup image to migrate the data of the basic software related to the source node to the target node includes:

[0014] Determine the type of basic software data and obtain basic software data of each type; wherein the types include disk data and memory data;

[0015] The priorities of the various types of basic software data are determined, and the data increments are migrated to the target node using the source node migration script according to the priorities.

[0016] On the one hand, in the case of determining that the network between the source node to be migrated and the target node is interconnected, after obtaining the startup image of the source node to be migrated, the method further includes:

[0017] Determine the type of the target node; wherein the type of the target node is any one of a block storage node, a component disk node, and a virtualization node;

[0018] Modify the configuration file according to the type of the target node to obtain a modified configuration file;

[0019] Execute the configuration script including the modified configuration file to obtain a modified source node migration script;

[0020] Accordingly, using the source node migration script in the startup image to migrate the data of the basic software related to the source node to the target node includes:

[0021] The modified source node migration script is used to migrate the data of the basic software related to the source node to the target node.

[0022] In one aspect, the target node script includes network, specification, firewall and project information.

[0023] On the one hand, when it is determined that the migration is completed, the target node script is used to automatically configure the source node migrated to the target node, and after obtaining the configured target migration node, the method further includes:

[0024] Obtain a script file of the cloud host; wherein the script file of the cloud host includes a project ID, a user ID, a specification ID, a network ID, and a system disk corresponding to the disk to be migrated;

[0025] Execute the script file of the cloud host and create a new cloud host on the configured target migration node.

[0026] On the one hand, the upgrade migration method further includes:

[0027] Get the upgrade migration task status;

[0028] Determine whether the upgrade migration task is completed according to the upgrade migration task status;

[0029] If yes, set it to completed flag;

[0030] Otherwise, obtain the upgrade migration task failure log;

[0031] Analyze the upgrade migration task failure log to determine the cause of the failure;

[0032] Determine to modify the relevant configuration information of the startup image based on the failure reason, and obtain a modified startup image;

[0033] Performing upgrade migration based on the modified startup image;

[0034] or when it is determined that there is a problem with the network based on the failure cause, monitoring the network between the source node and the target node to be migrated, and when it is determined that the current network can be upgraded to the migration requirements, determining to use the startup image for migration;

[0035] Or when it is determined that there is a problem with the target node based on the failure cause, determining the time required to repair the problem of the target node;

[0036] When the time required to fix the problem is less than the minimum time required, determine to migrate after solving the problem through a first solution; wherein the first solution includes at least one of restarting and software updating;

[0037] When the repair time of the problem is not less than the minimum time, a migration plan is determined; wherein the migration plan includes migration time, migration files, and problem response plan; wherein the migration time is the time determined according to the problem solving time and system performance, the migration files are files uploaded during the migration process, and the problem response plan is a problem solving method generated according to the current problem.

[0038] The present invention also provides an upgrade migration device, comprising:

[0039] A module for determining a source node to be migrated, used for installing a driver on a source node to obtain a source node to be migrated;

[0040] A startup image acquisition module is used to obtain the startup image of the source node to be migrated when it is determined that the network between the source node to be migrated and the target node is interconnected; wherein the information in the startup image includes the basic software of the source node, the source node migration script and the target node script; the basic software is software set according to the requirements; the source node migration script is the information of the source node configured according to the destination node of the migration; the target node script is a script for configuring the target node information; the migration from the source node to the target node is a cross-version migration;

[0041] A data migration module, used to migrate the data of the basic software related to the source node to the target node by using the source node migration script in the startup image;

[0042] The target migration node configuration module is used to determine when the migration is completed, use the target node script to automatically configure the source node migrated to the target node, obtain the configured target migration node, and use the cloud management platform to manage the target migration node.

[0043] The present invention also provides an upgrade migration device, comprising:

[0044] Memory for storing computer programs;

[0045] A processor is used to execute the computer program to implement the steps of the upgrade migration method as described above.

[0046] The present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the upgrade migration method described above are implemented.

[0047] An embodiment of the present invention further provides a computer program product, including a computer program / instruction, wherein the computer program / instruction implements the steps of the upgrade migration method when executed by a processor.

[0048] The purpose of the embodiments of the present invention is to provide an upgrade migration method, device, equipment and computer-readable storage medium, which can solve the problem that cross-version migration cannot be achieved.

[0049] To solve the above technical problems, an embodiment of the present invention provides an upgrade migration method, including: installing a driver to a source node to obtain a source node to be migrated; determining that the network between the source node to be migrated and the target node is interconnected, obtaining a startup image of the source node to be migrated; wherein the information in the startup image includes the basic software of the source node, a source node migration script and a target node script; the basic software is software set according to requirements; the source node migration script configures the information of the source node according to the destination node of the migration; the target node script is a script for configuring the target node information; the migration from the source node to the target node is a cross-version migration; the migration from the source node to the target node is a cross-version migration; using the source node migration script in the startup image, the data of the basic software related to the source node is migrated to the target node; when it is determined that the migration is completed, using the target node script to automatically configure the source node migrated to the target node to obtain a configured target migration node, and using the cloud management platform to manage the target migration node.

[0050] It can be seen from the above technical scheme that the beneficial effect of the present invention is that: compared with the current cloud management platform which only performs migration within the existing version (the same environment), and can migrate node A to node B in an environment, or migrate from an openstack environment to VMware, and vice versa, but cannot migrate from a lower version of openstack to a newer version of openstack, or from a lower version of VMware to a higher version of VMware, the beneficial effect of the present invention is that: the old version of the node to be migrated is started through a customized tool image, the required parameters of the target environment to be migrated are preset, and then the source node migration script is executed. After waiting for the migration script to be executed, the image is deployed to the target node according to the target node script, thereby realizing the migration of the old and new versions. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0052] Figure 1 A flowchart of an upgrade migration method provided by an embodiment of the present invention;

[0053] Figure 2 A schematic diagram of the structure of a cross-cloud platform migration framework based on offline tools provided in an embodiment of the present invention;

[0054] Figure 3 A schematic diagram of the structure of an upgrade migration device provided by an embodiment of the present invention;

[0055] Figure 4 A schematic diagram of the structure of an upgrade migration device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0057] The terms "including" and "having" in the specification of the present invention and the above-mentioned drawings, as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but may include steps or units that are not listed.

[0058] Some of the terms that appear in the description of the embodiments of the present invention may be interpreted as follows:

[0059] ISO (International Organization for Standardization, CD-ROM image file);

[0060] LiveCD: A very powerful tool that can run a complete operating system without affecting the existing system installation. No matter what problems the system encounters, it can be diagnosed and repaired through LiveCD without worrying about further damage to the current system or data.

[0061] Openstack, an open source cloud computing management platform project;

[0062] VMware, virtual machine software;

[0063] RBD is the abbreviation of RADOS Block Device. RBD block storage is the most stable and most commonly used storage type.

[0064] G2 configuration and G5 configuration refer to the hardware and software settings of different models of devices, respectively. G2 configuration involves the hard disk information of a specific model of device, such as capacity, interface type, etc. This helps to ensure the compatibility and performance of data storage during device migration or upgrade. G5 configuration generally refers to higher-performance device configurations, such as those equipped with Intel's 10th-generation standard-voltage processor Core i7-10750H and GeForce RTX 3050 Mobile 4GB graphics card.

[0065] In order to enable those skilled in the art to better understand the solution of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0066] Next, an upgrade migration method provided by an embodiment of the present invention is described in detail. Figure 1 A flowchart of an upgrade migration method provided by an embodiment of the present invention, the method may include:

[0067] S101, installing a driver to a source node to obtain a source node to be migrated.

[0068] The executor of this embodiment is an electronic device, for example, the electronic device can be a computer, or a management platform for managing a cluster. This embodiment does not limit the specific source node, as long as it is necessary to migrate from a low-version A environment to a high-version B environment. For example, the source node in this embodiment can be a low-version openstack; or the source node in this embodiment can also be a low-version VMware. The low version in this embodiment refers to an older version of the software, hardware or system, which is usually not the latest highest version. The driver in this embodiment refers to the software interface of a computer hardware device, which is used for communication and control between the operating system and the hardware device.

[0069] It should be further explained that before obtaining the boot image of the source node to be migrated, it can include: obtaining the operating system, memory size and disk capacity information of the source node to be migrated; and making the boot image according to the operating system, memory size and disk capacity information. The operating system information in this embodiment may include the type and version of the operating system: first, it is necessary to determine the operating system type (such as Linux, Windows, etc.) and its specific version of the source node. This helps to ensure the compatibility of the boot image with the source node and avoid startup failures due to incompatibility. Kernel parameters of the operating system: determine kernel parameters, such as startup mode, boot options, etc., which are crucial for making a boot image. The memory size in this embodiment includes the total memory amount: obtain the total memory size of the source node to ensure that the boot image can provide sufficient memory support for the system. This is crucial for the normal operation and performance of the system. And memory allocation: understand the memory allocation of the source node, such as which processes occupy more memory, which memory areas are used for caching, etc. This helps to make reasonable memory configuration when making a boot image. The disk capacity information in this embodiment includes the total disk capacity and partition information, total disk capacity: obtain the total disk capacity of the source node so that sufficient storage space can be allocated when making a boot image. At the same time, this also helps to evaluate the data volume and storage requirements of the system. Partition information: Understand the disk partitioning of the source node, including the number of partitions, the size of each partition, and the file system type. This information is crucial for making a boot image with the correct partition structure.

[0070] It should be further explained that, in this embodiment, a suitable boot image format can be selected according to the operating system type of the source node and the requirements of the target node. Common formats include ISO, IMG, and VMDK. Each format has its own characteristics and applicable scenarios, and needs to be selected according to actual conditions. ISO (International Standard Organization) is an international standard optical disc file system format; IMG (Image) is a universal disk image format that can simulate the data structure of a hard disk, floppy disk or other storage device; VMDK (Virtual Machine Disk) is a virtual disk format developed by VMware, mainly used in VMware's virtual machine environment. The operating system installation file of the source node is included in the boot image to install the system on the target node. This usually involves copying the installation media of the operating system (such as ISO files) into the image file. Driver integration: If the source node uses specific hardware drivers, these drivers need to be integrated into the image when the boot image is made. This helps to ensure that the target node can normally identify and use these hardware devices after startup. Configuration file replication: Copy the configuration files (such as network settings, user accounts, etc.) on the source node to the boot image. This helps to quickly restore the configuration environment of the source node on the target node.

[0071] S102, when it is determined that the network between the source node to be migrated and the target node is interconnected, obtain the startup image of the source node to be migrated; wherein the information in the startup image includes the basic software of the source node, the source node migration script and the target node script; the basic software is the software set according to the requirements; the source node migration script is the information of the source node configured according to the destination node of the migration; the target node script is the script for configuring the target node information; the migration from the source node to the target node is a cross-version migration.

[0072] The target node of this embodiment is a high-version source node. For example, when the source node is a low-version openstack, the target node is a high-version openstack; when the source node is a low-version VMware, the target node is a high-version VMware. The network intercommunication between the source node to be migrated and the target node in this embodiment is achieved by configuring the network intercommunication between the source node to be migrated and the target node. The boot image in this embodiment is a file containing a complete operating system or a boot loader, which is used to load and execute when the computer starts. It can be a disk-based image (such as an ISO file) or a network-booted image (such as a PXE image). The basic software of the source node in this embodiment generally includes an operating system, a database management system, and middleware; or includes an operating system and a configuration file. When selecting these software, their stability, performance, compatibility, and future scalability need to be considered. The source node migration script in this embodiment is used to automatically upgrade the source node according to the information of the source node configured by the destination node of the migration. The target node script in this embodiment is a script that ensures that the data of the source node is migrated to the target node to ensure compatibility and performance. This embodiment can execute the migration script to migrate the disk on the source node to rbd or G2 / G5. After the migration is completed, the cloud hard disk is automatically managed and the creation of a cloud host based on the specified system disk is supported.

[0073] It should be further explained that, in the case of determining that the network between the source node to be migrated and the target node is interconnected, after obtaining the startup image of the source node to be migrated, the following may also be included:

[0074] Determine the type of the target node; wherein the type of the target node is any one of a block storage node, a component disk node, and a virtualization node;

[0075] Modify the configuration file according to the type of the target node to obtain a modified configuration file;

[0076] Execute the configuration script including the modified configuration file to obtain the modified source node migration script;

[0077] Accordingly, the data of the basic software related to the source node is migrated to the target node using the source node migration script in the startup image, including:

[0078] The modified source node migration script is used to migrate the data of the basic software related to the source node to the target node.

[0079] In this embodiment, the configuration file can be modified according to the demand to obtain the modified configuration file, so as to perform migration based on the modified configuration file, thereby improving the user experience.

[0080] S103, using the source node migration script in the startup image, migrate the data of the basic software related to the source node to the target node.

[0081] In this embodiment, the source node migration script can modify the IP of the source node to be migrated, the storage information end (rbd configuration, G2 configuration (component disk information), G5 configuration (upgraded version)) and other information, which are specifically set according to the different conditions of each platform. If migrating to rbd, modify #icfs config (configuration file, the configuration script modifies the configuration file) according to the on-site situation. If it is UV3 version and above, you need to execute bash install (command line interpreter) to install the UV3 client. If migrating to G2 / G5, modify #iscsi config (block-level storage protocol) according to the specific G2 / G5 username and password used.

[0082] It should be further explained that the above-mentioned use of the source node migration script in the startup image to migrate the data of the basic software related to the source node to the target node may include:

[0083] S1031, determining the type of basic software data, and obtaining basic software data of various types; wherein the types include disk data and memory data;

[0084] S1032, determining the priority of each type of basic software data, and using the source node migration script to migrate the data incrementally to the target node according to the priority.

[0085] When migrating data to the target node, this embodiment will use the source node migration script to migrate the data incrementally to the target node according to the priority. For example, the disk data of the virtual machine will be migrated first, and then the memory data will be migrated as needed, so as to reduce the migration time and data volume, and prevent the migration failure caused by the large network bandwidth due to excessive migration at one time. In addition, after the migration is completed, this embodiment can verify the migrated data, including checking the integrity, consistency and availability of the data, to ensure that the migrated data can be used normally and meet business needs. If problems or abnormal situations are found, they need to be processed and repaired in a timely manner.

[0086] S104, when it is determined that the migration is completed, the source node migrated to the target node is automatically configured using the target node script to obtain a configured target migration node, and the target migration node is managed using the cloud management platform.

[0087] In this implementation, the target node script can be used to configure the corresponding information in the target node, including network, specifications, firewall, project and other information, and can automatically configure the information required to create a cloud host in the target node. According to the migration plan, the appropriate information is automatically configured to ensure that the migrated cloud host can run normally. The network configuration in this embodiment includes IP address, subnet mask and gateway configuration, etc.; the firewall configuration in this embodiment includes configuring rules for allowing or denying inbound traffic from a specific IP address or port number. This helps prevent unauthorized access and attacks. At the same time, some unnecessary outbound traffic can also be restricted according to business needs. The specifications in this embodiment refer to CPU and memory configuration, storage space and I / O performance. The project information in this embodiment includes project configuration files and environment files. The project configuration file contains key information of the project, such as project name, version number, dependencies, etc. This embodiment can be used to incorporate the migrated virtual machine into the management system of the target cloud platform, realize the automated management of resources, and ensure that the business data can still be fully used in the target cloud management platform.

[0088] It should be further explained that when the migration is determined to be completed, the target node script is used to automatically configure the source node migrated to the target node. After obtaining the configured target migration node, it can also include: obtaining the script file of the cloud host; wherein the script file of the cloud host includes the project ID, user ID, specification ID, network ID and the system disk corresponding to the disk to be migrated; executing the script file of the cloud host to create a new cloud host in the configured target migration node. The target node script should contain the necessary configuration commands and parameters to automatically complete the configuration of the source node. This may include network settings, security group rules, firewall configuration, etc. The project ID in this embodiment is used to group resources such as cloud hosts according to logic or business needs for easy management and search. Through the project ID, access control of different projects can be implemented to limit unauthorized access and operations. The user ID in this embodiment is an important credential for users to log in to the cloud platform and is used to verify the identity and authority of the user. The specification ID in this embodiment defines the hardware configuration of the cloud host, such as the number of CPU cores, memory capacity, etc. The system disk in this embodiment is used to install and run the operating system and is a core component of the cloud host. The project ID, user ID, specification ID, network ID, and system disk information corresponding to the disk to be migrated in this embodiment play a vital role in the cloud environment. Together, they form the basic framework of cloud resource management, ensuring effective resource allocation, secure access, and efficient operation. In actual operation, these elements need to be reasonably configured according to specific needs and scenarios to achieve the best cloud resource utilization and management effect.

[0089] It should be further explained that the above-mentioned upgrade migration method may also include: obtaining the upgrade migration task status; judging whether the upgrade migration task is completed according to the upgrade migration task status; if so, setting it as a completed flag; otherwise, obtaining the upgrade migration task failure log; analyzing the upgrade migration task failure log to determine the failure cause; determining to modify the relevant configuration information of the startup image based on the failure cause to obtain the modified startup image; performing upgrade migration based on the modified startup image; or, when it is determined that there is a problem with the network based on the failure cause, monitoring the network between the source node and the target node to be migrated, and when it is determined that the current network can meet the upgrade migration requirements, determining to use Start the image for migration; or when it is determined that there is a problem with the target node based on the cause of failure, determine the time to repair the problem of the target node; when the time to repair the problem is less than the minimum time, determine to migrate after solving the problem through the first solution; wherein the first solution includes at least one of restarting and software updating; when the time to repair the problem is not less than the minimum time, determine the migration plan; wherein the migration plan includes migration time, migration files, and problem response plans; wherein the migration time is the time determined according to the problem solving time and system performance, the migration file is the file uploaded during the migration process, and the problem response plan is the problem solving method generated according to the current problem. The upgrade migration task status in this embodiment may include waiting, upgrade in progress, upgrade completed, upgrade failed, etc. In this embodiment, during the entire upgrade migration process, continuously monitoring the task status, accurately analyzing the cause of failure, and timely adjusting the strategy and executing it are key steps to ensure the success of the task. Through careful planning and effective execution, the risk of migration failure can be minimized, and the smooth transition of the system and the continuity of the business can be ensured.

[0090] It should be further explained that the VXLAN technology is used to achieve the isolation of the configured target migration node, or the virtual machine management tool is used to achieve the isolation of the configured target migration node. VXLAN (Virtual eXtensible Local Area Network) is a network virtualization technology that establishes a logical tunnel on the existing network, encapsulates the virtual machine's data packet in a UDP data packet, and transmits it through the IP network. This encapsulation method allows the virtual machine's data packet to communicate across different subnets and data centers while maintaining the isolation and security of the network. VXLAN technology builds a virtual large Layer 2 network on the Layer 3 network. As long as the virtual machine route is reachable, it can be planned to the same large Layer 2 network. This solves the problem of limited virtual machine migration range. Using the KVM virtual machine management tool: KVM (Kernel-based Virtual Machine) is an open source system virtualization module that allows multiple isolated virtual environments to run on a single physical hardware. By using KVM management tools such as libvirt, virsh, and virt-manager, you can create, manage, and isolate virtual machines. Alternatively, in the cloud platform, this embodiment can limit the communication between virtual machines by setting network security groups, access control lists, and firewall rules, thereby achieving network-level isolation. These policies can be flexibly configured according to actual needs to ensure that only authorized traffic can enter or leave the virtual machine. Alternatively, by using a distributed storage system or an independent storage volume, exclusive storage resources can be allocated to each virtual machine. In this way, even if the virtual machines share the same physical server, their storage space is isolated from each other, thereby preventing data leakage and tampering.

[0091] An upgraded migration method improved by an embodiment of the present invention may include: S101, installing a driver to a source node to obtain a source node to be migrated; S102, obtaining a startup image of the source node to be migrated when determining that the network between the source node to be migrated and the target node is interconnected; wherein the information in the startup image includes the basic software of the source node, the source node migration script and the target node script; the basic software is software set according to requirements; the source node migration script configures the information of the source node according to the destination node of the migration; the target node script is a script for configuring the target node information; the migration from the source node to the target node is a cross-version migration; S103, using the source node migration script in the startup image to migrate the data of the basic software related to the source node to the target node; S104, when determining that the migration is completed, using the target node script to automatically configure the source node migrated to the target node to obtain a configured target migration node, and using the cloud management platform to manage the target migration node. Compared with the current cloud management platform which only performs internal migration of the existing version, and can migrate node A to node B in one environment, or migrate from an openstack environment to VMware, and vice versa, but cannot migrate from a lower version of openstack to a newer version of openstack, or from a lower version of VMware to a higher version of VMware, the beneficial effects of the present invention are: customizing the startup image according to the old version of the node to be migrated, presetting the parameters required for the target node to be migrated, and then executing the source node migration script, and after waiting for the migration script to be executed, deploying the image to the target node according to the target node script, thereby realizing the migration of the old and new versions, ensuring the integrity of the business data, and enabling the old version data to continue to be used.

[0092] In order to make the present invention easier to understand, please refer to Figure 2 , Figure 2 A schematic diagram of the structure of a cross-cloud platform migration framework based on offline tools provided in an embodiment of the present invention may specifically include: installing a virtio driver on the source node to be migrated (the virtio driver is a semi-virtualized driver solution for improving the I / O performance of a virtual machine). In order to avoid the problem of being unable to start when migrating to another cloud platform, the source virtual machine or physical node to be migrated is connected to the management network and business network of the storage end, and the source node needs to be shut down for offline migration. The tool mainly includes a migration preparation module, a data migration module, a system configuration module, and a management integration module. The migration preparation module is used to collect information about the source virtual machine and generate a migration plan; the data migration module is used to migrate the disk data and memory data of the virtual machine; the system configuration module is used to perform system configuration on the virtual machine after the migration is completed; and the management integration module is used to incorporate the migrated virtual machine into the management system of the target cloud platform.

[0093] Migration preparation module: responsible for collecting information about the source virtual machine or physical machine, such as the operating system, memory size, disk capacity, etc. Based on the collected information, it creates an ISO image of the LiveCD, which contains basic software, configuration files, and preset virtual machine scripts to support offline migration.

[0094] This embodiment makes an offline tool based on the specific migration data, and performs some customized operations based on the LiveCD ISO image made by centos7.4, including basic software, configuration files, and scripts. If the source node system is running, the disk cannot be directly migrated, so this solution adopts an offline migration method, using a customized LiveCD image. The source node is started through the LiveCD, so that the disk of the source node is idle and the migration operation can be performed. The source node restarts and restarts through the customized image.

[0095] Data migration module: After receiving the migration plan, the module executes the migration script. The data migration module adopts an incremental migration strategy, first migrating the disk data of the virtual machine, and then migrating the memory data as needed to reduce the migration time and data volume; at the same time, it ensures that the migration fails due to a large network bandwidth caused by a large amount of migration at one time.

[0096] The migration script for executing the data migration module in this embodiment is the configuration script for executing the data migration module. The migration script in this embodiment will modify the IP and storage end (rbd configuration, G2 configuration, G5 configuration) information of the source node to be migrated, and the specific settings are based on the different conditions of each platform. Different files need to be executed when migrating to different storage backends. If migrating to rbd, modify #icfs config according to the on-site situation; if it is UV3 version and above, you need to execute bashinstall to install the UV3 client; if migrating to G2 / G5, modify #iscsi config according to the specific G2 / G5 username and password used; after the modification is completed, execute the configuration script. The configuration script in this embodiment corresponds to the source node migration script above.

[0097] System configuration module: After the migration is completed, the corresponding information in the target node is configured, including network, specifications, firewall, project and other information. It can automatically configure the information required to create a cloud host in the target node. According to the migration plan, it automatically configures the appropriate information to ensure that the migrated cloud host can run normally.

[0098] In this embodiment, the corresponding information in the target node can be configured to obtain the target node script. Figure 2The prefabricated target node in the creates cloud host parameters. The information of the target node in this embodiment may also include the project ID, user ID, specification ID, network ID, and the storage end corresponding to the disk. This embodiment can migrate the disk on the source node to rbd or G2 / G5, automatically manage the cloud hard disk after the migration is completed, and support the creation of a cloud host based on a specified system disk. The format is as follows, where different migration scripts are selected in the migration script according to different versions of the cloud management platform, and the migration scripts of each version are different; the storage backend is G2, G5 or rbd; the name is custom, and this name is the command to migrate to the storage backend; if there are multiple disks to be migrated, they are separated by spaces in the middle; the -s parameter is followed by the system disk, and the migration script will create a cloud host based on the disk. This parameter can also be omitted. If it is not added, only the cloud hard disk will be managed, and the cloud host will not be created. The specific execution method is as follows: [python migration script file storage backend name disk to be migrated-s system disk].

[0099] Management integration module: responsible for incorporating the migrated virtual machines into the management system of the target cloud platform, realizing automated resource management, and ensuring that business data can still be fully used in the target cloud management platform.

[0100] The embodiment of the present invention realizes data consistency and improves migration efficiency through an offline migration tool, simplifies the migration process, reduces migration costs, and adopts software-defined migration technology and automated configuration strategies to reduce human intervention and improve migration efficiency and accuracy. Through detailed description and optimization of the migration process, the migration time is shortened and data security is improved. The method is simple to operate, and only requires presetting of configuration information of different versions and required storage end information. It can be used for cross-platform migration of multiple versions, reducing the manpower and time costs caused by maintaining old versions, and can realize migration of different platforms. It can flexibly ensure the availability and integrity of the business on each version, thereby ensuring major accidents caused by data loss. Even if the old version cannot be maintained, it will not affect the normal operation of the business. Different ISO images can be formulated according to different versions for adaptation, and the running status of the latest version of the cloud management platform can be uniformly managed and monitored, simplifying the operation and maintenance work.

[0101] The following is an introduction to an upgrade migration device provided by an embodiment of the present invention. The upgrade migration device described below and the upgrade migration method described above can be referenced to each other.

[0102] Figure 3 A schematic diagram of the structure of an upgrade migration device provided by an embodiment of the present invention, the device may include:

[0103] The source node to be migrated determining module 100 is used to install the driver to the source node to obtain the source node to be migrated;

[0104] The startup image acquisition module 200 is used to obtain the startup image of the source node to be migrated when determining that the network between the source node to be migrated and the target node is interconnected; wherein the information in the startup image includes the basic software of the source node, the source node migration script and the target node script; the basic software is software set according to the requirements; the source node migration script is the information of the source node configured according to the destination node of the migration; the target node script is a script for configuring the target node information; the migration from the source node to the target node is a cross-version migration;

[0105] A data migration module 300 is used to migrate the data of the basic software related to the source node to the target node by using the source node migration script in the startup image;

[0106] The target migration node configuration module 400 is used to determine when the migration is completed, automatically configure the source node migrated to the target node using the target node script, obtain the configured target migration node, and manage the target migration node using the cloud management platform.

[0107] It should be further explained that, based on the above embodiment, the above upgrade migration device may further include:

[0108] A source node information acquisition module is used to obtain the operating system, memory size and disk capacity information of the source node to be migrated;

[0109] The startup image making module is used to make the startup image according to the operating system, the memory size and the disk capacity information.

[0110] Further, based on any of the above embodiments, the data migration module 300 may include:

[0111] Each type of basic software data determination unit is used to determine the type of basic software data and obtain each type of basic software data; wherein the type includes disk data and memory data;

[0112] The incremental migration unit is used to determine the priority of each type of basic software data, and migrate the data incrementally to the target node using the source node migration script according to the priority.

[0113] It should be further explained that, based on any of the above embodiments, the above upgrade migration device may further include:

[0114] A type determination module, used to determine the type of the target node; wherein the type of the target node is any one of a block storage node, a component disk node, and a virtualization node;

[0115] A configuration file modification module, used to modify the configuration file according to the type of the target node to obtain a modified configuration file;

[0116] A modified source node migration script determination module, used to execute a configuration script including the modified configuration file to obtain a modified source node migration script;

[0117] Accordingly, the data migration module 300 includes:

[0118] The data migration unit is used to migrate the data of the basic software related to the source node to the target node by using the modified source node migration script.

[0119] Further, based on any of the above embodiments, the target node script includes network, specification, firewall and project information.

[0120] It should be further explained that, based on any of the above embodiments, the above upgrade migration device may further include:

[0121] A script file acquisition module of a cloud host, used to acquire a script file of a cloud host; wherein the script file of the cloud host includes a project ID, a user ID, a specification ID, a network ID, and a system disk corresponding to the disk to be migrated;

[0122] The cloud host creation module is used to execute the script file of the cloud host and create a new cloud host on the configured target migration node.

[0123] It should be further explained that, based on any of the above embodiments, the above upgrade migration device may further include:

[0124] The upgrade migration task status acquisition module is used to obtain the upgrade migration task status;

[0125] A judgment module, used to judge whether the upgrade migration task is completed according to the upgrade migration task status;

[0126] A completed identification setting module, used for setting the completed identification if yes;

[0127] The upgrade migration task failure log acquisition module is used to obtain the upgrade migration task failure log;

[0128] A failure cause determination module is used to analyze the upgrade migration task failure log to determine the failure cause;

[0129] A modified startup image determination module, used for determining, based on the failure cause, to modify the relevant configuration information of the startup image to obtain a modified startup image;

[0130] An upgrade migration module, used for performing upgrade migration based on the modified startup image;

[0131] A monitoring module, for monitoring the network between the source node and the target node to be migrated when it is determined that there is a problem with the network based on the failure cause, and determining to use the startup image for migration when it is determined that the current network can be upgraded to the migration requirement;

[0132] A repair time determination module, used to determine the time required to repair the problem of the target node when it is determined that the target node has a problem based on the failure cause;

[0133] A problem solving module, configured to determine to perform migration after solving the problem through a first solution when the time required to fix the problem is less than a minimum time required; wherein the first solution includes at least one of restarting and software updating;

[0134] A migration plan determination module is used to determine the migration plan when the repair time of the problem is not less than the minimum time; wherein, the migration plan includes migration time, migration files, and problem response plan; wherein, the migration time is the time determined according to the problem solving time and system performance, the migration file is the file uploaded during the migration process, and the problem response plan is the problem solving method generated according to the current problem.

[0135] It should be noted that the order of the modules and units in the above-mentioned upgrade migration device can be changed without affecting the logic.

[0136] Figure 3 The description of the features in the corresponding embodiments can be found in Figure 3 The relevant descriptions of the corresponding embodiments will not be repeated here one by one.

[0137] An upgrade migration device provided by an embodiment of the present invention may include: a source node determination module 100 to be migrated, which is used to install a driver to a source node to obtain a source node to be migrated; a startup image acquisition module 200, which is used to obtain a startup image of the source node to be migrated when determining that the network between the source node to be migrated and the target node is interconnected; wherein the information in the startup image includes the basic software of the source node, the source node migration script and the target node script; the basic software is software set according to requirements; the source node migration script configures the information of the source node according to the destination node of the migration; the target node script is a script for configuring the target node information; the migration from the source node to the target node is a cross-version migration; a data migration module 300, which is used to use the source node migration script in the startup image to migrate the data of the basic software related to the source node to the target node; a target migration node configuration module 400, which is used to automatically configure the source node migrated to the target node using the target node script when determining that the migration is completed, obtain a configured target migration node, and manage the target migration node using a cloud management platform. Compared with the current cloud management platform which only performs internal migration of the existing version, and can migrate node A to node B in one environment, or migrate from an openstack environment to VMware, and vice versa, but cannot migrate from a lower version of openstack to a newer version of openstack, or from a lower version of VMware to a higher version of VMware, the beneficial effects of the present invention are: customizing the startup image according to the old version of the node to be migrated, presetting the parameters required for the target node to be migrated, and then executing the source node migration script, and after waiting for the migration script to be executed, deploying the image to the target node according to the target node script, thereby realizing the migration of the old and new versions, ensuring the integrity of the business data, and enabling the old version data to continue to be used.

[0138] An upgrade migration device provided by an embodiment of the present invention is introduced below. The upgrade migration device described below and the upgrade migration method described above can refer to each other.

[0139] Figure 4 A schematic diagram of the structure of an upgrade migration device provided by an embodiment of the present invention is shown in FIG. Figure 4 As shown, the upgrade migration device includes: a memory 60 for storing computer programs;

[0140] The processor 61 is used to implement the steps of the upgrade migration method in the above embodiment when executing the computer program.

[0141] The upgrade migration device provided in this embodiment may include but is not limited to a smart phone, a tablet computer, a laptop computer, or a desktop computer.

[0142] Among them, the processor 61 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 61 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 61 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a central processing unit (CPU); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 61 may be integrated with a graphics processing unit (GPU), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 61 may also include an artificial intelligence (AI) processor, which is used to process computing operations related to machine learning.

[0143] The memory 60 may include one or more computer-readable storage media, which may be non-transitory. The memory 60 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 60 is at least used to store the following computer program 601, wherein, after the computer program is loaded and executed by the processor 61, it can implement the relevant steps of the upgrade migration method disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 60 may also include an operating system 602 and data 603, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 602 may include Windows, Unix, Linux, etc. Data 603 may include but is not limited to upgrade migration data, etc.

[0144] In some embodiments, the upgrade migration device may further include a display screen 62 , an input and output interface 63 , a communication interface 64 , a power supply 65 , and a communication bus 66 .

[0145] Those skilled in the art will understand that Figure 4 The structure shown in the figure does not constitute a limitation on the upgrade migration device, and may include more or fewer components than those shown in the figure.

[0146] It is understandable that if the upgrade migration method in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the current technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium to execute all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), electrically erasable programmable ROM, register, hard disk, removable disk, CD-ROM, magnetic disk or optical disk and other media that can store program codes.

[0147] Based on this, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the upgrade migration method described above are implemented.

[0148] The above is a detailed introduction to an upgrade migration device provided by an embodiment of the present invention. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0149] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0150] The above is a detailed introduction to an upgrade migration method, device, equipment and computer-readable storage medium provided by the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present invention, several improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the scope of protection of the claims of the present invention.

Claims

1. An upgrade migration method, characterized in that: include: Install the driver to the source node to obtain the source node to be migrated; When it is determined that the network between the source node to be migrated and the target node is interconnected, the startup image of the source node to be migrated is obtained; wherein the information in the startup image includes the basic software of the source node, the source node migration script and the target node script; the basic software is software set according to the requirements; the source node migration script is the information of the source node configured according to the destination node of the migration; the target node script is the script for configuring the target node information; the migration from the source node to the target node is a cross-version migration; Migrating the data of the basic software related to the source node to the target node using the source node migration script in the startup image; When it is determined that the migration is completed, the target node script is used to automatically configure the source node migrated to the target node to obtain a configured target migration node, and the target migration node is managed by the cloud management platform.

2. The upgrade migration method according to claim 1, characterized in that: Before obtaining the startup image of the source node to be migrated, the method further includes: Obtaining the operating system, memory size, and disk capacity information of the source node to be migrated; The startup image is created according to the operating system, the memory size and the disk capacity information.

3. The upgrade migration method according to claim 1, characterized in that: Migrating the data of the basic software related to the source node to the target node by using the source node migration script in the startup image, including: Determine the type of basic software data and obtain basic software data of each type; wherein the types include disk data and memory data; The priorities of the various types of basic software data are determined, and the data increments are migrated to the target node using the source node migration script according to the priorities.

4. The upgrade migration method according to any one of claims 1 to 3, characterized in that: In the case where it is determined that the network between the source node to be migrated and the target node is interconnected, after obtaining the startup image of the source node to be migrated, the method further includes: Determine the type of the target node; wherein the type of the target node is any one of a block storage node, a component disk node, and a virtualization node; Modify the configuration file according to the type of the target node to obtain a modified configuration file; Execute the configuration script including the modified configuration file to obtain the modified source node migration script; Accordingly, using the source node migration script in the startup image to migrate the data of the basic software related to the source node to the target node includes: The modified source node migration script is used to migrate the data of the basic software related to the source node to the target node.

5. The upgrade migration method according to claim 1, characterized in that: The target node script includes network, specification, firewall and project information.

6. The upgrade migration method according to claim 1, characterized in that: When it is determined that the migration is completed, the target node script is used to automatically configure the source node migrated to the target node, and after obtaining the configured target migration node, the method further includes: Obtain a script file of the cloud host; wherein the script file of the cloud host includes a project ID, a user ID, a specification ID, a network ID, and a system disk corresponding to the disk to be migrated; Execute the script file of the cloud host and create a new cloud host on the configured target migration node.

7. The upgrade migration method according to claim 1, characterized in that: The upgrade migration method further includes: Get the upgrade migration task status; Determine whether the upgrade migration task is completed according to the upgrade migration task status; If yes, set it to completed flag; Otherwise, obtain the upgrade migration task failure log; Analyze the upgrade migration task failure log to determine the cause of the failure; Determine to modify the relevant configuration information of the startup image based on the failure reason, and obtain a modified startup image; Performing upgrade migration based on the modified startup image; or when it is determined that there is a problem with the network based on the failure cause, monitoring the network between the source node and the target node to be migrated, and when it is determined that the current network can be upgraded to the migration requirements, determining to use the startup image for migration; Or when it is determined that there is a problem with the target node based on the failure cause, determining the time required to repair the problem of the target node; When the time required to fix the problem is less than the minimum time required, determine to migrate after solving the problem through a first solution; wherein the first solution includes at least one of restarting and software updating; When the repair time of the problem is not less than the minimum time, a migration plan is determined; wherein the migration plan includes migration time, migration files, and problem response plan; wherein the migration time is the time determined according to the problem solving time and system performance, the migration files are files uploaded during the migration process, and the problem response plan is a problem solving method generated according to the current problem.

8. An upgrade migration device, characterized in that: include: A module for determining a source node to be migrated, used for installing a driver on a source node to obtain a source node to be migrated; A startup image acquisition module is used to obtain the startup image of the source node to be migrated when it is determined that the network between the source node to be migrated and the target node is interconnected; wherein the information in the startup image includes the basic software of the source node, the source node migration script and the target node script; the basic software is software set according to the requirements; the source node migration script is the information of the source node configured according to the destination node of the migration; the target node script is a script for configuring the target node information; the migration from the source node to the target node is a cross-version migration; A data migration module, used to migrate the data of the basic software related to the source node to the target node by using the source node migration script in the startup image; The target migration node configuration module is used to determine when the migration is completed, use the target node script to automatically configure the source node migrated to the target node, obtain the configured target migration node, and use the cloud management platform to manage the target migration node.

9. An upgrade migration device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute the computer program to implement the steps of the upgrade migration method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the upgrade migration method according to any one of claims 1 to 7 are implemented.

Citation Information

Cited By

  • Application migration method and device, equipment, readable storage medium and program product

    CN120104289A

  • Distributed storage system automatic capacity expansion method and system and readable storage medium

    CN120596034A