Skip to content

Commit 6cf2b02

Browse files
authored
Update octavia.rst
Updating the Octavia docs to explain how to deploy it, alongside other important settings.
1 parent a22c955 commit 6cf2b02

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

doc/source/operations/octavia.rst

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,29 @@
22
Octavia
33
=======
44

5+
.. _Deploying Octavia:
6+
7+
Deploying Octavia
8+
=================
9+
10+
Much like any other Kolla managed service, the method of deploying Octavia is as simple
11+
as enabling ``kolla_enable_octavia: true`` within the chosen environment's ``kolla.yml``.
12+
However, before running a ``kayobe overcloud service configure``, check
13+
``octavia_net_interface`` (often found within the ``controllers`` directory within
14+
``group_vars``) to see the network which Octavia management network will be using.
15+
If it is configured to use a VLAN then ``kolla_enable_neutron_provider_networks: true``
16+
should also be set in ``kolla.yml``.
17+
18+
.. note::
19+
20+
It of course goes without saying that the network configured for ``octavia_net_interface``
21+
should also exist in ``networks.yml``.
22+
23+
By default Octavia will deploy a single Amphora VM per load balancing service, this should be
24+
changed to make them highly available and have two Amphora VM per service. Done by setting
25+
``octavia_loadbalancer_topology: "ACTIVE_STANDBY"``, this will ensure that if an Amphora VM
26+
were to go down, the other would be able to take over the load balancing functions.
27+
528
.. _Amphora image:
629

730
Building and rotating amphora images

0 commit comments

Comments
 (0)