Comment 2 for bug 1449958

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (master)

Reviewed: https://review.openstack.org/200054
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=4a860f715c21be26b5b4e92f0d9f75e665015469
Submitter: Jenkins
Branch: master

commit 4a860f715c21be26b5b4e92f0d9f75e665015469
Author: git-harry <email address hidden>
Date: Wed Jul 8 10:31:45 2015 +0100

    Restart mysql when config changed

    Currently mysql is only (re)started when creating a cluster, adding a
    node or the service isn't running. This means changes to configuration
    files are not used.

    This commit moves the restart functionality to a handler and sets
    notifies on the the appropriate tasks so that when the config is changes
    mysql is restarted.

    This commit modifies the galera play to run in serial so that only one
    instance of mysql can be restarted at a time. This is to prevent the
    possibility of them all being restarted in one go. An additional play
    'Check galera cluster status' has been added, this makes an attempt to
    check that the cluster is healthy before proceeding with any possible
    config changes. The checks can be overridden by setting
    'galera_ignore_cluster_state=true' when running the playbook.

    A facts module has been added to gather information about the status of
    the cluster for use by the galera-install playbook.

    DocImpact
    Closes-bug: #1449958

    Change-Id: Id83ba642c114d1f5cac04cc219be151a82a1023f