Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
2025-4, 2025-5
Description
Python dependencies of burza are installed using Poetry, but all the other parts (like MariaDB connector/node exporter/flame graphs/perf and its kernel modules) are not covered by any automated process.
There is also a buildbot task that runs burza on hetzner servers, but there are some problems with it:
- allocation of VMs and their provisioning is inseparable. You cannot allocate VMs once and then develop on them, updating the sources
- there is no direct access to these VMs, only thru jump hosts, which complicates the development
- task itself is run in Buildbot. So for every change one has to create a PR, wait for review, then run it
- buildbot tasks are not a standard tech. It is not available outside of the company. So for example Tempesta had to implement their own Ansible provisioning. If burza becomes open source in the future, we'll also need some standard tech for deployment
So I propose using https://github.com/mariadb-corporation/columnstore-ansible-aws (Terraform + Ansible, the project is open) as a base to add deployment of burza using Ansible
Attachments
Issue Links
- relates to
-
MCOL-6060 Update process of running multiburza
-
- Closed
-