Hello, It would be extremely hard to detect "reliable" network...if it even exists:) We use autohealing because we also use rabbitmq clusterer plugin, which simplifies recovery from partition. As for hardcoded, one thing I noticed is that these files indeed aren't overridable. I published this bug [1] to fix it.
[1] https://bugs.launchpad.net/kolla-ansible/+bug/1674446 On 20 March 2017 at 07:43, Nikita Gerasimov <nikita.gerasi...@oracle.com> wrote: > Hi, > > Since [1] kolla-ansible have rabbitmq cluster_partition_handling option > hard-coded to 'autoheal'. According to [2] it's not a best mode for 3+ node > clusters with reliable network. > Is it reasonable to make this option changeable by user or even place some > logic to pickup mode based on cluster structure? > Or we have a reason to keep it hard-coded? > > > [1] > https://github.com/openstack/kolla-ansible/commit/0c6594c25864d0c90cd0009726cee84967fe65dc > [2] https://www.rabbitmq.com/partitions.html > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
