CN117827233B - Rancher platform-based simplified installation and deployment method - Google Patents
Rancher platform-based simplified installation and deployment method Download PDFInfo
- Publication number
- CN117827233B CN117827233B CN202410244930.5A CN202410244930A CN117827233B CN 117827233 B CN117827233 B CN 117827233B CN 202410244930 A CN202410244930 A CN 202410244930A CN 117827233 B CN117827233 B CN 117827233B
- Authority
- CN
- China
- Prior art keywords
- file
- package
- yaml
- char
- directory
- 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
- 238000009434 installation Methods 0.000 title claims abstract description 51
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000004806 packaging method and process Methods 0.000 claims abstract description 6
- 241000380131 Ammophila arenaria Species 0.000 claims description 14
- 230000009286 beneficial effect Effects 0.000 abstract 1
- 238000012360 testing method Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 239000003153 chemical reaction reagent Substances 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 229940005022 metadate Drugs 0.000 description 1
- JUMYIBMBTDDLNG-UHFFFAOYSA-N methylphenidate hydrochloride Chemical compound [Cl-].C=1C=CC=CC=1C(C(=O)OC)C1CCCC[NH2+]1 JUMYIBMBTDDLNG-UHFFFAOYSA-N 0.000 description 1
- 238000012856 packing 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
- 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/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a rancher platform-based simplified installation and deployment method which is used for deploying products obtained by combining a plurality of spaces; the method comprises the following steps: kubernetes and rancher were installed; creating a char package; editing all yaml files in the chart package; creating a first yaml file in a templates directory file of the char package; all the function yaml files in the product are automatically loaded into the templates directory files in the corresponding space in the char directory files; adding a second yaml file to the templates directory file of any file under the char directory file; packaging the char package; pushing the installation package; uploading an installation package; and downloading the installation package. The beneficial effects achieved by the invention are as follows: the problem of product simple deployment at rancher platforms that many spaces are constituteed is solved.
Description
Technical Field
The invention relates to the technical field of installation and deployment, in particular to a rancher platform-based simplified installation and deployment method.
Background
Rancher is an open source container management platform, a big feature of Rancher is its support for HELM CHARTS, these charts being referred to as RANCHER CHARTS. RANCHER CHARTS is a pre-configured HELM CHART package that allows easy deployment and management of applications in Kubernetes clusters. Using RANCHER CHARTS, the user can avoid the complexity of manually configuring various applications and services, thereby significantly improving deployment speed and efficiency. Traditionally, with respect to the development steps of Kubernetes and Rancher, a developer first creates and edits the configuration of the chart; packaging and issuing to a helm warehouse; when an administrator uses helm to command installation, the relevant dependencies are downloaded from the warehouse; then helm deploys resources to Kubernetes according to the downloaded configuration; this is a general installation deployment procedure.
Rancher application merchandise when deployed at the rancher application store requires that a space name be filled in, which is only a space, and a traditional charts package can only handle a single namespace. However, for products combining different services in multiple spaces, yaml files under each space folder of the products are independent in space, and when the products are directly installed in the conventional helmchart installation deployment, the corresponding spaces cannot be found out by mistake. In addition, the conventional charts package cannot process the basic sql file, and after all the functions yaml are completed, the sql database needs to be operated independently, so that the whole process is complicated and complicated.
Based on the method, the invention provides a rancher platform-based simplified installation and deployment method, which solves the problem of multi-space integration and the problem that sql files cannot be processed.
Disclosure of Invention
The invention aims to overcome the defects of the prior art, provides a rancher platform-based simplified installation and deployment method which is easy to operate, solves the problem that products formed by multiple spaces are simply deployed on a rancher platform, and solves the problem that basic sql cannot be processed.
The aim of the invention is achieved by the following technical scheme: the method is based on rancher platform simplified installation and deployment, and is used for deploying products combined by a plurality of spaces, each space provides different functions, and the space is a name space; it is characterized in that the method comprises the steps of,
The method for simplifying installation and deployment based on rancher platforms comprises the following steps:
step S1: an installation environment, an installation Kubernetes environment and rancher application stores;
step S2: creating a package, creating a char package using helm of Kubernetes;
Step S3: editing the content of all yaml files in the chart package;
step S4: creating a plurality of first directory files in the char package, and adding the function yaml files in each space in the product into the templates directory files in the corresponding files in the char directory files;
Step S5: creating a second directory file under the char directory file in the char package, adding a second yaml file in the template directory file of the second directory file, and configuring an image file in the second yaml file for running the sql database;
Step S6: creating a first yaml file in a templates directory file of the char package, creating a plurality of namespaces in the Kubernetes cluster through the first yaml file, wherein each namespace corresponds to a plurality of first directory files in the char directory file;
step S7: packaging the char package;
Step S8: pushing a hart package to upload an installation package through helm-push commands, wherein the hart package is the installation package;
step S9: downloading the installation package at rancher at a restore address of the application store configuration hart package;
Step S10: filling out form information by applying store pages at rancher, and installing and starting;
The simplified installation and deployment method further comprises the following steps: during installation, a plurality of namespaces are created in the Kubernetes cluster by moving the first yaml file, and the function yaml file under the templates directory under the char directory file is automatically loaded into the corresponding space in the Kubernetes cluster, so that correct installation and deployment of the function yaml file are completed.
Further, the step S3 includes: editing contents in values.yaml and Chart.yaml, adding and editing contents in READE.md and questins.yml;
The value.yaml file is used for defining default configuration options of the chart package, the default configuration options are modified and created according to helm template grammar, and the creating and modifying contents comprise: mirror image, domain name, database address, database user name, database password, redis address, redis password, es account number and Es password;
the Chart.yaml file is used for describing a Chart package;
the READM.md file is used for describing product information;
The query.yml file is used for configuring rancherUI interfaces, and the configured form filling information is configured according to default in the value.yaml file.
Further, after executing step S4, and before executing step S5, modifying the variable according to the char syntax for the file yaml in the templates directory file in each space in the char directory file, where the modifying content includes: database information, es information, redis information, domain name information, and mirror version.
Further, the executing command of the image file includes: the mysql client downloads and installs wget command operations;
Further, the image file also includes a shell script that executes a series of commands, the shell script including gitlab pull-up sql file commands, process and load each sql file command individually, and execute the sql file commands.
The invention has the following advantages:
(1) The invention can be manufactured across spaces, namely, the resources in all spaces in the Kubernetes cluster are packed into a whole and integrated into rancher application stores for deployment; the problem that the traditional charts package can only process a single naming space and cannot correctly configure a plurality of space products is solved; creating a first yaml file in the templates directory file of the hart package, creating a plurality of spaces in the reagents directory file in the hart package through the first yaml file, and creating space names and spaces of a plurality of corresponding product spaces in the reagents package after executing the first yaml file so as to process the plurality of namespaces and realize cross-space operation.
(2) The traditional helmchart is installed and can only operate yaml resources in the Kubernetes cluster, and a database cannot be operated, so that the method is extremely unfriendly for manufacturing a product installation package of an internet product, and after yaml files are loaded, the database needs to be independently operated, and the whole process is tedious and complex. According to the invention, yaml resources are integrated, all sql data are integrated, the two are integrated, after the page is filled, all yaml files are deployed, and all sql operation commands are executed.
Drawings
FIG. 1 is a process step diagram of the present invention;
FIG. 2 is a schematic diagram of a plurality of files under a chart package;
FIG. 3 is a schematic diagram of a plurality of first directory files of a char package;
FIG. 4 is a schematic diagram of a char/crms file;
FIG. 5 is a schematic diagram of a char/crms/templates file;
FIG. 6 is a second yaml file path diagram;
FIG. 7 is a first yaml file path diagram;
fig. 8 is a first yaml file portion content example.
Detailed Description
The present invention will be further described with reference to the accompanying drawings, but the scope of the present invention is not limited to the following.
It should be noted that, the azimuth or positional relationship indicated by "left", "right", etc. is based on the azimuth or positional relationship shown in the drawings, or the azimuth or positional relationship conventionally put in use of the inventive product, or the azimuth or positional relationship conventionally understood by those skilled in the art, such terms are merely for convenience of describing the present invention and simplifying the description, and do not indicate or imply that the apparatus or element referred to must have a specific azimuth, be configured and operated in a specific azimuth, and therefore should not be construed as limiting the present invention.
It should be noted that, under the condition of no conflict, the embodiments of the present invention and the features and technical solutions in the embodiments may be combined with each other.
As shown in fig. 1, the method for installing and deploying the product based on the rancher platform is provided in this embodiment, and is used for deploying the product combined by a plurality of spaces, wherein each space provides different functions;
The simplified installation and deployment method flow based on rancher platforms comprises the following steps:
step S1: an installation environment, an installation Kubernetes environment and rancher application stores;
step S2: creating a package, creating a char package using helm of Kubernetes;
Step S3: editing the content of all yaml files in the chart package;
specifically, step S3 includes: editing contents in values.yaml and Chart.yaml, adding and editing contents in READE.md and questins.yml;
values. Yaml file: default configuration options for defining the chart package, modification creation of the default configuration options according to helm template syntax, creation and modification of content including but not limited to: mirror image, domain name, database address, database user name, database password, redis address, redis password, es account number and Es password;
Chart. Yaml file: for describing a chart package;
READM. Md File: for describing product information;
the query.yml file is used for configuring rancherUI interfaces, and the configured form filling information is configured according to default in the value.yaml file.
Only four files which are respectively values.yaml, chart.yaml, charts catalog files and templates catalog files are created in the default of the Chart package, so READM.md and query.yml files are needed to be added under the catalog of the Chart package, and the two files are necessary files for forming a rancher application store deployment UI interface form.
Step S4: creating a plurality of first directory files in the char package, and adding the function yaml files in each space in the product into the template directory files in the corresponding first directory files in the char directory files;
After step S4 is performed and before step S5 is performed, the function yaml file is not directly available and the yaml file in the templates directory file in each space needs to be modified according to the char syntax to modify the variables including but not limited to: database information, es information, redis information, domain name information, and mirror version.
Step S5: creating a second directory file under the char directory file in the char package, adding a second yaml file in the template directory file of the second directory file, and configuring an image file in the second yaml file for running the sql database;
The second yaml file is configured with an image file, and the image file execution command includes: the mysql client downloads and installs wget command operations; the image file includes a shell script that executes a series of commands, the shell script including gitlab pull-up sql file commands, process and load each sql file command individually, and execute the sql file commands.
For the conventional helmchart package, which can only operate yaml resources in the Kubernetes cluster and cannot operate the database, a second. yaml is added in the templates directory file in any file under the char directory file in the char package, in some embodiments,
Specifically, as shown in fig. 6, the second directory file created in step S5 is xzsql files, a second yaml file is added in the templates directory file of xzsql files, the second yaml file is named as an sqljob.yaml file, an image file is configured in the sqljob.yaml file, and the image file performs mysql client downloading and installing and wget command operations;
The mirror file further includes a shell script executing a series of commands, the shell script including gitlab pull-up sql file commands, processing and loading each sql file command separately, and executing the sql file command. The shell script is used for pulling the sql file up GitLab, and then executing the sql load command after each piece of processing.
The execute sql file command mainly includes the mysql data address, mysql database password, and mysql database account number, which is the configuration of the relevant mysql database at rancher interface configuration.
Step S6: creating a first yaml file in a templates directory file of the char package, creating a plurality of namespaces in the Kubernetes cluster through the first yaml file, wherein each namespace corresponds to a plurality of first directory files in the char directory file;
For a product with different service combinations of a plurality of spaces, the functions yaml files under each space folder under the product are independent in space, and if the product is directly installed, the installation failure is caused by error reporting because the corresponding space cannot be found in the Kubernetes cluster; the traditional chart package can only process a single name space, can not integrate all name spaces in the Kubernetes cluster, and only one name space can be created by the chart package installation, so that the problem of creating a plurality of spaces is solved; creating a first yaml file in a templates directory file of the char package, and creating a plurality of namespaces in the Kubernetes cluster through the first yaml file, wherein the namespaces correspond to the creation of the plurality of first directory files in the char package;
When the installation package is installed, a plurality of namespaces are created in the Kubernetes cluster by running the first yaml file, and the function yaml file under the templates directory under the char directory file is automatically loaded into the corresponding namespaces in the Kubernetes cluster, so that the correct installation and deployment of the function yaml file are completed. The namespaces in the Kubernetes cluster are integrated through the first yaml file, so that cross-space operation is realized.
Taking crms files under the char directory file as an example;
By creating a first yaml file in the templates directory file under the first directory of the char package, the first yaml file name is custom, the in-file program commands include creating multiple namespaces, for example, as shown in FIG. 8, in the Kubernetes Cluster creation crms space:
apiVersion:v1
kind:Namespace
metadate:
name:crms
The created crms space in the Kubernetes cluster, the program automatically loads the function yaml file in the product, which corresponds to the crms space, in the Kubernetes cluster, and the function yaml file in the product, which corresponds to the crms space, is located in the templates directory file in the crms file under the char directory file, thereby completing the correct configuration of the corresponding space and file.
Step S7: packaging the char package;
Specifically, after the char package is manufactured, packaging is instructed through HELM PACKAGE.
Step S8: pushing a part package through helm-push commands, wherein the part package is an installation package;
Step S9: configuring a repositive address of the char package (downloading the install package) at rancher by the application store;
Step S10: store page filling form information is applied at rancher and install launch.
Specifically, as shown in fig. 2-8, after waiting for the completion of the installation of Kubernetes and Rancher, setting up an environment; creating a test (chat package) named home; the concrete values.yaml, chart.yaml, charts directory file and templates directory file are below test; adding and editing READM.md and questins.yml files at test, and simultaneously editing value.yaml and Chart.yaml files;
As shown in FIG. 3, a plurality of first directory files are created under the char directory files, including yumi-xy files, xzsql files, web files, matir-core files, kong files, front files, crms files, cmc files, cim files, and ai3 files;
As shown in fig. 7, creating a create_Namespace_secret_yaml file in the templates directory file under test, wherein the create_Namespace_secret_yaml file is used for creating a plurality of namespaces, and the create_Namespace_secret_yaml file is run to automatically create a plurality of namespaces in the Kubernetes cluster;
As shown in fig. 2-5, after the creation of the namespaces is completed, for example, the test/characters/crms/templates have the ingress. Yaml file and the development. Yaml file, which are automatically loaded into crms space in the Kubernetes cluster.
For the operation of the sql database, as shown in fig. 6, a second directory file is created at the char under test, the second directory file is named xzsql, an sqljob.yaml file is added under test/char/xzsql/templates, an image file is configured in sqljob.yaml, a mysql client is installed in the image file, a shell script of a series of commands is executed in the container, the shell script functions to pull the sql file from gitlab, and then the sql loading command is executed after each processing.
After the configuration of the step file is completed, packing a test into an installation package through HELM PACKAGE commands, pushing the installation package through helm-push commands, and configuring a repositive address of the char package at rancher by an application store (downloading the installation package);
And finally, filling out the form information by using the store page at rancher, and installing and starting.
Meanwhile, the simplified installation and deployment provided by the invention realizes standardized application configuration. RANCHER CHARTS provides a standardized way to configure and deploy applications so that it becomes more efficient to manage and maintain Kubernetes applications. By using the values. Yaml of the chart package, a user can easily customize the application configuration without manually editing a complex number of Kubernetes resource files.
In summary, the present invention compares to conventional application deployment: 1. the invention realizes cross-space production, namely, the resources in all spaces in the Kubernetes cluster are packed into a whole and integrated into rancher application stores for deployment. The simplified deployment under the product consisting of the multi-space service is solved; 2. the traditional HELM CHART is installed and can only operate yaml resources in the Kubernetes cluster, and a database cannot be operated, so that the method is extremely unfriendly for manufacturing a product installation package of an internet product, and after yaml is loaded, the database needs to be independently operated, and the whole process is complicated. According to the invention, by newly adding the second yaml file, yaml resources are integrated, all sql data are integrated, the yaml resources and the sql data are integrated, after the page is filled, all yaml files are deployed, and all sql data are executed.
The foregoing examples represent only preferred embodiments, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that variations and modifications can be made by those skilled in the art without departing from the spirit of the invention, which falls within the scope of the invention.
Claims (5)
1. The method is based on rancher platform and is used for deploying products obtained by combining a plurality of spaces, each space provides different functions, and the space is a naming space; it is characterized in that the method comprises the steps of,
The rancher platform-based simplified installation and deployment method comprises the following steps:
step S1: an installation environment, an installation Kubernetes environment and rancher application stores;
step S2: creating a package, creating a char package using helm of Kubernetes;
Step S3: editing the content of all yaml files in the chart package;
Step S4: creating a plurality of first directory files in the char package, and adding the function yaml files in each space in the product into the template directory files in the corresponding first directory files in the char directory files;
Step S5: creating a second directory file under the char directory file in the char package, adding a second yaml file in the template directory file of the second directory file, and configuring an image file in the second yaml file for running the sql database;
Step S6: creating a first yaml file in a templates directory file of the char package, creating a plurality of namespaces in the Kubernetes cluster through the first yaml file, wherein each namespace corresponds to a plurality of first directory files in the char directory file;
step S7: packaging the char package;
Step S8: pushing a hart package to upload an installation package through helm-push commands, wherein the hart package is the installation package;
step S9: downloading the installation package at rancher at a restore address of the application store configuration hart package;
Step S10: filling out form information by applying store pages at rancher, and installing and starting;
The simplified installation and deployment method further comprises the following steps: during installation, a plurality of namespaces are created in the Kubernetes cluster by running the first yaml files, and function yaml files under the templates directory under the char directory files are automatically loaded into the corresponding spaces in the Kubernetes cluster, so that correct installation and deployment of the function yaml files are completed.
2. The rancher platform-based facilitation installation deployment method as defined in claim 1 wherein: the step S3 comprises the following steps: editing contents in values.yaml and Chart.yaml, adding and editing contents in READE.md and questins.yml;
The value.yaml file is used for defining default configuration options of the chart package, the default configuration options are modified and created according to helm template grammar, and the creating and modifying contents comprise: mirror image, domain name, database address, database user name, database password, redis address, redis password, es account number and Es password;
The Chart.yaml file is used for describing a Chart package;
the READM.md file is used for describing product information;
The query.yml file is used for configuring rancherUI interfaces, and the configured form filling information is configured according to default in the value.yaml file.
3. The rancher platform-based facilitation installation deployment method as defined in claim 1 wherein: after step S4 is performed, and before step S5 is performed, the variable is modified for the yaml file in the templates directory file in each space in the char directory file according to the char syntax, where the modifying content includes: database information, es information, redis information, domain name information, and mirror version.
4. The rancher platform-based facilitation installation deployment method as defined in claim 1 wherein: the executing command of the image file comprises: the mysql client downloads and installs wget command operations.
5. The rancher platform-based facilitation installation deployment method as defined in claim 4 wherein: the image file also includes a shell script that executes a series of commands, the shell script including gitlab pull-up sql file commands, process and load each sql file command individually, and execute the sql file commands.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410244930.5A CN117827233B (en) | 2024-03-05 | 2024-03-05 | Rancher platform-based simplified installation and deployment method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410244930.5A CN117827233B (en) | 2024-03-05 | 2024-03-05 | Rancher platform-based simplified installation and deployment method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117827233A CN117827233A (en) | 2024-04-05 |
| CN117827233B true CN117827233B (en) | 2024-04-30 |
Family
ID=90523216
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410244930.5A Active CN117827233B (en) | 2024-03-05 | 2024-03-05 | Rancher platform-based simplified installation and deployment method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117827233B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111984271A (en) * | 2020-08-27 | 2020-11-24 | 北京海益同展信息科技有限公司 | Block chain application program processing method and device and block chain application system |
| CN112187860A (en) * | 2020-08-28 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Construction method and device of kubernets cluster node mirror image |
| CN112506477A (en) * | 2020-11-09 | 2021-03-16 | 麒麟软件有限公司 | Method for adding computing nodes by using RESTful API in Kubernetes cluster |
| CN113312074A (en) * | 2021-06-16 | 2021-08-27 | 上海驻云信息科技有限公司 | Kubernetes-based software deployment method |
| CN114610443A (en) * | 2022-02-25 | 2022-06-10 | 华控清交信息科技(北京)有限公司 | Multi-service deployment method and device based on k8s container cluster and electronic equipment |
| CN114721809A (en) * | 2020-12-21 | 2022-07-08 | 航天信息股份有限公司 | Application deployment method and device of kubernets cluster |
| CN115729610A (en) * | 2022-12-07 | 2023-03-03 | 杭州谐云科技有限公司 | Operation and maintenance management method and system for components in cloud native environment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11954473B2 (en) * | 2021-09-20 | 2024-04-09 | Microstrategy Incorporated | Deployment architecture for multi-tenant cloud computing systems |
-
2024
- 2024-03-05 CN CN202410244930.5A patent/CN117827233B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111984271A (en) * | 2020-08-27 | 2020-11-24 | 北京海益同展信息科技有限公司 | Block chain application program processing method and device and block chain application system |
| CN112187860A (en) * | 2020-08-28 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Construction method and device of kubernets cluster node mirror image |
| CN112506477A (en) * | 2020-11-09 | 2021-03-16 | 麒麟软件有限公司 | Method for adding computing nodes by using RESTful API in Kubernetes cluster |
| CN114721809A (en) * | 2020-12-21 | 2022-07-08 | 航天信息股份有限公司 | Application deployment method and device of kubernets cluster |
| CN113312074A (en) * | 2021-06-16 | 2021-08-27 | 上海驻云信息科技有限公司 | Kubernetes-based software deployment method |
| CN114610443A (en) * | 2022-02-25 | 2022-06-10 | 华控清交信息科技(北京)有限公司 | Multi-service deployment method and device based on k8s container cluster and electronic equipment |
| CN115729610A (en) * | 2022-12-07 | 2023-03-03 | 杭州谐云科技有限公司 | Operation and maintenance management method and system for components in cloud native environment |
Non-Patent Citations (3)
| Title |
|---|
| Containerization: Cloud Computing based Inspiration Technology for Adoption through Docker and Kubernetes;Sanjay Hardikar等;《2021 Second International Conference on Electronics and Sustainable Communication Systems (ICESC)》;20210923;1996-2003 * |
| 基于Docker容器的云平台功能设计与实现;隋伟;《中国优秀硕士学位论文全文数据库 信息科技辑》;20210615;I139-71 * |
| 面向多个容器云环境的服务构建与发布系统设计与实现;丁彭飞;《中国优秀硕士学位论文全文数据库 信息科技辑》;20220615;I139-80 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117827233A (en) | 2024-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101831430B1 (en) | Apparatus and method for infrastructure automation | |
| US7530079B2 (en) | Managing application customization | |
| US7496890B2 (en) | Generation of configuration instructions using an abstraction technique | |
| US7412687B2 (en) | Creating customized applications using templates having points of variability | |
| US7330967B1 (en) | System and method for injecting drivers and setup information into pre-created images for image-based provisioning | |
| CN111399865A (en) | Method for automatically constructing target file based on container technology | |
| US8762986B2 (en) | Advanced packaging and deployment of virtual appliances | |
| WO2017071494A1 (en) | Application deployment method and apparatus | |
| US7861243B2 (en) | Automatically deploying program units to a cluster of networked servers | |
| US6098067A (en) | Remote computer management system | |
| US20060271844A1 (en) | Thin client method and system for generating page delivery language output from applets, views, and screen definitions | |
| CN108897547B (en) | Software automation deployment method and device | |
| US20040088397A1 (en) | System and method for management of software applications | |
| CN115658232A (en) | Cloud native platform rapid deployment method and system | |
| CN115437653A (en) | Method for privatized deployment by using container technology | |
| CN117827233B (en) | Rancher platform-based simplified installation and deployment method | |
| JP2001325098A (en) | Method for preparing application program method for operating database, method for managing item object, method for controlling module operation and computer- readable recording medium recorded with program for realizing operation, management and control methods | |
| CN110908767B (en) | Automatic parameter deployment method and device | |
| CN115454572A (en) | Method and system for constructing disk image of virtual machine based on Docker tool | |
| CN114791826A (en) | Jenkins project operation method and device based on parameter configuration | |
| CN112685051A (en) | Method, device, platform and storage medium for automatically executing shell script | |
| CN113064698A (en) | Method for providing product environment and corresponding device, system, equipment and medium | |
| CN112463289A (en) | Method, system, equipment and medium for realizing application service based on virtual machine | |
| CN116360779B (en) | Method for constructing micro front end base based on qiankun in Vue CLI application | |
| US11900091B2 (en) | Extensible upgrade and modification as a service |
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 |