Since we moved all functionality of galera-client part to galera-server
role there's no sense in futher keeping and branching of client part.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/765777
Change-Id: I1623dbc80bee4eb7d889ee570d0ce27697b58cea
In certain use cases, you may be listening on a different interface
and it is not possible to listen to multiple interfaces with MySQL.
This changes the behaviour to connect via the local socket, as
Galera treats 'localhost' as a connection via the UNIX socket and
'127.0.0.1' as using the TCP socket.
This will allow using Galera on a specific interface while still
letting the bootstrap process talk to the local machine via the
socket which is still available.
Change-Id: Ib46f91e0a6becc934984d372bc51fc2aa77a0c95
If the galera_client role is templating its config file on a galera
server host it should always use a localhost address.
Change-Id: I468b171c1e72697ea6450fe08aa0acb3faf91201
Add a dependency on the apt_package_pinning role and use it, instead of a
template within this role, to pin the MariaDB repo.
Change-Id: I26111d7191db793b9cddca29c681399040ab6011
Dmitriy Rabotyagov