WO2016000137A1

WO2016000137A1 - Method, client and system for multi-site automatic update

Info

Publication number: WO2016000137A1
Application number: PCT/CN2014/081179
Authority: WO
Inventors: 张奇; 冯杰
Original assignee: 北京新媒传信科技有限公司
Priority date: 2014-06-30
Filing date: 2014-06-30
Publication date: 2016-01-07
Also published as: CN105765908A; CN105765908B

Abstract

Disclosed in the present invention are a method, client and system for a multi-site automatic update. The method of the present invention includes: obtaining update execution information of a management end, and parsing out client update information based on the update execution information; determining, according to a site naming principle and an application naming principle of a specification, the sites or services that need to be stopped, started or restarted in the client from the client update information; determining files that need to be updated from the client update information, performing update operation automatically in the order of stopping sites, stopping services, updating files, starting services and starting sites; after finishing the update operation, storing an update operation result locally and returning the update operation result to the management end. The solution of the present invention can solve problems in the prior art caused by manually updating the sites one by one, and guarantee the security, accuracy, and reliability of the multi-site automatic update while improving the work efficiency.

Description

TECHNICAL FIELD The present invention relates to the field of computer technologies, and in particular, to a multi-site automatic update method, a client, and a system. BACKGROUND OF THE INVENTION With the continuous development of the information age, the popularization of clustering and load balancing technologies, the server has evolved from a few initial stages to a huge data center, and the website update management has become increasingly complicated. At present, most of the work of updating management is manual. Operational. Even a simple system change or update often requires the operation and maintenance personnel to log in to each device to make manual changes one by one. When the number of devices reaches hundreds of thousands, the workload can be imagined. The stability and reliability of the update will gradually decrease as the workload increases.

Currently, for multi-site updates, most of the processing schemes are the process of the operator repeating the single-site update operation, or writing a script execution, but the update package upload still requires the operator to operate one by one, and encounters multiple deployments of one server. At the time of the site, it is still necessary to manually perform the operation of stopping, starting the site or the service one by one, and the work efficiency is very low. SUMMARY OF THE INVENTION Based on the above problems, an embodiment of the present invention provides a multi-site automatic update method, a client, and a system, to solve the problem in the prior art that a manual update is required on a site-by-site basis.

According to an aspect of the present invention, an embodiment of the present invention provides a multi-site automatic update method, where the method includes: acquiring update execution information of a management end, and parsing client update information according to the specification; Determining the site in the client that needs to be stopped, started, or restarted from the client update information; determining the service that needs to be stopped, started, or restarted in the client from the client update information according to the standard application naming principle; The client update information determines the files that need to be updated, and automatically performs the update operation in the order of stopping the site, stopping the service, updating the file, starting the service, and starting the site; after the update operation ends, the update operation result is stored locally and the update is performed. The result of the operation is returned to the management terminal.

The obtaining the update execution information of the management terminal, and parsing the client update information according to the method includes: Acquiring the grouping information and the update information of the management terminal; wherein the grouping information is information that the management terminal divides the client into groups according to the difference of the site or the service, where the group information includes a group name and a client ID list; the update information includes The group name and the client actually update the directory; by comparing the client ID with the grouping information, identifying the group to which the client belongs; and parsing the client update information from the update information of the management terminal according to the group to which the client belongs.

Optionally, the method further includes: before the performing the update operation, packaging the file that needs to be updated to obtain an archive package, storing the backup information of the archive package locally, and returning the backup information to the management end.

Optionally, the method further includes: acquiring rollback execution information of the management end; determining, from the rollback execution information, a site or a service that needs to be stopped, started, or restarted in the client; performing execution information according to the rollback Read the locally stored backup information, and release the content that needs to be rolled back from the archive package to overwrite the file that failed the update; execute the order in the order of stopping the site, stopping the service, restoring the file, starting the service, and starting the site. Roll operation; after the rollback operation ends, return the result of the rollback operation to the management side.

Optionally, the method further includes: after the end of the update operation, obtaining an information-summary algorithm MD5 value of the updated file from the update operation result; recording the MD5 value in a local file and returning the MD5 to the management terminal The value is used by the management side to verify the result of the update operation.

Optionally, the method further includes: acquiring deletion execution information of the management terminal; acquiring content information that the client needs to delete according to the deletion execution information; performing a deletion operation, and returning the deletion operation result to the management terminal. According to another aspect of the present invention, an embodiment of the present invention provides a client, including: an information processing module, configured to acquire update execution information of a management end, and parse out client update information according to the method; According to the standard site naming principle, the site that needs to be stopped, started, or restarted in the client is determined from the client update information; the service control module is configured to determine the client from the client update information according to the standard application naming principle. The service that needs to be stopped, started, or restarted; the update module is used to determine the files that need to be updated from the client update information, and automatically execute in the order of stopping the site, stopping the service, updating the file, starting the service, and starting the site. The update operation, after the update operation ends, stores the update operation result locally and returns the update operation result to the management terminal.

The information processing module includes: a grouping information acquiring sub-module, configured to acquire grouping information and update information of the management terminal; wherein the grouping information is information that the management terminal divides the client into groups according to differences in sites or services. , the group information includes a group name and a client ID list; The new information includes a group name and a client actual update directory; a packet comparison submodule, configured to identify a packet to which the client belongs by comparing the client ID with the grouping information; and parsing the submodule for using the client The belonging packet parses the client update information from the update information of the management terminal.

Optionally, the client further includes: a backup module, configured to: before the performing the update operation, package the file that needs to be updated to obtain an archive package, store the backup information of the archive package locally, and return the backup information to the management end.

Optionally, the information processing module is further configured to obtain rollback execution information of the management end; the site control module is further configured to: determine, from the rollback execution information, that the client needs to stop, start, or restart The service control module is further configured to: determine, from the rollback execution information, a service that needs to be stopped, started, or restarted in the client; the client further includes: a rollback module, configured to perform Rewinding the execution information, reading the locally stored backup information, and releasing the content that needs to be rolled back from the archive package to overwrite the file that failed the update, according to stopping the site, stopping the service, restoring the file, starting the service, starting The sequence of the site performs a rollback operation. After the rollback operation ends, the result of the rollback operation is returned to the management terminal.

Optionally, the client further includes: a verification module, configured to: after the update operation ends, obtain an information of the updated file from the update operation result, a digest algorithm MD5 value; and record the MD5 value in a local file. And returning the MD5 value to the management terminal for the management side to verify the update operation result.

Optionally, the information processing module is further configured to obtain the deletion execution information of the management terminal; the client further includes: a deletion module, configured to acquire, according to the deletion execution information, content information that the client needs to delete; Action, and return the result of the delete operation to the management side.

According to still another aspect of the present invention, an embodiment of the present invention provides a multi-site automatic update system, including: a management terminal and at least one of the foregoing clients; wherein the management terminal is configured to be used by the client The terminal provides update information, group information, and execution information, and saves the operation record. The invention has the following advantages: The method, the client and the system for automatically updating the multi-site provided by the embodiment of the present invention obtain the update information of the management terminal, and parse out the client update information, and parse the client update information. Ability to distinguish between sites, services, and common content; then, based on the canonical site naming principles and application naming principles, determine the sites and/or services in the client that need to be stopped, started, or restarted from the client update information to accurately execute the relevant Action, to ensure that the site update is not abnormal during the update process; then determine the files that need to be updated from the client update information, according to the stop site, Stop the service, update files, start the service, and start the site automatically to perform the update operation, ensuring safe, fast, and accurate completion of automatic updates of multiple sites on the client; after the update operation, store the update operation results locally and The update operation result is returned to the management terminal to make the update operation traceable. It can be seen that the technical solution of the present invention can solve the problem that the prior art needs to be manually updated on a site-by-site basis, and the work efficiency is improved, and the security, accuracy, and reliability of automatic updating of multiple sites are ensured.

Further, the management terminal may divide the client into several groups according to the difference of the site or the service, and the clients in the group are mostly load balancing configurations, and different packet update contents are different; the management terminal provides the client with update information with group information. The content of the update information can be reduced, and the management side can update the client of multiple load balancing configurations at the same time, thereby expanding the number of automatic update sites.

The above description is only an overview of the technical solutions of the present invention, and the technical means of the present invention can be more clearly understood, and can be implemented in accordance with the contents of the specification, and the above and other objects, features and advantages of the present invention can be more clearly understood. Specific embodiments of the invention are set forth below. BRIEF DESCRIPTION OF THE DRAWINGS Various other advantages and benefits will become apparent to those of ordinary skill in the art. The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting. Throughout the drawings, the same reference numerals are used to refer to the same parts. In the drawing:

FIG. 1 is a schematic diagram showing a multi-site automatic updating method according to an embodiment of the present invention; FIG. 2 is a schematic structural diagram showing a multi-site automatic updating system according to an embodiment of the present invention; A structural diagram of a client of an embodiment of the present invention;

FIG. 4 is a schematic structural diagram showing another client of an embodiment of the present invention.

FIG. 5 is a schematic structural block diagram of a multi-site automatic update system according to an embodiment of the present invention. Mode for Carrying Out the Invention Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided to provide a more thorough understanding of the present invention. The disclosure is to be fully disclosed to those skilled in the art. The main technical idea of the present invention is that the client parses the client update information that can distinguish the site, the service, and the common content according to the update execution information of the management terminal, and judges from the client update information according to the standardized site naming principle and service naming principle. Sites and/or services in which the sites need to be stopped, started, or restarted in the client, and the update operations are automatically performed in the order of stopping the site, stopping the service, updating the client files, starting the service, and starting the site, thereby accurately performing related actions, Ensure that the site update is not performed during the update process, thereby completing the automatic update of multiple sites on the client safely, quickly and accurately. After the update is completed, the update operation result is stored locally and the update operation result is returned to the management terminal to make the update The operation is traceable. In addition, the present invention can also provide update execution information with group information on the management side, reduce the content repetition of the update information, and realize the simultaneous update operation of the client for multiple sets of load balancing configurations, and expand the number of automatic update sites. . FIG. 1 shows a flow chart of a multi-site automatic update method according to an embodiment of the present invention. As shown in FIG. 1 , a multi-site automatic updating method provided by an embodiment of the present invention includes the following steps:

Sl l, obtain the update execution information of the management terminal, and parse the client update information accordingly.

The multi-site automatic update system needs two roles of management and client, and the management terminal provides update execution information; the client obtains update execution information and implements functions such as backup, update, rollback, and restart.

For clients with load balancing configuration, the management side can also split the client into groups according to site or service differences and construct a group information file. Grouping is to reduce duplicate content. The group information is recorded in the management file, and the configuration is basically unchanged. The group information format: group name, client ID list.

For this reason, the management terminal needs to include the group name when sending the update execution information to the client. The management terminal can automatically generate an update information file according to the specified update file directory rule, for example, the first layer directory name is required to update the group name, and the rest is the structure of the client actual directory. When the management terminal sends an update execution instruction to the client, the management information is distributed to the plurality of clients together with the update information.

As shown in FIG. 2, FIG. 2 is a structural diagram of a multi-site automatic update system according to an embodiment of the present invention. The management side distributes the group information and the update information to each controlled client, and the clients are divided into groups according to the difference of the site or the service, and the contents of the clients in different groups need to be updated differently. The group information includes a group name and a client ID list, and the update information includes a group name and a client actual update directory. After each client in the packet acquires the grouping information and the update information of the management terminal, it compares the self ID with the grouping information, identifies the packet to which the client belongs, and according to the group to which the user belongs, from the management terminal. The client update information is parsed in the new information, and then the corresponding operation is performed locally on the client. The information published by the management side and the information returned by the client can be implemented by the open source tool Saltstack. According to the execution information of the management terminal, functions such as update, backup, rollback, delete, check, restart, etc. can be automatically implemented on the client.

512. According to the standard site naming principle, determine the site in the client that needs to be stopped, started, or restarted from the client update information.

When multiple sites are deployed on a client, the client determines from the client update information which sites on the client need to stop, start, or restart according to the standard site naming principle, and perform related actions. In the process of stopping the site operation, it is also necessary to obtain a process value that needs to stop the site, and the process value can be provided by the management terminal in the execution information. When multiple contents of the site need to be modified, a decision lock is established to prevent the same site from performing repeated operations multiple times. The execution result of the site can be returned to the management terminal separately in the form of a list data structure as needed.

513. According to the standard service naming principle, the service that needs to be stopped, started, or restarted in the client is determined from the client update information.

When a client provides multiple services, the client determines the service items on the client that need to be stopped, started, and restarted according to the application naming principle of the specification. The service can be a Java application and executed. The specified operation, the result of the execution can be returned to the management terminal separately according to the needs of the list data structure.

NOTE: The above steps S12 and S13 can be performed simultaneously. The update execution information of the management terminal can also only indicate that the client stops, starts, restarts some or some sites or services, and does not involve the update of the client file. The result of the execution of the site or service needs to be returned to the management terminal separately.

514. Determine, from the client update information, a file that needs to be updated.

The client can update the client update information according to the update information of the management terminal, and can distinguish the site, the service, and the common content from the client update information, and the common content can be a client file or configuration information, and the client updates according to the generated client. Information automatically maintains relevant sites and services.

The generated client update information includes the actual update directory of the client, and the client obtains the update source file from the management terminal according to the actual update directory, and then updates the client local destination file.

515. Perform the update operation in the order of stopping the site, stopping the service, updating the file, starting the service, and starting the site.

To ensure the security of the update, each site is executed in the order of stopping the site, stopping the service, and updating. Files, startup services, startup sites, if the update does not include services or sites, the site or service will not be stopped or started.

When the update execution information indicates that there are multiple sites on the client that need to be updated synchronously, the multiple sites can perform their respective update operations independently and synchronously.

S16. After the update operation ends, the update operation result is stored locally and the update operation result is returned to the management terminal.

After the update operation ends, the update operation results are returned to the management terminal, and the update operation result is stored locally. The results of the update operation are recorded with specific sites, and/or services, and/or content that the client file update succeeded or failed. The recording and returning of the result of the update operation can make the update operation traceable.

The result of the client performing the update operation is saved on the management side, and is recorded in the management terminal file according to the operator information, the operation time, the operation content, and the operation result. In a method embodiment of the present invention, the multi-site automatic update method of the present invention may further include the steps of: before the automatic update operation is performed, packaging the file that needs to be updated to obtain an archive package, and storing the backup of the archive package locally. Information and return the backup information to the management terminal.

After receiving the update execution information of the management terminal, the client parses the client update information from the update execution information, and then determines the file information that needs to be updated from the client update information, and needs to change first before the file is changed. The file is archived to a local backup, and the archived backup information is stored locally, the backup information records the file name of the archive package, and the backup information is returned to the client. The method embodiment automatically backs up files before the client file is updated, which ensures the security and reliability of the multi-site automatic update method. In another method embodiment of the present invention, the multi-site automatic update method of the present invention may further include the steps of: acquiring rollback execution information of the management terminal; determining, from the rollback execution information, that the client needs to stop and start Or restarting the site or service; reading the locally stored backup information according to the rollback execution information, and releasing the content that needs to be rolled back from the archive package for overwriting the file that failed the update; Stop the service, restore the file, start the service, start the site in the order of the rollback operation; after the rollback operation ends, return the result of the rollback operation to the management side.

When the client fails to perform the update operation, the update operation result is also returned to the management terminal, and the management terminal generates a rollback execution information according to the update operation result of the update failure, and the client obtains the rollback execution of the management terminal. After the line information, the local backup information is read, and the content that needs to be rolled back is released from the archive package and overwrites the file that failed the update. The rollback execution information includes the site or service content, and the site or service in the client that needs to be stopped, started, or restarted is determined from the rollback execution information, and then stops the site, stops the service, restores the file, and starts the service. Start the site in the order of the rollback operation to ensure the security of the rollback operation; if the rollback content does not include the service or the site, the site or service will not be stopped. The result of the rollback operation needs to be returned to the management side. The method embodiment provides a solution for multi-site automatic update failure, which ensures the stability and reliability of the multi-site automatic update method. In still another method embodiment of the present invention, the multi-site automatic update method of the present invention may further include the steps of: after the end of the update operation, obtaining an information-summary algorithm MD5 value of the updated file from the update operation result; The MD5 value is recorded in the local file and the MD5 value is returned to the management terminal for the management side to verify the update operation result.

MD5, Message-Digest Algorithm 5, is also known as digest algorithm, hash algorithm, etc., to ensure complete and consistent information transmission. After the client update operation ends, the MD5 value of the client update file is automatically obtained and recorded in the local file. The file content format is "file name: MD5", one per line, and the file name is also returned to the management terminal. , MD5 is the dictionary type data of the value. After receiving the MD5 value, the management end performs security, confidentiality verification, and version detection on the updated content of the client according to the MD5 value. The method embodiment automatically obtains the MD5 value of the update file and returns it to the management terminal after the client file is updated, thereby ensuring the security and integrity of the multi-site automatic update method. In still another method embodiment of the present invention, the multi-site automatic update method of the present invention may further include the steps of: acquiring deletion execution information of the management terminal; acquiring content information that the client needs to delete according to the deletion execution information; Delete the operation and return the result of the deletion operation to the management side.

For example, when the client performs the update operation successfully, the update operation result is returned to the management terminal, and the management terminal generates the deletion execution information according to the update operation result of the update success. After the client obtains the deletion execution information of the management terminal, the backup is performed before the update operation is performed. The archive package is deleted. The method embodiment provides a solution for multi-site automatic update success, which ensures the integrity and security of the multi-site automatic update method. Based on the same inventive concept as the above method embodiment, FIG. 3 illustrates an embodiment in accordance with the present invention. A structure diagram of a client. As shown in FIG. 3, the client 300 provided by the embodiment of the present invention includes: an information processing module 310, configured to acquire update execution information of the management terminal, and parse the client update information accordingly;

The site control module 320 is configured to determine, according to the standard site naming principle, a site in the client that needs to be stopped, started, or restarted from the client update information;

The service control module 330 is configured to determine, according to the application naming principle of the specification, a service that needs to be stopped, started, or restarted in the client from the client update information;

The update module 340 is configured to determine, from the client update information, a file that needs to be updated, and automatically perform an update operation in the order of stopping the site, stopping the service, updating the file, starting the service, and starting the site, and storing the storage locally after the update operation ends. Update the operation result and return the update operation result to the management terminal. In an embodiment of the present invention, the information processing module 310 provided by the embodiment of the present invention may include:

a grouping information obtaining sub-module, configured to acquire grouping information and update information of the management terminal; wherein the grouping information is information that the management terminal divides the client into groups according to differences in sites or services, and the grouping information includes a group name and a client. ID list; the update information includes a group name and a client actual update directory;

a packet comparison submodule, configured to identify a packet to which the client belongs by comparing the client ID with the grouping information;

The parsing submodule is configured to parse the client update information from the update information of the management terminal according to the group to which the client belongs. In a product embodiment of the present invention, referring to FIG. 4, further based on the client structure shown in FIG. 3, another client 400 provided by the embodiment of the present invention further includes:

The backup module 450 is configured to: before the performing the update operation, package the file that needs to be updated to obtain an archive file, store the backup information of the archive package locally, and return the backup information to the management terminal.

In another embodiment of the present invention, referring to FIG. 4, the client 400 provided by the embodiment of the present invention further includes:

The rollback module 460 is configured to read the locally stored backup information according to the rollback execution information of the management end, and release the content that needs to be rolled back from the archive package to cover the file that fails to be updated; according to stopping the site, stopping the service, Recover files, start services, start the site in a sequence, perform a rollback operation, and roll back the operation After the bundle, return the result of the rollback operation to the management side. among them,

The information processing module 310 is further configured to acquire rollback execution information of the management end.

The site control module 320 is further configured to determine, from the rollback execution information, a site in the client that needs to be stopped, started, or restarted.

The service control module 330 is further configured to determine, from the rollback execution information, a service that needs to be stopped, started, or restarted in the client.

In still another embodiment of the present invention, referring to FIG. 4, the client 400 provided by the embodiment of the present invention further includes:

The verification module 470 is configured to: after the end of the update operation, obtain an information-summary algorithm MD5 value of the updated file from the update operation result; record the MD5 value in a local file, and return the MD5 value to the management end to use The update operation results are verified on the management side.

The deleting module 480 is configured to obtain content information that the client needs to delete according to the deletion execution information; perform a deletion operation, and return the deletion operation result to the management terminal. among them,

The information processing module 310 is further configured to acquire deletion execution information of the management terminal.

For the specific working mode of each module in the client of the embodiment of the present invention, refer to the related content in the foregoing method embodiment of the present invention, and details are not described herein again. Based on the same inventive concept as the above method embodiment, FIG. 5 shows a block diagram of a multi-site automatic updating system according to an embodiment of the present invention. As shown in FIG. 5, a system for automatically updating a multi-site according to an embodiment of the present invention includes a management terminal 500 and at least one client (1, 2, ... N); wherein the management terminal 500 , used to provide update information, group information, and execution information to the client, and save the operation record.

The execution information of the management terminal, including the update execution information, the rollback execution information, and the deletion execution information, are delivered to the client through the interactive interface of the management terminal, and the specified client performs the specified operation. The client returns the automatically executed update result, the backup result, the rollback result, the MD5 value, and the deletion result to the management terminal, and the management terminal records the operation execution result in the management terminal file. In summary, the multi-site automatic update method, the client, and the system provided by the embodiment of the present invention obtain the update information of the management terminal, and parse out the client update information, and parse the client. The end update information can distinguish between the site, the service, and the normal content; and then, according to the standardized site naming principle and the application naming principle, the site and/or service in the client that needs to be stopped, started, or restarted is determined from the client update information, thereby Accurately perform related actions to ensure that there is no site exception during the update process; then determine the files that need to be updated from the client update information, and automatically perform the update operation in the order of stopping the site, stopping the service, updating the file, starting the service, and starting the site, ensuring The automatic update of multiple sites on the client is completed securely, quickly and accurately; after the update operation ends, the update operation result is stored locally and the update operation result is returned to the management terminal, so that the update operation is traceable. It can be seen that the technical solution of the present invention can solve the problems in the prior art that need to be manually updated on a site-by-site basis, and improve the work efficiency, and also ensure the security, accuracy, and reliability of automatic update of multiple sites. .

Further, before performing the automatic update operation, packaging the file that needs to be updated to obtain an archive package, storing the backup information of the archive package locally, and returning the backup information to the management side, can ensure the security and reliability of the multi-site automatic update. Sex.

Further, when the client performs the update operation, the local backup information is read by performing the rollback operation, the content that needs to be rolled back is released from the archive package, and the file that fails the update is overwritten, and the result of the rollback operation is returned to the management terminal. Provides a solution for multi-site automatic update failure, ensuring the stability and reliability of the multi-site automatic update method.

Further, after the update operation ends, the information of the updated file is obtained from the update operation result - the digest algorithm MD5 value; the MD5 value is recorded in the local file and the MD5 value is returned to the management terminal for the management end pair The scheme of updating the operation results for verification ensures the security and integrity of the multi-site automatic update method.

Further, the client obtains the content information that the client needs to delete according to the deletion execution information of the management terminal, performs the deletion operation, and returns the deletion operation result to the management terminal, thereby ensuring the integrity and security of the multi-site automatic update method. It should be noted: The various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components in accordance with embodiments of the present invention. The invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein. Such a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

"an embodiment," or "an embodiment," or "an embodiment," In addition, it should be noted that the phrase "in one embodiment" herein does not necessarily refer to the same embodiment.

In addition, it should be noted that the language used in the specification has been selected for the purpose of reading and teaching, and is not intended to explain or limit the subject matter of the present invention. Therefore, many modifications and changes will be apparent to those skilled in the art without departing from the scope of the invention. The disclosure of the present invention is intended to be illustrative, and not restrictive, and the scope of the invention is defined by the appended claims.

Claims

Claim

A method for automatically updating a multi-site, the method comprising:

Obtaining the update execution information of the management terminal, and parsing the client update information accordingly;

According to the standard site naming principle, the site in the client that needs to be stopped, started, or restarted is determined from the client update information;

According to the standard application naming principle, the service that needs to be stopped, started, or restarted in the client is determined from the client update information;

Determine the files that need to be updated from the client update information, and automatically perform the update operation in the order of stopping the site, stopping the service, updating the file, starting the service, and starting the site;

After the update operation ends, the update operation result is stored locally and the update operation result is returned to the management side.

The method according to claim 1, wherein the obtaining the update execution information of the management terminal, and parsing the client update information according to the method includes:

Acquiring the grouping information and the update information of the management terminal; wherein the grouping information is information that the management terminal divides the client into groups according to the difference of the site or the service, where the group information includes a group name and a client ID list; the update information includes The group name and the actual update directory of the client;

By comparing the client ID with the grouping information, the packet to which the client belongs is identified; and the client update information is parsed from the update information of the management terminal according to the group to which the client belongs.

The method according to claim 1 or 2, wherein the method further comprises: before performing the automatic update operation, packaging the file that needs to be updated to obtain an archive package, and locally storing the backup information of the archive package. And return the backup information to the management terminal.

4. The method according to claim 3, wherein the method further comprises:

Obtaining the rollback execution information of the management terminal;

Determining, from the rollback execution information, a site or service in the client that needs to be stopped, started, or restarted;

And reading, according to the rollback execution information, the locally stored backup information, and releasing the content that needs to be rolled back from the archive package to cover the file that fails to be updated;

Back in the order of stopping the site, stopping the service, restoring the file, starting the service, and starting the site

The method according to claim 1 or 2, wherein the method further comprises: after the end of the updating operation, obtaining an information-digest algorithm MD5 value of the updated file from the update operation result;

The MD5 value is recorded in a local file and the MD5 value is returned to the management terminal for the management side to verify the update operation result.

The method according to claim 5, wherein the method further comprises:

Obtain the deletion execution information of the management terminal;

Obtaining content information that the client needs to delete according to the deletion execution information;

Perform the delete operation and return the result of the delete operation to the management terminal.

A client, wherein the client further includes:

An information processing module, configured to obtain update execution information of the management terminal, and parse the client update information accordingly;

a site control module, configured to determine, from the client update information, a site in the client that needs to be stopped, started, or restarted according to the standard site naming principle;

a service control module, configured to determine, according to a standard application naming principle, a service that needs to be stopped, started, or restarted in the client from the client update information;

An update module, configured to determine a file that needs to be updated from the client update information, and automatically perform an update operation in the order of stopping the site, stopping the service, updating the file, starting the service, starting the site, and storing the update locally after the update operation ends The result of the operation is returned to the management terminal.

The client according to claim 7, wherein the information processing module comprises: a grouping information obtaining sub-module, configured to acquire grouping information and update information of the management terminal; wherein the grouping information is The difference of the site or service divides the client into several groups of information, and the group information includes a group name and a client ID list; the update information includes a group name and a client actual update directory;

The parsing submodule is configured to parse the client update information from the update information of the management terminal according to the group to which the client belongs.

The client according to claim 7 or 8, wherein the client further comprises: a backup module, configured to package the file to be updated to be archived before performing an update operation The package stores the backup information of the archive package locally and returns the backup information to the management terminal.

10. Apparatus according to claim 9 wherein:

The information processing module is further configured to acquire rollback execution information of the management end;

The site control module is further configured to determine, from the rollback execution information, a site in the client that needs to be stopped, started, or restarted;

The service control module is further configured to determine, from the rollback execution information, a service that needs to be stopped, started, or restarted in the client;

The client also includes:

a rollback module, configured to read the locally stored backup information according to the rollback execution information, and release the content that needs to be rolled back from the archive package to cover the file that fails to be updated, according to stopping the site, stopping the service The file is restored, the service is started, the site is started, and the rollback operation is performed. After the rollback operation ends, the result of the rollback operation is returned to the management terminal.

The client according to claim 7 or 8, wherein the client further comprises: a verification module, configured to obtain information of the updated file from the update operation result after the update operation ends - summary Algorithm MD5 value; record the MD5 value in a local file and return the MD5 value to the management terminal for the management side to verify the update operation result.

12. The client of claim 7 wherein:

The information processing module is further configured to acquire deletion execution information of the management terminal;

The client also includes:

The deleting module is configured to obtain content information that the client needs to delete according to the deletion execution information; perform a deletion operation, and return the deletion operation result to the management terminal.

A multi-site automatic update system, comprising: a management terminal and at least one client according to any one of claims 7 to 12; wherein the management terminal is configured to provide an update to the client Information, grouping information, and execution information, and save operation records.