CN111752581A - Distributed system upgrading method and device and computer system - Google Patents
Distributed system upgrading method and device and computer system Download PDFInfo
- Publication number
- CN111752581A CN111752581A CN202010443494.6A CN202010443494A CN111752581A CN 111752581 A CN111752581 A CN 111752581A CN 202010443494 A CN202010443494 A CN 202010443494A CN 111752581 A CN111752581 A CN 111752581A
- Authority
- CN
- China
- Prior art keywords
- upgrade
- upgrading
- configuration file
- request
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 230000008569 process Effects 0.000 claims abstract description 8
- 238000013515 script Methods 0.000 claims description 48
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 238000012423 maintenance Methods 0.000 abstract description 23
- 238000004891 communication Methods 0.000 description 8
- 238000007726 management method Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 230000003993 interaction Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application discloses an upgrading method and device of a distributed system and a computer system. The method comprises the following steps: the version publishing node receives the upgrading request, acquires an upgrading packet corresponding to the upgrading request, calls a module corresponding to the upgrading request in the ansable, and sends the upgrading packet to the remote node in batches, wherein the upgrading packet comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrading program required by the remote node; and after receiving the corresponding upgrade package, the remote node acquires an identifier, identifies the content of the configuration file in the upgrade package, matches the upgrade program of the system according to the identifier, replaces the original program in the content of the configuration file with the acquired upgrade program, and sends an upgrade result to the version release node after the upgrade is completed. The high-cost operation and maintenance service mode of the traditional operation and maintenance is changed, the standardized upgrading process of the system is customized according to the requirement, manual intervention upgrading is not needed, the repeated operation times are reduced, upgrading is avoided, and the possibility of misoperation is reduced.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to an upgrading method and device of a distributed system and a computer system.
Background
With the rapid development of cloud computing and distributed systems, the architecture of the IT system is becoming more complex, the number of application services and nodes is multiplied, and the traditional operation and maintenance upgrading tool has certain limitations:
1. the traditional upgrading tool needs more manual operations and is easy to have misoperation.
2. The traditional operation and maintenance upgrading has no standardized flow, the repeated operation is more, and the operation process is complicated.
These limitations are increasingly highlighted with the rapid development of cloud computing and distributed systems. Therefore, the management function and efficiency of the traditional upgrading tool cannot meet the requirement, and a set of distributed automatic upgrading tool is needed urgently to improve the management efficiency of the application nodes of the distributed system.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides an upgrading method and device of a distributed system and a computer system.
The embodiment of the invention provides the following specific technical scheme:
in a first aspect, the present invention provides a method for upgrading a distributed system, where the method includes:
the method comprises the steps that a version release node receives an upgrade request, acquires an upgrade package corresponding to the upgrade request, calls a module corresponding to the upgrade request in an idle and sends the upgrade package to remote nodes in batches, wherein the upgrade package comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrade program required by the remote nodes;
and after receiving the corresponding upgrade package, the remote node acquires the identifier, identifies the content of the configuration file in the upgrade package, matches the upgrade program of the system according to the identifier, replaces the original program in the content of the configuration file with the acquired upgrade program, and sends an upgrade result to the version release node after the upgrade is finished.
Preferably, the name suffix of the configuration file content in the upgrade package is the host name of the corresponding remote node.
Preferably, before the remote node identifies the configuration file content in the upgrade package, the method further comprises:
and the remote node backs up the corresponding upgrade package and stores the backed-up upgrade package in a backup folder.
Preferably, before the version publishing node sends the upgrade package to the remote node in batch, the method further includes:
and the version release node generates a version number corresponding to the upgrade package.
Preferably, the method further comprises:
the version publishing node receives a rollback request, calls a module corresponding to the rollback request in an idle according to the rollback request, and sends the rollback request to the remote node in batches, wherein the rollback request comprises a version number corresponding to an upgrade package to be rolled back;
the remote node analyzes the rollback request to obtain a version number, acquires an upgrade package to be rolled back corresponding to the version number from a backup folder, identifies the corresponding configuration file content in the upgrade package to be rolled back and acquires an identifier, acquires a backed-up upgrade program according to the acquired identifier, and replaces the original program in the configuration file content with the acquired backed-up upgrade program.
Preferably, the generation process of the upgrade package includes:
obtaining upgrading content;
compiling and packaging the upgrading content to generate the upgrading package.
Preferably, the method further comprises:
the version publishing node receives an upgrading script operation request, acquires an upgrading script corresponding to the upgrading script operation request, calls a module corresponding to the upgrading script operation request in an idle and sends the upgrading script to a remote node in batches;
and the remote node runs the upgrading script after receiving the upgrading script, and sends a script running result to the version release node after the running is finished.
In a second aspect, the present invention provides an upgrade apparatus for a distributed system, where the upgrade apparatus includes a version release node and a remote node;
the version publishing node is used for receiving an upgrading request, acquiring an upgrading packet corresponding to the upgrading request, calling a module corresponding to the upgrading request in an idle, and sending the upgrading packet to remote nodes in batches, wherein the upgrading packet comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrading program required by the remote nodes;
the remote node is used for acquiring the identification after receiving the corresponding upgrade package, identifying the configuration file content in the upgrade package, matching the upgrade program of the system according to the identification, replacing the original program in the configuration file content with the acquired upgrade program, and sending an upgrade result to the version release node after the upgrade is completed.
Preferably, the name suffix of the configuration file content in the upgrade package is the host name of the corresponding remote node.
Preferably, the remote node is further configured to backup the corresponding upgrade package before identifying the content of the configuration file in the upgrade package, and store the backed-up upgrade package in the backup folder.
Preferably, the version publishing node is further configured to generate a version number corresponding to the upgrade package before sending the upgrade package to a remote node in batch.
Preferably, the remote node is further configured to receive a rollback request, call a module corresponding to the rollback request in an idle according to the rollback request, and send the rollback request to the remote node in batch, where the rollback request includes a version number corresponding to an upgrade package to be rolled back;
the remote node is further configured to analyze the rollback request to obtain a version number, obtain an upgrade package to be rolled back corresponding to the version number from a backup folder, identify corresponding configuration file content in the upgrade package to be rolled back and obtain an identifier, obtain a backed-up upgrade program according to the obtained identifier, and replace an original program in the configuration file content with the obtained backed-up upgrade program.
Preferably, the apparatus further comprises:
the compiling module is used for acquiring upgrading content;
compiling and packaging the upgrading content to generate the upgrading package.
Preferably, the version publishing node is further configured to receive an upgrade script operation request, obtain an upgrade script corresponding to the upgrade script operation request, call a module in the infrastructure corresponding to the upgrade script operation request, and send the upgrade script to the remote node in batch;
the remote node is also used for running the upgrading script after receiving the upgrading script and sending a script running result to the version release node after the running is finished.
In a third aspect, the present invention provides a computer system comprising:
one or more processors; and
a memory associated with the one or more processors for storing program instructions that, when read and executed by the one or more processors, perform operations comprising:
the method comprises the steps that a version release node receives an upgrade request, acquires an upgrade package corresponding to the upgrade request, calls a module corresponding to the upgrade request in an idle and sends the upgrade package to remote nodes in batches, wherein the upgrade package comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrade program required by the remote nodes;
and after receiving the corresponding upgrade package, the remote node acquires the identifier, identifies the content of the configuration file in the upgrade package, matches the upgrade program of the system according to the identifier, replaces the original program in the content of the configuration file with the acquired upgrade program, and sends an upgrade result to the version release node after the upgrade is finished.
The embodiment of the invention has the following beneficial effects:
1. the method supports functions of batch system configuration, batch program deployment, batch operation commands and the like through being integrated in various modules of the ansable, can well complete maintenance work such as daily upgrading and the like when facing hundreds of cloud nodes, improves the efficiency of operation and maintenance upgrading, reduces upgrading errors, reduces the operation difficulty of personnel, does not need manual intervention upgrading, reduces the repeated operation times, reduces the possibility of misoperation, and is convenient for the operation and maintenance personnel to use; the method changes the high-cost operation and maintenance service mode of the traditional operation and maintenance, can customize the standardized upgrading process of the system according to the requirement, can be used for daily maintenance management of the computer system, and has special advantages for daily maintenance of a large-size distributed computer system;
2. the method can automatically identify and modify the file content according to different configuration files, reduce the repeated operability of operation and maintenance, achieve the aim of upgrading automation, and carry out different modifications without different configuration files;
3. according to the method, the plurality of upgrading scripts are integrated, so that the nodes can run the upgrading scripts in batches, the difficulty of daily script management is improved, and the operation and maintenance personnel can use the upgrading scripts conveniently.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a system architecture diagram deployed on a version publishing node according to an embodiment of the present application;
FIG. 2 is a flow chart of processing a service request according to a deployed system architecture according to an embodiment of the present application;
fig. 3 is a flowchart of an upgrade method for a distributed system according to an embodiment of the present application;
FIG. 4 is a schematic application environment diagram of a distributed system according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a computer system according to a third embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As described in the background art, the conventional upgrading tool needs more manual operations and is easy to have operation errors; the method for upgrading the distributed system comprises the steps of setting a plurality of nodes in a distributed mode, and upgrading the nodes in the distributed mode, wherein the nodes are connected with the nodes in a distributed mode, and the nodes are connected with the nodes in a distributed mode.
Example one
The method can be applied to a cloud environment host cluster formed by a plurality of clusters, as shown in fig. 1, a set of system architecture is deployed on a version release node, and an automatic operation and maintenance platform is generated based on the system architecture.
The automation operation and maintenance platform integrates nginx, uwsgi, a database and a django framework integrating a plurality of processing modules (comprising a controller, a model interaction module, a view display module and an allowed API module).
When specifically processing a service, as shown in fig. 2, nginx and uwsgi receive a service request, send the service request to a controller, the controller sends the service request to a model interaction module, the model interaction module stores data in a database, receives a return result of the database and sends the return result to a view display module, the view display module calls an anchor, sends the request to each cluster through a module integrated in the anchor, and each cluster returns an execution result to a version publishing node through the anchor and finally returns the execution result to a browser through the view display module so that a page displays the execution result.
The automatic operation and maintenance platform achieves high system concurrency by using nginx and uwsgi. nginx occupies less memory, has ultrahigh concurrency capability, has over ten thousands of concurrency capability of a single unit, has more outstanding performance in pure static web service, and has more excellent performance because the bottom layer of the Web service is processed by using an epoll asynchronous IO model.
In order to control and manage the remote virtual machine, the automatic operation and maintenance platform uses and provides an allowed third-party library to be packaged into an API, and the allowed third-party library integrates contents such as shell (command module), fetch (remotely acquiring files), copy (copying files) and the like. In addition, django can also realize quick calling in the view, and the development speed is improved.
In the scheme, the ansable is deployed on the version release node, and the version release node communicates with each node in the cloud environment host cluster through the ssh protocol.
The version release host installed with the above automatic operation and maintenance platform, as shown in fig. 3, may implement the following steps:
s11, the version release node receives the upgrade request, acquires the upgrade package corresponding to the upgrade request, calls the module corresponding to the upgrade request in the ansable, and sends the upgrade package to the remote node in batch.
The upgrading package comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrading program required by the remote node. In addition, in order to accurately upload the upgrade package to each corresponding remote node, the name suffix of the configuration file content in the upgrade package in the scheme is the host name of the corresponding remote node.
The generation process of the upgrade package comprises the following steps:
1. obtaining upgrading content;
2. compiling and packaging the upgrading content to generate an upgrading package.
Specifically, the operation and maintenance personnel add the upgrade content, upload the upgrade content to a production compiling environment so that the upgrade content is compiled and packaged to generate an upgrade package, and then download the generated upgrade package to a version issuing machine, so that the upgrade package can be called conveniently during subsequent upgrade, wherein the version issuing machine is a version issuing node.
Before the version release node sends the upgrade package to the remote node in batch, the method also comprises the following steps:
and the version publishing node generates a version number corresponding to the upgrade package.
S12, after receiving the corresponding upgrade package, the remote node acquires the identifier, identifies the configuration file content in the upgrade package, matches the upgrade program of the system according to the identifier, replaces the original program in the configuration file content with the acquired upgrade program, and sends the upgrade result to the version release node after the upgrade is completed.
The method can be applied in the application environment as shown in fig. 4.
Specifically, the version issuing machine receives an upgrade request sent by operation and maintenance personnel, acquires an upgrade package corresponding to the upgrade request, and calls a module corresponding to the upgrade request in the infrastructure, so that the upgrade request is sent to each remote node in the cloud platform to be upgraded in batches; each remote node in the cloud platform acquires an identifier, matches an upgrading program of the system according to the identifier, simultaneously identifies the content of the configuration file in the upgrading package, replaces the original program in the content of the configuration file with the acquired upgrading program, and sends an upgrading result to the version issuing machine after upgrading is completed.
In the above example, the cloud platform is a dual-hub in the same city, and each hub includes two remote nodes, so that the content of the configuration file updated by the application may be different, and based on this, the name suffix of the content of the configuration file may be configured to be the same as the host name of the corresponding remote node, so that the version issuer may accurately send different update packages to the corresponding remote nodes, so that each remote node replaces the content of the configuration file according to the host name.
Therefore, the method can identify the nodes through different configuration files, so that the nodes modify the contents in the configuration files, automatic upgrading is realized, manual intervention is not needed, and the efficiency of operation and maintenance upgrading is improved.
In addition, before the remote node identifies the corresponding configuration file in the upgrade package, the method may further include the following steps:
and the remote node backs up the corresponding upgrade package according to the upgrade request and stores the backed-up upgrade package in a backup folder.
Thus, if a problem occurs in the current upgrade, the rollback operation can be realized according to the backed-up upgrade package without affecting the normal production operation, and specifically, the rollback operation may include the following steps:
1. the version publishing node receives the rollback request, calls a module corresponding to the rollback request in the ansable according to the rollback request, and sends the rollback request to the remote nodes in batches;
the rollback request comprises a version number corresponding to an upgrade package to be rolled back;
2. the remote node analyzes the rollback request to obtain a version number, acquires an upgrade package to be rolled back corresponding to the version number from the backup folder, identifies the corresponding configuration file content in the upgrade package to be rolled back and acquires an identifier, acquires a backed-up upgrade program according to the acquired identifier, and replaces the original program in the configuration file content with the acquired backed-up upgrade program.
For operation and maintenance personnel, the background (version release node) can send batch commands to each remote node through the ansable by only clicking the version number at the front end and sending a rollback request, so that each remote node unlocks the upgrade package of the corresponding version and restarts the application process.
In addition, the front end of the version release host integrates a plurality of upgrading scripts, so that the upgrading scripts can be operated by the nodes in batch, the difficulty of daily script management is improved, and the operation and maintenance personnel can use the upgrading scripts conveniently. The method comprises the following specific steps:
1. the version publishing node receives the upgrading script operation request, acquires the upgrading script corresponding to the upgrading script operation request, calls a module corresponding to the upgrading script operation request in the ansable, and sends the upgrading script to the remote node in batches;
2. and after receiving the upgrading script, the remote node runs the upgrading script and sends a script running result to the version release node after the running is finished.
Example two
Corresponding to the embodiment, the application also provides an upgrading device of the distributed system, which comprises a version release node and a remote node;
the version publishing node is used for receiving the upgrading request, acquiring an upgrading packet corresponding to the upgrading request, calling a module corresponding to the upgrading request in the ansable, and sending the upgrading packet to the remote node in batches, wherein the upgrading packet comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrading program required by the remote node;
the remote node is used for acquiring the identification after receiving the corresponding upgrade package, identifying the content of the configuration file in the upgrade package, matching the upgrade program of the system according to the identification, replacing the original program in the content of the configuration file with the acquired upgrade program, and sending an upgrade result to the version release node after the upgrade is completed.
Preferably, the name suffix of the configuration file in the upgrade package is the host name of the corresponding remote node.
Preferably, the remote node is further configured to backup the corresponding upgrade package before identifying the content of the configuration file in the upgrade package, and store the backed-up upgrade package in the backup folder.
Preferably, the version publishing node is further configured to generate a version number corresponding to the upgrade package before sending the upgrade package to the remote node in batch.
Preferably, the remote node is further configured to receive a rollback request, call a module corresponding to the rollback request in the ansable according to the rollback request, and send the rollback request to the remote nodes in batch, where the rollback request includes a version number corresponding to an upgrade package to be rolled back;
the remote node is further used for analyzing the rollback request to obtain a version number, obtaining an upgrade package to be rolled back corresponding to the version number from the backup folder, identifying corresponding configuration file content in the upgrade package to be rolled back and obtaining an identifier, obtaining a backed-up upgrade program according to the obtained identifier, and replacing the original program in the configuration file content with the obtained backed-up upgrade program.
Preferably, the above apparatus further comprises:
the compiling module is used for acquiring upgrading content;
compiling and packaging the upgrading content to generate an upgrading package.
Preferably, the version publishing node is further configured to receive an upgrade script operation request, obtain an upgrade script corresponding to the upgrade script operation request, call a module in the infrastructure corresponding to the upgrade script operation request, and send the upgrade script to the remote node in batch;
the remote node is also used for running the upgrading script after receiving the upgrading script and sending a script running result to the version release node after the running is finished.
EXAMPLE III
The present application further provides a computer system comprising:
one or more processors; and
a memory associated with the one or more processors for storing program instructions that, when read and executed by the one or more processors, perform operations comprising:
the version publishing node receives the upgrading request, acquires an upgrading packet corresponding to the upgrading request, calls a module corresponding to the upgrading request in the ansable, and sends the upgrading packet to the remote node in batches, wherein the upgrading packet comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrading program required by the remote node;
and after receiving the corresponding upgrade package, the remote node acquires an identifier, identifies the content of the configuration file in the upgrade package, matches the upgrade program of the system according to the identifier, replaces the original program in the content of the configuration file with the acquired upgrade program, and sends an upgrade result to the version release node after the upgrade is completed.
FIG. 5 illustrates an architecture of a computer system that may include, in particular, a processor 32, a video display adapter 34, a disk drive 36, an input/output interface 38, a network interface 310, and a memory 312. The processor 32, video display adapter 34, disk drive 36, input/output interface 38, network interface 310, and memory 312 may be communicatively coupled via a communication bus 314.
The processor 32 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solution provided in the present Application.
The Memory 312 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random access Memory), a static storage device, a dynamic storage device, or the like. The memory 312 may store an operating system 316 for controlling the operation of the computer system 30, a Basic Input Output System (BIOS)318 for controlling low-level operations of the computer system. In addition, a web browser 320, a data storage management system 322, and the like may also be stored. In summary, when the technical solution provided by the present application is implemented by software or firmware, the relevant program code is stored in the memory 312 and invoked by the processor 32 for execution.
The input/output interface 38 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The network interface 310 is used for connecting a communication module (not shown in the figure) to realize communication interaction between the device and other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
Communication bus 314 includes a path to transfer information between the various components of the device, such as processor 32, video display adapter 34, disk drive 36, input/output interface 38, network interface 310, and memory 312.
In addition, the computer system can also obtain the information of specific receiving conditions from the virtual resource object receiving condition information database for condition judgment and the like.
It should be noted that although the above-described device only shows the processor 32, the video display adapter 34, the disk drive 36, the input/output interface 38, the network interface 310, the memory 312, the communication bus 314, etc., in a specific implementation, the device may also include other components necessary for normal operation.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a cloud server, or a network device) to execute the method according to the embodiments or some parts of the embodiments of the present application.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention. In addition, the computer system, the upgrading device of the distributed system and the upgrading method of the distributed system provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in detail in the method embodiments and are not described herein again.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A method for upgrading a distributed system, the method comprising:
the method comprises the steps that a version release node receives an upgrade request, acquires an upgrade package corresponding to the upgrade request, calls a module corresponding to the upgrade request in an idle and sends the upgrade package to remote nodes in batches, wherein the upgrade package comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrade program required by the remote nodes;
and after receiving the corresponding upgrade package, the remote node acquires the identifier, identifies the content of the configuration file in the upgrade package, matches the upgrade program of the system according to the identifier, replaces the original program in the content of the configuration file with the acquired upgrade program, and sends an upgrade result to the version release node after the upgrade is finished.
2. The method of claim 1, wherein the name suffix of the configuration file content in the upgrade package is a host name of the corresponding remote node.
3. The method of claim 1, wherein before the remote node identifies the configuration file content in the upgrade package, the method further comprises:
and the remote node backs up the corresponding upgrade package and stores the backed-up upgrade package in a backup folder.
4. The method of claim 1, wherein before the version publishing node sends the upgrade package to a remote node in bulk, the method further comprises:
and the version release node generates a version number corresponding to the upgrade package.
5. The method of claim 4, further comprising:
the version publishing node receives a rollback request, calls a module corresponding to the rollback request in an idle according to the rollback request, and sends the rollback request to the remote node in batches, wherein the rollback request comprises a version number corresponding to an upgrade package to be rolled back;
the remote node analyzes the rollback request to obtain a version number, acquires an upgrade package to be rolled back corresponding to the version number from a backup folder, identifies the corresponding configuration file content in the upgrade package to be rolled back and acquires an identifier, acquires a backed-up upgrade program according to the acquired identifier, and replaces the original program in the configuration file content with the acquired backed-up upgrade program.
6. The method according to any one of claims 1 to 5, wherein the generation process of the upgrade package comprises:
obtaining upgrading content;
compiling and packaging the upgrading content to generate the upgrading package.
7. The method according to any one of claims 1 to 5, further comprising:
the version publishing node receives an upgrading script operation request, acquires an upgrading script corresponding to the upgrading script operation request, calls a module corresponding to the upgrading script operation request in an idle and sends the upgrading script to a remote node in batches;
and the remote node runs the upgrading script after receiving the upgrading script, and sends a script running result to the version release node after the running is finished.
8. The upgrading device of the distributed system is characterized by comprising a version release node and a remote node;
the version publishing node is used for receiving an upgrading request, acquiring an upgrading packet corresponding to the upgrading request, calling a module corresponding to the upgrading request in an idle, and sending the upgrading packet to remote nodes in batches, wherein the upgrading packet comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrading program required by the remote nodes;
the remote node is used for acquiring the identification after receiving the corresponding upgrade package, identifying the configuration file content in the upgrade package, matching the upgrade program of the system according to the identification, replacing the original program in the configuration file content with the acquired upgrade program, and sending an upgrade result to the version release node after the upgrade is completed.
9. The apparatus of claim 8, wherein the name suffix of the configuration file content in the upgrade package is a host name of the corresponding remote node.
10. A computer system, comprising:
one or more processors; and
a memory associated with the one or more processors for storing program instructions that, when read and executed by the one or more processors, perform operations comprising:
the method comprises the steps that a version release node receives an upgrade request, acquires an upgrade package corresponding to the upgrade request, calls a module corresponding to the upgrade request in an idle and sends the upgrade package to remote nodes in batches, wherein the upgrade package comprises a configuration file, and the configuration file carries an identifier corresponding to an upgrade program required by the remote nodes;
and after receiving the corresponding upgrade package, the remote node acquires the identifier, identifies the content of the configuration file in the upgrade package, matches the upgrade program of the system according to the identifier, replaces the original program in the content of the configuration file with the acquired upgrade program, and sends an upgrade result to the version release node after the upgrade is finished.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010443494.6A CN111752581B (en) | 2020-05-22 | 2020-05-22 | Upgrading method and device of distributed system and computer system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010443494.6A CN111752581B (en) | 2020-05-22 | 2020-05-22 | Upgrading method and device of distributed system and computer system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111752581A true CN111752581A (en) | 2020-10-09 |
| CN111752581B CN111752581B (en) | 2024-06-28 |
Family
ID=72674078
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010443494.6A Active CN111752581B (en) | 2020-05-22 | 2020-05-22 | Upgrading method and device of distributed system and computer system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111752581B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112434008A (en) * | 2020-11-18 | 2021-03-02 | 星环信息科技(上海)股份有限公司 | Distributed database upgrading method, device and medium |
| CN112925544A (en) * | 2021-02-26 | 2021-06-08 | 湖南强智科技发展有限公司 | Method and device for updating application program, electronic equipment and computer storage medium |
| CN115001957A (en) * | 2022-05-26 | 2022-09-02 | 苏州思萃工业互联网技术研究所有限公司 | System and method for quickly and automatically upgrading software |
| CN115080149A (en) * | 2022-07-20 | 2022-09-20 | 荣耀终端有限公司 | Terminal device control method and terminal device |
| CN115955399A (en) * | 2022-12-12 | 2023-04-11 | 安芯网盾(北京)科技有限公司 | Grading method and system for distributed multi-node detection engine |
| CN116661821A (en) * | 2023-05-10 | 2023-08-29 | 浙江简捷物联科技有限公司 | Application upgrading method and device, electronic equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030233648A1 (en) * | 2002-06-12 | 2003-12-18 | Earl William J. | System and method for managing software upgrades in a distributed computing system |
| US20120210312A1 (en) * | 2009-10-26 | 2012-08-16 | Zte Corporation | Software upgrading method, software upgrading system and client |
| CN104468235A (en) * | 2014-12-25 | 2015-03-25 | 浙江中控研究院有限公司 | Allocable full-network remote node firmware upgrading system and device based on IAP |
| CN105071971A (en) * | 2015-08-26 | 2015-11-18 | 广州云宏信息科技股份有限公司 | Method for automatically upgrading server side |
| US20180004503A1 (en) * | 2016-06-29 | 2018-01-04 | Vmware, Inc. | Automated upgradesystem for a service-based distributed computer system |
| CN110333889A (en) * | 2019-07-19 | 2019-10-15 | 浪潮云信息技术有限公司 | The upgrade method and system of container service user's cluster |
| CN110855501A (en) * | 2019-11-21 | 2020-02-28 | 广州西麦科技股份有限公司 | Batch publishing system, method and storage medium for creating middleware |
-
2020
- 2020-05-22 CN CN202010443494.6A patent/CN111752581B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030233648A1 (en) * | 2002-06-12 | 2003-12-18 | Earl William J. | System and method for managing software upgrades in a distributed computing system |
| US20120210312A1 (en) * | 2009-10-26 | 2012-08-16 | Zte Corporation | Software upgrading method, software upgrading system and client |
| CN104468235A (en) * | 2014-12-25 | 2015-03-25 | 浙江中控研究院有限公司 | Allocable full-network remote node firmware upgrading system and device based on IAP |
| CN105071971A (en) * | 2015-08-26 | 2015-11-18 | 广州云宏信息科技股份有限公司 | Method for automatically upgrading server side |
| US20180004503A1 (en) * | 2016-06-29 | 2018-01-04 | Vmware, Inc. | Automated upgradesystem for a service-based distributed computer system |
| CN110333889A (en) * | 2019-07-19 | 2019-10-15 | 浪潮云信息技术有限公司 | The upgrade method and system of container service user's cluster |
| CN110855501A (en) * | 2019-11-21 | 2020-02-28 | 广州西麦科技股份有限公司 | Batch publishing system, method and storage medium for creating middleware |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112434008A (en) * | 2020-11-18 | 2021-03-02 | 星环信息科技(上海)股份有限公司 | Distributed database upgrading method, device and medium |
| CN112925544A (en) * | 2021-02-26 | 2021-06-08 | 湖南强智科技发展有限公司 | Method and device for updating application program, electronic equipment and computer storage medium |
| CN115001957A (en) * | 2022-05-26 | 2022-09-02 | 苏州思萃工业互联网技术研究所有限公司 | System and method for quickly and automatically upgrading software |
| CN115001957B (en) * | 2022-05-26 | 2024-05-28 | 苏州思萃工业互联网技术研究所有限公司 | System and method for rapidly and automatically upgrading software |
| CN115080149A (en) * | 2022-07-20 | 2022-09-20 | 荣耀终端有限公司 | Terminal device control method and terminal device |
| CN115080149B (en) * | 2022-07-20 | 2023-06-27 | 荣耀终端有限公司 | Control method of terminal equipment and terminal equipment |
| CN115955399A (en) * | 2022-12-12 | 2023-04-11 | 安芯网盾(北京)科技有限公司 | Grading method and system for distributed multi-node detection engine |
| CN115955399B (en) * | 2022-12-12 | 2023-09-15 | 安芯网盾(北京)科技有限公司 | Method and system for upgrading and downgrading distributed multi-node detection engine |
| CN116661821A (en) * | 2023-05-10 | 2023-08-29 | 浙江简捷物联科技有限公司 | Application upgrading method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111752581B (en) | 2024-06-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111752581B (en) | Upgrading method and device of distributed system and computer system | |
| KR102493449B1 (en) | Edge computing test methods, devices, electronic devices and computer-readable media | |
| EP3828701B1 (en) | Mini app processing method, server, device and storage medium | |
| WO2024077885A1 (en) | Management method, apparatus and device for container cluster, and non-volatile readable storage medium | |
| KR20210040850A (en) | Method, apparatus, device, and storage medium for parsing document | |
| CN106502717B (en) | Application program running method and device | |
| CN111580926A (en) | Model publishing method, model deploying method, model publishing device, model deploying device, model publishing equipment and storage medium | |
| CN102262555B (en) | Method and device for loading different versions of JAVA three-party library | |
| CN116301951B (en) | Micro-service application installation upgrading method and device based on kubernetes | |
| CN114968406B (en) | Plug-in management method and device, electronic equipment and storage medium | |
| CN112131208A (en) | Full data migration method, device and equipment and computer readable storage medium | |
| CN112214388A (en) | Memory monitoring method, device, equipment and computer readable storage medium | |
| CN111158743B (en) | Big data operation and maintenance management platform | |
| CN116436794A (en) | OPC real-time data integration and control method based on Internet of things model | |
| CN113656001A (en) | Platform component development method and device, computer equipment and storage medium | |
| CN116662039B (en) | Industrial information parallel detection method, device and medium based on shared memory | |
| CN113760462A (en) | Method and device for constructing verification environment of dispatching automation system | |
| CN111258618A (en) | File configuration method and device, computer equipment and storage medium | |
| CN110806891A (en) | Method and device for generating software version of embedded equipment | |
| CN116248526A (en) | Method and device for deploying container platform and electronic equipment | |
| CN115509531A (en) | Micro front end implementation method, device, terminal and storage medium based on front end technology | |
| CN114510334A (en) | Class instance calling method and device, electronic equipment and automatic driving vehicle | |
| CN111190693B (en) | Method and device for building cloud platform based on Kunpeng platform | |
| CN113553065A (en) | Code file publishing method and device | |
| CN113326098A (en) | Cloud management platform supporting KVM virtualization and container virtualization |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |