Introduction

1. What is dbbot?

dbbot is a collection of Ansible Playbooks for the MySQL ecosystem, used to automatically deliver production-level MySQL, Percona, and GreatSQL, as well as their supporting ClickHouse OLAP scenarios and common monitoring components.

Project release and issue tracking:

The current public documents mainly cover:

  • MySQL 5.7 / 8.0 / 8.4
  • GreatSQL 8.0
  • ClickHouse cluster deployment, backup, restore, and operations
  • Prometheus monitoring access

2. What is included in the dbbot repository?

dbbot uses a single GitHub repository to maintain multiple sub-capabilities. Common directories include:

  • mysql_ansible: MySQL/Percona/GreatSQL related scripts
  • clickhouse_ansible: ClickHouse cluster, backup, and restore related playbooks
  • monitoring_prometheus_ansible: Prometheus/Grafana/Alertmanager related scripts
  • portable-ansible-v0.5.0-py3: portable Ansible distribution

3. Concept of dbbot

  • Efficient: Concurrently distribute installation packages and execute deployment concurrently.
  • Elegance: Try to use Ansible’s built-in capabilities to reduce additional environment intrusions.
  • Specifications: Solidify the deployment specifications into the Playbook to reduce the manual steps of word-of-mouth communication.

4. Main problems solved by dbbot

  1. Unify the delivery method of infrastructure related to the MySQL ecosystem.
  2. Incorporate supporting capabilities such as OLTP, OLAP, and monitoring into the same repository and release rhythm.
  3. Reduce the risks caused by environmental drift and manual operation differences.

5. Roadmap: From Playbook to AI Agent

The short-term goal of dbbot is not to be a chat-only tool, but to first polish the core actions of dbbot for MySQL into a stable execution base.

Roadmap is roughly divided into three steps:

  1. Solidify the deterministic processes such as deployment, backup, recovery, and monitoring in the MySQL ecosystem.
  2. On this basis, reusable skills are accumulated to make high-frequency actions composable and auditable.
  3. Finally introduce AI agent to generate plans through natural language and call skills and underlying Playbook for execution.

This means that future natural language portals will be built on the existing script system, rather than bypassing the script and directly executing commands.

ClickHouse document entry: ClickHouse

Roadmap details: Roadmap

Next chapter: Before you begin: Where is dbbot installed