Before You Start: Where to Install dbbot

dbbot is recommended to be installed on a control node with network-wide communication capabilities. The control node will uniformly execute mysql_ansible, clickhouse_ansible and monitoring related playbooks.

  • Production environment: Prioritize deployment on springboard machines, operations nodes or monitoring nodes.
  • Test environment: can be reused with any database host.
  • When managing MySQL and ClickHouse at the same time: the control node needs to access the database node, ClickHouse node and ZooKeeper / Keeper node at the same time.

MySQL scenario example

Take MySQL MGR as an example:

  • Minimum machine requirements: at least 3 database hosts, it is recommended to prepare 1 control node separately to deploy dbbot.
  • If there are no additional control nodes, dbbot can also be temporarily deployed on the first MySQL host.

ClickHouse scenario example

Take the ClickHouse cluster as an example:

  • It is recommended to prepare a separate 1 control node to perform deployment, backup and recovery in a unified manner.
  • In cluster mode, the control node needs to access the clickhouse_deploy group and zookeeper_deploy / clickhouse_keeper related nodes.
  • If you only perform single-node validation, you can also directly deploy dbbot on the experimental host and execute deploy_single.yml.

General restrictions

  1. Before each deployment, confirm that the target host port, directory, and disk planning are as expected.
  2. It is recommended to unify the operating system, time zone and software directory layout within the same topology.
  3. Before executing high-risk scripts, check the inventory, variable files, and target environment range.

Next chapter: Download dbbot