System migration compatibility assessment method and device

Abstract

The present invention discloses a system migration compatibility assessment method and device, belonging to the field of computer technology. The method includes: obtaining a binary file related to business software in a source operating system, and obtaining a first basic library file on which the business software depends and a first symbol information called for the first basic library file by parsing the binary file; obtaining difference comparison data of the target operating system relative to the source operating system at a difference granularity of symbol information; the difference types include same, added, removed and changed; according to the difference comparison data, determining whether the target operating system has removed and / or changed the first symbol information called for the first basic library file by the business software relative to the source operating system; if so, determining that the business software is incompatible with the target operating system. The present invention can more accurately obtain an assessment result of whether the business software is compatible with the target operating system.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a system migration compatibility assessment method and device. Background Art

[0002] After using the server operating system for a period of time, such as 5 years, enterprise users will face the need to update the operating system. However, it is difficult to redeploy their own business software and business data in the new operating system environment. Therefore, they will require the operating system to be changed by in-place migration. The principle of in-place migration of the operating system is to keep the upper-layer application software and configuration unchanged, keep the user data and the underlying hardware devices unchanged, and only replace the middle layer provided by the operating system to achieve the purpose of in-place migration of the operating system. In-place migration of the operating system requires that the target operating system after migration is compatible with the business software before migration.

[0003] In the related art, a virtual environment identical to the target operating system after migration is constructed, and then the business software is simulated in the virtual environment to evaluate whether the two are compatible. However, the virtual environment simulation method cannot cover the interaction process of all business software, which is not only time-consuming but also has poor evaluation accuracy. Summary of the invention

[0004] The present invention provides a system migration compatibility assessment method and device, which can solve the problems of high time cost and poor assessment accuracy of compatibility assessment in related technologies. The technical solution is as follows:

[0005] In one aspect, a system migration compatibility assessment method is provided, the method comprising:

[0006] Obtaining a binary file related to the business software in the source operating system, and obtaining a first basic library file on which the business software depends and first symbol information called for the first basic library file by parsing the binary file;

[0007] Obtaining difference comparison data of the target operating system relative to the source operating system at a difference granularity of symbol information; the difference types include identical, added, removed, and changed;

[0008] Based on the difference comparison data, determine whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system; if so, determine that the business software is incompatible with the target operating system.

[0009] In another aspect, a system migration compatibility assessment device is provided, the device comprising:

[0010] A first acquisition unit is used to acquire a binary file related to the business software in the source operating system, and obtain a first basic library file on which the business software depends and first symbol information called for the first basic library file by parsing the binary file;

[0011] A second acquisition unit is used to acquire difference comparison data of the target operating system relative to the source operating system in the difference granularity of symbol information; the difference types include same, added, removed and changed;

[0012] An evaluation and determination unit is used to determine, based on the difference comparison data, whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system; if so, determine that the business software is incompatible with the target operating system.

[0013] On the other hand, a computer device is provided, which includes a memory and a processor, wherein the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory to implement the steps of the system migration compatibility assessment method described above.

[0014] On the other hand, a computer-readable storage medium is provided, wherein a computer program is stored in the storage medium, and when the computer program is executed by a processor, the steps of the system migration compatibility assessment method described above are implemented.

[0015] On the other hand, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the steps of the system migration compatibility assessment method described above are implemented.

[0016] The technical solution provided by the present invention can at least bring the following beneficial effects:

[0017] Whether the business software can run normally in the target operating system is not just whether the basic library files it depends on exist in the target operating system, but whether the symbol information in the basic library files called by the business software exists in the corresponding basic library files in the target operating system. Therefore, by obtaining the first basic library file that the business software depends on and the first symbol information called for the first basic library file, and obtaining the difference comparison data of the target operating system relative to the source operating system in the difference granularity of symbol information, it is determined whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system. It can be seen that this solution does not need to build a virtual environment for the target operating system, but only needs to analyze the difference in symbol granularity, which not only has low time cost, but also can more accurately obtain the evaluation result of whether the business software is compatible with the target operating system. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0019] Figure 1 is a flow chart of a system migration compatibility assessment method provided by an embodiment of the present invention;

[0020] Figure 2 It is a structural diagram of a system migration compatibility assessment device provided by an embodiment of the present invention;

[0021] Figure 3 It is a hardware architecture diagram of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions 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 part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0023] As mentioned above, the relevant technology is to build a virtual environment that is the same as the target operating system after migration, and then simulate the operation of the business software in the virtual environment to evaluate whether the two are compatible. However, the method of using virtual environment simulation operation cannot cover the interaction process of all business software, which is not only time-consuming, but also has poor evaluation accuracy.

[0024] The inventive concept of the present invention is that the business software can run compatibly in the target operating system, which is related to the basic library files provided by the target operating system, and the business software needs to call the symbol information in the basic library files when running. Based on this, when evaluating whether the business software is compatible with the target operating system, it is not necessary to build a virtual environment, but to determine whether the target operating system has the basic library files that the business software depends on and the symbol information called for the basic library files to achieve compatibility evaluation.

[0025] The specific implementation of the above concept is described below.

[0026] Please refer to Figure 1 , an embodiment of the present invention provides a system migration compatibility assessment method, the method comprising:

[0027] Step 100, obtaining a binary file related to the business software in the source operating system, and obtaining a first basic library file on which the business software depends and first symbol information called for the first basic library file by parsing the binary file;

[0028] Step 102, obtaining difference comparison data of the target operating system relative to the source operating system at a difference granularity of symbol information; the difference types include same, added, removed and changed;

[0029] Step 104, based on the difference comparison data, determine whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system; if so, determine that the business software is incompatible with the target operating system.

[0030] In the embodiment of the present invention, whether the business software can run normally in the target operating system is not determined by whether the basic library files it depends on exist in the target operating system, but whether the symbol information in the basic library files called by the business software exists in the corresponding basic library files in the target operating system. Therefore, by obtaining the first basic library file that the business software depends on and the first symbol information called for the first basic library file, and obtaining the difference comparison data of the target operating system relative to the source operating system in the difference granularity of symbol information, it is determined whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system. It can be seen that this solution does not need to build a virtual environment for the target operating system, but only needs to analyze the difference in symbol granularity, which not only has low time cost, but also can more accurately obtain the evaluation result of whether the business software is compatible with the target operating system.

[0031] Described below Figure 1 How the various steps are performed.

[0032] First, for step 100, a binary file related to the business software in the source operating system is obtained, and a first basic library file on which the business software depends and first symbol information called for the first basic library file are obtained by parsing the binary file.

[0033] In the embodiment of the present invention, the binary files related to the business software need to be obtained in the customer's source operating system environment. In the embodiment of the present invention, the binary files can be obtained in at least the following three ways:

[0034] Method 1: Traverse the process services running in the source operating system to obtain.

[0035] In the first method, the business software runs in the source operating system. The process services running in the source operating system must contain the process services of the business software. Therefore, the binary files related to the business software can be obtained by traversing the process services running in the source operating system. Specifically, the following steps may be included:

[0036] S11, traversing the process services running in the source operating system to obtain a binary file corresponding to each process service;

[0037] S12. Filter out the binary files executed by the source operating system basic service from the binary files corresponding to each process service obtained through traversal, obtain the first binary file related to the business software, and record the obtained first binary file into a list to obtain list A1.

[0038] Since not all process services running in the source operating system are process services of the business software, but there are binary files executed by some basic services, among which the binary files of the source operating system's basic services can be obtained in the official software release package released for the source operating system, the binary files executed by this part of the basic services can be filtered out from the traversed binary files to obtain the first binary file related to the business software. In this method one, the first binary file can be used as the binary file related to the business software in the source operating system.

[0039] Method 2: Obtaining the specified business software based on user input.

[0040] In this second method, since not all business software in the operating system may be in the process of running, the first binary file obtained by using the first method may not be able to overwrite the business software that is not running. In this second method, the user is familiar with the business software deployed in the operating system, and the user can input the specified business software to obtain the binary file related to the specified business software, which can specifically include: obtaining the specified business software input by the user, and traversing the specified business software in the source operating system to obtain the second binary file corresponding to the specified business software, and recording the second binary file in the list to obtain List A2. In this second method, the obtained second binary file can be directly used as a binary file related to the business software.

[0041] Method 3: Merge the binary files obtained by the above two methods.

[0042] Since the business software that is not running will be missed in method one, and the user in method two is only concerned about the individual business software, so some business software may be missed, the binary files obtained by the above two methods are merged, that is: the first binary file and the second binary file are taken as the union operation to obtain the binary files related to the business software in the source operating system. That is to say, after taking the union of List A1 and List A2, List A3 is obtained. This can make up for the shortcomings of the above two methods, so that the business software covered by the binary file obtained by method three is wider and more accurate, which can further improve the accuracy of the compatibility assessment results.

[0043] After obtaining the binary file related to the business software in the source operating system, the binary file needs to be parsed to obtain the basic library file in the binary file, and the obtained basic library file is determined as the first basic library file that the business software depends on; continue to parse the first basic library file to obtain all the symbol information contained in the first basic library file. Not all the symbol information in the first basic library file needs to be called by the business software, and the first symbol information called by the business software for the first basic library file is filtered out from all the symbol information. Among them, the system command "readelf()" can be used to obtain the symbol information called by the business software in the system for a binary file.

[0044] It can be understood that in order for the business software to run normally in the target operating system, the target operating system needs to have a first basic library file and the first basic library file needs to have the first symbol information called by the business software. It can also be understood that the number of first basic library files can be at least one, and each first basic library file has at least one first symbol information. For example, the first basic library files are file 11, file 12, file 13, file 21, file 22 and file 31, respectively. The first symbol information called in file 11 is symbol information 111 and symbol information 112. The first symbol information called in file 12 is symbol information 211, symbol information 212 and symbol information 213, and so on.

[0045] Then, for step 102, the difference comparison data of the target operating system relative to the source operating system at the difference granularity of symbol information is obtained; the difference types include same, added, removed and changed.

[0046] In the embodiment of the present invention, the difference comparison data may be generated in advance based on the software release package and software debugging package officially provided for the source operating system and the target operating system.

[0047] The difference granularity of the difference comparison data in the embodiment of the present invention is the level of symbol information. Among them, the difference granularity can be rpm package level, basic library file level, and symbol information level from high level to low level. Since the business software needs to call the function interface during operation, and the function interface belongs to the symbol information level, therefore, only using the basic library file to perform compatibility analysis and evaluation, the accuracy of the evaluation result is poor.

[0048] In order to obtain the difference comparison data of the target operating system with respect to the source operating system in the difference granularity of symbol information, it is necessary to collect the symbol information of the source operating system and the target operating system respectively in advance. In the embodiment of the present invention, the symbol information of the operating system can be collected at least in the following manner (S21-S24):

[0049] S21: Obtain the official software release package and software debugging package for the corresponding version of the operating system.

[0050] S22: parsing the basic library files provided by the version of the operating system from the software release package, and parsing the software debugging files provided by the version of the operating system from the software debugging package.

[0051] S23: The basic library file and the software debugging file with the same file name are taken as a pair to obtain a plurality of file pairs.

[0052] S24: For each file pair, function matching is performed using the basic library file and the software debugging file in the file pair to determine the symbol information in the basic library file in the file pair.

[0053] In step S21, the software release package is a software package officially released for the operating system, and the software release package includes multiple rpm packages; the software debugging package is a software package corresponding to the debugging information of the software release package, and the name of the software debugging package generally has the word debuginfo after it.

[0054] In step S22, for the Linux system, the name of the basic library file parsed from the software release package generally has the word ".so.", and the software debugging file parsed from the software debugging package has the same name as the basic library file, but the software debugging file suffix is ​​generally ".dubug". The software debugging file records the symbol information provided by the corresponding basic file in the software release package.

[0055] In step S24, since the basic library file of the software release package is a compiled binary file, the binary file is unreadable, while the software debugging file is a text file, which is equivalent to the source code and remark information before compilation. In the embodiment of the present invention, multiple function symbols can be retrieved from the software debugging file of the file pair by text retrieval, and then each function symbol is used to verify whether the function symbol exists in the basic library file of the file pair. If it exists, it is determined that the function symbol is the symbol information in the basic library file. If it does not exist, it is determined that the function symbol is not the symbol information in the basic library file.

[0056] By using the above method, the rpm package, the basic library file in the rpm package, and the symbol information in the basic library file can be obtained from both the source operating system and the target operating system. Then, the information obtained from the two operating systems is compared to obtain the difference comparison data. Among them, the difference types in the difference comparison data can include same, added, removed, and changed.

[0057] In one implementation, the difference comparison data includes at least a first difference comparison table whose difference granularity is the basic library file and a second difference comparison table whose difference granularity is the symbol information; the second difference comparison table is a statistics of the symbol information differences in the basic library files that exist in both the source operating system and the target operating system and whose difference type is change.

[0058] Among them, the first difference comparison table records the differences in basic library files of the target operating system compared to the source operating system. The first difference comparison table includes multiple first difference items, each of which has a difference type, and the difference type may include same, addition, removal and change.

[0059] For example, a first difference item includes a basic library file A1 of a source operating system and a basic library file A1 of a target operating system, and the difference type is the same, indicating that the basic library file A1 exists in both the source operating system and the target operating system; for another example, a first difference item includes a basic library file A2 of a target operating system, and the difference type is increase, indicating that the target operating system has added basic library file A2 relative to the source operating system; for another example, a first difference item includes a basic library file A3 of a source operating system, and the difference type is removal, indicating that the target operating system has removed basic library file A3 relative to the source operating system; for another example, a first difference item includes a basic library file A4 of a source operating system and a basic library file A5 of a target operating system, and the difference type is change, indicating that the target operating system has changed basic library file A4 in the source operating system to basic library file A5.

[0060] For the basic library files whose difference types are same, removed, and added in the first difference comparison table, the corresponding difference types of the symbol information in the basic library files are also same, removed, and added. Therefore, in the second difference comparison table, there is no need to explain the symbol information in the basic library files whose difference types are same, removed, and added. Only the symbol information differences in the basic library files whose difference types are changed can be counted. In this way, the use of these two difference comparison tables can reduce the amount of difference comparison data and improve the evaluation speed of compatibility evaluation.

[0061] In order to further reduce the data volume of the symbol information in the second difference comparison table, the difference types of the symbol information in the second difference comparison table include removal, addition and change, and there is no need to count the symbol information with the same difference type. Among them, the second difference comparison table includes multiple second difference items, and the second difference items may include the identifier of the basic library file in the source operating system, the identifier of the basic library file in the target operating system, the difference type, the symbol information in the source operating system, and the symbol information in the target operating system. For example, a second difference item includes the identifier B11 of the basic library file in the source operating system, the identifier B21 of the basic library file in the target operating system, the difference type is addition, the symbol information in the source operating system is none, and the symbol information in the target operating system is symbol information B2111.

[0062] Finally, for step 104, based on the difference comparison data, determine whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system; if so, determine that the business software is incompatible with the target operating system.

[0063] In the embodiment of the present invention, based on the difference comparison data obtained in the above steps, this step can be implemented in at least the following ways:

[0064] Determine, according to the first difference comparison table, whether there is a second basic library file whose difference type is removal and / or a third basic library file whose difference type is change in the second basic library file;

[0065] The first step is to determine: if the second basic library file exists, determine that the business software is incompatible with the target operating system;

[0066] If there is a second basic library file whose difference type is removed, it means that all symbol information in the second basic library file has been removed, which means that the second basic library file that the business software depends on and the first symbol information called for the second basic library file do not exist, so the business software is incompatible with the target operating system; if there is no second basic library file whose difference type is removed, it is necessary to determine the compatibility evaluation result in conjunction with the result of the second step.

[0067] The second step is to determine: if the third basic library file exists, determine whether there is second symbol information that has been removed and / or changed in the first symbol information called for the third basic library file based on the second difference comparison table; if so, determine that the business software is incompatible with the target operating system.

[0068] If there is a third basic library file with a difference type of change, then locate the second difference item in the second difference comparison table according to the identifier of the third basic library file in the source operating system. The second difference item can be at least one, and then determine whether the second difference item contains the first symbol information called for the third basic library file, and the first symbol information is removed and / or changed. If it exists, use the first symbol information as the second symbol information, so that the evaluation result can be obtained that the business software is incompatible with the target operating system. If it does not exist, it is necessary to determine the compatibility evaluation result in conjunction with the first step determination result.

[0069] If at least one of the above two determination results is incompatible, the evaluation result is incompatible; if the above two determination results are both compatible, the evaluation result is compatible.

[0070] Further, after obtaining the evaluation result, if the evaluation result is incompatible, in order to provide the customer with incompatible warning information, the rpm software package to which the second basic library file and / or the third basic library file belongs can be determined, and incompatible warning information is generated according to the rpm software package to which it belongs. If the result of the first step is incompatible, it is necessary to determine the rpm package to which the third basic library file belongs, and the generated incompatible warning information is that the business software is incompatible with the destination operating system because the third basic library file in the rpm package is removed by the destination operating system. If the result of the second step is incompatible, it is necessary to determine the rpm package to which the fourth basic library file belongs, and the generated incompatible warning information is that the business software is incompatible with the destination operating system because the fourth basic library file in the rpm package is changed by the destination operating system, resulting in the removal and / or change of the second symbol information called by the business software for the fourth basic library file, resulting in the incompatibility of the business software with the destination operating system.

[0071] In the embodiment of the present invention, there is no need to build a virtual environment for the target operating system. It is only necessary to analyze the difference in symbol granularity, which not only reduces the time cost but also can more accurately obtain the evaluation result of whether the business software is compatible with the target operating system.

[0072] Please refer to Figure 2 , an embodiment of the present invention provides a system migration compatibility assessment device, the device comprising:

[0073] A first acquisition unit 201 is used to acquire a binary file related to the business software in the source operating system, and obtain a first basic library file on which the business software depends and first symbol information called for the first basic library file by parsing the binary file;

[0074] The second acquisition unit 202 is used to acquire the difference comparison data of the target operating system relative to the source operating system in the difference granularity of symbol information; the difference types include same, added, removed and changed;

[0075] The evaluation and determination unit 203 is used to determine whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system based on the difference comparison data; if so, it is determined that the business software is incompatible with the target operating system.

[0076] In one embodiment of the present invention, when the first acquisition unit executes the acquisition of the binary file related to the business software in the source operating system, the process specifically includes:

[0077] Traverse the process services currently running in the source operating system to obtain the binary file corresponding to each process service;

[0078] The binary file executed by the source operating system basic service is filtered out from the binary files corresponding to each process service obtained through traversal, so as to obtain the first binary file related to the business software.

[0079] In one embodiment of the present invention, when the first acquisition unit executes the acquisition of the binary file related to the business software in the source operating system, the process specifically includes:

[0080] The designated business software input by the user is obtained, and the designated business software is traversed in the source operating system to obtain a second binary file corresponding to the designated business software.

[0081] In one embodiment of the present invention, the difference comparison data is generated in advance based on the software release package and software debugging package officially provided for the source operating system and the target operating system.

[0082] In one embodiment of the present invention, the difference comparison data at least includes a first difference comparison table whose difference granularity is a basic library file and a second difference comparison table whose difference granularity is symbol information; the second difference comparison table is a statistical analysis of the symbol information differences in the basic library files that exist in both the source operating system and the target operating system and whose difference type is a change;

[0083] The evaluation and determination unit is specifically used to: determine whether there is a second basic library file with a difference type of removal and / or a third basic library file with a difference type of change in the first basic library file according to the first difference comparison table; if the second basic library file exists, determine that the business software is incompatible with the target operating system; if the third basic library file exists, determine whether there is second symbol information that is removed and / or changed in the first symbol information called for the third basic library file according to the second difference comparison table, and if so, determine that the business software is incompatible with the target operating system.

[0084] In one embodiment of the present invention, the device may further include: a warning determination unit, configured to determine the rpm software package to which the second basic library file and / or the third basic library file belongs, and generate incompatible warning information according to the rpm software package to which they belong.

[0085] It should be noted that the system migration compatibility assessment device provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the system migration compatibility assessment device provided in the above embodiment and the system migration compatibility assessment method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0086] The embodiment of the present application also provides a computer device, please refer to Figure 3 The computer device includes a processor and a memory, in which at least one instruction, at least one program, code set or instruction set is stored, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the system migration compatibility assessment method provided by the above-mentioned method embodiments.

[0087] An embodiment of the present application also provides a computer-readable storage medium, on which is stored at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement the system migration compatibility assessment method provided by the above-mentioned method embodiments.

[0088] An embodiment of the present application also provides a computer program product, which includes a computer program. A processor of a computer device reads the computer program from a computer-readable storage medium, and the processor executes the computer program, so that the computer device executes the system migration compatibility assessment method described in any of the above embodiments.

[0089] For the convenience of description, the above system or device is described by dividing it into various modules or units according to its functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0090] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

[0091] Finally, it should be noted that, in this article, relational terms such as first, second, third and fourth are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0092] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A system migration compatibility assessment method, characterized in that: For evaluating whether the service software in the source operating system is compatible with the target operating system, the method comprises: Obtaining a binary file related to the business software in the source operating system, and obtaining a first basic library file on which the business software depends and first symbol information called for the first basic library file by parsing the binary file; the first symbol information is symbol information that needs to be called that is screened out from all symbol information contained in the first basic library file; Obtaining difference comparison data of the target operating system relative to the source operating system at a difference granularity of symbol information; the difference types include identical, added, removed, and changed; Determine, based on the difference comparison data, whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system; if so, determine that the business software is incompatible with the target operating system; The difference comparison data at least includes a first difference comparison table whose difference granularity is the basic library file and a second difference comparison table whose difference granularity is the symbol information; the second difference comparison table is a statistical analysis of the symbol information differences in the basic library files that exist in both the source operating system and the target operating system and whose difference type is the change; The method of determining, based on the difference comparison data, whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system, and if so, determining that the business software is incompatible with the target operating system, includes: determining, based on the first difference comparison table, whether there is a second basic library file with a difference type of removal and / or a third basic library file with a difference type of change in the first basic library file; if the second basic library file exists, determining that the business software is incompatible with the target operating system; if the third basic library file exists, determining, based on the second difference comparison table, whether there is second symbol information that is removed and / or changed in the first symbol information called for the third basic library file, and if so, determining that the business software is incompatible with the target operating system.

2. The method according to claim 1, characterized in that The step of obtaining binary files related to the business software in the source operating system includes: Traverse the process services currently running in the source operating system to obtain the binary file corresponding to each process service; The binary file executed by the source operating system basic service is filtered out from the binary files corresponding to each process service obtained through traversal, so as to obtain the first binary file related to the business software.

3. The method according to claim 1 or 2, characterized in that: The step of obtaining binary files related to the business software in the source operating system includes: The designated business software input by the user is obtained, and the designated business software is traversed in the source operating system to obtain a second binary file corresponding to the designated business software.

4. The method according to claim 1, characterized in that: The difference comparison data is generated in advance based on the software release package and software debugging package officially provided for the source operating system and the target operating system.

5. The method according to claim 1, characterized in that After determining that the business software is incompatible with the target operating system, the method further includes: Determine the rpm software package to which the second basic library file and / or the third basic library file belongs, and generate incompatible warning information according to the rpm software package to which they belong.

6. A system migration compatibility assessment device, characterized in that: The device is used to evaluate whether the service software in the source operating system is compatible with the target operating system, and includes: A first acquisition unit is used to acquire a binary file related to the business software in the source operating system, and obtain a first basic library file on which the business software depends and first symbol information called for the first basic library file by parsing the binary file; the first symbol information is symbol information that needs to be called that is screened out from all symbol information contained in the first basic library file; A second acquisition unit is used to acquire difference comparison data of the target operating system relative to the source operating system in the difference granularity of symbol information; the difference types include same, added, removed and changed; an evaluation and determination unit, configured to determine, based on the difference comparison data, whether the target operating system has removed and / or changed the first symbol information called by the business software for the first basic library file relative to the source operating system; if so, determining that the business software is incompatible with the target operating system; The difference comparison data at least includes a first difference comparison table whose difference granularity is the basic library file and a second difference comparison table whose difference granularity is the symbol information; the second difference comparison table is a statistical analysis of the symbol information differences in the basic library files that exist in both the source operating system and the target operating system and whose difference type is the change; The evaluation and determination unit is specifically used to determine whether there is a second basic library file with a difference type of removal and / or a third basic library file with a difference type of change in the first basic library file according to the first difference comparison table; if the second basic library file exists, it is determined that the business software is incompatible with the target operating system; if the third basic library file exists, it is determined according to the second difference comparison table whether there is second symbol information that is removed and / or changed in the first symbol information called for the third basic library file, and if so, it is determined that the business software is incompatible with the target operating system.

7. The device according to claim 6, characterized in that When the first acquisition unit executes the acquisition of binary files related to the business software in the source operating system, it specifically includes: traversing the process services currently running in the source operating system to obtain the binary files corresponding to each process service; filtering out the binary files executed by the source operating system basic services from the binary files corresponding to each process service obtained through the traversal to obtain the first binary file related to the business software.

8. The device according to claim 6 or 7, characterized in that When executing the step of obtaining the binary file related to the business software in the source operating system, the first obtaining unit specifically includes: obtaining the specified business software input by the user, and traversing the source operating system for the specified business software to obtain a second binary file corresponding to the specified business software.

9. The device according to claim 6, characterized in that The difference comparison data is generated in advance based on the software release package and software debugging package officially provided for the source operating system and the target operating system.

10. The device according to claim 6, characterized in that The device also includes: a warning determination unit, which is used to determine the rpm software package to which the second basic library file and / or the third basic library file belongs, and generate incompatible warning information according to the rpm software package to which they belong.

11. A computer device, characterized in that: The computer device includes a memory and a processor, the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory to implement the steps of any one of the methods described in claims 1-5.

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

13. A computer program product, characterized in that The method comprises a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 5.

Images