CN111708608A - Container large cluster rapid deployment method and system based on infrastructure - Google Patents
Container large cluster rapid deployment method and system based on infrastructure Download PDFInfo
- Publication number
- CN111708608A CN111708608A CN202010562960.2A CN202010562960A CN111708608A CN 111708608 A CN111708608 A CN 111708608A CN 202010562960 A CN202010562960 A CN 202010562960A CN 111708608 A CN111708608 A CN 111708608A
- Authority
- CN
- China
- Prior art keywords
- module
- kubedm
- deployment
- mirror image
- ansable
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- 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
Abstract
The invention discloses a container large cluster rapid deployment method and system based on ansible, belonging to the field of kubernets cluster deployment; the method comprises the following steps: s1, compiling the kubedm based on the ansable framework; s2 executing phase by using the written kubedm; s3, manufacturing a docker mirror image, and driving the installation package into the mirror image; s4, pulling the mirror image of the installation package, and executing the ansable script in the mirror image; s5, storing and summarizing the ansable execution log by the kubedm; the method writes the kubedm to be responsible for each step of operation of specific execution, the kubedm initiates the operation, the operation can be executed on all nodes simultaneously, the execution time is saved, each large step in the kubedm contains a plurality of phases, and the script images are manufactured and installed, so that each node can run an ansibel script.
Description
Technical Field
The invention discloses a container large cluster rapid deployment method and system based on ansible, and relates to the technical field of kubernets cluster deployment.
Background
In recent years, with the development of cloud computing and cloud services, container technology is widely applied, kubernets are increasingly emphasized as advanced container arrangement systems, and in the past application of kubernets, the cluster scale of kubernets is not large due to the fact that the number of services needing to be supported is small. However, with the development, more and more services are migrated to kubernets clusters, and with the increase of pressure, the required cluster size is larger and larger, but when the cluster size is large to a certain extent, the cluster deployment problem is more severe, and how to rapidly deploy a large container cluster, so that a method and a system for rapidly deploying a large container cluster based on an alarm are invented to solve the problems.
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a container large cluster rapid deployment method and system based on an anchor, and the adopted technical scheme is as follows:
a container large cluster rapid deployment method based on anchor is characterized by comprising the following steps:
s1, compiling the kubedm based on the ansable framework;
s2 executing phase by using the written kubedm;
s3, manufacturing a docker mirror image, and driving the installation package into the mirror image;
s4, pulling the mirror image of the installation package, and executing the ansable script in the mirror image;
and S5 kubedm stores and summarizes the ansable execution log.
And the S1 adds a deployment cluster function when the kubedm is written based on the ansable framework.
The method for compiling the kubedm based on the ansable framework comprises the following specific steps of:
s101, initializing a node;
s102, mounting an etcd cluster;
s103, initializing kubel;
s104, initializing a master node;
s105, installing a node;
s106, installing a network plug-in;
s107, initializing a storage plug-in;
s108, the detection script and the backup script are initialized.
The specific execution step of the S2 for executing the phase by using the written kubeadm comprises the following steps:
s201 executes common;
s211, executing the ansible script and adjusting the corresponding role;
s212, processing the log and returning an execution result.
A container large cluster rapid deployment system based on infrastructure comprises an arrangement module, a deployment module, a combination module, an execution module and a summary module:
an arrangement module: compiling the kubedm based on an ansable framework;
a deployment module: executing phase by using the written kubedm;
combining the modules: manufacturing a docker mirror image, and driving an installation package into the mirror image;
an execution module: pulling the installation package mirror image, and executing an ansable script in the mirror image;
a summary module: and the kubetm stores and summarizes the ansable execution logs.
The arranging module adds a deployment cluster function when compiling the kubedm based on the ansable framework.
The arrangement module specifically comprises:
a first processing module: initializing a node;
a first mounting module: installing an etcd cluster;
a second processing module: initializing a kubel;
a third processing module: initializing a master node;
a second mounting module: installing a node;
a third mounting module: installing a network plug-in;
a fourth processing module: initializing a storage plug-in;
a fifth processing module: and initializing the detection script and the backup script.
The deployment module specifically comprises a deployment execution module, a deployment calling module and a deployment processing module:
the deployment execution module: s201 executes common;
deploying and calling the module: s211, executing the ansible script and adjusting the corresponding role;
a deployment processing module: s212, processing the log and returning an execution result.
The invention has the beneficial effects that: the method writes the kubedm to be responsible for each step of operation of specific execution, the kubedm initiates the operation, the operation can be executed on all nodes simultaneously, the execution time is saved, each large step in the kubedm contains a plurality of phases, and the script images are manufactured and installed, so that each node can run an ansibel script.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of the method of the present invention; FIG. 2 is a schematic diagram of the system of the present invention; FIG. 3 is a diagram of an installation process for a script.
Detailed Description
The present invention is further described below in conjunction with the following figures and specific examples so that those skilled in the art may better understand the present invention and practice it, but the examples are not intended to limit the present invention.
Kubernets is an advanced container orchestration system, and clusters are deployed with the following core concepts:
cluster scale: the larger the number of nodes is, the larger the scale is.
master node: and the container cluster management node is used for deploying the cluster management component.
A work node: and the container cluster working node is managed by the master node.
Cluster deployment: deploying a kubernets cluster on a planning node, wherein the node initialization and the deployment of each component are included;
the first embodiment is as follows:
a container large cluster rapid deployment method based on anchor comprises the following steps:
s1, compiling the kubedm based on the ansable framework;
s2 executing phase by using the written kubedm;
s3, manufacturing a docker mirror image, and driving the installation package into the mirror image;
s4, pulling the mirror image of the installation package, and executing the ansable script in the mirror image;
s5, storing and summarizing the ansable execution log by the kubedm;
when the method is used for large container cluster deployment, based on an audible framework, according to S1, a kubadm is compiled and named as kubadm-instur, phase is executed according to S2 through the compiled kubadm-instur, then a docker mirror image is made through S3, an installation package is driven into the made mirror image, then the installation package mirror image is pulled according to S4, audible scripts in the mirror image are executed as shown in FIG. 3, finally the audible scripts are executed according to S5 by using the kubadm-instur, corresponding role is adjusted, logs of the tasks are processed, and execution results are returned;
the method writes the kubadm-inster to be responsible for each step of operation of specific execution, the kubadm-inster initiates the operation, the operation can be executed on all nodes at the same time, the execution time is saved, each big step in the kubadm-inster comprises a plurality of phases, and the manufactured and installed script images can enable each node to run an ansibel script;
further, the S1 adds a deployment cluster function when compiling the kubedm based on the ansable framework;
further, the step S1 of compiling kubedm based on the ansable framework specifically includes:
s101, initializing a node;
s102, mounting an etcd cluster;
s103, initializing kubel;
s104, initializing a master node;
s105, installing a node;
s106, installing a network plug-in;
s107, initializing a storage plug-in;
s108, initializing a detection script and a backup script;
when the kubadm is written according to S1 based on the infrastructure framework, prepare is performed according to S101 node initialization, and a kubadm-inpur prepare-config config is called, which is mainly used for node initialization related operations, and includes the following phases: calling secret for configuring the secret-free login of each node and the node in the cluster; calling a node-parameter for configuring node system parameters, such as the maximum file number, the process number and the like, and dns and hosts files; calling docker for initializing docker configuration; calling load-images for mirroring the load docker to the node;
each phase can be operated independently, and kubeadm-inner prep phase secret-configconfig;
installing the etcd cluster according to 102 for Setcd, calling kubeudm-inpur etcd-config config, mainly used for installing the etcd cluster, and comprising the following phases: calling the etcd-server for deploying the etcd cluster; invoking etcd-client for initializing the non-etcd node certificate;
each phase can be independently operated, and kubedm-inpur etcd phase etcd-server-config config is called;
initializing the kubel according to S103 to be node, calling the beacon-inpur kube-node-configconfigconfig, mainly used for initializing the kubel, and comprising the following phases: calling a be-node for installing the kubel and initializing configuration;
each phase can be operated independently, and the bean-inpur club-node-config config is called;
initializing the master node according to S104 to perform kube-master, calling kube-inpur kube-master-config config, mainly used for initializing the master node, and comprising the following phases: calling keepalived to initialize keepalived configuration; calling a key component of a kube-master installation master to call a client to configure kubecect; calling cluster-roles authority configuration;
each phase can be independently operated, and kubedm-inpur kube-masterphasekeepalived-config config is called;
installing a node according to S105 to perform join-node, calling kubedm-inpur join-node-config config, mainly used for installing the node, and comprising the following phase: calling a join-node to install a node;
each phase can be independently operated, and a kubedm-inpur join-node phase join-node-config config is called;
installing a network plug-in to carry out network according to S106, calling kubedm-inpur network-configconfigconfig, mainly used for installing the network plug-in, and comprising the following phase: calling cni to configure cni plug-in, and initializing the calico configuration; calling start to start the calico-node; invoking
The policy-controller starts the calico-kubecontroller; calling a router-reflector to configure rr nodes;
each phase can be independently operated, and kubedm-input network phase cni-configconfig is called;
initializing the memory plug-in to store according to S107, and calling kubeeam-instruction storage-configconfigconfigconfig, wherein the kubeeam-instruction storage-config is mainly used for initializing the memory plug-in and comprises the following phases: calling the flexdriver to install the flexdriver; calling a provisioner to install the provisioner in a binary deployment mode; calling a script configuration detection script; calling a provisosner of a provisioner-pod installation pod deployment mode;
each phase can be independently operated, and a kubedm-instruction storage phase flexdriver-config config is called;
finally, initializing the detection script and the backup script according to S108 to perform monitors, calling kubbeam-inpurronitors-config config, mainly used for initializing the detection script and the backup script, and comprising the following phases: calling a kemonitor to initialize detection scripts such as rbd detection, split brain detection and the like; calling backup-etcd-data to backup etcd data; calling the etcd-check to install the etcd detection program;
each phase can independently run and call kubedm-instruction monomers phase manager-config config;
still further, the specific step of executing the phase by using the written kubeadm in S2 includes:
s201 executes common;
s211, executing the ansible script and adjusting the corresponding role;
s212, processing the log and returning an execution result;
in S2, the kubeadm-instur executes phase mainly in the following two ways:
for a simple operation, common is executed as by S201, and common is executed using a code;
for complex operation, executing the ansable script according to S211, adjusting the corresponding role, processing the log of the role, and returning the execution result.
Example two:
a container large cluster rapid deployment system based on infrastructure comprises an arrangement module, a deployment module, a combination module, an execution module and a summary module:
an arrangement module: compiling the kubedm based on an ansable framework;
a deployment module: executing phase by using the written kubedm;
combining the modules: manufacturing a docker mirror image, and driving an installation package into the mirror image;
an execution module: pulling the installation package mirror image, and executing an ansable script in the mirror image;
a summary module: the kubedm stores and summarizes the ansable execution log;
when container large cluster deployment is carried out through the system, based on an audible framework, a kubadm is compiled according to an arranging module and named as kubadm-inster, the compiled kubadm-inster uses the arranging module to execute phase, then a docker mirror image is made through a combination module, an installation package is injected into the made mirror image, then the execution module is used for pulling the installation package mirror image, audible scripts in the mirror image are executed, finally the summarizing module is used for executing audible scripts through the kubadm-inster, corresponding role is adjusted, logs of the role are processed, and execution results are returned;
the system writes the kubadm-inster to be responsible for each step of operation of specific execution, the kubadm-inster initiates the operation, the operation can be executed on all nodes at the same time, the execution time is saved, each big step in the kubadm-inster comprises a plurality of phases, and the manufactured and installed script images can enable each node to run an ansibel script;
further, the arranging module adds a deployment cluster function when compiling the kubedm based on the ansable framework;
further, the arrangement module specifically includes:
a first processing module: s101, initializing a node;
a first mounting module: s102, mounting an etcd cluster;
a second processing module: s103, initializing kubel;
a third processing module: s104, initializing a master node;
a second mounting module: s105, installing a node;
a third mounting module: s106, installing a network plug-in;
a fourth processing module: s107, initializing a storage plug-in;
a fifth processing module: s108, initializing a detection script and a backup script;
still further, the specific step of executing the phase by using the written kubeadm in S2 includes:
the deployment module specifically comprises a deployment execution module, a deployment calling module and a deployment processing module:
the deployment execution module: executing common;
deploying and calling the module: executing the ansable script and adjusting the corresponding role;
a deployment processing module: processing the log and returning an execution result;
the deployment module kubedm-instur executes phase mainly in the following two ways:
for simple operations, common is executed according to the deployment execution module, and is executed by using codes;
for complex operation, executing the ansable script according to the deployment and calling module, calling the corresponding role, processing the log by the deployment and processing module, and returning an execution result.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (8)
1. A container large cluster rapid deployment method based on anchor is characterized by comprising the following steps:
s1, compiling the kubedm based on the ansable framework;
s2 executing phase by using the written kubedm;
s3, manufacturing a docker mirror image, and driving the installation package into the mirror image;
s4, pulling the mirror image of the installation package, and executing the ansable script in the mirror image;
and S5 kubedm stores and summarizes the ansable execution log.
2. The method for rapidly deploying container large clusters based on the ansable according to claim 1, wherein the S1 is added with a cluster deploying function when the kubedm is written based on the ansable framework.
3. The anchor-based container large cluster rapid deployment method according to claim 2, wherein the anchor-based framework writing kubedm comprises the following specific steps:
s101, initializing a node;
s102, mounting an etcd cluster;
s103, initializing kubel;
s104, initializing a master node;
s105, installing a node;
s106, installing a network plug-in;
s107, initializing a storage plug-in;
s108, the detection script and the backup script are initialized.
4. The method for rapidly deploying container large clusters based on anchored according to claim 3, wherein the specific execution step of S2 for executing phase by using written kubedm comprises:
s201 executes common;
s211, executing the ansible script and adjusting the corresponding role;
s212, processing the log and returning an execution result.
5. A container large cluster rapid deployment system based on infrastructure is characterized by comprising an arrangement module, a deployment module, a combination module, an execution module and a summary module:
an arrangement module: compiling the kubedm based on an ansable framework;
a deployment module: executing phase by using the written kubedm;
combining the modules: manufacturing a docker mirror image, and driving an installation package into the mirror image;
an execution module: pulling the installation package mirror image, and executing an ansable script in the mirror image;
a summary module: and the kubetm stores and summarizes the ansable execution logs.
6. The anchor-based container large cluster rapid deployment system as claimed in claim 5, wherein the orchestration module adds a deployment cluster function when compiling kubedm based on an anchor framework.
7. The anchor-based rapid deployment system for large container clusters according to claim 6, wherein the orchestration module specifically comprises:
a first processing module: initializing a node;
a first mounting module: installing an etcd cluster;
a second processing module: initializing a kubel;
a third processing module: initializing a master node;
a second mounting module: installing a node;
a third mounting module: installing a network plug-in;
a fourth processing module: initializing a storage plug-in;
a fifth processing module: and initializing the detection script and the backup script.
8. The system for rapidly deploying the large container cluster based on the infrastructure according to claim 7, wherein the deployment module specifically comprises a deployment execution module, a deployment retrieval module and a deployment processing module:
the deployment execution module: s201 executes common;
deploying and calling the module: s211, executing the ansible script and adjusting the corresponding role;
a deployment processing module: s212, processing the log and returning an execution result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010562960.2A CN111708608B (en) | 2020-06-19 | 2020-06-19 | Container large cluster rapid deployment method and system based on stable |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010562960.2A CN111708608B (en) | 2020-06-19 | 2020-06-19 | Container large cluster rapid deployment method and system based on stable |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111708608A true CN111708608A (en) | 2020-09-25 |
| CN111708608B CN111708608B (en) | 2023-04-25 |
Family
ID=72542261
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010562960.2A Active CN111708608B (en) | 2020-06-19 | 2020-06-19 | Container large cluster rapid deployment method and system based on stable |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111708608B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112328361A (en) * | 2020-11-02 | 2021-02-05 | 杭州当虹科技股份有限公司 | Method for rapidly deploying kubenetes cluster |
| CN112416524A (en) * | 2020-11-25 | 2021-02-26 | 电信科学技术第十研究所有限公司 | Implementation method and device of cross-platform CI/CD (compact disc/compact disc) based on docker and kubernets offline |
| CN112491606A (en) * | 2020-11-20 | 2021-03-12 | 湖南麒麟信安科技股份有限公司 | Method for automatically deploying high-availability cluster of service system based on infrastructure |
| CN113626043A (en) * | 2021-08-04 | 2021-11-09 | 湖北美和易思教育科技有限公司 | Kubernetes-based automatic container development environment packaging method and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108694053A (en) * | 2018-05-14 | 2018-10-23 | 平安科技（深圳）有限公司 | Build the method and terminal device of Kubernetes host nodes automatically based on Ansible tools |
| CN109104305A (en) * | 2018-07-26 | 2018-12-28 | 广东浪潮大数据研究有限公司 | A kind of node increases method and relevant apparatus |
| CN109976774A (en) * | 2019-04-11 | 2019-07-05 | 北京启迪区块链科技发展有限公司 | Block chain node deployment method, device, equipment and storage medium |
| CN109981351A (en) * | 2019-03-06 | 2019-07-05 | 浪潮通用软件有限公司 | A kind of private clound dispositions method |
| CN110333889A (en) * | 2019-07-19 | 2019-10-15 | 浪潮云信息技术有限公司 | The upgrade method and system of container service user's cluster |
| CN110806881A (en) * | 2019-11-05 | 2020-02-18 | 浪潮云信息技术有限公司 | Method for deploying different CPU architectures by kubernets |
| US20200195501A1 (en) * | 2018-12-17 | 2020-06-18 | Juniper Networks, Inc. | Network device configuration using a message bus |
-
2020
- 2020-06-19 CN CN202010562960.2A patent/CN111708608B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108694053A (en) * | 2018-05-14 | 2018-10-23 | 平安科技（深圳）有限公司 | Build the method and terminal device of Kubernetes host nodes automatically based on Ansible tools |
| CN109104305A (en) * | 2018-07-26 | 2018-12-28 | 广东浪潮大数据研究有限公司 | A kind of node increases method and relevant apparatus |
| US20200195501A1 (en) * | 2018-12-17 | 2020-06-18 | Juniper Networks, Inc. | Network device configuration using a message bus |
| CN109981351A (en) * | 2019-03-06 | 2019-07-05 | 浪潮通用软件有限公司 | A kind of private clound dispositions method |
| CN109976774A (en) * | 2019-04-11 | 2019-07-05 | 北京启迪区块链科技发展有限公司 | Block chain node deployment method, device, equipment and storage medium |
| CN110333889A (en) * | 2019-07-19 | 2019-10-15 | 浪潮云信息技术有限公司 | The upgrade method and system of container service user's cluster |
| CN110806881A (en) * | 2019-11-05 | 2020-02-18 | 浪潮云信息技术有限公司 | Method for deploying different CPU architectures by kubernets |
Non-Patent Citations (2)
| Title |
|---|
| CHENLEIKING: "使用Ansible+kubeadm部署K8S集群", 《开发者知识库》 * |
| 青蛙小白: "使用kubeadm安装Kubernetes 1.13", 《KUBERNETES中文社区》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112328361A (en) * | 2020-11-02 | 2021-02-05 | 杭州当虹科技股份有限公司 | Method for rapidly deploying kubenetes cluster |
| CN112491606A (en) * | 2020-11-20 | 2021-03-12 | 湖南麒麟信安科技股份有限公司 | Method for automatically deploying high-availability cluster of service system based on infrastructure |
| CN112491606B (en) * | 2020-11-20 | 2022-05-24 | 湖南麒麟信安科技股份有限公司 | Method for automatically deploying high-availability cluster of service system based on infrastructure |
| CN112416524A (en) * | 2020-11-25 | 2021-02-26 | 电信科学技术第十研究所有限公司 | Implementation method and device of cross-platform CI/CD (compact disc/compact disc) based on docker and kubernets offline |
| CN113626043A (en) * | 2021-08-04 | 2021-11-09 | 湖北美和易思教育科技有限公司 | Kubernetes-based automatic container development environment packaging method and system |
| CN113626043B (en) * | 2021-08-04 | 2024-04-05 | 武汉美和易思数字科技有限公司 | Automatic packaging method and system for container development environment based on Kubernetes |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111708608B (en) | 2023-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111708608A (en) | Container large cluster rapid deployment method and system based on infrastructure | |
| US11385993B2 (en) | Dynamic integration of command line utilities | |
| US20130151598A1 (en) | Apparatus, systems and methods for deployment of interactive desktop applications on distributed infrastructures | |
| EP1840741A1 (en) | Device, method, and computer program product for accessing a non-native application executing in a virtual machine environment | |
| WO2002075540A2 (en) | Method and apparatus for providing application specific strategies to a java platform including load balancing policies | |
| CN111026414B (en) | HDP platform deployment method based on kubernetes | |
| CN111610985B (en) | Kubernetes cluster rapid deployment method on domestic platform | |
| WO2002084479A2 (en) | Method and apparatus for performing online application upgrades in a java platform | |
| CN105099739A (en) | Plug-in type software deployment method and apparatus, and application server | |
| CN111897633A (en) | Task processing method and device | |
| CN112099919B (en) | Application service visualization rapid deployment method based on cloud computing API | |
| CN112328361A (en) | Method for rapidly deploying kubenetes cluster | |
| WO2002084487A2 (en) | Method and apparatus for performing failure recovery in a java platform | |
| US20020144002A1 (en) | Method and apparatus for providing application specific strategies to a JAVA platform including start and stop policies | |
| CN106850598B (en) | Uniform resource management system and method for whole-ship computing environment | |
| CN114661420B (en) | Application protection method, device and system based on Kubernetes container platform | |
| CN112564979B (en) | Execution method and device of construction task, computer equipment and storage medium | |
| CN115442372A (en) | Interface calling method and micro-service application system applying same | |
| CN111984275A (en) | System deployment method, system, terminal and storage medium based on CPU architecture type | |
| CN110661852B (en) | Service processing method and device in cloud environment | |
| CN210007726U (en) | private cloud service systems | |
| CN111008043A (en) | Server starting method of cloud platform and terminal | |
| CN111190693B (en) | Method and device for building cloud platform based on Kunpeng platform | |
| US20240111579A1 (en) | Termination of sidecar containers | |
| US11729051B2 (en) | Automated deployment of control nodes at remote locations |
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 |