dbbot Repository Layout and Components

dbbot maintains multiple automation capabilities through a single GitHub repository. Although external documents are displayed by MySQL, ClickHouse, and Prometheus partitions, these capabilities belong to the same publishing unit at the repository level.

1. Top-level directory

Typical installation path:

/usr/local/dbbot

Common directories:

  • mysql_ansible: MySQL / Percona / GreatSQL deployment and operations scripts.
  • clickhouse_ansible: ClickHouse cluster deployment, backup, restore, and operations scripts.
  • monitoring_prometheus_ansible: Prometheus, Grafana, Alertmanager and exporter related scripts.
  • portable-ansible-v0.5.0-py3: Green version of Ansible runtime.
  • docs: Hugo document content in the site source code repository; the running directory is usually maintained separately by the official website.
  • mysql_ansible is responsible for the core OLTP delivery of MySQL ecosystem.
  • clickhouse_ansible is responsible for MySQL downstream OLAP scenarios.
  • monitoring_prometheus_ansible is responsible for supporting monitoring capabilities.
  • portable-ansible-* provides a unified execution environment for the above scripts.

3. Relationship between versions and releases

  • GitHub Releases is for the entire dbbot repository version.
  • A release version number corresponds to a set of repository contents, rather than a separate release of a separate subdirectory.
  • In a production environment, it is recommended to always deploy the complete release package to avoid subdirectory version inconsistencies.

4. Related document entry