galera_wsrep_provider_options cannot be customised

Bug #1464699 reported by Jesse Pretorius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Wishlist
Jesse Pretorius
Kilo
Fix Released
Wishlist
Jesse Pretorius
Trunk
Fix Released
Wishlist
Jesse Pretorius

Bug Description

Currently the galera_server role only allows the gcache.size value to be set in wsrep_provider_options. In order to increase the flexibility and allow the implementation of global clusters, the ability to apply more options should be possible

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

Fix proposed to branch: master
Review: https://review.openstack.org/191106

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/194236

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

Reviewed: https://review.openstack.org/194236
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=6142f0f385bf7653e76d5acb3b6afa85a0507539
Submitter: Jenkins
Branch: kilo

commit 6142f0f385bf7653e76d5acb3b6afa85a0507539
Author: Jesse Pretorius <email address hidden>
Date: Fri Jun 12 16:00:50 2015 +0100

    Allow galera wsrep_provider_options to be customised

    This patch introduces galera_wsrep_provider_options as a list of
    options instead of only catering for changing the gcache.size
    option. This allows the deployer to change any number of the
    wsrep_provider_options available.

    Note: The variable galera_gcache_size is respected in this patch
    but if galera_wsrep_provider_options is customised by a deployer
    then the custom list must include reference to galera_gcache_size
    for it to be respected.

    DocImpact
    Closes-Bug: #1464699
    Co-Authored-By: Ian Cordasco <email address hidden>
    Change-Id: I78a5a1d344729fdc06636b1c6dade63a7ba59e94
    (cherry picked from commit 999fc102d11fc64d7140b87e1a246bb196b44f39)

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.