Removing spare_amphora_pool_size option
Victoria and future releases going to deprecate this option. https://docs.openstack.org/octavia/latest/configuration/configref.html#house_keeping.spare_amphora_pool_size Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/765544 Change-Id: I99425c9b65c6327636a94c00b32545553a705611
This commit is contained in:
parent
58a9f7b62f
commit
1be636c5ab
@ -265,9 +265,6 @@ octavia_amp_vcpu: 1
|
||||
octavia_amp_disk: 20
|
||||
#octavia_amp_extra_specs:
|
||||
|
||||
# spare pool - increase to speed up load balancer creation and fail over
|
||||
octavia_spare_amphora_pool_size: 1
|
||||
|
||||
# only increase when it's a really busy system since this is by deployed host,
|
||||
# e.g. 3 hosts, 5 workers (this param) per host, results in 15 worker total
|
||||
octavia_task_flow_max_workers: 5
|
||||
|
@ -221,10 +221,3 @@ by adding ``octavia_loadbalancer_topology: ACTIVE_STANDBY`` and
|
||||
``octavia_enable_anti_affinity=True`` to ensure that the active and passive
|
||||
amphora are (depending on the anti-affinity filter deployed in nova) on two
|
||||
different hosts to the user file in /etc/openstack-deploy
|
||||
|
||||
To speed up the creation of load balancers or in a SINGLE topolgy
|
||||
to speed up the failover a spare pool can be used.
|
||||
The variable ``octavia_spare_amphora_pool_size`` controls
|
||||
the size of the pool. The system will try
|
||||
to prebuild this number so using too big a number will
|
||||
consumes a lot of unnecessary resources.
|
||||
|
@ -114,9 +114,6 @@ loadbalancer_topology = {{ octavia_loadbalancer_topology }}
|
||||
# engine = serial
|
||||
max_workers = {{ octavia_task_flow_max_workers }}
|
||||
|
||||
[house_keeping]
|
||||
spare_amphora_pool_size = {{ octavia_spare_amphora_pool_size }}
|
||||
|
||||
|
||||
[service_auth]
|
||||
insecure = {{ keystone_service_internaluri_insecure | bool }}
|
||||
|
Loading…
Reference in New Issue
Block a user