CN111124596A - Container-based release management method and system - Google Patents
Container-based release management method and system Download PDFInfo
- Publication number
- CN111124596A CN111124596A CN201811295950.6A CN201811295950A CN111124596A CN 111124596 A CN111124596 A CN 111124596A CN 201811295950 A CN201811295950 A CN 201811295950A CN 111124596 A CN111124596 A CN 111124596A
- Authority
- CN
- China
- Prior art keywords
- container
- application
- construction
- release
- issuing
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 32
- 238000010276 construction Methods 0.000 claims abstract description 47
- 238000000034 method Methods 0.000 claims abstract description 31
- 238000009826 distribution Methods 0.000 claims abstract description 22
- 238000003860 storage Methods 0.000 claims description 6
- 230000006378 damage Effects 0.000 claims description 3
- 238000012163 sequencing technique Methods 0.000 claims description 2
- 230000000977 initiatory effect Effects 0.000 claims 1
- 230000007613 environmental effect Effects 0.000 abstract description 2
- 230000009471 action Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000004140 cleaning Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000009430 construction management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to the release of application software, and discloses a release management method and a release management system based on a container, which solve the problems of environmental conflict and step conflict of multi-application deployment. The method comprises the following steps: acquiring information of N applications to be issued, wherein N is a positive integer; respectively creating a container mirror image of a construction container and a release container corresponding to each application to be released according to the information, and starting the created container mirror images to obtain the construction container and the release container; each construction container constructs a distribution package for the corresponding application to be distributed and submits the distribution package to a container mirror image warehouse; each issuing container pulls a corresponding issuing package of the application to be issued from the container mirror image warehouse and deploys the issuing package to a corresponding cluster; destroying the construction container and the release container.
Description
Technical Field
The present application relates to the publishing of application software, and more particularly, to container-based publication management techniques.
Background
Kubernetes (k 8s for short) is a Google open source container cluster management system. On the basis of the Docker technology, a series of complete functions such as deployment and operation, resource scheduling, service discovery, dynamic scaling and the like are provided for containerized application, and convenience in large-scale container cluster management is improved.
Kubernets is a complete distributed system supporting platform and has complete cluster management capacity, a multi-expansion multi-level security protection and admission mechanism, multi-tenant application supporting capacity, a transparent service registration and discovery mechanism, a built-in intelligent load balancer, strong fault discovery and self-repair capacity, service rolling upgrade and online capacity expansion capacity, an expandable resource automatic scheduling mechanism and multi-granularity resource quota management capacity. Meanwhile, Kubernetes provides a perfect management tool, and covers all links including development, deployment test and operation and maintenance monitoring.
In the k8s release process of daily operation and maintenance, problems often occur in the process that the release control machine simultaneously performs concurrent construction management and image cleaning of a plurality of images in the same local environment. For example, at the time of daily k8s release, the operations performed are: and locally pulling the code, constructing a docker image, submitting the docker image, executing a k8s command to update the mirror image, and cleaning the local mirror image cache. However, if the mirror deployment of multiple applications is performed simultaneously, different mirrors may affect each other at different stages, for example, the release of the application a is about to be completed, and the local cache starts to be cleared, and at this time, the application B just performs the operation of building dockerrimage, so that the clearing operation of the application a may affect the building operation of the application B, and the commonly used cache layer is cleared, resulting in a failure in building the application B. In addition, when multiple sets of K8S environments are managed, if different applications deployed at the same time belong to different K8S clusters, the clusters are mutually exclusive, and release waiting is caused.
Disclosure of Invention
The application aims to provide a container-based release management method and a container-based release management system, which solve the problems of environmental conflicts and step conflicts of multi-application deployment.
In order to solve the above problem, the present application discloses a container-based publication management method, including:
acquiring information of N applications to be issued, wherein N is a positive integer;
respectively creating a container mirror image of a construction container and a release container corresponding to each application to be released according to the information, and starting the created container mirror images to obtain the construction container and the release container;
each construction container constructs a distribution package for the corresponding application to be distributed and submits the distribution package to a container mirror image warehouse;
each issuing container pulls a corresponding issuing package of the application to be issued from the container mirror image warehouse and deploys the issuing package to a corresponding cluster;
destroying the build container and the issue container.
In a preferred embodiment, after obtaining the information of the N applications to be published, the method further includes: writing the information of the application to be published into a message queue, sequencing according to the dependence between the applications, and generating a dependence list of the application to be published;
in the step of deploying the publishing package to the corresponding cluster, the method further includes:
the issuing container judges whether the applications to be issued have dependence among the applications according to the dependence list; if no dependency exists, directly deploying the publishing package; and if the dependency exists, waiting according to the deployment dependency sequence in the message queue until the depended application to be issued is deployed after the deployment is finished.
In a preferred embodiment, the step of creating a container image of a build container and a publishing container respectively corresponding to each application to be published further includes:
acquiring the application type of the application to be released according to the information of the application to be released;
matching to obtain a container mirror image template according to the application type from a container mirror image template set generated in advance;
and creating container images of the construction container and the release container according to the container image template obtained by matching.
In a preferred embodiment, the container mirror image template is internally provided with compiling construction environments of corresponding languages, and different environments are provided for different languages respectively; the container mirror template contains support for container commands; the container mirror template configures an access rights configuration file for a plurality of local sets of kubernates clusters.
In a preferred embodiment, the distribution package is a container mirror.
In a preferred embodiment, the information of the application to be published includes an application name and a version number.
In a preferred embodiment, after the step of starting the created container image to obtain the build container and the release container, the method further includes:
according to the application type of the corresponding application to be issued, the construction container and the issuing container respectively read the configuration information, initialize kubernates environment variables and a container construction environment in the container, and execute the corresponding container initialization script.
The application also discloses a release management system based on the container, including:
the information acquisition module is used for acquiring information of N applications to be issued, wherein N is a positive integer;
the container creating module is used for respectively creating a container mirror image of a construction container and a release container corresponding to each application to be released according to the information, and starting the created container mirror images to obtain the construction container and the release container;
the system comprises a construction container, a container mirror image warehouse and a distribution package, wherein the construction container is used for constructing a distribution package for a corresponding application to be distributed and submitting the distribution package to the container mirror image warehouse;
the issuing container is used for pulling the corresponding issuing package of the application to be issued from the container mirror image warehouse and deploying the issuing package to the corresponding cluster;
and the destruction module is used for destroying the construction container and the release container after the release package is deployed.
The application also discloses a release management system based on the container, including:
a memory for storing computer executable instructions; and the number of the first and second groups,
a processor for implementing the steps in the method as described hereinbefore when executing the computer executable instructions.
The present application also discloses a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement the steps in the method as described hereinbefore.
In the embodiment of the application, the characteristics of the isolation environment of the container are skillfully utilized, and the concurrent construction and deployment of a plurality of different applications in the same host environment are isolated, so that the mutual influence is avoided, and the deployment efficiency of the k8s cluster application is improved.
The present specification describes a number of technical features distributed throughout the various technical aspects, and if all possible combinations of technical features (i.e. technical aspects) of the present specification are listed, the description is made excessively long. In order to avoid this problem, the respective technical features disclosed in the above summary of the invention of the present application, the respective technical features disclosed in the following embodiments and examples, and the respective technical features disclosed in the drawings may be freely combined with each other to constitute various new technical solutions (which are considered to have been described in the present specification) unless such a combination of the technical features is technically infeasible. For example, in one example, the feature a + B + C is disclosed, in another example, the feature a + B + D + E is disclosed, and the features C and D are equivalent technical means for the same purpose, and technically only one feature is used, but not simultaneously employed, and the feature E can be technically combined with the feature C, then the solution of a + B + C + D should not be considered as being described because the technology is not feasible, and the solution of a + B + C + E should be considered as being described.
Drawings
FIG. 1 is a schematic flow chart of a container-based publication management method according to a first embodiment of the present application
FIG. 2 is a schematic release diagram according to one embodiment of the present application
Detailed Description
In the following description, numerous technical details are set forth in order to provide a better understanding of the present application. However, it will be understood by those skilled in the art that the technical solutions claimed in the present application may be implemented without these technical details and with various changes and modifications based on the following embodiments.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
A first embodiment of the present application relates to a container-based publication management method, a flow of which is shown in fig. 1, and the method includes the following steps:
in step 101, information of N applications to be published is obtained, where N is a positive integer. In one embodiment, the information of the application to be published includes an application name, a version number, and the like. In one embodiment, after the information of the N applications to be published is acquired, the information of the applications to be published is written into a message queue, and is sorted according to the dependencies among the applications to generate a dependency list of the applications to be published.
Then, step 102 is entered, a container mirror image of a construction container and a release container is respectively created corresponding to each application to be released according to the acquired information, and the created container mirror image is started to obtain the construction container and the release container. In other words, 2N container images may be created and started, including N container images of build containers and N container images of publish containers. In one embodiment, the application type of the application to be released is obtained according to the information of the application to be released; obtaining a container mirror image template from a container mirror image template set (which comprises a plurality of container mirror image templates) generated in advance according to application type matching; and creating container images of the construction container and the release container according to the container image template obtained by matching. Wherein, the container mirror image template has following characteristics: compiling construction environments of corresponding languages are built in, and different environments exist for different languages respectively; containing support for container commands; an access rights configuration file for a local multi-set of kubernates clusters is configured. For one application to be issued, two container mirror templates are obtained according to application type matching, wherein one container mirror template is used for constructing a container, and the other container mirror template is used for issuing the container.
In one embodiment, after the build container and the release container are started, the build container and the release container respectively read configuration information according to the application type of the corresponding application to be released, initialize kubberonates environment variables and a container build environment in the container, and execute a corresponding container initialization script.
Then, step 103 is entered, and each build container builds a distribution package for the corresponding application to be distributed, and submits the distribution package to the container mirror repository.
Then step 104 is entered, each publishing container pulls the corresponding publishing package of the application to be published from the container mirror repository, and deploys the publishing package to the corresponding cluster. In one embodiment, the publishing package is a container mirror. In one embodiment, the publishing container determines whether the application to be published has a dependency between applications according to the dependency list. If no dependency exists, the publishing package is directly deployed. And if the dependency exists, waiting according to the deployment dependency sequence in the message queue until the depended application to be issued is deployed after the deployment is finished.
Then, step 105 is performed, and after one publishing package is deployed, the building container and the publishing container corresponding to the publishing package are destroyed.
In various embodiments of the present application, the container may be implemented with a Docker.
In one embodiment, a schematic diagram of dynamically creating dockers for different applications is shown in FIG. 2.
According to the technical scheme, the mutual influence of concurrent multi-application deployment is eliminated, application issuing serial caused by the dependence on a k8s cluster environment is changed into parallel, and issuing efficiency is improved.
In order to better understand the technical solution of the present application, the following description is given with reference to a specific example, in which the listed details are mainly for the sake of understanding and are not intended to limit the scope of the present application.
Step A, recording a corresponding release application and a corresponding version number in a deployment management system, for example, the corresponding json configuration is as follows:
the deployment system writes the corresponding application information into the message queue, sorts the application information according to the dependencies among the applications, and generates a dependency list of the applications to be published.
And step B, matching corresponding release execution docker images in a plurality of release execution docker images pre-generated in the system according to different application construction types by a release control machine of the deployment management system, wherein the images are used for executing application construction and application deployment of corresponding types. The mirror image has the following characteristics: the 1 mirror image is internally provided with compiling construction environments of corresponding languages, different environments exist for different languages, the 2 mirror image comprises support for docker commands, and the 3 mirror image is configured with access authority configuration files for local multi-set k8s clusters. The deployment task execution container mainly comprises a construction container image and a release execution container image, and the construction operation and the release operation of each application are respectively and independently executed.
Creating a docker image of a construction container and a release container (the number of the started containers is 2 multiplied by the number of the applications to be released) with the same number as the applications to be released through a command, starting the docker image, writing the configuration of the name and the version number of the applications to be deployed of the corresponding docker container, wherein the directory is/wls/app/appname/version/ver
Step C, after the deployment management system release controller starts the deployment work container (the work container includes a build container and a release container), the work container of the corresponding release application type reads the corresponding configuration (for example, if the release application type is Java, the Java-related configuration is read, and if the release application type is Python, the Python-related configuration is read), initializes the k8s environment variable and the docker build environment in the docker container, and executes the corresponding container initialization script.
And step D, after the construction containers with the same number as the application are started, automatically connecting a message queue of the deployment management system, sequentially acquiring corresponding application names and version numbers of the containers according to the application dependence sequence, starting construction operation of corresponding applications, executing construction tasks according to corresponding application types, constructing docker images of the distribution packages, and submitting the docker images to a docker image warehouse.
Step E, the issuing containers with the same number as the applications to be issued respectively acquire application version numbers to be deployed from the message queue, call a CMDB cluster information interface according to the version numbers, acquire cluster information and a docker mirror warehouse address of the current issuing container, execute corresponding issuing packet docker image pulling operation to be deployed of k8s, execute a kubecect command to switch to an application cluster configured by CMDB in the issuing container after pulling is completed, execute the corresponding kubecect command if no dependency exists between the applications, execute related issuing waiting operation on the applications of the corresponding cluster if dependency exists between the applications issued currently, poll whether the adjacent dependency issuing is completed or not in a unit of five seconds, and deploy the current issuing packet if the issuing is completed, otherwise, the waiting is continued.
And F, after the deployment of the issuing execution container initiated by the deployment management system is completed, executing the operation of clearing the issuing execution container, informing the issuing system of the completion of the deployment, writing the final issued result back to the message queue, and destroying the docker container of the issuing application, including the construction container and the issuing container.
The technical scheme provides a new set of k8s construction deployment management mode, and when a plurality of applications are issued, the problems of environment conflict and step conflict of a plurality of application deployments in the same environment of an issuing control machine are solved by opening different containers for the plurality of applications on the issuing control machine to isolate the environment and isolate the command. By performing container scheduling of application granularity at the release controller, an isolated, independent, non-interfering environment for docker image construction and k8s application deployment is provided for the release of each application, avoiding the problems of the prior art.
A second embodiment of the present application relates to a container-based distribution management system including:
the information acquisition module is used for acquiring information of N applications to be issued, wherein N is a positive integer.
And the container creating module is used for respectively creating a container mirror image of a constructed container and a release container corresponding to each application to be released according to the information, and starting the created container mirror images to obtain the constructed container and the release container.
The system comprises a construction container, a container mirror image warehouse and a distribution package, wherein the construction container is used for constructing a distribution package for a corresponding application to be distributed and submitting the distribution package to the container mirror image warehouse;
and the issuing container is used for pulling the corresponding issuing package of the application to be issued from the container mirror image warehouse and deploying the issuing package to the corresponding cluster.
And the destruction module is used for destroying the construction container and the release container after the release package is deployed.
The first embodiment is a method embodiment corresponding to the present embodiment, and the technical details in the first embodiment may be applied to the present embodiment, and the technical details in the present embodiment may also be applied to the first embodiment.
It should be noted that, as will be understood by those skilled in the art, the implementation functions of the modules shown in the embodiment of the container-based publication management system can be understood by referring to the related description of the container-based publication management method. The functions of the respective modules shown in the embodiments of the container-based publication management system described above may be implemented by a program (executable instructions) running on a processor, and may also be implemented by a specific logic circuit. The container-based distribution management system according to the embodiment of the present application may be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as an independent product. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or portions thereof contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.
Accordingly, the present application also provides a computer storage medium, in which computer executable instructions are stored, and when executed by a processor, the computer executable instructions implement the method embodiments of the present application.
In addition, the present application also provides a container-based publication management system, which includes a memory for storing computer-executable instructions, and a processor; the processor is configured to implement the steps of the method embodiments described above when executing the computer-executable instructions in the memory. The Processor may be a Central Processing Unit (CPU), other general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like. The aforementioned memory may be a read-only memory (ROM), a Random Access Memory (RAM), a Flash memory (Flash), a hard disk, or a solid state disk. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
It is noted that, in the present patent application, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the use of the verb "comprise a" to define an element does not exclude the presence of another, same element in a process, method, article, or apparatus that comprises the element. In the present patent application, if it is mentioned that a certain action is executed according to a certain element, it means that the action is executed according to at least the element, and two cases are included: performing the action based only on the element, and performing the action based on the element and other elements. The expression of a plurality of, a plurality of and the like includes 2, 2 and more than 2, more than 2 and more than 2.
All documents mentioned in this application are to be considered as being incorporated in their entirety into the disclosure of this application so as to be subject to modification as necessary. Further, it is understood that various changes or modifications may be made to the present application by those skilled in the art after reading the above disclosure of the present application, and such equivalents are also within the scope of the present application as claimed.
Claims (10)
1. A container-based publication management method, comprising:
acquiring information of N applications to be issued, wherein N is a positive integer;
respectively creating a container mirror image of a construction container and a release container corresponding to each application to be released according to the information, and starting the created container mirror images to obtain the construction container and the release container;
each construction container constructs a distribution package for the corresponding application to be distributed and submits the distribution package to a container mirror image warehouse;
each issuing container pulls a corresponding issuing package of the application to be issued from the container mirror image warehouse and deploys the issuing package to a corresponding cluster;
destroying the build container and the issue container.
2. The method of claim 1, wherein after obtaining the information of the N applications to be published, the method further comprises: writing the information of the applications to be published into a message queue, sequencing according to the dependence between the applications, and generating a dependence list of the applications to be published;
in the step of deploying the publishing packet to the corresponding cluster, the method further includes:
the issuing container judges whether the applications to be issued have dependence among the applications according to the dependence list; if no dependency exists, directly deploying the publishing package; and if the dependency exists, waiting according to the deployment dependency sequence in the message queue until the depended application to be issued is deployed after the deployment is finished.
3. The method of claim 1, wherein the step of creating a container image of a build container and a publishing container for each of the applications to be published respectively further comprises:
acquiring the application type of the application to be issued according to the information of the application to be issued;
matching to obtain a container mirror image template from a container mirror image template set generated in advance according to the application type;
and creating container images of the construction container and the release container according to the container image template obtained by matching.
4. The method of claim 3, wherein the container mirror template is built with a compilation build environment of a corresponding language, and has different environments for different languages; the container mirror template contains support for container commands; the container mirror image template is configured with an access authority configuration file for a plurality of local groups of kubernates clusters.
5. The method of claim 1, wherein the distribution package is a container mirror.
6. The method of claim 1, wherein the information of the application to be published includes an application name and a version number.
7. The method of any of claims 1-6, wherein after the steps of initiating the created container image resulting in a build container and a publish container, further comprising:
according to the application type of the corresponding application to be issued, the construction container and the issuing container respectively read the configuration information, initialize kubernates environment variables and a container construction environment in the container, and execute the corresponding container initialization script.
8. A container-based publication management system, comprising:
the information acquisition module is used for acquiring information of N applications to be issued, wherein N is a positive integer;
the container creating module is used for respectively creating a container mirror image of a construction container and a release container corresponding to each application to be released according to the information, and starting the created container mirror images to obtain the construction container and the release container;
the system comprises a construction container, a container mirror image warehouse and a distribution package, wherein the construction container is used for constructing a distribution package for a corresponding application to be distributed and submitting the distribution package to the container mirror image warehouse;
the issuing container is used for pulling the corresponding issuing package of the application to be issued from the container mirror image warehouse and deploying the issuing package to the corresponding cluster;
and the destruction module is used for destroying the construction container and the release container after the release package is deployed.
9. A container-based publication management system, comprising:
a memory for storing computer executable instructions; and the number of the first and second groups,
a processor for implementing the steps in the method of any one of claims 1 to 7 when executing the computer-executable instructions.
10. A computer-readable storage medium having stored thereon computer-executable instructions which, when executed by a processor, implement the steps in the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811295950.6A CN111124596A (en) | 2018-11-01 | 2018-11-01 | Container-based release management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811295950.6A CN111124596A (en) | 2018-11-01 | 2018-11-01 | Container-based release management method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111124596A true CN111124596A (en) | 2020-05-08 |
Family
ID=70494834
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811295950.6A Pending CN111124596A (en) | 2018-11-01 | 2018-11-01 | Container-based release management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111124596A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111654531A (en) * | 2020-05-22 | 2020-09-11 | 国云科技股份有限公司 | Container-based mirror image update publishing method and device |
| CN111694737A (en) * | 2020-06-02 | 2020-09-22 | 中国人民解放军国防科技大学 | Container influence measuring method and device based on mirror image dependency network |
| CN111796863A (en) * | 2020-07-10 | 2020-10-20 | 四川中电启明星信息技术有限公司 | Cross-environment project version management method |
| CN111813440A (en) * | 2020-07-21 | 2020-10-23 | 北京千丁互联科技有限公司 | Multithreading application issuing method and device |
| CN112835713A (en) * | 2021-01-28 | 2021-05-25 | 交通银行股份有限公司 | Workload combination unified deployment method and system based on multi-container cluster |
| CN113296879A (en) * | 2020-10-29 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Container creation method and device |
| CN113472845A (en) * | 2021-05-27 | 2021-10-01 | 四川大学华西医院 | Medical Internet of things intelligent system based on container technology |
| CN113485795A (en) * | 2021-07-26 | 2021-10-08 | 四川万益能源科技有限公司 | Automatic container starting method based on multiple types of projects |
| CN113760442A (en) * | 2020-10-19 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Application running and accessing method, device and equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104793946A (en) * | 2015-04-27 | 2015-07-22 | 广州杰赛科技股份有限公司 | Application deployment method and system based on cloud computing platform |
| CN106445585A (en) * | 2016-08-30 | 2017-02-22 | 中国民生银行股份有限公司 | Application deployment method and system based on container technology |
| CN107608757A (en) * | 2017-08-29 | 2018-01-19 | 华为技术有限公司 | A kind of isolation processing method and relevant device based on container |
| CN107678756A (en) * | 2017-09-29 | 2018-02-09 | 千寻位置网络有限公司 | A kind of Web based on Docker applies a key dissemination method |
| CN107766052A (en) * | 2017-09-18 | 2018-03-06 | 网宿科技股份有限公司 | A kind of method and apparatus for building mirror image |
| CN108563451A (en) * | 2018-02-26 | 2018-09-21 | 挖财网络技术有限公司 | A kind of method, apparatus and system of the structure and publication of Docker containers |
-
2018
- 2018-11-01 CN CN201811295950.6A patent/CN111124596A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104793946A (en) * | 2015-04-27 | 2015-07-22 | 广州杰赛科技股份有限公司 | Application deployment method and system based on cloud computing platform |
| CN106445585A (en) * | 2016-08-30 | 2017-02-22 | 中国民生银行股份有限公司 | Application deployment method and system based on container technology |
| CN107608757A (en) * | 2017-08-29 | 2018-01-19 | 华为技术有限公司 | A kind of isolation processing method and relevant device based on container |
| CN107766052A (en) * | 2017-09-18 | 2018-03-06 | 网宿科技股份有限公司 | A kind of method and apparatus for building mirror image |
| CN107678756A (en) * | 2017-09-29 | 2018-02-09 | 千寻位置网络有限公司 | A kind of Web based on Docker applies a key dissemination method |
| CN108563451A (en) * | 2018-02-26 | 2018-09-21 | 挖财网络技术有限公司 | A kind of method, apparatus and system of the structure and publication of Docker containers |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111654531B (en) * | 2020-05-22 | 2023-05-05 | 国云科技股份有限公司 | Mirror image update release method and device based on container |
| CN111654531A (en) * | 2020-05-22 | 2020-09-11 | 国云科技股份有限公司 | Container-based mirror image update publishing method and device |
| CN111694737A (en) * | 2020-06-02 | 2020-09-22 | 中国人民解放军国防科技大学 | Container influence measuring method and device based on mirror image dependency network |
| CN111694737B (en) * | 2020-06-02 | 2023-04-21 | 中国人民解放军国防科技大学 | Container influence measuring method and device based on mirror image dependency network |
| CN111796863A (en) * | 2020-07-10 | 2020-10-20 | 四川中电启明星信息技术有限公司 | Cross-environment project version management method |
| CN111796863B (en) * | 2020-07-10 | 2024-04-05 | 四川中电启明星信息技术有限公司 | Cross-environment project version management method |
| CN111813440A (en) * | 2020-07-21 | 2020-10-23 | 北京千丁互联科技有限公司 | Multithreading application issuing method and device |
| CN113760442A (en) * | 2020-10-19 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Application running and accessing method, device and equipment |
| CN113296879A (en) * | 2020-10-29 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Container creation method and device |
| CN113296879B (en) * | 2020-10-29 | 2024-03-08 | 阿里巴巴集团控股有限公司 | Container creation method and device |
| CN112835713A (en) * | 2021-01-28 | 2021-05-25 | 交通银行股份有限公司 | Workload combination unified deployment method and system based on multi-container cluster |
| CN112835713B (en) * | 2021-01-28 | 2024-02-06 | 交通银行股份有限公司 | Workload combination unified deployment method and system based on multi-container cluster |
| CN113472845B (en) * | 2021-05-27 | 2023-05-09 | 四川大学华西医院 | Medical internet of things intelligent system based on container technology |
| CN113472845A (en) * | 2021-05-27 | 2021-10-01 | 四川大学华西医院 | Medical Internet of things intelligent system based on container technology |
| CN113485795A (en) * | 2021-07-26 | 2021-10-08 | 四川万益能源科技有限公司 | Automatic container starting method based on multiple types of projects |
| CN113485795B (en) * | 2021-07-26 | 2024-03-26 | 四川万益能源科技有限公司 | Automatic container starting method based on multiple types of items |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111124596A (en) | Container-based release management method and system | |
| US10324696B2 (en) | Dynamic container deployment with parallel conditional layers | |
| US10303450B2 (en) | Systems and methods for a policy-driven orchestration of deployment of distributed applications | |
| CN110389832B (en) | ZooKeeper container cluster deployment method, system, device and storage medium | |
| CN110389766B (en) | HBase container cluster deployment method, system, equipment and computer readable storage medium | |
| CN108776643B (en) | Target code merging control method and system based on version control process | |
| CN112242920B (en) | Cloud platform deployment method, device and node | |
| US9542173B2 (en) | Dependency handling for software extensions | |
| CN112764753A (en) | Project deployment method and device, electronic equipment and storage medium | |
| CN110851143B (en) | Source code deployment method, device, equipment and storage medium | |
| CN116166379A (en) | Mirror image cutting and multi-architecture mirror image construction method based on cloud platform | |
| CN115632944A (en) | Node configuration method, device, equipment, readable storage medium and server | |
| US20160364258A1 (en) | Method for generating upgrade campaigns to upgrade virtualization facilities | |
| CN115220863A (en) | Operation and maintenance method and device for container application, computer equipment and storage medium | |
| US9760364B2 (en) | Checks for software extensions | |
| CN110968333B (en) | Configuration information replacement method and device, machine-readable storage medium and processor | |
| CN116775061A (en) | Deployment method, device, equipment and storage medium of micro-service application | |
| CN115480785A (en) | Container-based service deployment method and device and server | |
| US11562105B2 (en) | System and method for module engineering with sequence libraries | |
| CN113708971A (en) | Openstack cloud platform deployment method and related device | |
| JP3692960B2 (en) | Cluster system installation method, system, and program | |
| CN117827277B (en) | Multi-kernel adapting device and method of operating system and industrial Internet of things operating system | |
| JP5834875B2 (en) | System configuration management apparatus, system configuration management method, and system configuration management program | |
| US12014161B2 (en) | Deployment of management features using containerized service on management device and application thereof | |
| CN114138324A (en) | Task control method and device based on cloud service and electronic equipment |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200508 |
|
| WD01 | Invention patent application deemed withdrawn after publication |