Cluster operating system migration method, device and equipment

Abstract

The present invention discloses a cluster operating system migration method, device and equipment, and relates to the field of server technology. The method comprises: determining and isolating target nodes from the cluster to be migrated according to the cluster business type of the cluster to be migrated; establishing a target cluster using the target nodes, and configuring a target operating system and respective target business software in each target node according to the original configuration information corresponding to each target node; isolating non-target nodes in the cluster to be migrated and adding them to the target cluster in sequence according to the minimum number of business required nodes, and configuring the target operating system and respective target business software in each non-target node; the present invention can identify and adapt to the differences between the old and new operating systems, automatically adjust the configuration to avoid conflicts, realize the synchronous upgrade of the operating system and the business software, ensure the seamless operation of the operating system after migration, and the migration process can be completed without service downtime, thereby reducing the impact on business continuity.

Description

Technical Field

[0001] The present invention relates to the technical field of servers, and in particular to a cluster operating system migration method, device and equipment. Background Art

[0002] A cluster typically refers to a group of cooperating servers that work together as a whole to provide higher performance, reliability, and scalability. Migrating the operating system within a cluster is a complex undertaking. The difficulty lies in the large number of nodes in a cluster, and different nodes often provide different service functions, which makes OS migration complex and challenging. At the same time, many users' business software has been running smoothly for years, and they hope to take this opportunity to upgrade their business software simultaneously with the operating system to meet their business functional and performance requirements. However, due to the rapid iteration of business software, many software systems have undergone software architecture reconstruction in pursuit of extreme performance and functionality. In this case, a direct upgrade cannot meet the requirements of the business software and requires redeployment, which poses even greater challenges.

[0003] In related technologies, cluster operating system migration usually adopts in-place migration technology; that is, the original operating system is migrated on the original server hardware, that is, the underlying operating system of the original business system is directly upgraded, and the business system and system configuration remain unchanged. It generally includes: migration assessment, compatibility judgment, system backup and migration implementation and other steps; it can achieve the migration of the user's original operating system to the new operating system without deleting key files such as business application data and configuration.

[0004] However, in-place migration only considers operating system migration and doesn't factor in the compatibility between the upgraded operating system and business software. Often, after an operating system upgrade, the business software on top of it can't run directly and requires a long time to adapt. In-place migration requires a server restart, which, combined with the time it takes for the software to adapt after the restart, can result in significant service downtime. Furthermore, in-place migration isn't suitable for cluster environments; it requires compatibility assessments and adaptations for each node in the cluster, a significant workload. Therefore, how to quickly and accurately complete cluster operating system migration and achieve simultaneous upgrades of the operating system and business software while minimizing disruption to business continuity is an urgent challenge. Summary of the Invention

[0005] The purpose of the present invention is to provide a cluster operating system migration method, device and equipment to quickly and accurately complete the cluster operating system migration without affecting business continuity as much as possible, and realize the synchronous upgrade of the operating system and business software.

[0006] To solve the above technical problems, the present invention provides a cluster operating system migration method, comprising:

[0007] Determine and isolate target nodes from the cluster to be migrated according to the cluster service type of the cluster to be migrated; wherein the number of the target nodes is greater than or equal to the minimum number of cluster nodes corresponding to the cluster service type;

[0008] Establish a target cluster using the target nodes, and configure a target operating system and respective target business software in each target node according to the original configuration information corresponding to each target node; wherein the original configuration information includes the system configuration information and middleware configuration information of the original operating system of an original node corresponding to each target node when it is in the cluster to be migrated;

[0009] According to the minimum number of business required nodes, the non-target nodes in the cluster to be migrated are isolated and added to the target cluster in turn, and the target operating system and the respective target business software are configured in each non-target node according to the original configuration information corresponding to each non-target node; wherein, when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of business required nodes, and the number of nodes in the target cluster is greater than or equal to the minimum number of business required nodes, the target cluster is started and the cluster to be migrated is stopped.

[0010] On the other hand, configuring the target operating system and the respective target business software in each target node according to the original configuration information corresponding to each target node includes:

[0011] Installing the target operating system in each target node and deploying respective target business software;

[0012] The original configuration information is detected from the source node corresponding to each of the target nodes, and the system configuration and middleware configuration of the target operating system in each target node are updated according to the original configuration information.

[0013] On the other hand, detecting the original configuration information from the source node corresponding to each of the target nodes and updating the system configuration and middleware configuration of the target operating system in each target node according to the original configuration information includes:

[0014] Scanning the original operating system directory of the original node corresponding to the current target node, and using the software configuration management library to detect and obtain the original middleware configuration file; wherein the current target node is any of the target nodes, the original middleware configuration file includes middleware configuration information of the original operating system of the original node corresponding to the current target node, and the software configuration management library includes middleware-related information of each preset operating system, and the middleware-related information includes the middleware name, middleware version, operating system version, and configuration file directory;

[0015] Parsing the original middleware configuration file to obtain the middleware configuration items of the original operating system of the original node corresponding to the current target node;

[0016] Mapping the middleware configuration items to the target operating system using a configuration item mapping library to obtain mapped middleware configuration items for the target operating system; wherein the configuration item mapping library includes equivalent mapping relationships between various preset middleware configuration items in different preset operating systems;

[0017] Generate a mapping middleware configuration file corresponding to the mapping middleware configuration item by using a configuration file template library; wherein the configuration file template library includes standard templates of configuration files of each middleware in different preset operating systems;

[0018] The mapping middleware configuration file is synchronized to the target operating system of the current target node.

[0019] On the other hand, detecting the original configuration information from the source node corresponding to each of the target nodes and updating the system configuration and middleware configuration of the target operating system in each target node according to the original configuration information includes:

[0020] Reading original system configuration information of the original operating system of the original node corresponding to the current target node; wherein the original system configuration information includes at least one of system user configuration, remote warehouse configuration, firewall configuration, file system configuration, network configuration, pluggable authentication module configuration file, system startup parameters, kernel parameters, and environment variables;

[0021] Comparing the original system configuration information with the default system configuration information of the target operating system in the operating system configuration library to determine the different system configuration items in the target operating system of the current target node; wherein the operating system configuration library is used to store the default system configuration information of each preset operating system;

[0022] The difference system configuration items are adjusted according to the original system configuration information.

[0023] On the other hand, installing the target operating system in each target node and deploying the respective target business software includes:

[0024] The target operating systems are batch-installed on the target nodes according to the host information of each target node; wherein the host information includes the intelligent platform management interface address, user name and password of each target node.

[0025] On the other hand, isolating non-target nodes in the cluster to be migrated and adding them to the target cluster in sequence according to the minimum number of business required nodes, and configuring the target operating system and respective target business software in each non-target node according to the original configuration information corresponding to each non-target node, includes:

[0026] Isolate the migratable nodes other than the business maintenance nodes in the cluster to be migrated in batches and add them to the target cluster, and configure the target operating system and the target business software in each migratable node according to the original configuration information corresponding to each migratable node; wherein the business maintenance nodes are non-target nodes with the minimum number of business required nodes, and the migratable nodes are non-target nodes other than the business maintenance nodes;

[0027] When the number of nodes in the target cluster is greater than or equal to the minimum number of nodes required for business, performing a synchronous business test on the target cluster to obtain a synchronous test result;

[0028] When the migration of the migratable node is completed and the synchronization test result is a test pass, starting the target cluster and stopping the cluster to be migrated;

[0029] The business maintenance nodes are added to the target cluster, and the target operating system and respective target business software are configured in each of the business maintenance nodes according to respective original configuration information corresponding to each of the business maintenance nodes.

[0030] On the other hand, before isolating non-target nodes in the cluster to be migrated and adding them to the target cluster in sequence according to the minimum number of nodes required for business, the method further includes:

[0031] The minimum number of business required nodes is determined based on the key resource information of the cluster to be migrated; wherein the key resource information includes the business usage corresponding to each key resource and the ownership of each node; the business usage includes average usage and / or peak usage.

[0032] On the other hand, determining the minimum number of nodes required for business operations based on key resource information of the cluster to be migrated includes:

[0033] According to the cluster business type of the cluster to be migrated, key resource information of the cluster to be migrated is obtained; wherein, the key resources corresponding to at least two cluster business types are different; the cluster business type includes cluster type and / or business type, the cluster type includes at least one of a load balancing cluster, a web service cluster, a database cluster, a storage cluster and a high-performance computing cluster, the business type includes at least one of input / input intensive, CPU intensive, GPU intensive, memory intensive and network intensive, and the key resources include at least one of CPU resources, memory resources, GPU resources and disk capacity resources.

[0034] The present invention also provides a cluster operating system migration device, comprising:

[0035] a node determination module, configured to determine and isolate target nodes from the cluster to be migrated based on the cluster service type of the cluster to be migrated; wherein the number of the target nodes is greater than or equal to the minimum number of cluster nodes corresponding to the cluster service type;

[0036] Establishing a migration module for establishing a target cluster using the target nodes, and configuring a target operating system and respective target business software in each target node according to the original configuration information corresponding to each target node; wherein the original configuration information includes the system configuration information and middleware configuration information of the original operating system of an original node corresponding to each target node when it is in the cluster to be migrated;

[0037] A migration switching module is used to isolate the non-target nodes in the cluster to be migrated and add them to the target cluster in sequence according to the minimum number of business requirement nodes, and configure the target operating system and the respective target business software in each non-target node according to the original configuration information corresponding to each non-target node; wherein, when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of business requirement nodes, and the number of nodes in the target cluster is greater than or equal to the minimum number of business requirement nodes, the target cluster is started and the cluster to be migrated is stopped.

[0038] In addition, the present invention also provides a cluster operating system migration device, comprising:

[0039] memory for storing computer programs;

[0040] The processor is configured to implement the steps of the cluster operating system migration method as described above when executing the computer program.

[0041] The present invention provides a cluster operating system migration method, comprising: determining and isolating target nodes from the cluster to be migrated according to the cluster business type of the cluster to be migrated; wherein the number of target nodes is greater than or equal to the minimum number of cluster nodes corresponding to the cluster business type; establishing a target cluster using the target nodes, and configuring a target operating system and respective target business software in each target node according to the original configuration information corresponding to each target node; wherein the original configuration information includes system configuration information and middleware configuration information of the original operating system when an original node corresponding to each target node is in the cluster to be migrated; isolating non-target nodes in the cluster to be migrated and adding them to the target cluster in turn according to the minimum number of business requirement nodes, and configuring the target operating system and respective target business software in each non-target node according to the original configuration information corresponding to each non-target node; wherein, when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of business requirement nodes, and the number of nodes in the target cluster is greater than or equal to the minimum number of business requirement nodes, starting the target cluster and stopping the cluster to be migrated;

[0042] It can be seen that the present invention configures the target operating system and the respective target business software in each target node according to the original configuration information corresponding to each target node, can identify and adapt to the differences between the old and new operating systems, automatically adjust the configuration to avoid conflicts, achieve synchronous upgrades of the operating system and business software, and ensure that the migrated operating system can run seamlessly; and by starting the target cluster and stopping the cluster to be migrated when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of nodes required for business, and the number of nodes in the target cluster is greater than or equal to the minimum number of nodes required for business, the migration process of the present invention can be completed without service downtime, with little impact on business continuity, thereby improving user experience. In addition, the present invention also provides a cluster operating system migration device and equipment, which also has the above-mentioned beneficial effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0044] Figure 1 A flowchart of a cluster operating system migration method provided by an embodiment of the present invention;

[0045] Figure 2 A flowchart of a node configuration migration process provided by an embodiment of the present invention;

[0046] Figure 3 A structural block diagram of a cluster operating system migration device provided by an embodiment of the present invention;

[0047] Figure 4 A simplified structural diagram of a cluster operating system migration device provided by an embodiment of the present invention;

[0048] Figure 5 This is a schematic diagram of the specific structure of a cluster operating system migration device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0049] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings 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 making creative efforts shall fall within the scope of protection of the present invention.

[0050] Please refer to Figure 1 , Figure 1 A flowchart of a cluster operating system migration method provided by an embodiment of the present invention. The method may include:

[0051] Step 101: Determine and isolate target nodes from the cluster to be migrated according to the cluster service type of the cluster to be migrated; wherein the number of target nodes is greater than or equal to the minimum number of cluster nodes corresponding to the cluster service type.

[0052] It is understandable that the cluster to be migrated in this embodiment may be a cluster that requires operating system migration, such as a cluster that requires operating system replacement or upgrade. The target node in this embodiment may be a node (such as a server) required to complete basic business deployment in the cluster to be migrated; the minimum number of cluster nodes in this embodiment may be the minimum number of nodes required to complete basic business deployment of the cluster to be migrated. In this embodiment, the processor may determine and isolate nodes (i.e., target nodes) of at least the minimum number of cluster nodes from the cluster to be migrated based on the cluster business type of the cluster to be migrated, in order to build a minimum cluster that meets business continuity.

[0053] Correspondingly, the node isolated from the cluster to be migrated in this embodiment (such as the target node) can be a node that does not affect the business processing of the cluster to be migrated. For example, the target node can be a node that does not perform business processing of the cluster to be migrated, so as to complete the isolation of the nodes in the cluster to be migrated without affecting the original business of the cluster to be migrated.

[0054] Accordingly, in this embodiment, the cluster business type of the cluster to be migrated may include cluster type and / or business type, such as the cluster type may include any one or more of a load balancing cluster, a web page (Web) service cluster, a database cluster, a storage cluster and a high-performance computing cluster; the business type may include input / output (IO) intensive, central processing unit (CPU) intensive, graphics processing unit (GPU) intensive, memory intensive and network intensive; if the cluster to be migrated is a GPU-intensive high-performance computing cluster, its cluster type is a high-performance computing cluster and its business type is GPU intensive.

[0055] Among them, the specific method for the processor to determine and isolate the target node from the cluster to be migrated according to the cluster business type of the cluster to be migrated in this step can be set by the designer according to the usage scenario and user needs. For example, the processor can determine the minimum number of cluster nodes according to the cluster business type of the cluster to be migrated; and determine and isolate the target node from the cluster to be migrated based on the minimum number of cluster nodes.

[0056] Correspondingly, the specific method for determining the minimum number of cluster nodes corresponding to the cluster to be migrated based on the cluster business type of the cluster to be migrated can be set by the designer. For example, when the preset minimum number of cluster nodes corresponding to each cluster business type is pre-set, the processor can directly match the corresponding preset minimum number of cluster nodes according to the cluster business type of the cluster to be migrated as the minimum number of cluster nodes, that is, the minimum number of cluster nodes can be less than the minimum number of business nodes required. The processor can also obtain key resource information of the cluster to be migrated based on the cluster business type of the cluster to be migrated; determine the minimum number of cluster nodes based on the key resource information of the cluster to be migrated; wherein the key resource information includes the business usage corresponding to each key resource and the ownership of each node, the business usage includes average usage and / or peak usage, the key resources corresponding to at least two cluster business types are different, and the key resources include at least one of central processing unit resources, memory resources, graphics processing unit resources and disk capacity resources; for example, the minimum number of cluster nodes can be equal to the minimum number of business nodes required, so that when the target cluster is established, its scale can meet the current business services of the cluster to be migrated.

[0057] Accordingly, for the aforementioned minimum number of cluster nodes, the specific method for determining and isolating the target nodes from the cluster to be migrated can be set by the designer. For example, the processor can directly determine and isolate the target nodes with the minimum number of cluster nodes from the cluster to be migrated, that is, the number of target nodes can be equal to the minimum number of cluster nodes. The processor can also increase the number of nodes based on the minimum number of cluster nodes to leave a certain margin. For example, the processor can determine the number of target nodes based on the minimum number of cluster nodes and the key resource information of the cluster to be migrated, and determine and isolate the target nodes from the cluster to be migrated according to this number. In other words, the processor can increase the number of nodes based on the key resource information of the cluster to be migrated, based on the matched preset minimum number of cluster nodes, to obtain the final number of target nodes.

[0058] Taking the operating system migration of a GPU-intensive high-performance computing cluster as an example, there are 103 physical servers (i.e., nodes) in the cluster to be migrated, including 2 management nodes, 1 login node, and 100 computing nodes. The computing nodes are used to provide services. Each computing node has the same configuration and provides the same GPU resources. After a period of monitoring, the key resource of the cluster is GPU resources, and the total amount of GPU resources is R total is 100, the GPU resource ownership of each server is R sig is 1. After a period of monitoring, the peak usage of GPU resources R top =40, that is, 40% of the cluster's GPU resources can meet normal business services; therefore, the preset minimum number of cluster nodes corresponding to the high-performance computing cluster is 5, that is, to build a high-performance computing cluster (i.e., the target cluster), at least 5 nodes are required: 2 management nodes, 1 login node, and 2 computing nodes (2 computing nodes are used for task scheduling testing). Since the peak usage of GPU resources is only 40%, 5 nodes can be added to isolate 10 computing nodes (i.e., target nodes) to deploy the minimum available cluster. Alternatively, you can use a*R top / R sig Calculate the minimum number of cluster nodes. Where a can be a value less than or equal to 1. For example, if a is 1, the minimum number of cluster nodes can be 40. You can directly isolate 40 nodes for target cluster deployment.

[0059] It should be noted that this embodiment does not limit the specific node types of target nodes determined and isolated from the cluster to be migrated, such as computing nodes, management nodes, and login nodes; if there are management nodes and backup management nodes in the cluster to be migrated, the target nodes determined and isolated in this step may include backup management nodes, so as to directly use the backup management nodes to implement the functions of the management nodes in the cluster to be migrated in the target cluster, so that the backup management nodes can directly use their own original configuration information to complete the configuration of the target operating system and target business software during the operating system migration process, reduce the node type conversion process, and improve the migration speed; when there is a management node in the cluster to be migrated and there is no backup management node, the target nodes determined and isolated in this step may include the computing nodes corresponding to the management nodes, so as to use the computing nodes to implement the functions of the management nodes in the cluster to be migrated in the target cluster.

[0060] Step 102: Use the target nodes to establish a target cluster, and configure the target operating system and the respective target business software in each target node according to the original configuration information corresponding to each target node; wherein the original configuration information includes the system configuration information and middleware configuration information of the original operating system when an original node corresponding to each target node is in the cluster to be migrated.

[0061] It can be understood that the target operating system in this embodiment can be the operating system (i.e., the new operating system) to which each node in the cluster to be migrated needs to be migrated and updated; the target business software can be the new business software under the target operating system, and the target business software in each target node can include the business software corresponding to the original business software in the corresponding original node, such as the business software after the version upgrade of the original business software under the target operating system.

[0062] Correspondingly, in this embodiment, the original node corresponding to each target node can be a node in the cluster to be migrated and upgraded. For example, if the target node is a backup management node, the original node corresponding to the target node can be itself. If there is a management node but no backup management node in the cluster to be migrated, and a target node is a compute node, the original node corresponding to the target node can be itself or the management node. Taking the aforementioned cluster to be migrated with 103 servers (i.e., original nodes) as an example, if the target nodes are 10 compute nodes, the original nodes corresponding to two compute nodes can be the two management nodes in the cluster to be migrated, the original node corresponding to one compute node can be a login node, and the original nodes corresponding to the remaining seven compute nodes can be themselves.

[0063] It should be noted that, in this embodiment, by detecting and identifying the middleware configuration information in the original configuration information corresponding to each target node, it is possible to identify and adapt to the differences between the old and new operating systems, automatically adjust the configuration to avoid conflicts between the migrated operating system and the business software, and ensure that the migrated system can run seamlessly.

[0064] Correspondingly, in this step, the processor uses the target node to establish a target cluster, and according to the original configuration information corresponding to each target node, the specific method of configuring the target operating system and the respective target business software in each target node can be set by the designer. For example, the processor can install the target operating system in each target node and deploy the respective target business software; detect the original configuration information from the original node corresponding to each target node, and update the system configuration and middleware configuration of the target operating system in each target node according to the original configuration information.

[0065] Accordingly, the specific method of installing the target operating system in each target node and deploying the respective target business software can be set by the designer. For example, the processor can be Figure 2 As shown in step 201, a target operating system is installed on each target node according to the host information of each target node; wherein the host information includes an Intelligent Platform Management Interface (IPMI) address, a user name, and a password of each target node; for example, the processor may call an operating system installation file and an operating system installation configuration file corresponding to the target operating system information according to the acquired target operating system information and the host information of each target node, and install the target operating system on each target node according to the target operating system; wherein the target operating system information may include a version of the target operating system, the operating system installation file may include an image file for booting the installed operating system, and the operating system installation configuration file may include common configurations during operating system installation, such as installed software packages, operating system installation method, installation language, and network configuration.

[0066] To improve the efficiency of target operating system installation, in some embodiments, the processor can batch install the target operating system on the target nodes based on the host information of each target node. For example, the processor can import the operating system installation file and operating system installation configuration file corresponding to the target operating system information to each target node based on the host information of each target node, and use the PXE (Preboot eXecution Environment, a standard protocol for network booting computers) protocol or the IPXE (a standard protocol for network booting computers) protocol to batch install the target operating system on each target node.

[0067] Correspondingly, after the target operating system in each target node is installed, the processor can also deploy corresponding business software (ie, target business software) under the target operating system of each target node according to the business software information of the original node corresponding to each target node.

[0068] It should be noted that the above process of detecting the original configuration information from the source node corresponding to each target node and updating the system configuration and middleware configuration of the target operating system in each target node according to the original configuration information may include the synchronization process of the middleware configuration and the synchronization process of the system configuration. The synchronization process of the middleware configuration may be as follows: Figure 2 As shown in steps 202 to 205, the process includes: scanning the original operating system directory of the original node corresponding to the current target node, detecting and obtaining the original middleware configuration file using the software configuration management library; parsing the original middleware configuration file to obtain the middleware configuration items of the original operating system of the original node corresponding to the current target node; using the configuration item mapping library to map the middleware configuration items to the target operating system to obtain the mapped middleware configuration items of the target operating system; and using the configuration file template library to generate a mapped middleware configuration file corresponding to the mapped middleware configuration item. The current target node is any target node, the original middleware configuration file includes the middleware configuration information of the original operating system of the original node corresponding to the current target node, the software configuration management library includes the middleware related information of each preset operating system, and the middleware related information includes the middleware name, middleware version, operating system version, and configuration file directory; the configuration item mapping library includes the equivalent mapping relationship of each preset middleware configuration item in different preset operating systems; and the configuration file template library includes the standard templates of each middleware configuration file in different preset operating systems.

[0069] That is, even if the original operating system and the target operating system belong to the same operating system category, such as the Linux operating system, there are still differences between different versions of the operating system. Therefore, this embodiment can automatically detect the middleware present in the original operating system, extract its configuration files, and automatically convert the relevant original operating system middleware configuration files into the relevant configuration of the target operating system according to relevant rules. The software configuration management library includes middleware-related information for each preset operating system, such as the middleware name, middleware version, operating system version, and configuration file directory, so as to identify and export the original operating system's middleware configuration files (i.e., original middleware configuration files) from the original operating system directory. For example, based on the original operating system's middleware-related information in the software configuration management library, the original operating system directory is scanned based on the directory path information of the original operating system version to identify installed middleware. For each identified middleware, its configuration file is exported. The configuration item mapping library can include equivalent mapping relationships between commonly used middleware configuration items (i.e., preset middleware configuration items) in different operating systems, used to map the original operating system's configuration items to equivalent configuration items (i.e., mapped middleware configuration items) in the target operating system. The configuration file template library may include standard templates for each middleware configuration file in different operating systems, which are used to regenerate the middleware configuration file for the target operating system (i.e., the mapped middleware configuration file) from the mapped configuration items (i.e., the mapped middleware configuration items). The preset operating system may include the original operating system and the target operating system.

[0070] Accordingly, the specific method for parsing the original middleware configuration file to obtain the middleware configuration items of the original operating system of the original node corresponding to the current target node can be set by the designer. For example, the processor can parse the original middleware configuration file into structured data, such as JSON (a text data exchange format) format data, to obtain the middleware configuration items of the original operating system of the original node corresponding to the current target node, so that the configuration item mapping library can be used to map to the corresponding configuration items of the target operating system. Then, the standard templates and corresponding configuration items in the configuration file template library are used to generate the corresponding configuration file of the target operating system. For example, when the original middleware configuration file includes an nginx (an open source web server) configuration file, the configuration file can be parsed into the following JSON format data:

[0071] {

[0072] "middleware": [

[0073] {

[0074] "name": "Nginx",

[0075] "versions": ["1.18.0"],

[0076] "configFiles": [

[0077] {

[0078] "path": " / etc / nginx / nginx.conf",

[0079] "parameters": {

[0080] "server": [

[0081] { "listen": 80,

[0082] "server_name": 192.168.122.45,

[0083] "root": / usr / share / nginx / html,

[0084] "location":[

[0085] { "path": / mnt / test,

[0086] "alias": / data,

[0087] "autoindex": on,

[0088] "charset": utf-8

[0089] } ]

[0091] } ]

[0093] }

[0094] }, ]

[0096] } ]

[0098] }

[0099] Correspondingly, the synchronization process of the above system configuration can be as follows Figure 2As shown in steps 206 to 208, the process includes: reading original system configuration information of the original operating system of the original node corresponding to the current target node; comparing the original system configuration information with the default system configuration information of the target operating system in the operating system configuration library to determine the difference system configuration items in the target operating system of the current target node; and adjusting the difference system configuration items based on the original system configuration information. The original system configuration information includes at least one of system user configuration, remote repository configuration, firewall configuration, file system configuration, network configuration, pluggable authentication module configuration file, system startup parameters, kernel parameters, and environment variables; and the operating system configuration library is used to store the default system configuration information of each preset operating system.

[0100] In other words, the operating system configuration library can include the default system configuration information (i.e., default system configuration items) for each pre-set operating system, facilitating comparison with the original operating system. In this embodiment, the specific contents of the operating system configuration library, the software configuration management library, the configuration item mapping library, and the configuration file template library can be customized by the designer or user. As more operating systems are migrated, the four configuration management libraries will cover an increasing number of software configurations, gradually enhancing the intelligence of operating system migration.

[0101] Furthermore, the method provided in this embodiment may also include the steps of detecting error information during the system configuration synchronization process; and generating and outputting an error report based on the error information. During the middleware configuration synchronization process, since the middleware configuration files have been pre-configured in the configuration management repository, problems are generally unlikely to occur. However, during the system configuration synchronization process, errors may occur, such as errors in executing command setting parameters or the non-existence of the configuration synchronization path. Therefore, the above-mentioned error information detection and report generation process allows users to promptly understand and address these errors.

[0102] The configuration parsing process during system configuration synchronization differs from the middleware configuration synchronization process. The collected and read system configuration information of the original operating system (i.e., the original system configuration information) can be compared with the default system configuration information of the target operating system in the operating system configuration library. Only those system configuration items with differences (i.e., differential system configuration items) are adjusted. For example, the configuration files corresponding to the differential system configuration items in the original operating system can be directly overwritten with the configuration files corresponding to the differential system configuration items in the target operating system. For example, the processor can compare the original system configuration information with the default system configuration information of the target operating system in the operating system configuration library to obtain a list of differences; the differential system configuration items in the list of differences can then be adjusted based on the original system configuration information.

[0103] Correspondingly, Figure 2The synchronization process of the system configuration in FIG is demonstrated by taking the comparison synchronization of the system configuration as an example, and the original system configuration information of the original operating system can also be directly used to adjust all the system configuration items of the target operating system. This embodiment does not impose any limitation on this.

[0104] Step 103: Based on the minimum number of business required nodes, the non-target nodes in the cluster to be migrated are isolated and added to the target cluster in turn, and the target operating system and the respective target business software are configured in each non-target node based on the original configuration information corresponding to each non-target node; wherein, when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of business required nodes, and the number of nodes in the target cluster is greater than or equal to the minimum number of business required nodes, the target cluster is started and the cluster to be migrated is stopped.

[0105] It should be noted that the minimum number of business requirement nodes in this embodiment can be the minimum number of nodes required to meet the normal business services of the cluster to be migrated, so that when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of business requirement nodes, and the number of nodes in the target cluster is greater than or equal to the minimum number of business requirement nodes, the business service is switched to the target cluster to avoid the situation where the business service cannot operate normally after the switch. That is to say, in this step, the processor will switch the cluster that performs business services from the cluster to be migrated to the target cluster in the process of adding all non-target nodes to the target cluster in sequence, so as to reduce the impact on business continuity; for example, the processor can start the target cluster and stop the cluster to be migrated when the number of nodes in the cluster to be migrated is equal to the minimum number of business requirement nodes; or it can directly start the target cluster and stop the cluster to be migrated when the number of nodes in the target cluster is equal to the minimum number of business requirement nodes.

[0106] Correspondingly, the specific value and acquisition method for the minimum number of business-required nodes in this embodiment can be set by the designer based on practical scenarios and user needs. For example, the processor can determine the minimum number of business-required nodes based on the cluster size of the cluster to be migrated; for example, the larger the cluster size (such as the number of nodes), the larger the minimum number of business-required nodes. To ensure the accuracy of the minimum number of business-required nodes, the processor can also determine the minimum number of business-required nodes based on the key resource information of the cluster to be migrated; wherein the key resource information includes the business usage corresponding to each key resource and the ownership of each node; the business usage includes average usage and / or peak usage; and the key resources include at least one of central processing unit resources, memory resources, graphics processing unit resources, and disk capacity resources.

[0107] For example, suppose the total amount of a key resource used by the cluster to be migrated is R total And the amount of resource each node owns R sig, monitor and record the key resources in the cluster to be migrated within a preset time (such as a week). For example, continuous monitoring can be used to obtain the resource change curve over a period of time, or several time periods can be selected for monitoring every day (such as morning, afternoon, evening, and early morning, etc.), and finally the average usage R of the key resource within the preset time period can be obtained. avg and peak usage R top ;By b*R avg / R sig and / or b*R top / R sig , determine the minimum number of nodes required for business, so as to obtain the minimum cluster size that meets business continuity; wherein, b can be a value greater than or equal to 1, such as b can be greater than 1 to leave a certain margin. For example, the peak usage R top When the number of occurrences is small (such as less than the number threshold), b*R avg / R sig , determine the minimum number of nodes required for business; conversely, you can use b*R top / R sig , determine the minimum number of nodes required for business.

[0108] Furthermore, in some embodiments, the correspondence between each cluster business type and key resources can be pre-set to obtain key resource information of the cluster to be migrated based on the cluster business type of the cluster to be migrated, thereby further improving the accuracy of the minimum number of business required nodes; wherein, the key resources corresponding to at least two cluster business types are different; the cluster business type includes cluster type and / or business type, the cluster type includes at least one of a load balancing cluster, a web service cluster, a database cluster, a storage cluster and a high-performance computing cluster, the business type includes at least one of input / input intensive, CPU intensive, GPU intensive, memory intensive and network intensive, and the key resources include at least one of CPU resources, memory resources, GPU resources and disk capacity resources.

[0109] It should be noted that in this step, the non-target nodes in the cluster to be migrated are isolated and added to the target cluster in turn according to the minimum number of nodes required for business operations, and the specific method of configuring the target operating system and the respective target business software in each non-target node according to the original configuration information corresponding to each non-target node can be set by the designer. For example, the processor can perform a synchronous business test on the target cluster before switching the target cluster to provide business services to ensure that the target cluster can provide business services normally and ensure business continuity; and the non-target nodes in the cluster to be migrated can be added to the target cluster in batches to facilitate the observation of the stability of the target cluster. For example, after the target cluster is created, you can perform synchronous business testing on the target cluster, and at the same time, isolate the nodes in the cluster to be migrated (i.e., non-target nodes) in batches and gradually add them to the target cluster. For example, the nodes outside the minimum number of business requirement nodes in the cluster to be migrated (i.e., migratable nodes) are added to the new cluster in batches to facilitate observation of the stability of the new cluster. The nodes can be divided into two or three batches according to the number of migratable nodes, etc., until all nodes outside the minimum number of business requirement nodes are added to the target cluster. At this time, the business will not be affected. When the target cluster is fully tested, you can find a time window, stop the cluster to be migrated, start the target cluster, and then add the remaining nodes in the cluster to be migrated (i.e., business maintenance nodes) to the new cluster environment until all nodes in the cluster to be migrated are migrated.

[0110] For example, in this step, the processor can isolate the migratable nodes other than the business maintenance nodes in the cluster to be migrated in batches and add them to the target cluster, and configure the target operating system and the respective target business software in each migratable node according to the original configuration information corresponding to each migratable node; when the number in the target cluster is greater than or equal to the minimum business requirement node number, perform a synchronous business test on the target cluster to obtain the synchronization test result; when the migration of the migratable nodes is completed and the synchronization test result is a passed test, start the target cluster and stop the cluster to be migrated; add the business maintenance nodes to the target cluster, and configure the target operating system and the respective target business software in each business maintenance node according to the original configuration information corresponding to each business maintenance node; wherein, the business maintenance nodes are non-target nodes with the minimum business requirement node number, and the migratable nodes are non-target nodes other than the business maintenance nodes.

[0111] It should be noted that the specific process of configuring the target operating system and the respective target business software in each non-target node in this step based on the original configuration information corresponding to each non-target node can be implemented in the same or similar manner as the process of configuring the target operating system and the respective target business software in each target node in step 102, and will not be repeated here.

[0112] Correspondingly, in this embodiment, the original nodes in the cluster to be migrated corresponding to all target nodes and non-target nodes can be all nodes in the cluster to be migrated before migration. Taking the aforementioned cluster to be migrated with 103 servers (i.e., original nodes) as an example, if the target nodes are 10 compute nodes, the original nodes corresponding to two compute nodes can be the two management nodes in the cluster to be migrated, the original node corresponding to one compute node can be the login node, and the original nodes corresponding to the remaining seven compute nodes can be themselves. Of the 93 non-target nodes, the original nodes corresponding to 90 compute nodes can be themselves, and the original nodes corresponding to the two management nodes and the login node can be the three compute nodes that previously served as management nodes and login nodes. The original nodes in the cluster to be migrated corresponding to all target nodes and non-target nodes can also be some of the nodes in the cluster to be migrated before migration. For example, the original nodes corresponding to the aforementioned 93 non-target nodes can be themselves. After all nodes in the cluster to be migrated are migrated, the three compute nodes that previously served as management nodes and login nodes can reconfigure the target operating system and their respective target business software based on the system configuration information and middleware configuration information of their original operating systems when they were in the cluster to be migrated, thereby restoring their node types. This embodiment does not impose any restrictions on this.

[0113] In this embodiment, the embodiment of the present invention configures the target operating system and the respective target business software in each target node according to the original configuration information corresponding to each target node, can identify and adapt to the differences between the old and new operating systems, automatically adjust the configuration to avoid conflicts, achieve synchronous upgrades of the operating system and business software, and ensure that the migrated operating system can run seamlessly; and by starting the target cluster and stopping the cluster to be migrated when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of nodes required for business, and the number of nodes in the target cluster is greater than or equal to the minimum number of nodes required for business, the migration process of the present invention can be completed without service downtime, with little impact on business continuity, thereby improving user experience.

[0114] Corresponding to the above method embodiment, an embodiment of the present invention further provides a cluster operating system migration device. The cluster operating system migration device described below and the cluster operating system migration method described above can refer to each other.

[0115] Please refer to Figure 3 , Figure 3 This is a block diagram of a cluster operating system migration device provided by an embodiment of the present invention. The device may include:

[0116] A node determination module 10 is configured to determine and isolate target nodes from the cluster to be migrated based on the cluster service type of the cluster to be migrated; wherein the number of target nodes is greater than or equal to the minimum number of cluster nodes corresponding to the cluster service type;

[0117] Establishing a migration module 20 for establishing a target cluster using the target nodes and configuring a target operating system and respective target business software in each target node based on the original configuration information corresponding to each target node; wherein the original configuration information includes the system configuration information and middleware configuration information of the original operating system of an original node corresponding to each target node when it is in the cluster to be migrated;

[0118] The migration switching module 30 is used to isolate the non-target nodes in the cluster to be migrated and add them to the target cluster in sequence according to the minimum number of business required nodes, and configure the target operating system and the respective target business software in each non-target node according to the original configuration information corresponding to each non-target node; wherein, when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of business required nodes, and the number of nodes in the target cluster is greater than or equal to the minimum number of business required nodes, the target cluster is started and the cluster to be migrated is stopped.

[0119] In another aspect, establishing the migration module 20 may include:

[0120] The installation and deployment submodule is used to install the target operating system in each target node and deploy the respective target business software;

[0121] The configuration update submodule is used to detect original configuration information from the source node corresponding to each target node, and update the system configuration and middleware configuration of the target operating system in each target node according to the original configuration information.

[0122] In another aspect, the configuration update submodule may include:

[0123] a scanning unit, configured to scan an original operating system directory of an original node corresponding to a current target node, and detect and obtain an original middleware configuration file using a software configuration management library; wherein the current target node is any target node, the original middleware configuration file includes middleware configuration information of the original operating system of the original node corresponding to the current target node, and the software configuration management library includes middleware-related information of each preset operating system, wherein the middleware-related information includes a middleware name, a middleware version, an operating system version, and a configuration file directory;

[0124] A parsing unit, configured to parse the original middleware configuration file and obtain the middleware configuration items of the original operating system of the original node corresponding to the current target node;

[0125] A mapping unit, configured to map the middleware configuration items to the target operating system using a configuration item mapping library to obtain mapped middleware configuration items of the target operating system; wherein the configuration item mapping library includes equivalent mapping relationships between various preset middleware configuration items in different preset operating systems;

[0126] A generating unit, configured to generate a mapping middleware configuration file corresponding to a mapping middleware configuration item by using a configuration file template library; wherein the configuration file template library includes standard templates of configuration files of various middlewares in different preset operating systems;

[0127] The synchronization unit is used to synchronize the mapping middleware configuration file to the target operating system of the current target node.

[0128] In another aspect, the configuration update submodule may include:

[0129] a reading unit, configured to read original system configuration information of an original operating system of an original node corresponding to the current target node; wherein the original system configuration information includes at least one of system user configuration, remote repository configuration, firewall configuration, file system configuration, network configuration, pluggable authentication module configuration file, system startup parameters, kernel parameters, and environment variables;

[0130] a comparison unit, configured to compare the original system configuration information with the default system configuration information of the target operating system in the operating system configuration library, and determine the different system configuration items in the target operating system of the current target node; wherein the operating system configuration library is used to store the default system configuration information of each preset operating system;

[0131] The adjustment unit is used to adjust the different system configuration items according to the original system configuration information.

[0132] In another aspect, installing the deployment submodule may include:

[0133] The batch installation unit is used to batch install the target operating system on the target nodes according to the host information of each target node; wherein the host information includes the intelligent platform management interface address, user name and password of each target node.

[0134] In another aspect, the migration switching module 30 may include:

[0135] The batch migration submodule is used to isolate the migratable nodes other than the business maintenance nodes in the cluster to be migrated in batches and add them to the target cluster. It also configures the target operating system and the target business software in each migratable node based on the original configuration information corresponding to each migratable node. The business maintenance nodes are non-target nodes with the minimum number of business required nodes, and the migratable nodes are non-target nodes other than the business maintenance nodes.

[0136] The test submodule is used to perform a synchronization service test on the target cluster when the number of nodes in the target cluster is greater than or equal to the minimum number of nodes required for the service, and obtain a synchronization test result;

[0137] The switching submodule is used to start the target cluster and stop the cluster to be migrated when the migration of the migratable node is completed and the synchronization test result is passed;

[0138] The remaining migration submodule is used to add the business maintenance nodes to the target cluster and configure the target operating system and the respective target business software in each business maintenance node according to the original configuration information corresponding to each business maintenance node.

[0139] In another aspect, the apparatus further comprises:

[0140] The quantity determination module is used to determine the minimum number of business required nodes based on the key resource information of the cluster to be migrated; wherein the key resource information includes the business usage corresponding to each key resource and the ownership of each node; the business usage includes average usage and / or peak usage.

[0141] In another aspect, the quantity determination module may include:

[0142] The resource acquisition submodule is used to obtain key resource information of the cluster to be migrated according to the cluster business type of the cluster to be migrated; wherein, the key resources corresponding to at least two cluster business types are different; the cluster business type includes cluster type and / or business type, the cluster type includes at least one of load balancing cluster, web service cluster, database cluster, storage cluster and high-performance computing cluster, the business type includes at least one of input / input intensive, CPU intensive, GPU intensive, memory intensive and network intensive, and the key resources include at least one of CPU resources, memory resources, GPU resources and disk capacity resources.

[0143] In this embodiment, the embodiment of the present invention establishes a migration module 20 to configure the target operating system and the respective target business software in each target node according to the original configuration information corresponding to each target node. It can identify and adapt to the differences between the old and new operating systems, automatically adjust the configuration to avoid conflicts, and achieve synchronous upgrades of the operating system and business software, ensuring that the migrated operating system can run seamlessly; and by starting the target cluster and stopping the cluster to be migrated when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of nodes required for business, and the number of nodes in the target cluster is greater than or equal to the minimum number of nodes required for business, the migration process of the present invention can be completed without service downtime, with little impact on business continuity, thereby improving user experience.

[0144] Corresponding to the above method embodiment, an embodiment of the present invention further provides a cluster operating system migration device. The cluster operating system migration device described below and the cluster operating system migration method described above can refer to each other.

[0145] Please refer to Figure 4 , Figure 4 A simplified structural diagram of a cluster operating system migration device provided by an embodiment of the present invention. The device may include:

[0146] Memory D1, for storing computer programs;

[0147] The processor D2 is configured to implement the steps of the cluster operating system migration method provided in the above method embodiment when executing a computer program.

[0148] Please refer to Figure 5 , Figure 5 This is a schematic diagram of the specific structure of a cluster operating system migration device provided in an embodiment of the present invention. The operating system migration device 310 may vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 322 (e.g., one or more processors), memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) storing application programs 342 or data 344. The memory 332 and storage media 330 may be either transient or persistent storage. The program stored in the storage medium 330 may include one or more units (not shown), each of which may include a series of instruction operations on the host. Furthermore, the central processing unit 322 may be configured to communicate with the storage medium 330, executing the series of instruction operations stored in the storage medium 330 on the operating system migration device 310.

[0149] The operating system migration device 310 may further include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input and output interfaces 358, and / or one or more operating systems 341, such as Linux system.

[0150] The data storage device 310 in this embodiment may be a node in the cluster to be migrated, such as a server; or may be an electronic device outside the cluster to be migrated, such as a computer or a server.

[0151] The steps in the cluster operating system migration method described above can be implemented by the structure of the cluster operating system migration device.

[0152] Corresponding to the above method embodiment, an embodiment of the present invention further provides a computer-readable storage medium. The computer-readable storage medium described below and the cluster operating system migration method described above can refer to each other.

[0153] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the cluster operating system migration method of the above method embodiment.

[0154] The computer-readable storage medium may be a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, which may store program codes.

[0155] Corresponding to the above method embodiment, an embodiment of the present invention further provides a computer program product. The computer program product described below and the cluster operating system migration method described above can refer to each other.

[0156] A computer program product includes a computer program / instruction, which, when executed by a processor, implements the steps of the cluster operating system migration method provided by the above method embodiment.

[0157] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. References to the common and similar parts between the various embodiments are sufficient. The devices, apparatuses, computer program products, and computer-readable storage media disclosed in the embodiments are described briefly because they correspond to the methods disclosed in the embodiments. For relevant details, refer to the description of the methods.

[0158] The above is a detailed introduction to the cluster operating system migration method, device, and equipment provided by the present invention. This article uses specific examples to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only intended to help understand the method and core concept of the present invention. 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 present invention.

Claims

1. A cluster operating system migration method, characterized in that: include: Determine and isolate target nodes from the cluster to be migrated according to the cluster service type of the cluster to be migrated; wherein the number of the target nodes is greater than or equal to the minimum number of cluster nodes corresponding to the cluster service type; Establish a target cluster using the target nodes, and configure a target operating system and respective target business software in each target node according to the original configuration information corresponding to each target node; wherein the original configuration information includes the system configuration information and middleware configuration information of the original operating system of an original node corresponding to each target node when it is in the cluster to be migrated; According to the minimum number of business required nodes, the non-target nodes in the cluster to be migrated are isolated and added to the target cluster in turn, and the target operating system and the respective target business software are configured in each non-target node according to the original configuration information corresponding to each non-target node; wherein, when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of business required nodes, and the number of nodes in the target cluster is greater than or equal to the minimum number of business required nodes, the target cluster is started and the cluster to be migrated is stopped.

2. The cluster operating system migration method according to claim 1, characterized in that: The configuring the target operating system and the target business software in each target node according to the original configuration information corresponding to each target node includes: Installing the target operating system in each target node and deploying respective target business software; The original configuration information is detected from the source node corresponding to each of the target nodes, and the system configuration and middleware configuration of the target operating system in each target node are updated according to the original configuration information.

3. The cluster operating system migration method according to claim 2, characterized in that: The detecting the original configuration information from the source node corresponding to each of the target nodes and updating the system configuration and middleware configuration of the target operating system in each target node according to the original configuration information includes: Scanning the original operating system directory of the original node corresponding to the current target node, and using the software configuration management library to detect and obtain the original middleware configuration file; wherein the current target node is any of the target nodes, the original middleware configuration file includes middleware configuration information of the original operating system of the original node corresponding to the current target node, and the software configuration management library includes middleware-related information of each preset operating system, and the middleware-related information includes the middleware name, middleware version, operating system version, and configuration file directory; Parsing the original middleware configuration file to obtain the middleware configuration items of the original operating system of the original node corresponding to the current target node; Mapping the middleware configuration items to the target operating system using a configuration item mapping library to obtain mapped middleware configuration items for the target operating system; wherein the configuration item mapping library includes equivalent mapping relationships between various preset middleware configuration items in different preset operating systems; Generate a mapping middleware configuration file corresponding to the mapping middleware configuration item by using a configuration file template library; wherein the configuration file template library includes standard templates of configuration files of each middleware in different preset operating systems; The mapping middleware configuration file is synchronized to the target operating system of the current target node.

4. The cluster operating system migration method according to claim 2, characterized in that: The detecting the original configuration information from the source node corresponding to each of the target nodes and updating the system configuration and middleware configuration of the target operating system in each target node according to the original configuration information includes: Reading original system configuration information of the original operating system of the original node corresponding to the current target node; wherein the original system configuration information includes at least one of system user configuration, remote warehouse configuration, firewall configuration, file system configuration, network configuration, pluggable authentication module configuration file, system startup parameters, kernel parameters, and environment variables; Comparing the original system configuration information with the default system configuration information of the target operating system in the operating system configuration library to determine the different system configuration items in the target operating system of the current target node; wherein the operating system configuration library is used to store the default system configuration information of each preset operating system; The difference system configuration items are adjusted according to the original system configuration information.

5. The cluster operating system migration method according to claim 2, characterized in that: The step of installing the target operating system in each target node and deploying respective target business software includes: The target operating systems are batch-installed on the target nodes according to the host information of each target node; wherein the host information includes the intelligent platform management interface address, user name and password of each target node.

6. The cluster operating system migration method according to claim 1, characterized in that: The step of isolating the non-target nodes in the cluster to be migrated and adding them to the target cluster in sequence according to the minimum number of nodes required for business operations, and configuring the target operating system and the target business software in each non-target node according to the original configuration information corresponding to each non-target node, includes: Isolate the migratable nodes other than the business maintenance nodes in the cluster to be migrated in batches and add them to the target cluster, and configure the target operating system and the target business software in each migratable node according to the original configuration information corresponding to each migratable node; wherein the business maintenance nodes are non-target nodes with the minimum number of business required nodes, and the migratable nodes are non-target nodes other than the business maintenance nodes; When the number of nodes in the target cluster is greater than or equal to the minimum number of nodes required for business, performing a synchronous business test on the target cluster to obtain a synchronous test result; When the migration of the migratable node is completed and the synchronization test result is a test pass, starting the target cluster and stopping the cluster to be migrated; The business maintenance nodes are added to the target cluster, and the target operating system and respective target business software are configured in each of the business maintenance nodes according to respective original configuration information corresponding to each of the business maintenance nodes.

7. The cluster operating system migration method according to any one of claims 1 to 6, characterized in that: Before isolating non-target nodes in the cluster to be migrated and adding them to the target cluster in sequence according to the minimum number of nodes required by the business, the method further includes: The minimum number of business required nodes is determined based on the key resource information of the cluster to be migrated; wherein the key resource information includes the business usage corresponding to each key resource and the ownership of each node; the business usage includes average usage and / or peak usage.

8. The cluster operating system migration method according to claim 7, characterized in that: The determining, based on the key resource information of the cluster to be migrated, the minimum number of nodes required for the business, includes: According to the cluster business type of the cluster to be migrated, key resource information of the cluster to be migrated is obtained; wherein, the key resources corresponding to at least two cluster business types are different; the cluster business type includes cluster type and / or business type, the cluster type includes at least one of a load balancing cluster, a web service cluster, a database cluster, a storage cluster and a high-performance computing cluster, the business type includes at least one of input / input intensive, CPU intensive, GPU intensive, memory intensive and network intensive, and the key resources include at least one of CPU resources, memory resources, GPU resources and disk capacity resources.

9. A cluster operating system migration device, characterized in that: include: a node determination module, configured to determine and isolate target nodes from the cluster to be migrated based on the cluster service type of the cluster to be migrated; wherein the number of the target nodes is greater than or equal to the minimum number of cluster nodes corresponding to the cluster service type; Establishing a migration module for establishing a target cluster using the target nodes, and configuring a target operating system and respective target business software in each target node according to the original configuration information corresponding to each target node; wherein the original configuration information includes the system configuration information and middleware configuration information of the original operating system of an original node corresponding to each target node when it is in the cluster to be migrated; A migration switching module is used to isolate the non-target nodes in the cluster to be migrated and add them to the target cluster in sequence according to the minimum number of business requirement nodes, and configure the target operating system and the respective target business software in each non-target node according to the original configuration information corresponding to each non-target node; wherein, when the number of nodes in the cluster to be migrated is greater than or equal to the minimum number of business requirement nodes, and the number of nodes in the target cluster is greater than or equal to the minimum number of business requirement nodes, the target cluster is started and the cluster to be migrated is stopped.

10. A cluster operating system migration device, characterized in that: include: memory for storing computer programs; A processor is configured to implement the steps of the cluster operating system migration method according to any one of claims 1 to 7 when executing the computer program.

Images