From d68844ede5930fe0813434e80829484b44681c1e Mon Sep 17 00:00:00 2001
From: Mihail Avram <mihail.avram@garr.it>
Date: Tue, 27 May 2025 12:31:00 +0200
Subject: [PATCH] sposta Create an Openstack Load Balancer nei tutorial +
alcune modifiche
---
.../kb/openstack => compute/images}/lb0.png | Bin
.../kb/openstack => compute/images}/lb1.png | Bin
.../kb/openstack => compute/images}/lb2.png | Bin
.../kb/openstack => compute/images}/lb3.png | Bin
.../kb/openstack => compute/images}/lb4.png | Bin
.../kb/openstack => compute/images}/lb5.png | Bin
.../kb/openstack => compute/images}/lb6.png | Bin
.../kb/openstack => compute/images}/lb7.png | Bin
.../kb/openstack => compute/images}/lb8.png | Bin
.../lbaas_services_tutorial.rst | 30 +++++++++---------
web/doc/tutorials/index.rst | 1 +
11 files changed, 16 insertions(+), 15 deletions(-)
rename web/{support/kb/openstack => compute/images}/lb0.png (100%)
rename web/{support/kb/openstack => compute/images}/lb1.png (100%)
rename web/{support/kb/openstack => compute/images}/lb2.png (100%)
rename web/{support/kb/openstack => compute/images}/lb3.png (100%)
rename web/{support/kb/openstack => compute/images}/lb4.png (100%)
rename web/{support/kb/openstack => compute/images}/lb5.png (100%)
rename web/{support/kb/openstack => compute/images}/lb6.png (100%)
rename web/{support/kb/openstack => compute/images}/lb7.png (100%)
rename web/{support/kb/openstack => compute/images}/lb8.png (100%)
rename web/{support/kb/openstack => compute}/lbaas_services_tutorial.rst (79%)
diff --git a/web/support/kb/openstack/lb0.png b/web/compute/images/lb0.png
similarity index 100%
rename from web/support/kb/openstack/lb0.png
rename to web/compute/images/lb0.png
diff --git a/web/support/kb/openstack/lb1.png b/web/compute/images/lb1.png
similarity index 100%
rename from web/support/kb/openstack/lb1.png
rename to web/compute/images/lb1.png
diff --git a/web/support/kb/openstack/lb2.png b/web/compute/images/lb2.png
similarity index 100%
rename from web/support/kb/openstack/lb2.png
rename to web/compute/images/lb2.png
diff --git a/web/support/kb/openstack/lb3.png b/web/compute/images/lb3.png
similarity index 100%
rename from web/support/kb/openstack/lb3.png
rename to web/compute/images/lb3.png
diff --git a/web/support/kb/openstack/lb4.png b/web/compute/images/lb4.png
similarity index 100%
rename from web/support/kb/openstack/lb4.png
rename to web/compute/images/lb4.png
diff --git a/web/support/kb/openstack/lb5.png b/web/compute/images/lb5.png
similarity index 100%
rename from web/support/kb/openstack/lb5.png
rename to web/compute/images/lb5.png
diff --git a/web/support/kb/openstack/lb6.png b/web/compute/images/lb6.png
similarity index 100%
rename from web/support/kb/openstack/lb6.png
rename to web/compute/images/lb6.png
diff --git a/web/support/kb/openstack/lb7.png b/web/compute/images/lb7.png
similarity index 100%
rename from web/support/kb/openstack/lb7.png
rename to web/compute/images/lb7.png
diff --git a/web/support/kb/openstack/lb8.png b/web/compute/images/lb8.png
similarity index 100%
rename from web/support/kb/openstack/lb8.png
rename to web/compute/images/lb8.png
diff --git a/web/support/kb/openstack/lbaas_services_tutorial.rst b/web/compute/lbaas_services_tutorial.rst
similarity index 79%
rename from web/support/kb/openstack/lbaas_services_tutorial.rst
rename to web/compute/lbaas_services_tutorial.rst
index fa49bae1..2ab36dd8 100644
--- a/web/support/kb/openstack/lbaas_services_tutorial.rst
+++ b/web/compute/lbaas_services_tutorial.rst
@@ -47,52 +47,52 @@ Create a new Load Balancer (Openstack Dashboard)
1. Select **"Load Balancers"** from the menu and select **"+ Create Load Balancer"**.
- .. image:: lb1.png
+ .. image:: images/lb1.png
:width: 600
-2. Name the new **load balancer** and select the subnet (must be the same subnet of the VMs "default" or user defined).
+2. Name the new **load balancer** and select the subnet (must be the same subnet of *test-vm-1* and *test-vm-2*).
- .. image:: lb2.png
+ .. image:: images/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 (HTTP/80 in our case) the load balancer should listen to.
- .. image:: lb3.png
+ .. image:: images/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 connection requests arrive.
- .. image:: lb4.png
+ .. image:: images/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 (*test-vm-1* and *test-vm-2* in our case) to the new **pool**, and for each select the subnet IP and the port (80 in our case) of the service running on that host.
- .. image:: lb5.png
+ .. image:: images/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 (HTTP in our case) to monitor on each member host. Click on **Create Load Balancer** to finish.
- .. image:: lb6.png
+ .. image:: images/lb6.png
:width: 600
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
+ .. image:: images/lb7.png
:width: 600
8. Assign a *Floating IP* to the new load balancer.
- .. image:: lb8.png
+ .. image:: images/lb8.png
:width: 600
**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
+**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 default or 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
+.. image:: images/lb0.png
:width: 600
diff --git a/web/doc/tutorials/index.rst b/web/doc/tutorials/index.rst
index 5df1a363..73a83af3 100644
--- a/web/doc/tutorials/index.rst
+++ b/web/doc/tutorials/index.rst
@@ -13,6 +13,7 @@ Quick Start Guides
- `Quick Start Guide to VM <../../compute/quick-vm>`_
- `Quick Start Guide to Virtual Datacenters <../../compute/quick-vdc>`_
+- `Quick Start Guide to Load Balancers <../../compute/lbaas_services_tutorial>`_
`OpenStack` Command Line Interface
--
GitLab