CN115396304A - System and method for automatically deploying cloud native application based on deployment planning table - Google Patents
System and method for automatically deploying cloud native application based on deployment planning table Download PDFInfo
- Publication number
- CN115396304A CN115396304A CN202211121566.0A CN202211121566A CN115396304A CN 115396304 A CN115396304 A CN 115396304A CN 202211121566 A CN202211121566 A CN 202211121566A CN 115396304 A CN115396304 A CN 115396304A
- Authority
- CN
- China
- Prior art keywords
- deployment
- application
- nodes
- node
- deployed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- 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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a system and a method for automatically deploying cloud native applications based on a deployment planning table, which comprises the following steps: the deployment planning table template module is used for collecting server ip addresses and public parameters of management nodes and application nodes to be deployed to form a planning table; the processing planning table module is used for processing the parameter values in the planning table template, storing the parameter values, and performing subsequent deployment service and configuration modification; the deployment checking module is used for judging whether the deployed server is a server required to be deployed or not, and the deployed server is not repeatedly deployed; the system also comprises a cloud native component deployment execution module, an application configuration replacement module, an application deployment module, a deployment node management module and a monitoring module; the platform can be deployed by only modifying the deployment planning table, the information in the analysis table is stored, and all the stored information can be read in subsequent deployment, so that unified and efficient management is provided, the deployment efficiency is improved, the deployment time is saved, and the deployment error rate is reduced.
Description
Technical Field
The invention relates to the technical field of native application deployment, in particular to a system and a method for automatically deploying cloud native applications based on a deployment planning table.
Background
The cloud-native-deployment-based system brings convenience, but when a new environment, particularly an offline environment needs to build a cloud-native-based system application, more components and configuration items need to be deployed manually, the cloud-native-based environment and various configurations need to be deployed at first, various offline packages are downloaded first, then the offline packages are executed step by step according to deployment documents, and then the application components are deployed after the completion. The application component based on the cloud primitive needs to modify a yaml file which is specific to the cloud primitive and contains configuration for filling in various environments, such as a cloud primitive namespace, a nacos namespace, a deployment url, an account password and other information.
In addition to the cloud-native related configuration, the application components themselves also contain various configuration information to be filled, such as database address account passwords, configuration information of various middleware, mirror addresses and the like, which usually involve hundreds of configuration fills of dozens of components, and currently, manual editing of configuration files is adopted to execute deployment commands, which is time-consuming and labor-consuming.
Disclosure of Invention
The invention aims to provide a system and a method for automatically deploying cloud native application based on a deployment planning table, which solve the following technical problems:
cloud native involves deployment and configuration of dozens of components, and application involves yaml file configuration of dozens of components and self component configuration items, and manual deployment is large in workload, long in time consumption, low in efficiency and prone to errors.
The purpose of the invention can be realized by the following technical scheme:
a system and method for automated deployment of cloud-native applications based on a deployment plan form, comprising:
the deployment planning table template module is used for collecting ip addresses and public parameters of the servers of the management nodes and the application nodes to be deployed to form a planning table;
the processing planning table module is used for processing the parameter values in the planning table template, storing the parameter values, and performing subsequent deployment service and configuration modification;
the deployment checking module is used for judging whether the deployed server is the server required to be deployed or not, and the deployed server is not repeatedly deployed;
the cloud native component deployment execution module is used for executing a deployment command from the management node to the server of the application node in a traversing manner to complete deployment according to the ip addresses of the management node to be deployed and the server of the application node acquired from the planning table;
and the application configuration replacement module is used for traversing all the component configuration item files according to the public parameters acquired from the planning table to replace the configuration items to be modified.
Further, the method also comprises the following steps:
and the application deployment module traverses the cloud native deployment files of all the components according to the number of the deployment application nodes acquired from the planning table, and modifies the required configuration items for the cloud native deployment application.
Further, the application configuration replacement module: obtaining the configuration item names required to be modified of all the components, and searching the configuration item names required to be replaced in the configuration file for replacement; all component configuration file modification is automatically completed in a unified manner by circularly traversing the components at the management node; respectively processing special configuration items of different components, and finding out corresponding configuration item names to be modified for accurate replacement; and automatically packaging all configuration items after modification and uploading the configuration items to a service management address of the specified configuration item.
Further, the method also comprises the following steps:
and the deployment node management module is used for matching the server of the application node to the corresponding management node according to the number of the deployed management nodes and the application nodes acquired from the planning table.
Further, the method also comprises the following steps:
and the monitoring module is used for monitoring the deployment condition of the server of the application node at intervals when the application node is deployed and providing a deployment node management module for acquiring a management node interface corresponding to the application node.
Further, the monitoring module randomly sorts the application nodes at intervals, starting from the application node at the head end, each i nodes form a group, the last group can be less than i nodes, sequentially inspects the deployment states of random components in each group of application nodes, records the application node groups with abnormal states, and marks the application node groups with abnormal deployment states as a group A; meanwhile, starting from a terminal application node, enabling each i +1 node to be a group, enabling the last group to be less than i +1 nodes, sequentially patrolling the deployment state of random components in each group of application nodes, recording the application node groups with abnormal states, grouping the application nodes with abnormal deployment states into a group B, if an abnormal application node group A is overlapped with an abnormal application node group B, grouping the application nodes at the overlapped part of the group A and the group B into a group C, performing key monitoring on the group C, polling and reading the progress condition of yaml files needing to be modified based on cloud-based deployment of all components of the application nodes in the group C, determining the nodes with abnormal deployment process states of the application nodes in the group C as fault nodes, and sending an alarm to a management node corresponding to the application nodes.
A method for automatically deploying cloud native applications based on a deployment plan table is characterized by comprising the following steps: .
S1: placing the deployment planning table to all management nodes needing deployment, and executing deployment scripts on the management nodes;
s2: the processing planning table module processes the parameter values in the planning table and stores the parameter values;
s3: according to the ip address of the application node deployed in the planning table, remotely logging in the deployed application node from the management node ssh, executing a deployment command to complete deployment of the cloud native basic component and the middleware, monitoring the deployment condition of the application node, and re-deploying the application node which is monitored abnormally;
s4: the modified configuration file is uploaded;
s5: polling and reading all the components, judging whether the polled components have affinity, if so, entering affinity circulation judgment, uniformly replacing and configuring all the components which accord with the affinity, judging a multi-node time port plan, a configuration file and a deployment name plan, and modifying a yaml file; if the affinity does not exist, the yaml file is directly modified;
s6: and deploying the components according to the modified yaml file through the cloud native command.
Further, the step S1 includes:
s101, acquiring a deployed script packet and decompressing the deployed script packet locally;
s102, filling a deployment planning table in the decompressed file, wherein the deployment planning table comprises server ip planning, database addresses, third party calling addresses and public parameters;
and S103, uploading the filled forms to a deployment package, and putting the deployment package to all nodes needing deployment.
Further, the step S4 of uploading the modified configuration file includes the following steps:
s401, polling and reading the stored parameter names, searching all component configuration files needing to be modified at a local management node, searching the parameter names, and replacing parameter values after the parameter names are found;
s402, after all the configuration files needing to be modified of the components are modified, the configuration files are packaged and automatically uploaded to a designated space of a configuration management server for the use of the components.
The invention has the beneficial effects that:
the platform can be deployed by only modifying the deployment planning table, the information in the table is analyzed and stored, all the stored information can be read in subsequent deployment, unified and efficient management is provided, the deployment efficiency is improved, the deployment time is saved, the deployment error rate is reduced, and most of manual tedious work is also reduced. And a set of complete and rapid deployment scheme is provided for subsequent new environment deployment.
Drawings
The invention will be further described with reference to the accompanying drawings.
FIG. 1 is a flow chart of a method for automatically deploying cloud-native applications based on a deployment plan table in accordance with the present invention;
FIG. 2 is a flowchart of step S1 of a specific embodiment of a method for automatically deploying cloud-based native applications based on a deployment plan table according to the present invention;
fig. 3 is a flowchart of step S4 according to a specific embodiment of the method for automatically deploying a cloud-native application based on a deployment plan table.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1-3, the present invention is a system and method for automatically deploying cloud native applications based on a deployment plan table, including:
the deployment planning table template module is used for collecting ip addresses and public parameters of the servers of the management nodes and the application nodes to be deployed to form a planning table;
the processing planning table module is used for processing the parameter values in the planning table template, storing the parameter values, and performing subsequent deployment service and configuration modification;
the deployment checking module is used for judging whether the deployed server is the server required to be deployed or not, and the deployed server is not repeatedly deployed;
the cloud native component deployment execution module is used for executing a deployment command from the management node to the server of the application node in a traversing manner to complete deployment according to the ip addresses of the management node to be deployed and the server of the application node acquired from the planning table;
and the application configuration replacement module is used for traversing all the component configuration item files according to the public parameters acquired from the planning table to replace the configuration items to be modified.
In one embodiment of the present invention, the method further comprises:
and the application deployment module traverses the cloud native deployment files of all the components according to the number of the deployment application nodes acquired in the planning table, modifies the required configuration items and is used for the cloud native deployment application.
In one embodiment of the invention, the application configuration replacement module: obtaining the configuration item names required to be modified of all the components, and searching the configuration item names required to be replaced in the configuration file for replacement; all component configuration file modification is automatically completed in a unified manner by circularly traversing the components at the management node; respectively processing special configuration items of different components, and finding out the corresponding configuration item name to be modified for accurate replacement; and automatically packaging all configuration items after modification and uploading the configuration items to a service management address of the specified configuration item.
In one embodiment of the present invention, the method further comprises:
and the deployment node management module is used for matching the server of the application node to the corresponding management node according to the number of the deployed management nodes and the application nodes acquired from the planning table.
In one embodiment of the present invention, the method further comprises:
and the monitoring module is used for monitoring the deployment condition of the server of the application node at intervals when the application node is deployed and providing a deployment node management module for acquiring a management node interface corresponding to the application node.
In one embodiment of the present invention, the monitoring module randomly sorts the application nodes at intervals, where each i nodes form one group from the head-end application node, and the last group may lack i nodes, sequentially inspects the deployment state of the random components in each group of application nodes, records the application node groups with abnormal states, and records the application node groups with abnormal deployment states as group a; meanwhile, starting from a terminal application node, enabling each i +1 node to be a group, enabling the last group to be less than i +1 nodes, sequentially patrolling the deployment state of random components in each group of application nodes, recording the application node groups with abnormal states, grouping the application nodes with abnormal deployment states into a group B, if an abnormal application node group A is overlapped with an abnormal application node group B, grouping the application nodes at the overlapped part of the group A and the group B into a group C, performing key monitoring on the group C, polling and reading the progress condition of yaml files needing to be modified based on cloud-based deployment of all components of the application nodes in the group C, determining the nodes with abnormal deployment process states of the application nodes in the group C as fault nodes, and sending an alarm to a management node corresponding to the application nodes. By grouping the application nodes after sequencing from front to back and from back to front simultaneously, monitoring the deployment state of the configuration information in a random component in each application node in the grouping, and polling and reading the progress condition of the yaml file needing to be modified based on cloud-based original deployment of all components of the application nodes monitoring the abnormal overlapping part of the grouping in two-time monitoring, the monitoring module is convenient to find out the nodes with problems in the deployment process of the application nodes quickly, and detection errors caused by the time difference between the deployment time and the detection time of the configuration information in a random component when the grouping is detected in sequence are avoided.
A method for automatically deploying cloud native applications based on a deployment plan table is characterized by comprising the following steps: .
S1: placing the deployment planning table to all management nodes needing deployment, and executing deployment scripts on the management nodes;
s2: the processing planning table module processes parameter values in the planning table and stores the parameter values;
s3: remotely logging in a deployed application node from a management node ssh according to an ip address of the application node deployed in the planning table, executing a deployment command to complete deployment of the cloud native basic component and the middleware, monitoring the deployment condition of the application node, and re-deploying the application node which is monitored abnormally;
s4: the modified configuration file is uploaded;
s5: polling and reading all components, judging whether the polled components have affinity, if so, entering affinity cycle judgment, uniformly replacing and configuring all components conforming to the affinity, judging port planning, configuration files and deployment name planning in multi-node process, and modifying the yaml files; if the affinity does not exist, the yaml file is directly modified;
s6: and deploying the components according to the modified yaml file through the cloud native command.
In one embodiment of the present invention, the step S1 includes:
s101, acquiring a deployed script packet and decompressing the deployed script packet locally;
s102, filling a deployment planning table in the decompressed file, wherein the deployment planning table comprises server ip planning, database addresses, third-party calling addresses and public parameters;
and S103, uploading the filled forms to a deployment package, and putting the deployment package to all nodes needing to be deployed.
In one embodiment of the present invention, the step S4 of uploading the modified configuration file includes the following steps:
s401, polling and reading the stored parameter names, searching all component configuration files needing to be modified in a local management node, searching the parameter names, and replacing parameter values after the parameter names are found;
s402, after all the configuration files needing to be modified of the components are modified, the configuration files are packaged and automatically uploaded to a designated space of a configuration management server for the use of the components.
In the description of the present invention, it is to be understood that the terms "upper", "lower", "left", "right", and the like, indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, are only for convenience in describing the present invention and simplifying the description, and do not indicate or imply that the referred device or element must have a specific orientation and a specific orientation configuration and operation, and thus, should not be construed as limiting the present invention. Furthermore, "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present invention, the meaning of "a plurality" is two or more unless otherwise specified.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and the like are to be construed broadly and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be directly connected or indirectly connected through an intermediate member, or they may be connected through two or more elements. The specific meanings of the above terms in the present invention can be understood in a specific case to those of ordinary skill in the art.
While one embodiment of the present invention has been described in detail, the description is only a preferred embodiment of the present invention and should not be taken as limiting the scope of the invention. All equivalent changes and modifications made within the scope of the present invention shall fall within the scope of the present invention.
Claims (9)
1. A system for automated deployment of cloud-native applications based on a deployment plan, comprising:
the deployment planning table template module is used for collecting server ip addresses and public parameters of management nodes and application nodes to be deployed to form a planning table;
the processing planning table module is used for processing the parameter values in the planning table template, storing the parameter values, and performing subsequent deployment service and configuration modification;
the deployment checking module is used for judging whether the deployed server is the server required to be deployed or not, and the deployed server is not repeatedly deployed;
the cloud native component deployment execution module is used for executing a deployment command from the management node to the server of the application node in a traversing manner to complete deployment according to the ip addresses of the management node to be deployed and the server of the application node acquired from the planning table;
and the application configuration replacement module is used for traversing all the component configuration item files according to the public parameters acquired from the planning table to replace the configuration items to be modified.
2. The system for automatically deploying the cloud-native application based on the deployment plan table according to claim 1, further comprising:
and the application deployment module traverses the cloud native deployment files of all the components according to the number of the deployment application nodes acquired from the planning table, and modifies the required configuration items for the cloud native deployment application.
3. The system for automatically deploying cloud-native applications based on the deployment plan form of claim 1, wherein the application configuration replacement module: obtaining the names of the configuration items required to be modified by all the components, and searching the names of the configuration items required to be replaced in the configuration file for replacement; all component configuration file modification is automatically completed in a unified manner by circularly traversing the components at the management node; respectively processing special configuration items of different components, and finding out corresponding configuration item names to be modified for accurate replacement; and automatically packaging all the modified configuration items and uploading the configuration items to the service management address of the specified configuration item.
4. The system for automatically deploying cloud-native applications based on a deployment plan form according to claim 1, further comprising:
and the deployment node management module is used for matching the server of the application node to the corresponding management node according to the number of the deployed management nodes and the application nodes acquired from the planning table.
5. The system for automatically deploying cloud-native applications based on a deployment plan form according to claim 1, further comprising:
and the monitoring module is used for monitoring the deployment condition of the server of the application node at intervals when the application node is deployed and providing a deployment node management module for acquiring a management node interface corresponding to the application node.
6. The system for automatically deploying cloud native applications based on the deployment plan table according to claim 5, wherein the monitoring module randomly sorts the application nodes at intervals, starting from a head-end application node, each i nodes form one group, the last group can be less than i nodes, the deployment state of random components in each group of application nodes is sequentially patrolled, the application node groups with abnormal states are recorded, and the application nodes with abnormal deployment states are grouped into a group A; meanwhile, starting from a tail end application node, setting every i +1 nodes as a group, setting the last group to be less than i +1 nodes, sequentially inspecting the deployment states of random components in each group of application nodes, recording the application node groups with abnormal states, grouping the application nodes with abnormal deployment states as a group B, if an abnormal application node group A is overlapped with an abnormal application node group B, dividing the application nodes at the overlapped part of the group A and the group B into a group C, performing key monitoring on the group C, polling and reading the progress condition of a yaml file needing to be modified based on cloud-native deployment of all components of the application nodes in the group C, determining the nodes with abnormal deployment progress states of the application nodes in the group C as fault nodes, and sending an alarm to a management node corresponding to the application nodes.
7. A method for automatically deploying cloud native applications based on a deployment plan table is characterized by comprising the following steps:
s1: placing the deployment planning table to all management nodes needing deployment, and executing deployment scripts on the management nodes;
s2: the processing planning table module processes parameter values in the planning table and stores the parameter values;
s3: remotely logging in a deployed application node from a management node ssh according to an ip address of the application node deployed in the planning table, executing a deployment command to complete deployment of the cloud native basic component and the middleware, monitoring the deployment condition of the application node, and re-deploying the application node which is monitored abnormally;
s4: the modified configuration file is uploaded;
s5: polling and reading all the components, judging whether the polled components have affinity, if so, entering affinity circulation judgment, uniformly replacing and configuring all the components which accord with the affinity, judging a multi-node time port plan, a configuration file and a deployment name plan, and modifying a yaml file; if the file does not have affinity, the yaml file is directly modified;
s6: and deploying the components according to the modified yaml file through the cloud native command.
8. The method for automatically deploying the cloud-native application based on the deployment plan table according to claim 7, wherein the step S1 comprises:
s101, acquiring a deployed script packet and decompressing the deployed script packet locally;
s102, filling a deployment planning table in the decompressed file, wherein the deployment planning table comprises server ip planning, database addresses, third party calling addresses and public parameters;
and S103, uploading the filled forms to a deployment package, and putting the deployment package to all nodes needing to be deployed.
9. The method for automatically deploying the cloud native application based on the deployment plan table according to claim 7, wherein the step S4 of modifying and uploading the configuration file comprises the following steps:
s401, polling and reading the stored parameter names, searching all component configuration files needing to be modified in a local management node, searching the parameter names, and replacing parameter values after the parameter names are found;
s402, after all the configuration files needing to be modified of the components are modified, the configuration files are packaged and automatically uploaded to a designated space of a configuration management server for the use of the components.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211121566.0A CN115396304B (en) | 2022-09-15 | 2022-09-15 | System and method for automatically deploying cloud native application based on deployment planning table |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211121566.0A CN115396304B (en) | 2022-09-15 | 2022-09-15 | System and method for automatically deploying cloud native application based on deployment planning table |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115396304A true CN115396304A (en) | 2022-11-25 |
| CN115396304B CN115396304B (en) | 2023-08-08 |
Family
ID=84126114
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211121566.0A Active CN115396304B (en) | 2022-09-15 | 2022-09-15 | System and method for automatically deploying cloud native application based on deployment planning table |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115396304B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115757361A (en) * | 2022-12-26 | 2023-03-07 | 北京柏睿数据技术股份有限公司 | Method and system for automatic deployment of database cluster system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140325503A1 (en) * | 2012-01-09 | 2014-10-30 | Huawei Technologies Co., Ltd. | Cloud infrastructure-based management system and method for maintenance and deployment of application system |
| US10007501B1 (en) * | 2017-05-19 | 2018-06-26 | Central South University | Method of deploying applications rapidly based on customized android platform |
| CN110704164A (en) * | 2019-09-30 | 2020-01-17 | 珠海市新德汇信息技术有限公司 | Cloud native application platform construction method based on Kubernetes technology |
| CN111736827A (en) * | 2020-08-25 | 2020-10-02 | 长沙慧码至一信息科技有限公司 | Cloud native development component system |
| CN113127150A (en) * | 2021-03-18 | 2021-07-16 | 同盾控股有限公司 | Rapid deployment method and device of cloud native system, electronic equipment and storage medium |
| CN113824790A (en) * | 2021-09-23 | 2021-12-21 | 大连华信计算机技术股份有限公司 | Cloud native PaaS management platform supporting enterprise-level application |
| US11243989B1 (en) * | 2021-07-02 | 2022-02-08 | Noragh Analytics, Inc. | Configurable, streaming hybrid-analytics platform |
| CN114064083A (en) * | 2021-11-22 | 2022-02-18 | 江苏安超云软件有限公司 | Method for deploying cloud native application through self-defined template in configuration center and application |
-
2022
- 2022-09-15 CN CN202211121566.0A patent/CN115396304B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140325503A1 (en) * | 2012-01-09 | 2014-10-30 | Huawei Technologies Co., Ltd. | Cloud infrastructure-based management system and method for maintenance and deployment of application system |
| US10007501B1 (en) * | 2017-05-19 | 2018-06-26 | Central South University | Method of deploying applications rapidly based on customized android platform |
| CN110704164A (en) * | 2019-09-30 | 2020-01-17 | 珠海市新德汇信息技术有限公司 | Cloud native application platform construction method based on Kubernetes technology |
| CN111736827A (en) * | 2020-08-25 | 2020-10-02 | 长沙慧码至一信息科技有限公司 | Cloud native development component system |
| CN113127150A (en) * | 2021-03-18 | 2021-07-16 | 同盾控股有限公司 | Rapid deployment method and device of cloud native system, electronic equipment and storage medium |
| US11243989B1 (en) * | 2021-07-02 | 2022-02-08 | Noragh Analytics, Inc. | Configurable, streaming hybrid-analytics platform |
| CN113824790A (en) * | 2021-09-23 | 2021-12-21 | 大连华信计算机技术股份有限公司 | Cloud native PaaS management platform supporting enterprise-level application |
| CN114064083A (en) * | 2021-11-22 | 2022-02-18 | 江苏安超云软件有限公司 | Method for deploying cloud native application through self-defined template in configuration center and application |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115757361A (en) * | 2022-12-26 | 2023-03-07 | 北京柏睿数据技术股份有限公司 | Method and system for automatic deployment of database cluster system |
| CN115757361B (en) * | 2022-12-26 | 2023-08-18 | 北京柏睿数据技术股份有限公司 | Automatic deployment method and system for database cluster system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115396304B (en) | 2023-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109361562B (en) | Automatic testing method based on associated network equipment access | |
| CN110691009B (en) | Network equipment inspection method and device | |
| CN110908909A (en) | Automatic testing method and device, storage medium and equipment | |
| CN115396304A (en) | System and method for automatically deploying cloud native application based on deployment planning table | |
| CN111224845A (en) | Equipment automatic testing system and method based on Internet of things cloud | |
| EP3809269A1 (en) | Monitoring a distributed application server environment | |
| CN111723019A (en) | Interface debugging method and system | |
| CN108650134B (en) | Network fault positioning method and device and electronic equipment | |
| CN112269697B (en) | Equipment storage performance testing method, system and related device | |
| CN112019405B (en) | Automatic testing method and system | |
| US10068786B1 (en) | Data structures for semiconductor die packaging | |
| CN117370203A (en) | Automatic test method, system, electronic equipment and storage medium | |
| CN112583663A (en) | Automatic network performance testing method based on domestic operating system | |
| CN109379588B (en) | Automatic testing method and system for high-definition DVR | |
| CN110880990A (en) | Configuration checking method and device for big data cluster component and computing equipment | |
| CN111966394B (en) | ETL-based data analysis method, device, equipment and storage medium | |
| CN115525545A (en) | Docker-based automatic testing method, system, equipment and medium | |
| CN109062746A (en) | A kind of fault self-diagnosis method, device and the storage medium of server admin unit | |
| CN114595089A (en) | Hard disk remote diagnosis method, system, terminal and storage medium | |
| CN106992873B (en) | Protection group processing method and device | |
| CN112346930A (en) | Method and system for monitoring full link based on CAT | |
| CN116795724B (en) | Method, system, equipment and medium for testing unmanned aerial vehicle loading equipment software interface | |
| CN113076243B (en) | Method for optimizing automatic testing cost of image recognition | |
| CN113452580B (en) | Method for automatically checking network equipment faults in batches and test host end | |
| CN114826956B (en) | Automatic DPI policy library file generation method and device for DPI test equipment |
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 |