Codership is pleased to announce a new release of Galera Manager. This brings the installer to version 1.5 and the actual Galera Manager GUI to 1.4.0.
Users will notice some usability improvements like the cluster name being added to the authorized_keys
generated file, while there are benefits around gmd
generating a new key for the updated installation. There is also a port checker, so if ports are used and unavailable, the user will be informed and Galera Manager will refuse to install. In addition, on Debian/Ubuntu where apt/dpkg supports interactivity, we have now ensured that all steps will remain non-interactive.
We now have native support to deploy MariaDB Server 10.6
From the Galera Manager GUI standpoint, we have ensured that job monitoring and charts have better performance. One user experience enhancement for monitored or self-hosted clusters? Galera Manager now checks to ensure it has access to the nodes before it decides to continue (very much like how it does so with AWS). While we are on the topic of AWS, the user experience around EC2 deployment configuration, is also improved.
Sizing guides are common database practice, and while less common in the MySQL world, we do have a maximum expected database size field now, for the cluster. In addition, there have been improvements in the deployment logs display, as well as the last transaction number executed on nodes.
Please download Galera Manager
and we look forward to your feedback.
- Fix the Ubuntu AWS image path template (to avoid picking up a wrong image)
- Fix form validation issues
- unable to create new cluster if cluster configuration is open in the background
- unable to add a new node if node configuration is open in the background
- Fix copy button issue
- now display a message to user if copy is not working because the application is not served over HTTPS
- Fix node state display if there are multiple nodes with same name