Fix old docs listing octavia as experimental
We long ago moved the Octavia role out of experimental status[1] so this patch fixes the old docs comments that list it as such. [1] https://docs.openstack.org/openstack-ansible/queens/contributor/ \ testing.html#maturity-matrix Change-Id: I537275e43ff304c8c3e92f401e687029dada79cd
This commit is contained in:
parent
ea21d76875
commit
8f8bb5681e
@ -22,10 +22,10 @@ debug: False
|
|||||||
octavia_service_setup_host: "{{ openstack_service_setup_host | default('localhost') }}"
|
octavia_service_setup_host: "{{ openstack_service_setup_host | default('localhost') }}"
|
||||||
octavia_service_setup_host_python_interpreter: "{{ openstack_service_setup_host_python_interpreter | default((octavia_service_setup_host == 'localhost') | ternary(ansible_playbook_python, ansible_python['executable'])) }}"
|
octavia_service_setup_host_python_interpreter: "{{ openstack_service_setup_host_python_interpreter | default((octavia_service_setup_host == 'localhost') | ternary(ansible_playbook_python, ansible_python['executable'])) }}"
|
||||||
|
|
||||||
## Octavia standalone (v2) experimental
|
## Octavia standalone (v2)
|
||||||
octavia_v2: True
|
octavia_v2: True
|
||||||
|
|
||||||
## Activate Octavia V1 API
|
## Activate Octavia V1 API (deprecated)
|
||||||
octavia_v1: False
|
octavia_v1: False
|
||||||
|
|
||||||
## Allow TLS listener
|
## Allow TLS listener
|
||||||
|
@ -2,11 +2,6 @@
|
|||||||
Configuring the Octavia Load Balancing service (optional)
|
Configuring the Octavia Load Balancing service (optional)
|
||||||
=========================================================
|
=========================================================
|
||||||
|
|
||||||
.. note::
|
|
||||||
|
|
||||||
This feature is experimental at this time and it has not been fully
|
|
||||||
production tested yet.
|
|
||||||
|
|
||||||
Octavia is an OpenStack project which provides operator-grade Load Balancing
|
Octavia is an OpenStack project which provides operator-grade Load Balancing
|
||||||
(as opposed to the namespace driver) by deploying each individual load
|
(as opposed to the namespace driver) by deploying each individual load
|
||||||
balancer to its own virtual machine and leveraging haproxy to perform the
|
balancer to its own virtual machine and leveraging haproxy to perform the
|
||||||
|
Loading…
x
Reference in New Issue
Block a user