CN119088409A - Upgrade migration method, device, equipment and computer readable storage medium - Google Patents
Upgrade migration method, device, equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN119088409A CN119088409A CN202411368068.5A CN202411368068A CN119088409A CN 119088409 A CN119088409 A CN 119088409A CN 202411368068 A CN202411368068 A CN 202411368068A CN 119088409 A CN119088409 A CN 119088409A
- Authority
- CN
- China
- Prior art keywords
- migration
- node
- source node
- script
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses an upgrade migration method, device, equipment and a computer readable storage medium, which are applied to the technical field of migration and comprise the steps of installing a driver to a source node to obtain a source node to be migrated, acquiring a starting mirror image of the source node to be migrated under the condition of determining network intercommunication between the source node to be migrated and a target node, utilizing a source node migration script in the starting mirror image to migrate data of basic software related to the source node to the target node, automatically configuring the source node migrated to the target node by utilizing the target node script when the migration is determined to be completed, obtaining the configured target migration node, and managing the target migration node by utilizing a cloud management platform. Under the condition of network intercommunication between the source node to be migrated and the target node, the source node migration script is executed, and after the execution of the source migration script is completed, the target node script is utilized to automatically configure the source node migrated to the target node, so that the migration of the node in different environments is realized.
Description
Technical Field
The present invention relates to the field of migration technologies, and in particular, to an upgrade migration method, apparatus, device, and computer readable storage medium.
Background
At present, the cloud management platform only makes migration inside the existing version, and can migrate from an A node to a B node in one environment or from an openstack environment (an open-source cloud computing management platform project) to VMware (virtual machine software), or vice versa, but cannot migrate from a low-version openstack to a new-version openstack or from a low-version VMware to a high-version VMware.
It can be seen how to implement version migration under the condition of ensuring the integrity of service data is a problem to be solved by those skilled in the art.
Disclosure of Invention
Accordingly, an object of the present invention is to provide an upgrade migration method, apparatus, device, and computer readable storage medium, which solve the problem that the low version cannot be realized in the prior art.
In order to solve the technical problems, the invention provides an upgrade migration method, which comprises the following steps:
Installing a drive to a source node to obtain a source node to be migrated;
Acquiring a starting mirror image of a source node to be migrated under the condition of network intercommunication between the source node to be migrated and a target node, wherein information in the starting mirror image comprises basic software of the source node, a source node migration script and a target node script, wherein the basic software is software set according to requirements, the source node migration script is information of the source node configured according to a migrated target node, and the target node script is a script configured with target node information;
migrating data of the base software related to the source node to the target node by utilizing a source node migration script in the starting mirror image;
When the migration is determined to be completed, the target node script is utilized to automatically configure a source node migrated to a target node, a configured target migration node is obtained, and the cloud management platform is utilized to manage the target migration node.
In one aspect, before the obtaining the boot image of the source node to be migrated, the method further includes:
Acquiring the operating system, memory size and disk capacity information of the source node to be migrated;
and manufacturing the starting mirror image according to the operating system, the memory size and the disk capacity information.
In one aspect, migrating data of base software related to the source node to the target node by using a source node migration script in the boot image includes:
determining the type of data of the basic software to obtain various types of basic software data, wherein the types comprise disk data and memory data;
And determining the priority of the various types of basic software data, and utilizing the source node migration script to migrate the data increment to the target node according to the priority.
On the one hand, under the condition that the network intercommunication between the source node to be migrated and the target node is determined, after the starting mirror image of the source node to be migrated is obtained, the method further comprises the following steps:
determining the type of a 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;
Modifying the configuration file according to the type of the target node to obtain a modified configuration file;
Executing the configuration script comprising the modified configuration file to obtain a modified source node migration script;
correspondingly, migrating the data of the base software related to the source node to the target node by using the source node migration script in the boot image comprises the following steps:
and migrating the data of the basic software related to the source node to the target node by utilizing the modified source node migration script.
In one aspect, the target node script includes network, specification, firewall, and project information.
On the one hand, when determining that the migration is completed, automatically configuring the source node migrated to the target node by using the target node script, and after obtaining the configured target migration node, further including:
The method comprises the steps of obtaining a script file of a cloud host, wherein the script file of the cloud host comprises an item ID, a user ID, a specification ID, a network ID and a system disk corresponding to a disk to be migrated;
Executing the script file of the cloud host, and creating a new cloud host at the configured target migration node.
In one aspect, the upgrade migration method further includes:
Acquiring an upgrade migration task state;
Judging whether the upgrade migration task is completed or not according to the upgrade migration task state;
If yes, setting the mark as finished;
otherwise, obtaining an upgrade migration task failure log;
analyzing the upgrade migration task failure log, and determining a failure reason;
Based on the failure reason, determining to modify the relevant configuration information of the starting mirror image to obtain a modified starting mirror image;
performing upgrade migration based on the modified boot image;
or monitoring the network between the source node to be migrated and the target node when the network is determined to have a problem based on the failure reason, and determining to utilize the starting mirror image to migrate when the current network upgradeable migration requirement is determined;
or when the problem of the target node is determined to exist based on the failure reason, determining the problem repairing duration of the target node;
when the repair time length of the problem is smaller than the minimum time length, determining to migrate after the problem is solved by a first solution, wherein the first solution comprises at least one of restarting and software updating;
And determining a migration plan when the repair time of the problem is not less than the minimum time, wherein the migration plan comprises migration time, a migration file and a problem solving scheme, the migration time is determined according to the problem solving time and the system performance, the migration file is a file in the uploading migration process, and the problem solving scheme is a problem solving mode generated according to the current problem.
The invention also provides an upgrade migration device, which comprises:
the source node to be migrated determining module is used for installing a drive to the source node to obtain the source node to be migrated;
The system comprises a starting mirror image acquisition module, a target node script, a source node migration script and a target node migration script, wherein the starting mirror image acquisition module is used for acquiring a starting mirror image of a source node to be migrated under the condition of network intercommunication between the source node to be migrated and the target node, and information in the starting mirror image comprises basic software of the source node, the source node migration script and the target node script, wherein the basic software is software set according to requirements;
The data migration module is used for migrating the data of the basic software related to the source node to the target node by utilizing the source node migration script in the starting mirror image;
And the target migration node configuration module is used for automatically configuring the source node migrated to the target node by utilizing the target node script when the migration is determined to be completed, obtaining the configured target migration node, and managing the target migration node by utilizing the cloud management platform.
The invention also provides upgrade migration equipment, which comprises:
a memory for storing a computer program;
and a processor for executing the computer program to implement the steps of the upgrade migration method as described above.
The present invention also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of the upgrade migration method as described above.
The embodiment of the invention also provides a computer program product, which comprises a computer program/instruction, wherein the computer program/instruction realizes the steps of the upgrade migration method when being executed by a processor.
The embodiment of the invention aims to provide an upgrade migration method, device, equipment and a computer readable storage medium, which can solve the problem that cross-version migration cannot be realized.
The method comprises the steps of installing a driver to a source node to obtain the source node to be migrated, acquiring a starting mirror image of the source node to be migrated under the condition of network intercommunication between the source node to be migrated and a target node, wherein information in the starting mirror image comprises basic software of the source node, source node migration scripts and target node scripts, the basic software is software set according to requirements, the source node migration scripts are information of the source node configured according to migrated target nodes, the target node scripts are scripts configured with target node information, migration from the source node to the target node is cross-version migration, data of the basic software related to the source node is migrated to the target node by utilizing the source node migration scripts in the starting mirror image, and when the migration is completed, the target node scripts are utilized to automatically configure the source node migrated to the target node, so that the configured target migration node is obtained, and management is conducted on the target migration node by utilizing a cloud management platform.
Compared with the prior cloud management platform which only performs migration in the prior version (same environment), the method has the advantages that the method can migrate from an A node to a B node in one environment or from an openstack environment to VMware, or vice versa, but cannot migrate from a low-version openstack to a new-version openstack or from a low-version VMware to a high-version VMware, and has the advantages that compared with the prior cloud management platform which only performs migration in the prior version (same environment), the method starts the node to be migrated in the prior version through the customized tool mirror image, presets required parameters of the target environment to be migrated, then executes the source node migration script, and arranges the mirror image to the target node according to the target node script after the execution of the migration script is completed, so that the new and old version migration is realized.
Drawings
For a clearer description of embodiments of the present invention, the drawings that are required to be used in the embodiments will be briefly described, it being apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.
FIG. 1 is a flowchart of an upgrade migration method according to an embodiment of the present invention;
Fig. 2 is a schematic structural diagram of a cross-cloud platform migration framework based on an offline tool according to an embodiment of the present invention;
Fig. 3 is a schematic structural diagram of an upgrade migration apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an upgrade migration device according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by a person of ordinary skill in the art without making any inventive effort are within the scope of the present invention.
The terms "comprising" and "having" in the description of the invention and in the above-described figures, as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may include other steps or elements not expressly listed.
Some of the terms or terms appearing in describing embodiments of the present invention are applicable to the following explanation:
ISO (International Organization for Standardization, optical disc image file);
LiveCD A very powerful tool that can run a complete operating system without affecting the installation of existing systems, and can perform diagnosis and repair by LiveCD without worrying about further damage to current or data no matter what problem the system encounters;
Openstack, open-source cloud computing management platform project;
VMware, virtual machine software;
RBD, i.e., RADOS Block Device for short, RBD block storage is the most stable and most commonly used storage type.
G2 configuration and G5 configuration refer to hardware and software settings, respectively, for different model devices. G2 configures hard disk information related to a specific model of device, such as capacity, interface type, etc. This helps ensure compatibility and performance of the data store during device migration or upgrades. The G5 configuration generally refers to a higher performance device configuration, such as a display card with Intel Ten-generation standard pressure processors, kuri 7-10750H and GeForce RTX 3050 Mobile 4 GB.
In order to better understand the aspects of the present invention, the present invention will be described in further detail with reference to the accompanying drawings and detailed description.
Next, an upgrade migration method provided by the embodiment of the present invention is described in detail. Fig. 1 is a flowchart of an upgrade migration method according to an embodiment of the present invention, where the method may include:
s101, installing a drive to a source node to obtain the source node to be migrated.
The execution body of this embodiment is an electronic device, which may be a computer, or a management platform that manages a cluster, for example. This embodiment is not limited to a specific source node as long as it is required to migrate from a low version a environment to a high version B environment. For example, the source node in this embodiment may be a low version of openstack, or the source node in this embodiment may also be a low version of VMware. The lower version in this embodiment refers to the older version of the software, hardware, or system, and is typically not the most up-to-date version. The driver in this embodiment refers to a software interface of a computer hardware device for communication and control between an operating system and the hardware device.
It should be further noted that, before obtaining the boot image of the source node to be migrated, the method may include obtaining information of an operating system, a memory size and a disk capacity of the source node to be migrated, and making the boot image according to the information of the operating system, the memory size and the disk capacity. The operating system information in this embodiment may include the type and version of the operating system, which first requires a determination of the source node's operating system type (e.g., linux, windows, etc.) and its specific version. This helps to ensure the compatibility of the boot image with the source node, avoiding boot failure due to incompatibility. Kernel parameters of the operating system, which are critical for making a boot image, are determined, such as boot mode, boot options, etc. The memory size in this embodiment includes the total memory size of the source node is obtained to ensure that the boot image can provide adequate memory support for the system. This is critical to the proper operation and performance of the system. And memory allocation, namely knowing the memory allocation condition of the source node, such as which processes occupy more memory and which memory areas are used for caching and the like. This facilitates a reasonable memory configuration when creating the boot image. The disk capacity information in this embodiment includes total disk capacity, which is obtained from the source node in order to allocate sufficient storage space for the boot image to be made, and partition information. At the same time, this also helps to assess the data volume and storage requirements of the system. Partition information, namely knowing the partition condition of the disk of the source node, wherein the partition condition comprises the number of partitions, the size of each partition, the type of a file system and the like. This information is critical to making a boot image that contains the correct partition structure.
It should be further noted that, in this embodiment, an appropriate boot image format may be selected according to the type of operating system of the source node and the requirements of the target node. Common formats include ISO, IMG, VMDK, and the like. Each format has the characteristics and the applicable scene, 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, which can simulate the data structure of hard disk, floppy disk or other storage devices, VMDK (Virtual MACHINE DISK) is a Virtual disk format developed by VMware corporation, and is mainly used in the Virtual machine environment of VMware. The boot image contains the operating system installation file of the source node for system installation on the target node. This typically involves copying the installation medium (e.g., ISO file) of the operating system into an image file. Driver integration if the source node uses specific hardware drivers, these drivers need to be integrated into the image when making the boot image. This helps ensure that the target node can properly identify and use these hardware devices after startup. Configuration file replication, namely, copying configuration files (such as network settings, user accounts and the like) on the source node into the boot image. This helps to quickly restore the source node's configuration environment at the target node.
S102, acquiring a starting mirror image of a source node to be migrated under the condition of network intercommunication between the source node to be migrated and a target node, wherein information in the starting mirror image comprises 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 is information of the source node configured according to the migrated target node, the target node script is a script for configuring target node information, and migration from the source node to the target node is cross-version migration.
The target node of this embodiment is a high version source node. For example, when the source node is a low version of openstack, the target node is a high version of openstack, and when the source node is a low version of VMware, the target node is a high version of VMware. The network interworking between the source node to be migrated and the target node in this embodiment is by configuring the network interworking between the source node to be migrated and the target node, and the boot image in this embodiment is a file containing a complete operating system or boot loader for loading and executing at the time of computer startup. It may be a disk-based image (e.g., an ISO file) or a network boot image (e.g., a PXE image). The underlying software of the source node in this embodiment typically includes an operating system, a database management system, middleware, or an operating system and configuration files. In selecting such software, stability, performance, compatibility, and future extensibility thereof need to be considered. The source node migration script in the embodiment is used for automatically upgrading the source node according to the information of the source node configured by the migrated destination node. The target node script in this embodiment is a script that ensures that the source node's data is migrated to the target node to ensure compatibility and performance. The embodiment can execute a migration script, migrate the disk on the source node to rbd or G2/G5, and automatically receive the cloud hard disk after migration is completed, so as to support the creation of the cloud host based on the specified system disk.
It should be further noted that, in the case of determining the network interworking between the source node to be migrated and the target node, after obtaining the boot image of the source node to be migrated, the method may further include:
determining the type of a 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;
modifying the configuration file according to the type of the target node to obtain a modified configuration file;
Executing the configuration script comprising the modified configuration file to obtain a modified source node migration script;
Accordingly, the migration script of the source node in the boot image is utilized to migrate the data of the base software related to the source node to the target node, including:
and migrating the data of the basic software related to the source node to the target node by utilizing the modified source node migration script.
According to the embodiment, the configuration file can be modified according to the requirement to obtain the modified configuration file, so that migration is performed based on the modified configuration file, and the experience of a user is improved.
And S103, migrating the data of the basic software related to the source node to the target node by utilizing the source node migration script in the starting mirror image.
In this embodiment, the source node migration script may modify information such as the source node IP to be migrated, the storage information end (rbd configuration, G2 configuration (information of the disc of the component), and G5 configuration (upgrade version)), and specifically set according to different situations of each platform. If the client is migrated to rbd, if the version of UV3 is modified by the field condition modification # icfs config (configuration file, configuration script modifies the configuration file) or above, the flash interpreter is required to execute the flash install UV3 client, if the client is migrated to G2/G5, the configuration of # iscsi config (block level storage protocol) is modified according to the information such as the specific G2/G5 user name password.
It should be further noted that, using the source node migration script in the boot image to migrate the data of the base software related to the source node to the target node may include:
S1031, determining the type of data of the basic software to obtain various types of basic software data, wherein the types comprise disk data and memory data;
s1032, determining the priority of the various types of basic software data, and utilizing the source node migration script to migrate the data increment to the target node according to the priority.
When data is migrated to a target node, the source node migration script is utilized to migrate the data increment to the target node according to the priority, for example, disk data of a virtual machine is migrated first, then memory data is migrated according to the requirement, migration time and data volume are reduced, and network bandwidth is large and migration failure caused by overlarge primary migration volume is prevented. In addition, after the migration is completed, the embodiment can verify the migrated data, including checking the integrity, consistency and availability of the data, so as to ensure that the migrated data can be normally used and meet the service requirements. If a problem or abnormal situation is found, the problem or abnormal situation needs to be treated and repaired in time.
And S104, when the migration is completed, automatically configuring a 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.
In the implementation, the corresponding information in the target node can be configured by utilizing the target node script, including information such as a network, a specification, a firewall, a project and the like, so that the information required by the cloud host established by the target node can be automatically configured, and proper information can be automatically configured according to a migration plan, thereby ensuring that the migrated cloud host can normally operate. The network configuration in this embodiment includes an IP address, a subnet mask, a gateway configuration, etc., and the firewall configuration in this embodiment includes rules that configure inbound traffic that is allowed or denied for a particular IP address or port number. This helps to prevent unauthorized access and attacks. Meanwhile, some unnecessary outbound traffic can be limited according to service requirements. The specification in this embodiment refers to CPU and memory, storage space and I/O performance. The item information in this embodiment includes an item profile containing key information of the item, such as an item name, version number, dependency, and the like, and an environment file. By utilizing the embodiment, the migrated virtual machine can be incorporated into a management system of the target cloud platform, so that automatic management of resources is realized, and the business data can still be completely used in the target cloud platform.
It should be further noted that when it is determined that migration is completed, performing automatic configuration for a source node migrated to a target node by using a target node script, and after obtaining a configured target migration node, obtaining a script file of a cloud host, where the script file of the cloud host includes an item ID, a user ID, a specification ID, a network ID, and a system disk corresponding to a disk to be migrated, executing the script file of the cloud host, and creating a new cloud host at 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 configurations, etc. The project ID in the embodiment is used for grouping resources such as a cloud host according to logic or service requirements, is convenient to manage and search, and can realize access control on different projects and limit unauthorized access and operation. The user ID in this embodiment is an important credential for the user to log into the cloud platform for verifying the user's identity and rights. The specification ID in this embodiment defines the hardware configuration of the cloud host, such as the number of CPU cores, memory capacity, and the like. The system disk in this embodiment is used to install and run an operating system, and is a core component of the cloud host. The item 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 allocation, secure access and efficient operation of resources. In actual operation, these elements need to be reasonably configured according to specific requirements and scenes to achieve optimal cloud resource utilization and management effects.
The upgrade migration method further includes the steps of obtaining an upgrade migration task state, judging whether an upgrade migration task is completed according to the upgrade migration task state, setting to be completed identification if the upgrade migration task is completed, otherwise, obtaining an upgrade migration task failure log, analyzing the upgrade migration task failure log, determining a failure reason, determining relevant configuration information for modifying a startup image based on the failure reason to obtain a modified startup image, upgrading migration based on the modified startup image, or monitoring a network between a source node and a target node when a network is determined to have a problem based on the failure reason, determining migration by utilizing the startup image when a current network is determined to have an upgrade migration requirement, or determining a problem repair time length of the target node when the target node is determined to have a problem based on the failure reason, determining migration after the problem is solved by a first solution when the problem repair time length is smaller than a minimum time length, determining a migration plan when the problem repair time length is not smaller than the minimum time length in software update, wherein the migration plan comprises migration time, migration file and problem reply, or migration file is generated according to the migration file, and the problem reply time is determined to be the current problem reply time. The upgrade migration task state in this embodiment may include waiting, upgrade in progress, upgrade completed, upgrade failed, etc. In the whole upgrade migration process, the embodiment continuously monitors the task state, accurately analyzes the failure reason, timely adjusts the strategy and executes the strategy, which is a key step for ensuring the success of the task. Through careful planning and effective execution, the risk of migration failure can be reduced to the greatest extent, and smooth transition of the system and continuity of service are ensured.
It should be further noted that, isolation of the configured target migration node is achieved by using VXLAN technology, or isolation of the configured target migration node is achieved by using a virtual machine management tool. VXLAN (Virtual eXtensible Local Area Network) is a network virtualization technology that encapsulates a packet of a virtual machine in a UDP packet by establishing a logical tunnel over an existing network and transmits the packet over an IP network. The encapsulation mode enables the data packets of the virtual machine to be communicated across different subnets and data centers, and meanwhile, the isolation and the security of the network are maintained. The VXLAN technology constructs a virtual large two-layer network on a three-layer network, and the virtual machine can be planned into the same large two-layer network as long as the route of the virtual machine is reachable. This solves the problem of limited migration scope of the virtual machine. KVM (Kernel-based Virtual Machine), a system virtualization module of open source, is utilized as a KVM virtual machine management tool, which allows multiple isolated virtual environments to run on a single physical hardware. Creation, management, and quarantine of virtual machines can be achieved through the use of management tools for KVM, such as libvirt, virsh, virt-manager, etc. Or in the cloud platform, the communication between the virtual machines can be limited by setting a network security group, an access control list and firewall rules, so that isolation of a network layer is realized. These policies can be flexibly configured according to actual needs to ensure that only authorized traffic can enter or leave the virtual machine. Or by using a distributed storage system or independent storage volumes, dedicated storage resources may be allocated for each virtual machine. In this way, even if the same physical server is shared between virtual machines, their storage spaces are isolated from each other, thereby preventing data leakage and tampering.
The upgrade migration method comprises the steps of S101, installing a driver to a source node to obtain the source node to be migrated, S102, obtaining a starting mirror image of the source node to be migrated under the condition of network intercommunication between the source node to be migrated and a target node, wherein information in the starting mirror image comprises basic software of the source node, source node migration scripts and target node scripts, the basic software is software set according to requirements, the source node migration scripts are information of the source node configured according to the migrated target node, the target node scripts are scripts configured with target node information, migration from the source node to the target node is cross-version migration, S103, migrating data of the basic software related to the source node to the target node by using the source node migration scripts in the starting mirror image, S104, automatically configuring the source node migrated to the target node by using the target node scripts when the migration is completed, and managing the target migration node by using a cloud management platform. Compared with the prior cloud management platform which only makes migration inside the existing version, can migrate from an A node to a B node in an environment or from an openstack environment to VMware, or vice versa, but can not migrate from a low-version openstack to a new-version openstack or from a low-version VMware to a high-version VMware, the invention has the advantages that the mirror image is customized and started according to the old-version to-be-migrated node, the parameters required by the target node to be migrated are preset, then the source node migration script is executed, the mirror image is arranged to the target node according to the target node script after the execution of the migration script is waited, the migration of the new and old versions is realized, the integrity of service data is ensured, and the old version data can be continuously used.
In order to facilitate understanding of the present invention, referring to fig. 2 specifically, fig. 2 is a schematic structural diagram of a cross-cloud platform migration framework based on an offline tool provided by the embodiment of the present invention, which specifically may include installing virtio a source node to be migrated (virtio is a paravirtualized driving solution for improving I/O performance of a virtual machine), in order to avoid a problem that a migration cannot be started on another cloud platform, a management network of a source virtual machine or a physical node to be migrated and a storage end are communicated with a service network, and offline migration of the source node needs to be shut down. The system comprises a migration preparation module, a data migration module, a system configuration module and a management integration module, wherein the migration preparation module is used for collecting information of a source virtual machine and generating a migration plan, the data migration module is used for migrating disk data and memory data of the virtual machine, the system configuration module is used for carrying out system configuration on the virtual machine after migration is completed, and the management integration module is used for bringing the migrated virtual machine into a management system of a target cloud platform.
And the migration preparation module is responsible for collecting information of the source virtual machine or the physical machine, such as an operating system, a memory size, a disk capacity and the like, and making LiveCD ISO mirror images according to the collected information, wherein basic software, configuration files and preset virtual machine scripts are contained in the ISO mirror images so as to support offline migration.
This embodiment makes offline tools based on specific migration data, and does some customized operations including base software, configuration files, scripts, etc., based on the LiveCD ISO mirror of centos 7.4.4 production. If the source node system is in operation, the disk cannot be directly migrated, so that the scheme adopts an offline migration mode, a customized LiveCD mirror image is used, the source node is started through LiveCD, and thus the migration operation can be executed when the disk of the source node is idle. The source node is restarted by the customized mirror image.
The data migration module executes the migration script after the module migrates the data and receives the migration plan, and the data migration module adopts an incremental migration strategy to migrate the disk data of the virtual machine first, then migrate the memory data according to the need, reduce the migration time and the data volume, and simultaneously ensure that the network bandwidth is larger and the migration fails due to the overlarge primary migration volume.
In this embodiment, the migration script of the data migration module is a configuration script for executing the data migration module. The migration script in this embodiment modifies the information of the IP and storage end (rbd configuration, G2 configuration, G5 configuration) of the source node to be migrated, specifically according to different situations of each platform, and specifically set. Migration to different storage backend, the files that need to be executed are different. If the user is migrated to the rbd, the # icfs config is modified according to the field condition, if the user is in the UV3 version or above, the user needs to execute the flash software to install the UV3 client, if the user is migrated to the G2/G5, the # iscsi config is modified according to the information such as the specific G2/G5 user name password, and after the modification is completed, the configuration script is executed. The configuration script in this embodiment corresponds to the source node migration script above.
And the system configuration module is used for configuring corresponding information in the target node after the migration is completed, including information such as a network, a specification, a firewall, a project and the like, automatically configuring information required by the cloud host established by the target node, automatically configuring proper information according to a migration plan, and ensuring that the migrated cloud host can normally operate.
The corresponding information in the target node is configured in the embodiment to obtain the target node script, and the information of the target node in the embodiment corresponds to the prefabricated target node in fig. 2 to create the cloud host parameters. The information of the target node in this embodiment may further include an item ID, a user ID, a specification ID, a network ID, a storage end corresponding to the disk, and the like. The embodiment can transfer discs on a source node to rbd or G2/G5, automatically receive a tube cloud hard disc after the transfer is completed, support creation of a cloud host based on a specified system disc, and have the following format that different transfer scripts are selected according to different versions of a cloud tube platform in the transfer scripts, the transfer scripts of each version are different, the storage back end is G2, G5 or rbd, the name is customized, the name is a command for transferring to the storage back end, if a plurality of discs to be transferred exist, the middle is separated by a space, the back of an s parameter is a system disc, the transfer scripts can create the cloud host according to the disc, the parameter can be added, and only the tube cloud hard disc can be received without adding the parameter, and the cloud host can not be created.
And the management integration module is responsible for bringing the migrated virtual machine into a management system of the target cloud platform, realizing automatic management of resources and ensuring that the service data can still be used completely in the target cloud platform.
According to the embodiment of the invention, the consistency of data and the improvement of migration efficiency are realized through the offline migration tool, the migration process is simplified, the migration cost is reduced, the migration technology and the automatic configuration strategy based on software definition are adopted, the human intervention is reduced, and the migration efficiency and the migration accuracy are improved. Through detailed description and optimization of the migration process, the shortening of the migration time and the improvement of the data security are realized. The method is simple to operate, only configuration information of different versions and storage end information are required to be preset, cross-platform migration of multiple versions can be realized, labor and time cost caused by maintaining old versions are reduced, migration of different platforms can be realized, service availability and integrity can be flexibly ensured on each version, and important accidents caused by data loss are ensured, and even if old versions cannot be maintained, normal operation of the service is not influenced. The cloud management platform can formulate different ISO images to adapt according to different versions, can uniformly manage and monitor the running state of the cloud management platform in the latest version, and simplifies operation and maintenance work.
The upgrade migration apparatus provided by the embodiment of the present invention is described below, and the upgrade migration apparatus described below and the upgrade migration method described above may be referred to correspondingly.
Fig. 3 is a schematic structural diagram of an upgrade migration apparatus according to an embodiment of the present invention, where the apparatus may include:
the source node to be migrated determining module 100 is configured to install a driver to a source node to obtain a source node to be migrated;
The system comprises a starting image acquisition module 200, a target node script, a source node migration script and a target node migration script, wherein the starting image acquisition module 200 is used for acquiring a starting image of a source node to be migrated under the condition of network intercommunication between the source node to be migrated and the target node, and information in the starting image comprises basic software of the source node, the source node migration script and the target node script, wherein the basic software is software set according to requirements;
The data migration module 300 is configured to migrate, by using a source node migration script in the boot image, data of base software related to the source node to the target node;
And the target migration node configuration module 400 is configured to automatically configure a source node migrated to a target node by using the target node script when determining that migration is completed, obtain a configured target migration node, and manage the target migration node by using a cloud management platform.
It should be further noted that, based on the above embodiment, the upgrade migration apparatus may further include:
the source node information acquisition module is used for acquiring the operating system, the memory size and the disk capacity information of the source node to be migrated;
and the starting mirror image making module is used for making the starting mirror image according to the operating system, the memory size and the disk capacity information.
Further, based on any of the above embodiments, the data migration module 300 may include:
the system comprises a base software data determining unit, a storage unit and a data processing unit, wherein the base software data determining unit is used for determining the type of data of base software to obtain the base software data of various types;
and the increment migration unit is used for determining the priority of the various types of basic software data and utilizing the source node migration script to migrate the data increment to the target node according to the priority.
It should be further noted that, based on any of the above embodiments, the upgrade migration apparatus may further include:
The system comprises a type determining module, a storage module and a virtualization module, wherein the type determining module is used for determining the type of a target node, and the type of the target node is any one of a block storage node, a component disk node and a virtualization node;
the configuration file modification module is used for modifying the configuration file according to the type of the target node to obtain a modified configuration file;
The modified source node migration script determining module is used for executing the configuration script comprising the modified configuration file to obtain a modified source node migration script;
Accordingly, the data migration module 300 includes:
And the data migration unit is used for migrating the data of the basic software related to the source node to the target node by utilizing the modified source node migration script.
Further, based on any of the embodiments above, the target node script includes network, specification, firewall, and project information.
It should be further noted that, based on any of the above embodiments, the upgrade migration apparatus may further include:
the cloud host script file acquisition module is used for acquiring a cloud host script file, wherein the cloud host script file comprises a project ID, a user ID, a specification ID, a network ID and a system disk corresponding to a disk to be migrated;
And the cloud host creation module is used for executing the script file of the cloud host and creating a new cloud host at the configured target migration node.
It should be further noted that, based on any of the above embodiments, the upgrade migration apparatus may further include:
the upgrade migration task state acquisition module is used for acquiring the upgrade migration task state;
the judging module is used for judging whether the upgrade migration task is completed according to the upgrade migration task state;
the completed mark setting module is used for setting the completed mark if the completed mark is the completed mark;
the upgrade migration task failure log obtaining module is used for obtaining an upgrade migration task failure log if not;
the failure cause determining module is used for analyzing the upgrade migration task failure log and determining the failure cause;
The modified starting mirror image determining module is used for determining relevant configuration information for modifying the starting mirror image based on the failure reason to obtain a modified starting mirror image;
the upgrade migration module is used for carrying out upgrade migration based on the modified starting image;
The monitoring module is used for monitoring the network between the source node and the target node to be migrated when the network is determined to have a problem or based on the failure cause, and determining to utilize the starting mirror image to migrate when the current network upgradeable migration requirement is determined;
The repair duration determining module is used for determining the problem repair duration of the target node when the problem exists in the target node or based on the failure reason;
the problem solving module is used for determining to migrate after the problem is solved by the first solution when the repair time of the problem is less than the minimum time, wherein the first solution comprises at least one of restarting and software updating;
The migration plan determining module is used for determining a migration plan when the repair time of the problem is not less than the minimum time, wherein the migration plan comprises migration time, a migration file and a problem coping scheme, the migration time is determined according to the problem solving time and the system performance, the migration file is a file in the uploading migration process, and the problem coping scheme is a problem solving mode generated according to the current problem.
It should be noted that, the order of the modules and units in the upgrade migration apparatus may be changed before and after the upgrade migration apparatus does not affect the logic.
The description of the features in the embodiment corresponding to fig. 3 may be referred to the related description of the embodiment corresponding to fig. 3, which is not repeated here.
The upgrade migration device provided by the embodiment of the invention can comprise a source node to be migrated determining module 100 for installing a drive to a source node to obtain the source node to be migrated, a starting mirror image obtaining module 200 for obtaining a starting mirror image of the source node to be migrated under the condition of determining network intercommunication between the source node to be migrated and a target node, wherein information in the starting mirror image comprises 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 is information of the source node configured according to the migrated target node, the target node script is a script for configuring information of the target node, migration from the source node to the target node is cross-version migration, a data migration module 300 for utilizing the source node migration script in the starting mirror image to migrate data of basic software related to the target node, and a target node configuration module 400 for utilizing the target node script to automatically configure the source node migrated to the target node when migration is determined to be completed, so that the configured target node is migrated, and a cloud management platform is utilized for managing the target node. Compared with the prior cloud management platform which only makes migration inside the existing version, can migrate from an A node to a B node in an environment or from an openstack environment to VMware, or vice versa, but can not migrate from a low-version openstack to a new-version openstack or from a low-version VMware to a high-version VMware, the invention has the advantages that the mirror image is customized and started according to the old-version to-be-migrated node, the parameters required by the target node to be migrated are preset, then the source node migration script is executed, the mirror image is arranged to the target node according to the target node script after the execution of the migration script is waited, the migration of the new and old versions is realized, the integrity of service data is ensured, and the old version data can be continuously used.
The following describes an upgrade migration device provided by the embodiment of the present invention, and the upgrade migration device described below and the upgrade migration method described above may be referred to correspondingly.
FIG. 4 is a schematic structural diagram of an upgrade migration apparatus according to an embodiment of the present invention, and as shown in FIG. 4, the upgrade migration apparatus includes a memory 60 for storing a computer program;
a processor 61 for implementing the steps of the upgrade migration method according to the above embodiment when executing a computer program.
The upgrade migration device provided in this embodiment may include, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, or the like.
Processor 61 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 61 may be implemented in at least one hardware form of Digital Signal Processing (DSP), field-Programmable gate array (fieldprogrammable GATE ARRAY, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 61 may also include a main processor, which is a processor for processing data in a wake-up state, also referred to as a central processor (Central Processing Unit, CPU), and a coprocessor, which is a low-power processor for processing data in a standby state. In some embodiments, the processor 61 may be integrated with an image processor (Graphics Processing Unit, GPU) for rendering and rendering of content to be displayed by the display screen. In some embodiments, the processor 61 may also include an artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) processor for processing computing operations related to machine learning.
Memory 60 may include one or more computer-readable storage media, which may be non-transitory. Memory 60 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 60 is at least used for storing a computer program 601, which, when loaded and executed by the processor 61, is capable of implementing the relevant steps of the upgrade migration method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 60 may further include an operating system 602, data 603, and the like, where the storage manner may be transient storage or permanent storage. Operating system 602 may include Windows, unix, linux, among other things. Data 603 may include, but is not limited to, upgrade migration data, and the like.
In some embodiments, the upgrade migration apparatus may further comprise a display 62, an input/output interface 63, a communication interface 64, a power supply 65, and a communication bus 66.
Those skilled in the art will appreciate that the architecture shown in fig. 4 is not limiting of the upgrade migration apparatus and may include more or fewer components than shown.
It will be appreciated that if the upgrade migration method in the above embodiments is implemented in the form of a software functional unit and sold or used as a stand-alone product, it may be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in part or in whole or in part in the form of a software product stored in a storage medium for performing all or part of the steps of the method according to the embodiments of the present invention. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), an electrically erasable programmable ROM, a register, a hard disk, a removable magnetic disk, a CD-ROM, a magnetic disk, or an optical disk, etc. which can store program codes.
Based on this, the embodiment of the invention further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of the upgrade migration method as described above.
The upgrade migration equipment provided by the embodiment of the invention is described in detail above. In the description, each embodiment is described in a progressive manner, and each embodiment is mainly described by the differences from other embodiments, so that the same similar parts among the embodiments are mutually referred. 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 points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The method, the device, the equipment and the computer readable storage medium for upgrading and migration provided by the invention are described in detail. The principles and embodiments of the present invention have been described herein with reference to specific examples, the description of which is intended only to facilitate an understanding of the method of the present invention and its core ideas. It should be noted that it will be apparent to those skilled in the art that various modifications and adaptations of the invention can be made without departing from the principles of the invention and these modifications and adaptations are intended to be within the scope of the invention as defined in the following claims.
Claims (10)
1. An upgrade migration method, comprising:
Installing a drive to a source node to obtain a source node to be migrated;
Acquiring a starting mirror image of a source node to be migrated under the condition of network intercommunication between the source node to be migrated and a target node, wherein information in the starting mirror image comprises basic software of the source node, a source node migration script and a target node script, wherein the basic software is software set according to requirements, the source node migration script is information of the source node configured according to a migrated target node, and the target node script is a script configured with target node information;
migrating data of the base software related to the source node to the target node by utilizing a source node migration script in the starting mirror image;
When the migration is determined to be completed, the target node script is utilized to automatically configure a source node migrated to a target node, a configured target migration node is obtained, and the cloud management platform is utilized to manage the target migration node.
2. The upgrade migration method according to claim 1, further comprising, prior to said obtaining the boot image of the source node to be migrated:
Acquiring the operating system, memory size and disk capacity information of the source node to be migrated;
and manufacturing the starting mirror image according to the operating system, the memory size and the disk capacity information.
3. The upgrade migration method of claim 1, wherein migrating data of base software associated with the source node to the target node using a source node migration script in the boot image comprises:
determining the type of data of the basic software to obtain various types of basic software data, wherein the types comprise disk data and memory data;
And determining the priority of the various types of basic software data, and utilizing the source node migration script to migrate the data increment to the target node according to the priority.
4. The upgrade migration method according to any one of claims 1 to 3, further comprising, after obtaining a boot image of the source node to be migrated in a case where it is determined that the network interworking between the source node to be migrated and the target node is determined:
determining the type of a 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;
Modifying the configuration file according to the type of the target node to obtain a modified configuration file;
Executing the configuration script comprising the modified configuration file to obtain a modified source node migration script;
correspondingly, migrating the data of the base software related to the source node to the target node by using the source node migration script in the boot image comprises the following steps:
and migrating the data of the basic software related to the source node to the target node by utilizing the modified source node migration script.
5. The upgrade migration method of claim 1, wherein the target node script comprises network, specification, firewall, and project information.
6. The upgrade migration method according to claim 1, wherein when determining that migration is completed, automatically configuring a source node migrated to a target node by using the target node script, after obtaining a configured target migration node, further comprises:
The method comprises the steps of obtaining a script file of a cloud host, wherein the script file of the cloud host comprises an item ID, a user ID, a specification ID, a network ID and a system disk corresponding to a disk to be migrated;
Executing the script file of the cloud host, and creating a new cloud host at the configured target migration node.
7. The upgrade migration method of claim 1, the upgrade migration method is characterized by further comprising the following steps:
Acquiring an upgrade migration task state;
Judging whether the upgrade migration task is completed or not according to the upgrade migration task state;
If yes, setting the mark as finished;
otherwise, obtaining an upgrade migration task failure log;
analyzing the upgrade migration task failure log, and determining a failure reason;
Based on the failure reason, determining to modify the relevant configuration information of the starting mirror image to obtain a modified starting mirror image;
performing upgrade migration based on the modified boot image;
or monitoring the network between the source node to be migrated and the target node when the network is determined to have a problem based on the failure reason, and determining to utilize the starting mirror image to migrate when the current network upgradeable migration requirement is determined;
or when the problem of the target node is determined to exist based on the failure reason, determining the problem repairing duration of the target node;
when the repair time length of the problem is smaller than the minimum time length, determining to migrate after the problem is solved by a first solution, wherein the first solution comprises at least one of restarting and software updating;
And determining a migration plan when the repair time of the problem is not less than the minimum time, wherein the migration plan comprises migration time, a migration file and a problem solving scheme, the migration time is determined according to the problem solving time and the system performance, the migration file is a file in the uploading migration process, and the problem solving scheme is a problem solving mode generated according to the current problem.
8. An upgrade migration apparatus, comprising:
the source node to be migrated determining module is used for installing a drive to the source node to obtain the source node to be migrated;
The system comprises a starting mirror image acquisition module, a target node script, a source node migration script and a target node migration script, wherein the starting mirror image acquisition module is used for acquiring a starting mirror image of a source node to be migrated under the condition of network intercommunication between the source node to be migrated and the target node, and information in the starting mirror image comprises basic software of the source node, the source node migration script and the target node script, wherein the basic software is software set according to requirements;
The data migration module is used for migrating the data of the basic software related to the source node to the target node by utilizing the source node migration script in the starting mirror image;
And the target migration node configuration module is used for automatically configuring the source node migrated to the target node by utilizing the target node script when the migration is determined to be completed, obtaining the configured target migration node, and managing the target migration node by utilizing the cloud management platform.
9. An upgrade migration apparatus, comprising:
a memory for storing a computer program;
a processor for executing 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 has stored thereon a computer program which, when executed by a processor, implements the steps of the upgrade migration method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411368068.5A CN119088409A (en) | 2024-09-27 | 2024-09-27 | Upgrade migration method, device, equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411368068.5A CN119088409A (en) | 2024-09-27 | 2024-09-27 | Upgrade migration method, device, equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN119088409A true CN119088409A (en) | 2024-12-06 |
Family
ID=93669678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202411368068.5A Pending CN119088409A (en) | 2024-09-27 | 2024-09-27 | Upgrade migration method, device, equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN119088409A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120104289A (en) * | 2025-05-09 | 2025-06-06 | 济南浪潮数据技术有限公司 | Application migration method, device, equipment, readable storage medium and program product |
| CN120596034A (en) * | 2025-08-06 | 2025-09-05 | 融科联创(天津)信息技术有限公司 | A distributed storage system automatic expansion method, system and readable storage medium |
-
2024
- 2024-09-27 CN CN202411368068.5A patent/CN119088409A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN120104289A (en) * | 2025-05-09 | 2025-06-06 | 济南浪潮数据技术有限公司 | Application migration method, device, equipment, readable storage medium and program product |
| CN120596034A (en) * | 2025-08-06 | 2025-09-05 | 融科联创(天津)信息技术有限公司 | A distributed storage system automatic expansion method, system and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3588296A1 (en) | Dynamically scaled hyperconverged system | |
| US8589554B2 (en) | Intelligent and elastic resource pools for heterogeneous datacenter environments | |
| CN119088409A (en) | Upgrade migration method, device, equipment and computer readable storage medium | |
| EP3442203B1 (en) | Method for migrating a virtual machine, and system | |
| CN113196237A (en) | Container migration in a computing system | |
| CN104350466B (en) | Virtual machine image writes lease | |
| WO2019146763A1 (en) | Robot application management device, system, method, and program | |
| US20150372935A1 (en) | System and method for migration of active resources | |
| CN111600972B (en) | Configuration method of double-stack address, server and readable storage medium | |
| US12182602B2 (en) | Provisioning DPU management operating systems using firmware capsules | |
| CN111857951A (en) | Containerized deployment platform and deployment method | |
| CN108319492B (en) | Method, device and system for resetting a physical machine | |
| US20250358191A1 (en) | Resource Configuration Method and System, and Related Device | |
| CN114647488A (en) | Task training method, device, equipment and storage medium | |
| CN114281444A (en) | Arrangement method for implementing cloud desktop client | |
| WO2024130997A1 (en) | Node configuration method and apparatus, and device, non-volatile readable storage medium and server | |
| CN112616153B (en) | Container processing method, device, computer equipment and storage medium | |
| JP6878570B2 (en) | Methods and devices for resource reconfiguration | |
| US11295018B1 (en) | File system modification | |
| CN113127144A (en) | Processing method, processing device and storage medium | |
| JP2024524398A (en) | Method, apparatus and system for managing storage resources of a container cluster - Patents.com | |
| US11805012B2 (en) | Cloud network mechanism driver migration | |
| CN114461244B (en) | A client hardware update method for cloud desktop system | |
| CN114281442B (en) | A cloud desktop client and method thereof | |
| CN116225616A (en) | Virtual machine control method, device and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |