CN106953746A - Clustered node upgrade-system and method - Google Patents
Clustered node upgrade-system and method Download PDFInfo
- Publication number
- CN106953746A CN106953746A CN201710117288.4A CN201710117288A CN106953746A CN 106953746 A CN106953746 A CN 106953746A CN 201710117288 A CN201710117288 A CN 201710117288A CN 106953746 A CN106953746 A CN 106953746A
- Authority
- CN
- China
- Prior art keywords
- server
- file
- upgrade
- data
- cluster
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 158
- 238000013515 script Methods 0.000 claims abstract description 122
- 238000004458 analytical method Methods 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 7
- 230000001960 triggered effect Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000011112 process operation Methods 0.000 description 2
- 238000003860 storage Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of clustered node upgrade-system, the clustered node upgrade-system includes：First server and second server；Wherein, the first server includes：Sending module, for upgrade file to be sent to each server into the affiliated cluster of the first server by running ant scripts；The second server includes：Determining module, for when receiving the upgrade file of first server transmission, determining the corresponding process of the upgrade file, and close the process of determination；Parsing module, upgrade described in the second server the corresponding file data of data for when the process is closed, parsing the upgrade file to obtain upgrading data, and update.The invention also discloses a kind of clustered node upgrade method.The present invention realizes the automatic upgrading of the i.e. server of clustered node, and then realizes the upgrading of a patch multinode in cluster, reduces the upgrading flow of clustered node, substantially increases the upgrading efficiency of clustered node.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a system and a method for upgrading a cluster node.
Background
With the rapid development of the internet and the big data industry and the rapid development of smart phones, people can not live away from the internet at present, and in order to make network services faster and more stable, a common method is to adopt a cluster to disperse a large number of requests to different node responses to improve the response speed of a system.
At present, when nodes in a cluster need to be upgraded without requiring, the existing open-source framework is mainly adopted to upgrade the nodes by deploying software. However, the adoption of the upgrading method needs to develop a corresponding patch for each node, so that the node upgrading process is complex and the upgrading efficiency is low.
Disclosure of Invention
The invention provides a cluster node upgrading system and method, and aims to solve the technical problems of complex upgrading process and low upgrading efficiency of the existing cluster node.
In order to achieve the above object, the present invention provides a cluster node upgrade system, which includes: a first server and a second server; wherein,
the first server includes:
the sending module is used for sending the upgrading file to each server in the cluster to which the first server belongs by running an ant script;
the second server includes:
the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining a process corresponding to an upgrading file when the upgrading file sent by a first server is received, and closing the determined process;
and the analysis module is used for analyzing the upgrade file to obtain upgrade data and updating file data corresponding to the upgrade data in the second server when the process is closed.
In one embodiment, the upgrade data comprises: the deployment script corresponding to the source file data, the compiled file data and the configuration file; the analysis module comprises:
an updating unit, configured to update data corresponding to the source file data in the second server based on the source file data, and update data corresponding to the compiled file data in the second server based on the compiled file data;
and the running unit is used for running the deployment script to modify the data corresponding to the configuration file in the second server.
In an embodiment, the first server further comprises:
the acquisition module is used for acquiring source file data, compiled file data and a deployment script corresponding to the configuration file;
a generating module for generating the upgrade file based on the source file data, the compiled file data, and the deployment script.
In an embodiment, the second server further comprises:
and the backup module is used for carrying out backup operation on the file corresponding to the upgrade file so as to obtain a backup file.
In an embodiment, the second server further comprises:
the first starting module is used for starting the process based on the updated file data;
and the second starting module is used for starting the process based on the backup file when the process fails to be started.
In addition, to achieve the above object, the present invention further provides a cluster node upgrading method, where the cluster node upgrading method includes the following steps:
the method comprises the steps that a first server sends an upgrading file to each server in a cluster to which the first server belongs by running an ant script;
when an upgrade file sent by a first server is received, a second server determines a process corresponding to the upgrade file and closes the determined process;
and when the process is closed, the second server analyzes the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server.
In one embodiment, the upgrade data comprises: the deployment script corresponding to the source file data, the compiled file data and the configuration file;
the step of updating the file data corresponding to the upgrade data in the second server includes:
the second server updates data corresponding to the source file data in the second server based on the source file data, and updates data corresponding to the compiled file data in the second server based on the compiled file data;
and the second server runs the deployment script to modify the data corresponding to the configuration file in the second server.
In an embodiment, before the step of the first server sending the upgrade file to each server in the cluster to which the first server belongs by running an ant script, the method further includes:
the first server acquires source file data, compiled file data and a deployment script corresponding to a configuration file;
the first server generates the upgrade file based on the source file data, compiled file data, and the deployment script.
In an embodiment, after the closing the determined process and before the second server parses the upgrade file to obtain upgrade data, the method further comprises:
and the second server performs backup operation on the file corresponding to the upgrade file to obtain a backup file.
In an embodiment, after the step of updating the file data corresponding to the upgrade data in the second server, the method further includes:
the second server starts the process based on the updated file data;
when the process fails to start, the second server starts the process based on the backup file
According to the method, a sending module sends an upgrade file to each server in a cluster to which a first server belongs by running an ant script, then when the upgrade file sent by the first server is received, a determining module determines a process corresponding to the upgrade file and closes the determined process, and then when the process is closed, an analyzing module analyzes the upgrade file to obtain upgrade data and updates file data corresponding to the upgrade data in a second server; the automatic upgrading of cluster nodes, namely servers, is realized, the upgrading of one patch of multiple nodes in a cluster is further realized, the upgrading process of the cluster nodes is reduced, and the upgrading efficiency of the cluster nodes is greatly improved.
Drawings
FIG. 1 is a schematic structural diagram of a cluster in various embodiments of the present invention;
FIG. 2 is a functional block diagram of a first embodiment of a cluster node upgrade system according to the present invention;
FIG. 3 is a schematic diagram illustrating an upgrading process of cluster nodes in the cluster node upgrading system according to the present invention;
FIG. 4 is a diagram of a detailed functional module of an analysis module in a second embodiment of a cluster node upgrade system according to the present invention;
fig. 5 is a schematic diagram of a detailed functional module of a first server in a third embodiment of a cluster node upgrade system according to the present invention;
FIG. 6 is a diagram illustrating a detailed functional module of a second server in a fourth embodiment of a cluster node upgrade system according to the present invention;
FIG. 7 is a flowchart illustrating a cluster node upgrade method according to a first embodiment of the present invention;
fig. 8 is a schematic detailed flow chart of a step of updating file data corresponding to the update data in the second server in the second embodiment of the cluster node update method of the present invention;
FIG. 9 is a flowchart illustrating a cluster node upgrade method according to a third embodiment of the present invention;
fig. 10 is a flowchart illustrating a cluster node upgrade method according to a fourth embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Clustering refers to the process of collecting a plurality of nodes, i.e., servers, together to perform the same service, and can use a plurality of computers to perform parallel computation to obtain a high computation speed, and also can use a plurality of computers to perform backup, so that any one machine can damage the whole system or can normally operate.
Cluster nodes and servers implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.
Fig. 1 is a schematic hardware structure of a cluster for implementing various embodiments of the present invention.
In fig. 1, a cluster includes a load balancing server 1, a plurality of groups of application servers 2, and one or more groups of data servers 3, where the load balancing server 1 is configured to implement global load balancing of the cluster, implement traffic allocation between servers in different regions on a wide area network (including the internet), and use the best application server 2 to provide services for the nearest visitor, thereby ensuring quality of service. Because the cluster comprises a plurality of groups of application servers 2, when one application server 2 is interrupted due to invalidity, other application servers 2 can be allocated to provide services for the current visitor, so that the service quality of the cluster is further improved, and the availability of the cluster is improved.
Based on the hardware structure of the cluster, the embodiments of the present invention are provided.
The invention further provides a cluster node upgrading system. Referring to fig. 2, fig. 2 is a functional module schematic diagram of a first embodiment of upgrading a cluster node according to the present invention.
In this embodiment, the cluster node upgrade system includes: a first server 10 and a second server 20; wherein, the first server 10 includes:
a sending module 10, configured to send the upgrade file to each server in the cluster to which the first server belongs by running an ant script;
in this embodiment, the cluster is a server cluster, and the cluster node is a server in the cluster, where the first server is a server in the cluster for editing and generating the upgrade file. Before cluster node upgrading, namely server upgrading, patch packages, namely upgrading files are firstly manufactured, the patch package comprises a source file corresponding to the upgrade of the server, namely source file data, a compiled file, namely compiled file data, and a deployment script corresponding to a configuration file, namely a shell script, in each file of the patch package, the source file and the compiled file can directly cover the file in the server to be upgraded, the configuration files are related to the server environment, and different operating environments correspond to different configuration files, therefore, in the process of upgrading the server, the configuration file needs to be incrementally modified according to the actual situation, such as adding content, modifying content and/or deleting content, so that the modified content is arranged in the deployment script, and in the upgrading process of the server, modifying the configuration file of the server by running the shell script. The patch package further comprises upgrade node information, the upgrade node information comprises application node information, namely node information corresponding to an application server, and database node information, namely node information corresponding to a database server, the node information is uniformly configured in a local configuration file and is generally configured in properties files, then the node information is imported into an ant script, and an upgrade flow is concurrently distributed to each node through the ant script, so that the corresponding node, namely the server, is upgraded.
In an embodiment, after the user finishes editing the upgrade file, that is, the patch package, the sending module 10 sends the upgrade file to each server in the cluster to which the first server belongs by running the ant script, so that each server in the cluster performs a corresponding upgrade operation when receiving the upgrade file. Specifically, when the first server 10 receives a sending instruction, the sending module 10 sends the upgrade file to each server in the cluster to which the first server belongs by running the ant script, where the sending instruction may be a running instruction of the ant script or an instruction triggered by a user through a related control of a display interface of the first server.
The second server 20 includes:
the determining module 21 is configured to determine, when receiving an upgrade file sent by a first server, a process corresponding to the upgrade file, and close the determined process;
wherein, the second server 20 is another server except the first server 10 in the cluster to which the first server 10 belongs; or, the second server 20 is a server that needs to be upgraded in other servers except the first server 10 in the cluster to which the first server 10 belongs, and the patch package includes identification information corresponding to the second server, that is, when the patch package is manufactured, the identification information corresponding to the second server is stored in the patch package.
In this embodiment, when receiving an upgrade file sent by a first server, the determining module 21 determines a service corresponding to the upgrade file, further determines a process corresponding to the upgrade file, and then closes the determined process, so as to upgrade the service. Specifically, determination module 21 may call the container script directly or close the determined process by killing the process number by kill.
And the analysis module 22 is configured to analyze the upgrade file to obtain upgrade data when the process is closed, and update file data corresponding to the upgrade data in the second server.
In this embodiment, after the process is closed, the parsing module 22 parses the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server. The upgrade data comprises a source file corresponding to server upgrade, a compiled file and a deployment script corresponding to a configuration file, after the source file data, the compiled file data and the deployment script corresponding to the configuration file are obtained through analysis, an analysis module 22 updates data corresponding to the source file data in the second server based on the source file data, updates data corresponding to the compiled file data in the second server based on the compiled file data, and runs the deployment script to modify the data corresponding to the configuration file in the server to realize upgrade of the second server, so that upgrade of one patch multi-node in a cluster is realized, upgrade processes of cluster nodes are reduced, and upgrade efficiency of the cluster nodes is greatly improved.
Further, in an embodiment, the second server 20 further includes: and the deleting module is used for deleting the upgrading file when the file data corresponding to the upgrading data in the second server is updated.
In this embodiment, after the parsing module 22 updates the file data corresponding to the upgrade data in the second server, the deleting module deletes the upgrade file, so as to reduce the file data storage capacity of the second server, improve the resource utilization rate of the second server, and further improve the service quality of the second server.
Further, in an embodiment, the second server 20 further includes:
and the backup module is used for carrying out backup operation on the file corresponding to the upgrade file so as to obtain a backup file.
In this embodiment, in order to avoid that the second server cannot run the corresponding service and cannot be used by the second server when the second server is not upgraded successfully, when the patch package is obtained, the backup module performs a backup operation on the file corresponding to the patch package in the second server to obtain a backup file. Specifically, the obtained patch package includes a storage directory of a backup file and a directory of a file to be backed up, where the file to be backed up refers to a file related to the current upgrade, and includes data corresponding to the source file data in the second server, data corresponding to the compiled file data in the second server, and data corresponding to the configuration file in the server, so that when the service upgrade is unsuccessful, the process is run through the backup file, and it is ensured that the second server can run sequentially.
Taking fig. 3 as an example, fig. 3 is a schematic view of an upgrade flow of a cluster node in the cluster node upgrade system according to this embodiment. In fig. 3, step S1 is first executed: and (4) making the upgrade file and the patch, and executing the step (S2) when the patch is made: configuring node upgrade information, namely determining a node needing to be upgraded, namely a server, and then executing step S3: sending the upgrade file to each server, i.e. node 4, in the cluster to which the first server belongs by running an ant script according to a one-key upgrade instruction sending module, and when each server receives the upgrade file, executing step S4 according to the upgrade file: the method comprises the steps of stopping service, backing up, deploying and starting service, specifically, closing a determined process, backing up a file corresponding to an upgrade file, updating data corresponding to source file data in a second server based on the source file data, updating data corresponding to compiled file data in the second server based on the compiled file data, simultaneously running a deployment script to modify data corresponding to a configuration file in the second server, and running the upgraded process to enable the server to continuously provide the service corresponding to the process after the server is upgraded.
In the cluster node upgrading system provided by this embodiment, an ant script is run through a sending module 11 to send an upgrade file to each server in a cluster to which a first server belongs, then when the upgrade file sent by the first server is received, a determining module 21 determines a process corresponding to the upgrade file, and closes the determined process, and then when the process is closed, an analyzing module 22 analyzes the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in a second server; the automatic upgrading of cluster nodes, namely servers, is realized, the upgrading of one patch of multiple nodes in a cluster is further realized, the upgrading process of the cluster nodes is reduced, and the upgrading efficiency of the cluster nodes is greatly improved.
A second embodiment of the cluster node upgrade system according to the present invention is provided based on the first embodiment, and referring to fig. 4, in this embodiment, upgrade data includes source file data, compiled file data, and a deployment script corresponding to a configuration file; the parsing module 22 includes:
an updating unit 221, configured to update data corresponding to the source file data in the second server based on the source file data, and update data corresponding to the compiled file data in the second server based on the compiled file data;
in this embodiment, after analyzing the patch package to obtain the upgrade data including the source file data, the compiled file data, and the deployment script corresponding to the configuration file, the updating unit 221 first updates the data corresponding to the source file data in the second server based on the source file data, and updates the data corresponding to the compiled file data in the second server based on the compiled file data, specifically, the updating unit 221 determines the data corresponding to the source file data and the data corresponding to the compiled file data in the second server, and then directly overlays the source file data and the compiled file data on the corresponding data, so as to update the source file data and the compiled file data.
An operation unit 222, configured to operate the deployment script to modify data corresponding to the configuration file in the second server.
In this embodiment, when the deployment script, that is, the shell script, corresponding to the configuration file is acquired, the running unit 222 runs the deployment script to modify the data and the incremental modification configuration file corresponding to the configuration file in the second server, so as to delete, add, and modify the configuration file.
In the cluster node upgrade system provided in this embodiment, the update unit 221 updates data corresponding to the source file data in the second server based on the source file data, updates data corresponding to the compiled file data in the second server based on the compiled file data, and then the operation unit 222 operates the deployment script to modify data corresponding to the configuration file in the second server, so that automatic upgrade of a cluster node is achieved, a configuration file of the cluster node can be set, and efficiency of upgrading the cluster node is further improved.
Based on the first embodiment, a third embodiment of the cluster node upgrade system of the present invention is provided, and referring to fig. 5, in this embodiment, the first server 10 further includes:
an obtaining module 12, configured to obtain source file data, compiled file data, and a deployment script corresponding to a configuration file;
in this embodiment, when the upgrade file is manufactured, the first server 10 acquires the source file data, the compiled file data, and the deployment script corresponding to the configuration file through the acquisition module 12, specifically, an administrator may edit the source file data through the first server 10, compile the source file data to obtain the compiled file data, and edit the deployment script corresponding to the configuration file.
A generating module 13, configured to generate the upgrade file based on the source file data, the compiled file data, and the deployment script.
In this embodiment, when the obtaining module 12 obtains the source file data, the compiled file data, and the deployment script corresponding to the configuration file, the generating module 13 generates the upgrade file based on the source file data, the compiled file data, and the deployment script. Specifically, when a manager finishes editing a source file data, deploys a script, and obtains compiled file data through compiling, the generation of a current editing interface or line selection for making an upgrade file is used for making the upgrade file, and when the upgrade file is made, the sending module 11 sends the upgrade file to each server in a cluster to which the first server belongs by running an ant script, so that each server can upgrade the server according to the received upgrade file.
According to the cluster node upgrading system provided by the embodiment, the obtaining module 12 obtains the source file data, the compiled file data and the deployment script corresponding to the configuration file, and the generating module 13 generates the upgrading file based on the source file data, the compiled file data and the deployment script, so that the first server can manufacture the upgrading file according to the source file data, the compiled file data and the deployment script, the second server can be accurately upgraded, and the upgrading efficiency of the cluster node is further improved.
Based on the first embodiment, a fourth embodiment of the cluster node upgrade system of the present invention is provided, and referring to fig. 6, in this embodiment, the second server 20 further includes:
a first starting module 23, configured to start the process based on the updated file data;
in this embodiment, after the file data corresponding to the upgrade data in the second server is updated, the first starting module 23 starts the process based on the updated file data to determine that the updated second service can smoothly run, so that the second server can continue to provide the corresponding service for the user.
And a second starting module 24, configured to start the process based on the backup file when the process fails to be started.
In this embodiment, when the process operation fails, the current second server fails to upgrade, and the upgraded process cannot be operated again, so that the second starting module 24 operates the corresponding process through the backup file, so as to ensure smooth operation of the server, and avoid unnecessary influence on the user due to the fact that the server cannot operate and influence the normal service in the cluster.
In the cluster node upgrade system provided in this embodiment, the first starting module 23 starts the process based on the updated file data, and then the second starting module 24 starts the process based on the backup file when the process fails to start, so as to avoid unnecessary influence on a user due to the fact that a server cannot operate in a cluster to affect normal service, thereby ensuring that the cluster can normally provide service for the user.
The invention provides a cluster node upgrading method. Referring to fig. 7, fig. 7 is a flowchart illustrating a cluster node upgrading method according to a first embodiment of the present invention.
In this embodiment, the system and method for upgrading cluster nodes includes:
step S710, a first server sends an upgrade file to each server in a cluster to which the first server belongs by running an ant script;
in this embodiment, the cluster is a server cluster, and the cluster node is a server in the cluster, where the first server is a server in the cluster for editing and generating the upgrade file. Before cluster node upgrading, namely server upgrading, patch packages, namely upgrading files are firstly manufactured, the patch package comprises a source file corresponding to the upgrade of the server, namely source file data, a compiled file, namely compiled file data, and a deployment script corresponding to a configuration file, namely a shell script, in each file of the patch package, the source file and the compiled file can directly cover the file in the server to be upgraded, the configuration files are related to the server environment, and different operating environments correspond to different configuration files, therefore, in the process of upgrading the server, the configuration file needs to be incrementally modified according to the actual situation, such as adding content, modifying content and/or deleting content, so that the modified content is arranged in the deployment script, and in the upgrading process of the server, modifying the configuration file of the server by running the shell script. The patch package further comprises upgrade node information, the upgrade node information comprises application node information, namely node information corresponding to an application server, and database node information, namely node information corresponding to a database server, the node information is uniformly configured in a local configuration file and is generally configured in properties files, then the node information is imported into an ant script, and an upgrade flow is concurrently distributed to each node through the ant script, so that the corresponding node, namely the server, is upgraded.
In an embodiment, after the user finishes editing the upgrade file, that is, the patch package, the sending module 10 sends the upgrade file to each server in the cluster to which the first server belongs by running the ant script, so that each server in the cluster performs a corresponding upgrade operation when receiving the upgrade file. Specifically, when the first server 10 receives a sending instruction, the sending module 10 sends the upgrade file to each server in the cluster to which the first server belongs by running the ant script, where the sending instruction may be a running instruction of the ant script or an instruction triggered by a user through a related control of a display interface of the first server.
Step S720, when receiving the upgrade file sent by the first server, the second server determines the process corresponding to the upgrade file and closes the determined process;
wherein, the second server 20 is another server except the first server 10 in the cluster to which the first server 10 belongs; or, the second server 20 is a server that needs to be upgraded in other servers except the first server 10 in the cluster to which the first server 10 belongs, and the patch package includes identification information corresponding to the second server, that is, when the patch package is manufactured, the identification information corresponding to the second server is stored in the patch package.
In this embodiment, when receiving an upgrade file sent by a first server, the determining module 21 determines a service corresponding to the upgrade file, further determines a process corresponding to the upgrade file, and then closes the determined process, so as to upgrade the service. Specifically, determination module 21 may call the container script directly or close the determined process by killing the process number by kill.
Step S730, when the process is closed, the second server parses the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server.
In this embodiment, after the process is closed, the parsing module 22 parses the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server. The upgrade data comprises a source file corresponding to server upgrade, a compiled file and a deployment script corresponding to a configuration file, after the source file data, the compiled file data and the deployment script corresponding to the configuration file are obtained through analysis, an analysis module 22 updates data corresponding to the source file data in the second server based on the source file data, updates data corresponding to the compiled file data in the second server based on the compiled file data, and runs the deployment script to modify the data corresponding to the configuration file in the server to realize upgrade of the second server, so that upgrade of one patch multi-node in a cluster is realized, upgrade processes of cluster nodes are reduced, and upgrade efficiency of the cluster nodes is greatly improved.
Further, after step S720 and before step S730, the method further includes: and the second server performs backup operation on the file corresponding to the upgrade file to obtain a backup file.
In this embodiment, in order to avoid that the second server cannot run the corresponding service and cannot be used by the second server when the second server is not upgraded successfully, when the patch package is obtained, the backup module performs a backup operation on the file corresponding to the patch package in the second server to obtain a backup file. Specifically, the obtained patch package includes a storage directory of a backup file and a directory of a file to be backed up, where the file to be backed up refers to a file related to the current upgrade, and includes data corresponding to the source file data in the second server, data corresponding to the compiled file data in the second server, and data corresponding to the configuration file in the server, so that when the service upgrade is unsuccessful, the process is run through the backup file, and it is ensured that the second server can run sequentially.
Taking fig. 3 as an example, fig. 3 is a schematic view of an upgrade flow of a cluster node in the cluster node upgrade system according to this embodiment. In fig. 3, step S1 is first executed: and (4) making the upgrade file and the patch, and executing the step (S2) when the patch is made: configuring node upgrade information, namely determining a node needing to be upgraded, namely a server, and then executing step S3: sending the upgrade file to each server, i.e. node 4, in the cluster to which the first server belongs by running an ant script according to a one-key upgrade instruction sending module, and when each server receives the upgrade file, executing step S4 according to the upgrade file: the method comprises the steps of stopping service, backing up, deploying and starting service, specifically, closing a determined process, backing up a file corresponding to an upgrade file, updating data corresponding to source file data in a second server based on the source file data, updating data corresponding to compiled file data in the second server based on the compiled file data, simultaneously running a deployment script to modify data corresponding to a configuration file in the second server, and running the upgraded process to enable the server to continuously provide the service corresponding to the process after the server is upgraded.
In the cluster node upgrading method provided by this embodiment, an ant script is run through a sending module 11 to send an upgrade file to each server in a cluster to which a first server belongs, then when the upgrade file sent by the first server is received, a determining module 21 determines a process corresponding to the upgrade file, and closes the determined process, and then when the process is closed, an analyzing module 22 analyzes the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in a second server; the automatic upgrading of cluster nodes, namely servers, is realized, the upgrading of one patch of multiple nodes in a cluster is further realized, the upgrading process of the cluster nodes is reduced, and the upgrading efficiency of the cluster nodes is greatly improved.
A second embodiment of the cluster node upgrade method according to the present invention is provided based on the first embodiment, and referring to fig. 8, in this embodiment, upgrade data includes source file data, compiled file data, and a deployment script corresponding to a configuration file; step S730 includes:
step S831, the second server updates data corresponding to the source file data in the second server based on the source file data, and updates data corresponding to the compiled file data in the second server based on the compiled file data;
in this embodiment, after analyzing the patch package to obtain the upgrade data including the source file data, the compiled file data, and the deployment script corresponding to the configuration file, the updating unit 211 updates the data corresponding to the source file data in the second server based on the source file data, and updates the data corresponding to the compiled file data in the second server based on the compiled file data, specifically, the updating unit 211 determines the data corresponding to the source file data and the data corresponding to the compiled file data in the second server, and then directly overlays the source file data and the compiled file data on the corresponding data, so as to update the source file data and the compiled file data.
In step S832, the second server runs the deployment script to modify the data corresponding to the configuration file in the second server.
In this embodiment, when the deployment script, that is, the shell script, corresponding to the configuration file is acquired, the running unit 212 runs the deployment script to modify the data and the incremental modification configuration file corresponding to the configuration file in the second server, so as to delete, add, and modify the configuration file.
In the cluster node upgrade method provided in this embodiment, the update unit 211 updates data corresponding to the source file data in the second server based on the source file data, updates data corresponding to the compiled file data in the second server based on the compiled file data, and then the operation unit 212 operates the deployment script to modify data corresponding to the configuration file in the second server, so that automatic upgrade of a cluster node is achieved, a configuration file of the cluster node can be set, and efficiency of upgrading the cluster node is further improved.
A third embodiment of the cluster node upgrade method according to the present invention is provided based on the first embodiment, and referring to fig. 9, in this embodiment, the method includes:
step S910, the first server obtains source file data, compiled file data and a deployment script corresponding to a configuration file;
in this embodiment, when the upgrade file is manufactured, the first server 10 acquires the source file data, the compiled file data, and the deployment script corresponding to the configuration file through the acquisition module 12, specifically, an administrator may edit the source file data through the first server 10, compile the source file data to obtain the compiled file data, and edit the deployment script corresponding to the configuration file.
Step S920, the first server generates the upgrade file based on the source file data, the compiled file data, and the deployment script.
In this embodiment, when the obtaining module 12 obtains the source file data, the compiled file data, and the deployment script corresponding to the configuration file, the generating module 13 generates the upgrade file based on the source file data, the compiled file data, and the deployment script. Specifically, when a manager finishes editing a source file data, deploys a script, and obtains compiled file data through compiling, the generation of a current editing interface or line selection for making an upgrade file is used for making the upgrade file, and when the upgrade file is made, the sending module 11 sends the upgrade file to each server in a cluster to which the first server belongs by running an ant script, so that each server can upgrade the server according to the received upgrade file.
Step S930, the first server sends the upgrade file to each server in the cluster to which the first server belongs by running an ant script;
in this embodiment, the cluster is a server cluster, and the cluster node is a server in the cluster, where the first server is a server in the cluster for editing and generating the upgrade file. Before cluster node upgrading, namely server upgrading, patch packages, namely upgrading files are firstly manufactured, the patch package comprises a source file corresponding to the upgrade of the server, namely source file data, a compiled file, namely compiled file data, and a deployment script corresponding to a configuration file, namely a shell script, in each file of the patch package, the source file and the compiled file can directly cover the file in the server to be upgraded, the configuration files are related to the server environment, and different operating environments correspond to different configuration files, therefore, in the process of upgrading the server, the configuration file needs to be incrementally modified according to the actual situation, such as adding content, modifying content and/or deleting content, so that the modified content is arranged in the deployment script, and in the upgrading process of the server, modifying the configuration file of the server by running the shell script. The patch package further comprises upgrade node information, the upgrade node information comprises application node information, namely node information corresponding to an application server, and database node information, namely node information corresponding to a database server, the node information is uniformly configured in a local configuration file and is generally configured in properties files, then the node information is imported into an ant script, and an upgrade flow is concurrently distributed to each node through the ant script, so that the corresponding node, namely the server, is upgraded.
In an embodiment, after the user finishes editing the upgrade file, that is, the patch package, the sending module 10 sends the upgrade file to each server in the cluster to which the first server belongs by running the ant script, so that each server in the cluster performs a corresponding upgrade operation when receiving the upgrade file. Specifically, when the first server 10 receives a sending instruction, the sending module 10 sends the upgrade file to each server in the cluster to which the first server belongs by running the ant script, where the sending instruction may be a running instruction of the ant script or an instruction triggered by a user through a related control of a display interface of the first server.
Step S940, when receiving the upgrade file sent by the first server, the second server determines the process corresponding to the upgrade file and closes the determined process;
wherein, the second server 20 is another server except the first server 10 in the cluster to which the first server 10 belongs; or, the second server 20 is a server that needs to be upgraded in other servers except the first server 10 in the cluster to which the first server 10 belongs, and the patch package includes identification information corresponding to the second server, that is, when the patch package is manufactured, the identification information corresponding to the second server is stored in the patch package.
In this embodiment, when receiving an upgrade file sent by a first server, the determining module 21 determines a service corresponding to the upgrade file, further determines a process corresponding to the upgrade file, and then closes the determined process, so as to upgrade the service. Specifically, determination module 21 may call the container script directly or close the determined process by killing the process number by kill.
Step S950, when the process is closed, the second server analyzes the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server.
In this embodiment, after the process is closed, the parsing module 22 parses the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server. The upgrade data comprises a source file corresponding to server upgrade, a compiled file and a deployment script corresponding to a configuration file, after the source file data, the compiled file data and the deployment script corresponding to the configuration file are obtained through analysis, an analysis module 22 updates data corresponding to the source file data in the second server based on the source file data, updates data corresponding to the compiled file data in the second server based on the compiled file data, and runs the deployment script to modify the data corresponding to the configuration file in the server to realize upgrade of the second server, so that upgrade of one patch multi-node in a cluster is realized, upgrade processes of cluster nodes are reduced, and upgrade efficiency of the cluster nodes is greatly improved.
According to the cluster node upgrading method provided by the embodiment, the obtaining module 12 obtains the source file data, the compiled file data and the deployment script corresponding to the configuration file, and the generating module 13 generates the upgrading file based on the source file data, the compiled file data and the deployment script, so that the first server can make the upgrading file according to the source file data, the compiled file data and the deployment script, the second server can be accurately upgraded, and the upgrading efficiency of the cluster node is further improved.
A fourth embodiment of the cluster node upgrade method according to the present invention is provided based on the first embodiment, and referring to fig. 10, in this embodiment, the method includes:
step S101, a first server sends an upgrade file to each server in a cluster to which the first server belongs by running an ant script;
in this embodiment, the cluster is a server cluster, and the cluster node is a server in the cluster, where the first server is a server in the cluster for editing and generating the upgrade file. Before cluster node upgrading, namely server upgrading, patch packages, namely upgrading files are firstly manufactured, the patch package comprises a source file corresponding to the upgrade of the server, namely source file data, a compiled file, namely compiled file data, and a deployment script corresponding to a configuration file, namely a shell script, in each file of the patch package, the source file and the compiled file can directly cover the file in the server to be upgraded, the configuration files are related to the server environment, and different operating environments correspond to different configuration files, therefore, in the process of upgrading the server, the configuration file needs to be incrementally modified according to the actual situation, such as adding content, modifying content and/or deleting content, so that the modified content is arranged in the deployment script, and in the upgrading process of the server, modifying the configuration file of the server by running the shell script. The patch package further comprises upgrade node information, the upgrade node information comprises application node information, namely node information corresponding to an application server, and database node information, namely node information corresponding to a database server, the node information is uniformly configured in a local configuration file and is generally configured in properties files, then the node information is imported into an ant script, and an upgrade flow is concurrently distributed to each node through the ant script, so that the corresponding node, namely the server, is upgraded.
In an embodiment, after the user finishes editing the upgrade file, that is, the patch package, the sending module 10 sends the upgrade file to each server in the cluster to which the first server belongs by running the ant script, so that each server in the cluster performs a corresponding upgrade operation when receiving the upgrade file. Specifically, when the first server 10 receives a sending instruction, the sending module 10 sends the upgrade file to each server in the cluster to which the first server belongs by running the ant script, where the sending instruction may be a running instruction of the ant script or an instruction triggered by a user through a related control of a display interface of the first server.
Step S102, when receiving an upgrade file sent by a first server, a second server determines a process corresponding to the upgrade file and closes the determined process;
wherein, the second server 20 is another server except the first server 10 in the cluster to which the first server 10 belongs; or, the second server 20 is a server that needs to be upgraded in other servers except the first server 10 in the cluster to which the first server 10 belongs, and the patch package includes identification information corresponding to the second server, that is, when the patch package is manufactured, the identification information corresponding to the second server is stored in the patch package.
In this embodiment, when receiving an upgrade file sent by a first server, the determining module 21 determines a service corresponding to the upgrade file, further determines a process corresponding to the upgrade file, and then closes the determined process, so as to upgrade the service. Specifically, determination module 21 may call the container script directly or close the determined process by killing the process number by kill.
Step S103, when the process is closed, the second server analyzes the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server.
In this embodiment, after the process is closed, the parsing module 22 parses the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server. The upgrade data comprises a source file corresponding to server upgrade, a compiled file and a deployment script corresponding to a configuration file, after the source file data, the compiled file data and the deployment script corresponding to the configuration file are obtained through analysis, an analysis module 22 updates data corresponding to the source file data in the second server based on the source file data, updates data corresponding to the compiled file data in the second server based on the compiled file data, and runs the deployment script to modify the data corresponding to the configuration file in the server to realize upgrade of the second server, so that upgrade of one patch multi-node in a cluster is realized, upgrade processes of cluster nodes are reduced, and upgrade efficiency of the cluster nodes is greatly improved.
Step S104, the second server starts the process based on the updated file data;
in this embodiment, after the file data corresponding to the upgrade data in the second server is updated, the first starting module 23 starts the process based on the updated file data to determine that the updated second service can smoothly run, so that the second server can continue to provide the corresponding service for the user.
Step S105, when the process fails to be started, the second server starts the process based on the backup file.
In this embodiment, when the process operation fails, the current second server fails to upgrade, and the upgraded process cannot be operated again, so that the second starting module 24 operates the corresponding process through the backup file, so as to ensure smooth operation of the server, and avoid unnecessary influence on the user due to the fact that the server cannot operate and influence the normal service in the cluster.
In the cluster node upgrading method provided in this embodiment, the process is started by the first starting module 23 based on the updated file data, and then the process is started by the second starting module 24 based on the backup file when the process is failed to be started, so that unnecessary influence on a user due to the fact that a server cannot operate to affect normal service in a cluster is avoided, and the cluster is ensured to be capable of providing service for the user normally.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A cluster node upgrade system, comprising: a first server and a second server; wherein,
the first server includes:
the sending module is used for sending the upgrading file to each server in the cluster to which the first server belongs by running an ant script;
the second server includes:
the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining a process corresponding to an upgrading file when the upgrading file sent by a first server is received, and closing the determined process;
and the analysis module is used for analyzing the upgrade file to obtain upgrade data and updating file data corresponding to the upgrade data in the second server when the process is closed.
2. The cluster node upgrade system according to claim 1, wherein the upgrade data comprises: the deployment script corresponding to the source file data, the compiled file data and the configuration file; the analysis module comprises:
an updating unit, configured to update data corresponding to the source file data in the second server based on the source file data, and update data corresponding to the compiled file data in the second server based on the compiled file data;
and the running unit is used for running the deployment script to modify the data corresponding to the configuration file in the second server.
3. The cluster node upgrade system according to claim 1, wherein the first server further comprises:
the acquisition module is used for acquiring source file data, compiled file data and a deployment script corresponding to the configuration file;
a generating module for generating the upgrade file based on the source file data, the compiled file data, and the deployment script.
4. The cluster node upgrade system according to any one of claims 1 to 3, wherein the second server further comprises:
and the backup module is used for carrying out backup operation on the file corresponding to the upgrade file so as to obtain a backup file.
5. The cluster node upgrade system according to claim 4, wherein the second server further comprises:
the first starting module is used for starting the process based on the updated file data;
and the second starting module is used for starting the process based on the backup file when the process fails to be started.
6. A cluster node upgrading method is characterized by comprising the following steps:
the method comprises the steps that a first server sends an upgrading file to each server in a cluster to which the first server belongs by running an ant script;
when an upgrade file sent by a first server is received, a second server determines a process corresponding to the upgrade file and closes the determined process;
and when the process is closed, the second server analyzes the upgrade file to obtain upgrade data, and updates file data corresponding to the upgrade data in the second server.
7. The cluster node upgrade method of claim 6, wherein the upgrade data comprises: the deployment script corresponding to the source file data, the compiled file data and the configuration file;
the step of updating the file data corresponding to the upgrade data in the second server includes:
the second server updates data corresponding to the source file data in the second server based on the source file data, and updates data corresponding to the compiled file data in the second server based on the compiled file data;
and the second server runs the deployment script to modify the data corresponding to the configuration file in the second server.
8. The cluster node upgrade method of claim 6, wherein before the step of the first server sending an upgrade file to each server in the cluster to which the first server belongs by running an ant script, the method further comprises:
the first server acquires source file data, compiled file data and a deployment script corresponding to a configuration file;
the first server generates the upgrade file based on the source file data, compiled file data, and the deployment script.
9. The cluster node upgrade method of any of claims 6 to 8, wherein after the shutting down of the determined process and before the second server parses the upgrade file to obtain upgrade data, the method further comprises:
and the second server performs backup operation on the file corresponding to the upgrade file to obtain a backup file.
10. The cluster node upgrade method of claim 9, wherein after the step of updating the file data corresponding to the upgrade data in the second server, the method further comprises:
the second server starts the process based on the updated file data;
and when the process fails to start, the second server starts the process based on the backup file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710117288.4A CN106953746A (en) | 2017-02-28 | 2017-02-28 | Clustered node upgrade-system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710117288.4A CN106953746A (en) | 2017-02-28 | 2017-02-28 | Clustered node upgrade-system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106953746A true CN106953746A (en) | 2017-07-14 |
Family
ID=59467480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710117288.4A Withdrawn CN106953746A (en) | 2017-02-28 | 2017-02-28 | Clustered node upgrade-system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106953746A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107634860A (en) * | 2017-10-09 | 2018-01-26 | 上海新炬网络信息技术股份有限公司 | A kind of weblogic clusters patch batch automatically updating method |
| CN108521342A (en) * | 2018-03-26 | 2018-09-11 | 北京奇艺世纪科技有限公司 | A kind of management method and device of cluster |
| CN108681461A (en) * | 2018-05-07 | 2018-10-19 | 广东电网有限责任公司 | A kind of clustered software system does not shut down newer method, system and relevant apparatus |
| CN108768726A (en) * | 2018-05-30 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of upgrade method and device of server cluster |
| CN109274521A (en) * | 2018-08-24 | 2019-01-25 | 郑州云海信息技术有限公司 | A kind of automatically updating method and device of distributed memory system mode |
| CN109445825A (en) * | 2018-11-09 | 2019-03-08 | 郑州云海信息技术有限公司 | The method and apparatus that a kind of server cluster system updates upgrading |
| CN109753300A (en) * | 2017-11-03 | 2019-05-14 | 阿里巴巴集团控股有限公司 | A kind of algorithm upgrade method, calculating task sending method and Related product |
| CN111930402A (en) * | 2020-08-27 | 2020-11-13 | 中山市天启智能科技有限公司 | Firmware upgrading method of cluster server and cluster server |
| CN112069152A (en) * | 2020-09-08 | 2020-12-11 | 北京达佳互联信息技术有限公司 | Database cluster upgrading method, device, equipment and storage medium |
| CN112579139A (en) * | 2020-12-09 | 2021-03-30 | 北京红山信息科技研究院有限公司 | Multi-cluster patch updating method, system, server and storage medium |
| CN114978938A (en) * | 2022-05-26 | 2022-08-30 | 西安易朴通讯技术有限公司 | Switch testing method, system and equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103455346A (en) * | 2013-08-19 | 2013-12-18 | 北京京东尚科信息技术有限公司 | Application program deployment method, deployment main control computer, deployment client side and cluster |
| CN104426976A (en) * | 2013-09-03 | 2015-03-18 | 方正宽带网络服务股份有限公司 | Online updating device and online updating method for virtual server cluster |
| CN104486394A (en) * | 2014-12-10 | 2015-04-01 | 杭州华三通信技术有限公司 | Non-interrupting service software upgrading method and device |
| CN105511911A (en) * | 2015-11-27 | 2016-04-20 | 青岛海信移动通信技术股份有限公司 | System firmware upgrade package generation method and device |
| CN105893070A (en) * | 2015-11-25 | 2016-08-24 | 乐视云计算有限公司 | Application SDK upgrading method and system |
-
2017
- 2017-02-28 CN CN201710117288.4A patent/CN106953746A/en not_active Withdrawn
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103455346A (en) * | 2013-08-19 | 2013-12-18 | 北京京东尚科信息技术有限公司 | Application program deployment method, deployment main control computer, deployment client side and cluster |
| CN104426976A (en) * | 2013-09-03 | 2015-03-18 | 方正宽带网络服务股份有限公司 | Online updating device and online updating method for virtual server cluster |
| CN104486394A (en) * | 2014-12-10 | 2015-04-01 | 杭州华三通信技术有限公司 | Non-interrupting service software upgrading method and device |
| CN105893070A (en) * | 2015-11-25 | 2016-08-24 | 乐视云计算有限公司 | Application SDK upgrading method and system |
| CN105511911A (en) * | 2015-11-27 | 2016-04-20 | 青岛海信移动通信技术股份有限公司 | System firmware upgrade package generation method and device |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107634860A (en) * | 2017-10-09 | 2018-01-26 | 上海新炬网络信息技术股份有限公司 | A kind of weblogic clusters patch batch automatically updating method |
| CN107634860B (en) * | 2017-10-09 | 2021-05-25 | 上海新炬网络信息技术股份有限公司 | Method for automatically upgrading weblogic cluster patches in batches |
| CN109753300B (en) * | 2017-11-03 | 2022-05-06 | 阿里巴巴集团控股有限公司 | Algorithm upgrading method, calculation task sending method and related device |
| CN109753300A (en) * | 2017-11-03 | 2019-05-14 | 阿里巴巴集团控股有限公司 | A kind of algorithm upgrade method, calculating task sending method and Related product |
| CN108521342A (en) * | 2018-03-26 | 2018-09-11 | 北京奇艺世纪科技有限公司 | A kind of management method and device of cluster |
| CN108681461A (en) * | 2018-05-07 | 2018-10-19 | 广东电网有限责任公司 | A kind of clustered software system does not shut down newer method, system and relevant apparatus |
| CN108768726A (en) * | 2018-05-30 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of upgrade method and device of server cluster |
| CN109274521A (en) * | 2018-08-24 | 2019-01-25 | 郑州云海信息技术有限公司 | A kind of automatically updating method and device of distributed memory system mode |
| CN109445825A (en) * | 2018-11-09 | 2019-03-08 | 郑州云海信息技术有限公司 | The method and apparatus that a kind of server cluster system updates upgrading |
| CN111930402A (en) * | 2020-08-27 | 2020-11-13 | 中山市天启智能科技有限公司 | Firmware upgrading method of cluster server and cluster server |
| CN111930402B (en) * | 2020-08-27 | 2024-05-07 | 中山市天启智能科技有限公司 | Firmware upgrading method of cluster server and cluster server |
| CN112069152A (en) * | 2020-09-08 | 2020-12-11 | 北京达佳互联信息技术有限公司 | Database cluster upgrading method, device, equipment and storage medium |
| CN112069152B (en) * | 2020-09-08 | 2023-10-03 | 北京达佳互联信息技术有限公司 | Database cluster upgrading method, device, equipment and storage medium |
| CN112579139A (en) * | 2020-12-09 | 2021-03-30 | 北京红山信息科技研究院有限公司 | Multi-cluster patch updating method, system, server and storage medium |
| CN114978938A (en) * | 2022-05-26 | 2022-08-30 | 西安易朴通讯技术有限公司 | Switch testing method, system and equipment |
| CN114978938B (en) * | 2022-05-26 | 2024-07-26 | 西安易朴通讯技术有限公司 | Switch testing method, system and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106953746A (en) | Clustered node upgrade-system and method | |
| CN109818902B (en) | Automatic service deployment method, service scheduling management module and EPG platform | |
| KR102259679B1 (en) | Network slice management method, unit and system | |
| WO2017161984A1 (en) | Method, device and system for deploying data clusters, and computer storage medium | |
| US20180157568A1 (en) | Predictive management of on-demand code execution | |
| CN111324571B (en) | Container cluster management method, device and system | |
| CN112118565A (en) | Multi-tenant service gray level publishing method and device, computer equipment and storage medium | |
| CN108572845B (en) | Upgrading method of distributed micro-service cluster and related system | |
| WO2017194990A1 (en) | Orchestrator for a virtual network platform as a service (vnpaas) | |
| CN110768807B (en) | Virtual resource method and device, virtual resource processing network element and storage medium | |
| CN107769949A (en) | A kind of application component dispositions method and deployment node | |
| CN102508693A (en) | Web server capacity expansion system based on virtual machine | |
| US20240111549A1 (en) | Method and apparatus for constructing android running environment | |
| CN112463290A (en) | Method, system, apparatus and storage medium for dynamically adjusting the number of computing containers | |
| CN111831191A (en) | Workflow configuration method and device, computer equipment and storage medium | |
| CN112698952A (en) | Unified management method and device for computing resources, computer equipment and storage medium | |
| US12035156B2 (en) | Communication method and apparatus for plurality of administrative domains | |
| CN115086166A (en) | Computing system, container network configuration method, and storage medium | |
| CN113419818A (en) | Basic component deployment method, device, server and storage medium | |
| CN104104701A (en) | Online service configuration updating method and system | |
| CN112905306A (en) | Multi-cluster container management method and device, electronic equipment and storage medium | |
| CN109660379B (en) | Network method, system and terminal | |
| CN115729590A (en) | Service deployment method, device, equipment and computer readable storage medium | |
| CN115129348A (en) | Resource updating method, device and equipment of application program and readable storage medium | |
| US11269615B2 (en) | Automatically orchestrating deployments of software-defined storage stacks |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20170714 |