Hot patch application management method and device

Abstract

The invention discloses a hot patch application management method and device. The method comprises the steps of initiating an execution request to a server by a client; wherein the execution request comprises information of the client; receiving a hot patch list fed back by the server; detecting to-be-downloaded hot patch information according to the fed back hot patch list, and sending the to-be-downloaded hot patch information to the server; receiving a hot patch file sent by the server; and loading the received hot patch file. The server receives an execution request initiated by the client; querying a hot patch list according to the information of the client in the execution request; feeding back the queried hot patch list to the client; receiving to-be-downloaded hot patch information sent by the client; downloading the hot patch according to the received information of the hot patch to be downloaded; and sending the downloaded hot patch file to the client. According to the invention, the workload of an administrator is reduced, and the accuracy and uniformity are improved.

Description

technical field [0001] The invention relates to the field of hot patch application, in particular to a method and device for managing hot patch application. Background technique [0002] For ordinary patches, in order to fix kernel problems, kernel vulnerabilities or improve kernel functions, after recompiling the kernel or modules and copying them into the target system, the system must be restarted to complete; however, restarting the system will seriously affect the production environment business in many cases, so Hot patches came into being. [0003] The process of using the hot patch is generally to copy the hot patch to the target machine through a USB flash drive or SSH / SFTP after generating the hot patch, and then execute the hot patch loading action. This process has the following disadvantages: 1) Whether it is a U disk or SSH / SFTP, when there are many machines to be managed (such as a service cluster), this will be a very cumbersome task; 2) Many times the U dis...

AI Technical Summary

Problems solved by technology

This process has the following disadvantages: 1) Whether it is a U disk or SSH / SFTP, when there are many machines to be managed (such as a service cluster), this will be a very cumbersome task; 2) Many times the U disk is inconvenient , it may be that the storage location of the machine is far away and not centralized, and it is often a virtual machine; 3) Using a USB disk may lead to the introduction of Trojan viruses; 4) Using SSH or SFTP requires recording the password of each machine, or performing password-free configuration; 5) If the machine involves multiple architectures and multiple kernel versions, you also need to pay attention to comparing the version and architecture information, because the hot patch can only be used normally if the version and architecture are consistent; 6) If an error occurs during the copy process, or the copy The process is interrupted abnormally (without noticing it), resulting in the hot patch not being copied to the target machine normally, which will lead to the failure of hot patch loading and application, and it takes time to locate the cause

Images