CN112084170A - Ansable-based mysql-mha cluster one-key deployment method and system - Google Patents
Ansable-based mysql-mha cluster one-key deployment method and system Download PDFInfo
- Publication number
- CN112084170A CN112084170A CN202010805534.7A CN202010805534A CN112084170A CN 112084170 A CN112084170 A CN 112084170A CN 202010805534 A CN202010805534 A CN 202010805534A CN 112084170 A CN112084170 A CN 112084170A
- Authority
- CN
- China
- Prior art keywords
- mha
- master
- deployment
- mysql
- ansable
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000012544 monitoring process Methods 0.000 claims abstract description 18
- 238000013515 script Methods 0.000 claims description 25
- 238000009434 installation Methods 0.000 claims description 21
- 238000004519 manufacturing process Methods 0.000 abstract description 4
- 230000006870 function Effects 0.000 description 8
- 101100264195 Caenorhabditis elegans app-1 gene Proteins 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 101100029789 Mus musculus Pigz gene Proteins 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000004140 cleaning Methods 0.000 description 2
- 239000002131 composite material Substances 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 230000006837 decompression Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000010076 replication Effects 0.000 description 2
- 239000000523 sample Substances 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a mysql-mha cluster one-key deployment method and system based on ansable, wherein the method comprises the following steps: s1 is used for installing the mysql database in the server; s2 is used for creating accounts in the master library and configuring the master node; s3 is used for configuring the main library connection for the database; s4, a step for deploying and configuring mha basic nodes; s5 is used for carrying out deployment configuration on the mha management node; s6 is used for the step of node deployment monitoring. Each step is split one by one through the ansable, a single logic step is generated, the single logic step is divided into a plurality of large steps according to operation logic, each large step is divided into a plurality of small steps, the deployment environment is decoupled, only different points of each cluster need to be concerned in each deployment, complex deployment can be completed through unified configuration, the operation difficulty is reduced, the production efficiency is improved, repeated labor is avoided, and the time is saved.
Description
Technical Field
The invention relates to the technical field of computer software, in particular to a mysql-mha cluster one-key deployment method and system based on ansable.
Background
Deploying the mysql-mha cluster in the traditional scene requires a series of work such as manual installation of various server software, downloading of a toolkit, copying of a script, configuration of database parameters, establishment of a directory, modification of a password, starting of a process and the like, and each step has a certain sequence and cannot be skipped or the operation sequence is changed. In large-scale and large-batch scenes, the efficiency is low through manual deployment each time, the operation is difficult, and the waste of resources is easily caused. The prior art does not have a method and a system for one-key deployment through an infrastructure tool.
Disclosure of Invention
The invention aims to provide a mysql-mha cluster one-key deployment method and system based on ansable.
The invention provides a mysql-mha cluster one-key deployment method based on ansable, which comprises the following steps: s1 is used for installing the mysql database in the server; s2 is used for creating accounts in the master library and configuring the master node; s3 is used for configuring the main library connection for the database; s4, a step for deploying and configuring mha basic nodes; s5 is used for carrying out deployment configuration on the mha management node; s6 is used for the step of node deployment monitoring.
The step S1 of installing the mysql database on the server includes: s11 is used for creating users, user groups and catalogs; s12 is used for decompressing the installation package and copying the installation package to the specified directory; s13 is used for inquiring the original database and backing up; s14 is used for obtaining a new software source step; s15 is a step for registering the database, configuring the user, and setting the user' S right. The step of S2 for creating an account in the master repository and configuring the master repository includes: s21 is a step for creating and authorizing a user. The step S3 of configuring the master library connection for the database includes: s31 is used for copying the master-slave IP definition file; s32 is used for copying the master-slave configuration py; s33 is for configuring a master-slave copy and start-up step. The step S5 of configuring deployment of the mha management node includes: s51 is used for establishing mha files and directories and checking the mha running state; s52 is for manual or automatic control of the step of failover. The step S6 of monitoring node deployment includes: s61, a step for constructing a deployment environment; s62 is used for copying the tool and script in the program package; s63 is a step for writing a timed task. The invention provides a mysql-mha cluster one-key deployment method based on ansable, which further comprises the following steps: s7 is a step for creating a backup directory and a script directory and making a copy.
The invention provides an ansable-based mysql-mha cluster one-key deployment system, which comprises: a module for installing a mysql database at a server; a module for creating an account in the master repository and configuring the master node; a module for configuring a master library connection to a database; a module for deployment configuration of mha base nodes; a module for deployment configuration of mha management nodes; and the module is used for monitoring the node deployment.
The module for installing the mysql database on the server comprises the following modules: a submodule for creating users, user groups and directories; a submodule for decompressing the installation package and copying the installation package to the specified directory; the submodule is used for inquiring the original database and backing up the database and is used for acquiring a new software source submodule; and the submodule is used for logging in the database, configuring the user and setting the authority of the user. The module for creating an account in the master repository and configuring the master repository comprises: a sub-module for creating and authorizing a user. The module for configuring a master library connection to a database comprises: a submodule for copying master-slave IP definition files; a submodule for copying the master-slave configuration py; and the submodule is used for configuring master-slave copy and starting. The module for deployment and configuration of mha management node comprises: a submodule for creating mha files and directories and checking mha the running status; a submodule for manually or automatically controlling failover. The module for node deployment monitoring comprises: a submodule for setting up a deployment environment; a submodule for copying tools and scripts in the package; a submodule for writing timing tasks. The mysql-mha cluster one-key deployment system based on ansable further comprises: and a module for creating and copying the backup directory and the script directory.
According to the mysql-mha cluster one-key deployment method and system based on the ansable, each step is split one by one through the ansable, a single logic step is generated, the single logic step is divided into a plurality of large steps according to operation logic, each large step is divided into a plurality of small steps, the deployment environment is decoupled, and the structure is clear and organized. The complex deployment can be completed only by paying attention to different points of each cluster in each deployment, the operation difficulty is reduced, the production efficiency is improved, the repeated labor is avoided, and the time is saved.
Drawings
FIG. 1 is a schematic diagram illustrating steps of a mysql-mha cluster one-key deployment method based on ansable according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating the step S1 of installing the mysql database on the server according to the first embodiment of the present invention;
FIG. 3 is a diagram illustrating the step S3 of configuring the master library connection for the database according to an embodiment of the present invention;
fig. 4 is a schematic diagram of the step of S6 for node deployment monitoring according to the first embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, 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 some, but not all, embodiments of the present invention. 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.
Example one
As shown in fig. 1, the embodiment provides an ansable-based mysql-mha cluster one-key deployment method, including the following steps:
s1 is used for installing the mysql database in the server;
s2 is used for creating accounts in the master library and configuring the master node;
s3 is used for configuring the main library connection for the database;
s4, a step for deploying and configuring mha basic nodes;
s5 is used for carrying out deployment configuration on the mha management node;
s6 is used for the step of node deployment monitoring.
Those skilled in the art can understand that in the mysql-mha cluster one-key deployment method based on the ansable provided in this embodiment, each step is split one by one through the ansable, a single logic step is generated, and the single logic step is divided into several large steps according to the operation logic, each large step is divided into several small steps, the deployment environment is decoupled, and the structure is clear and organized. The complex deployment can be completed only by paying attention to different points of each cluster in each deployment, the operation difficulty is reduced, the production efficiency is improved, the repeated labor is avoided, and the time is saved.
Mha (master High availability) is a software package for automatic master failover and Slave promotion. It is based on standard MySQL replication (asynchronous/semi-synchronous). MHA consists of two parts: MHA Manager and MHA Node. The MHA Manager can be separately deployed on one independent machine to manage a plurality of master-slave clusters, and can also be deployed on one slave. The MHA Manager probes the node nodes of the cluster, and when finding that a master fails, it can automatically promote the slave with the latest data to a new master, and then direct all other slaves to the new master. The entire failover process is transparent to the application. The MHA node runs on each MySQL server (master/slave/manager) which speeds failover by monitoring scripts that have the function of parsing and cleaning logs files.
The infrastructure is developed based on Python paramiko, distributed, free of a client, light in weight, strong in remote command execution operation by using YMAL and Jinja2 template languages in configuration grammar. The goals of the anchor tool include: automatically deploying the APP; an automation management configuration item; automated continuous interaction; automated (AWS) cloud service management.
As shown in fig. 2, the step S1 of installing the mysql database on the server includes:
s11 is used for creating users, user groups and catalogs;
s12 is used for decompressing the installation package and copying the installation package to the specified directory;
s13 is a step for querying the original database and backing up,
s14 is used for obtaining a new software source step;
s15 is a step for registering the database, configuring the user, and setting the user' S right.
As will be appreciated by those skilled in the art, the new software sources include yum source and epel source, py is the user's login code, and the mysql is logged in using a root username password, which facilitates the installation and operation of the mysql database. According to the implementation, when mysql is installed, a Dbbase source program is adopted to execute installation of a mysql database, a user and a group are created, a directory is established, mysql is decompressed and transmitted, the directory name is changed, an authorized installation directory, an authorized data directory and an authorized data directory are established, the directory is written into a register, result is circularly judged, service is added into init.d, an old yum source is backed up, a new yum source is obtained, a new epel source is obtained, the copy my.cnf is carried out by utilizing an available yum downloading method, the copy of the changed my.cnf is carried out, the py of the changed my.cnf is automatically obtained, the mysql is initialized, the mysql is started, an execution file in the mysql/bin is added into the/usr/bin, a compiling library is added, a password is changed by copying, the py of a copy user is added, and a modification password is operated.
Further, the step of S2, configured to create an account in the master library and configure the master node, includes:
s21 is a step for creating and authorizing a user.
Those skilled in the art will understand that the embodiment uses the Master source code to implement account creation in the primary library, where the users include a copy user, a backup user, a root user, a mysql user, an analyzer user, a monitor user, a slow _ query user, and an incep _ read user.
As shown in fig. 3, the step of S3 for configuring the master library connection for the database includes:
s31 is used for copying the master-slave IP definition file;
s32 is used for copying the master-slave configuration py;
s33 is for configuring a master-slave copy and start-up step.
Those skilled in the art can understand that in the embodiment, a Slave source code is used to implement a function of connecting a database configuration master library, py is a login code of a user, deployment and configuration are performed on mha base nodes, a Mha-base source program is used to execute installation of mha-node software, mha node files are copied, perls are already done, perls cannot be directly done on the mha node, and inc files are in a staggered directory.
Further, the step of S5 for performing deployment configuration on the mha management node includes:
s51 is used for establishing mha files and directories and checking the mha running state;
s52 is for manual or automatic control of the step of failover.
Those skilled in the art can understand that the present embodiment adopts mha-manager source code to implement the function of installing mha-manager software on the control node, where the mha file includes mha parameter file and log file, the directories include mha parameter file directory, mha log directory, binlog directory, and the like, and binlog is a binary tool of the database. In this embodiment, mha-manager software is installed on a control node, a mha parameter file directory is established, a mha log directory is established, a log file is established, a remote binlog directory is established, which is master _ binlog _ dir in app1.cnf, ssh users are mysql, directory permissions are also mysql, a fault switching script is transmitted, a manual switching script is transmitted, app1.cnf is transmitted, functional codes such as app.cnf, failover, online _ change py are copied and modified, and a py file is executed.
As shown in fig. 4, the step S6 of monitoring node deployment includes:
s61, a step for constructing a deployment environment;
s62 is used for copying the tool and script in the program package;
s63 is a step for writing a timed task.
Those skilled in the art can understand that in the embodiment, an Anemomer and Zabbix are used for building a deployment environment to realize a monitoring function, and Anemomer software can be used for program query.
Further, this embodiment provides a mysql-mha cluster one-key deployment method based on ansable, further including:
s7 is a step for creating a backup directory and a script directory and making a copy.
As can be understood by those skilled in the art, the embodiment adopts a xtrabackup tool, a decompression transmission xtrabackup tool, a xtrabackup directory name changing, a command of copying xtrabackup and the like to a/usr/bin directory, and yum of enable downloads a pigz multithread compression tool and copies a qpress front-end program. Creating a backup catalog, creating a script catalog, copying a composite script, copying a backup log script, adding a db backup database backup into a crontab timing execution task command, and adding a log backup into a crontab timing execution task command.
Example two
The embodiment provides an ansable-based mysql-mha cluster one-key deployment system, which comprises:
a module for installing a mysql database at a server;
a module for creating an account in the master repository and configuring the master node;
a module for configuring a master library connection to a database;
a module for deployment configuration of mha base nodes;
a module for deployment configuration of mha management nodes;
and the module is used for monitoring the node deployment.
Those skilled in the art can understand that, in the mysql-mha cluster one-key deployment system based on ansable provided in this embodiment, each step is split one by one through ansable, a single logic step is generated, and the system is divided into several large steps according to operation logic, each large step is divided into several small steps, the deployment environment is decoupled, and the structure is clear and organized. The complex deployment can be completed only by paying attention to different points of each cluster in each deployment, the operation difficulty is reduced, the production efficiency is improved, the repeated labor is avoided, and the time is saved.
Mha (master High availability) is a software package for automatic master failover and Slave promotion. It is based on standard MySQL replication (asynchronous/semi-synchronous). MHA consists of two parts: MHA Manager and MHA Node. The MHA Manager can be separately deployed on one independent machine to manage a plurality of master-slave clusters, and can also be deployed on one slave. The MHA Manager probes the node nodes of the cluster, and when finding that a master fails, it can automatically promote the slave with the latest data to a new master, and then direct all other slaves to the new master. The entire failover process is transparent to the application. The MHA node runs on each MySQL server (master/slave/manager) which speeds failover by monitoring scripts that have the function of parsing and cleaning logs files.
The infrastructure is developed based on Python paramiko, distributed, free of a client, light in weight, strong in remote command execution operation by using YMAL and Jinja2 template languages in configuration grammar. The goals of the anchor tool include: automatically deploying the APP; an automation management configuration item; automated continuous interaction; automated (AWS) cloud service management.
Further, the module for installing the mysql database on the server comprises:
a submodule for creating users, user groups and directories;
a submodule for decompressing the installation package and copying the installation package to the specified directory;
a sub-module for querying the original database and backing up,
the software source submodule is used for acquiring a new software source submodule;
and the submodule is used for logging in the database, configuring the user and setting the authority of the user.
As will be appreciated by those skilled in the art, the new software sources include yum source and epel source, py is the user's login code, and the mysql is logged in using a root username password, which facilitates the installation and operation of the mysql database. According to the implementation, when mysql is installed, a Dbbase source program is adopted to execute installation of a mysql database, a user and a group are created, a directory is established, mysql is decompressed and transmitted, the directory name is changed, an authorized installation directory, an authorized data directory and an authorized data directory are established, the directory is written into a register, result is circularly judged, service is added into init.d, an old yum source is backed up, a new yum source is obtained, a new epel source is obtained, the copy my.cnf is carried out by utilizing an available yum downloading method, the copy of the changed my.cnf is carried out, the py of the changed my.cnf is automatically obtained, the mysql is initialized, the mysql is started, an execution file in the mysql/bin is added into the/usr/bin, a compiling library is added, a password is changed by copying, the py of a copy user is added, and a modification password is operated.
Further, the module for creating an account in a master repository and configuring a master node includes:
a sub-module for creating and authorizing a user.
Those skilled in the art will understand that the embodiment uses the Master source code to implement account creation in the primary library, where the users include a copy user, a backup user, a root user, a mysql user, an analyzer user, a monitor user, a slow _ query user, and an incep _ read user.
Further, the module for configuring a master library connection for a database includes:
a submodule for copying master-slave IP definition files;
a submodule for copying the master-slave configuration py;
and the submodule is used for configuring master-slave copy and starting.
Those skilled in the art can understand that in the embodiment, a Slave source code is used to implement a function of connecting a database configuration master library, py is a login code of a user, deployment and configuration are performed on mha base nodes, a Mha-base source program is used to execute installation of mha-node software, mha node files are copied, perls are already done, perls cannot be directly done on the mha node, and inc files are in a staggered directory.
Further, the module for deployment and configuration of mha management node includes:
a submodule for creating mha files and directories and checking mha the running status;
a submodule for manually or automatically controlling failover.
Those skilled in the art can understand that the present embodiment adopts mha-manager source code to implement the function of installing mha-manager software on the control node, where the mha file includes mha parameter file and log file, the directories include mha parameter file directory, mha log directory, binlog directory, and the like, and binlog is a binary tool of the database. In this embodiment, mha-manager software is installed on a control node, a mha parameter file directory is established, a mha log directory is established, a log file is established, a remote binlog directory is established, which is master _ binlog _ dir in app1.cnf, ssh users are mysql, directory permissions are also mysql, a fault switching script is transmitted, a manual switching script is transmitted, app1.cnf is transmitted, functional codes such as app.cnf, failover, online _ change py are copied and modified, and a py file is executed.
Further, the module for monitoring node deployment includes:
a submodule for setting up a deployment environment;
a submodule for copying tools and scripts in the package;
a submodule for writing timing tasks.
Those skilled in the art can understand that in the embodiment, an Anemomer and Zabbix are used for building a deployment environment to realize a monitoring function, and Anemomer software can be used for program query.
Further, this embodiment provides an ansable-based mysql-mha cluster one-key deployment system, further including:
and a module for creating and copying the backup directory and the script directory.
As can be understood by those skilled in the art, the embodiment adopts a xtrabackup tool, a decompression transmission xtrabackup tool, a xtrabackup directory name changing, a command of copying xtrabackup and the like to a/usr/bin directory, and yum of enable downloads a pigz multithread compression tool and copies a qpress front-end program. Creating a backup catalog, creating a script catalog, copying a composite script, copying a backup log script, adding a db backup database backup into a crontab timing execution task command, and adding a log backup into a crontab timing execution task command.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (14)
1. An ansable-based mysql-mha cluster one-key deployment method is characterized by comprising the following steps: s1 is used for installing the mysql database in the server; s2 is used for creating accounts in the master library and configuring the master node; s3 is used for configuring the main library connection for the database; s4, a step for deploying and configuring mha basic nodes; s5 is used for carrying out deployment configuration on the mha management node; s6 is used for the step of node deployment monitoring.
2. The ansable-based mysql-mha cluster one-key deployment method of claim 1, wherein the step of S1 for installing a mysql database on a server comprises: s11 is used for creating users, user groups and catalogs; s12 is used for decompressing the installation package and copying the installation package to the specified directory; s13 is used for inquiring the original database and backing up, S14 is used for obtaining a new software source; s15 is a step for registering the database, configuring the user, and setting the user' S right.
3. The ansable-based mysql-mha cluster one-key deployment method of claim 2, wherein the step of S2 for creating accounts at a master repository and configuring master nodes comprises: s21 is a step for creating and authorizing a user.
4. The ansable-based mysql-mha cluster one-key deployment method of claim 3, wherein the step of S3 for configuring master library connections to a database comprises: s31 is used for copying the master-slave IP definition file; s32 is used for copying the master-slave configuration py; s33 is for configuring a master-slave copy and start-up step.
5. The ansable-based mysql-mha cluster one-key deployment method of claim 4, wherein the step of S5 for deployment configuration of mha management nodes comprises: s51 is used for establishing mha files and directories and checking the mha running state; s52 is for manual or automatic control of the step of failover.
6. The ansable-based mysql-mha cluster one-key deployment method of claim 1, wherein the step of S6 for node deployment monitoring comprises: s61, a step for constructing a deployment environment; s62 is used for copying the tool and script in the program package; s63 is a step for writing a timed task.
7. The ansable-based mysql-mha cluster one-key deployment method as claimed in any of claims 1 to 6, further comprising: s7 is a step for creating a backup directory and a script directory and making a copy.
8. An ansable-based mysql-mha cluster one-key deployment system, comprising: a module for installing a mysql database at a server; a module for creating an account in the master repository and configuring the master node; a module for configuring a master library connection to a database; a module for deployment configuration of mha base nodes; a module for deployment configuration of mha management nodes; and the module is used for monitoring the node deployment.
9. The ansable-based mysql-mha cluster key deployment system of claim 8, wherein the module for installing a mysql database at a server comprises: a submodule for creating users, user groups and directories; a submodule for decompressing the installation package and copying the installation package to the specified directory; the submodule is used for inquiring the original database and backing up the database and is used for acquiring a new software source submodule; and the submodule is used for logging in the database, configuring the user and setting the authority of the user.
10. The ansable-based mysql-mha cluster key deployment system of claim 9, wherein the modules for creating accounts at a master repository and configuring master nodes comprise: a sub-module for creating and authorizing a user.
11. The ansable-based mysql-mha cluster key deployment system of claim 10, wherein the module for configuring master library connections for a database comprises: a submodule for copying master-slave IP definition files; a submodule for copying the master-slave configuration py; and the submodule is used for configuring master-slave copy and starting.
12. The ansable-based mysql-mha cluster one-key deployment system of claim 11, wherein the modules for deployment configuration of mha management nodes comprise: a submodule for creating mha files and directories and checking mha the running status; a submodule for manually or automatically controlling failover.
13. The ansable-based mysql-mha cluster key deployment system of claim 12, wherein the means for node deployment monitoring comprises: a submodule for setting up a deployment environment; a submodule for copying tools and scripts in the package; a submodule for writing timing tasks.
14. The ansable-based mysql-mha cluster key deployment system of any of claims 8 to 13, further comprising: and a module for creating and copying the backup directory and the script directory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010805534.7A CN112084170A (en) | 2020-08-12 | 2020-08-12 | Ansable-based mysql-mha cluster one-key deployment method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010805534.7A CN112084170A (en) | 2020-08-12 | 2020-08-12 | Ansable-based mysql-mha cluster one-key deployment method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112084170A true CN112084170A (en) | 2020-12-15 |
Family
ID=73727869
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010805534.7A Withdrawn CN112084170A (en) | 2020-08-12 | 2020-08-12 | Ansable-based mysql-mha cluster one-key deployment method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112084170A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050010926A1 (en) * | 2003-07-11 | 2005-01-13 | Sreedhara Narayanaswamy | System and method for cluster deployment |
| US20050080801A1 (en) * | 2000-05-17 | 2005-04-14 | Vijayakumar Kothandaraman | System for transactionally deploying content across multiple machines |
| US20170180205A1 (en) * | 2015-12-17 | 2017-06-22 | International Business Machines Corporation | Automatic generation of validators to validate deployment code used for configuring servers |
| CN107203617A (en) * | 2017-05-24 | 2017-09-26 | 杭州铭师堂教育科技发展有限公司 | The online migratory systems of mysql and method based on MHA |
| CN110795420A (en) * | 2019-10-30 | 2020-02-14 | 浪潮云信息技术有限公司 | Automatic MySQL database backup method based on infrastructure |
-
2020
- 2020-08-12 CN CN202010805534.7A patent/CN112084170A/en not_active Withdrawn
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050080801A1 (en) * | 2000-05-17 | 2005-04-14 | Vijayakumar Kothandaraman | System for transactionally deploying content across multiple machines |
| US20050010926A1 (en) * | 2003-07-11 | 2005-01-13 | Sreedhara Narayanaswamy | System and method for cluster deployment |
| US20170180205A1 (en) * | 2015-12-17 | 2017-06-22 | International Business Machines Corporation | Automatic generation of validators to validate deployment code used for configuring servers |
| CN107203617A (en) * | 2017-05-24 | 2017-09-26 | 杭州铭师堂教育科技发展有限公司 | The online migratory systems of mysql and method based on MHA |
| CN110795420A (en) * | 2019-10-30 | 2020-02-14 | 浪潮云信息技术有限公司 | Automatic MySQL database backup method based on infrastructure |
Non-Patent Citations (2)
| Title |
|---|
| 5SDBA: ""ansible一键安装mysql8.0", pages 1 - 8, Retrieved from the Internet <URL:https://www.cnblogs.com/5sdba-notes/p/12813302.html> * |
| MRK轻语: "技术论坛搭建项目", pages 1 - 18, Retrieved from the Internet <URL:https://blog.51cto.com/u_13968682/2434176> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110389900B (en) | Distributed database cluster testing method and device and storage medium | |
| CN107450961B (en) | Distributed deep learning system based on Docker container and construction method and working method thereof | |
| CN111614733B (en) | Deployment method, device and storage medium of distributed multi-fragmentation cluster | |
| KR100761551B1 (en) | A method, a controller, an arrangement and a computer program for managing a configuration of clustered computers | |
| EP1460530A2 (en) | Network printer connection update scheme for printer clients | |
| CN110990026B (en) | Automatic deployment method and system for PaaS platform | |
| CN113434158B (en) | Custom management method, device, equipment and medium for big data component | |
| WO2005008935A2 (en) | System and method for cluster deployment | |
| CN115220874B (en) | Kubernetes cluster deployment method, device, equipment and storage medium | |
| US20200293502A1 (en) | Systems and methods for database management system (dbms) discovery | |
| CN112286636B (en) | Implementation method of unified configuration center based on Docker and SVN | |
| Gupta et al. | Deploying hadoop architecture using ansible and terraform | |
| CN112084170A (en) | Ansable-based mysql-mha cluster one-key deployment method and system | |
| CN112114746A (en) | Automatic deployment method of distributed storage cluster | |
| US8015270B2 (en) | Redundant appliance configuration repository in standard hierarchical format | |
| CN116149713A (en) | Program upgrading method and device for all-level equipment under tree-type heterogeneous network | |
| CN113987068A (en) | Automatic configuration method for MySQL group replication cluster based on script | |
| CN115857955A (en) | Method, device and equipment for offline deployment of K8S cluster and storage medium | |
| US20220100615A1 (en) | Method and system for cloning database and associated application | |
| Cisco | Installing the VPN Solutions Center Software | |
| Cisco | Release Notes for Cisco Cable Manager Release 2.0 | |
| CN110362582B (en) | Method and device for realizing zero-shutdown upgrading | |
| CN111966364A (en) | Weblogic automatic environment building method and system based on docker | |
| CN115827009B (en) | Method and system for deploying Ambari based on automation script | |
| CN109783198B (en) | Rapid and automatic construction method for batch big data experiment environment |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20201215 |