History

Kevin Carter 886fe01edb Add release pinning to galera roles

As both Ubuntu and the MariaDB repositories carry packages with the same
names, apt package pinning is required to ensure that the packages we install
come from the right repository. This patch adds a pinning preference file to
ensure that the packages we install come from the MariaDB repository.

Due to the OpenStack CI images having conflicting packages installed in the
base image, this patch also includes the removal of these packages during the
AIO bootstrap to ensure that the deployment succeeds.

For environments where the same two packages are installed on the hosts prior
to the deployment of os-ansible-deployment, they would need to ensure that the
packages are removed first. This has been seen in environments where
monitoring tooling has installed the packages as a dependancy.

Closes-Bug: #1446772
Change-Id: I5ad0b9010e49832c4f866c0b141e1c035d5f9268

2015-04-23 10:32:35 +01:00

defaults

Add release pinning to galera roles

2015-04-23 10:32:35 +01:00

README.rst

OpenStack Galera Client

tags: openstack, galera, client, cloud, ansible
category: *nix

Role for the installation of the mariadb and xtrabackup clients used to interact with and manage a galera cluster.

Example Ansible play

- name: Install galera server
  hosts: galera_all
  user: root
  roles:
    - { role: "galera_server", tags: [ "galera-server" ] }
  vars:
    galera_address: "10.0.0.1"
    galera_root_password: secrete
    galera_root_user: root