CN111813420A - Method for carrying out automated performance test on OpenStack cluster - Google Patents
Method for carrying out automated performance test on OpenStack cluster Download PDFInfo
- Publication number
- CN111813420A CN111813420A CN202010660326.2A CN202010660326A CN111813420A CN 111813420 A CN111813420 A CN 111813420A CN 202010660326 A CN202010660326 A CN 202010660326A CN 111813420 A CN111813420 A CN 111813420A
- Authority
- CN
- China
- Prior art keywords
- job
- performance test
- executing
- running
- openstack
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000011056 performance test Methods 0.000 title claims abstract description 78
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000012360 testing method Methods 0.000 claims abstract description 68
- 230000008569 process Effects 0.000 claims abstract description 12
- 238000004519 manufacturing process Methods 0.000 claims abstract description 6
- 238000013515 script Methods 0.000 claims description 31
- 241000380131 Ammophila arenaria Species 0.000 claims description 14
- 230000003068 static effect Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3058—Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention discloses a method for carrying out automatic performance test on an OpenStack cluster, which relates to the technical field of Kubernets and aims at solving the problem that manual performance test is complicated after the OpenStack cluster is deployed in a Kubernets environment, and the technical scheme sequentially comprises three parts of presetting test precondition, configuring cluster environment information and executing performance test; manufacturing an LOCI mirror image of a rally component on a preset test precondition part; compiling values.yaml files according to deployment environment requirements in a cluster environment information configuration part, and configuring environment variables required by testing; in the performance test execution part, the OpenStack cluster performance test is automatically completed through three processes of running the initialization job, running the performance test job and running the export test report job. The method can automatically complete a series of work of OpenStack cluster performance test by creating preset resources required by the cluster performance test, configuring special variables of the environment and executing the performance test, and can improve the test efficiency.
Description
Technical Field
The invention relates to the technical field of Kubernets, in particular to a method for carrying out automatic performance testing on an OpenStack cluster.
Background
With the rise of containerization technology and the continuous optimization of a container arrangement engine, meanwhile, the containerization mode has the advantages of high deployment and recovery speed, convenience in operation and maintenance, high availability of service, elastic expansion, rapid capacity expansion, visualization of a container warehouse, rolling upgrade and the like, so that more and more manufacturers and users use the containerization mode to deploy OpenStack related components.
In a containerized OpenStack cluster deployed in a Kubernets environment, the OpenStack cluster is deployed and deployed by using Helm, Helm is a package manager for the Kubernets, and functions of software deployment, deletion, upgrading, rollback and packaging, application dependency management, application version management, application warehouse release and application and the like on the Kubernets can be realized through Helm. Helm makes the release configurable, thereby simplifying the application deployment and maintenance in the Kubernetes cluster.
After the OpenStack cluster deployment is completed, a Rally component is generally used to perform performance testing on the OpenStack cluster. Rally is an OpenStack community derived open source test tool and can be used for performing performance test on each component of OpenStack. By using the Rally components, a user can complete a series of actions such as function verification, large-scale load test (performance test), test report output and the like of each component of the OpenStack cloud computing platform.
The OpenStack-Helm project comprises basic functions of a Rally test and is used for performing performance test on an OpenStack cluster deployed in a Kubernets environment, the OpenStack-Helm is a sub-project of the OpenStack, a group of Helm charts which are used for deploying OpenStack related services on the Kubernets cluster simply and flexibly is provided, however, the function of the Rally project in the OpenStack-Helm is still incomplete, performance test cannot be automatically executed and a test report can be generated after the OpenStack cluster is deployed, test environments need to be preset manually, jobs such as job execution, resource clearing and the like need to be executed, and a large amount of initialization information needs to be configured.
Disclosure of Invention
After an OpenStack cluster deployed in a production environment is completed, performance of each component of the cluster generally needs to be tested. A commonly used performance test is the Openstack Rally component. In a containerized OpenStack cluster deployed in a kubernets environment, components of the OpenStack are deployed and managed in a palm mode, after the OpenStack cluster is deployed and completed through the palm, a user generally needs to manually create preset resources required by tests such as networks and images in the environment, then configure related configuration files, manually start all jobs, complete the creation of a default execution task by a trace command, and finally manually execute a job for exporting a test report. The process is complicated, needs to be manually executed, needs to accumulate certain OpenStack test prior knowledge for operation and maintenance personnel, and increases the deployment and delivery cost. Based on the method, aiming at OpenStack deployed in Kubernets, the invention provides a method for carrying out automatic performance testing on an OpenStack cluster.
The invention discloses a method for carrying out automatic performance test on an OpenStack cluster, which adopts the following technical scheme for solving the technical problems:
a method for carrying out automatic performance test on OpenStack cluster sequentially comprises the steps of presetting test precondition, configuring cluster environment information and executing performance test,
manufacturing a LOCI mirror image of a rally assembly in a preset test precondition part,
in the cluster environment information configuration part, values.yaml files are compiled according to the requirements of a deployment environment, environment variables required by testing are configured,
in the performance test execution part, the OpenStack cluster performance test is automatically completed through three processes of running the initialization job, running the performance test job and running the export test report job.
Further, at the preset test precondition part, manufacturing a LOCI mirror image of the rally component, and the specific operation steps include:
custom installing OpenStack client in the image for executing OpenStack client commands in the initialization script,
and simultaneously, introducing a raw format cirros image file into the image to create a virtual machine image used for testing.
Furthermore, in the information part of the cluster environment configuration, values.yaml files are compiled according to the requirements of the deployment environment, and environment variables required by the test are configured,
the test cases needing to be tested in the task corresponding to each component can be manually added to values.
Further, in the performance test executing section, the operation of running the initialization job specifically includes:
(1.1) running a job of preset Mysql database information, wherein the job generates a job helm template file of the preset Mysql database information by referring to openstack-helm-infra-helm-tool-manifests-jobb-init-Mysql; the jobs mainly comprises a contacts which starts a script for presetting Mysql database information by executing/tmp/db-init.py command in a container;
(1.2) running a job for initializing Keystone end point information, wherein the job mainly comprises a container, and starting a script for initializing the Keystone end point information by executing a/tmp/ks-end points.
(1.3) running a job for initializing Keystone service information, wherein the job mainly comprises a contacts, and starting a script for initializing the Keystone service information by executing a/tmp/ks-service.sh command in a container;
(1.4) running a joba for initializing Keystone user information, wherein the joba generates a job helm template file for initializing Keystone user information by referring to openstack-helm-infra, helm-toolkit, manestists, jobksuser, the jobb mainly comprises a container, and a script for initializing Keystone user information is started by executing/tmp/ks-user py command in the container
(1.5) running a job for initializing Mysql database data, wherein the job depends on the above 1), 2) and 4) three jobs, wherein the job comprises contacts, and the script mounted to the container is run by executing/tmp/management-db.sh commands in the container: sh, tpl, initializing Mysql database data, executing a rally db create or rally dbupplide command to initialize rally related database data.
Further, in the execution performance test section, a job for initializing Mysql database data is executed depending on (1.5), the performance test job is executed, the job contains a contacts, and the script mounted to the container is executed by executing/tmp/run-task.sh command in the container: sh, tpl, and carrying out performance test, and exporting a performance test report to a target position.
Furthermore, in the performance test executing section, the performance test job is executed, and the operation specifically includes:
2.1) creating a deployment, importing environment resource information and configuring the deployment;
2.2) configuring task file: executing an OpenStack client command to obtain an initialization resource id, and updating the initialization resource id to a container/tasks/rally/< task >. yaml file by using a sed command;
2.3) execute the performance test task configured in values.yaml and generate a test report.
Furthermore, in the process of running the performance test job, the performance test job is implemented by a script _ run-task.sh.tpl mounted in a container, and the script comprises the following four stages:
(2-1) executing the function create _ default: creating openstack-helm deployment by a random deployment create command;
(2-2) traversing enabled _ tasks list defined in values.yaml, executing function run _ rally:
a. configuring and checking the deployment through the deployment user and the deployment check;
b. execute function replace _ task _ args: backing up an original task xml file, executing an OpenStack command through an OpenStackclient to obtain preset resource information required in the task, and updating the preset resource information to the task xml file under a corresponding/tasks/rally/directory by using a sed command;
(2-3) verifying and executing the performance test task through a random task valid command and a random task start command;
and (2-4) exporting the performance test report to the target position through the random task report-out.
Further, in the execution performance test section, a job of an export test report is executed depending on execution of a performance test job containing a contiiners, and the exported performance test report is copied to a script of a target node by executing a cp command in a container.
Furthermore, in the section for performing performance testing, the export test report jobis executed, which specifically includes:
prepare dependencies in values.yaml: the static of the utility model,
meanwhile, the anotations of 'helm.sh/hook' of post-install is configured in the jobtemplate of the derived test report,
and after the post-upgrade finishes running the performance test jobe, automatically running the export test report jobe.
Compared with the prior art, the method for automatically testing the performance of the OpenStack cluster has the beneficial effects that:
the invention automatically tests the performance of the OpenStack cluster deployed in Kubernetes, and in the test process, a user only needs to configure the environment specific variable before testing, so that the preset resource required by the cluster performance test can be established, the environment specific variable can be configured and the performance test can be executed after the containerized OpenStack cluster is deployed, a series of work of the OpenStack cluster performance test can be automatically completed, the deployment test process is simplified, and the test efficiency is improved.
Drawings
FIG. 1 is a performance testing basic framework of the present invention;
FIG. 2 is a flow chart of the present invention for performing a performance test;
FIG. 3 is a flow chart of the operational performance test jobof the present invention.
Detailed Description
In order to make the technical scheme, the technical problems to be solved and the technical effects of the present invention more clearly apparent, the following technical scheme of the present invention is clearly and completely described with reference to the specific embodiments.
The first embodiment is as follows:
with reference to fig. 1, this embodiment provides a method for performing an automated performance test on an OpenStack cluster, where the method sequentially includes three parts, namely, presetting a test precondition, configuring cluster environment information, and performing a performance test.
Firstly, manufacturing a LOCI mirror image of a rally component in a preset test precondition part, wherein the process comprises the following steps:
custom installing OpenStack client in the image for executing OpenStack client commands in the initialization script,
and simultaneously, introducing a raw format cirros image file into the image to create a virtual machine image used for testing.
Secondly, in the information part of the configuration cluster environment, values.yaml files are written according to the requirements of the deployment environment, environment variables required by the test are configured, in the process,
the test cases needing to be tested in the task corresponding to each component can be manually added to values.
And (III) in the performance test execution part, automatically completing the OpenStack cluster performance test through three processes of (1) running the initialization jobb, (2) running the performance test jobb and (3) running the export test report jobb.
(1) With reference to fig. 2, the operation of running the initialization job specifically includes:
(1.1) running a job of preset Mysql database information, wherein the job generates a job helm template file of the preset Mysql database information by referring to openstack-helm-infra-helm-tool-manifests-jobb-init-Mysql; the jobs mainly comprises a contacts which starts a script for presetting Mysql database information by executing/tmp/db-init.py command in a container;
(1.2) running a job for initializing Keystone end point information, wherein the job mainly comprises a container, and starting a script for initializing the Keystone end point information by executing a/tmp/ks-end points.
(1.3) running a job for initializing Keystone service information, wherein the job mainly comprises a contacts, and starting a script for initializing the Keystone service information by executing a/tmp/ks-service.sh command in a container;
(1.4) running a joba for initializing Keystone user information, wherein the joba generates a job helm template file for initializing Keystone user information by referring to openstack-helm-infra, helm-toolkit, manestists, jobksuser, the jobb mainly comprises a container, and a script for initializing Keystone user information is started by executing/tmp/ks-user py command in the container
(1.5) running a job for initializing Mysql database data, wherein the job depends on the above 1), 2) and 4) three jobs, wherein the job comprises contacts, and the script mounted to the container is run by executing/tmp/management-db.sh commands in the container: sh, tpl, initializing Mysql database data, executing a rally db create or rally dbupplide command to initialize rally related database data.
(2) Running a performance test jobb that relies on (1.5) running a job that initializes Mysql database data, which jobb contains a containers, running scripts that are mounted to the container by executing/tmp/run-task.sh commands in the container: sh, tpl, and carrying out performance test, and exporting a performance test report to a target position.
With reference to fig. 3, the operation of the job of the operation performance test specifically includes:
(2.1) creating a deployment, importing environment resource information and configuring the deployment;
(2.2) configuring task file: executing an OpenStack client command to obtain an initialization resource id, and updating the initialization resource id to a container/tasks/rally/< task >. yaml file by using a sed command;
(2.3) executing the performance test task configured in values.yaml and generating a test report.
In the process of the step (2), the script is realized by a script _ run-task.sh.tpl mounted in a container, and the script comprises the following four stages:
(2-1) executing the function create _ default: creating openstack-helm deployment by a random deployment create command;
(2-2) traversing enabled _ tasks list defined in values.yaml, executing function run _ rally:
a. configuring and checking the deployment through the deployment user and the deployment check;
b. execute function replace _ task _ args: backing up an original task xml file, executing an OpenStack command through an OpenStackclient to obtain preset resource information required in the task, and updating the preset resource information to the task xml file under a corresponding/tasks/rally/directory by using a sed command;
(2-3) verifying and executing the performance test task through a random task valid command and a random task start command;
and (2-4) exporting the performance test report to the target position through the random task report-out.
(3) Running an export test report jobb that depends on (2) running a performance test jobb that contains a contiiners script that copies the export performance test report to the target node by executing a cp command in the container.
The operation of running the job of the export test report specifically comprises the following steps:
prepare dependencies in values.yaml: the static of the utility model,
meanwhile, the anotations of 'helm.sh/hook' of post-install is configured in the jobtemplate of the derived test report,
and after the post-upgrade finishes running the performance test jobe, automatically running the export test report jobe.
In summary, by using the method for performing the automated performance test on the OpenStack cluster, after the deployment of the OpenStack cluster is completed in kubernets, a series of work of the OpenStack cluster performance test can be automatically completed by creating preset resources required by the cluster performance test, configuring special variables of an environment and executing the performance test, so that the test efficiency can be improved.
The principles and embodiments of the present invention have been described in detail using specific examples, which are provided only to aid in understanding the core technical content of the present invention. Based on the above embodiments of the present invention, those skilled in the art should make any improvements and modifications to the present invention without departing from the principle of the present invention, and therefore, the present invention should fall into the protection scope of the present invention.
Claims (9)
1. A method for carrying out automatic performance test on OpenStack cluster is characterized in that the method sequentially comprises three parts of presetting test precondition, configuring cluster environment information and executing performance test,
manufacturing a LOCI mirror image of a rally assembly in a preset test precondition part,
in the cluster environment information configuration part, values.yaml files are compiled according to the requirements of a deployment environment, environment variables required by testing are configured,
in the performance test execution part, the OpenStack cluster performance test is automatically completed through three processes of running the initialization job, running the performance test job and running the export test report job.
2. The method for performing automated performance testing on the OpenStack cluster according to claim 1, wherein a preset test precondition part is used to fabricate a LOCI mirror image of a rally component, and the specific operation steps include:
custom installing OpenStack client in the image for executing OpenStack client commands in the initialization script,
and simultaneously, introducing a raw format cirros image file into the image to create a virtual machine image used for testing.
3. The method of claim 1, wherein in the section of configuring cluster environment information, values.yaml files are written according to deployment environment requirements, and environment variables required for testing are configured, and in this process,
the test cases needing to be tested in the task corresponding to each component can be manually added to values.
4. The method for performing automatic performance testing on the OpenStack cluster according to claim 1, 2 or 3, wherein in the performance testing executing section, the operation of running the initialization job specifically includes:
(1.1) running a job of preset Mysql database information, wherein the job generates a job helm template file of the preset Mysql database information by referring to openstack-helm-infra-helm-tool-manifests-jobb-init-Mysql; the jobs mainly comprises a contacts which starts a script for presetting Mysql database information by executing/tmp/db-init.py command in a container;
(1.2) running a job for initializing Keystone end point information, wherein the job mainly comprises a containers, and starting a script for initializing the Keystone end point information by executing/tmp/ks-end points.sh commands in a container;
(1.3) running a job for initializing Keystone service information, wherein the job mainly comprises a contacts, and starting a script for initializing the Keystone service information by executing a/tmp/ks-service.sh command in a container;
(1.4) running a joba for initializing Keystone user information, wherein the joba generates a job helm template file for initializing Keystone user information by referring to openstack-helm-infra, helm-toolkit, manestists, jobksuser, the jobb mainly comprises a container, and a script for initializing Keystone user information is started by executing/tmp/ks-user py command in the container
(1.5) running a job for initializing Mysql database data, wherein the job depends on the above 1), 2) and 4) three jobs, wherein the job comprises contacts, and the script mounted to the container is run by executing/tmp/management-db.sh commands in the container: sh, tpl, initializing Mysql database data, executing a rally db create or rally db update command to initialize rally related database data.
5. The method of claim 4, wherein in the performance testing section, a job for initializing Mysql database data is executed in dependence on (1.5), the performance testing job is executed, the job comprises a containers, and the script mounted to the container is executed by executing/tmp/run-task. Sh, tpl, and carrying out performance test, and exporting a performance test report to a target position.
6. The method of claim 5, wherein in the section for performing the performance test, the operation of running the performance test job specifically includes:
2.1) creating a deployment, importing environment resource information and configuring the deployment;
2.2) configuring task file: executing an OpenStack client command to obtain an initialization resource id, and updating the initialization resource id to a container/tasks/rally/< task >. yaml file by using a sed command;
2.3) execute the performance test task configured in values.yaml and generate a test report.
7. The method of claim 5, wherein the performance test job is executed by a script _ run-task.sh.tpl installed in a container, and the script comprises the following four stages:
(2-1) executing the function create _ default: creating openstack-helm deployment by a random deployment create command;
(2-2) traversing enabled _ tasks list defined in values.yaml, executing function run _ rally:
a. configuring and checking the deployment through the deployment user and the deployment check;
b. execute function replace _ task _ args: backing up an original task xml file, executing an OpenStack command through an OpenStackclient to obtain preset resource information required in the task, and updating the preset resource information to the task xml file under a corresponding/tasks/rally/directory by using a sed command;
(2-3) verifying and executing the performance test task through a random task valid command and a random task start command;
and (2-4) exporting the performance test report to the target position through the random task report-out.
8. The method of claim 5, wherein in the step of performing the performance test, a job comprising a contiiners is run in dependence on running a performance test job, and the job is copied to a script of the target node by executing a cp command in the container.
9. The method of claim 8, wherein in the section for performing performance testing, a job of running a derived test report specifically includes:
prepare dependencies in values.yaml: the static of the utility model,
meanwhile, the anotations of 'helm.sh/hook' of post-install is configured in the jobtemplate of the derived test report,
and after the post-upgrade finishes running the performance test jobe, automatically running the export test report jobe.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010660326.2A CN111813420A (en) | 2020-07-10 | 2020-07-10 | Method for carrying out automated performance test on OpenStack cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010660326.2A CN111813420A (en) | 2020-07-10 | 2020-07-10 | Method for carrying out automated performance test on OpenStack cluster |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111813420A true CN111813420A (en) | 2020-10-23 |
Family
ID=72842751
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010660326.2A Pending CN111813420A (en) | 2020-07-10 | 2020-07-10 | Method for carrying out automated performance test on OpenStack cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111813420A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791941A (en) * | 2021-09-15 | 2021-12-14 | 华云数据控股集团有限公司 | Method for automatically testing stability of OpenStack cluster and application |
| US20230142198A1 (en) * | 2021-11-05 | 2023-05-11 | Microsoft Technology Licensing, Llc | Exposure and de-duplication of input parameters for complex helm chart deployment |
| CN116866180A (en) * | 2023-07-04 | 2023-10-10 | 北京志凌海纳科技有限公司 | Cluster upgrading test method and system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017045424A1 (en) * | 2015-09-18 | 2017-03-23 | 乐视控股（北京）有限公司 | Application program deployment system and deployment method |
| CN111338657A (en) * | 2020-02-26 | 2020-06-26 | 山东汇贸电子口岸有限公司 | Template-based palm parameter batch configuration method |
-
2020
- 2020-07-10 CN CN202010660326.2A patent/CN111813420A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017045424A1 (en) * | 2015-09-18 | 2017-03-23 | 乐视控股（北京）有限公司 | Application program deployment system and deployment method |
| CN111338657A (en) * | 2020-02-26 | 2020-06-26 | 山东汇贸电子口岸有限公司 | Template-based palm parameter batch configuration method |
Non-Patent Citations (2)
| Title |
|---|
| 杜磊;: "基于OpenStack和Kubernetes的双向部署技术研究", 电脑知识与技术, no. 01 * |
| 柳春懿;张晓;李阿妮;陈震;: "私有云平台服务能力检测方法", 计算机应用, no. 05 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791941A (en) * | 2021-09-15 | 2021-12-14 | 华云数据控股集团有限公司 | Method for automatically testing stability of OpenStack cluster and application |
| US20230142198A1 (en) * | 2021-11-05 | 2023-05-11 | Microsoft Technology Licensing, Llc | Exposure and de-duplication of input parameters for complex helm chart deployment |
| US11893373B2 (en) * | 2021-11-05 | 2024-02-06 | Microsoft Technology Licensing, Llc | Exposure and de-duplication of input parameters for complex Helm chart deployment |
| CN116866180A (en) * | 2023-07-04 | 2023-10-10 | 北京志凌海纳科技有限公司 | Cluster upgrading test method and system |
| CN116866180B (en) * | 2023-07-04 | 2024-03-01 | 北京志凌海纳科技有限公司 | Cluster upgrading test method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111813420A (en) | Method for carrying out automated performance test on OpenStack cluster | |
| CN111147555B (en) | Heterogeneous resource mixed arrangement method | |
| US8621419B2 (en) | Automating the life cycle of a distributed computing application | |
| US8533676B2 (en) | Single development test environment | |
| US10423571B2 (en) | Method for configuring a real or virtual electronic control unit | |
| US20070101197A1 (en) | System and method for representing system capabilities as software packages in a software package management system | |
| US20130007726A1 (en) | Virtual machine disk image installation | |
| CN111444104B (en) | OpenStack function test method | |
| CN113434158B (en) | Custom management method, device, equipment and medium for big data component | |
| CN109240716B (en) | Big data platform version management and rapid iterative deployment method and system | |
| AU2012201749B2 (en) | Single development test environment | |
| CN113779477A (en) | Assembly line publishing method and system based on PaaS cloud platform | |
| CN113312086B (en) | Software robot system based on instruction set and robot operation method | |
| Talwar et al. | Comparison of approaches to service deployment | |
| CN111459530B (en) | Patching method, device and storage medium | |
| US20110055804A1 (en) | Using Ecoprint for Cloning of Applications | |
| Sethi et al. | Rapid deployment of SOA solutions via automated image replication and reconfiguration | |
| CN112035352B (en) | Cloud lifecycle management-based rapid automatic compiling and deploying method | |
| CN103530151A (en) | Customization method of Linux operating system capable of switching service software systems | |
| CN113918452A (en) | Industrial software compatibility testing method under multi-country productization platform | |
| CN113704081A (en) | Automatic testing method and system for application program compatibility | |
| CN101840337A (en) | Method for customizing reducing system applied to packet capture application | |
| CN111488264A (en) | Deployment scheduling method for interface performance test cluster | |
| CN113961174B (en) | Model development and deployment method based on cloud native microservice | |
| CN112836220B (en) | Cloud center environment inspection method |
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 |