Load balancing software patch upgrade and rollback method, device, equipment and medium

Abstract

The present application discloses a method, device, equipment and medium for patch upgrade and rollback of load balancing software, which relates to the field of computer technology, including determining the type of execution command; if it is a patch upgrade, judging whether there is a patch installation package corresponding to the execution command, if it exists, performing a legitimacy check on the patch installation package, and if the legitimacy check passes, performing a patch upgrade on the load balancing software using the patch installation package, and generating a patch upgrade log; if it is a patch rollback, judging whether the status of the patch installation package corresponding to the execution command is upgraded, and if it is upgraded, performing a dependency check on the upgraded patch installation package, and if the dependency check passes, performing a patch rollback on the load balancing software using the upgraded patch installation package, modifying the configuration file of the load balancing software, and generating a patch rollback log. The present application can ensure the security and reliability of the load balancing software patch upgrade and rollback, and improve the efficiency of the load balancing software patch upgrade and rollback.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a load balancing software patch upgrade and rollback method, device, equipment and medium. Background Art

[0002] Load balancing software is used as a Web (World Wide Web) server. With the update of technology, the functions of the load balancing software will be upgraded or increased. At present, the patch upgrade of load balancing software usually adopts the method of backing up the original binary files as a whole. During the upgrade process, the new version of the binary file is used to overwrite the corresponding files of the original load balancing software. When the patch needs to be rolled back, the backup content will be overwritten as a whole. However, this traditional upgrade method has some problems, which makes the upgrade process complicated and inefficient; in addition, this traditional upgrade method may cause the upgrade to fail because the original binary files are not released correctly. At the same time, there is a potential risk in backing up the original binary files, which may damage the original files, making it difficult to roll back to the original version, and may even cause the load balancing software to fail to start normally.

[0003] As can be seen from the above, how to ensure the security and reliability of load balancing software patch upgrades and rollbacks and improve the efficiency of load balancing software patch upgrades and rollbacks are issues to be resolved in the art. Summary of the invention

[0004] In view of this, the purpose of the present invention is to provide a load balancing software patch upgrade and rollback method, device, equipment and medium, which can ensure the security and reliability of load balancing software patch upgrade and rollback, and improve the efficiency of load balancing software patch upgrade and rollback. The specific scheme is as follows:

[0005] In a first aspect, the present application discloses a load balancing software patch upgrade and rollback method, comprising:

[0006] Obtaining an execution command for the load balancing software sent by the user end, and determining the type of the execution command;

[0007] If the type is patch upgrade, determine whether there is a patch installation package corresponding to the execution command locally; if there is a patch installation package corresponding to the execution command locally, perform a legitimacy check on the patch installation package; if the legitimacy check passes, use the patch installation package to perform a patch upgrade on the load balancing software, and generate a patch upgrade log;

[0008] If the type is patch rollback, determine whether the status of the patch installation package corresponding to the execution command in the local area is upgraded; if the status of the patch installation package corresponding to the execution command is upgraded, perform dependency detection on the upgraded patch installation package; if the dependency detection passes, use the upgraded patch installation package to perform patch rollback on the load balancing software, and modify the configuration file of the load balancing software to generate a patch rollback log.

[0009] Optionally, obtaining an execution command for the load balancing software sent by the user terminal and determining a type of the execution command includes:

[0010] Obtaining the execution command for the load balancing software sent by the user terminal, and performing a correctness check on the parameters in the execution command;

[0011] If the correctness check passes, determining the type of the execution command based on the parameter type corresponding to the parameter;

[0012] If the correctness check fails, a parameter error prompt message is generated and the parameter error prompt message is recorded in a local log file.

[0013] Optionally, the load balancing software patch upgrade and rollback method further includes:

[0014] Obtain a patch installation package, and save the patch installation package to a preset patch directory; the patch installation package includes a binary file to be upgraded and a patch manual;

[0015] If the type of the execution command is to display the patch installation package, then the patch installation package in the patch directory is displayed;

[0016] If the type of the execution command is patch upgrade record viewing, the patch upgrade record is determined from the local log file so that the user terminal can view the patch upgrade record.

[0017] Optionally, after determining whether a patch installation package corresponding to the execution command exists locally, the method further includes:

[0018] If the patch installation package corresponding to the execution command does not exist locally, it is determined that the patch upgrade fails, and patch upgrade failure information is generated;

[0019] The patch upgrade failure information is saved in a local log file, and a patch upgrade failure prompt is sent to the user terminal.

[0020] Optionally, the performing a validity check on the patch installation package includes:

[0021] The patch installation package is respectively subjected to availability check, consistency check and security check; the availability check includes a patch package basic version dependency check; the consistency check includes a patch package name check; the security check includes a patch package decryption check.

[0022] Optionally, performing dependency detection on the upgraded patch installation package, and if the dependency detection passes, using the upgraded patch installation package to perform patch rollback on the load balancing software includes:

[0023] Determine whether the upgraded patch installation package has a dependency relationship;

[0024] If the upgraded patch installation package does not have a dependency relationship, it is determined that the dependency detection is passed, and the load balancing software is patch rolled back using the upgraded patch installation package;

[0025] If the upgraded patch installation package has dependencies, it is determined that the dependency detection fails, patch rollback failure information is generated, the patch rollback failure information is saved to a local log file, and a patch rollback failure prompt is sent to the user terminal.

[0026] Optionally, the step of rolling back the load balancing software patch by using the upgraded patch installation package and modifying the configuration file of the load balancing software includes:

[0027] Use the upgraded patch installation package to roll back the load balancing software patch and perform a correctness check on the configuration file of the load balancing software;

[0028] If the correctness check fails, the configuration content in the configuration file is automatically modified.

[0029] In a second aspect, the present application discloses a load balancing software patch upgrade and rollback device, comprising:

[0030] A command acquisition module, used to acquire an execution command for the load balancing software sent by the user end, and determine the type of the execution command;

[0031] A patch upgrade module, for determining whether a patch installation package corresponding to the execution command exists locally if the type is a patch upgrade; if a patch installation package corresponding to the execution command exists locally, performing a legitimacy check on the patch installation package; if the legitimacy check passes, performing a patch upgrade on the load balancing software using the patch installation package, and generating a patch upgrade log;

[0032] A patch rollback module is used to determine whether the status of the patch installation package corresponding to the execution command in the local area is upgraded if the type is patch rollback; if the status of the patch installation package corresponding to the execution command is upgraded, a dependency check is performed on the upgraded patch installation package; if the dependency check passes, the upgraded patch installation package is used to perform a patch rollback on the load balancing software, and the configuration file of the load balancing software is modified to generate a patch rollback log.

[0033] In a third aspect, the present application discloses an electronic device, comprising:

[0034] Memory, used to store computer programs;

[0035] The processor is used to execute the computer program to implement the aforementioned load balancing software patch upgrade and rollback method.

[0036] In a fourth aspect, the present application discloses a computer storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the aforementioned disclosed load balancing software patch upgrade and rollback method are implemented.

[0037] It can be seen that the present application provides a load balancing software patch upgrade and rollback method, including obtaining an execution command for the load balancing software sent by the user end, and determining the type of the execution command; if the type is a patch upgrade, then determining whether there is a patch installation package corresponding to the execution command locally, if there is a patch installation package corresponding to the execution command locally, then performing a legitimacy check on the patch installation package, if the legitimacy check passes, then performing a patch upgrade on the load balancing software using the patch installation package, and generating a patch upgrade log; if the type is a patch rollback, then determining whether the status of the patch installation package corresponding to the execution command locally is upgraded, if the status of the patch installation package corresponding to the execution command is upgraded, then performing a dependency check on the upgraded patch installation package, if the dependency check passes, then performing a patch rollback on the load balancing software using the upgraded patch installation package, and modifying the configuration file of the load balancing software to generate a patch rollback log. The present application determines whether to perform a patch upgrade or patch rollback on the load balancing software by executing a command type, thereby avoiding the hidden dangers caused by manually replacing the product package. If it is a patch upgrade, it determines whether a patch installation package exists and performs a legitimacy check. If the legitimacy check passes, a patch upgrade log is generated to ensure the reversibility of the patch upgrade operation. During the patch rollback process, the dependency of the patch installation package is intelligently detected. If the dependency detection passes, the patch is rolled back and the configuration file is modified to ensure the correctness of the relevant configuration of the load balancing software and generate a patch rollback log so that the version can be rolled back quickly and reliably when needed, thereby ensuring the security and reliability of the load balancing software patch upgrade and rollback, and also improving the efficiency of the load balancing software patch upgrade and rollback. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] 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 only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0039] Figure 1 A flow chart of a load balancing software patch upgrade and rollback method disclosed in this application;

[0040] Figure 2 This is a flow chart of another load balancing software patch upgrade and rollback method disclosed in this application;

[0041] Figure 3 A specific flow chart of a load balancing software patch upgrade and rollback method disclosed in this application;

[0042] Figure 4 A schematic diagram of the structure of a load balancing software patch upgrade and rollback device disclosed in this application;

[0043] Figure 5 A structural diagram of an electronic device provided for this application. DETAILED DESCRIPTION

[0044] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0045] Load balancing software is used as a Web (World Wide Web, global wide area network) server. With the update of technology, the functions of the load balancing software will be upgraded or increased. At present, the patch upgrade of the load balancing software usually adopts the method of backing up the original binary class files as a whole. During the upgrade process, the new version of the binary file is used to overwrite the corresponding files of the original load balancing software. When the patch needs to be rolled back, the backup content will be overwritten as a whole. However, this traditional upgrade method has some problems, which makes the upgrade process complicated and inefficient; in addition, this traditional upgrade method may cause the upgrade to fail because the original binary class files are not released correctly. At the same time, there are potential risks in backing up the original binary class files, which may damage the original files, making it difficult to roll back to the original version, and may even cause the load balancing software to fail to start normally. As can be seen from the above, how to ensure the security and reliability of the load balancing software patch upgrade and rollback, and improve the efficiency of the load balancing software patch upgrade and rollback are problems to be solved in this field.

[0046] See also Figure 1 As shown, the embodiment of the present invention discloses a load balancing software patch upgrade and rollback method, which may specifically include:

[0047] Step S11: Obtaining an execution command for the load balancing software sent by the user end, and determining the type of the execution command.

[0048] In this embodiment, the execution command sent by the user end to the load balancing software is obtained, and the parameters in the execution command are checked for correctness; if the correctness check passes, the type of the execution command is determined based on the parameter type corresponding to the parameter; if the correctness check fails, a parameter error prompt message is generated, and the parameter error prompt message is recorded in a local log file. Specifically, the present application determines the correctness of the parameters in the execution command through the parameter information configured by the user. If the parameter information is incorrect, an error message prompt will be given and the error message will be recorded in a log file; when the parameter information is correct, the parameter information type will be determined, and the type of the execution command will be determined according to the parameter information type.

[0049] In this embodiment, it also includes: obtaining a patch installation package, saving the patch installation package to a preset patch directory; the patch installation package includes the binary file to be upgraded and the patch manual; if the type of the execution command is to display the patch installation package, then the patch installation package in the patch directory is displayed; if the type of the execution command is to view the patch upgrade record, then the patch upgrade record is determined from the local log file so that the user terminal can view the patch upgrade record. Specifically, the patch installation package includes the binary file to be upgraded and the patch manual; the patch installation package is stored in the preset patch directory, and commands are used to perform patch upgrade operations, patch rollback operations, display patch installation packages, and view patch upgrade records on the patch installation package.

[0050] Step S12: If the type is patch upgrade, determine whether there is a patch installation package corresponding to the execution command locally. If there is a patch installation package corresponding to the execution command locally, perform a legitimacy check on the patch installation package. If the legitimacy check passes, use the patch installation package to perform a patch upgrade on the load balancing software and generate a patch upgrade log.

[0051] In this embodiment, after determining whether there is a patch installation package corresponding to the execution command locally, it also includes: if there is no patch installation package corresponding to the execution command locally, determining that the patch upgrade has failed, and generating patch upgrade failure information; saving the patch upgrade failure information to a local log file, and sending a patch upgrade failure prompt to the user terminal.

[0052] In addition, the uploaded patch installation package will be parsed to obtain the patch installation package version information and distinguish whether the patch installation package has been upgraded, so as to facilitate the patch upgrade of the load balancing software.

[0053] Step S13: If the type is patch rollback, determine whether the status of the patch installation package corresponding to the execution command in the local area is upgraded; if the status of the patch installation package corresponding to the execution command is upgraded, perform dependency detection on the upgraded patch installation package; if the dependency detection passes, use the upgraded patch installation package to perform patch rollback on the load balancing software, and modify the configuration file of the load balancing software to generate a patch rollback log.

[0054] In this embodiment, if the dependency detection passes, the load balancing software is patched and rolled back using the upgraded patch installation package, and the configuration file of the load balancing software is checked for correctness; if the correctness detection fails, the configuration content in the configuration file is automatically modified.

[0055] This application generates log records after patch upgrades and patch rollbacks. The patch upgrade log can be used to track the version information of the load balancing software. If there is a problem with the upgrade, you may need to roll back to the previous version so that you can roll back the version quickly and reliably when needed.

[0056] In this embodiment, an execution command for the load balancing software sent by the user end is obtained, and the type of the execution command is determined; if the type is a patch upgrade, it is determined whether a patch installation package corresponding to the execution command exists locally; if the patch installation package corresponding to the execution command exists locally, a legitimacy check is performed on the patch installation package; if the legitimacy check passes, the load balancing software is patch upgraded using the patch installation package, and a patch upgrade log is generated; if the type is a patch rollback, it is determined whether the status of the patch installation package corresponding to the execution command in the local area is upgraded; if the status of the patch installation package corresponding to the execution command is upgraded, a dependency check is performed on the upgraded patch installation package; if the dependency check passes, the load balancing software is patch rolled back using the upgraded patch installation package, and the configuration file of the load balancing software is modified to generate a patch rollback log. The present application determines whether to perform a patch upgrade or patch rollback on the load balancing software by executing a command type, thereby avoiding the hidden dangers caused by manually replacing the product package. If it is a patch upgrade, it determines whether a patch installation package exists and performs a legitimacy check. If the legitimacy check passes, a patch upgrade log is generated to ensure the reversibility of the patch upgrade operation. During the patch rollback process, the dependency of the patch installation package is intelligently detected. If the dependency detection passes, the patch is rolled back and the configuration file is modified to ensure the correctness of the relevant configuration of the load balancing software and generate a patch rollback log so that the version can be rolled back quickly and reliably when needed, thereby ensuring the security and reliability of the load balancing software patch upgrade and rollback, and also improving the efficiency of the load balancing software patch upgrade and rollback.

[0057] See also Figure 2 As shown, the embodiment of the present invention discloses a load balancing software patch upgrade and rollback method, which may specifically include:

[0058] Step S21: Obtaining an execution command for the load balancing software sent by the user end, and determining the type of the execution command.

[0059] Step S22: If the type is patch upgrade, determine whether there is a patch installation package corresponding to the execution command locally. If there is a patch installation package corresponding to the execution command locally, perform availability check, consistency check and security check on the patch installation package respectively. If the legality check passes, use the patch installation package to perform a patch upgrade on the load balancing software and generate a patch upgrade log. The availability check includes a patch package basic version dependency check; the consistency check includes a patch package name check; and the security check includes a patch package decryption check.

[0060] Specifically, during the patch upgrade process, availability verification, consistency verification, and security verification are performed. Availability verification includes verifying the basic version dependency of the patch; consistency verification covers checking whether there is a patch package with the same name, and verifying the consistency of the patch; security verification requires decrypting the patch to verify its legitimacy. Upgrades are not allowed for illegal patch installation packages. Only legal patch installation packages are allowed to be upgraded, and the original binary files are automatically backed up during the process to facilitate patch rollback operations and ensure the reversibility of the operation. After the upgrade is successful, relevant logs are generated to record the entire upgrade process, and the instructions in the patch installation package are stored in a designated location so that relevant upgrade instructions can be viewed.

[0061] Step S23: If the type is patch rollback, determine whether the status of the patch installation package corresponding to the execution command in the local area is upgraded; if the status of the patch installation package corresponding to the execution command is upgraded, determine whether the upgraded patch installation package has a dependency; if the upgraded patch installation package does not have a dependency, determine that the dependency detection has passed, use the upgraded patch installation package to perform a patch rollback on the load balancing software, and modify the configuration file of the load balancing software to generate a patch rollback log.

[0062] In this embodiment, it is determined whether the upgraded patch installation package has any dependency. If the upgraded patch installation package has any dependency, it is determined that the dependency detection has failed, patch rollback failure information is generated, the patch rollback failure information is saved to a local log file, and a patch rollback failure prompt is sent to the user terminal.

[0063] Specifically, during the patch rollback process, it will check whether the patch package has been upgraded. For patch packages that have not been upgraded, rollback cannot be performed and a corresponding error message will be given. For patch packages that have been upgraded, the dependencies of the patch packages will be checked. For patch packages without superior dependencies, rollback is allowed. For patch packages with superior dependencies, the superior dependent patch packages must be rolled back first. After the rollback is successful, it will check whether the configuration of the relevant configuration files needs to be modified. For the configuration that needs to be modified, it will be modified automatically.

[0064] The specific process of this application is as follows Figure 3 As shown, first obtain the execution command for the load balancing software sent by the user end; then check the correctness of the parameters of the execution command; if the correctness check fails, the parameter error is determined, and a parameter error prompt message is generated, and the parameter error prompt message is recorded in a local log file; if the correctness check passes, the type of the execution command is determined; if the type is to display the patch installation package, the patch installation package in the patch directory is displayed; if the type is to view the patch upgrade record, the patch upgrade record is determined from the local log file so that the user end can view the patch upgrade record. If the type is a patch upgrade, it is determined whether there is a patch installation package corresponding to the execution command locally. If there is a patch installation package corresponding to the execution command locally, the patch installation package is checked for legitimacy. If the legitimacy check passes, the load balancing software is patched and upgraded using the patch installation package, and a patch upgrade log is generated; if the legitimacy check fails, it is determined that the patch package is unavailable, and the patch upgrade fails. If there is no patch installation package corresponding to the execution command locally, the patch upgrade fails as well. If the type of the execution command is patch rollback, determine whether the status of the patch installation package corresponding to the execution command in the local area is upgraded; if the status of the patch installation package is not upgraded, determine that the rollback has failed, and generate a rollback failure prompt message; if the status of the patch installation package is upgraded, perform a dependency check on the upgraded patch installation package; if the dependency check passes, use the upgraded patch installation package to perform a patch rollback on the load balancing software, and modify the configuration file of the load balancing software to generate a patch rollback log; if the dependency check fails, determine that the patch rollback has failed, and also generate a rollback failure prompt message.

[0065] The key points of this application are as follows: (1) When performing a patch upgrade on the load balancing software, the upgraded patch installation package will be checked for availability, consistency, and security. If an error occurs, an error message will be returned and the patch upgrade process cannot be completed; (2) When performing a patch rollback on the load balancing software, the rolled back version will be checked. If the rolled back version depends on other upgraded patch versions, the rollback will not be possible and an error message will be returned. The error message will indicate the patch installation package that needs to be rolled back first; (3) When performing a patch rollback on the load balancing software, the configuration file will be automatically modified to ensure the correctness of the configuration file after the rollback is complete.

[0066] In this embodiment, an execution command for the load balancing software sent by the user end is obtained, and the type of the execution command is determined; if the type is a patch upgrade, it is determined whether a patch installation package corresponding to the execution command exists locally; if the patch installation package corresponding to the execution command exists locally, a legitimacy check is performed on the patch installation package; if the legitimacy check passes, the load balancing software is patch upgraded using the patch installation package, and a patch upgrade log is generated; if the type is a patch rollback, it is determined whether the status of the patch installation package corresponding to the execution command in the local area is upgraded; if the status of the patch installation package corresponding to the execution command is upgraded, a dependency check is performed on the upgraded patch installation package; if the dependency check passes, the load balancing software is patch rolled back using the upgraded patch installation package, and the configuration file of the load balancing software is modified to generate a patch rollback log. The present application determines whether to perform a patch upgrade or patch rollback on the load balancing software by executing a command type, thereby avoiding the hidden dangers caused by manually replacing the product package. If it is a patch upgrade, it determines whether a patch installation package exists and performs a legitimacy check. If the legitimacy check passes, a patch upgrade log is generated to ensure the reversibility of the patch upgrade operation. During the patch rollback process, the dependency of the patch installation package is intelligently detected. If the dependency detection passes, the patch is rolled back and the configuration file is modified to ensure the correctness of the relevant configuration of the load balancing software and generate a patch rollback log so that the version can be rolled back quickly and reliably when needed, thereby ensuring the security and reliability of the load balancing software patch upgrade and rollback, and also improving the efficiency of the load balancing software patch upgrade and rollback.

[0067] See also Figure 4 As shown, the embodiment of the present invention discloses a load balancing software patch upgrade and rollback device, which may specifically include:

[0068] The command acquisition module 11 is used to acquire the execution command for the load balancing software sent by the user end and determine the type of the execution command;

[0069] The patch upgrade module 12 is used for, if the type is a patch upgrade, determining whether there is a patch installation package corresponding to the execution command locally, and if there is a patch installation package corresponding to the execution command locally, performing a legitimacy check on the patch installation package, and if the legitimacy check passes, using the patch installation package to perform a patch upgrade on the load balancing software, and generating a patch upgrade log;

[0070] The patch rollback module 13 is used to determine whether the status of the patch installation package corresponding to the execution command in the local area is upgraded if the type is patch rollback; if the status of the patch installation package corresponding to the execution command is upgraded, perform dependency detection on the upgraded patch installation package; if the dependency detection passes, use the upgraded patch installation package to perform patch rollback on the load balancing software, and modify the configuration file of the load balancing software to generate a patch rollback log.

[0071] In this embodiment, an execution command for the load balancing software sent by the user end is obtained, and the type of the execution command is determined; if the type is a patch upgrade, it is determined whether a patch installation package corresponding to the execution command exists locally; if the patch installation package corresponding to the execution command exists locally, a legitimacy check is performed on the patch installation package; if the legitimacy check passes, the load balancing software is patch upgraded using the patch installation package, and a patch upgrade log is generated; if the type is a patch rollback, it is determined whether the status of the patch installation package corresponding to the execution command in the local area is upgraded; if the status of the patch installation package corresponding to the execution command is upgraded, a dependency check is performed on the upgraded patch installation package; if the dependency check passes, the load balancing software is patch rolled back using the upgraded patch installation package, and the configuration file of the load balancing software is modified to generate a patch rollback log. The present application determines whether to perform a patch upgrade or patch rollback on the load balancing software by executing a command type, thereby avoiding the hidden dangers caused by manually replacing the product package. If it is a patch upgrade, it determines whether a patch installation package exists and performs a legitimacy check. If the legitimacy check passes, a patch upgrade log is generated to ensure the reversibility of the patch upgrade operation. During the patch rollback process, the dependency of the patch installation package is intelligently detected. If the dependency detection passes, the patch is rolled back and the configuration file is modified to ensure the correctness of the relevant configuration of the load balancing software and generate a patch rollback log so that the version can be rolled back quickly and reliably when needed, thereby ensuring the security and reliability of the load balancing software patch upgrade and rollback, and also improving the efficiency of the load balancing software patch upgrade and rollback.

[0072] In some specific embodiments, the command acquisition module 11 may specifically include:

[0073] A parameter correctness checking module, used for obtaining the execution command for the load balancing software sent by the user end, and performing correctness checking on the parameters in the execution command;

[0074] A type determination module, configured to determine the type of the execution command based on the parameter type corresponding to the parameter if the correctness check passes;

[0075] The parameter error prompt information generation module is used to generate parameter error prompt information if the correctness check fails, and record the parameter error prompt information to a local log file.

[0076] In some specific embodiments, the load balancing software patch upgrade and rollback device may also include:

[0077] A patch installation package saving module, used to obtain a patch installation package and save the patch installation package to a preset patch directory; the patch installation package includes a binary file to be upgraded and a patch manual;

[0078] A patch installation package display module, used for displaying the patch installation package in the patch directory if the type of the execution command is to display the patch installation package;

[0079] The patch upgrade record viewing module is used to determine the patch upgrade record from the local log file if the type of the execution command is patch upgrade record viewing, so that the user terminal can view the patch upgrade record.

[0080] In some specific embodiments, the patch upgrade module 12 may specifically include:

[0081] A patch upgrade failure information generating module, used to determine that the patch upgrade fails and generate patch upgrade failure information if the patch installation package corresponding to the execution command does not exist locally;

[0082] The patch upgrade failure prompt module is used to save the patch upgrade failure information to a local log file and send a patch upgrade failure prompt to the user terminal.

[0083] In some specific embodiments, the patch upgrade module 12 may specifically include:

[0084] The verification module is used to perform availability verification, consistency verification and security verification on the patch installation package respectively; the availability verification includes the patch package basic version dependency verification; the consistency verification includes the patch package name verification; the security verification includes the patch package decryption verification.

[0085] In some specific embodiments, the patch rollback module 13 may specifically include:

[0086] A dependency determination module, used to determine whether the upgraded patch installation package has a dependency relationship;

[0087] A software patch rollback module, used to determine that the dependency detection has passed if there is no dependency relationship between the upgraded patch installation package, and to perform a patch rollback on the load balancing software using the upgraded patch installation package;

[0088] The patch rollback failure information generation module is used to determine that the dependency detection fails if the upgraded patch installation package has a dependency, generate patch rollback failure information, save the patch rollback failure information to a local log file, and send a patch rollback failure prompt to the user terminal.

[0089] In some specific embodiments, the patch rollback module 13 may specifically include:

[0090] The file correctness detection module is used to use the upgraded patch installation package to roll back the load balancing software patch and to detect the correctness of the configuration file of the load balancing software;

[0091] The configuration content modification module is used to automatically modify the configuration content in the configuration file if the correctness detection fails.

[0092] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is used to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the load balancing software patch upgrade and rollback method performed by the electronic device disclosed in any of the aforementioned embodiments.

[0093] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0094] In addition, the memory 22, as a carrier for storing resources, can be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon include an operating system 221, a computer program 222 and data 223, etc. The storage method can be temporary storage or permanent storage.

[0095] Among them, the operating system 221 is used to manage and control the hardware devices and computer programs 222 on the electronic device 20 to realize the operation and processing of the data 223 in the memory 22 by the processor 21, which can be Windows, Unix, Linux, etc. In addition to including a computer program that can be used to complete the load balancing software patch upgrade and rollback method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include a computer program that can be used to complete other specific tasks. In addition to including data transmitted from an external device received by the load balancing software patch upgrade and rollback device, the data 223 can also include data collected by its own input and output interface 25, etc.

[0096] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0097] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium, in which a computer program is stored. When the computer program is loaded and executed by a processor, the load balancing software patch upgrade and rollback method steps disclosed in any of the aforementioned embodiments are implemented.

[0098] Finally, it should be noted that, in this article, relational terms such as first and second, etc. 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 sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0099] The above is a detailed introduction to a load balancing software patch upgrade and rollback method, device, equipment and storage medium provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A method for upgrading and rolling back a load balancing software patch, characterized in that: include: Obtaining an execution command for the load balancing software sent by the user end, and determining the type of the execution command; If the type is patch upgrade, determine whether there is a patch installation package corresponding to the execution command locally; if there is a patch installation package corresponding to the execution command locally, perform a legitimacy check on the patch installation package; if the legitimacy check passes, use the patch installation package to perform a patch upgrade on the load balancing software, and generate a patch upgrade log; If the type is patch rollback, determine whether the status of the patch installation package corresponding to the execution command in the local area is upgraded; if the status of the patch installation package corresponding to the execution command is upgraded, perform dependency detection on the upgraded patch installation package; if the dependency detection passes, perform patch rollback on the load balancing software using the upgraded patch installation package, and modify the configuration file of the load balancing software to generate a patch rollback log; Among them, the dependency detection is performed on the upgraded patch installation package, and if the dependency detection passes, the load balancing software is patch rolled back using the upgraded patch installation package, including: judging whether the upgraded patch installation package has a dependency; if the upgraded patch installation package does not have a dependency, determining that the dependency detection has passed, and patch rolling back the load balancing software using the upgraded patch installation package; if the upgraded patch installation package has a dependency, determining that the dependency detection has failed, generating patch rollback failure information, saving the patch rollback failure information to a local log file, and sending a patch rollback failure prompt to the user end.

2. The load balancing software patch upgrade and rollback method according to claim 1, characterized in that: The obtaining of the execution command for the load balancing software sent by the user end and determining the type of the execution command includes: Obtaining the execution command for the load balancing software sent by the user terminal, and performing a correctness check on the parameters in the execution command; If the correctness check passes, determining the type of the execution command based on the parameter type corresponding to the parameter; If the correctness check fails, a parameter error prompt message is generated and the parameter error prompt message is recorded in a local log file.

3. The load balancing software patch upgrade and rollback method according to claim 1, characterized in that: Also includes: Obtain a patch installation package, and save the patch installation package to a preset patch directory; the patch installation package includes a binary file to be upgraded and a patch manual; If the type of the execution command is to display the patch installation package, then the patch installation package in the patch directory is displayed; If the type of the execution command is patch upgrade record viewing, the patch upgrade record is determined from the local log file so that the user terminal can view the patch upgrade record.

4. The load balancing software patch upgrade and rollback method according to claim 1, characterized in that: After determining whether there is a patch installation package corresponding to the execution command locally, the method further includes: If the patch installation package corresponding to the execution command does not exist locally, it is determined that the patch upgrade fails, and patch upgrade failure information is generated; The patch upgrade failure information is saved in a local log file, and a patch upgrade failure prompt is sent to the user terminal.

5. The load balancing software patch upgrade and rollback method according to claim 1, characterized in that: The checking the legitimacy of the patch installation package includes: The patch installation package is respectively subjected to availability check, consistency check and security check; the availability check includes a patch package basic version dependency check; the consistency check includes a patch package name check; the security check includes a patch package decryption check.

6. The load balancing software patch upgrade and rollback method according to any one of claims 1 to 5, characterized in that: The step of rolling back the load balancing software patch by using the upgraded patch installation package and modifying the configuration file of the load balancing software includes: Use the upgraded patch installation package to roll back the load balancing software patch and perform a correctness check on the configuration file of the load balancing software; If the correctness check fails, the configuration content in the configuration file is automatically modified.

7. A load balancing software patch upgrade and rollback device, characterized in that: include: A command acquisition module, used to acquire an execution command for the load balancing software sent by the user end, and determine the type of the execution command; A patch upgrade module, for determining whether a patch installation package corresponding to the execution command exists locally if the type is a patch upgrade; if a patch installation package corresponding to the execution command exists locally, performing a legitimacy check on the patch installation package; if the legitimacy check passes, performing a patch upgrade on the load balancing software using the patch installation package, and generating a patch upgrade log; A patch rollback module, for determining whether the status of the patch installation package corresponding to the execution command in the local area is upgraded if the type is a patch rollback; if the status of the patch installation package corresponding to the execution command is upgraded, performing a dependency check on the upgraded patch installation package; if the dependency check passes, performing a patch rollback on the load balancing software using the upgraded patch installation package, and modifying a configuration file of the load balancing software to generate a patch rollback log; Among them, the dependency detection is performed on the upgraded patch installation package, and if the dependency detection passes, the load balancing software is patch rolled back using the upgraded patch installation package, including: judging whether the upgraded patch installation package has a dependency; if the upgraded patch installation package does not have a dependency, determining that the dependency detection has passed, and patch rolling back the load balancing software using the upgraded patch installation package; if the upgraded patch installation package has a dependency, determining that the dependency detection has failed, generating patch rollback failure information, saving the patch rollback failure information to a local log file, and sending a patch rollback failure prompt to the user end.

8. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, configured to execute the computer program to implement the load balancing software patch upgrade and rollback method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: Used to store computer programs; wherein, when the computer program is executed by a processor, the load balancing software patch upgrade and rollback method as described in any one of claims 1 to 6 is implemented.

Images