CN111399855B - Automatic application instance publishing method based on container technology - Google Patents
Automatic application instance publishing method based on container technology Download PDFInfo
- Publication number
- CN111399855B CN111399855B CN202010155717.9A CN202010155717A CN111399855B CN 111399855 B CN111399855 B CN 111399855B CN 202010155717 A CN202010155717 A CN 202010155717A CN 111399855 B CN111399855 B CN 111399855B
- Authority
- CN
- China
- Prior art keywords
- container
- setting
- application instance
- configuration
- application
- 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
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000005516 engineering process Methods 0.000 title claims abstract description 11
- 230000008569 process Effects 0.000 claims abstract description 21
- 238000007689 inspection Methods 0.000 claims description 9
- 238000005096 rolling process Methods 0.000 claims description 8
- 230000036541 health Effects 0.000 claims description 5
- 238000003860 storage Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 5
- 230000007704 transition Effects 0.000 abstract description 2
- 230000008447 perception Effects 0.000 abstract 1
- 230000004044 response Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/161—Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses an automatic application instance publishing method based on a container technology, which comprises the following steps: setting an application instance basic configuration, setting a container configuration of a container instance, wherein the basic configuration comprises the following contents: setting a published Kubernetes cluster, a published strategy, an instance type and a number of copies; the container configuration includes the content: add application instance container, set container type, container mirror, etc. According to the method, a Kubernetes cluster configuration file is not required to be manually written in the release process of the application example, so that errors in the manual operation process of operation and maintenance personnel are prevented, and the risk of manual operation of the operation and maintenance personnel is reduced; the method is convenient for automatic upgrading and publishing of the application instance, users have no perception in the version switching process, smooth transition of the service in the upgrading process is guaranteed, the publishing risk is reduced, and the method can be flexibly set according to the actual situation of the user Kubernetes cluster.
Description
Technical Field
The invention relates to the technical field of cloud computing, and particularly provides an automatic application instance publishing method based on a container technology.
Background
As cloud computing technologies tend to mature, and in particular, dock container technologies are widely used in various industries, business systems in various industries have gradually migrated into cloud platforms for deployment and operation under the pushing of various cloud computing manufacturers and communities.
kubernetes, abbreviated as K8s, is an abbreviation that replaces 8 characters "kubernete" with 8. Is an open source for managing containerized applications on multiple hosts in a cloud platform, and the goal of Kubernetes is to make deploying containerized applications simple and efficient (powerful), which provides a mechanism for application deployment, planning, updating, and maintenance.
The traditional application deployment mode is to install the application through a plug-in or script. The disadvantage of this is that the running, configuration, management, all life cycles of the application will be bound to the current operating system, which is not beneficial for the upgrade update/rollback etc. operations of the application, of course, some functions can be implemented by creating virtual machines, which are very heavy and not beneficial for portability.
The new mode is realized by deploying containers, each container is isolated from each other, each container has a file system, processes among the containers cannot affect each other, and computing resources can be distinguished. Compared with a virtual machine, the container can be rapidly deployed, and can migrate among different cloud and different version operating systems due to decoupling of the container from underlying facilities and machine file systems.
The container occupies less resources and is quick to deploy, each application can be packaged into a container mirror image, the container is further advantageous due to the fact that each application is in one-to-one relation with the container, the container mirror image can be created for the application in the build or release stage by using the container, and because each application does not need to be combined with the rest of application stacks and does not depend on a production environment infrastructure, a consistent environment can be provided from research, development to testing and production. Similarly, the container is lighter weight, more "transparent" than the virtual machine, which is more convenient to monitor and manage.
When migrating services to a Kubernetes cluster, a large number of application programming configuration files need to be written, errors are very easy to occur in the programming process, parameter configuration errors are very likely to occur, and accordingly the application instance publishing faults are caused.
Disclosure of Invention
The technical task of the invention is to provide an automatic application instance publishing method based on the container technology aiming at the existing problems, and the purposes of automatically creating the application instance, remarkably reducing the workload of a developer and improving the publishing efficiency are achieved by simply setting and automatically generating configuration resources required by application instance deployment.
In order to achieve the above purpose, the present invention provides the following technical solutions:
an automatic application instance publishing method based on container technology, wherein the method publishes an initial version application instance, and the implementation process comprises the following steps: setting an application instance base configuration, setting a container configuration of a container instance, wherein:
the basic configuration includes the content: setting a published Kubernetes cluster, a published strategy, an instance type and a number of copies;
the container configuration includes the content: adding an application instance container, setting a container type, a container mirror image, a container port, a container quota, an environment variable, a mounting volume, a health check and a running user.
The application instance basic configuration setting step comprises the following steps:
1) Selecting a cluster: the application instance supports the release of multiple Kubernetes clusters, a user selects one of the Kubernetes clusters, and the application instance is released to the appointed Kubernetes cluster;
2) Selecting a namespace: publishing the application instance under the namespace of the specified cluster;
3) Selecting release strategies, including three release strategies of rolling release, bluish green release or gray release, defaulting to rolling release, wherein a stateful load only supports the rolling release strategies;
4) Selecting instance types, including two load types of stateful or stateless, and defaulting to stateless;
5) The number of the selected copies: the number of selectable copies is between 1 and 20 (either slidably selected or entered digitally selected).
The step of container configuration of the container instance includes:
1) The adding container comprises: a plurality of containers can be added, including application containers and initialization containers, and a maximum of 10 containers can be added, and at least one application container is needed, so that the custom container names are supported;
2) Selecting a container type, comprising:
the application container comprises: the container in which the application instance runs, an application instance must contain an application container;
initial container: preset conditions required for completing the application container before starting the application container;
3) Selecting a container mirror image: selecting images to be deployed from the image list;
4) Filling out a container port: the container port is a port actually opened by an application program in the container mirror image and is also a target port of a service. Such as: the nginx program actually opens port 80. The input can be: the port range is 0-65535, the protocol is TCP or UDP, a plurality of ports can be input, and the ports are separated by English commas, such as: 80: TCP,9081: UDP, default 80: TCP;
5) Setting a container quota: the method comprises two quota selection modes of CPU limitation or memory limitation;
6) Setting a container environment variable, wherein the environment variable comprises three types of custom, reference configuration items or reference keys, and the referenced configuration items or key data are mapped into the specified environment variable;
7) Setting a container mounting roll, wherein the mounting roll comprises two mounting modes:
reference mount: providing a data mounting volume of a reference type for the container, wherein the data of the reference configuration item and the key are mounted in a specified directory of the container;
and (3) direct mounting: directly mounting different types of data volumes for the container, including a temporary directory and a host directory, and supporting the dynamic creation of volumes for specified storage types or mounting existing volumes;
8) Setting container health inspection: including HTTP inspection requests and TCP port inspection, configured with page hints, and no such option when the container type is the initial container;
9) Setting a container operation user: the container rights are set to protect the system and other containers from the user ID range 1-65534, and the container will run with the current user rights.
The application instance configuration process further includes automatic telescoping settings: and carrying out automatic expansion setting according to the CPU utilization rate or the memory utilization rate and the copy number of the application instance.
The application instance configuration process further includes affinity settings: including node affinity, application anti-affinity, custom affinity, and the like.
The method further comprises an application instance access configuration step, wherein the configuration is carried out by setting an access mode, and the access mode comprises the following steps: selecting intra-cluster access, domain name access or node access, default to domain name access.
When the access mode selects domain name access, the access configuration step further comprises setting a domain name, and the response speed of access is improved by setting the access domain name of the application instance.
The application instance access configuration process also comprises default port setting, and the response speed of access is improved by designating the default access port of the application instance service.
In the container configuration setting step, when a plurality of initial containers are set, the plurality of initial containers are sequentially operated one by one, and after successful execution is completed, the system continues to execute the next initial container.
In the container mirror image selection step, a mirror image needing to be deployed is selected from a mirror image list in a searching mode.
Compared with the prior art, the automatic application instance publishing method based on the container technology has the following outstanding beneficial effects:
(1) The Kubernetes cluster configuration file is not required to be manually written in the release process of the application instance, so that errors are prevented in the manual operation process of operation and maintenance personnel, and the risk of manual operation of the operation and maintenance personnel is reduced;
(2) Three application release and update strategies of rolling release, bluish green release and gray release are provided, automatic upgrade release of application examples is facilitated, users do not feel in the version switching process, smooth transition of business in the upgrade process is ensured, and release risks are reduced;
(3) The three access modes of intra-cluster access, domain name access and node access are provided, and the method can be flexibly set according to the actual situation of the user Kubernetes cluster.
Drawings
FIG. 1 is a flow chart of a method implementation of the present invention.
Detailed Description
The invention will be described in further detail with reference to the drawings and examples.
Examples
As shown in fig. 1, a method for publishing an automation application instance based on container technology includes the following implementation steps:
1) Setting application instance basic configuration: formulating a cluster to which an application instance is issued, an issuing and updating strategy of the application instance, an application instance type and a copy number;
2) Setting an application instance container configuration: container type setting, container mirror image selection, container port, container quota, environment variable, mounting volume, monitoring and checking container configuration setting of operation users and the like;
3) Setting application instance advanced configuration: setting an application instance automatic expansion and application instance affinity strategy;
4) Setting an application instance access configuration: setting an access mode and a service access port of an application instance;
5) An application instance is published.
The application instance basic configuration setting step comprises the following steps:
1) Selecting a cluster: the application instance supports the release of multiple Kubernetes clusters, a user selects one of the Kubernetes clusters, and the application instance is released to the appointed Kubernetes cluster;
2) Selecting a namespace: publishing the application instance under the namespace of the specified cluster;
3) Selecting release strategies, including three release strategies of rolling release, bluish green release or gray release, defaulting to rolling release, wherein a stateful load only supports the rolling release strategies;
4) Selecting instance types, including two load types of stateful or stateless, and defaulting to stateless;
5) The number of the selected copies: the number of selectable copies is between 1 and 20 (either slidably selected or entered digitally selected).
The step of container configuration of the container instance includes:
1) The adding container comprises: a plurality of containers can be added, including application containers and initialization containers, and a maximum of 10 containers can be added, and at least one application container is needed, so that the custom container names are supported;
2) Selecting a container type, comprising:
the application container comprises: the container in which the application instance runs, an application instance must contain an application container;
initial container: preset conditions required for completing the application container before starting the application container;
3) Selecting a container mirror image: selecting images to be deployed from the image list;
4) Filling out a container port: the container port is a port actually opened by an application program in the container mirror image and is also a target port of a service. Such as: the nginx program actually opens port 80. The input can be: the port range is 0-65535, the protocol is TCP or UDP, a plurality of ports can be input, and the ports are separated by English commas, such as: 80: TCP,9081: UDP, default 80: TCP;
5) Setting a container quota: the method comprises two quota selection modes of CPU limitation or memory limitation;
6) Setting a container environment variable, wherein the environment variable comprises three types of custom, reference configuration items or reference keys, and the referenced configuration items or key data are mapped into the specified environment variable;
7) Setting a container mounting roll, wherein the mounting roll comprises two mounting modes:
reference mount: providing a data mounting volume of a reference type for the container, wherein the data of the reference configuration item and the key are mounted in a specified directory of the container;
and (3) direct mounting: directly mounting different types of data volumes for the container, including a temporary directory and a host directory, and supporting the dynamic creation of volumes for specified storage types or mounting existing volumes;
8) Setting container health inspection: including HTTP inspection requests and TCP port inspection, configured with page hints, and no such option when the container type is the initial container;
9) Setting a container operation user: the container rights are set to protect the system and other containers from the user ID range 1-65534, and the container will run with the current user rights.
The application instance configuration process further includes automatic telescoping settings: and carrying out automatic expansion setting according to the CPU utilization rate or the memory utilization rate and the copy number of the application instance.
The application instance configuration process further includes affinity settings: including node affinity, application anti-affinity, custom affinity, and the like.
The method further comprises an application instance access configuration step, wherein the configuration is carried out by setting an access mode, and the access mode comprises the following steps: selecting intra-cluster access, domain name access or node access, default to domain name access.
When the access mode selects domain name access, the access configuration step further comprises setting a domain name, and the response speed of access is improved by setting the access domain name of the application instance.
The application instance access configuration process also comprises default port setting, and the response speed of access is improved by designating the default access port of the application instance service.
In the container configuration setting step, when a plurality of initial containers are set, the plurality of initial containers are sequentially operated one by one, and after successful execution is completed, the system continues to execute the next initial container.
In the container mirror image selection step, a mirror image needing to be deployed is selected from a mirror image list in a searching mode.
The above embodiments are only preferred embodiments of the present invention, and it is intended that the common variations and substitutions made by those skilled in the art within the scope of the technical solution of the present invention are included in the scope of the present invention.
Claims (1)
1. An automatic application instance publishing method based on container technology is characterized in that the method for publishing an initial version application instance comprises the following implementation processes: setting an application instance base configuration, setting a container configuration of a container instance, wherein:
the basic configuration includes the content: setting a published Kubernetes cluster, a published strategy, an instance type and a number of copies;
the container configuration includes the content: adding an application instance container, setting a container type, a container mirror image, a container port, a container quota, an environment variable, a mounting volume, a health check and an operation user; the application instance basic configuration setting step comprises the following steps:
1) Selecting a certain Kubernetes cluster by the cluster, and publishing an application instance to the appointed Kubernetes cluster;
2) Selecting a namespace: publishing the application instance under the namespace of the specified cluster;
3) Selecting release strategies, including three release strategies of rolling release, bluish green release or gray release;
4) Selecting instance types, including two load types, namely stateful or stateless;
5) The number of the selected copies: the number of the copies is between 1 and 20;
the step of container configuration of the container instance includes:
1) The adding container comprises: a plurality of containers can be added, including an application container and an initialization container, wherein a maximum of 10 containers can be added, and at least one application container is needed;
2) Selecting a container type, comprising:
the application container comprises: the container in which the application instance runs, an application instance must contain an application container;
initial container: preset conditions required for completing the application container before starting the application container;
3) Selecting a container mirror image: selecting images to be deployed from the image list;
4) Filling in a container port;
5) Setting a container quota: the method comprises two quota selection modes of CPU limitation or memory limitation;
6) Setting a container environment variable, wherein the environment variable comprises three types of custom, reference configuration items or reference keys, and the referenced configuration items or key data are mapped into the specified environment variable;
7) Setting a container mounting roll, wherein the mounting roll comprises two mounting modes:
reference mount: providing a data mounting volume of a reference type for the container, wherein the data of the reference configuration item and the key are mounted in a specified directory of the container;
and (3) direct mounting: directly mounting different types of data volumes for the container, including a temporary directory and a host directory, and supporting the dynamic creation of volumes for specified storage types or mounting existing volumes;
8) Setting container health inspection: including HTTP inspection requests and TCP port inspection, configured with page hints, and no such option when the container type is the initial container;
9) Setting a container operation user: setting the authority of the container, protecting the system and other containers from being influenced, wherein the user ID range is 1-65534, and the container operates with the current user authority;
the application instance configuration process also includes automatic telescoping settings: performing automatic expansion setting according to the CPU utilization rate or the copy number of the application instance corresponding to the memory utilization rate;
the application instance configuration process also includes affinity settings: including node affinity, application anti-affinity, custom affinity policy;
the method also comprises an application instance access configuration step, wherein the configuration is carried out by setting an access mode, and the access mode comprises the following steps: selecting intra-cluster access, domain name access or node access;
when the access mode selects domain name access, the access configuration step further comprises setting a domain name;
the application instance access configuration process also includes default port settings, through which default access ports for application instance services are specified;
in the container configuration setting step, when a plurality of initial containers are set, the containers are operated one by one in sequence, and after successful execution is completed, the system continues to execute the next initial container;
in the container mirror image selection step, a mirror image needing to be deployed is selected from a mirror image list in a searching mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010155717.9A CN111399855B (en) | 2020-03-09 | 2020-03-09 | Automatic application instance publishing method based on container technology |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010155717.9A CN111399855B (en) | 2020-03-09 | 2020-03-09 | Automatic application instance publishing method based on container technology |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111399855A CN111399855A (en) | 2020-07-10 |
| CN111399855B true CN111399855B (en) | 2023-10-20 |
Family
ID=71430596
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010155717.9A Active CN111399855B (en) | 2020-03-09 | 2020-03-09 | Automatic application instance publishing method based on container technology |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111399855B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112506615B (en) * | 2020-12-11 | 2023-11-03 | 浪潮电子信息产业股份有限公司 | Java Web application deployment method, device, equipment and storage medium |
| CN113342461B (en) * | 2021-05-31 | 2023-04-07 | 北京市商汤科技开发有限公司 | Equipment mounting method and device, computer equipment and readable storage medium |
| CN113626138B (en) * | 2021-06-30 | 2022-12-20 | 济南浪潮数据技术有限公司 | Application program access method and related device |
| CN115378808A (en) * | 2022-08-16 | 2022-11-22 | 广州骏伯网络科技有限公司 | Method for realizing blue-green release by using iptables |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107193504A (en) * | 2017-06-02 | 2017-09-22 | 郑州云海信息技术有限公司 | A kind of method and system of automation distribution and establishment application memory based on Kubernetes |
| US9928059B1 (en) * | 2014-12-19 | 2018-03-27 | Amazon Technologies, Inc. | Automated deployment of a multi-version application in a network-based computing environment |
| US10078537B1 (en) * | 2016-06-29 | 2018-09-18 | EMC IP Holding Company LLC | Analytics platform and associated controller for automated deployment of analytics workspaces |
| CN109032760A (en) * | 2018-08-01 | 2018-12-18 | 北京百度网讯科技有限公司 | Method and apparatus for application deployment |
| CN109117265A (en) * | 2018-07-12 | 2019-01-01 | 北京百度网讯科技有限公司 | The method, apparatus, equipment and storage medium of schedule job in the cluster |
| CN109309581A (en) * | 2018-08-22 | 2019-02-05 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Container management system crossing hardware architecture |
| CN109491674A (en) * | 2018-11-07 | 2019-03-19 | 李斌 | A kind of method and system of the automatic deployment service in Kubernetes cluster |
| WO2019095936A1 (en) * | 2017-11-15 | 2019-05-23 | 腾讯科技（深圳）有限公司 | Method and system for building container mirror image, and server, apparatus and storage medium |
| CN109981351A (en) * | 2019-03-06 | 2019-07-05 | 浪潮通用软件有限公司 | A kind of private clound dispositions method |
| CN110032376A (en) * | 2018-12-13 | 2019-07-19 | 中国电子科技集团公司电子科学研究院 | Automated software dispositions method and device based on Docker |
| CN110221845A (en) * | 2019-06-06 | 2019-09-10 | 江苏满运软件科技有限公司 | Using dispositions method, device, equipment and medium |
| CN110333877A (en) * | 2019-07-09 | 2019-10-15 | 西安点告网络科技有限公司 | Visualized container configuring management method, apparatus and system based on application |
| CN110427204A (en) * | 2019-08-08 | 2019-11-08 | 浪潮云信息技术有限公司 | A kind of automation gray scale dissemination method based on container and service grid |
| CN110489204A (en) * | 2019-07-01 | 2019-11-22 | 广东轩辕网络科技股份有限公司 | A kind of big data platform architecture system based on container cluster |
| CN110489205A (en) * | 2019-07-01 | 2019-11-22 | 广东轩辕网络科技股份有限公司 | A kind of education services architecture system based on container cluster |
| CN110502244A (en) * | 2019-07-11 | 2019-11-26 | 新华三大数据技术有限公司 | Dispose the method and device of Kubernetes cluster |
| US10558457B1 (en) * | 2018-08-24 | 2020-02-11 | Dais Technology, LLC | Platform discovery and deployment automation system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10225335B2 (en) * | 2011-02-09 | 2019-03-05 | Cisco Technology, Inc. | Apparatus, systems and methods for container based service deployment |
| EP3364623B1 (en) * | 2016-02-25 | 2022-05-04 | Huawei Technologies Co., Ltd. | Method for automatically deploying application, and cloud management node |
| US10915349B2 (en) * | 2018-04-23 | 2021-02-09 | Hewlett Packard Enterprise Development Lp | Containerized application deployment |
-
2020
- 2020-03-09 CN CN202010155717.9A patent/CN111399855B/en active Active
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9928059B1 (en) * | 2014-12-19 | 2018-03-27 | Amazon Technologies, Inc. | Automated deployment of a multi-version application in a network-based computing environment |
| US10078537B1 (en) * | 2016-06-29 | 2018-09-18 | EMC IP Holding Company LLC | Analytics platform and associated controller for automated deployment of analytics workspaces |
| CN107193504A (en) * | 2017-06-02 | 2017-09-22 | 郑州云海信息技术有限公司 | A kind of method and system of automation distribution and establishment application memory based on Kubernetes |
| WO2019095936A1 (en) * | 2017-11-15 | 2019-05-23 | 腾讯科技（深圳）有限公司 | Method and system for building container mirror image, and server, apparatus and storage medium |
| CN109117265A (en) * | 2018-07-12 | 2019-01-01 | 北京百度网讯科技有限公司 | The method, apparatus, equipment and storage medium of schedule job in the cluster |
| CN109032760A (en) * | 2018-08-01 | 2018-12-18 | 北京百度网讯科技有限公司 | Method and apparatus for application deployment |
| CN109309581A (en) * | 2018-08-22 | 2019-02-05 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Container management system crossing hardware architecture |
| US10558457B1 (en) * | 2018-08-24 | 2020-02-11 | Dais Technology, LLC | Platform discovery and deployment automation system |
| CN109491674A (en) * | 2018-11-07 | 2019-03-19 | 李斌 | A kind of method and system of the automatic deployment service in Kubernetes cluster |
| CN110032376A (en) * | 2018-12-13 | 2019-07-19 | 中国电子科技集团公司电子科学研究院 | Automated software dispositions method and device based on Docker |
| CN109981351A (en) * | 2019-03-06 | 2019-07-05 | 浪潮通用软件有限公司 | A kind of private clound dispositions method |
| CN110221845A (en) * | 2019-06-06 | 2019-09-10 | 江苏满运软件科技有限公司 | Using dispositions method, device, equipment and medium |
| CN110489204A (en) * | 2019-07-01 | 2019-11-22 | 广东轩辕网络科技股份有限公司 | A kind of big data platform architecture system based on container cluster |
| CN110489205A (en) * | 2019-07-01 | 2019-11-22 | 广东轩辕网络科技股份有限公司 | A kind of education services architecture system based on container cluster |
| CN110333877A (en) * | 2019-07-09 | 2019-10-15 | 西安点告网络科技有限公司 | Visualized container configuring management method, apparatus and system based on application |
| CN110502244A (en) * | 2019-07-11 | 2019-11-26 | 新华三大数据技术有限公司 | Dispose the method and device of Kubernetes cluster |
| CN110427204A (en) * | 2019-08-08 | 2019-11-08 | 浪潮云信息技术有限公司 | A kind of automation gray scale dissemination method based on container and service grid |
Non-Patent Citations (3)
| Title |
|---|
| 《k8s笔记六（kubernetes中容器的配置）》;dayi_123;《CSDN》;20190506;全文 * |
| 《基于K8S的Docker分布式容器自动化运维系统的设计与实现》;金子威;《中国优秀硕士学位论文全文数据库 信息科技辑》;20190515;全文 * |
| 《容器云平台的设计与实现》;徐江生;《中国优秀硕士学位论文全文数据库 信息科技辑》;20180315;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111399855A (en) | 2020-07-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111399855B (en) | Automatic application instance publishing method based on container technology | |
| CN107577475B (en) | Software package management method and system of data center cluster system | |
| US8949364B2 (en) | Apparatus, method and system for rapid delivery of distributed applications | |
| EP4010797A1 (en) | Dynamic image composition for container deployment | |
| US20090210869A1 (en) | Advanced packaging and deployment of virtual appliances | |
| CA2539460C (en) | System and method for dynamic version management of applications | |
| US9710249B2 (en) | Dynamic configuration of virtual appliances | |
| US20140007092A1 (en) | Automatic transfer of workload configuration | |
| CN112416524A (en) | Implementation method and device of cross-platform CI/CD (compact disc/compact disc) based on docker and kubernets offline | |
| US20040088397A1 (en) | System and method for management of software applications | |
| CN103425511A (en) | System and method of installing and deploying application software in cloud computing environment | |
| CN110727440A (en) | Software packaging method | |
| CN108073423A (en) | A kind of accelerator loading method, system and accelerator loading device | |
| CN113127150A (en) | Rapid deployment method and device of cloud native system, electronic equipment and storage medium | |
| CN111880738A (en) | Method for automatically creating and mounting LVM (logical volume manager) volume in K8s environment | |
| CN111857735A (en) | Method and system for creating Crush based on hook deployment Ceph | |
| CN113918281A (en) | Method for improving cloud resource expansion efficiency of container | |
| CN116783581A (en) | Deploying software release on a data center configured in a cloud platform | |
| WO2019152748A1 (en) | System and method for preserving entity identifiers for virtual machines | |
| CN114389934B (en) | Cloud platform control system based on created environment | |
| CN105144085A (en) | Software framework for a storage device | |
| CN116601605A (en) | Declaratively provisioning resources on a cloud platform | |
| CN111459510A (en) | Cross-network operating system installation method and device, electronic equipment and medium | |
| CN115543548B (en) | Configuration method, device and equipment of container group and readable storage medium | |
| CN116578353A (en) | Application starting method and device, computer equipment and storage medium |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230905 Address after: Energy Building 1-2201, No. 10777 Jingshi Road, Jinan Area, China (Shandong) Pilot Free Trade Zone, Jinan City, Shandong Province, 250013 Applicant after: Shandong Electronic Port Co.,Ltd. Address before: Floor S06, Inspur Science Park, No. 1036, Inspur Road, hi tech Zone, Jinan City, Shandong Province Applicant before: SHANDONG HUIMAO ELECTRONIC PORT Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |