Migration evaluation method and system for improving system migration reliability

Abstract

The invention discloses a migration evaluation method and system for improving system migration reliability. The method comprises the following steps: calling an information collection plug-in to collect system information of a target system; calling an abnormal scene preprocessing plug-in to preprocess the target system; calling an abnormal scene checking plug-in to carry out abnormal scene checking on the target system; giving a migration evaluation result about whether system migration is suggested or not according to a check result of the preprocessed abnormal scene check; and generating a migration evaluation report according to the system information of the target system and the migration evaluation result. According to the method, the functions of the migration evaluation tool are continuously expanded through the expanded abnormal scene preprocessing plug-in and the abnormal scene checking plug-in, different business scenes of different enterprises are adapted, the migration evaluation reliability and safety are improved, and stability and high efficiency of the whole system migration process are guaranteed.

Description

Technical Field

[0001] The present invention relates to the technical field of system migration, and in particular to a migration evaluation method and system for improving the reliability of system migration. Background Art

[0002] Since the CentOS operating system is discontinued, it is necessary to help users achieve system migration from CentOS series products to seamlessly switch to other operating systems. System migration involves migrating the existing system architecture, data and business logic from one platform to another. Various abnormal scenarios are often encountered during the system migration process, which may cause migration failure or unstable system operation after migration. Therefore, before system migration, it is necessary to conduct a migration assessment on the migrated system to determine whether migration can be performed. However, the use scenarios of the CentOS system are very extensive and complex. Different enterprises have different business scenarios, so the dimensions of migration analysis and evaluation of the migrated system may be different. In addition, it is impossible to exhaustively enumerate the possible abnormal migration scenarios. Different businesses have different abnormal scenarios, and the existing migration assessment technology only provides common system assessment items. When encountering abnormal scenarios that cannot be identified by the migration assessment, the function of the migration assessment tool cannot be dynamically expanded. When encountering unsupported problems, new migration tools need to be developed or manual assessments need to be performed, which is extremely inefficient. When the migration assessment result is not passed, it is usually necessary to manually process the migrated system manually, and then use the migration assessment tool to perform migration assessment. Manual processing is prone to errors, and the processing efficiency is low when dealing with thousands of devices. Summary of the invention

[0003] Technical problem to be solved by the present invention: In view of the above-mentioned problems in the prior art, a method and system for migration evaluation that improves the reliability of system migration are provided. The present invention aims to continuously expand the functions of the migration evaluation tool through an extended abnormal scenario preprocessing plug-in and an abnormal scenario checking plug-in, adapt to different business scenarios of different enterprises, improve the reliability and security of migration evaluation, and ensure the stability and efficiency of the entire system migration process.

[0004] In order to solve the above technical problems, the technical solution adopted by the present invention is: A migration assessment method for improving system migration reliability comprises the following steps: Call the information collection plug-in to collect system information of the target system; Call the abnormal scenario preprocessing plug-in to preprocess the target system; Call the abnormal scenario check plug-in to perform abnormal scenario check on the target system; Provide a migration assessment result of whether to recommend system migration based on the inspection results of the pre-processed abnormal scenario inspection; Generate a migration assessment report based on the system information of the target system and the migration assessment results.

[0005] Optionally, calling the abnormal scenario preprocessing plug-in to preprocess the target system includes: reading the activation status information of all abnormal scenario preprocessing plug-ins, calling the abnormal scenario preprocessing plug-in with the activation status information activated to preprocess the target system, and the preprocessing includes: ignoring the upgrade of the specified software package, uninstalling the specified software package, skipping the kernel module check, skipping the backup step, specifying the backup path, and cleaning up part or all of the disk space.

[0006] Optionally, calling the abnormal scenario check plug-in to perform abnormal scenario check on the target system includes: software source verification, software package conflict detection, disk and directory status check, kernel module compatibility check, system compatibility check, software compatibility check and part or all of software package difference comparison.

[0007] Optionally, when giving a migration assessment result of whether to recommend system migration and generating a migration assessment report based on the inspection result of the pre-processed abnormal scenario check, if any pre-processing result or the inspection result of the abnormal scenario check is failure, a migration assessment result that does not recommend system migration is given and a migration assessment report is generated; otherwise, a migration assessment result that recommends system migration is given and a migration assessment report is generated.

[0008] Optionally, it also includes the step of adding a customized abnormal scenario preprocessing plug-in or abnormal scenario inspection plug-in: loading a customized plug-in generated based on a plug-in template, wherein the plug-in template specifies the template language, the type of the customized plug-in, and the data format of the corresponding type of result, wherein the type of the customized plug-in is an abnormal scenario preprocessing plug-in or an abnormal scenario inspection plug-in, and the corresponding type of result refers to the preprocessing result or the inspection result of the abnormal scenario inspection; verifying the syntax, input, and output of the customized plug-in and performing a test run, and if the test run is successful, adding it to the plug-in library; the plug-in library contains all abnormal scenario preprocessing plug-ins and abnormal scenario inspection plug-ins, and the activation status information of the plug-in can be set to activated or inactivated.

[0009] In addition, the present invention also provides a system migration method based on migration evaluation in a simulation environment, comprising: S1, collects environmental information in the migrated system; S2, generating a simulated upgrade environment based on container technology or virtualization technology according to the environment information of the migrated system; S3, executing the migration assessment method for improving the reliability of system migration in a simulated upgrade environment to obtain a migration assessment report; S4, parsing the migration assessment result in the migration assessment report, if the migration assessment result is a recommendation to perform system migration, jump to step S5; otherwise, end and exit; S5, performing system migration in the real environment of the migrated system.

[0010] Optionally, when performing the migration assessment method for improving system migration reliability in a simulated upgrade environment to obtain a migration assessment report in step S3, calling an abnormal scenario preprocessing plug-in to preprocess the target system includes: S101, use the rpm package compilation tool to back up and ignore the upgrade software package; S102, check whether the software package exists and is complete. If the software package exists and is complete, jump to step S103; otherwise, it is determined that the execution is wrong, and the process ends and exits; S103, uninstalling the upgrade software package ignored in the simulated upgrade environment; The calling of the abnormal scenario check plug-in to perform abnormal scenario check on the target system includes performing a package conflict check and a dependency check on the simulated upgrade environment after uninstalling the ignored upgrade software package, and providing a migration assessment result that recommends system migration if the package conflict check and the dependency check pass; In step S5, executing system migration in the real environment of the migrated system includes: uninstalling the ignore upgrade software package in the real environment of the migrated system, executing system upgrade of the real environment of the migrated system, and after the system upgrade of the real environment of the migrated system is completed, installing the ignore upgrade software package backed up by the rpm package compilation tool back to the real environment of the migrated system.

[0011] Optionally, when performing the migration assessment method for improving system migration reliability in a simulated upgrade environment to obtain a migration assessment report in step S3, calling the abnormal scenario check plug-in to perform an abnormal scenario check on the target system includes calling the abnormal scenario check plug-in to perform a software compatibility check on the target system: S201, obtaining the process ID pid of the target application in the migrated system; S202, obtaining a library file used by a target application process according to the process ID pid, and obtaining a used rpm package and a system library, system interface, and variables used by the target application according to the library file used by the target application process; S203, repackaging the rpm package used by the target application to obtain a local rpm package; S204, compare the local rpm package with the rpm package corresponding to the target application in the migration software source to generate a software compatibility analysis report, wherein the software compatibility analysis report includes whether the rpm packages are compatible, whether the system libraries are compatible, and whether the system interfaces are compatible. If the rpm package corresponding to the target application in the migration software source does not exist, the target application is determined to be incompatible, otherwise the target application is determined to be compatible; if the system library used by the local rpm package exists in the target application in the migration software source, the system library of the target application is determined to be compatible, otherwise the system library of the target application is determined to be incompatible; if the system interface and variables used by the local rpm package are the same as the system library in the rpm package of the target application in the migration software source, the system interface of the target application is determined to be compatible, otherwise the system interface of the target application is determined to be incompatible; S205, outputting a software compatibility analysis report.

[0012] In addition, the present invention also provides a migration assessment system for improving system migration reliability, comprising a microprocessor and a memory connected to each other, wherein the microprocessor is programmed or configured to execute the migration assessment method for improving system migration reliability or the system migration method based on migration assessment in a simulation environment.

[0013] In addition, the present invention also provides a computer-readable storage medium, which stores a computer program or instruction, and the computer program or instruction is programmed or configured to execute the migration evaluation method for improving the reliability of system migration or the system migration method based on migration evaluation in a simulation environment through a processor.

[0014] In addition, the present invention also provides a computer program product, including a computer program or instructions, which are programmed or configured to execute the migration evaluation method for improving system migration reliability or the system migration method based on migration evaluation in a simulation environment through a processor.

[0015] Compared with the prior art, the present invention mainly has the following advantages: the present invention provides a plug-in evaluation method for a dynamically extensible migration tool for system migration, which implements a plug-in information collection framework and template, a plug-in preprocessing framework and template, and a plug-in abnormal scenario inspection framework and template, deeply collects operating system information, and performs comprehensive migration abnormal scenario analysis, and is committed to adapting to different enterprises and different business evaluation needs without iteration, and has built-in multiple unique inspection plug-ins, which provide pre-migration stage strategy recommendations for the smooth transition of the CentOS operating system to the domestic operating system, and ensure the stability and efficiency of the entire system migration process. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1Schematic diagram of the basic flow of the method of the embodiment of the present invention.

[0017] Figure 2 It is a schematic diagram of the structure of an extensible plug-in framework in an embodiment of the present invention.

[0018] Figure 3 The present invention is a schematic diagram of an application process of a system migration scenario in an embodiment of the present invention.

[0019] Figure 4 The present invention is a schematic diagram of another application process of a system migration scenario in an embodiment of the present invention.

[0020] Figure 5 The figure is a schematic diagram of the workflow of the software compatibility analysis plug-in in an embodiment of the present invention. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the 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 creative work are within the scope of protection of the present invention.

[0022] like Figure 1 As shown, this embodiment provides a migration evaluation method for improving system migration reliability, comprising the following steps: Call the information collection plug-in to collect system information of the target system; Call the abnormal scenario preprocessing plug-in to preprocess the target system; Call the abnormal scenario check plug-in to perform abnormal scenario check on the target system; Provide a migration assessment result of whether to recommend system migration based on the inspection results of the pre-processed abnormal scenario inspection; Generate a migration assessment report based on the system information of the target system and the migration assessment results.

[0023] In this embodiment, when the information collection plug-in is called to collect system information of the target system, the collected system information includes part or all of the system version, architecture, host name, storage space, kernel configuration, startup parameters, version number, open ports, device drivers, command line interface, memory status, hardware board information, system call interface, file system mount point, service status, configuration parameters, disk details, environment variables, network connection status, process list and software package information. It should be noted that the collection of the above system information can be implemented in different calling information collection plug-ins, or partially or completely in the same calling information collection plug-in.

[0024] In this embodiment, calling the abnormal scenario preprocessing plug-in to preprocess the target system includes: reading the activation status information of all abnormal scenario preprocessing plug-ins, calling the abnormal scenario preprocessing plug-in with the activation status information activated to preprocess the target system, and the preprocessing includes: ignoring the upgrade of the specified software package, uninstalling the specified software package, skipping the kernel module check, skipping the backup step, specifying the backup path, and cleaning up part or all of the disk space; it should be noted that the above preprocessing can be implemented in different abnormal scenario preprocessing plug-ins respectively, and can also be implemented partially or completely in the same abnormal scenario preprocessing plug-in. Before the system information is collected and transferred to the migration abnormal scenario analysis phase, the known problems must be preprocessed. After preprocessing the known problems, the abnormal scenario is checked. Through the migration assessment preprocessing, the smooth progress of the system assessment can be ensured. The migration assessment method of this embodiment has a built-in abnormal scenario preprocessing framework, which contains a variety of predefined preprocessing plug-ins, and allows users to customize and add additional processing plug-ins according to needs. By default, these built-in plug-ins are not activated.

[0025] In this embodiment, the calling of the abnormal scenario check plug-in to perform abnormal scenario check on the target system includes: software source verification, software package conflict detection, disk and directory status check, kernel module compatibility check, system compatibility check, software compatibility check and some or all of the software package difference comparison. After completing the preprocessing of the migration abnormal scenario, a detailed inspection of common abnormalities will be carried out, and a simulated system migration will be implemented. Only by successfully passing this series of evaluations can the smooth progress of system migration be ensured. The migration evaluation method of this embodiment is equipped with a comprehensive abnormal scenario inspection framework, which covers multiple inspection dimensions and allows users to flexibly add customized abnormal inspection plug-ins to expand the inspection scope at any time. The default inspection plug-ins built into the tool include: software source verification plug-in, software package conflict detection plug-in, disk and directory status check plug-in, kernel module compatibility check plug-in, system compatibility check, software compatibility check plug-in, software compatibility check plug-in and software package difference comparison plug-in.

[0026] In this embodiment, when the migration assessment result of whether to recommend system migration is given and a migration assessment report is generated according to the inspection result of the pre-processed abnormal scenario inspection, if any of the pre-processing results or the inspection result of the abnormal scenario inspection is a failure, a migration assessment result that does not recommend system migration is given and a migration assessment report is generated; otherwise, a migration assessment result that recommends system migration is given and a migration assessment report is generated. The migration assessment report integrates the system information collection results and the inspection results of each plug-in module. The collected information is used to organize and back up the original system environment, while the inspection results of the plug-in module are used to evaluate the feasibility of system migration, and migration suggestions are made accordingly, clearly indicating whether it is "migratable" or "non-migratable". For environments that are evaluated as non-migratable, the migration assessment report will guide how to activate the corresponding pre-processing plug-in or add a new abnormal handling plug-in to try to solve the problems encountered during the evaluation process. If it is necessary to expand the information collection scope of the evaluation report or enhance the detection capability of abnormal scenarios, the user can insert the corresponding functional plug-in in the migration assessment method of this embodiment and re-execute the migration assessment process accordingly.

[0027] In this embodiment, the step of adding a custom abnormal scenario preprocessing plug-in or an abnormal scenario checking plug-in is also included: loading a custom plug-in generated based on a plug-in template, wherein the plug-in template specifies the template language, the type of the custom plug-in, and the data format of the corresponding type of result, wherein the type of the custom plug-in is an abnormal scenario preprocessing plug-in or an abnormal scenario checking plug-in, and the corresponding type of result refers to the result of preprocessing or the result of abnormal scenario checking; the syntax, input, and output of the custom plug-in are verified and tested, and if the test run is successful, it is added to the plug-in library; the plug-in library contains all abnormal scenario preprocessing plug-ins and abnormal scenario checking plug-ins, and the activation status information of the plug-in can be set to activated or inactivated. This embodiment provides a dynamically extended plug-in template that can support the dynamic expansion and preprocessing of the evaluation tool. By continuously inserting plug-ins, the continuous expansion of the functions of the migration evaluation tool can be achieved to adapt to different business scenarios of different enterprises.

[0028] Due to the different operating system states in different enterprises and business scenarios, the migration assessment tool cannot analyze whether the system can be migrated in any scenario. When it is analyzed that the system cannot be migrated, the pre-processing solution provided by the migration assessment tool cannot solve all abnormal scenarios so that the assessment can pass and reach the migration state. It is often necessary to manually process the migrated nodes, which is inefficient and cannot synchronize the processing results to other migrated systems. In order to solve the above problems, the method of this embodiment implements an extensible plug-in framework, such as Figure 2As shown, in addition to being responsible for page display, migration tool management, and node scheduling, the extensible plug-in framework also provides plug-in management functions and plug-in template management functions, and provides plug-in implementation templates for each type. The use process of the extensible plug-in framework is as follows: 1. Through plug-in template management, select a specific template according to the requirement type to quickly generate a plug-in of the specified type. The plug-in template specifies the template language and the data format for generating inspection results. 2. When adding a new plug-in, the syntax and plug-in input and output will be verified, and a test run will be performed. If the plug-in is successfully added, it will be added to the template management. 3. Any migration node can enable the plug-in and apply it on the migrated system. 4. On the migrated node, the migration analysis tool will load the plug-in under the execution path to realize the client operation of the plug-in. This embodiment also provides a built-in plug-in implementation method and a plug-in operating environment design to improve the reliability and security of migration assessment.

[0029] In order to solve the problem of the migrated system being modified and damaged during the migration assessment process, the method of this embodiment implements the execution of the evaluated plug-in content in a simulated environment, only modifies the rpm database content of the specified path, does not operate the real system environment file, and after the migration system assessment is completed, removes the migration tool and deletes the data to ensure that the migration assessment does not modify the system, and solves the problem of unclean environment and data damage caused by migration assessment in environments that do not need or cannot be migrated. Evaluation analysis and real upgrade testing are implemented in a simulated environment to ensure the safety and reliability of the migrated environment.

[0030] The migration assessment method for improving the reliability of system migration in this embodiment is used in the form of an assessment tool. As an optional application method, such as Figure 3 As shown, when it is applied to software package upgrade, its use method includes: installing the assessment tool on the migrated node; loading the assessment analysis plug-in, that is, calling the information collection plug-in, the abnormal scenario preprocessing plug-in and the abnormal scenario checking plug-in; copying the rpm database, and generating a simulated upgrade environment based on container technology or virtualization technology; executing the abnormal scenario preprocessing plug-in in the simulated upgrade environment to delete the software package; executing the abnormal scenario checking plug-in in the simulated upgrade environment to upgrade the software package of the simulated upgrade environment; generating a migration assessment report and performing environment cleanup.

[0031] As another optional application method, if there are packages in the migrated system that are forcibly installed and the dependencies are incomplete, a package conflict will be detected, resulting in the inability to migrate the system. Or some packages on the system need to be retained and cannot be upgraded. These two scenarios usually require manual repeated dependency processing and testing on the migrated nodes, which is inefficient. In order to solve these two problems, the ignored package preprocessing plug-in is implemented. During the migration assessment, the ignored packages are repackaged into rpm packages, and then installed back to the migrated system after the migration is completed. Figure 4 As shown, this embodiment provides a system migration method based on migration evaluation in a simulation environment, including the following steps: S1, collects environmental information in the migrated system; S2, generating a simulated upgrade environment based on container technology or virtualization technology according to the environment information of the migrated system; S3, executing the migration assessment method for improving the reliability of system migration in a simulated upgrade environment to obtain a migration assessment report; S4, parsing the migration assessment result in the migration assessment report, if the migration assessment result is a recommendation to perform system migration, jump to step S5; otherwise, end and exit; S5, performing system migration in the real environment of the migrated system.

[0032] In this embodiment, when the method for improving the reliability of system migration is performed in a simulated upgrade environment in step S3 to obtain a migration assessment report, calling the abnormal scenario preprocessing plug-in to preprocess the target system includes: S101, use the rpm package compilation tool to back up and ignore the upgrade software package; S102, check whether the software package exists and is complete. If the software package exists and is complete, jump to step S103; otherwise, it is determined that the execution is wrong, and the process ends and exits; S103, uninstalling the upgrade software package ignored in the simulated upgrade environment; The calling of the abnormal scenario check plug-in to perform abnormal scenario check on the target system includes performing a package conflict check and a dependency check on the simulated upgrade environment after uninstalling the ignored upgrade software package, and providing a migration assessment result that recommends system migration if the package conflict check and the dependency check pass; In step S5, executing system migration in the real environment of the migrated system includes: uninstalling the ignore upgrade software package in the real environment of the migrated system, executing system upgrade of the real environment of the migrated system, and after the system upgrade of the real environment of the migrated system is completed, installing the ignore upgrade software package backed up by the rpm package compilation tool back to the real environment of the migrated system.

[0033] In addition, in order to ensure that the application can run stably and reliably after migration, a reliable software compatibility analysis plug-in is built into the plug-in migration assessment tool of this embodiment. Users can input by adding the software package name or process id. The plug-in implements the compatibility analysis of the program's rpm package, library files, and interface variables, and outputs a compatibility analysis report. The criteria for whether the application is compatible are as follows: 1. The rpm package used by the application must exist in the migration software source; 2. The library files used by the application must exist in the corresponding software package of the migration software source; 3. The system interfaces and variables used by the application correspond to the software package related interfaces and variables in the migration software source. As an optional application method, such as Figure 5 As shown, in step S3, when the method for improving the reliability of system migration is performed in a simulated upgrade environment to obtain a migration assessment report, calling the abnormal scenario check plug-in to perform an abnormal scenario check on the target system includes calling the abnormal scenario check plug-in to perform a software compatibility check on the target system: S201, obtaining the process ID pid of the target application in the migrated system; S202, obtaining a library file used by a target application process according to the process ID pid, and obtaining a used rpm package and a system library, system interface, and variables used by the target application according to the library file used by the target application process; S203, repackaging the rpm package used by the target application to obtain a local rpm package; S204, compare the local rpm package with the rpm package corresponding to the target application in the migration software source to generate a software compatibility analysis report, wherein the software compatibility analysis report includes whether the rpm packages are compatible, whether the system libraries are compatible, and whether the system interfaces are compatible. If the rpm package corresponding to the target application in the migration software source does not exist, the target application is determined to be incompatible, otherwise the target application is determined to be compatible; if the system library used by the local rpm package exists in the target application in the migration software source, the system library of the target application is determined to be compatible, otherwise the system library of the target application is determined to be incompatible; if the system interface and variables used by the local rpm package are the same as the system library in the rpm package of the target application in the migration software source, the system interface of the target application is determined to be compatible, otherwise the system interface of the target application is determined to be incompatible; S205, outputting a software compatibility analysis report.

[0034] In summary, this embodiment proposes a plug-in evaluation method for a dynamically extensible migration tool for system migration. The method implements a plug-in migration evaluation framework, splits the evaluation function of the migration evaluation tool into independent plug-ins, and can quickly implement plug-ins and apply global plug-ins through plug-in templates. Plug-in templates are divided into information collection plug-ins, abnormal scenario preprocessing plug-ins, and abnormal scenario inspection plug-ins. The plug-in system migration evaluation method first loads the information collection plug-in to perform a comprehensive environmental evaluation and information collection on the target system, then loads the abnormal scenario preprocessing plug-in, preprocesses the system in a simulated environment, simulates the environment adjustment before migration, and finally loads the abnormal scenario inspection plug-in. In the simulated environment, the system is inspected and simulated upgraded. Through the inspection results and the results of the simulated upgrade, it is deeply evaluated whether the system can be migrated. If the migration evaluation result is not satisfied, the plug-in content executed in each stage can be adjusted or a new plug-in can be inserted according to the template to achieve the functions of rapid migration debugging and tool expansion.

[0035] The method of this embodiment mainly has the following advantages: 1. The plug-in template can realize the rapid generation of plug-ins. After adding a plug-in, the plug-in can be sent to all migrated systems that enable the plug-in for application. There is no need to manually process each node manually, which reduces manual errors and greatly improves the use efficiency. 2. The plug-in framework can realize customized migration assessment content and can meet the assessment needs of different enterprises and different businesses. 3. The migration assessment is carried out in a simulated environment to ensure that the environment of the migrated system is not damaged, and the environment cleanup after the assessment can restore the system environment. 4. By fully upgrading the software package of the simulated environment, the most accurate prediction of whether it can be upgraded can be achieved. 5. Since the existing environment can be left unchanged, a solution for system upgrade can be explored by continuously adjusting the migration assessment preprocessing method. 6. By ignoring the software package plug-in, it is possible to retain the software packages that are not wanted or needed to be upgraded. For example, if the system has x86_64 and i686 software packages, when only the x86_64 software package needs to be upgraded, the i686 software package can be ignored in batches. 7. By ignoring the software package plug-in, it can be used to solve abnormal scenarios such as software package conflicts in the migration assessment as a preprocessing before migration. 8. In the migration assessment, ignoring the software package means uninstalling the corresponding rpm package in the simulation environment, and then performing a comprehensive simulation upgrade. Therefore, the ignore software package plug-in can be used as a debugging tool for the migration assessment to explore how to deal with some abnormal environments to achieve a successful assessment, and then find solutions that can achieve a real upgrade. 9. The software compatibility analysis plug-in can ensure that the software package runs safely and reliably on the migrated system, improve the quality of migration, reduce the frequency of system rollbacks, and improve migration efficiency. 10. According to the compatibility analysis report, you can get a detailed understanding of the rpm packages, libraries used, interfaces, etc. related to the application. For incompatible software packages, the report can also be used as a basis for solving compatibility issues. 11. For software packages that are checked and determined to be incompatible, they can be migrated by uninstalling or performing software adaptation or software replacement.

[0036] In addition, this embodiment also provides a migration assessment system for improving system migration reliability, including a microprocessor and a memory connected to each other, wherein the microprocessor is programmed or configured to execute the migration assessment method for improving system migration reliability or the system migration method based on migration assessment in a simulation environment.

[0037] In addition, this embodiment also provides a computer-readable storage medium, which stores a computer program or instruction, and the computer program or instruction is programmed or configured to execute the migration evaluation method for improving the reliability of system migration or the system migration method based on migration evaluation in a simulation environment through a processor.

[0038] In addition, this embodiment also provides a computer program product, including a computer program or instructions, which are programmed or configured to execute the migration evaluation method for improving system migration reliability or the system migration method based on migration evaluation in a simulation environment through a processor.

[0039] Those skilled in the art should understand that the technical solutions provided by the embodiments of the present application may be in the form of methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the process Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide for implementing the process in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0040] The above is only a preferred embodiment of the present invention, and the protection scope of the present invention is not limited to the above embodiments. All technical solutions under the concept of the present invention belong to the protection scope of the present invention. It should be pointed out that for ordinary technicians in this technical field, some improvements and modifications without departing from the principle of the present invention should also be regarded as the protection scope of the present invention.

Claims

1. A migration evaluation method for improving system migration reliability, characterized in that: The steps include: Call the information collection plug-in to collect system information of the target system; Call the abnormal scenario preprocessing plug-in to preprocess the target system; Call the abnormal scenario check plug-in to perform abnormal scenario check on the target system; Provide a migration assessment result of whether to recommend system migration based on the inspection results of the pre-processed abnormal scenario inspection; Generate a migration assessment report based on the system information of the target system and the migration assessment results.

2. The migration evaluation method for improving system migration reliability according to claim 1, characterized in that: The calling of the abnormal scenario preprocessing plug-in to preprocess the target system includes: reading the activation status information of all abnormal scenario preprocessing plug-ins, calling the abnormal scenario preprocessing plug-in with the activation status information as activated to preprocess the target system, and the preprocessing includes: ignoring the upgrade of the specified software package, uninstalling the specified software package, skipping the kernel module check, skipping the backup step, specifying the backup path, and cleaning up part or all of the disk space; the calling of the abnormal scenario inspection plug-in to perform abnormal scenario inspection on the target system includes: software source verification, software package conflict detection, disk and directory status check, kernel module compatibility check, system compatibility check, software compatibility check, and part or all of software package difference comparison.

3. The migration evaluation method for improving system migration reliability according to claim 1, characterized in that: When the migration assessment result of whether to recommend system migration is given and a migration assessment report is generated based on the inspection result of the pre-processed abnormal scenario check, if any pre-processing result or the inspection result of the abnormal scenario check is failure, a migration assessment result of not recommending system migration is given and a migration assessment report is generated; otherwise, a migration assessment result of recommending system migration is given and a migration assessment report is generated.

4. The migration evaluation method for improving system migration reliability according to claim 1, characterized in that: It also includes the step of adding a customized abnormal scenario preprocessing plug-in or an abnormal scenario inspection plug-in: loading a customized plug-in generated based on a plug-in template, wherein the plug-in template specifies a template language, a type of customized plug-in, and a data format of a result of a corresponding type, wherein the type of customized plug-in is an abnormal scenario preprocessing plug-in or an abnormal scenario inspection plug-in, and the result of a corresponding type refers to a preprocessing result or an abnormal scenario inspection result; verifying the syntax, input, and output of the customized plug-in and performing a test run, and if the test run is successful, adding it to the plug-in library; the plug-in library contains all abnormal scenario preprocessing plug-ins and abnormal scenario inspection plug-ins, and the activation status information of the plug-in can be set to activated or inactivated.

5. A system migration method based on migration evaluation in a simulation environment, characterized in that: The steps include: S1, collects environmental information in the migrated system; S2, generating a simulated upgrade environment based on container technology or virtualization technology according to the environment information of the migrated system; S3, executing the migration assessment method for improving system migration reliability as described in any one of claims 1 to 4 in a simulated upgrade environment to obtain a migration assessment report; S4, parsing the migration assessment result in the migration assessment report, if the migration assessment result is a recommendation to perform system migration, jump to step S5; otherwise, end and exit; S5, performing system migration in the real environment of the migrated system.

6. The system migration method based on migration evaluation in a simulation environment according to claim 5, characterized in that: When the method for improving the reliability of system migration as claimed in any one of claims 1 to 4 is executed in a simulated upgrade environment in step S3 to obtain a migration assessment report, calling the abnormal scenario preprocessing plug-in to preprocess the target system includes: S101, use the rpm package compilation tool to back up and ignore the upgrade software package; S102, check whether the software package exists and is complete. If the software package exists and is complete, jump to step S103; otherwise, it is determined that the execution is wrong, and the process ends and exits; S103, uninstalling the upgrade software package ignored in the simulated upgrade environment; The calling of the abnormal scenario check plug-in to perform abnormal scenario check on the target system includes performing a package conflict check and a dependency check on the simulated upgrade environment after uninstalling the ignored upgrade software package, and providing a migration assessment result that recommends system migration if the package conflict check and the dependency check pass; In step S5, executing system migration in the real environment of the migrated system includes: uninstalling the ignore upgrade software package in the real environment of the migrated system, executing system upgrade of the real environment of the migrated system, and after the system upgrade of the real environment of the migrated system is completed, installing the ignore upgrade software package backed up by the rpm package compilation tool back to the real environment of the migrated system.

7. The system migration method based on migration evaluation in a simulation environment according to claim 5, characterized in that: In step S3, when the method for improving the reliability of system migration as described in any one of claims 1 to 4 is performed in a simulated upgrade environment to obtain a migration assessment report, calling the abnormal scenario check plug-in to perform an abnormal scenario check on the target system includes calling the abnormal scenario check plug-in to perform a software compatibility check on the target system: S201, obtaining the process ID pid of the target application in the migrated system; S202, obtaining a library file used by a target application process according to the process ID pid, and obtaining a used rpm package and a system library, system interface, and variables used by the target application according to the library file used by the target application process; S203, repackaging the rpm package used by the target application to obtain a local rpm package; S204, compare the local rpm package with the rpm package corresponding to the target application in the migration software source to generate a software compatibility analysis report, wherein the software compatibility analysis report includes whether the rpm packages are compatible, whether the system libraries are compatible, and whether the system interfaces are compatible. If the rpm package corresponding to the target application in the migration software source does not exist, the target application is determined to be incompatible, otherwise the target application is determined to be compatible; if the system library used by the local rpm package exists in the target application in the migration software source, the system library of the target application is determined to be compatible, otherwise the system library of the target application is determined to be incompatible; if the system interface and variables used by the local rpm package are the same as the system library in the rpm package of the target application in the migration software source, the system interface of the target application is determined to be compatible, otherwise the system interface of the target application is determined to be incompatible; S205, outputting a software compatibility analysis report.

8. A migration assessment system for improving system migration reliability, comprising a microprocessor and a memory connected to each other, characterized in that: The microprocessor is programmed or configured to execute the migration evaluation method for improving system migration reliability as described in any one of claims 1 to 4 or the system migration method based on migration evaluation in a simulation environment as described in any one of claims 5 to 7.

9. A computer-readable storage medium having a computer program or instruction stored therein, characterized in that: The computer program or instruction is programmed or configured to execute, through a processor, the method for migration evaluation for improving system migration reliability as described in any one of claims 1 to 4 or the system migration method based on migration evaluation in a simulation environment as described in any one of claims 5 to 7.

10. A computer program product comprising a computer program or instructions, characterized in that The computer program or instruction is programmed or configured to execute, through a processor, the method for migration evaluation for improving system migration reliability as described in any one of claims 1 to 4 or the system migration method based on migration evaluation in a simulation environment as described in any one of claims 5 to 7.

Images