File tree Expand file tree Collapse file tree 1 file changed +23
-0
lines changed Expand file tree Collapse file tree 1 file changed +23
-0
lines changed Original file line number Diff line number Diff line change 2
2
Octavia
3
3
=======
4
4
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
+
5
28
.. _Amphora image :
6
29
7
30
Building and rotating amphora images
You can’t perform that action at this time.
0 commit comments