Update the galera_server role and change the mysqlcheck port

This change updates the galera deployment options for kolide which will
allow it to co-exist on the same host as an elasticsearch environment.
Because the galera cluster for kolide is on the backend, and not user
facing the installation and setup of a VIP for the backend galera
cluster is not needed.
Change-Id: Ia5f581ebb028bf35c00dc7606b0eb1a12ad54670
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
Kevin Carter
2019年01月25日 22:11:26 -06:00
parent 82cc72e166
commit 926695fbf1

View File

@@ -15,10 +15,11 @@
scm:git
src:https://git.openstack.org/openstack/openstack-ansible-galera_client
version:master
# Galera server is using a forked role until https://review.openstack.org/#/c/633321/ is merged
- name:galera_server
scm:git
src:https://git.openstack.org/openstack/openstack-ansible-galera_server
version:master
src:https://github.com/os-cloud/openstack-ansible-galera_server
version:xinetd-check
- name:apt_package_pinning
scm:git
src:https://git.openstack.org/openstack/openstack-ansible-apt_package_pinning

View File

@@ -39,5 +39,7 @@
galera_cluster_name:telemetry_galera_cluster
galera_monitoring_allowed_source:"0.0.0.0/0"
galera_root_password:"{{ kolide_galera_root_password }}"
galera_monitoring_check_enabled:false
galera_monitoring_check_port:29200
environment:"{{ deployment_environment_variables | default({}) }}"
Reference in New Issue
openstack/openstack-ansible-ops
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.

The note is not visible to the blocked user.