A version upgrading method and device, a storage medium and an electronic device

Abstract

Embodiments of the present application disclose a version upgrading method and device, a storage medium and an electronic device, comprising: obtaining an existing version and a to-be-upgraded version of each to-be-upgraded server in a monitoring system; for each to-be-upgraded server in the monitoring system, performing version upgrading verification on the current to-be-upgraded server according to the existing version and the to-be-upgraded version of the current to-be-upgraded server; when it is determined that all to-be-upgraded servers in the monitoring system pass the version upgrading verification, for each to-be-upgraded server in the monitoring system, performing version matching upgrading verification between the current to-be-upgraded server and other to-be-upgraded servers according to the existing version and the to-be-upgraded version of the current to-be-upgraded server; and when it is determined that all to-be-upgraded servers in the monitoring system pass the version matching upgrading verification, performing version upgrading on each to-be-upgraded server in the monitoring system. The embodiments of the present application can effectively improve the reliability of the monitoring system upgrading.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of data processing technology, and in particular to a version upgrade method, apparatus, storage medium and electronic device. Background Technology

[0002] With the development of the surveillance field, the products required for surveillance systems are becoming increasingly diverse, such as common central management servers, big data servers, intelligent servers, storage servers, video distribution servers, image distribution servers, and so on. Different types of servers need to work together; however, each server has its own independent version, yet they still need to be compatible with each other. Furthermore, users have different customization needs in different business scenarios. Therefore, the way various products in a surveillance system work together varies depending on the user.

[0003] Due to the aforementioned two demands, upgrading the server version in the monitoring system often encounters two types of problems: First, the upgraded version fails to include certain customized requirements from the user side, resulting in the unavailability of some functions after the upgrade; second, the upgraded version is incompatible with the versions of other products (servers) in the monitoring system, causing some functions to be unavailable. These problems not only decrease user satisfaction but also increase the manpower consumption for R&D and after-sales support. Summary of the Invention

[0004] This invention provides a version upgrade method, apparatus, storage medium, and electronic device, which can effectively avoid the problem of missing functions or incompatible product versions after the monitoring system is upgraded, resulting in the failure of some functions, and can greatly improve the reliability of the monitoring system upgrade.

[0005] In a first aspect, embodiments of the present invention provide a version upgrade method, including:

[0006] Obtain the current version and the version to be upgraded for each server in the monitoring system;

[0007] For each server in the monitoring system that needs to be upgraded, a version upgrade verification is performed on the server based on its current version and the version to be upgraded.

[0008] When it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification, for each server to be upgraded in the monitoring system, a version compatibility upgrade verification is performed between the current server to be upgraded and other servers to be upgraded, based on the current version and the version to be upgraded of the current server to be upgraded; wherein, the other servers to be upgraded are the servers to be upgraded in the monitoring system other than the current server to be upgraded.

[0009] When it is determined that all servers in the monitoring system that need to be upgraded have passed the version matching upgrade verification, the version upgrade is performed on each server in the monitoring system.

[0010] Secondly, embodiments of the present invention also provide a version upgrade device, comprising:

[0011] The version acquisition module is used to acquire the existing version and the version to be upgraded for each server in the monitoring system.

[0012] The version upgrade verification module is used to perform version upgrade verification on each server to be upgraded in the monitoring system based on the current version and the version to be upgraded.

[0013] The version matching upgrade verification module is used to perform version matching upgrade verification between the current server to be upgraded and other servers to be upgraded, based on the current version and the version to be upgraded of each server to be upgraded in the monitoring system when it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification. The other servers to be upgraded are the servers to be upgraded in the monitoring system other than the current server to be upgraded.

[0014] The version upgrade module is used to upgrade each server in the monitoring system when it is determined that all servers to be upgraded in the monitoring system have passed the version matching upgrade verification.

[0015] Thirdly, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the version upgrade method provided in embodiments of the present invention.

[0016] Fourthly, embodiments of the present invention provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the version upgrade method provided in embodiments of the present invention.

[0017] This invention provides a version upgrade scheme, which involves obtaining the existing version and the version to be upgraded of each server to be upgraded in a monitoring system; for each server to be upgraded in the monitoring system, performing a version upgrade verification based on the existing version and the version to be upgraded; when it is determined that all servers to be upgraded in the monitoring system pass the version upgrade verification, for each server to be upgraded in the monitoring system, performing a version compatibility upgrade verification between the current server to be upgraded and other servers to be upgraded, based on the existing version and the version to be upgraded; wherein, the other servers to be upgraded are the servers to be upgraded in the monitoring system other than the current server to be upgraded; when it is determined that all servers to be upgraded in the monitoring system pass the version compatibility upgrade verification, performing a version upgrade on each server to be upgraded in the monitoring system. The technical solution provided by this invention performs single-version upgrade verification and version compatibility upgrade verification between each server to be upgraded and other servers in the monitoring system before upgrading the monitoring system. When all servers to be upgraded in the monitoring system pass the single-version upgrade verification and version compatibility upgrade verification, the upgrade operation is then performed on each server in the monitoring system. This not only effectively avoids the problem of missing functions or incompatible product versions after the monitoring system is upgraded, which may lead to the failure of some functions, but also greatly improves the reliability of the monitoring system upgrade and saves manpower for later system maintenance. Attached Figure Description

[0018] Figure 1 This is a flowchart of a version upgrade method provided in an embodiment of the present invention;

[0019] Figure 2 This is a schematic diagram of the existing version and the version to be upgraded of the server in the monitoring system provided by an embodiment of the present invention;

[0020] Figure 3 This is a schematic diagram of the version iteration process of a central management server provided in an embodiment of the present invention;

[0021] Figure 4 This is a schematic diagram of the version iteration process of a big data server provided in an embodiment of the present invention;

[0022] Figure 5 This is a flowchart of a version upgrade method provided in another embodiment of the present invention;

[0023] Figure 6 This is a schematic diagram of a version upgrade device provided in another embodiment of the present invention;

[0024] Figure 7This is a schematic diagram of the structure of an electronic device according to another embodiment of the present invention. Detailed Implementation

[0025] Embodiments of the present invention will now be described in more detail with reference to the accompanying drawings. While some embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the invention. It should be understood that the accompanying drawings and embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the invention.

[0026] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0027] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0028] It should be noted that the concepts of "first" and "second" mentioned in this invention are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0029] It should be noted that the terms "a" and "a plurality of" used in this invention are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0030] The names of the messages or information exchanged between the multiple devices in the embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0031] Figure 1 This is a flowchart illustrating a version upgrade method according to an embodiment of the present invention. This embodiment is applicable to upgrading the versions of various servers to be upgraded in a monitoring system. The method can be executed by a version upgrade device, which can consist of hardware and / or software and is generally integrated into an electronic device. Figure 1 As shown, the method specifically includes the following steps:

[0032] Step 110: Obtain the current version and the version to be upgraded for each server in the monitoring system.

[0033] The monitoring system may include one or more servers to be upgraded. It should be noted that the embodiments of the present invention do not limit the number of servers to be upgraded in the monitoring system.

[0034] In this embodiment of the invention, the existing versions of each server to be upgraded in the monitoring system are obtained. For example, this can be done through the central management server in the monitoring system. The central management server is responsible for managing device and user information, as well as signaling interaction and scheduling of services; it serves as the command center for the entire monitoring system. For instance, the administrators of the monitoring system can store the versions of each server to be upgraded in a preset upgrade path and can read these versions from that path.

[0035] For example, the server to be upgraded in the monitoring system may include a central management server, a big data server, or other servers, wherein the big data server is the server used in the monitoring system to store image analysis data. Figure 2 This is a schematic diagram illustrating the existing version and the version to be upgraded of the server in a monitoring system provided by an embodiment of the present invention. For example... Figure 2 As shown, the current version of the central management server in the monitoring system is D001, and the version to be upgraded is D003; the current version of the big data server is D002SP20, and the version to be upgraded is D003SP01.

[0036] Step 120: For each server to be upgraded in the monitoring system, perform a version upgrade verification based on the current version and the version to be upgraded of the current server.

[0037] In this embodiment of the invention, for each server to be upgraded in the monitoring system, a single-version upgrade verification is performed on the server to be upgraded based on its existing version and the version to be upgraded. The server to be upgraded is any server in the monitoring system. For example, a single-version upgrade verification is performed on the central management server based on its existing version D001 and the version to be upgraded D003; and a single-version upgrade verification is performed on the big data server based on its existing version D002SP20 and the version to be upgraded D003SP01.

[0038] For example, based on the current version and the version to be upgraded of the server to be upgraded, a version upgrade verification is performed on the server to be upgraded, including: determining whether the current version of the server to be upgraded is the process version of the version to be upgraded; if not, determining the common and latest first target process version of the current version and the version to be upgraded; and performing a version upgrade verification on the server to be upgraded based on the current version, the version to be upgraded, and the first target process version. Optionally, when the current version of the server to be upgraded is the process version of the version to be upgraded, the server to be upgraded is determined to have passed the version upgrade verification.

[0039] If new code is merged into version B based on version A, then version A is the baseline version of version B; if version A is the baseline version of version B and version B is the baseline version of version C, then both version A and version B are process versions of version C.

[0040] In this embodiment of the invention, it is determined whether the current version of the server to be upgraded is the process version of the server to be upgraded. For example, this can be determined by checking the problem tickets of the current server to be upgraded in the problem ticket database. The problem ticket database includes problem tickets for each server in the monitoring system, and the problem tickets of the current server to be upgraded contain baseline version information for all versions involved in the current server to be upgraded. Therefore, a first baseline version of the server to be upgraded can be extracted from the problem tickets of the current server to be upgraded. It is then determined whether the first baseline version is the current version of the server to be upgraded. If yes, it indicates that the current version of the server to be upgraded is the process version of the server to be upgraded. If no, a second baseline version is further extracted, and it is determined whether the second baseline version is the baseline version of the first baseline version. If yes, it indicates that the current version of the server to be upgraded is the process version of the server to be upgraded. If no, a third baseline version is further extracted, where the third baseline version is the baseline version of the second baseline version. This process continues until the initial process version of the server to be upgraded has been determined.

[0041] In this embodiment of the invention, when the current version of the server to be upgraded is the process version of the version to be upgraded, it is determined that the server to be upgraded has passed the version upgrade verification. It can be understood that when the current version of the server to be upgraded is the process version of the version to be upgraded, it means that the version to be upgraded includes all the functions of the current version. Upgrading the server from its current version to the version to be upgraded will not result in the loss of the original functions of the server after the upgrade. Therefore, it can be determined that the server to be upgraded has passed the version upgrade verification. For example, Figure 3 This is a schematic diagram of the version iteration process of the central management server provided in an embodiment of the present invention. The problem form of the central management server is shown in the table below:

[0042] Serial Number Product Type Product version number Baseline version number 1 Central Management Server D003 D002 2 Central Management Server D002 D001 .. .. .. ..

[0043] according to Figure 3 As shown in the table above, the current version D001 of the central management server in the monitoring system is the process version of its upgrade to version D003. Therefore, the central management server has passed the version upgrade verification.

[0044] In this embodiment of the invention, when the existing version of the server to be upgraded is not the process version of the server to be upgraded, a common and latest first target process version is determined based on the issue form of the server to be upgraded. For example, when the existing version of the server to be upgraded is not the process version of the server to be upgraded, all first process versions of the existing version and all second process versions of the server to be upgraded are extracted from the issue form of the server to be upgraded. Then, from the first process versions and second process versions, the common and latest first target process version of the server to be upgraded is determined. This common and latest first target process version is the process version shared by both the existing version and the server to be upgraded, and is the closest to either the existing version or the server to be upgraded.

[0045] For example, Figure 4 This is a schematic diagram of the version iteration process of a big data server provided in an embodiment of the present invention. The problem form of the big data server is shown in the table below:

[0046] Serial Number Product Type Product version number Baseline version number 1 Big data server D003SP01 D003 2 Big data server D003 D002 3 Big data server D002SP20 D002 .. .. .. ..

[0047] according to Figure 4 As shown in the table above, the existing version D002SP20 and the version to be upgraded D003SP01 of the big data server share the same latest first target process version, which is D002.

[0048] In this embodiment of the invention, a version upgrade verification is performed on the server to be upgraded based on its existing version, the version to be upgraded, and the first target process version. Optionally, performing the version upgrade verification on the server to be upgraded based on its existing version, the version to be upgraded, and the first target process version includes: extracting a first incremental modification record of the existing version of the server to be upgraded relative to the first target process version; determining whether the first incremental modification record is included in the version to be upgraded or the process version of the version to be upgraded of the server to be upgraded; if so, the server to be upgraded is determined to have passed the version upgrade verification. Optionally, if the first incremental modification record is not included in the version to be upgraded of the server to be upgraded, and the first incremental modification record is not included in the process version of the version to be upgraded of the server to be upgraded, the server to be upgraded is determined to have failed the version upgrade verification.

[0049] For example, based on the issue ticket of the server to be upgraded, the first incremental modification record (i.e., the first incremental issue ticket) of the current version of the server to be upgraded relative to the first target process version is extracted. It is then determined whether all of the first incremental modification records are included in the version to be upgraded or the process version of the version to be upgraded of the current server to be upgraded. If so, it is determined that the server to be upgraded has passed the version upgrade verification. It can be understood that when the first incremental modification record is included in the version to be upgraded or its process version of the current server to be upgraded, it means that the version to be upgraded of the current server to be upgraded contains all the functions of the current version. Upgrading the current server to the version to be upgraded will not result in the loss of the original functions of the server after the upgrade. Therefore, it can be determined that the server to be upgraded has passed the version upgrade verification. Specifically, if the first incremental modification record is partially included in the version to be upgraded of the current server and partially included in the process version of the version to be upgraded, the current server to be upgraded can be determined to have passed the version upgrade verification. If the first incremental modification record is partially included in a certain process version of the version to be upgraded of the current server, and the other part is included in other process versions of the version to be upgraded, the current server to be upgraded can be determined to have passed the version upgrade verification. However, if the first incremental modification record is not included in the version to be upgraded of the current server, and the first incremental modification record is also not included in the process version of the version to be upgraded of the current server, it indicates that the version to be upgraded of the current server does not include all the functions of the existing version. If the current server to be upgraded is upgraded from its existing version to the version to be upgraded, it may result in the loss of the original functions of the server after the upgrade. In this case, the current server to be upgraded is determined to have failed the version upgrade verification.

[0050] For example, let's take a big data server as the current server to be upgraded as an example. Extract the first incremental modification record of the existing version D002SP20 of the big data server relative to the first target process version D002, that is, extract the first incremental modification record merged between the first target process version D002 and the existing version D002SP20 (i.e., the first incremental issue form). There can be one or multiple first incremental issue forms. When there are multiple first incremental issue forms, compare each one to determine whether all first incremental issue forms have been merged into the process version of the big data server to be upgraded, D003SP01 or D003SP01 (i.e., D003SP01, D003). If so, the big data server has passed the version upgrade verification; otherwise, the big data server has failed the version upgrade verification.

[0051] Step 130: When it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification, for each server to be upgraded in the monitoring system, according to the current version and the version to be upgraded, a version compatibility upgrade verification is performed between the current server to be upgraded and other servers to be upgraded; wherein, the other servers to be upgraded are the servers to be upgraded in the monitoring system other than the current server to be upgraded.

[0052] In this embodiment of the invention, when all servers to be upgraded in the monitoring system pass the single-version upgrade verification, it indicates that the upgraded servers will not experience any loss of original functionality. However, whether the upgraded servers can be used in conjunction with the existing versions is also an important issue to consider when upgrading the monitoring system. Therefore, when it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification, for each server to be upgraded in the monitoring system, a version compatibility upgrade verification is performed between the current server to be upgraded and other servers to be upgraded in the monitoring system, based on the current version and the version to be upgraded.

[0053] Optionally, based on the current version and the version to be upgraded of the server to be upgraded, a version compatibility upgrade verification is performed between the current server to be upgraded and other servers to be upgraded. This includes: obtaining a second target process version from the current version of the server to be upgraded to the version to be upgraded of the current server to be upgraded; obtaining the version to be upgraded of the current server to be upgraded and the second target process version, respectively, and a second incremental modification record for coordinating modifications with other servers to be upgraded; and performing a version compatibility upgrade verification between the current server to be upgraded and the target server to be upgraded based on the second incremental modification record, the current version of the target server to be upgraded involved in the second incremental modification record, and the version to be upgraded of the target server to be upgraded.

[0054] For a certain function of the monitoring system, both server A and server B need to be upgraded or modified together to ensure the normal operation of the monitoring system. In this case, a problem ticket is needed to ensure that server A and server B are modified together and reverted together (testing whether server A and server B have been modified successfully). This type of problem ticket is called a synchronization problem ticket.

[0055] For example, based on the issue ticket of the current server to be upgraded, all second target process versions from the current version of the server to be upgraded to its upgrade version are obtained. There can be one or more second target process versions; this embodiment of the invention does not limit the number of second target process versions. Incremental modification records of the upgrade version of the current server to be upgraded and the second target process version relative to their baseline versions are obtained, along with second incremental modification records (i.e., second synchronization issue tickets) modified in coordination with other servers to be upgraded in the monitoring system. Then, based on the second incremental modification records and the current version and the upgrade version of the target servers to be upgraded involved in the second incremental modification records, version compatibility upgrade verification is performed on the current server to be upgraded and the target server to be upgraded. The target server to be upgraded is the server in the monitoring system that needs to be modified in coordination with the incremental modification records of the upgrade version of the current server to be upgraded or the second target process version relative to its baseline version.

[0056] Optionally, based on the second incremental modification record, the existing version of the target server to be upgraded involved in the second incremental modification record, and the version to be upgraded of the target server to be upgraded, a version compatibility upgrade verification is performed between the current server to be upgraded and the target server to be upgraded, including: obtaining a third target process version from the existing version of the target server to be upgraded involved in the second incremental modification record to the version to be upgraded of the target server to be upgraded; determining whether the second incremental modification record is included in the version to be upgraded of the target server to be upgraded or the third target process version, and if so, determining that the current server to be upgraded passes the version compatibility upgrade verification with the target server to be upgraded.

[0057] For example, the target server to be upgraded involved in the second incremental modification record is determined. Based on the issue ticket of the target server to be upgraded, the current version of the target server to be upgraded and its third target process version to be upgraded are obtained. It is determined whether the second incremental modification record is included in the target server to be upgraded version or the third target process version. If so, it is determined that the current server to be upgraded has passed the version compatibility upgrade verification with the target server to be upgraded; otherwise, it is determined that the current server to be upgraded has not passed the version compatibility upgrade verification with the target server to be upgraded. It can be understood that when the second incremental modification record (i.e., the synchronization issue ticket) is included in the target server to be upgraded version or the third target process version, it means that after upgrading the current upgrade version server and the target server to be upgraded, the upgraded server version includes the matching synchronization issue ticket between the two, which can effectively ensure the normal compatibility use of the server after the upgrade. Therefore, it is determined that the current server to be upgraded has passed the version compatibility upgrade verification with the target server to be upgraded.

[0058] For example, taking the central management server as the current server to be upgraded, the second process version from the existing version D001 of the central management server to its upgrade version D003 is D002. The incremental modification records of the upgrade version D003 and the second target process version D002 of the central management server relative to their respective baseline versions are obtained, along with the second incremental modification records (i.e., the second synchronization issue tickets) modified in coordination with other servers to be upgraded in the monitoring system. For example, if the upgrade version D003 of the central management server incorporates a function A relative to its baseline version, the corresponding incremental modification record is issue ticket M12222. This issue ticket M12222 only involves the synchronization modification of the big data server in the monitoring system. The synchronization issue ticket (i.e., the second incremental modification record for coordinated modification) between the upgrade version D003 of the central management server and the big data server is D10232. In this embodiment of the invention, the synchronization problem form D10232 involving the central management server's upgrade version D003 and the big data server involves a target upgrade server, which is a big data server. The third target process version of the big data server from its existing version D002SP20 to its upgrade version D003SP01 is D003. It is determined whether the synchronization problem form D10232 is included in the big data server's upgrade version D003SP01 or the third target process version D003. If so, it indicates that the version compatibility upgrade verification between the central management server and the big data server has passed; otherwise, it indicates that the version compatibility upgrade verification between the central management server and the big data server has failed.

[0059] Step 140: When it is determined that all servers to be upgraded in the monitoring system have passed the version matching upgrade verification, the version of each server to be upgraded in the monitoring system is upgraded.

[0060] In this embodiment of the invention, when it is determined that all servers to be upgraded in the monitoring system have passed the version matching upgrade verification, each server to be upgraded in the monitoring system is upgraded from its existing version to the corresponding version to be upgraded.

[0061] Optionally, if at least one server in the monitoring system fails the version upgrade verification, or if at least one server in the monitoring system fails the version matching upgrade verification, version upgrades for each server in the monitoring system shall be prohibited.

[0062] This invention provides a version upgrade method, which involves obtaining the existing version and the version to be upgraded of each server to be upgraded in a monitoring system; for each server to be upgraded in the monitoring system, performing a version upgrade verification based on the existing version and the version to be upgraded; when it is determined that all servers to be upgraded in the monitoring system pass the version upgrade verification, performing a version compatibility upgrade verification between the current server to be upgraded and other servers to be upgraded, based on the existing version and the version to be upgraded; wherein, the other servers to be upgraded are the servers to be upgraded in the monitoring system other than the current server to be upgraded; when it is determined that all servers to be upgraded in the monitoring system pass the version compatibility upgrade verification, performing a version upgrade on each server to be upgraded in the monitoring system. The technical solution provided by this invention performs single-version upgrade verification and version compatibility upgrade verification between each server to be upgraded and other servers in the monitoring system before upgrading the monitoring system. When all servers to be upgraded in the monitoring system pass the single-version upgrade verification and version compatibility upgrade verification, the upgrade operation is then performed on each server in the monitoring system. This not only effectively avoids the problem of missing functions or incompatible product versions after the monitoring system is upgraded, which may lead to the failure of some functions, but also greatly improves the reliability of the monitoring system upgrade and saves manpower for later system maintenance.

[0063] Figure 5 A flowchart of a version upgrade method provided in another embodiment of the present invention is shown below. Figure 5 As shown, the method specifically includes the following steps:

[0064] Step 510: Obtain the current version and the version to be upgraded for each server in the monitoring system.

[0065] Step 520: For each server to be upgraded in the monitoring system, determine whether the current version of the server to be upgraded is the process version of the server to be upgraded. If yes, proceed to step 560; otherwise, proceed to step 530.

[0066] Step 530: Determine the latest first target process version that is common to both the existing version and the version to be upgraded on the server to be upgraded.

[0067] Step 540: Extract the first incremental modification record of the current version of the server to be upgraded relative to the first target process version.

[0068] Step 550: Determine whether the first incremental modification record is included in the upgrade version of the current server to be upgraded or the process version of the upgrade version of the current server to be upgraded. If yes, proceed to step 560; otherwise, proceed to step 570.

[0069] Step 560: Confirm that the server to be upgraded has passed the version upgrade verification.

[0070] Step 570: Determine that the server to be upgraded has failed the version upgrade verification.

[0071] Step 580: Determine whether all servers to be upgraded in the monitoring system have passed the version upgrade verification. If so, proceed to step 590; otherwise, proceed to step 5170.

[0072] Step 590: For each server to be upgraded in the monitoring system, obtain the second target process version from the current version of the server to be upgraded to the version to be upgraded.

[0073] Step 5100: Obtain the upgrade version and the second target process version of the current server to be upgraded, as well as the second incremental modification record modified in conjunction with other servers to be upgraded.

[0074] Step 5110: Obtain the third target process version from the existing version of the target server to be upgraded to the version to be upgraded of the target server involved in the second incremental modification record.

[0075] Step 5120: Determine whether the second incremental modification record is included in the version to be upgraded of the target server or the third target process version. If yes, proceed to step 5130; otherwise, proceed to step 5140.

[0076] Step 5130: Determine if the current server to be upgraded passes the version compatibility upgrade verification with the target server to be upgraded.

[0077] Step 5140: Determine that the current server to be upgraded has failed the version compatibility upgrade verification with the target server to be upgraded.

[0078] Step 5150: Determine whether all servers to be upgraded in the monitoring system have passed the version matching upgrade verification. If so, proceed to step 5160; otherwise, proceed to step 5170.

[0079] Step 5160: Upgrade the versions of each server in the monitoring system that needs to be upgraded.

[0080] Step 5170: Prohibit version upgrades for the servers in the monitoring system that are to be upgraded.

[0081] The version upgrade method provided in this invention performs single-version upgrade verification and version compatibility upgrade verification between each server to be upgraded and other servers in the monitoring system before upgrading the monitoring system. When all servers to be upgraded in the monitoring system pass the single-version upgrade verification and version compatibility upgrade verification, the upgrade operation is then performed on each server in the monitoring system. This not only effectively avoids the problem of missing functions or incompatible product versions after the monitoring system is upgraded, which may lead to the failure of some functions, but also greatly improves the reliability of the monitoring system upgrade and saves manpower for later system maintenance.

[0082] Figure 6 This is a schematic diagram of a version upgrade device provided in another embodiment of the present invention. Figure 6 As shown, the device includes: a version acquisition module 610, a version upgrade verification module 620, a version matching upgrade verification module 630, and a version upgrade module 640. Among them,

[0083] Version acquisition module 610 is used to acquire the existing version and the version to be upgraded of each server to be upgraded in the monitoring system;

[0084] The version upgrade verification module 620 is used to perform version upgrade verification on each server to be upgraded in the monitoring system based on the existing version and the version to be upgraded.

[0085] The version matching upgrade verification module 630 is used to perform version matching upgrade verification between the current server to be upgraded and other servers to be upgraded, based on the existing version and the version to be upgraded of each server to be upgraded in the monitoring system when it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification; wherein, the other servers to be upgraded are the servers to be upgraded in the monitoring system other than the current server to be upgraded.

[0086] The version upgrade module 640 is used to upgrade each server to be upgraded in the monitoring system when it is determined that all servers to be upgraded in the monitoring system have passed the version matching upgrade verification.

[0087] This invention provides a version upgrade device that acquires the existing version and the version to be upgraded of each server to be upgraded in a monitoring system; for each server to be upgraded in the monitoring system, a version upgrade verification is performed on the current server to be upgraded based on its existing version and the version to be upgraded; when it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification, a version compatibility upgrade verification is performed between the current server to be upgraded and other servers to be upgraded, based on their existing versions and the version to be upgraded; wherein, the other servers to be upgraded are the servers to be upgraded in the monitoring system other than the current server to be upgraded; when it is determined that all servers to be upgraded in the monitoring system have passed the version compatibility upgrade verification, a version upgrade is performed on each server to be upgraded in the monitoring system. The technical solution provided by this invention performs single-version upgrade verification and version compatibility upgrade verification between each server to be upgraded and other servers in the monitoring system before upgrading the monitoring system. When all servers to be upgraded in the monitoring system pass the single-version upgrade verification and version compatibility upgrade verification, the upgrade operation is then performed on each server in the monitoring system. This not only effectively avoids the problem of missing functions or incompatible product versions after the monitoring system is upgraded, which may lead to the failure of some functions, but also greatly improves the reliability of the monitoring system upgrade and saves manpower for later system maintenance.

[0088] Optionally, the version upgrade verification module includes:

[0089] The version determination unit is used to determine whether the current version of the server to be upgraded is the process version of the server to be upgraded.

[0090] The first process version determination unit is used to determine, if not, the latest first target process version that is common to both the existing version and the version to be upgraded of the current server to be upgraded.

[0091] The version upgrade verification unit is used to perform version upgrade verification on the server to be upgraded based on the existing version, the version to be upgraded, and the first target process version.

[0092] Optionally, the version upgrade verification unit is used for:

[0093] Extract the first incremental modification record of the existing version of the current server to be upgraded relative to the first target process version;

[0094] Determine whether the first incremental modification record is included in the upgrade version of the current server to be upgraded or the process version of the upgrade version of the current server to be upgraded. If so, determine that the current server to be upgraded has passed the version upgrade verification.

[0095] Optionally, the device further includes:

[0096] The verification failure determination unit is used to determine that the current server to be upgraded has failed the version upgrade verification when the first incremental modification record is not included in the version to be upgraded of the current server to be upgraded, and the first incremental modification record is not included in the process version of the version to be upgraded of the current server to be upgraded.

[0097] Optionally, the device further includes:

[0098] The verification pass determination unit is used to determine that the current server to be upgraded has passed the version upgrade verification when the existing version of the current server to be upgraded is the process version of the current server to be upgraded.

[0099] Optionally, the version upgrade verification module includes:

[0100] The second process version determination unit is used to obtain the second target process version from the existing version of the server to be upgraded to the version to be upgraded of the server to be upgraded.

[0101] The second incremental modification record acquisition unit is used to acquire the upgrade version of the current server to be upgraded and the second target process version, and the second incremental modification record modified in cooperation with other servers to be upgraded.

[0102] The version matching upgrade verification unit is used to perform version matching upgrade verification between the current server to be upgraded and the target server to be upgraded based on the second incremental modification record, the existing version of the target server to be upgraded involved in the second incremental modification record, and the version to be upgraded of the target server to be upgraded.

[0103] Optionally, the version upgrade verification unit is used for:

[0104] Obtain the existing version of the target server to be upgraded involved in the second incremental modification record, and the third target process version of the target server to be upgraded.

[0105] Determine whether the second incremental modification record is included in the upgrade version of the target server to be upgraded or the third target process version. If so, determine whether the current server to be upgraded has passed the version compatibility upgrade verification with the target server to be upgraded.

[0106] Optionally, the device further includes:

[0107] The matching verification failure determination unit is used to determine that the current server to be upgraded has failed the version matching upgrade verification with the target server to be upgraded when the second incremental modification record is not included in the version to be upgraded of the target server to be upgraded, and the second incremental modification record is not included in the third target process version.

[0108] Optional, also includes:

[0109] The version upgrade prohibition module is used to prohibit version upgrades for each server to be upgraded in the monitoring system when at least one server to be upgraded in the monitoring system fails the version upgrade verification, or when at least one server to be upgraded in the monitoring system fails the version-related upgrade verification.

[0110] The above-described apparatus can execute the methods provided in all the foregoing embodiments of the present invention, and has the corresponding functional modules and beneficial effects for executing the above methods. Technical details not described in detail in the embodiments of the present invention can be found in the methods provided in all the foregoing embodiments of the present invention.

[0111] This invention also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the version upgrade method provided in this invention.

[0112] Storage medium – any type of memory device or storage device. The term “storage medium” is intended to include: mounting media, such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory, such as DRAM, DDRRAM, SRAM, EDORAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (e.g., hard disks or optical storage); registers or other similar types of memory elements, etc. Storage medium may also include other types of memory or combinations thereof. Furthermore, storage medium may reside in a first computer system in which the program is executed, or it may reside in a different second computer system connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term “storage medium” can include two or more storage media that may reside in different locations (e.g., in different computer systems connected via a network). Storage medium may store program instructions (e.g., specifically implemented as a computer program) executable by one or more processors.

[0113] Of course, the computer-executable instructions provided in the embodiments of the present invention are not limited to the version upgrade operation described above, but can also perform related operations in the version upgrade method provided in any embodiment of the present invention.

[0114] This invention provides an electronic device that can integrate a version upgrade device provided in this invention. Figure 7 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. The electronic device 700 may include: a memory 701, a processor 702, and a computer program stored in the memory 701 and executable on the processor. When the processor 702 executes the computer program, it implements the version upgrade method as described in the embodiment of the present invention.

[0115] The electronic device provided in this embodiment of the invention acquires the existing version and the version to be upgraded of each server to be upgraded in the monitoring system; for each server to be upgraded in the monitoring system, a version upgrade verification is performed on the current server to be upgraded based on its existing version and the version to be upgraded; when it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification, a version compatibility upgrade verification is performed between the current server to be upgraded and other servers to be upgraded based on their existing versions and the version to be upgraded; wherein, the other servers to be upgraded are the servers to be upgraded in the monitoring system other than the current server to be upgraded; when it is determined that all servers to be upgraded in the monitoring system have passed the version compatibility upgrade verification, a version upgrade is performed on each server to be upgraded in the monitoring system. The technical solution provided by this invention performs single-version upgrade verification and version compatibility upgrade verification between each server to be upgraded and other servers in the monitoring system before upgrading the monitoring system. When all servers to be upgraded in the monitoring system pass the single-version upgrade verification and version compatibility upgrade verification, the upgrade operation is then performed on each server in the monitoring system. This not only effectively avoids the problem of missing functions or incompatible product versions after the monitoring system is upgraded, which may lead to the failure of some functions, but also greatly improves the reliability of the monitoring system upgrade and saves manpower for later system maintenance.

[0116] The version upgrade device, storage medium, and electronic device provided in the above embodiments can execute the version upgrade method provided in any embodiment of the present invention, and have the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in the above embodiments can be found in the version upgrade method provided in any embodiment of the present invention.

[0117] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A version upgrade method characterized by comprising: include: Obtain the current version and the version to be upgraded for each server in the monitoring system; For each server in the monitoring system that needs to be upgraded, a version upgrade verification is performed on the server based on its current version and the version to be upgraded; wherein, the version upgrade verification is used to reflect whether the original functions are missing after the server is upgraded. When it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification, for each server to be upgraded in the monitoring system, a version compatibility upgrade verification is performed between the current server to be upgraded and other servers to be upgraded, based on the current version and the version to be upgraded. The other servers to be upgraded are those servers in the monitoring system other than the current server to be upgraded. The version compatibility upgrade verification is used to reflect whether the upgraded current server to be upgraded can be used in conjunction with the other servers to be upgraded. When it is determined that all servers to be upgraded in the monitoring system have passed the version matching upgrade verification, the version upgrade is performed on each server to be upgraded in the monitoring system. Specifically, based on the current version and the version to be upgraded of the server to be upgraded, a version upgrade verification is performed on the server to be upgraded, including: Determine whether the current version of the server to be upgraded is the process version of the server to be upgraded. If not, then determine the current version of the server to be upgraded and the latest version of the first target process that is common to both the existing version and the version to be upgraded. Based on the current version of the server to be upgraded, the version to be upgraded, and the first target process version, a version upgrade verification is performed on the server to be upgraded. Specifically, based on the current version of the server to be upgraded, the version to be upgraded, and the first target process version, a version upgrade verification is performed on the server to be upgraded, including: Extract the first incremental modification record of the existing version of the current server to be upgraded relative to the first target process version; Determine whether the first incremental modification record is included in the upgrade version of the current server to be upgraded or the process version of the upgrade version of the current server to be upgraded. If so, determine that the current server to be upgraded has passed the version upgrade verification.

2. The method according to claim 1, characterized in that, Also includes: When the first incremental modification record is not included in the upgrade version of the current server to be upgraded, and the first incremental modification record is not included in the process version of the upgrade version of the current server to be upgraded, it is determined that the current server to be upgraded has failed the version upgrade verification.

3. The method according to any one of claims 1-2, characterized in that, Also includes: When the current version of the server to be upgraded is the process version of the server to be upgraded, it is determined that the server to be upgraded has passed the version upgrade verification.

4. The method according to claim 1, characterized in that, Based on the current version and the version to be upgraded of the server to be upgraded, a version compatibility upgrade verification is performed between the current server to be upgraded and other servers to be upgraded, including: Obtain the existing version of the server to be upgraded to the second target process version of the server to be upgraded; Obtain the upgrade version of the current server to be upgraded and the second target process version, as well as the second incremental modification record for modification in conjunction with other servers to be upgraded; Based on the second incremental modification record, the existing version of the target server to be upgraded involved in the second incremental modification record, and the version to be upgraded of the target server to be upgraded, a version compatibility upgrade verification is performed between the current server to be upgraded and the target server to be upgraded.

5. The method according to claim 4, characterized in that, Based on the second incremental modification record, the existing version of the target server to be upgraded involved in the second incremental modification record, and the version to be upgraded of the target server to be upgraded, a version compatibility upgrade verification is performed between the current server to be upgraded and the target server to be upgraded, including: Obtain the existing version of the target server to be upgraded involved in the second incremental modification record, and the third target process version of the target server to be upgraded. Determine whether the second incremental modification record is included in the upgrade version of the target server to be upgraded or the third target process version. If so, determine whether the current server to be upgraded has passed the version compatibility upgrade verification with the target server to be upgraded.

6. The method according to claim 5, characterized in that, Also includes: When the second incremental modification record is not included in the upgrade version of the target server to be upgraded, and the second incremental modification record is not included in the third target process version, it is determined that the current server to be upgraded has not passed the version compatibility upgrade verification with the target server to be upgraded.

7. The method according to claim 1, characterized in that, Also includes: When at least one server in the monitoring system fails the version upgrade verification, or when at least one server in the monitoring system fails the version-matching upgrade verification, version upgrades for each server in the monitoring system are prohibited.

8. A version upgrade device, characterized in that, include: The version acquisition module is used to acquire the existing version and the version to be upgraded for each server in the monitoring system. The version upgrade verification module is used to perform version upgrade verification on each server to be upgraded in the monitoring system, based on the current version and the version to be upgraded. The version upgrade verification is used to reflect whether the original functions are missing after the server is upgraded. The version compatibility upgrade verification module is used to perform version compatibility upgrade verification between the current server to be upgraded and other servers to be upgraded, based on the current version and the version to be upgraded, when it is determined that all servers to be upgraded in the monitoring system have passed the version upgrade verification. The other servers to be upgraded are those in the monitoring system other than the current server to be upgraded. The version compatibility upgrade verification is used to reflect whether the upgraded current server to be upgraded can be used in conjunction with the other servers to be upgraded. The version upgrade module is used to upgrade each server to be upgraded in the monitoring system when it is determined that all servers to be upgraded in the monitoring system have passed the version matching upgrade verification. The version upgrade verification module includes: The version determination unit is used to determine whether the current version of the server to be upgraded is the process version of the server to be upgraded. The first process version determination unit is used to determine, if not, the latest first target process version that is common to both the existing version and the version to be upgraded of the current server to be upgraded. The version upgrade verification unit is used to perform version upgrade verification on the server to be upgraded based on the existing version, the version to be upgraded, and the first target process version. The version upgrade verification unit is used for: Extract the first incremental modification record of the existing version of the current server to be upgraded relative to the first target process version; Determine whether the first incremental modification record is included in the upgrade version of the current server to be upgraded or the process version of the upgrade version of the current server to be upgraded. If so, determine that the current server to be upgraded has passed the version upgrade verification.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processing device, it implements the version upgrade method as described in any one of claims 1-7.

10. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the version upgrade method as described in any one of claims 1-7.

Images