One small correction to the above description is that it actually requires two failures to trigger a failover but after a single failure it then requires two successive successes in order for a failure to be prevented. This is as per the static configuration from Neutron [1]. It is also worth noting that there is a plan upstream to make the keepalived config configurable so that e.g. the charms could define the healthcheck test to be whatever it deems appropriate [2][3]
One small correction to the above description is that it actually requires two failures to trigger a failover but after a single failure it then requires two successive successes in order for a failure to be prevented. This is as per the static configuration from Neutron [1]. It is also worth noting that there is a plan upstream to make the keepalived config configurable so that e.g. the charms could define the healthcheck test to be whatever it deems appropriate [2][3]
[1] https:/ /github. com/openstack/ neutron/ blob/3cbe340846 cb00e542afbad23 8207186cc22a858 /neutron/ agent/linux/ keepalived. py#L547 /bugs.launchpad .net/neutron/ +bug/1892200 /review. opendev. org/c/openstack /neutron/ +/759886/
[2] https:/
[3] https:/