openstack/openstack-ansible-os_octavia
Code Issues Proposed changes

Merge "Change defaults for octavia topology and affinity"

Browse Source
This commit is contained in:
Zuul 2022-12-12 18:25:08 +00:00 committed by Gerrit Code Review
commit 910128fa7c
2 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
defaults/main.yml
View File

@ -251,8 +251,7 @@ octavia_required_secrets:
## Octavia configs ## Octavia configs
# Load balancer topology options are SINGLE, ACTIVE_STANDBY # Load balancer topology options are SINGLE, ACTIVE_STANDBY
# ACTIVE_STANDBY is recommended for production settings octavia_loadbalancer_topology: ACTIVE_STANDBY
octavia_loadbalancer_topology: SINGLE
# Image tag for the amphora image in glance # Image tag for the amphora image in glance
octavia_glance_image_tag: octavia-amphora-image octavia_glance_image_tag: octavia-amphora-image
@ -320,8 +319,7 @@ octavia_neutron_oslomsg_rpc_password: "{{ neutron_oslomsg_rpc_password }}"
# this controls if Octavia should add an anti-affinity hint to make sure # this controls if Octavia should add an anti-affinity hint to make sure
# two amphora are not placed pn the same host (the most common setup of # two amphora are not placed pn the same host (the most common setup of
# ant affinity features in Nova). # ant affinity features in Nova).
# Since AIO only has one compute host this is set to false octavia_enable_anti_affinity: True
octavia_enable_anti_affinity: False
# Some installations put hardware more suited for load balancing in special # Some installations put hardware more suited for load balancing in special
# availability zones. This allows to target a specific availability zone # availability zones. This allows to target a specific availability zone

8
releasenotes/notes/octavia_default_topology-91f574bbaed85249.yaml Normal file
View File

@ -0,0 +1,8 @@
---
upgrade:
- |
Default values for variables ``octavia_loadbalancer_topology`` and
``octavia_enable_anti_affinity`` has been switched to ``ACTIVE_STANDBY``
and ``True`` accordingly to reflect most reasonable production setup.
You can define these variables to their previous defaults if you want
to preserve behaviour.