DATABASES Signal 407
Autobase 2.10 released
↗
Illustration only Photo by Brecht Corbeel on Unsplash
Autobase 2.10 adds UI-driven cluster actions, a system-settings tab, local-disk deployment, and extra Ansible playbooks for PostgreSQL management.
Operators can now trigger common cluster tasks from the console instead of the command line, reducing manual steps. The expanded configuration UI and local-disk option simplify environment setup and may lower storage costs. New playbooks let existing automation pipelines cover more lifecycle events without custom scripting.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
A new Actions menu in the console lets administrators run switchover, failover, replica reinstall, restart, stop/start, and delete operations directly.
A System tab on the Parameters page exposes advanced settings such as regional options, host mappings, DNS/NTP servers, kernel tweaks, and SSH keys.
Support for deploying PostgreSQL data on the local disk is added, and a suite of Ansible playbooks now automates cluster and node lifecycle tasks.
THE READ
What the cluster adds up to.
The console UI now includes an Actions menu that bundles the most frequent cluster commands. Instead of invoking scripts or CLI tools, operators can click to perform switchover, failover, replica reinstallation, restarts, and even full cluster removal. This reduces the chance of syntax errors and speeds up routine interventions, especially in environments where UI access is the primary control path.
A dedicated System tab on the Parameters page surfaces settings that previously required manual file edits or separate tooling. Administrators can adjust regional preferences, host name mappings, DNS and NTP server entries, kernel parameters, and upload SSH public keys from a single screen. Centralising these knobs simplifies compliance checks and makes it easier to propagate environment-wide changes without touching the underlying OS.
Deploying PostgreSQL data on the local disk is now supported, removing the need for an external network volume in simple setups. To activate this mode, the volume size must be set to zero or the System Disk option selected in Expert Mode. This option is useful for single-node or low-latency deployments but will not apply where storage is provisioned via network-attached devices or where volume sizing is mandatory.
The release bundles a fresh set of Ansible playbooks covering Patroni-based cluster actions, cluster start/stop, and node lifecycle commands. Teams can import these playbooks into existing CI/CD pipelines to automate switchover, failover, reinitialisation, and node restarts without writing custom modules. Adoption requires installing the new Ansible collection and updating inventory files to reference the new playbook names.
All of the new features are part of the Enterprise edition, so environments running the community edition will not see the UI actions or system tab. Additionally, the local-disk deployment only works when the storage configuration permits a zero-size volume or explicit system-disk selection, so clusters that rely on pre-provisioned network storage will continue to use the existing volume model. Organizations must evaluate licensing and storage topology before leveraging the full feature set.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER