You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/source/operations/octavia.rst
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,12 @@ Octavia
7
7
Introduction to Octavia
8
8
=======================
9
9
10
-
Octavia is known as an *operator-scaled* load balancing service.
10
+
Octavia is known as an *operator-scaled* load balancing service, whose primary goal is to
11
+
distribute incoming network traffic, destined for a single VM, across multiple VMs instead;
12
+
thus preventing overloading the VM and improving the overall performance of the VM's outbound
13
+
service.
14
+
15
+
For more information on Octavia, please refer to the `official documentation <https://docs.openstack.org/octavia/latest/reference/introduction.html>`_.
11
16
12
17
.. _Deploying Octavia:
13
18
@@ -18,21 +23,24 @@ Much like any other Kolla managed service, the method of deploying Octavia is as
18
23
as enabling ``kolla_enable_octavia: true`` within the chosen environment's ``kolla.yml``.
19
24
However, before running a ``kayobe overcloud service configure``, check
20
25
``octavia_net_interface`` (often found within the ``controllers`` directory within
21
-
``group_vars``) to see the network which Octavia management network will be using.
22
-
If it is configured to use a VLAN then ``kolla_enable_neutron_provider_networks: true``
26
+
``${KAYOBE_CONFIG_PATH}/inventory/group_vars``) to see the network which Octavia management
27
+
network will be using. If it is configured to use a VLAN then ``kolla_enable_neutron_provider_networks: true``
23
28
should also be set in ``kolla.yml``.
24
29
25
30
.. note::
26
31
27
32
It of course goes without saying that the network configured for ``octavia_net_interface``
28
33
should also exist in ``networks.yml``.
29
34
30
-
By default Octavia will deploy a single Amphora VM per load balancing service, this should be
35
+
By default Octavia will deploy an Amphorae (a single Amphora VM) per load balancing service, this should be
31
36
changed to make them highly available and have two Amphora VM per service. Done by setting
32
37
``octavia_loadbalancer_topology: "ACTIVE_STANDBY"`` in ``${KAYOBE_CONFIG_PATH}/kolla/globals.yml``,
33
38
this will ensure that if the master Amphora VM were to go down, the other would be able to
34
39
take over the load balancing functions.
35
40
41
+
Further configuration options and details on installation can be found in the
0 commit comments