From 343dd996450f4d3c2af4d1f71b0efd1066f6fdae Mon Sep 17 00:00:00 2001
From: Mihail Avram <mihail.avram@garr.it>
Date: Tue, 27 May 2025 09:01:35 +0200
Subject: [PATCH] fix load balancer doc typos
---
.../kb/openstack/lbaas_services_tutorial.rst | 27 ++++++++++---------
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/web/support/kb/openstack/lbaas_services_tutorial.rst b/web/support/kb/openstack/lbaas_services_tutorial.rst
index 551ac5e..fa49bae 100644
--- a/web/support/kb/openstack/lbaas_services_tutorial.rst
+++ b/web/support/kb/openstack/lbaas_services_tutorial.rst
@@ -12,12 +12,6 @@ Create a new security group that enables network traffic on port 80 and associat
Create and associate a floating IP to each VM.
-**Note**: If the service is not visible from the Internet (0.0.0.0/0) create a security group that enables ingress traffic from the private
-network of the VM's otherwise the Load Balancer will not be able to forward the requests to the worker VMs. In this case the CIDR of the security group rule
-is the network IP.
-
-.. image:: lb0.png
- :width: 600
Run a simple web server
@@ -51,37 +45,37 @@ Create a new Load Balancer (Openstack CLI)
Create a new Load Balancer (Openstack Dashboard)
---------------
-1. Select **Load Balancers** from the menu and select **+ Create Load Balancer**.
+1. Select **"Load Balancers"** from the menu and select **"+ Create Load Balancer"**.
.. image:: lb1.png
:width: 600
-2. Name the new load balancer and select the subnet (must be the same subnet of the VM's).
+2. Name the new **load balancer** and select the subnet (must be the same subnet of the VMs "default" or user defined).
.. image:: lb2.png
:width: 600
-3. Create a listener and select the protocol/port the load balancer listens to.
+3. Create a **listener** and select the protocol/port the load balancer listens to.
.. image:: lb3.png
:width: 600
-4. Create a worker pool and select a load balancer algorithm. The choosen algorithm determines how the workload is distributed among members when new requests arrive.
+4. Create a worker **pool** and select a load balancer algorithm. The choosen algorithm determines how the workload is distributed among members when new requests arrive.
.. image:: lb4.png
:width: 600
-5. Add members to the new pool, and for each member select the interface and the port of the service running on that host.
+5. Add members to the new **pool**, and for each member select the interface and the port of the service running on that host.
.. image:: lb5.png
:width: 600
-6. Create a monitor and select the type of service to monitor. Click on **Create Load Balancer** to finish.
+6. Create a **monitor** and select the type of service to monitor. Click on **Create Load Balancer** to finish.
.. image:: lb6.png
:width: 600
-7. Wait until load balancer *Operating Status* becomes Online. If a member is unreachable to the load balancer *Operating Status* turns to *Degraded*, in that case the requests are routed to the remaining members.
+7. Wait until the **load balancer** *Operating Status* becomes Online. If a member is unreachable to the load balancer *Operating Status* turns to *Degraded*, in that case the requests are routed to the remaining members.
.. image:: lb7.png
:width: 600
@@ -94,6 +88,13 @@ Create a new Load Balancer (Openstack Dashboard)
**Note**: now it is possibile to remove the floating ips from the two VMs.
+**Note**: If the service should not be visible from the Internet (0.0.0.0/0) create a security group that enables ingress traffic from your custom
+network and associate it to the VMs otherwise the load balancer will not be able to forward the requests to it's members. The CIDR of the security group rule
+is the network IP (if you use the "default" network it's 192.168.0.0/16).
+
+.. image:: lb0.png
+ :width: 600
+
Test the Load Balancer
-----------
--
GitLab