CN113064598B - Container cluster management system deployment method and deployment system - Google Patents
Container cluster management system deployment method and deployment system Download PDFInfo
- Publication number
- CN113064598B CN113064598B CN202110314672.XA CN202110314672A CN113064598B CN 113064598 B CN113064598 B CN 113064598B CN 202110314672 A CN202110314672 A CN 202110314672A CN 113064598 B CN113064598 B CN 113064598B
- Authority
- CN
- China
- Prior art keywords
- data
- name
- profile
- type
- metadata
- 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 25
- 238000006243 chemical reaction Methods 0.000 claims description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000004806 packaging method and process 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a container cluster management system deployment method, which comprises the steps of creating a first configuration file through another markup language, creating a second configuration file through the other markup language, executing the first configuration file, and executing the second configuration file, so that the deployment of a container cluster management system is realized, the practicability of third-party software is not needed, and the difficulty of the deployment of the container cluster management system is reduced. The invention also provides a deployment system for realizing the deployment method of the container cluster management system.
Description
Technical Field
The invention relates to the field of container cluster management systems, in particular to a position calibration method and a position calibration device.
Background
The machine solves the problems of excessive manual participation and complexity of each step of compiling, packaging the mirror image, uploading the mirror image and deploying the application during the release of the application, and realizes the automatic deployment of a container cluster management system (k 8 s).
The prior art is realized by third-party software such as jenkins, gitlab-CI, functions are similar, but each has own inherent configuration rules, is not suitable for entering the door, and is complicated in configuration.
The Chinese patent with publication number of CN112379946A discloses a template configuration method, device and computer equipment based on YAML, which can solve the problems that the current configurable template generation mode is high in configuration cost and insufficient in stability, and the signal to noise ratio and configuration structure cannot meet the normal requirements, wherein the method comprises the following steps: the method comprises the steps of obtaining a target template type to be configured, receiving a YAML configuration file, determining a template configuration rule corresponding to the target template type, wherein the template configuration rule comprises a target data field and a data assembly rule between the target data fields, and generating a configurable template based on the target data field, the data assembly rule and the YAML configuration file. However, the technical scheme cannot realize the deployment of the container cluster management system.
Therefore, there is a need to provide a novel container cluster management system deployment method and deployment system to solve the above-mentioned problems in the prior art.
Disclosure of Invention
The invention aims to provide a deployment method and a deployment system for a container cluster management system, which reduce the deployment difficulty of the container cluster management system.
In order to achieve the above object, the method for deploying a container cluster management system according to the present invention comprises the following steps:
s1: creating a first configuration file through another markup language, and creating a second configuration file through the other markup language;
s2: and executing the first configuration file and the second configuration file to realize the deployment of the container cluster management system.
The container cluster management system deployment method has the beneficial effects that: the first configuration file is created through another markup language, the second configuration file is created through the other markup language, the first configuration file is executed, and the second configuration file is executed, so that the deployment of the container cluster management system is realized, the practicability of third-party software is not needed, and the difficulty of the deployment of the container cluster management system is reduced.
Preferably, in the step S1, the creating the first profile by creating the first profile in another markup language includes setting a first main application interface type, a first profile type, first metadata, first specification data, and status data.
Further preferably, the first profile type is a custom resource.
Further preferably, the first metadata includes management field data and a metadata configuration file name, where the management field data includes a metadata first application interface type and a metadata second application interface type, and in step S2, when the first configuration file is executed, it is determined that the application interface type of the metadata is the first metadata reference interface type, a first main method is executed and updated, and when it is determined that the application interface type of the metadata is the second metadata reference interface type, a second main method is executed and updated.
Further preferably, the first specification data includes conversion data, group data, name group data including name type data, list type data, plural data, singular data, and name abbreviation data, and version data including additional printer column data including first state description data including state phase path data, state name data, and character string type data, and second state description data including start state description data, date and time format data, state start path data, age name data, and date type data.
Further preferably, the status data includes reception name data including reception name type data, reception name list type data, reception plural data, reception name abbreviation data, and reception singular data, and storage version data.
Preferably, in the step S1, creating the second configuration file through the other markup language includes creating second main application type interface data, second configuration file type data, second metadata, and second specification data.
Further preferably, the second specification data includes entry point data and template data.
Further preferably, the template data includes name group data and at least one piece of single name data, the name group data includes at least one piece of sub-name data, the sub-name data corresponds to the single name data one by one, in the step S2, when the second configuration file is executed, the name data is received, whether the number of the name data is greater than 1 is judged, when the number of the name data is greater than 1 is judged, the name data is matched with the sub-name data, the single name data is called according to the matched sub-name data, corresponding configuration processing is executed, and when the number of the name data is judged to be 1, the name data is directly matched with the single name data, and corresponding configuration processing is executed.
The invention also provides a deployment system which comprises a configuration file creation unit and an execution unit which are connected with each other, wherein the configuration file creation unit is used for creating a first configuration file and a second configuration file through another markup language, and the execution unit is used for executing the first configuration file and the second configuration file so as to realize the deployment of the container cluster management system.
The deployment system has the beneficial effects that: the configuration file creating unit is used for creating a first configuration file and a second configuration file through another markup language, and the executing unit is used for executing the first configuration file and the second configuration file so as to realize the deployment of the container cluster management system, the practicability of third-party software is not needed, and the difficulty of the deployment of the container cluster management system is reduced.
Drawings
FIG. 1 is a flow chart of a method of deploying a container cluster management system of the present invention;
fig. 2 is a block diagram of the deployment system of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention. Unless otherwise defined, technical or scientific terms used herein should be given the ordinary meaning as understood by one of ordinary skill in the art to which this invention belongs. As used herein, the word "comprising" and the like means that elements or items preceding the word are included in the element or item listed after the word and equivalents thereof without precluding other elements or items.
In view of the problems existing in the prior art, an embodiment of the present invention provides a container cluster management system deployment method, referring to fig. 1, including the following steps:
s1: creating a first profile by means of another markup language (YAMLAin't Markup Language, yaml), creating a second profile by means of said another markup language;
s2: and executing the first configuration file and the second configuration file to realize the deployment of the container cluster management system.
The invention further provides a deployment system 100, the deployment system 100 comprises a configuration file creation unit 101 and an execution unit 102 which are connected with each other, the configuration file creation unit 101 is used for creating a first configuration file and a second configuration file through another markup language, and the execution unit 102 is used for executing the first configuration file and the second configuration file so as to realize the deployment of the container cluster management system.
In some embodiments of the present invention, in the step S1, the creating the first configuration file through another markup language includes setting a first main application interface type, a first configuration file type, first metadata, first specification data, and status data. Specifically, the first host application interface type is "extensions.k8s.io/v 1".
In some embodiments of the invention, the first profile type is a custom resource (CustomResourceDefinition, CRD).
In some embodiments of the present invention, the first metadata includes management field data and a metadata configuration file name, where the management field data includes a metadata first application interface type and a metadata second application interface type, and in step S2, when the first configuration file is executed, it is determined that the application interface type of the metadata is the first metadata reference interface type, a first main method is executed and updated, and when it is determined that the application interface type of the metadata is the second metadata reference interface type, a second main method is executed and updated. Specifically, the metadata first application interface type is "apiextensions.k8s.io/v1", and the metadata second application interface type is "apiextensions.k8s.io/v1beta1".
In some embodiments of the present invention, the first specification data includes conversion data, group data, name group data, save field data, scope data, and version data, the name group data includes name type data, list type data, plural data, singular data, and name abbreviation data, the version data includes additional printer column data including first state description data including state phase path data, state name data, and character string type data, and second state description data including start state description data, date and time format data, state start path data, age name data, and date type data.
In still other embodiments of the present invention, the additional printer column data further comprises additional printer column name data, service data, storage data, and child resource data. Specifically, the save area data, the service data, and the storage data are all true.
In some embodiments of the invention, the status data includes received name data and stored version data, the received name data including received name type data, received name list type data, received plural data, received name abbreviation data, and received singular data. Specifically, the stored version data is "v1alpha1".
In some embodiments of the present invention, in the step S1, creating the second configuration file through the other markup language includes creating second main application type interface data, second configuration file type data, second metadata, and second specification data.
In some embodiments of the invention, the second specification data includes entry point data and template data.
In some embodiments of the present invention, the template data includes name group data and at least one single name data, the name group data includes at least one sub-name data, the sub-name data corresponds to the single name data one by one, in the step S2, when the second configuration file is executed, the name data is received, whether the number of the name data is greater than 1 is judged, when the number of the name data is greater than 1 is judged, the name data is matched with the sub-name data, the single name data is called according to the matched sub-name data, and corresponding configuration processing is executed, and when the number of the name data is judged to be 1, the name data is directly matched with the single name data, and corresponding configuration processing is executed.
Specifically, the name group data includes four pieces of sub-name data, which are respectively first sub-name data, second sub-name data, third sub-name data and fourth sub-name data, the number of the single-name data is 4, which are respectively first single-name data, second single-name data, third single-name data and fourth single-name data, wherein the first sub-name data corresponds to the first single-name data, the second sub-name data corresponds to the second single-name data, the third sub-name data corresponds to the third single-name data, the fourth sub-name data corresponds to the fourth single-name data, and the first single-name data, the second single-name data, the third single-name data and the fourth single-name data each include container data including container image data, "cmmand" commands and transfer character string data commands.
While embodiments of the present invention have been described in detail hereinabove, it will be apparent to those skilled in the art that various modifications and variations can be made to these embodiments. It is to be understood that such modifications and variations are within the scope and spirit of the present invention as set forth in the following claims. Moreover, the invention described herein is capable of other embodiments and of being practiced or of being carried out in various ways.
Claims (5)
1. A method for deploying a container cluster management system, comprising the steps of:
s1: creating a first profile through another markup language YAML, and creating a second profile through the another markup language YAML;
s2: executing the first configuration file and the second configuration file to realize the deployment of the container cluster management system
In said step S1, said creating a first profile by means of another markup language YAML comprises setting a first host application interface type, a first profile type, first metadata, first specification data and status data,
the first metadata includes management field data and metadata profile names, the management field data includes metadata first application interface type and metadata second application interface type, and in step S2, when the first profile is executed:
executing a first main method and updating if the application interface type of the metadata is judged to be the first reference interface type of the metadata;
judging the application interface type of the metadata is the metadata second reference interface type, executing a second main method and updating,
in said step S1, said creating a second profile by means of said further markup language YAML comprises creating second host application type interface data, second profile type data, second metadata and second specification data, said second specification data comprising entry point data and template data,
the template data comprises name group data and at least one single name data, the name group data comprises at least one piece of sub-name data, the sub-name data corresponds to the single name data one by one, in the step S2, when the second configuration file is executed, the name data is received, and whether the number of the name data is larger than 1 is judged:
when the number of the name data is judged to be larger than 1, matching the name data with the sub-name data, calling the single-name data according to the matched sub-name data, and executing corresponding configuration processing; and when the number of the name data is judged to be 1, directly matching the name data with the single name data and executing corresponding configuration processing.
2. The container cluster management system deployment method of claim 1, wherein the first profile type is a custom resource.
3. The container cluster management system deployment method of claim 1, wherein the first specification data comprises conversion data, group data, name group data, save field data, scope data, and version data, the name group data comprising name type data, list type data, plural data, singular data, and name abbreviation data, the version data comprising additional printer column data comprising first state description data comprising state phase path data, state name data, and string type data, and second state description data comprising start state description data, date time format data, state start path data, age name data, and date type data.
4. The container cluster management system deployment method of claim 1, wherein the status data comprises received name data and stored version data, the received name data comprising received name type data, received name list type data, received plural data, received name abbreviation data, and received singular data.
5. A deployment system for implementing the container cluster management system deployment method according to any one of claims 1 to 4, wherein the deployment system comprises a profile creation unit and an execution unit connected to each other, the profile creation unit is configured to create a first profile and a second profile through another markup language YAML, and the execution unit is configured to execute the first profile and the second profile to implement the deployment of the container cluster management system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110314672.XA CN113064598B (en) | 2021-03-24 | 2021-03-24 | Container cluster management system deployment method and deployment system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110314672.XA CN113064598B (en) | 2021-03-24 | 2021-03-24 | Container cluster management system deployment method and deployment system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113064598A CN113064598A (en) | 2021-07-02 |
| CN113064598B true CN113064598B (en) | 2024-02-06 |
Family
ID=76561719
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110314672.XA Active CN113064598B (en) | 2021-03-24 | 2021-03-24 | Container cluster management system deployment method and deployment system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113064598B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115495059B (en) * | 2022-09-23 | 2023-10-31 | 北京曼恒数字技术有限公司 | Method for creating data structure |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106982266A (en) * | 2017-05-27 | 2017-07-25 | 郑州云海信息技术有限公司 | A kind of method and apparatus of automatically dispose cluster |
| CN107967159A (en) * | 2017-11-22 | 2018-04-27 | 腾讯科技（深圳）有限公司 | The method and server of a kind of profileapplied |
| CN109104318A (en) * | 2018-08-23 | 2018-12-28 | 广东轩辕网络科技股份有限公司 | The dispositions method and system of method for realizing cluster self-adaption deployment, the self-adaption deployment big data cluster based on cloud platform |
| CN109885316A (en) * | 2019-02-18 | 2019-06-14 | 国家计算机网络与信息安全管理中心 | Hdfs-hbase dispositions method and device based on kubernetes |
| CN110113185A (en) * | 2019-04-18 | 2019-08-09 | 卓尔购电子商务(武汉)有限公司 | Method, system, storage medium and the device of a kind of rapid deployment alliance chain |
| CN110389832A (en) * | 2019-06-21 | 2019-10-29 | 深圳市汇川技术股份有限公司 | ZooKeeper container cluster dispositions method, system, equipment and storage medium |
| CN110752947A (en) * | 2019-10-18 | 2020-02-04 | 北京浪潮数据技术有限公司 | K8s cluster deployment method and device, and deployment platform |
| CN110908730A (en) * | 2019-10-31 | 2020-03-24 | 烽火通信科技股份有限公司 | Cloud platform configuration file management method and management system |
| CN111930465A (en) * | 2020-05-28 | 2020-11-13 | 武汉达梦数据库有限公司 | Kubernetes-based dreams master-slave cluster deployment method and device |
| CN112256388A (en) * | 2020-10-15 | 2021-01-22 | 深圳壹账通智能科技有限公司 | Container-based blockchain network deployment method, device, equipment and storage medium |
| CN112379946A (en) * | 2020-11-27 | 2021-02-19 | 平安普惠企业管理有限公司 | Template configuration method and device based on YAML and computer equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190324743A1 (en) * | 2018-04-24 | 2019-10-24 | Cloud66 Inc. | Configuration file management |
-
2021
- 2021-03-24 CN CN202110314672.XA patent/CN113064598B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106982266A (en) * | 2017-05-27 | 2017-07-25 | 郑州云海信息技术有限公司 | A kind of method and apparatus of automatically dispose cluster |
| CN107967159A (en) * | 2017-11-22 | 2018-04-27 | 腾讯科技（深圳）有限公司 | The method and server of a kind of profileapplied |
| CN109104318A (en) * | 2018-08-23 | 2018-12-28 | 广东轩辕网络科技股份有限公司 | The dispositions method and system of method for realizing cluster self-adaption deployment, the self-adaption deployment big data cluster based on cloud platform |
| CN109885316A (en) * | 2019-02-18 | 2019-06-14 | 国家计算机网络与信息安全管理中心 | Hdfs-hbase dispositions method and device based on kubernetes |
| CN110113185A (en) * | 2019-04-18 | 2019-08-09 | 卓尔购电子商务(武汉)有限公司 | Method, system, storage medium and the device of a kind of rapid deployment alliance chain |
| CN110389832A (en) * | 2019-06-21 | 2019-10-29 | 深圳市汇川技术股份有限公司 | ZooKeeper container cluster dispositions method, system, equipment and storage medium |
| CN110752947A (en) * | 2019-10-18 | 2020-02-04 | 北京浪潮数据技术有限公司 | K8s cluster deployment method and device, and deployment platform |
| CN110908730A (en) * | 2019-10-31 | 2020-03-24 | 烽火通信科技股份有限公司 | Cloud platform configuration file management method and management system |
| CN111930465A (en) * | 2020-05-28 | 2020-11-13 | 武汉达梦数据库有限公司 | Kubernetes-based dreams master-slave cluster deployment method and device |
| CN112256388A (en) * | 2020-10-15 | 2021-01-22 | 深圳壹账通智能科技有限公司 | Container-based blockchain network deployment method, device, equipment and storage medium |
| CN112379946A (en) * | 2020-11-27 | 2021-02-19 | 平安普惠企业管理有限公司 | Template configuration method and device based on YAML and computer equipment |
Non-Patent Citations (1)
| Title |
|---|
| 一种基于应用历史记录的Kubernetes调度算法;何龙;《数据通信》(第03期);第33-36页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113064598A (en) | 2021-07-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20080222617A1 (en) | Server side application integration framework | |
| US8789009B2 (en) | EMF model synchronization method and system | |
| US20080201703A1 (en) | Packaging content updates | |
| JP2006244451A (en) | Resource management system, resource management program, and resource management method | |
| CN111526052B (en) | Network element instruction management method, device, network equipment and storage medium | |
| US10495336B2 (en) | Energy operations across domains | |
| WO2010020124A1 (en) | Method, server and system for software installing | |
| CN109614088B (en) | Form component generation method and device | |
| US20070106770A1 (en) | Managing a remote device by a communication element that does not specify an identifier for the management object | |
| CN113064598B (en) | Container cluster management system deployment method and deployment system | |
| KR20070046587A (en) | Method and system for controlling a device using xml document | |
| US20060136602A1 (en) | Electronic data interchange apparatus | |
| CN106371931B (en) | A kind of high-performance geoscience computing service system based on Web frame | |
| CN114285691A (en) | Vehicle function implementation method and device and electronic equipment | |
| CN101001212B (en) | Multisystem message interaction managing and control system and method | |
| US9513878B2 (en) | Component integration by distribution of schema definition on heterogenous platforms | |
| CN106844819B (en) | Intelligent station secondary graph model library design tool database acquisition system | |
| CN111596872A (en) | Data printing method and data printing device | |
| CN110839079B (en) | BI node execution method, device, equipment and medium in workflow system | |
| CN109150694A (en) | Sending method, display methods and the server and mobile terminal of dynamic scene information | |
| CN105608097A (en) | Method and device for adaptively adjusting database structure | |
| CN101246421A (en) | Universal frame work based on workflow engine | |
| CN116414436A (en) | Compatible unified development platform development method, device, medium and equipment | |
| US20060026112A1 (en) | Method and apparatus for autonomous classification | |
| CN111367546A (en) | Method for realizing upgrading processing of xml configuration file in software upgrading process |
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 |