Add read_affinity and write_affinity swift settings

Bug #1415172 reported by Nolan Brubaker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
High
Andy McCrae
Kilo
Fix Released
High
Andy McCrae
Trunk
Fix Released
High
Andy McCrae

Bug Description

For a given proxy node, the read_affinity and write_affinity variables should be present so that an existing region can be specified for that proxy to use.

Revision history for this message
Nolan Brubaker (nolan-brubaker) wrote :
no longer affects: openstack-ansible/next
no longer affects: openstack-ansible/juno
Revision history for this message
Darren Birkett (darren-birkett) wrote :
Changed in openstack-ansible:
status: Confirmed → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

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

commit c1634b2e328af1bd5c535d750bd60d09d649d3c0
Author: Andy McCrae <email address hidden>
Date: Fri Jun 12 12:47:49 2015 +0100

    Add read/write_affinity settings for Swift

    Allow the setting of read/write_affinity and write_affinity_node_count
    on a per proxy_host basis.

    This allows the deployer to set preferences for which region to
    read/write to, which can increase the efficiency of a multi-region
    swift cluster.

    Sample swift.yml has been updated, as well as the aio swift.yml to
    ensure these settings are setup as part of the gate, but this shouldn't
    change the functionality of swift at all (since there is only 1 region).

    Change-Id: I95b456672f419fcc331d6739ce259b022d350472
    Closes-Bug: #1415172
    (cherry picked from commit 5b9b49f52b12052f93c72f44a31a972f2e98620c)

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

Remote bug watches

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