CN111427605B - Distributed code automatic updating and deploying method and system based on docker - Google Patents
Distributed code automatic updating and deploying method and system based on docker Download PDFInfo
- Publication number
- CN111427605B CN111427605B CN202010539935.2A CN202010539935A CN111427605B CN 111427605 B CN111427605 B CN 111427605B CN 202010539935 A CN202010539935 A CN 202010539935A CN 111427605 B CN111427605 B CN 111427605B
- Authority
- CN
- China
- Prior art keywords
- test
- node
- code
- production environment
- docker
- 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.)
- Active
Links
- 238000004519 manufacturing process Methods 0.000 claims abstract description 128
- 101700041465 CICD Proteins 0.000 claims description 14
- 238000000034 method Methods 0.000 description 3
- 240000007419 Hura crepitans Species 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006011 modification reaction Methods 0.000 description 1
- 230000002085 persistent Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
The invention discloses a distributed code automatic updating and deploying method and system based on docker, wherein the method comprises the following steps: testing the test code; after the tested test codes are sent to the GIT version manager, the test codes are pushed to a first stable code node and a second stable code node; the first stable code node and the second stable code node are respectively mounted to a first production environment docker node and a second production environment docker node; switching the access flow to a second production environment docker node; the first stable code node loads the test code passing the test to a first production environment docker node and updates the test code; switching the access flow to a first production environment docker node; and the second stable code node mounts the test code passing the test to a second production environment docker node and then updates the test code. The invention realizes the perceptive seamless updating switching when the project codes are updated.
Description
Technical Field
The invention relates to the technical field of software code updating and deploying, in particular to a distributed code automatic updating and deploying method and system based on docker.
Background
With the rapid development of cloud computing, container technology is mature day by day and is applied more and more widely in various fields, in ordinary development or daily deployment, our traditional project management is to manually submit codes to a server through git or svn, and then manually synchronize the latest version of codes to a production environment by operation and maintenance personnel, and has the following disadvantages: 1. the project codes and the production environment are in the same server, and the generated environment cannot be accessed immediately as long as the server is generated to be down; 2. the manual operation of manually submitting the codes and updating the codes exists, and the error rate is considered to be high; 3. when the code is updated, the service interruption condition exists, and the use of the production environment is influenced.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a distributed code automatic updating and deploying method and system based on a docker, introduce the docker container technology and distributed storage, realize the unaware seamless updating and switching when updating the project code by utilizing multi-node updating and switching, and separate the code from the generated environment server, so that the environment is more stable and safer.
In order to solve the technical problems, the invention provides the following technical scheme: a distributed code automatic updating and deploying method based on docker comprises the following steps:
s1, mounting the GIT version manager in the first NFS storage unit to a socket node of the test environment;
s2, the GIT version manager receives the test codes and sends the test codes to a docker node in a test environment for testing;
s3, the testing environment docker node feeds back the testing code passing the test to the GIT version manager;
s4, the GIT version manager synchronously pushes the test codes passing the test to a first stable code node and a second stable code node of a second NFS storage unit;
s5, respectively mounting a first stable code node and a second stable code node in a second NFS storage unit to a first production environment docker node and a second production environment docker node;
s6, switching all access flows to a second production environment docker node by the gateway entrance;
s7, the first stable code node mounts the test code passing the test to a first production environment docker node;
s8, after the first production environment docker node receives and updates the test code passing the test,
the gateway inlet switches the access flow to a first production environment docker node;
s9, the second stable code node mounts the test code passing the test to a second production environment docker node, and the second production environment docker node receives and updates the test code passing the test;
and S10, the gateway entrance restarts the connection of the access flow between the first production environment docker node and the second production environment docker node, and the test code updating deployment through the test is finished.
Specifically, the step S3 further includes: the docker node in the test environment feeds back the test code which does not pass the test to the GIT version manager;
synchronously pushing the test codes which do not pass the test to a first stable code node and a second stable code node of a second NFS storage unit by the GIT version manager;
and respectively mounting the first stable code node and the second stable code node in the second NFS storage unit to the first production environment docker node and the second production environment docker node, and synchronously pushing the test codes which do not pass the test to the first production environment docker node and the second production environment docker node, so that the updating and the deployment of the test codes which do not pass the test are finished.
Specifically, in step S3, the docker node feeds back the test code that passes the test to the GIT version manager through the CICD pipeline;
in S4, the GIT version manager synchronously pushes the test code passing the test to the first stable code node and the second stable code node of the second NFS storage unit through the cic pipeline.
Specifically, the docker node in the test environment feeds back a test code which does not pass the test to the GIT version manager through a CICD pipeline;
the GIT version manager synchronously pushes the test codes which do not pass the test to a first stable code node and a second stable code node of a second NFS storage unit through a CICD pipeline;
and respectively mounting the first stable code node and the second stable code node in the second NFS storage unit to the first production environment docker node and the second production environment docker node, and synchronously pushing the test codes which do not pass the test to the first production environment docker node and the second production environment docker node through a CICD pipeline.
The invention also aims to provide a docker-based distributed code automatic updating and deploying system, which comprises a first NFS storage unit, a second NFS storage unit, a test environment unit, an online production environment unit and a gateway entry unit, wherein the first NFS storage unit comprises a GIT version manager, the second NFS storage unit comprises a first stable code node module and a second stable code node module, the test environment unit comprises a test environment docker node module, and the online production environment unit comprises a first production environment docker node module and a second production environment docker node module;
the first NFS storage unit is used for mounting a GIT version manager to a socket node module in a test environment;
the GIT version manager is used for receiving the test codes and sending the test codes to the socket node module of the test environment unit;
the testing environment docker node module is used for testing the testing code and confirming whether the testing code passes the test;
the testing environment docker node module is also used for feeding back a testing code passing the test to the GIT version manager;
the GIT version manager is also used for synchronously pushing the test codes passing the test to a first stable code node module and a second stable code node module of the second NFS storage unit;
the second NFS storage unit is used for respectively mounting the first stable code node module and the second stable code node module to a first production environment docker node module and a second production environment docker node module of the on-line production environment unit;
the gateway entrance unit is used for switching all access flow to a first production environment docker node module or a second production environment docker node module; the gateway inlet unit is also used for starting the connection of the access flow between the first production environment docker node module and the second production environment docker node module together again;
the first stable code node module is to: when the gateway entry unit switches all the access traffic to the second production environment docker node module first, the first stable code node module is used for mounting the test code passing the test to the first production environment docker node module; the first production environment docker node module is used for receiving and updating the test codes passing the test;
the second stable code node module is to: when the gateway entry unit switches all the access traffic to the first production environment docker node module first, the second stable code node module is used for mounting the test code passing the test to the second production environment docker node module; and the second production environment docker node module is used for receiving the test codes passing the test and updating the test codes.
Specifically, the test environment docker node module is further configured to feed back a test code that fails the test to the GIT version manager, and the GIT version manager is configured to synchronously push the test code that fails the test to the first stable code node module and the second stable code node module of the second NFS storage unit;
the second NFS storage unit is used for respectively mounting the first stable code node module and the second stable code node module to the first production environment docker node module and the second production environment docker node module, and synchronously pushing the test codes which do not pass the test to the first production environment docker node module and the second production environment docker node module.
After the technical scheme is adopted, the invention at least has the following beneficial effects: the production environment, the test environment, the stable code and the test code are completely separated, and are mounted in a docker container generating the environment through an NFS storage technology, developers only need to care whether the code passes the test after being submitted, if the code passes the test, the developer automatically issues the code to the stable code node, and do not need to care about the docker node generating the environment, operation and maintenance personnel only need to monitor whether a server is normal, and the whole updating and deploying process achieves a scheme with high availability and extremely high stability;
the code node is completely separated from the production environment node, so that the safety and the stability are greatly improved;
according to the distributed node updating and deploying method, when one node goes wrong, the other node can be normally used, and high availability is achieved;
when the code is stable and successfully and synchronously pushed to the production environment, the invention can simultaneously reopen two nodes, and at least one node is kept to serve the outside under any condition, and the flow cutoff updating control is carried out, thus achieving the purpose of non-perception continuous service updating.
Drawings
FIG. 1 is a flowchart illustrating steps of a distributed code automatic update deployment method based on docker according to the present invention;
FIG. 2 is a framework diagram of a distributed code automatic update deployment system based on docker.
Detailed Description
It should be noted that, in the present application, the embodiments and features of the embodiments may be combined with each other without conflict, and the present application is further described in detail with reference to the drawings and specific embodiments.
Example 1
As shown in fig. 1, the invention discloses a distributed code automatic updating and deploying method based on docker, which comprises the following steps:
s11, mounting the GIT version manager in the first NFS storage unit to a socket node of the test environment;
s12, the GIT version manager receives the test codes and sends the test codes to a docker node in a test environment for testing; judging whether the test code passes the test or not by the docker node in the test environment;
s13, when the test code passes the test, the docker node in the test environment feeds the test code passing the test back to the GIT version manager; preferably, the docker node in the test environment feeds back the test code passing the test to the GIT version manager through the CICD pipeline;
s14, the GIT version manager synchronously pushes the test codes passing the test to a first stable code node and a second stable code node of a second NFS storage unit; the optimized GIT version manager synchronously pushes the test code passing the test to a first stable code node and a second stable code node of a second NFS storage unit through a CICD pipeline;
s15, respectively mounting a first stable code node and a second stable code node in a second NFS storage unit to a first production environment docker node and a second production environment docker node;
s16, switching all access flows to a second production environment docker node by the gateway entrance;
s17, the first stable code node mounts the test code passing the test to a first production environment docker node;
s18, after the first production environment docker node receives and updates the test code passing the test, the gateway inlet switches the access flow to the first production environment docker node;
s19, the second stable code node mounts the test code passing the test to a second production environment docker node, and the second production environment docker node receives and updates the code;
and S20, the gateway entrance restarts the connection of the access flow between the first production environment docker node and the second production environment docker node, and the test code updating deployment through the test is finished.
Further, step S13 includes: when the test code does not pass the test, the docker node in the test environment feeds the test code which does not pass the test back to the GIT version manager; specifically, the docker node in the test environment feeds back the test codes which do not pass the test to the GIT version manager through the CICD pipeline;
synchronously pushing the test codes which do not pass the test to a first stable code node and a second stable code node of a second NFS storage unit by the GIT version manager; specifically, the GIT version manager synchronously pushes the test code that fails the test to a first stable code node and a second stable code node of a second NFS storage unit through a cic d pipeline;
respectively mounting a first stable code node and a second stable code node in a second NFS storage unit to a first production environment docker node and a second production environment docker node, synchronously pushing test codes which do not pass the test to the first production environment docker node and the second production environment docker node, and ending the updating and the deployment of the test codes which do not pass the test; specifically, the second NFS storage unit synchronously pushes the test code that fails to pass the test to the first production environment docker node and the second production environment docker node through the CICD pipeline.
Among the above, Docker, NFS, Git, and CICD are all common technical means in the development field; the Docker is an open-source application container engine, so that developers can pack their applications and dependence packages into a portable container and then release the portable container to any popular Linux machine or Windows machine, and virtualization can be realized, the containers completely use a sandbox mechanism, and no interface exists between the containers; NFS refers to a network file System, which is called network file System in english, and is a UNIX presentation layer protocol (presentation layer protocol) developed by SUN corporation, and enables a user to access files in other places on the network just like using their own computer; git is an open-source distributed version control system, can effectively process the version management of projects from very small to very large at high speed, and is open-source version control software developed for managing the development of a Linux kernel.
The CICD assembly line is a conventional technical means in the development field, and specifically refers to: CI is persistent integration by which developers can frequently integrate their code into the main branch of a common code repository, developers can submit works to the repository multiple times at any time, rather than developing each functional module independently and submitting one at a time at the end of a development cycle; the CD is a continuous deployment that extends continuous delivery so that software build is automatically deployed when all tests are passed, in such a process, no human need to decide when and how to put into production; CI. The last step of the CD system will be automatic deployment when the built components, packages exit the pipeline, such automatic deployment can be configured to quickly distribute components, functional modules or repair patches to the customer and accurately account for the content currently being provided.
Example 2
The implementation provides a distributed code automatic update deployment system based on docker on the basis of embodiment 1, and as shown in fig. 2, the system includes a first NFS storage unit, a second NFS storage unit, a test environment unit, an online production environment unit, and a gateway entry unit, where the first NFS storage unit includes a GIT version manager, the second NFS storage unit includes a first stable code node module and a second stable code node module, the test environment unit includes a test environment docker node module, and the online production environment unit includes a first production environment docker node module and a second production environment docker node module;
the first NFS storage unit is used for mounting a GIT version manager to a socket node module in a test environment;
the GIT version manager is used for receiving the test codes and sending the test codes to the socket node module of the test environment unit;
the testing environment docker node module is used for testing the testing code and confirming whether the testing code passes the test;
the testing environment docker node module is also used for feeding back a testing code passing the test to the GIT version manager;
the GIT version manager is also used for synchronously pushing the test codes passing the test to a first stable code node module and a second stable code node module of the second NFS storage unit;
the second NFS storage unit is used for respectively mounting the first stable code node module and the second stable code node module to a first production environment docker node module and a second production environment docker node module of the on-line production environment unit;
the gateway entrance unit is used for switching all access flow to a first production environment docker node module or a second production environment docker node module; the gateway inlet unit is also used for starting the connection of the access flow between the first production environment docker node module and the second production environment docker node module together again;
the first stable code node module is to: when the gateway entry unit switches all the access traffic to the second production environment docker node module first, the first stable code node module is used for mounting the test code passing the test to the first production environment docker node module; the first production environment docker node module is used for receiving and updating the test codes passing the test;
the second stable code node module is to: when the gateway entry unit switches all the access traffic to the first production environment docker node module first, the second stable code node module is used for mounting the test code passing the test to the second production environment docker node module; and the second production environment docker node module is used for receiving the test codes passing the test and updating the test codes.
The testing environment docker node module is further configured to feed back the test code that fails the test to the GIT version manager, and the GIT version manager is configured to synchronously push the test code that fails the test to the first stable code node module and the second stable code node module of the second NFS storage unit;
the second NFS storage unit is used for respectively mounting the first stable code node module and the second stable code node module to the first production environment docker node module and the second production environment docker node module, and synchronously pushing the test codes which do not pass the test to the first production environment docker node module and the second production environment docker node module.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various equivalent changes, modifications, substitutions and alterations can be made herein without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.
Claims (6)
1. A distributed code automatic updating and deploying method based on docker is characterized by comprising the following steps:
s1, mounting the GIT version manager in the first NFS storage unit to a socket node of the test environment;
s2, the GIT version manager receives the test codes and sends the test codes to a docker node in a test environment for testing;
s3, the testing environment docker node feeds back the testing code passing the test to the GIT version manager;
s4, the GIT version manager synchronously pushes the test codes passing the test to a first stable code node and a second stable code node of a second NFS storage unit;
s5, respectively mounting a first stable code node and a second stable code node in a second NFS storage unit to a first production environment docker node and a second production environment docker node;
s6, switching all access flows to a second production environment docker node by the gateway entrance;
s7, the first stable code node mounts the test code passing the test to a first production environment docker node;
s8, after the first production environment docker node receives and updates the test code passing the test, the gateway inlet switches the access flow to the first production environment docker node;
s9, the second stable code node mounts the test code passing the test to a second production environment docker node, and the second production environment docker node receives and updates the test code passing the test;
and S10, the gateway entrance restarts the connection of the access flow between the first production environment docker node and the second production environment docker node, and the test code updating deployment through the test is finished.
2. The docker-based distributed code automatic update deployment method according to claim 1, wherein the step S3 further comprises: the docker node in the test environment feeds back the test code which does not pass the test to the GIT version manager;
synchronously pushing the test codes which do not pass the test to a first stable code node and a second stable code node of a second NFS storage unit by the GIT version manager;
and respectively mounting the first stable code node and the second stable code node in the second NFS storage unit to the first production environment docker node and the second production environment docker node, and synchronously pushing the test codes which do not pass the test to the first production environment docker node and the second production environment docker node, so that the updating and the deployment of the test codes which do not pass the test are finished.
3. The docker-based distributed code automatic update deployment method according to claim 1, wherein in step S3, the docker node feeds back the test code that passes the test to the GIT version manager through a CICD pipeline;
in S4, the GIT version manager synchronously pushes the test code passing the test to the first stable code node and the second stable code node of the second NFS storage unit through the cic pipeline.
4. The docker-based distributed code automatic update deployment method of claim 2, wherein the docker node feeds back test codes that fail testing to the GIT version manager through a CICD pipeline;
the GIT version manager synchronously pushes the test codes which do not pass the test to a first stable code node and a second stable code node of a second NFS storage unit through a CICD pipeline;
and respectively mounting the first stable code node and the second stable code node in the second NFS storage unit to the first production environment docker node and the second production environment docker node, and synchronously pushing the test codes which do not pass the test to the first production environment docker node and the second production environment docker node through a CICD pipeline.
5. A distributed code automatic updating deployment system based on docker is characterized by comprising a first NFS storage unit, a second NFS storage unit, a test environment unit, an online production environment unit and a gateway entry unit, wherein the first NFS storage unit comprises a GIT version manager, the second NFS storage unit comprises a first stable code node module and a second stable code node module, the test environment unit comprises a test environment docker node module, and the online production environment unit comprises a first production environment docker node module and a second production environment docker node module;
the first NFS storage unit is used for mounting a GIT version manager to a socket node module in a test environment;
the GIT version manager is used for receiving the test codes and sending the test codes to the socket node module of the test environment unit;
the testing environment docker node module is used for testing the testing code and confirming whether the testing code passes the test;
the testing environment docker node module is also used for feeding back a testing code passing the test to the GIT version manager;
the GIT version manager is also used for synchronously pushing the test codes passing the test to a first stable code node module and a second stable code node module of the second NFS storage unit;
the second NFS storage unit is used for respectively mounting the first stable code node module and the second stable code node module to a first production environment docker node module and a second production environment docker node module of the on-line production environment unit;
the gateway entrance unit is used for switching all access flow to a first production environment docker node module or a second production environment docker node module; the gateway inlet unit is also used for starting the connection of the access flow between the first production environment docker node module and the second production environment docker node module together again;
the first stable code node module is to: when the gateway entry unit switches all the access traffic to the second production environment docker node module first, the first stable code node module is used for mounting the test code passing the test to the first production environment docker node module; the first production environment docker node module is used for receiving and updating the test codes passing the test;
the second stable code node module is to: when the gateway entry unit switches all the access traffic to the first production environment docker node module first, the second stable code node module is used for mounting the test code passing the test to the second production environment docker node module; and the second production environment docker node module is used for receiving the test codes passing the test and updating the test codes.
6. The docker-based distributed code automatic update deployment system of claim 5, wherein the test environment docker node module is further configured to feed back test codes that fail the test to the GIT version manager, and the GIT version manager is configured to synchronously push the test codes that fail the test to the first and second stable code node modules of the second NFS storage unit;
the second NFS storage unit is used for respectively mounting the first stable code node module and the second stable code node module to the first production environment docker node module and the second production environment docker node module, and synchronously pushing the test codes which do not pass the test to the first production environment docker node module and the second production environment docker node module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010539935.2A CN111427605B (en) | 2020-06-15 | 2020-06-15 | Distributed code automatic updating and deploying method and system based on docker |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010539935.2A CN111427605B (en) | 2020-06-15 | 2020-06-15 | Distributed code automatic updating and deploying method and system based on docker |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111427605A CN111427605A (en) | 2020-07-17 |
| CN111427605B true CN111427605B (en) | 2020-10-16 |
Family
ID=71551399
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010539935.2A Active CN111427605B (en) | 2020-06-15 | 2020-06-15 | Distributed code automatic updating and deploying method and system based on docker |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111427605B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105187500A (en) * | 2015-08-07 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Container-based distributed storage system deployment method |
| CN108959547A (en) * | 2018-07-02 | 2018-12-07 | 山东汇贸电子口岸有限公司 | A kind of PV snapshot distributed experiment & measurement system restoration methods |
| CN109324819A (en) * | 2018-09-28 | 2019-02-12 | 中国平安财产保险股份有限公司 | Code server dispositions method, device, server apparatus and storage medium |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6944788B2 (en) * | 2002-03-12 | 2005-09-13 | Sun Microsystems, Inc. | System and method for enabling failover for an application server cluster |
| CN105045601A (en) * | 2015-08-14 | 2015-11-11 | 广东能龙教育股份有限公司 | Product release and deployment system based on cloud platform |
| US10396997B2 (en) * | 2016-12-14 | 2019-08-27 | International Business Machines Corporation | Container-based operating system and method |
| US10656927B2 (en) * | 2017-10-27 | 2020-05-19 | Intuit Inc. | Methods, systems, and computer program products for automating releases and deployment of a softawre application along the pipeline in continuous release and deployment of software application delivery models |
| CN108076159A (en) * | 2018-01-26 | 2018-05-25 | 成都精灵云科技有限公司 | A kind of cloud platform based on Docker builds device |
| CN110727446A (en) * | 2019-09-25 | 2020-01-24 | 光通天下网络科技股份有限公司 | Automatic deployment method, device, equipment and medium |
| CN111131146B (en) * | 2019-11-08 | 2021-04-09 | 北京航空航天大学 | Multi-supercomputing center software system deployment and incremental updating method in wide area environment |
-
2020
- 2020-06-15 CN CN202010539935.2A patent/CN111427605B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105187500A (en) * | 2015-08-07 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Container-based distributed storage system deployment method |
| CN108959547A (en) * | 2018-07-02 | 2018-12-07 | 山东汇贸电子口岸有限公司 | A kind of PV snapshot distributed experiment & measurement system restoration methods |
| CN109324819A (en) * | 2018-09-28 | 2019-02-12 | 中国平安财产保险股份有限公司 | Code server dispositions method, device, server apparatus and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111427605A (en) | 2020-07-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20100162226A1 (en) | Zero downtime mechanism for software upgrade of a distributed computer system | |
| US20200057619A1 (en) | System and method for creating and deploying a release package | |
| US20180143856A1 (en) | Flexible job management for distributed container cloud platform | |
| US20180146067A1 (en) | Embedded database as a microservice for distributed container cloud platform | |
| US9886260B2 (en) | Managing software version upgrades in a multiple computer system environment | |
| CN105224466A (en) | A kind of integration test method based on Docker and system | |
| CN102609281B (en) | Distributed software patch update method and system | |
| CN102254031A (en) | Batch processing request-based Microsoft SQL server database cluster | |
| US9354871B2 (en) | Multi-stage push notifications for software logistic tools | |
| US7870248B2 (en) | Exploiting service heartbeats to monitor file share | |
| US10379985B1 (en) | Automating and monitoring rolling cluster reboots | |
| CN108021608A (en) | A kind of lightweight website dispositions method based on Docker | |
| US20200348921A1 (en) | Microservice update system | |
| CN111427605B (en) | Distributed code automatic updating and deploying method and system based on docker | |
| EP3598297A1 (en) | Systems and methods for comparing computer scripts | |
| US20190317840A1 (en) | Integrating transaction processing system interfaces with event-driven polyglot runtime modules | |
| CN110196731A (en) | A kind of operational system, method and storage medium | |
| CN111818188B (en) | Load balancing availability improving method and device for Kubernetes cluster | |
| US10776134B2 (en) | Management of application properties | |
| US11086610B2 (en) | Instance upgrade techniques | |
| US10248396B1 (en) | Code review with automated translation | |
| CN110362582A (en) | A kind of method and apparatus for realizing zero shutdown upgrading | |
| WO2018077088A1 (en) | Application upgrading method and apparatus | |
| CN113315754B (en) | Intelligent linkage method, device, equipment and medium for firewall of container visit | |
| US11226978B2 (en) | Systems and methods for dynamic creation of schemas |
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 |