From 0df2dab565985ad076924fe0855671c9d33c022d Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 4 Jul 2025 02:56:24 +0200 Subject: [PATCH 1/4] use-lb - update Updated the text to use modern OVHcloud naming conventions where possible. Remaining names and screenshots need to be updated, as soon as the manager is updated to uniformly use the new names. --- .../load_balancer/use-lb/guide.en-gb.md | 37 ++++++++++--------- .../load_balancer/use-lb/guide.fr-fr.md | 11 +++--- 2 files changed, 25 insertions(+), 23 deletions(-) diff --git a/pages/network/load_balancer/use-lb/guide.en-gb.md b/pages/network/load_balancer/use-lb/guide.en-gb.md index 96abc8455b0..9604e214d7c 100644 --- a/pages/network/load_balancer/use-lb/guide.en-gb.md +++ b/pages/network/load_balancer/use-lb/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Managing your Load Balancer service via the Control Panel excerpt: An overview of the main features, and how to get started using the Load Balancer service from the Control Panel -updated: 2017-12-01 +updated: 2025-07-04 --- ## Objective @@ -25,18 +25,18 @@ On this page, you will see the following information: |Element|Purpose| |---|---| -|Status|An overview of your Load Balancer with the IP, front-ends, functional farms and servers added| +|Status|An overview of your Load Balancer with the IP, front-ends, functional clusters and servers added| |Use|A summary of how to use your Load Balancer| |Graphs|In this section, you will see the graphs linked to service, by concurrent connections or requests per minute| -|Information|Your IPv4 address and the Additional IPs linked to them, as well as the number of outgoing IPv4s (see more details by clicking on the ellipses)| -|Configuration|Here, you can customise the name of your solution (which will appear at the top of the left-hand column) The cipher(s) are customisable, as well as the datacentre where your Load Balancer is based| +|Information|Your IPv4 and IPv6 address and the Additional IPs linked to them, as well as the number of outgoing IPv4s (see more details by clicking on the `...`{.action} button)| +|Configuration|Here, you can customise the name of your solution (which will appear at the top of the left-hand column) The cipher(s) are customisable, as well as the availability zones where your Load Balancer is based| |Subscription|Here, you will see the admin details for your solution| -To add `Frontends`{.action} or `Server farms`{.action}, simply click on their respective buttons. A form will then help you configure each part of your solution. +To add `front-ends`{.action} or `Server clusters`{.action}, simply click on their respective buttons. A form will then help you configure each part of your solution. -### Managing frontends +### Managing front-ends -To add front-ends, simply go to the `Frontends`{.action} section, and click `Add a frontend`{.action}. The following menu will then appear: +To add front-ends, simply go to the `Front-ends`{.action} section, and click `Add a front-end`{.action}. The following menu will then appear: ![Add front-end](images/add_frontend.png){.thumbnail} @@ -47,8 +47,8 @@ Details of front-end parts: |Name|If you want, you can choose a name for your front-end. This is very useful when you have several front-ends, so you can tell them apart quickly| |Protocol|You can choose between HTTP, HTTPS, TCP, SSL TCP (or TLS) and UDP| |Port|Choose the listening port you wish to use| -|Datacentre|Choose between your datacentre or all datacentres to create your front-end| -|Default farm|If you have several farms configured, you can choose one of them as a default for each front-end| +|Datacentre|Choose between your availability zone or all availability zones to create your front-end| +|Default cluster|If you have several clusters configured, you can choose one of them as a default for each front-end| You can also access advanced settings: @@ -61,21 +61,21 @@ You can also access advanced settings: |HTTP redirection|Add a HTTP redirection URL| |HTTP header|Add a HTTP header here| -### Managing your farms +### Managing your clusters -To add a server farm, simply go to the `Server farms`{.action} section, and click `Add a server farm`{.action}. You will get the same main options as for the front-end. However, the advanced options are different: +To add a server cluster, simply go to the `Server clusters`{.action} section, and click `Add a server cluster`{.action}. You will get the same main options as for the front-end. However, the advanced options are different: -![Add a farm](images/advanced_cluster.png){.thumbnail} +![Add a cluster](images/advanced_cluster.png){.thumbnail} |Element|Purpose| |---|---| |Distribution method|Choosing between Round-robin, First, Last, Source or URI for your IP load balancing| -|Session tracking|You can track sessions via Cookie or source IP, this can be defined here| +|Track session|You can track sessions via Cookie or source IP, this can be defined here| |Probe|Choosing and activating a probe| ### Managing your servers -Once you have created your server farm, you just need to add servers to it. Details on these options are below, as well as advanced options: +Once you have created your server cluster, you just need to add servers to it. Details on these options are below, as well as advanced options: ![Add server](images/add_server.png){.thumbnail} ![Add server](images/add_server_advanced.png){.thumbnail} @@ -86,11 +86,12 @@ Once you have created your server farm, you just need to add servers to it. Deta |IPv4 address|Adding the IP address of the service that will act as a server| |Port|Server port| |Backup server|Selecting which server is a backup server| -|Use the server farm’s probe|Choosing the probe that was validated when you created the farm| +|Use the server cluster’s probe|Choosing the probe that was validated when you created the cluster| |Encrypt requests with SSL|Encrypting requests with an SSL certificate| |Cookie|Add a customised session cookie| |Certificate chain|Add a certificate chain| -|Balancing load|Choose the balancing load for the load balancer| +|Balancing weight|Choose the balancing weight for the load balancer| +|PROXY Protocol version|**Only if you have configured it**, choose the version of the PROXY protocol you wish to use on the server.
You can find more information on the PROXY protocol and how to use it with the OVHcloud Load Balancer in [this guide](/pages/network/load_balancer/create_proxyprotocol/).| ### Managing SSL certificates You can add an SSL certificate to the Load Balancer in the `SSL Certificate`{.action} section. You have two options: you can order an SSL certificate from OVH, or add an external certificate. @@ -118,6 +119,6 @@ If you already have your own SSL certificate, you can add it directly: |Certificate|Field for adding the certificate| |Chain|Field for adding the root certificate, if required| -## Going further +## Go further -Join our community of users on . \ No newline at end of file +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.fr-fr.md b/pages/network/load_balancer/use-lb/guide.fr-fr.md index ce8763bcc90..447e6ee5757 100644 --- a/pages/network/load_balancer/use-lb/guide.fr-fr.md +++ b/pages/network/load_balancer/use-lb/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: "Gestion du service OVHcloud Load Balancer via l'espace client" excerpt: "Résumé des principales fonctionnalités et prise en main du service Load Balancer via l'espace client OVHcloud" -updated: 2022-04-04 +updated: 2025-07-04 --- ## Objectif @@ -28,8 +28,8 @@ Sur la page de résumé de votre service Load Balancer, vous trouverez les menus |Statut|Résumé de votre Load Balancer avec le nom du service, les frontends, les fermes fonctionnelles et les serveurs ajoutés| |Utilisation|Un récapitulatif de l'utilisation de votre LoadBalancer| |Graphiques|Des graphiques présentant le nombre de connexions simultanées ou le nombre de requêtes par minute| -|Informations|Votre IPv4 et les Additional IP liées, ainsi que le nombre d'IPv4 de sortie (obtenez des détails en cliquant sur le bouton `...`{.action})| -|Configuration|Personnalisez ici le nom de votre offre. Retrouvez aussi le(s) cipher(s), qui sont personnalisables, ainsi que le datacenter où se situe votre Load Balancer| +|Informations|Vos adresses IPv4 et IPv6 et les Additional IP liées, ainsi que le nombre d'IPv4 de sortie (obtenez des détails en cliquant sur le bouton `...`{.action})| +|Configuration|Personnalisez ici le nom de votre offre. Retrouvez aussi le(s) cipher(s), qui sont personnalisables, ainsi que la zone de disponibilité où se situe votre Load Balancer| |Abonnement|Vous trouverez ici les détails administratifs de votre offre| Pour ajouter des `Frontends`{.action} ou des `Fermes de serveurs`{.action}, cliquez simplement sur les onglets respectifs. Un formulaire vous aidera ensuite à configurer chaque partie de votre service. @@ -47,7 +47,7 @@ Détails des éléments d'un frontend : |Nom|Vous pouvez nommer ici votre frontend, afin notamment de l'identifier rapidement si vous en avez plusieurs | |Protocole|Vous avez le choix entre le HTTP, HTTPS, TCP, SSL TCP (ou TLS) et l'UDP| |Port|Choisissez ici le port d'écoute à utiliser| -|Datacenter|Vous pouvez choisir entre un datacenter en particulier ou tous pour la création du frontend| +|Datacenter|Vous pouvez choisir entre une zone de disponibilité en particulier ou tous pour la création du frontend| |Ferme par défaut|Si vous avez plusieurs fermes paramétrées, vous pourrez en choisir une par défaut pour chaque frontend| Vous avez également accès à des paramètres avancés : @@ -91,6 +91,7 @@ Une fois votre ferme de serveurs créée, il vous reste à y ajouter des serveur |Cookie|Ajout d'un cookie de session personnalisé| |Chaîne de certification|Ajout d'une chaîne de certification| |Poids de balancement|Choix du poids de balancement pour la répartition de charge| +|Version du protocole de PROXU|**Uniquement si vous l'avez déjà configuré**, choisissez la version du protocole de PROXY que vous souhaitez utiliser sur ce serveur.
Vous pouvez trouver plus d'informations sur le protocole PROXY et sur son utilisation avec le service OVHcloud Load Balancer dans [ce guide](/pages/network/load_balancer/create_proxyprotocol/).| ### Gérer ses certificats SSL @@ -124,4 +125,4 @@ Si vous possédez déjà votre propre certificat SSL, il vous est possible de l' ## Aller plus loin -Échangez avec notre [communauté d'utilisateurs](/links/community). +Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file From 4d021da9d5db02baf8b01022becc90b481fb5bda Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 4 Jul 2025 15:07:57 +0200 Subject: [PATCH 2/4] farm > cluster Changing all instances of "farm" to "cluster" to respect the naming convention on the manager, except in instances where it would affect the guides' accuracy (file names, API calls, etc). --- .../case_blue_green/guide.en-asia.md | 64 +++--- .../case_blue_green/guide.en-au.md | 64 +++--- .../case_blue_green/guide.en-ca.md | 64 +++--- .../case_blue_green/guide.en-gb.md | 64 +++--- .../case_blue_green/guide.en-sg.md | 64 +++--- .../case_blue_green/guide.en-us.md | 64 +++--- .../load_balancer/case_http2/guide.en-asia.md | 6 +- .../load_balancer/case_http2/guide.en-au.md | 6 +- .../load_balancer/case_http2/guide.en-ca.md | 6 +- .../load_balancer/case_http2/guide.en-gb.md | 6 +- .../load_balancer/case_http2/guide.en-sg.md | 6 +- .../load_balancer/case_http2/guide.en-us.md | 6 +- .../load_balancer/case_smtp/guide.en-asia.md | 46 ++-- .../load_balancer/case_smtp/guide.en-ca.md | 46 ++-- .../load_balancer/case_smtp/guide.en-gb.md | 46 ++-- .../load_balancer/case_smtp/guide.en-sg.md | 46 ++-- .../load_balancer/case_smtp/guide.en-us.md | 46 ++-- .../create_balancing/guide.de-de.md | 34 +-- .../create_balancing/guide.en-asia.md | 46 ++-- .../create_balancing/guide.en-au.md | 46 ++-- .../create_balancing/guide.en-ca.md | 46 ++-- .../create_balancing/guide.en-gb.md | 46 ++-- .../create_balancing/guide.en-sg.md | 46 ++-- .../create_http_https/guide.en-asia.md | 46 ++-- .../create_http_https/guide.en-au.md | 46 ++-- .../create_http_https/guide.en-ca.md | 46 ++-- .../create_http_https/guide.en-gb.md | 50 ++--- .../create_http_https/guide.en-sg.md | 46 ++-- .../create_http_https/guide.en-us.md | 46 ++-- .../create_probes/guide.en-asia.md | 40 ++-- .../create_probes/guide.en-au.md | 40 ++-- .../create_probes/guide.en-ca.md | 2 +- .../create_probes/guide.en-gb.md | 40 ++-- .../create_probes/guide.en-sg.md | 40 ++-- .../create_probes/guide.en-us.md | 40 ++-- .../create_proxyprotocol/guide.en-asia.md | 4 +- .../create_proxyprotocol/guide.en-au.md | 4 +- .../create_proxyprotocol/guide.en-ca.md | 4 +- .../create_proxyprotocol/guide.en-gb.md | 4 +- .../create_proxyprotocol/guide.en-sg.md | 4 +- .../create_proxyprotocol/guide.en-us.md | 4 +- .../create_redirectlocation/guide.en-asia.md | 6 +- .../create_redirectlocation/guide.en-au.md | 6 +- .../create_redirectlocation/guide.en-ca.md | 6 +- .../create_redirectlocation/guide.en-gb.md | 6 +- .../create_redirectlocation/guide.en-sg.md | 6 +- .../create_redirectlocation/guide.en-us.md | 6 +- .../create_route/guide.en-asia.md | 58 ++--- .../load_balancer/create_route/guide.en-au.md | 58 ++--- .../load_balancer/create_route/guide.en-ca.md | 58 ++--- .../load_balancer/create_route/guide.en-gb.md | 58 ++--- .../load_balancer/create_route/guide.en-sg.md | 58 ++--- .../load_balancer/create_route/guide.en-us.md | 58 ++--- .../create_stickiness/guide.en-asia.md | 46 ++-- .../create_stickiness/guide.en-au.md | 46 ++-- .../create_stickiness/guide.en-ca.md | 46 ++-- .../create_stickiness/guide.en-gb.md | 46 ++-- .../create_stickiness/guide.en-sg.md | 46 ++-- .../create_stickiness/guide.en-us.md | 46 ++-- .../howto_route_ipfo/guide.en-asia.md | 6 +- .../howto_route_ipfo/guide.en-au.md | 6 +- .../howto_route_ipfo/guide.en-ca.md | 6 +- .../howto_route_ipfo/guide.en-gb.md | 6 +- .../howto_route_ipfo/guide.en-sg.md | 6 +- .../howto_route_ipfo/guide.en-us.md | 6 +- .../retrieve_servers_state/guide.en-asia.md | 8 +- .../retrieve_servers_state/guide.en-au.md | 8 +- .../retrieve_servers_state/guide.en-ca.md | 6 +- .../retrieve_servers_state/guide.en-gb.md | 8 +- .../retrieve_servers_state/guide.en-sg.md | 8 +- .../retrieve_servers_state/guide.en-us.md | 8 +- .../load_balancer/use-lb/guide.en-asia.md | 136 ++++++------ .../load_balancer/use-lb/guide.en-au.md | 136 ++++++------ .../load_balancer/use-lb/guide.en-ca.md | 136 ++++++------ .../load_balancer/use-lb/guide.en-sg.md | 136 ++++++------ .../load_balancer/use-lb/guide.en-us.md | 136 ++++++------ .../use_api_details/guide.en-asia.md | 210 +++++++++--------- .../use_api_details/guide.en-au.md | 210 +++++++++--------- .../use_api_details/guide.en-ca.md | 210 +++++++++--------- .../use_api_details/guide.en-gb.md | 210 +++++++++--------- .../use_api_details/guide.en-sg.md | 210 +++++++++--------- .../use_api_details/guide.en-us.md | 210 +++++++++--------- .../use_api_reference/guide.en-asia.md | 26 +-- .../use_api_reference/guide.en-au.md | 26 +-- .../use_api_reference/guide.en-ca.md | 26 +-- .../use_api_reference/guide.en-gb.md | 26 +-- .../use_api_reference/guide.en-sg.md | 26 +-- .../use_api_reference/guide.en-us.md | 26 +-- .../use_presentation/guide.en-asia.md | 8 +- .../use_presentation/guide.en-au.md | 8 +- .../use_presentation/guide.en-ca.md | 8 +- .../use_presentation/guide.en-gb.md | 8 +- .../use_presentation/guide.en-sg.md | 8 +- .../use_presentation/guide.en-us.md | 8 +- .../use_presentation/images/diag_gen.png | Bin 63892 -> 68828 bytes .../vrack_and_loadbalancer/guide.en-asia.md | 10 +- .../vrack_and_loadbalancer/guide.en-au.md | 10 +- .../vrack_and_loadbalancer/guide.en-ca.md | 10 +- .../vrack_and_loadbalancer/guide.en-gb.md | 10 +- .../vrack_and_loadbalancer/guide.en-sg.md | 10 +- .../vrack_and_loadbalancer/guide.en-us.md | 10 +- .../load_balancer/zones/guide.en-asia.md | 12 +- .../load_balancer/zones/guide.en-au.md | 12 +- .../load_balancer/zones/guide.en-ca.md | 12 +- .../load_balancer/zones/guide.en-gb.md | 12 +- .../load_balancer/zones/guide.en-sg.md | 12 +- .../load_balancer/zones/guide.en-us.md | 12 +- 107 files changed, 2214 insertions(+), 2224 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.en-asia.md b/pages/network/load_balancer/case_blue_green/guide.en-asia.md index de705cecacc..9fda0eccc6b 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-asia.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-07-04 --- ## Objective @@ -50,13 +50,13 @@ The diagram below gives a general idea of the architecture: ### Infrastructure A. -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server cluster that will later be associated with a front-end of your IP Load Balancer. This cluster will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. -In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. +In our scenario, we will declare a cluster of servers for the HTTP service. Please note that you can create as many clusters (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. #### Via the OVHcloud Control Panel: -![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure A](images/ferme1.png){.thumbnail} #### Via the API: @@ -69,7 +69,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server clusters respectively. > [!api] > @@ -86,11 +86,11 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Associate a server with your cluster, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each cluster (to balance the load and/or offer higher fault tolerance, for ex.). #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} +![Add a new server to the cluster HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} @@ -104,10 +104,10 @@ Associate a server with your farm, if it is a physical server hosting your produ |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77212| +|farmId|Required|Your server cluster ID|77212| |address|Required|Your server's IPv4 address|10.10.1.100| -|displayName||The name of the server associated with your farm|HTTP A server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP A server| +|port||The server port associated with your cluster|8080| With the additional calls listed below, you can list, modify and delete your servers respectively. @@ -128,15 +128,15 @@ With the additional calls listed below, you can list, modify and delete your ser ### Infrastructure B. -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server cluster that will later be associated with a second front-end of your IP Load Balancer. This server cluster exposes the same service to the front-end as the first server cluster. This service is supplied on the servers by port 8080. -Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). +Deploy the server cluster for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). #### Via the Sunrise Control Panel: -![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure B](images/ferme2.png){.thumbnail} -![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} +![Create a second cluster dedicated to infrastructure B](images/backend2.png){.thumbnail} #### Via the API: @@ -149,11 +149,11 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service |---|---| |serviceName|Your Load Balancer service ID| -Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. +Associate a server with your cluster. Here, it involves one or more physical servers hosting your development infrastructure. #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} +![Add a new server to the cluster HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} @@ -167,18 +167,18 @@ Associate a server with your farm. Here, it involves one or more physical server |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77213| +|farmId|Required|Your server cluster ID|77213| |address|Required|Your server's IPv4 address|10.10.2.100| -|displayName||The name of the server associated with your farm|HTTP B server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP B server| +|port||The server port associated with your cluster|8080| -At this stage, here is the configuration status for your two farms: +At this stage, here is the configuration status for your two clusters: ![Farm configuration](images/farms.png){.thumbnail} ## Front-ends. -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server clusters, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,7 +186,7 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server clusters (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your clusters. > ### Blue front-end. @@ -208,7 +208,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77212| +|defaultFarmId||Your production cluster’s ID|77212| |displayName||The name given to the front-end|Blue front-end| |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -233,7 +233,7 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77213| +|defaultFarmId||Your production cluster’s ID|77213| |displayName||The name given to the front-end|Green front-end| |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -263,16 +263,16 @@ Once you have finished configuring the components of the OVHcloud Load Balancer At this stage, our initial environment is deployed and ready to use. How do we use it? -To put it simply, you just need to switch over your front-ends from one server farm to another. +To put it simply, you just need to switch over your front-ends from one server cluster to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on `HTTP cluster A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. +- The development infrastructure (B) is deployed on `HTTP cluster B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. -To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. +To switch between the two clusters, you can simply update your different front-ends by modifying the ID of the cluster it is attached to, and applying the modification. The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). @@ -293,7 +293,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70089| -|defaultFarmId|Your development server farm ID|77213| +|defaultFarmId|Your development server cluster ID|77213| > [!api] > @@ -304,7 +304,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70090| -|defaultFarmId|Your development server farm ID|77212| +|defaultFarmId|Your development server cluster ID|77212| #### To apply your changes and effectively switch over the production and development environments: @@ -323,6 +323,6 @@ You now have an infrastructure you can use to simply and efficiently manage `blu Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). -The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). +The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new clusters dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). -Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. +Another way to consolidate your infrastructure even further is by multiplying the servers attached to your clusters. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. diff --git a/pages/network/load_balancer/case_blue_green/guide.en-au.md b/pages/network/load_balancer/case_blue_green/guide.en-au.md index de705cecacc..9fda0eccc6b 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-au.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-au.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-07-04 --- ## Objective @@ -50,13 +50,13 @@ The diagram below gives a general idea of the architecture: ### Infrastructure A. -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server cluster that will later be associated with a front-end of your IP Load Balancer. This cluster will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. -In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. +In our scenario, we will declare a cluster of servers for the HTTP service. Please note that you can create as many clusters (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. #### Via the OVHcloud Control Panel: -![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure A](images/ferme1.png){.thumbnail} #### Via the API: @@ -69,7 +69,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server clusters respectively. > [!api] > @@ -86,11 +86,11 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Associate a server with your cluster, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each cluster (to balance the load and/or offer higher fault tolerance, for ex.). #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} +![Add a new server to the cluster HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} @@ -104,10 +104,10 @@ Associate a server with your farm, if it is a physical server hosting your produ |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77212| +|farmId|Required|Your server cluster ID|77212| |address|Required|Your server's IPv4 address|10.10.1.100| -|displayName||The name of the server associated with your farm|HTTP A server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP A server| +|port||The server port associated with your cluster|8080| With the additional calls listed below, you can list, modify and delete your servers respectively. @@ -128,15 +128,15 @@ With the additional calls listed below, you can list, modify and delete your ser ### Infrastructure B. -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server cluster that will later be associated with a second front-end of your IP Load Balancer. This server cluster exposes the same service to the front-end as the first server cluster. This service is supplied on the servers by port 8080. -Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). +Deploy the server cluster for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). #### Via the Sunrise Control Panel: -![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure B](images/ferme2.png){.thumbnail} -![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} +![Create a second cluster dedicated to infrastructure B](images/backend2.png){.thumbnail} #### Via the API: @@ -149,11 +149,11 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service |---|---| |serviceName|Your Load Balancer service ID| -Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. +Associate a server with your cluster. Here, it involves one or more physical servers hosting your development infrastructure. #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} +![Add a new server to the cluster HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} @@ -167,18 +167,18 @@ Associate a server with your farm. Here, it involves one or more physical server |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77213| +|farmId|Required|Your server cluster ID|77213| |address|Required|Your server's IPv4 address|10.10.2.100| -|displayName||The name of the server associated with your farm|HTTP B server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP B server| +|port||The server port associated with your cluster|8080| -At this stage, here is the configuration status for your two farms: +At this stage, here is the configuration status for your two clusters: ![Farm configuration](images/farms.png){.thumbnail} ## Front-ends. -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server clusters, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,7 +186,7 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server clusters (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your clusters. > ### Blue front-end. @@ -208,7 +208,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77212| +|defaultFarmId||Your production cluster’s ID|77212| |displayName||The name given to the front-end|Blue front-end| |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -233,7 +233,7 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77213| +|defaultFarmId||Your production cluster’s ID|77213| |displayName||The name given to the front-end|Green front-end| |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -263,16 +263,16 @@ Once you have finished configuring the components of the OVHcloud Load Balancer At this stage, our initial environment is deployed and ready to use. How do we use it? -To put it simply, you just need to switch over your front-ends from one server farm to another. +To put it simply, you just need to switch over your front-ends from one server cluster to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on `HTTP cluster A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. +- The development infrastructure (B) is deployed on `HTTP cluster B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. -To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. +To switch between the two clusters, you can simply update your different front-ends by modifying the ID of the cluster it is attached to, and applying the modification. The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). @@ -293,7 +293,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70089| -|defaultFarmId|Your development server farm ID|77213| +|defaultFarmId|Your development server cluster ID|77213| > [!api] > @@ -304,7 +304,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70090| -|defaultFarmId|Your development server farm ID|77212| +|defaultFarmId|Your development server cluster ID|77212| #### To apply your changes and effectively switch over the production and development environments: @@ -323,6 +323,6 @@ You now have an infrastructure you can use to simply and efficiently manage `blu Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). -The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). +The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new clusters dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). -Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. +Another way to consolidate your infrastructure even further is by multiplying the servers attached to your clusters. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. diff --git a/pages/network/load_balancer/case_blue_green/guide.en-ca.md b/pages/network/load_balancer/case_blue_green/guide.en-ca.md index de705cecacc..9fda0eccc6b 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-ca.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-07-04 --- ## Objective @@ -50,13 +50,13 @@ The diagram below gives a general idea of the architecture: ### Infrastructure A. -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server cluster that will later be associated with a front-end of your IP Load Balancer. This cluster will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. -In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. +In our scenario, we will declare a cluster of servers for the HTTP service. Please note that you can create as many clusters (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. #### Via the OVHcloud Control Panel: -![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure A](images/ferme1.png){.thumbnail} #### Via the API: @@ -69,7 +69,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server clusters respectively. > [!api] > @@ -86,11 +86,11 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Associate a server with your cluster, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each cluster (to balance the load and/or offer higher fault tolerance, for ex.). #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} +![Add a new server to the cluster HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} @@ -104,10 +104,10 @@ Associate a server with your farm, if it is a physical server hosting your produ |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77212| +|farmId|Required|Your server cluster ID|77212| |address|Required|Your server's IPv4 address|10.10.1.100| -|displayName||The name of the server associated with your farm|HTTP A server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP A server| +|port||The server port associated with your cluster|8080| With the additional calls listed below, you can list, modify and delete your servers respectively. @@ -128,15 +128,15 @@ With the additional calls listed below, you can list, modify and delete your ser ### Infrastructure B. -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server cluster that will later be associated with a second front-end of your IP Load Balancer. This server cluster exposes the same service to the front-end as the first server cluster. This service is supplied on the servers by port 8080. -Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). +Deploy the server cluster for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). #### Via the Sunrise Control Panel: -![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure B](images/ferme2.png){.thumbnail} -![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} +![Create a second cluster dedicated to infrastructure B](images/backend2.png){.thumbnail} #### Via the API: @@ -149,11 +149,11 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service |---|---| |serviceName|Your Load Balancer service ID| -Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. +Associate a server with your cluster. Here, it involves one or more physical servers hosting your development infrastructure. #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} +![Add a new server to the cluster HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} @@ -167,18 +167,18 @@ Associate a server with your farm. Here, it involves one or more physical server |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77213| +|farmId|Required|Your server cluster ID|77213| |address|Required|Your server's IPv4 address|10.10.2.100| -|displayName||The name of the server associated with your farm|HTTP B server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP B server| +|port||The server port associated with your cluster|8080| -At this stage, here is the configuration status for your two farms: +At this stage, here is the configuration status for your two clusters: ![Farm configuration](images/farms.png){.thumbnail} ## Front-ends. -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server clusters, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,7 +186,7 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server clusters (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your clusters. > ### Blue front-end. @@ -208,7 +208,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77212| +|defaultFarmId||Your production cluster’s ID|77212| |displayName||The name given to the front-end|Blue front-end| |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -233,7 +233,7 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77213| +|defaultFarmId||Your production cluster’s ID|77213| |displayName||The name given to the front-end|Green front-end| |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -263,16 +263,16 @@ Once you have finished configuring the components of the OVHcloud Load Balancer At this stage, our initial environment is deployed and ready to use. How do we use it? -To put it simply, you just need to switch over your front-ends from one server farm to another. +To put it simply, you just need to switch over your front-ends from one server cluster to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on `HTTP cluster A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. +- The development infrastructure (B) is deployed on `HTTP cluster B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. -To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. +To switch between the two clusters, you can simply update your different front-ends by modifying the ID of the cluster it is attached to, and applying the modification. The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). @@ -293,7 +293,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70089| -|defaultFarmId|Your development server farm ID|77213| +|defaultFarmId|Your development server cluster ID|77213| > [!api] > @@ -304,7 +304,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70090| -|defaultFarmId|Your development server farm ID|77212| +|defaultFarmId|Your development server cluster ID|77212| #### To apply your changes and effectively switch over the production and development environments: @@ -323,6 +323,6 @@ You now have an infrastructure you can use to simply and efficiently manage `blu Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). -The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). +The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new clusters dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). -Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. +Another way to consolidate your infrastructure even further is by multiplying the servers attached to your clusters. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. diff --git a/pages/network/load_balancer/case_blue_green/guide.en-gb.md b/pages/network/load_balancer/case_blue_green/guide.en-gb.md index 3126cb4f2f5..77a55e05496 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-gb.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVH Load Balancer' -updated: 2019-02-25 +updated: 2025-07-04 --- ## Objective @@ -50,13 +50,13 @@ The diagram below gives a general idea of the architecture: ### Infrastructure A. -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVH Load Balancer service, you can read the following guide: [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). +This infrastructure is made up of a server cluster that will later be associated with a front-end of your IP Load Balancer. This cluster will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVH Load Balancer service, you can read the following guide: [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). -In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. +In our scenario, we will declare a cluster of servers for the HTTP service. Please note that you can create as many clusters (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. #### Via the OVH Control Panel: -![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure A](images/ferme1.png){.thumbnail} #### Via the API: @@ -69,7 +69,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server clusters respectively. > [!api] > @@ -86,11 +86,11 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Associate a server with your cluster, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each cluster (to balance the load and/or offer higher fault tolerance, for ex.). #### Via the OVH Control Panel: -![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} +![Add a new server to the cluster HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} @@ -104,10 +104,10 @@ Associate a server with your farm, if it is a physical server hosting your produ |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77212| +|farmId|Required|Your server cluster ID|77212| |address|Required|Your server's IPv4 address|10.10.1.100| -|displayName||The name of the server associated with your farm|HTTP A server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP A server| +|port||The server port associated with your cluster|8080| With the additional calls listed below, you can list, modify and delete your servers respectively. @@ -128,15 +128,15 @@ With the additional calls listed below, you can list, modify and delete your ser ### Infrastructure B. -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server cluster that will later be associated with a second front-end of your IP Load Balancer. This server cluster exposes the same service to the front-end as the first server cluster. This service is supplied on the servers by port 8080. -Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). +Deploy the server cluster for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). #### Via the Sunrise Control Panel: -![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure B](images/ferme2.png){.thumbnail} -![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} +![Create a second cluster dedicated to infrastructure B](images/backend2.png){.thumbnail} #### Via the API: @@ -149,11 +149,11 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service |---|---| |serviceName|Your Load Balancer service ID| -Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. +Associate a server with your cluster. Here, it involves one or more physical servers hosting your development infrastructure. #### Via the OVH Control Panel: -![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} +![Add a new server to the cluster HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} @@ -167,18 +167,18 @@ Associate a server with your farm. Here, it involves one or more physical server |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77213| +|farmId|Required|Your server cluster ID|77213| |address|Required|Your server's IPv4 address|10.10.2.100| -|displayName||The name of the server associated with your farm|HTTP B server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP B server| +|port||The server port associated with your cluster|8080| -At this stage, here is the configuration status for your two farms: +At this stage, here is the configuration status for your two clusters: ![Farm configuration](images/farms.png){.thumbnail} ## Front-ends. -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server clusters, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,7 +186,7 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server clusters (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your clusters. > ### Blue front-end. @@ -208,7 +208,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77212| +|defaultFarmId||Your production cluster’s ID|77212| |displayName||The name given to the front-end|Blue front-end| |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -233,7 +233,7 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77213| +|defaultFarmId||Your production cluster’s ID|77213| |displayName||The name given to the front-end|Green front-end| |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -263,16 +263,16 @@ Once you have finished configuring the components of the OVH Load Balancer servi At this stage, our initial environment is deployed and ready to use. How do we use it? -To put it simply, you just need to switch over your front-ends from one server farm to another. +To put it simply, you just need to switch over your front-ends from one server cluster to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on `HTTP cluster A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. +- The development infrastructure (B) is deployed on `HTTP cluster B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. -To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. +To switch between the two clusters, you can simply update your different front-ends by modifying the ID of the cluster it is attached to, and applying the modification. The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). @@ -293,7 +293,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70089| -|defaultFarmId|Your development server farm ID|77213| +|defaultFarmId|Your development server cluster ID|77213| > [!api] > @@ -304,7 +304,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70090| -|defaultFarmId|Your development server farm ID|77212| +|defaultFarmId|Your development server cluster ID|77212| #### To apply your changes and effectively switch over the production and development environments: @@ -323,6 +323,6 @@ You now have an infrastructure you can use to simply and efficiently manage `blu Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). -The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). +The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new clusters dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). -Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. +Another way to consolidate your infrastructure even further is by multiplying the servers attached to your clusters. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. diff --git a/pages/network/load_balancer/case_blue_green/guide.en-sg.md b/pages/network/load_balancer/case_blue_green/guide.en-sg.md index de705cecacc..9fda0eccc6b 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-sg.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-07-04 --- ## Objective @@ -50,13 +50,13 @@ The diagram below gives a general idea of the architecture: ### Infrastructure A. -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server cluster that will later be associated with a front-end of your IP Load Balancer. This cluster will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. -In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. +In our scenario, we will declare a cluster of servers for the HTTP service. Please note that you can create as many clusters (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. #### Via the OVHcloud Control Panel: -![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure A](images/ferme1.png){.thumbnail} #### Via the API: @@ -69,7 +69,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server clusters respectively. > [!api] > @@ -86,11 +86,11 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Associate a server with your cluster, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each cluster (to balance the load and/or offer higher fault tolerance, for ex.). #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} +![Add a new server to the cluster HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} @@ -104,10 +104,10 @@ Associate a server with your farm, if it is a physical server hosting your produ |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77212| +|farmId|Required|Your server cluster ID|77212| |address|Required|Your server's IPv4 address|10.10.1.100| -|displayName||The name of the server associated with your farm|HTTP A server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP A server| +|port||The server port associated with your cluster|8080| With the additional calls listed below, you can list, modify and delete your servers respectively. @@ -128,15 +128,15 @@ With the additional calls listed below, you can list, modify and delete your ser ### Infrastructure B. -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server cluster that will later be associated with a second front-end of your IP Load Balancer. This server cluster exposes the same service to the front-end as the first server cluster. This service is supplied on the servers by port 8080. -Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). +Deploy the server cluster for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). #### Via the Sunrise Control Panel: -![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure B](images/ferme2.png){.thumbnail} -![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} +![Create a second cluster dedicated to infrastructure B](images/backend2.png){.thumbnail} #### Via the API: @@ -149,11 +149,11 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service |---|---| |serviceName|Your Load Balancer service ID| -Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. +Associate a server with your cluster. Here, it involves one or more physical servers hosting your development infrastructure. #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} +![Add a new server to the cluster HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} @@ -167,18 +167,18 @@ Associate a server with your farm. Here, it involves one or more physical server |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77213| +|farmId|Required|Your server cluster ID|77213| |address|Required|Your server's IPv4 address|10.10.2.100| -|displayName||The name of the server associated with your farm|HTTP B server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP B server| +|port||The server port associated with your cluster|8080| -At this stage, here is the configuration status for your two farms: +At this stage, here is the configuration status for your two clusters: ![Farm configuration](images/farms.png){.thumbnail} ## Front-ends. -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server clusters, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,7 +186,7 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server clusters (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your clusters. > ### Blue front-end. @@ -208,7 +208,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77212| +|defaultFarmId||Your production cluster’s ID|77212| |displayName||The name given to the front-end|Blue front-end| |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -233,7 +233,7 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77213| +|defaultFarmId||Your production cluster’s ID|77213| |displayName||The name given to the front-end|Green front-end| |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -263,16 +263,16 @@ Once you have finished configuring the components of the OVHcloud Load Balancer At this stage, our initial environment is deployed and ready to use. How do we use it? -To put it simply, you just need to switch over your front-ends from one server farm to another. +To put it simply, you just need to switch over your front-ends from one server cluster to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on `HTTP cluster A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. +- The development infrastructure (B) is deployed on `HTTP cluster B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. -To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. +To switch between the two clusters, you can simply update your different front-ends by modifying the ID of the cluster it is attached to, and applying the modification. The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). @@ -293,7 +293,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70089| -|defaultFarmId|Your development server farm ID|77213| +|defaultFarmId|Your development server cluster ID|77213| > [!api] > @@ -304,7 +304,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70090| -|defaultFarmId|Your development server farm ID|77212| +|defaultFarmId|Your development server cluster ID|77212| #### To apply your changes and effectively switch over the production and development environments: @@ -323,6 +323,6 @@ You now have an infrastructure you can use to simply and efficiently manage `blu Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). -The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). +The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new clusters dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). -Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. +Another way to consolidate your infrastructure even further is by multiplying the servers attached to your clusters. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. diff --git a/pages/network/load_balancer/case_blue_green/guide.en-us.md b/pages/network/load_balancer/case_blue_green/guide.en-us.md index de705cecacc..9fda0eccc6b 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-us.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-us.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-07-04 --- ## Objective @@ -50,13 +50,13 @@ The diagram below gives a general idea of the architecture: ### Infrastructure A. -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server cluster that will later be associated with a front-end of your IP Load Balancer. This cluster will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. -In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. +In our scenario, we will declare a cluster of servers for the HTTP service. Please note that you can create as many clusters (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. #### Via the OVHcloud Control Panel: -![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure A](images/ferme1.png){.thumbnail} #### Via the API: @@ -69,7 +69,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server clusters respectively. > [!api] > @@ -86,11 +86,11 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Associate a server with your cluster, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each cluster (to balance the load and/or offer higher fault tolerance, for ex.). #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} +![Add a new server to the cluster HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} @@ -104,10 +104,10 @@ Associate a server with your farm, if it is a physical server hosting your produ |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77212| +|farmId|Required|Your server cluster ID|77212| |address|Required|Your server's IPv4 address|10.10.1.100| -|displayName||The name of the server associated with your farm|HTTP A server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP A server| +|port||The server port associated with your cluster|8080| With the additional calls listed below, you can list, modify and delete your servers respectively. @@ -128,15 +128,15 @@ With the additional calls listed below, you can list, modify and delete your ser ### Infrastructure B. -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server cluster that will later be associated with a second front-end of your IP Load Balancer. This server cluster exposes the same service to the front-end as the first server cluster. This service is supplied on the servers by port 8080. -Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). +Deploy the server cluster for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). #### Via the Sunrise Control Panel: -![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} +![Add a new HTTP cluster dedicated to infrastructure B](images/ferme2.png){.thumbnail} -![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} +![Create a second cluster dedicated to infrastructure B](images/backend2.png){.thumbnail} #### Via the API: @@ -149,11 +149,11 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service |---|---| |serviceName|Your Load Balancer service ID| -Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. +Associate a server with your cluster. Here, it involves one or more physical servers hosting your development infrastructure. #### Via the OVHcloud Control Panel: -![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} +![Add a new server to the cluster HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} @@ -167,18 +167,18 @@ Associate a server with your farm. Here, it involves one or more physical server |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|farmId|Required|Your server farm ID|77213| +|farmId|Required|Your server cluster ID|77213| |address|Required|Your server's IPv4 address|10.10.2.100| -|displayName||The name of the server associated with your farm|HTTP B server| -|port||The server port associated with your farm|8080| +|displayName||The name of the server associated with your cluster|HTTP B server| +|port||The server port associated with your cluster|8080| -At this stage, here is the configuration status for your two farms: +At this stage, here is the configuration status for your two clusters: ![Farm configuration](images/farms.png){.thumbnail} ## Front-ends. -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server clusters, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,7 +186,7 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server clusters (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your clusters. > ### Blue front-end. @@ -208,7 +208,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77212| +|defaultFarmId||Your production cluster’s ID|77212| |displayName||The name given to the front-end|Blue front-end| |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -233,7 +233,7 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |Setting|Required|Meaning|Example| |---|---|---|---| |serviceName|Required|Your Load Balancer service ID|loadbalancer-abcdef0123456789| -|defaultFarmId||Your production farm’s ID|77213| +|defaultFarmId||Your production cluster’s ID|77213| |displayName||The name given to the front-end|Green front-end| |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| @@ -263,16 +263,16 @@ Once you have finished configuring the components of the OVHcloud Load Balancer At this stage, our initial environment is deployed and ready to use. How do we use it? -To put it simply, you just need to switch over your front-ends from one server farm to another. +To put it simply, you just need to switch over your front-ends from one server cluster to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on `HTTP cluster A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. +- The development infrastructure (B) is deployed on `HTTP cluster B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. -To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. +To switch between the two clusters, you can simply update your different front-ends by modifying the ID of the cluster it is attached to, and applying the modification. The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). @@ -293,7 +293,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70089| -|defaultFarmId|Your development server farm ID|77213| +|defaultFarmId|Your development server cluster ID|77213| > [!api] > @@ -304,7 +304,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---|---| |serviceName|Your Load Balancer service ID|loadbalancer-abcdef0123456789| |frontendId|Your production front-end ID|70090| -|defaultFarmId|Your development server farm ID|77212| +|defaultFarmId|Your development server cluster ID|77212| #### To apply your changes and effectively switch over the production and development environments: @@ -323,6 +323,6 @@ You now have an infrastructure you can use to simply and efficiently manage `blu Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). -The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). +The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new clusters dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). -Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. +Another way to consolidate your infrastructure even further is by multiplying the servers attached to your clusters. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. diff --git a/pages/network/load_balancer/case_http2/guide.en-asia.md b/pages/network/load_balancer/case_http2/guide.en-asia.md index 60823bc6002..94200f24a72 100644 --- a/pages/network/load_balancer/case_http2/guide.en-asia.md +++ b/pages/network/load_balancer/case_http2/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Configuring HTTP/2 on an OVHcloud Load Balancer service excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service -updated: 2018-01-15 +updated: 2025-07-04 --- ## Objective @@ -15,7 +15,7 @@ ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables th ## Requirements - You need to have created a TCP front-end. -- You need to have created a TCP farm, with servers added to it. +- You need to have created a TCP cluster, with servers added to it. ## Instructions @@ -54,7 +54,7 @@ We will add a route to our service. >> >> >> >> **target** >> >> > ->> >> > `` +>> >> > `` >> > >> > **frontendId** >> > diff --git a/pages/network/load_balancer/case_http2/guide.en-au.md b/pages/network/load_balancer/case_http2/guide.en-au.md index 60823bc6002..94200f24a72 100644 --- a/pages/network/load_balancer/case_http2/guide.en-au.md +++ b/pages/network/load_balancer/case_http2/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Configuring HTTP/2 on an OVHcloud Load Balancer service excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service -updated: 2018-01-15 +updated: 2025-07-04 --- ## Objective @@ -15,7 +15,7 @@ ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables th ## Requirements - You need to have created a TCP front-end. -- You need to have created a TCP farm, with servers added to it. +- You need to have created a TCP cluster, with servers added to it. ## Instructions @@ -54,7 +54,7 @@ We will add a route to our service. >> >> >> >> **target** >> >> > ->> >> > `` +>> >> > `` >> > >> > **frontendId** >> > diff --git a/pages/network/load_balancer/case_http2/guide.en-ca.md b/pages/network/load_balancer/case_http2/guide.en-ca.md index 60823bc6002..94200f24a72 100644 --- a/pages/network/load_balancer/case_http2/guide.en-ca.md +++ b/pages/network/load_balancer/case_http2/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Configuring HTTP/2 on an OVHcloud Load Balancer service excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service -updated: 2018-01-15 +updated: 2025-07-04 --- ## Objective @@ -15,7 +15,7 @@ ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables th ## Requirements - You need to have created a TCP front-end. -- You need to have created a TCP farm, with servers added to it. +- You need to have created a TCP cluster, with servers added to it. ## Instructions @@ -54,7 +54,7 @@ We will add a route to our service. >> >> >> >> **target** >> >> > ->> >> > `` +>> >> > `` >> > >> > **frontendId** >> > diff --git a/pages/network/load_balancer/case_http2/guide.en-gb.md b/pages/network/load_balancer/case_http2/guide.en-gb.md index 1f1b55c87e9..65b856f4c8e 100644 --- a/pages/network/load_balancer/case_http2/guide.en-gb.md +++ b/pages/network/load_balancer/case_http2/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Configuring HTTP/2 on an OVH Load Balancer service excerpt: Configuring HTTP/2 on an OVH Load Balancer service -updated: 2018-01-15 +updated: 2025-07-04 --- ## Objective @@ -15,7 +15,7 @@ ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables th ## Requirements - You need to have created a TCP front-end. -- You need to have created a TCP farm, with servers added to it. +- You need to have created a TCP cluster, with servers added to it. ## Instructions @@ -54,7 +54,7 @@ We will add a route to our service. >> >> >> >> **target** >> >> > ->> >> > `` +>> >> > `` >> > >> > **frontendId** >> > diff --git a/pages/network/load_balancer/case_http2/guide.en-sg.md b/pages/network/load_balancer/case_http2/guide.en-sg.md index 60823bc6002..94200f24a72 100644 --- a/pages/network/load_balancer/case_http2/guide.en-sg.md +++ b/pages/network/load_balancer/case_http2/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Configuring HTTP/2 on an OVHcloud Load Balancer service excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service -updated: 2018-01-15 +updated: 2025-07-04 --- ## Objective @@ -15,7 +15,7 @@ ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables th ## Requirements - You need to have created a TCP front-end. -- You need to have created a TCP farm, with servers added to it. +- You need to have created a TCP cluster, with servers added to it. ## Instructions @@ -54,7 +54,7 @@ We will add a route to our service. >> >> >> >> **target** >> >> > ->> >> > `` +>> >> > `` >> > >> > **frontendId** >> > diff --git a/pages/network/load_balancer/case_http2/guide.en-us.md b/pages/network/load_balancer/case_http2/guide.en-us.md index 60823bc6002..94200f24a72 100644 --- a/pages/network/load_balancer/case_http2/guide.en-us.md +++ b/pages/network/load_balancer/case_http2/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Configuring HTTP/2 on an OVHcloud Load Balancer service excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service -updated: 2018-01-15 +updated: 2025-07-04 --- ## Objective @@ -15,7 +15,7 @@ ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables th ## Requirements - You need to have created a TCP front-end. -- You need to have created a TCP farm, with servers added to it. +- You need to have created a TCP cluster, with servers added to it. ## Instructions @@ -54,7 +54,7 @@ We will add a route to our service. >> >> >> >> **target** >> >> > ->> >> > `` +>> >> > `` >> > >> > **frontendId** >> > diff --git a/pages/network/load_balancer/case_smtp/guide.en-asia.md b/pages/network/load_balancer/case_smtp/guide.en-asia.md index 81712ab5352..bbc1a8aec8e 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-asia.md +++ b/pages/network/load_balancer/case_smtp/guide.en-asia.md @@ -1,12 +1,12 @@ --- title: 'Configuring SMTP on a Load Balancer service' excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +updated: 2025-07-04 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP cluster with one or more TCP servers, depending on how you choose to configure it. **This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** @@ -25,11 +25,11 @@ In this guide, we will configure a basic TCP load balancing service, for one or > This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, clusters and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach servers to them. > In the Sunrise Control Panel, you will see the features detailed below: @@ -45,9 +45,9 @@ Via the OVH API, in the section: For more information on the API’s features, you can refer to the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of TCP servers to our service, which is the part that balances traffic on the servers. ### Via the Sunrise Control Panel. @@ -55,19 +55,19 @@ In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +As an option, you can add an SMTP probe on your cluster. -![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_farm.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Farms`{.action} tab. +Your server cluster should appear in the list, in the `Farms`{.action} tab. -![Details of the server farm created](images/resume_farm.png){.thumbnail} +![Details of the server cluster created](images/resume_farm.png){.thumbnail} ### Via the API -- List of TCP server farms: +- List of TCP server clusters: > [!api] > @@ -81,21 +81,21 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Add a new TCP server farm: +- Add a new TCP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -104,30 +104,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the Sunrise Control Panel. -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > > It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. > -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -164,17 +164,17 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just ## Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +We will now add a `front-end`{.action} to our service, and connect it to our server cluster. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. ### Via the Sunrise Control Panel. Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your cluster. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Please remember to specify the cluster you created earlier as a “default cluster”. ![Add a front-end](images/add_frontend.png){.thumbnail} diff --git a/pages/network/load_balancer/case_smtp/guide.en-ca.md b/pages/network/load_balancer/case_smtp/guide.en-ca.md index 81712ab5352..bbc1a8aec8e 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-ca.md +++ b/pages/network/load_balancer/case_smtp/guide.en-ca.md @@ -1,12 +1,12 @@ --- title: 'Configuring SMTP on a Load Balancer service' excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +updated: 2025-07-04 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP cluster with one or more TCP servers, depending on how you choose to configure it. **This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** @@ -25,11 +25,11 @@ In this guide, we will configure a basic TCP load balancing service, for one or > This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, clusters and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach servers to them. > In the Sunrise Control Panel, you will see the features detailed below: @@ -45,9 +45,9 @@ Via the OVH API, in the section: For more information on the API’s features, you can refer to the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of TCP servers to our service, which is the part that balances traffic on the servers. ### Via the Sunrise Control Panel. @@ -55,19 +55,19 @@ In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +As an option, you can add an SMTP probe on your cluster. -![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_farm.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Farms`{.action} tab. +Your server cluster should appear in the list, in the `Farms`{.action} tab. -![Details of the server farm created](images/resume_farm.png){.thumbnail} +![Details of the server cluster created](images/resume_farm.png){.thumbnail} ### Via the API -- List of TCP server farms: +- List of TCP server clusters: > [!api] > @@ -81,21 +81,21 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Add a new TCP server farm: +- Add a new TCP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -104,30 +104,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the Sunrise Control Panel. -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > > It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. > -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -164,17 +164,17 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just ## Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +We will now add a `front-end`{.action} to our service, and connect it to our server cluster. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. ### Via the Sunrise Control Panel. Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your cluster. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Please remember to specify the cluster you created earlier as a “default cluster”. ![Add a front-end](images/add_frontend.png){.thumbnail} diff --git a/pages/network/load_balancer/case_smtp/guide.en-gb.md b/pages/network/load_balancer/case_smtp/guide.en-gb.md index 148b5f7fe61..20510bb0189 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-gb.md +++ b/pages/network/load_balancer/case_smtp/guide.en-gb.md @@ -1,12 +1,12 @@ --- title: 'Configuring SMTP on a Load Balancer service' excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +updated: 2025-07-04 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP cluster with one or more TCP servers, depending on how you choose to configure it. **This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** @@ -25,11 +25,11 @@ In this guide, we will configure a basic TCP load balancing service, for one or > This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, clusters and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach servers to them. > In the Sunrise Control Panel, you will see the features detailed below: @@ -45,9 +45,9 @@ Via the OVH API, in the section: For more information on the API’s features, you can refer to [the following guide in French](/pages/network/load_balancer/use_api_reference). -## Add a server farm. +## Add a server cluster. -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of TCP servers to our service, which is the part that balances traffic on the servers. ### Via the Sunrise Control Panel. @@ -55,19 +55,19 @@ In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +As an option, you can add an SMTP probe on your cluster. -![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_farm.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Farms`{.action} tab. +Your server cluster should appear in the list, in the `Farms`{.action} tab. -![Details of the server farm created](images/resume_farm.png){.thumbnail} +![Details of the server cluster created](images/resume_farm.png){.thumbnail} ### Via the API -- List of TCP server farms: +- List of TCP server clusters: > [!api] > @@ -81,21 +81,21 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Add a new TCP server farm: +- Add a new TCP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -104,30 +104,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the Sunrise Control Panel. -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > > It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. > -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -164,17 +164,17 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just ## Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +We will now add a `front-end`{.action} to our service, and connect it to our server cluster. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. ### Via the Sunrise Control Panel. Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your cluster. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Please remember to specify the cluster you created earlier as a “default cluster”. ![Add a front-end](images/add_frontend.png){.thumbnail} diff --git a/pages/network/load_balancer/case_smtp/guide.en-sg.md b/pages/network/load_balancer/case_smtp/guide.en-sg.md index 81712ab5352..bbc1a8aec8e 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-sg.md +++ b/pages/network/load_balancer/case_smtp/guide.en-sg.md @@ -1,12 +1,12 @@ --- title: 'Configuring SMTP on a Load Balancer service' excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +updated: 2025-07-04 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP cluster with one or more TCP servers, depending on how you choose to configure it. **This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** @@ -25,11 +25,11 @@ In this guide, we will configure a basic TCP load balancing service, for one or > This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, clusters and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach servers to them. > In the Sunrise Control Panel, you will see the features detailed below: @@ -45,9 +45,9 @@ Via the OVH API, in the section: For more information on the API’s features, you can refer to the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of TCP servers to our service, which is the part that balances traffic on the servers. ### Via the Sunrise Control Panel. @@ -55,19 +55,19 @@ In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +As an option, you can add an SMTP probe on your cluster. -![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_farm.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Farms`{.action} tab. +Your server cluster should appear in the list, in the `Farms`{.action} tab. -![Details of the server farm created](images/resume_farm.png){.thumbnail} +![Details of the server cluster created](images/resume_farm.png){.thumbnail} ### Via the API -- List of TCP server farms: +- List of TCP server clusters: > [!api] > @@ -81,21 +81,21 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Add a new TCP server farm: +- Add a new TCP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -104,30 +104,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the Sunrise Control Panel. -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > > It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. > -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -164,17 +164,17 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just ## Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +We will now add a `front-end`{.action} to our service, and connect it to our server cluster. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. ### Via the Sunrise Control Panel. Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your cluster. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Please remember to specify the cluster you created earlier as a “default cluster”. ![Add a front-end](images/add_frontend.png){.thumbnail} diff --git a/pages/network/load_balancer/case_smtp/guide.en-us.md b/pages/network/load_balancer/case_smtp/guide.en-us.md index 81712ab5352..bbc1a8aec8e 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-us.md +++ b/pages/network/load_balancer/case_smtp/guide.en-us.md @@ -1,12 +1,12 @@ --- title: 'Configuring SMTP on a Load Balancer service' excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +updated: 2025-07-04 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP cluster with one or more TCP servers, depending on how you choose to configure it. **This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** @@ -25,11 +25,11 @@ In this guide, we will configure a basic TCP load balancing service, for one or > This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, clusters and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach servers to them. > In the Sunrise Control Panel, you will see the features detailed below: @@ -45,9 +45,9 @@ Via the OVH API, in the section: For more information on the API’s features, you can refer to the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of TCP servers to our service, which is the part that balances traffic on the servers. ### Via the Sunrise Control Panel. @@ -55,19 +55,19 @@ In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +As an option, you can add an SMTP probe on your cluster. -![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_farm.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Farms`{.action} tab. +Your server cluster should appear in the list, in the `Farms`{.action} tab. -![Details of the server farm created](images/resume_farm.png){.thumbnail} +![Details of the server cluster created](images/resume_farm.png){.thumbnail} ### Via the API -- List of TCP server farms: +- List of TCP server clusters: > [!api] > @@ -81,21 +81,21 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Add a new TCP server farm: +- Add a new TCP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -104,30 +104,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the Sunrise Control Panel. -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > > It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. > -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -164,17 +164,17 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just ## Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +We will now add a `front-end`{.action} to our service, and connect it to our server cluster. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. ### Via the Sunrise Control Panel. Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your cluster. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Please remember to specify the cluster you created earlier as a “default cluster”. ![Add a front-end](images/add_frontend.png){.thumbnail} diff --git a/pages/network/load_balancer/create_balancing/guide.de-de.md b/pages/network/load_balancer/create_balancing/guide.de-de.md index 6fe2c8985a5..a2fa2f52776 100644 --- a/pages/network/load_balancer/create_balancing/guide.de-de.md +++ b/pages/network/load_balancer/create_balancing/guide.de-de.md @@ -1,7 +1,7 @@ --- title: Lastverteilungstyp excerpt: Diese Anleitung beschreibt die verschiedenen Lastverteilungsmethoden des OVH Loadbalancers -updated: 2018-01-17 +updated: 2025-07-04 --- ## Einleitung @@ -19,7 +19,7 @@ Der neue OVH Loadbalancer bietet Ihnen mehrere Lastverteilungstypen für Ihre Di ### Die verschiedenen Lastverteilungstypen -Lastverteilung (engl. „Load Balancing“) wird in Serverfarmen verwendet. Diese Einstellung bestimmt, wie Anfragen zwischen den verschiedenen Servern einer Farm aufgeteilt werden. +Lastverteilung (engl. „Load Balancing“) wird in Serverfarmen verwendet. Diese Einstellung bestimmt, wie Anfragen zwischen den verschiedenen Servern einer cluster aufgeteilt werden. Weitere Informationen zu den Grundbestandteilen des OVH Loadbalancers finden Sie in der [Einführung zum OVH Loadbalancer](/pages/network/load_balancer/use_presentation){.external}. @@ -31,9 +31,9 @@ Weitere Informationen zu den Grundbestandteilen des OVH Loadbalancers finden Sie |Source|Dieser Algorithmus wendet eine *Hashfunktion* auf die Quell-IP an und teilt anschließend das Ergebnis durch die Anzahl der aktuell aktiven Server. So wird die gleiche Quell-IP immer auf denselben Server weitergeleitet, solange dieser aktiv ist.| |URI|Dieser Algorithmus wendet eine *Hashfunktion* auf einen Teil oder den kompletten URI an und teilt anschließend das Ergebnis durch die Anzahl der aktuell aktiven Server. So wird der gleiche URI immer auf denselben Server weitergeleitet, solange dieser aktiv ist.| -### Lastverteilungstyp einer Farm über das Kundencenter anpassen +### Lastverteilungstyp einer cluster über das Kundencenter anpassen -- Im Bereich `Serverfarmen`{.action} Ihres OVH Loadbalancers werden Ihnen die aktuell eingerichteten Serverfarmen angezeigt. Um eine der Farmen zu bearbeiten, klicken Sie einfach auf die drei Punkte rechts neben der entsprechenden Farm (2) und anschließend auf `Ändern`{.action}: +- Im Bereich `Serverfarmen`{.action} Ihres OVH Loadbalancers werden Ihnen die aktuell eingerichteten Serverfarmen angezeigt. Um eine der clusteren zu bearbeiten, klicken Sie einfach auf die drei Punkte rechts neben der entsprechenden cluster (2) und anschließend auf `Ändern`{.action}: ![Serverfarm bearbeiten](images/server_cluster_change.png){.thumbnail} @@ -45,13 +45,13 @@ Wenn Sie den gewünschten Lastverteilungstyp ausgewählt haben, klicken Sie auf ![Konfiguration anwenden](images/apply_config.png){.thumbnail} -### Lastverteilungstyp einer Farm über die API anpassen +### Lastverteilungstyp einer cluster über die API anpassen Sie können die Einstellungen des Lastverteilungstyps anpassen, indem Sie die entsprechenden Einstellungen in den Serverfarmen vornehmen. -- Details einer Farm einsehen +- Details einer cluster einsehen -Mit dieser API-Funktion können Sie sich die Details einer Farm anzeigen lassen, wenn Sie deren ID kennen. Im folgenden Beispiel werden wir eine HTTP-Farm bearbeiten: +Mit dieser API-Funktion können Sie sich die Details einer cluster anzeigen lassen, wenn Sie deren ID kennen. Im folgenden Beispiel werden wir eine HTTP-Farm bearbeiten: > [!api] > @@ -61,21 +61,21 @@ Mit dieser API-Funktion können Sie sich die Details einer Farm anzeigen lassen, |Einstellung|Bedeutung| |---|---| |ServiceName*|ID Ihres Loadbalancer Dienstes| -|farmId*|ID der Farm| +|farmId*|ID der cluster| |Antwort (BackendHttp)|Bedeutung| |---|---| -|farmId|ID der Farm| -|balance|Aktuell auf der Farm konfigurierter Lastverteilungstyp| -|zone|Name der Zone, in der die Farm konfiguriert ist| +|farmId|ID der cluster| +|balance|Aktuell auf der cluster konfigurierter Lastverteilungstyp| +|zone|Name der Zone, in der die cluster konfiguriert ist| |port|Port, der verwendet wird, um die Server zu kontaktieren| -|probe|Aktuell auf der Farm konfigurierte Monitoring-Sonde| -|displayName|Name der Farm| -|stickiness|Aktuell auf der Farm konfigurierte Verbindungsüberwachung| +|probe|Aktuell auf der cluster konfigurierte Monitoring-Sonde| +|displayName|Name der cluster| +|stickiness|Aktuell auf der cluster konfigurierte Verbindungsüberwachung| - Lastverteilungstyp anpassen -Mit diesem Aufrufbefehl können Sie die Konfiguration einer Farm bearbeiten, wenn Sie deren ID kennen. Im folgenden Beispiel werden wir eine HTTP-Farm bearbeiten. Um den Lastverteilungstyp zu ändern, aktualisieren Sie das Feld `BackendHttp.balance` mit einem verfügbaren Lastverteilungstyp: +Mit diesem Aufrufbefehl können Sie die Konfiguration einer cluster bearbeiten, wenn Sie deren ID kennen. Im folgenden Beispiel werden wir eine HTTP-Farm bearbeiten. Um den Lastverteilungstyp zu ändern, aktualisieren Sie das Feld `BackendHttp.balance` mit einem verfügbaren Lastverteilungstyp: > [!api] > @@ -85,8 +85,8 @@ Mit diesem Aufrufbefehl können Sie die Konfiguration einer Farm bearbeiten, wen |Einstellung|Bedeutung| |---|---| |ServiceName*|ID Ihres Loadbalancer Dienstes| -|farmId*|ID der Farm| -|BackendHttp.balance|Der gewünschte Lastverteilungstyp für diese Farm| +|farmId*|ID der cluster| +|BackendHttp.balance|Der gewünschte Lastverteilungstyp für diese cluster| - Änderungen anwenden diff --git a/pages/network/load_balancer/create_balancing/guide.en-asia.md b/pages/network/load_balancer/create_balancing/guide.en-asia.md index c36f003bce4..06494034fe9 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-asia.md +++ b/pages/network/load_balancer/create_balancing/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -13,13 +13,13 @@ The new OVH Load Balancer service offers a variety of load balancing methods for ## Requirements - You must be logged in to the [OVH Control Panel](/links/manager). -- You need to have created a server farm. +- You need to have created a server cluster. ## Instructions ### Different load balancing methods -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +Load balancing is used in server clusters. This setting defines the way that requests are distributed between the servers within the cluster. To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. @@ -31,27 +31,27 @@ To understand the basics of the OVH Load Balancer service, please refer to the [ |Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| |URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server cluster’s load balancing method via the Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server clusters`{.action} section (1), you will see the clusters that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: -![Modify a farm](images/server_cluster_change.png){.thumbnail} +![Modify a cluster](images/server_cluster_change.png){.thumbnail} In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: -![Modify a farm](images/distrib_mode_edit.png){.thumbnail} +![Modify a cluster](images/distrib_mode_edit.png){.thumbnail} Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server cluster’s load balancing method via the API -You can modify the load balancing method settings by editing them in the server farm. +You can modify the load balancing method settings by editing them in the server cluster. -- View details on a server farm +- View details on a server cluster -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on an HTTP cluster: > [!api] > @@ -61,21 +61,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection monitoring method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently set for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection monitoring method currently set for the cluster| -- Modify a server farm’s load balancing method +- Modify a server cluster’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on an HTTP cluster. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: > [!api] > @@ -85,8 +85,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.balance|Preferred balancing method for this farm| +|farmId*|The cluster’s ID number| +|BackendHttp.balance|Preferred balancing method for this cluster| - Apply the modifications diff --git a/pages/network/load_balancer/create_balancing/guide.en-au.md b/pages/network/load_balancer/create_balancing/guide.en-au.md index c36f003bce4..06494034fe9 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-au.md +++ b/pages/network/load_balancer/create_balancing/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -13,13 +13,13 @@ The new OVH Load Balancer service offers a variety of load balancing methods for ## Requirements - You must be logged in to the [OVH Control Panel](/links/manager). -- You need to have created a server farm. +- You need to have created a server cluster. ## Instructions ### Different load balancing methods -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +Load balancing is used in server clusters. This setting defines the way that requests are distributed between the servers within the cluster. To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. @@ -31,27 +31,27 @@ To understand the basics of the OVH Load Balancer service, please refer to the [ |Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| |URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server cluster’s load balancing method via the Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server clusters`{.action} section (1), you will see the clusters that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: -![Modify a farm](images/server_cluster_change.png){.thumbnail} +![Modify a cluster](images/server_cluster_change.png){.thumbnail} In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: -![Modify a farm](images/distrib_mode_edit.png){.thumbnail} +![Modify a cluster](images/distrib_mode_edit.png){.thumbnail} Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server cluster’s load balancing method via the API -You can modify the load balancing method settings by editing them in the server farm. +You can modify the load balancing method settings by editing them in the server cluster. -- View details on a server farm +- View details on a server cluster -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on an HTTP cluster: > [!api] > @@ -61,21 +61,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection monitoring method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently set for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection monitoring method currently set for the cluster| -- Modify a server farm’s load balancing method +- Modify a server cluster’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on an HTTP cluster. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: > [!api] > @@ -85,8 +85,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.balance|Preferred balancing method for this farm| +|farmId*|The cluster’s ID number| +|BackendHttp.balance|Preferred balancing method for this cluster| - Apply the modifications diff --git a/pages/network/load_balancer/create_balancing/guide.en-ca.md b/pages/network/load_balancer/create_balancing/guide.en-ca.md index c36f003bce4..06494034fe9 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-ca.md +++ b/pages/network/load_balancer/create_balancing/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -13,13 +13,13 @@ The new OVH Load Balancer service offers a variety of load balancing methods for ## Requirements - You must be logged in to the [OVH Control Panel](/links/manager). -- You need to have created a server farm. +- You need to have created a server cluster. ## Instructions ### Different load balancing methods -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +Load balancing is used in server clusters. This setting defines the way that requests are distributed between the servers within the cluster. To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. @@ -31,27 +31,27 @@ To understand the basics of the OVH Load Balancer service, please refer to the [ |Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| |URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server cluster’s load balancing method via the Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server clusters`{.action} section (1), you will see the clusters that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: -![Modify a farm](images/server_cluster_change.png){.thumbnail} +![Modify a cluster](images/server_cluster_change.png){.thumbnail} In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: -![Modify a farm](images/distrib_mode_edit.png){.thumbnail} +![Modify a cluster](images/distrib_mode_edit.png){.thumbnail} Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server cluster’s load balancing method via the API -You can modify the load balancing method settings by editing them in the server farm. +You can modify the load balancing method settings by editing them in the server cluster. -- View details on a server farm +- View details on a server cluster -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on an HTTP cluster: > [!api] > @@ -61,21 +61,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection monitoring method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently set for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection monitoring method currently set for the cluster| -- Modify a server farm’s load balancing method +- Modify a server cluster’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on an HTTP cluster. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: > [!api] > @@ -85,8 +85,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.balance|Preferred balancing method for this farm| +|farmId*|The cluster’s ID number| +|BackendHttp.balance|Preferred balancing method for this cluster| - Apply the modifications diff --git a/pages/network/load_balancer/create_balancing/guide.en-gb.md b/pages/network/load_balancer/create_balancing/guide.en-gb.md index c36f003bce4..06494034fe9 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-gb.md +++ b/pages/network/load_balancer/create_balancing/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -13,13 +13,13 @@ The new OVH Load Balancer service offers a variety of load balancing methods for ## Requirements - You must be logged in to the [OVH Control Panel](/links/manager). -- You need to have created a server farm. +- You need to have created a server cluster. ## Instructions ### Different load balancing methods -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +Load balancing is used in server clusters. This setting defines the way that requests are distributed between the servers within the cluster. To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. @@ -31,27 +31,27 @@ To understand the basics of the OVH Load Balancer service, please refer to the [ |Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| |URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server cluster’s load balancing method via the Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server clusters`{.action} section (1), you will see the clusters that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: -![Modify a farm](images/server_cluster_change.png){.thumbnail} +![Modify a cluster](images/server_cluster_change.png){.thumbnail} In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: -![Modify a farm](images/distrib_mode_edit.png){.thumbnail} +![Modify a cluster](images/distrib_mode_edit.png){.thumbnail} Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server cluster’s load balancing method via the API -You can modify the load balancing method settings by editing them in the server farm. +You can modify the load balancing method settings by editing them in the server cluster. -- View details on a server farm +- View details on a server cluster -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on an HTTP cluster: > [!api] > @@ -61,21 +61,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection monitoring method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently set for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection monitoring method currently set for the cluster| -- Modify a server farm’s load balancing method +- Modify a server cluster’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on an HTTP cluster. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: > [!api] > @@ -85,8 +85,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.balance|Preferred balancing method for this farm| +|farmId*|The cluster’s ID number| +|BackendHttp.balance|Preferred balancing method for this cluster| - Apply the modifications diff --git a/pages/network/load_balancer/create_balancing/guide.en-sg.md b/pages/network/load_balancer/create_balancing/guide.en-sg.md index c36f003bce4..06494034fe9 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-sg.md +++ b/pages/network/load_balancer/create_balancing/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -13,13 +13,13 @@ The new OVH Load Balancer service offers a variety of load balancing methods for ## Requirements - You must be logged in to the [OVH Control Panel](/links/manager). -- You need to have created a server farm. +- You need to have created a server cluster. ## Instructions ### Different load balancing methods -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +Load balancing is used in server clusters. This setting defines the way that requests are distributed between the servers within the cluster. To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation){.external}. @@ -31,27 +31,27 @@ To understand the basics of the OVH Load Balancer service, please refer to the [ |Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| |URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server cluster’s load balancing method via the Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server clusters`{.action} section (1), you will see the clusters that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: -![Modify a farm](images/server_cluster_change.png){.thumbnail} +![Modify a cluster](images/server_cluster_change.png){.thumbnail} In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: -![Modify a farm](images/distrib_mode_edit.png){.thumbnail} +![Modify a cluster](images/distrib_mode_edit.png){.thumbnail} Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server cluster’s load balancing method via the API -You can modify the load balancing method settings by editing them in the server farm. +You can modify the load balancing method settings by editing them in the server cluster. -- View details on a server farm +- View details on a server cluster -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on an HTTP cluster: > [!api] > @@ -61,21 +61,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection monitoring method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently set for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection monitoring method currently set for the cluster| -- Modify a server farm’s load balancing method +- Modify a server cluster’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on an HTTP cluster. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: > [!api] > @@ -85,8 +85,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |ServiceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.balance|Preferred balancing method for this farm| +|farmId*|The cluster’s ID number| +|BackendHttp.balance|Preferred balancing method for this cluster| - Apply the modifications diff --git a/pages/network/load_balancer/create_http_https/guide.en-asia.md b/pages/network/load_balancer/create_http_https/guide.en-asia.md index 8b7a5b59a68..f1833c1562c 100644 --- a/pages/network/load_balancer/create_http_https/guide.en-asia.md +++ b/pages/network/load_balancer/create_http_https/guide.en-asia.md @@ -1,20 +1,20 @@ --- title: 'Configuring a HTTP/HTTPS OVH Load Balancer service' excerpt: 'Find out how to configure an OVH Load Balancer service' -updated: 2023-11-22 +updated: 2025-07-04 --- ## Objective The purpose of this guide is to help you create your first HTTP/HTTPS service with the new OVHcloud Load Balancer solution. Here, we will set up a basic OVHcloud Load Balancer service configuration to balance the HTTP load for a service like a website. -A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP farm. This farm can have one or more servers, depending on the configuration you have chosen/adapted. +A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP cluster. This cluster can have one or more servers, depending on the configuration you have chosen/adapted. As a reminder, the OVHcloud Load Balancer has four primary components: - `front-ends` - server `farms` and their `servers` -- the advanced `routes` between the front-ends and server farms +- the advanced `routes` between the front-ends and server clusters - `SSL/TLS` connections that can encrypt TCP and/or HTTP connections **This guide will show you how to configure an OVHcloud Load Balancer Service.** @@ -22,7 +22,7 @@ As a reminder, the OVHcloud Load Balancer has four primary components: ## Requirements - an OVHcloud Load Balancer -- the ability to add and configure a farm, a server, a front-end and an SSL certificate +- the ability to add and configure a cluster, a server, a front-end and an SSL certificate ## Introduction @@ -35,7 +35,7 @@ If you have not done so already, we recommend reading a general introduction to > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server farms in order to configure the front-end’s default farm. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server clusters in order to configure the front-end’s default cluster. > In the control panel of the load balancer, you will see the features detailed below: @@ -53,31 +53,31 @@ Similarly, this can be done via the OVHcloud API, in the section: For more information on the API’s features, you can consult the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of HTTP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of HTTP servers to our service, which is the part that balances traffic on the servers. ### Via the OVHCloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, click on the `Add a server farm`{.action} button. +In the `Server clusters`{.action} tab, click on the `Add a server cluster`{.action} button. Fill in the fields. The only mandatory fields for a basic configuration are *Protocol* and *Datacentre*. We recommend explicitly defining a *Port* (generally port 80 for a web service). If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end, and the probes will not be able to work as intended. -If you add several servers to your farm, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. +If you add several servers to your cluster, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. -![Add a server farm via the Control Panel](images/add_backend.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_backend.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Server farms`{.action} tab. +Your server cluster should appear in the list, in the `Server clusters`{.action} tab. -![Details of the server farm created](images/resume_backend.png){.thumbnail} +![Details of the server cluster created](images/resume_backend.png){.thumbnail} ### Via the API -- List of HTTP server farms: +- List of HTTP server clusters: > [!api] > @@ -91,21 +91,21 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Add a new HTTP server farm: +- Add a new HTTP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -114,27 +114,27 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the OVHcloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Server clusters`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. +Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Server farm`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Server cluster`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -171,7 +171,7 @@ Your server should appear in the server list, in the `Server farm`{.action} tab, ## Add a front-end. -We will now add a `front-end` to our service, and connect it to our server farm. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. +We will now add a `front-end` to our service, and connect it to our server cluster. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. ### Via the OVHcloud Control Panel. diff --git a/pages/network/load_balancer/create_http_https/guide.en-au.md b/pages/network/load_balancer/create_http_https/guide.en-au.md index 8b7a5b59a68..f1833c1562c 100644 --- a/pages/network/load_balancer/create_http_https/guide.en-au.md +++ b/pages/network/load_balancer/create_http_https/guide.en-au.md @@ -1,20 +1,20 @@ --- title: 'Configuring a HTTP/HTTPS OVH Load Balancer service' excerpt: 'Find out how to configure an OVH Load Balancer service' -updated: 2023-11-22 +updated: 2025-07-04 --- ## Objective The purpose of this guide is to help you create your first HTTP/HTTPS service with the new OVHcloud Load Balancer solution. Here, we will set up a basic OVHcloud Load Balancer service configuration to balance the HTTP load for a service like a website. -A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP farm. This farm can have one or more servers, depending on the configuration you have chosen/adapted. +A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP cluster. This cluster can have one or more servers, depending on the configuration you have chosen/adapted. As a reminder, the OVHcloud Load Balancer has four primary components: - `front-ends` - server `farms` and their `servers` -- the advanced `routes` between the front-ends and server farms +- the advanced `routes` between the front-ends and server clusters - `SSL/TLS` connections that can encrypt TCP and/or HTTP connections **This guide will show you how to configure an OVHcloud Load Balancer Service.** @@ -22,7 +22,7 @@ As a reminder, the OVHcloud Load Balancer has four primary components: ## Requirements - an OVHcloud Load Balancer -- the ability to add and configure a farm, a server, a front-end and an SSL certificate +- the ability to add and configure a cluster, a server, a front-end and an SSL certificate ## Introduction @@ -35,7 +35,7 @@ If you have not done so already, we recommend reading a general introduction to > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server farms in order to configure the front-end’s default farm. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server clusters in order to configure the front-end’s default cluster. > In the control panel of the load balancer, you will see the features detailed below: @@ -53,31 +53,31 @@ Similarly, this can be done via the OVHcloud API, in the section: For more information on the API’s features, you can consult the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of HTTP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of HTTP servers to our service, which is the part that balances traffic on the servers. ### Via the OVHCloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, click on the `Add a server farm`{.action} button. +In the `Server clusters`{.action} tab, click on the `Add a server cluster`{.action} button. Fill in the fields. The only mandatory fields for a basic configuration are *Protocol* and *Datacentre*. We recommend explicitly defining a *Port* (generally port 80 for a web service). If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end, and the probes will not be able to work as intended. -If you add several servers to your farm, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. +If you add several servers to your cluster, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. -![Add a server farm via the Control Panel](images/add_backend.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_backend.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Server farms`{.action} tab. +Your server cluster should appear in the list, in the `Server clusters`{.action} tab. -![Details of the server farm created](images/resume_backend.png){.thumbnail} +![Details of the server cluster created](images/resume_backend.png){.thumbnail} ### Via the API -- List of HTTP server farms: +- List of HTTP server clusters: > [!api] > @@ -91,21 +91,21 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Add a new HTTP server farm: +- Add a new HTTP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -114,27 +114,27 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the OVHcloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Server clusters`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. +Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Server farm`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Server cluster`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -171,7 +171,7 @@ Your server should appear in the server list, in the `Server farm`{.action} tab, ## Add a front-end. -We will now add a `front-end` to our service, and connect it to our server farm. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. +We will now add a `front-end` to our service, and connect it to our server cluster. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. ### Via the OVHcloud Control Panel. diff --git a/pages/network/load_balancer/create_http_https/guide.en-ca.md b/pages/network/load_balancer/create_http_https/guide.en-ca.md index 8fb7329b659..83107cdb85b 100644 --- a/pages/network/load_balancer/create_http_https/guide.en-ca.md +++ b/pages/network/load_balancer/create_http_https/guide.en-ca.md @@ -1,20 +1,20 @@ --- title: 'Configuring a HTTP/HTTPS OVH Load Balancer service' excerpt: 'Find out how to configure an OVH Load Balancer service' -updated: 2023-11-22 +updated: 2025-07-04 --- ## Objective The purpose of this guide is to help you create your first HTTP/HTTPS service with the new OVHcloud Load Balancer solution. Here, we will set up a basic OVHcloud Load Balancer service configuration to balance the HTTP load for a service like a website. -A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP farm. This farm can have one or more servers, depending on the configuration you have chosen/adapted. +A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP cluster. This cluster can have one or more servers, depending on the configuration you have chosen/adapted. As a reminder, the OVHcloud Load Balancer has four primary components: - `front-ends` - server `farms` and their `servers` -- the advanced `routes` between the front-ends and server farms +- the advanced `routes` between the front-ends and server clusters - `SSL/TLS` connections that can encrypt TCP and/or HTTP connections **This guide will show you how to configure an OVHcloud Load Balancer Service.** @@ -22,7 +22,7 @@ As a reminder, the OVHcloud Load Balancer has four primary components: ## Requirements - an OVHcloud Load Balancer -- the ability to add and configure a farm, a server, a front-end and an SSL certificate +- the ability to add and configure a cluster, a server, a front-end and an SSL certificate ## Introduction @@ -35,7 +35,7 @@ If you have not done so already, we recommend reading a general introduction to > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server farms in order to configure the front-end’s default farm. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server clusters in order to configure the front-end’s default cluster. > In the control panel of the load balancer, you will see the features detailed below: @@ -53,31 +53,31 @@ Similarly, this can be done via the OVHcloud API, in the section: For more information on the API’s features, you can consult the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of HTTP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of HTTP servers to our service, which is the part that balances traffic on the servers. ### Via the OVHCloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, click on the `Add a server farm`{.action} button. +In the `Server clusters`{.action} tab, click on the `Add a server cluster`{.action} button. Fill in the fields. The only mandatory fields for a basic configuration are *Protocol* and *Datacentre*. We recommend explicitly defining a *Port* (generally port 80 for a web service). If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end, and the probes will not be able to work as intended. -If you add several servers to your farm, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. +If you add several servers to your cluster, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. -![Add a server farm via the Control Panel](images/add_backend.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_backend.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Server farms`{.action} tab. +Your server cluster should appear in the list, in the `Server clusters`{.action} tab. -![Details of the server farm created](images/resume_backend.png){.thumbnail} +![Details of the server cluster created](images/resume_backend.png){.thumbnail} ### Via the API -- List of HTTP server farms: +- List of HTTP server clusters: > [!api] > @@ -91,21 +91,21 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Add a new HTTP server farm: +- Add a new HTTP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -114,27 +114,27 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the OVHcloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Server clusters`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. +Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Server farm`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Server cluster`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -171,7 +171,7 @@ Your server should appear in the server list, in the `Server farm`{.action} tab, ## Add a front-end. -We will now add a `front-end` to our service, and connect it to our server farm. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. +We will now add a `front-end` to our service, and connect it to our server cluster. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. ### Via the OVHcloud Control Panel. diff --git a/pages/network/load_balancer/create_http_https/guide.en-gb.md b/pages/network/load_balancer/create_http_https/guide.en-gb.md index 8fb7329b659..2dc30a88765 100644 --- a/pages/network/load_balancer/create_http_https/guide.en-gb.md +++ b/pages/network/load_balancer/create_http_https/guide.en-gb.md @@ -1,20 +1,20 @@ --- title: 'Configuring a HTTP/HTTPS OVH Load Balancer service' excerpt: 'Find out how to configure an OVH Load Balancer service' -updated: 2023-11-22 +updated: 2025-07-04 --- ## Objective The purpose of this guide is to help you create your first HTTP/HTTPS service with the new OVHcloud Load Balancer solution. Here, we will set up a basic OVHcloud Load Balancer service configuration to balance the HTTP load for a service like a website. -A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP farm. This farm can have one or more servers, depending on the configuration you have chosen/adapted. +A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP cluster. This cluster can have one or more servers, depending on the configuration you have chosen/adapted. As a reminder, the OVHcloud Load Balancer has four primary components: - `front-ends` -- server `farms` and their `servers` -- the advanced `routes` between the front-ends and server farms +- server `clusters` and their `servers` +- the advanced `routes` between the front-ends and server clusters - `SSL/TLS` connections that can encrypt TCP and/or HTTP connections **This guide will show you how to configure an OVHcloud Load Balancer Service.** @@ -22,7 +22,7 @@ As a reminder, the OVHcloud Load Balancer has four primary components: ## Requirements - an OVHcloud Load Balancer -- the ability to add and configure a farm, a server, a front-end and an SSL certificate +- the ability to add and configure a cluster, a server, a front-end and an SSL certificate ## Introduction @@ -35,7 +35,7 @@ If you have not done so already, we recommend reading a general introduction to > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server farms in order to configure the front-end’s default farm. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server clusters in order to configure the front-end’s default cluster. > In the control panel of the load balancer, you will see the features detailed below: @@ -53,31 +53,31 @@ Similarly, this can be done via the OVHcloud API, in the section: For more information on the API’s features, you can consult the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster -We will add a farm of HTTP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of HTTP servers to our service, which is the part that balances traffic on the servers. -### Via the OVHCloud Control Panel. +### Via the OVHCloud Control Panel Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, click on the `Add a server farm`{.action} button. +In the `Server clusters`{.action} tab, click on the `Add a server cluster`{.action} button. Fill in the fields. The only mandatory fields for a basic configuration are *Protocol* and *Datacentre*. We recommend explicitly defining a *Port* (generally port 80 for a web service). If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end, and the probes will not be able to work as intended. -If you add several servers to your farm, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. +If you add several servers to your cluster, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. -![Add a server farm via the Control Panel](images/add_backend.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_backend.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Server farms`{.action} tab. +Your server cluster should appear in the list, in the `Server clusters`{.action} tab. -![Details of the server farm created](images/resume_backend.png){.thumbnail} +![Details of the server cluster created](images/resume_backend.png){.thumbnail} ### Via the API -- List of HTTP server farms: +- List of HTTP server clusters: > [!api] > @@ -91,21 +91,21 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Add a new HTTP server farm: +- Add a new HTTP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -114,27 +114,27 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the OVHcloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Server clusters`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. +Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Server farm`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Server cluster`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -171,7 +171,7 @@ Your server should appear in the server list, in the `Server farm`{.action} tab, ## Add a front-end. -We will now add a `front-end` to our service, and connect it to our server farm. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. +We will now add a `front-end` to our service, and connect it to our server cluster. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. ### Via the OVHcloud Control Panel. diff --git a/pages/network/load_balancer/create_http_https/guide.en-sg.md b/pages/network/load_balancer/create_http_https/guide.en-sg.md index 8fb7329b659..83107cdb85b 100644 --- a/pages/network/load_balancer/create_http_https/guide.en-sg.md +++ b/pages/network/load_balancer/create_http_https/guide.en-sg.md @@ -1,20 +1,20 @@ --- title: 'Configuring a HTTP/HTTPS OVH Load Balancer service' excerpt: 'Find out how to configure an OVH Load Balancer service' -updated: 2023-11-22 +updated: 2025-07-04 --- ## Objective The purpose of this guide is to help you create your first HTTP/HTTPS service with the new OVHcloud Load Balancer solution. Here, we will set up a basic OVHcloud Load Balancer service configuration to balance the HTTP load for a service like a website. -A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP farm. This farm can have one or more servers, depending on the configuration you have chosen/adapted. +A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP cluster. This cluster can have one or more servers, depending on the configuration you have chosen/adapted. As a reminder, the OVHcloud Load Balancer has four primary components: - `front-ends` - server `farms` and their `servers` -- the advanced `routes` between the front-ends and server farms +- the advanced `routes` between the front-ends and server clusters - `SSL/TLS` connections that can encrypt TCP and/or HTTP connections **This guide will show you how to configure an OVHcloud Load Balancer Service.** @@ -22,7 +22,7 @@ As a reminder, the OVHcloud Load Balancer has four primary components: ## Requirements - an OVHcloud Load Balancer -- the ability to add and configure a farm, a server, a front-end and an SSL certificate +- the ability to add and configure a cluster, a server, a front-end and an SSL certificate ## Introduction @@ -35,7 +35,7 @@ If you have not done so already, we recommend reading a general introduction to > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server farms in order to configure the front-end’s default farm. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server clusters in order to configure the front-end’s default cluster. > In the control panel of the load balancer, you will see the features detailed below: @@ -53,31 +53,31 @@ Similarly, this can be done via the OVHcloud API, in the section: For more information on the API’s features, you can consult the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of HTTP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of HTTP servers to our service, which is the part that balances traffic on the servers. ### Via the OVHCloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, click on the `Add a server farm`{.action} button. +In the `Server clusters`{.action} tab, click on the `Add a server cluster`{.action} button. Fill in the fields. The only mandatory fields for a basic configuration are *Protocol* and *Datacentre*. We recommend explicitly defining a *Port* (generally port 80 for a web service). If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end, and the probes will not be able to work as intended. -If you add several servers to your farm, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. +If you add several servers to your cluster, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. -![Add a server farm via the Control Panel](images/add_backend.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_backend.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Server farms`{.action} tab. +Your server cluster should appear in the list, in the `Server clusters`{.action} tab. -![Details of the server farm created](images/resume_backend.png){.thumbnail} +![Details of the server cluster created](images/resume_backend.png){.thumbnail} ### Via the API -- List of HTTP server farms: +- List of HTTP server clusters: > [!api] > @@ -91,21 +91,21 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Add a new HTTP server farm: +- Add a new HTTP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -114,27 +114,27 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the OVHcloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Server clusters`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. +Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Server farm`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Server cluster`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -171,7 +171,7 @@ Your server should appear in the server list, in the `Server farm`{.action} tab, ## Add a front-end. -We will now add a `front-end` to our service, and connect it to our server farm. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. +We will now add a `front-end` to our service, and connect it to our server cluster. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. ### Via the OVHcloud Control Panel. diff --git a/pages/network/load_balancer/create_http_https/guide.en-us.md b/pages/network/load_balancer/create_http_https/guide.en-us.md index 8fb7329b659..83107cdb85b 100644 --- a/pages/network/load_balancer/create_http_https/guide.en-us.md +++ b/pages/network/load_balancer/create_http_https/guide.en-us.md @@ -1,20 +1,20 @@ --- title: 'Configuring a HTTP/HTTPS OVH Load Balancer service' excerpt: 'Find out how to configure an OVH Load Balancer service' -updated: 2023-11-22 +updated: 2025-07-04 --- ## Objective The purpose of this guide is to help you create your first HTTP/HTTPS service with the new OVHcloud Load Balancer solution. Here, we will set up a basic OVHcloud Load Balancer service configuration to balance the HTTP load for a service like a website. -A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP farm. This farm can have one or more servers, depending on the configuration you have chosen/adapted. +A front-end will be created to listen on port 80, while another listens on port 443 with an SSL/TLS certificate. These front-ends will be configured to direct their traffic to a common HTTP cluster. This cluster can have one or more servers, depending on the configuration you have chosen/adapted. As a reminder, the OVHcloud Load Balancer has four primary components: - `front-ends` - server `farms` and their `servers` -- the advanced `routes` between the front-ends and server farms +- the advanced `routes` between the front-ends and server clusters - `SSL/TLS` connections that can encrypt TCP and/or HTTP connections **This guide will show you how to configure an OVHcloud Load Balancer Service.** @@ -22,7 +22,7 @@ As a reminder, the OVHcloud Load Balancer has four primary components: ## Requirements - an OVHcloud Load Balancer -- the ability to add and configure a farm, a server, a front-end and an SSL certificate +- the ability to add and configure a cluster, a server, a front-end and an SSL certificate ## Introduction @@ -35,7 +35,7 @@ If you have not done so already, we recommend reading a general introduction to > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server farms in order to configure the front-end’s default farm. +> The order in which elements are created is important. In particular, the server clusters must be configured before we can attach an SSL/TLS certificate or servers to them. The front-ends must be configured after the server clusters in order to configure the front-end’s default cluster. > In the control panel of the load balancer, you will see the features detailed below: @@ -53,31 +53,31 @@ Similarly, this can be done via the OVHcloud API, in the section: For more information on the API’s features, you can consult the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} -## Add a server farm. +## Add a server cluster. -We will add a farm of HTTP servers to our service, which is the part that balances traffic on the servers. +We will add a cluster of HTTP servers to our service, which is the part that balances traffic on the servers. ### Via the OVHCloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, click on the `Add a server farm`{.action} button. +In the `Server clusters`{.action} tab, click on the `Add a server cluster`{.action} button. Fill in the fields. The only mandatory fields for a basic configuration are *Protocol* and *Datacentre*. We recommend explicitly defining a *Port* (generally port 80 for a web service). If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end, and the probes will not be able to work as intended. -If you add several servers to your farm, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. +If you add several servers to your cluster, we advise configuring an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, so that your web users are not affected. -![Add a server farm via the Control Panel](images/add_backend.png){.thumbnail} +![Add a server cluster via the Control Panel](images/add_backend.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server farm should appear in the list, in the `Server farms`{.action} tab. +Your server cluster should appear in the list, in the `Server clusters`{.action} tab. -![Details of the server farm created](images/resume_backend.png){.thumbnail} +![Details of the server cluster created](images/resume_backend.png){.thumbnail} ### Via the API -- List of HTTP server farms: +- List of HTTP server clusters: > [!api] > @@ -91,21 +91,21 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Add a new HTTP server farm: +- Add a new HTTP server cluster: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -- Modify a specific server farm: +- Modify a specific server cluster: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId} > -- Delete a specific server farm: +- Delete a specific server cluster: > [!api] > @@ -114,27 +114,27 @@ Your server farm should appear in the list, in the `Server farms`{.action} tab. ## Add a server. -We will now add a server to our server farm. +We will now add a server to our server cluster. ### Via the OVHcloud Control Panel. Log into the [OVHcloud Control Panel](/links/manager), click `Network`{.action} in the left-hand menu, then `Load Balancer`. Click on your load balancer service. -In the `Server farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Server clusters`{.action} tab, select the cluster you want to add a server to by clicking on the corresponding line. The list of servers already configured in the cluster will appear beneath the list of clusters, along with the `Add a server`{.action} button. Click on this button to add a new server. -Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. +Only the *IPv4 address* field is mandatory. If a server does not use the same port as the one defined earlier in the cluster, you may overload it by configuring a server. However, to keep the configuration as standardised and easy to maintain as possible, we recommend only using this parameter in advanced cases. -![Add a server to a farm.](images/add_server.png){.thumbnail} +![Add a server to a cluster.](images/add_server.png){.thumbnail} Click `Add`{.action} once you have filled in the fields. -Your server should appear in the server list, in the `Server farm`{.action} tab, just below the list of farms. +Your server should appear in the server list, in the `Server cluster`{.action} tab, just below the list of clusters. ![Details of the server created.](images/resume_server.png){.thumbnail} ### Via the API -- List of servers in the farm: +- List of servers in the cluster: > [!api] > @@ -171,7 +171,7 @@ Your server should appear in the server list, in the `Server farm`{.action} tab, ## Add a front-end. -We will now add a `front-end` to our service, and connect it to our server farm. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. +We will now add a `front-end` to our service, and connect it to our server cluster. The front-end is the part of your OVHcloud Load Balancer that exposes your service on the internet. First, we will only configure it in HTTP, without an SSL/TLS certificate. ### Via the OVHcloud Control Panel. diff --git a/pages/network/load_balancer/create_probes/guide.en-asia.md b/pages/network/load_balancer/create_probes/guide.en-asia.md index cebe6b13d2f..00195fb6e58 100644 --- a/pages/network/load_balancer/create_probes/guide.en-asia.md +++ b/pages/network/load_balancer/create_probes/guide.en-asia.md @@ -1,14 +1,14 @@ --- title: 'Working with probes' excerpt: 'Find out about the general principles behind probes, and why they are used' -updated: 2019-02-12 +updated: 2025-07-04 --- ## Objective -With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination farm. +With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination cluster. -There may be instances where a server in your farm becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. +There may be instances where a server in your cluster becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. However, the reasons behind certain types of unavailability can be harder to pinpoint. For example, if a new version of code is being deployed, the application may momentarily experience a glitch, and return a 500 error. In this particular case, a solution would be to mark the servers concerned as unavailable in the API before you begin the maintenance work, apply the configuration and update, then mark the server as available again. This method is not ideal, but it works. For more information on deploying a blue-green architecture with an OVH Load Balancer, please read our guide: . @@ -20,7 +20,7 @@ Since this service is still very new, its basic features are only available in t ## Requirements -- a correctly configured OVH Load Balancer, with farms and servers set +- a correctly configured OVH Load Balancer, with clusters and servers set ## Instructions @@ -28,7 +28,7 @@ Since this service is still very new, its basic features are only available in t The API for probes in the OVH Load Balancer is designed to be flexible and scalable. -The probes can be configured directly on the farms. All of the servers from a single farm will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single farm. +The probes can be configured directly on the clusters. All of the servers from a single cluster will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single cluster. You can view the list of available probes and their settings with the following API call: @@ -39,7 +39,7 @@ You can view the list of available probes and their settings with the following For more information on this call, please read the *Available probes* section at the bottom of this guide. -The probes in this list can be configured on `http` and `tcp` farms via the following calls: +The probes in this list can be configured on `http` and `tcp` clusters via the following calls: > [!api] > @@ -67,14 +67,14 @@ For more information on these calls, please read the *Probe configuration* secti #### Check if the server accepts TCP connections. -This is the simplest method to set up. It is compatible with `tcp` and `http` farms. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. +This is the simplest method to set up. It is compatible with `tcp` and `http` clusters. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. In practice, this gives a probe: |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|"tcp"| All other probe fields can keep their default values. Just apply the configuration to the zone concerned, and the probe will begin to work. @@ -88,7 +88,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.method|GET| |probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| @@ -99,7 +99,7 @@ All other probe fields can keep their default values. Finally, apply the configu #### Use an external HTTP test. -What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the farm. +What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the cluster. If you are using a `tcp` probe, it will manage to connect. As a result, it will consider the service to be available, even though this is not the case. @@ -110,7 +110,7 @@ For example, in this situation, you can have a HTTP server on port 8080\. It wil |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.port|8080| |probe.method|GET| @@ -131,7 +131,7 @@ Just apply the configuration to the zone concerned, and the probe will begin to ##### Configure a probe. -Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. +Probes can be configured on a new cluster (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. > [!faq] > @@ -177,7 +177,7 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **port** >> >> ->> >> > The port that the probe must use, if it is different to the port configured on the farm. +>> >> > The port that the probe must use, if it is different to the port configured on the cluster. >> >> > This enables you to delegate a server’s status validation to a separate service on the machine, and carry out arbitrary probes. >> > >> >> **method** @@ -203,21 +203,21 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **forceSsl** >> >> ->> >> > This defines whether the probe must work in SSL/TLS, even if the farm is configured to connect via standard TCP. +>> >> > This defines whether the probe must work in SSL/TLS, even if the cluster is configured to connect via standard TCP. >> >> > This can be useful when, for example, your OVH Load Balancer is configured to monitor HTTPS traffic in TCP without decrypting it. > Other settings can be edited via this call. Since this guide focuses on probes, they are not documented here. -If a port other than the farm’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured farm to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. +If a port other than the cluster’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured cluster to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. > [!warning] > -> When a probe is configured on a farm, it must be activated on the servers. +> When a probe is configured on a cluster, it must be activated on the servers. > ##### Activate probes on a server. -For a probe to be active, it must be configured on the farm and activated on the servers concerned. With this call, you can activate the probe being taken into account: +For a probe to be active, it must be configured on the cluster and activated on the servers concerned. With this call, you can activate the probe being taken into account: > [!faq] > @@ -348,7 +348,7 @@ This probe attempts to establish a HTTP connection to the server. If the server |URL|URL in the form: \[\[https?://]www.example.com]/path/to/check| |matches|`default`, `contains` or `matches`| -If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the farm’s SSL configuration. +If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the cluster’s SSL configuration. > [!primary] > @@ -406,9 +406,9 @@ This probe attempts to establish a TCP connection on port 79 of your server, and ## Via the OVH Control Panel. -You can configure probes when you add (or modify) a server farm, in advanced settings. +You can configure probes when you add (or modify) a server cluster, in advanced settings. -![Advanced settings for a farm](images/farm_advanced_settings.png){.thumbnail} +![Advanced settings for a cluster](images/farm_advanced_settings.png){.thumbnail} This is how you access the probe type’s configuration. diff --git a/pages/network/load_balancer/create_probes/guide.en-au.md b/pages/network/load_balancer/create_probes/guide.en-au.md index cebe6b13d2f..00195fb6e58 100644 --- a/pages/network/load_balancer/create_probes/guide.en-au.md +++ b/pages/network/load_balancer/create_probes/guide.en-au.md @@ -1,14 +1,14 @@ --- title: 'Working with probes' excerpt: 'Find out about the general principles behind probes, and why they are used' -updated: 2019-02-12 +updated: 2025-07-04 --- ## Objective -With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination farm. +With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination cluster. -There may be instances where a server in your farm becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. +There may be instances where a server in your cluster becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. However, the reasons behind certain types of unavailability can be harder to pinpoint. For example, if a new version of code is being deployed, the application may momentarily experience a glitch, and return a 500 error. In this particular case, a solution would be to mark the servers concerned as unavailable in the API before you begin the maintenance work, apply the configuration and update, then mark the server as available again. This method is not ideal, but it works. For more information on deploying a blue-green architecture with an OVH Load Balancer, please read our guide: . @@ -20,7 +20,7 @@ Since this service is still very new, its basic features are only available in t ## Requirements -- a correctly configured OVH Load Balancer, with farms and servers set +- a correctly configured OVH Load Balancer, with clusters and servers set ## Instructions @@ -28,7 +28,7 @@ Since this service is still very new, its basic features are only available in t The API for probes in the OVH Load Balancer is designed to be flexible and scalable. -The probes can be configured directly on the farms. All of the servers from a single farm will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single farm. +The probes can be configured directly on the clusters. All of the servers from a single cluster will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single cluster. You can view the list of available probes and their settings with the following API call: @@ -39,7 +39,7 @@ You can view the list of available probes and their settings with the following For more information on this call, please read the *Available probes* section at the bottom of this guide. -The probes in this list can be configured on `http` and `tcp` farms via the following calls: +The probes in this list can be configured on `http` and `tcp` clusters via the following calls: > [!api] > @@ -67,14 +67,14 @@ For more information on these calls, please read the *Probe configuration* secti #### Check if the server accepts TCP connections. -This is the simplest method to set up. It is compatible with `tcp` and `http` farms. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. +This is the simplest method to set up. It is compatible with `tcp` and `http` clusters. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. In practice, this gives a probe: |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|"tcp"| All other probe fields can keep their default values. Just apply the configuration to the zone concerned, and the probe will begin to work. @@ -88,7 +88,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.method|GET| |probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| @@ -99,7 +99,7 @@ All other probe fields can keep their default values. Finally, apply the configu #### Use an external HTTP test. -What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the farm. +What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the cluster. If you are using a `tcp` probe, it will manage to connect. As a result, it will consider the service to be available, even though this is not the case. @@ -110,7 +110,7 @@ For example, in this situation, you can have a HTTP server on port 8080\. It wil |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.port|8080| |probe.method|GET| @@ -131,7 +131,7 @@ Just apply the configuration to the zone concerned, and the probe will begin to ##### Configure a probe. -Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. +Probes can be configured on a new cluster (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. > [!faq] > @@ -177,7 +177,7 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **port** >> >> ->> >> > The port that the probe must use, if it is different to the port configured on the farm. +>> >> > The port that the probe must use, if it is different to the port configured on the cluster. >> >> > This enables you to delegate a server’s status validation to a separate service on the machine, and carry out arbitrary probes. >> > >> >> **method** @@ -203,21 +203,21 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **forceSsl** >> >> ->> >> > This defines whether the probe must work in SSL/TLS, even if the farm is configured to connect via standard TCP. +>> >> > This defines whether the probe must work in SSL/TLS, even if the cluster is configured to connect via standard TCP. >> >> > This can be useful when, for example, your OVH Load Balancer is configured to monitor HTTPS traffic in TCP without decrypting it. > Other settings can be edited via this call. Since this guide focuses on probes, they are not documented here. -If a port other than the farm’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured farm to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. +If a port other than the cluster’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured cluster to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. > [!warning] > -> When a probe is configured on a farm, it must be activated on the servers. +> When a probe is configured on a cluster, it must be activated on the servers. > ##### Activate probes on a server. -For a probe to be active, it must be configured on the farm and activated on the servers concerned. With this call, you can activate the probe being taken into account: +For a probe to be active, it must be configured on the cluster and activated on the servers concerned. With this call, you can activate the probe being taken into account: > [!faq] > @@ -348,7 +348,7 @@ This probe attempts to establish a HTTP connection to the server. If the server |URL|URL in the form: \[\[https?://]www.example.com]/path/to/check| |matches|`default`, `contains` or `matches`| -If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the farm’s SSL configuration. +If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the cluster’s SSL configuration. > [!primary] > @@ -406,9 +406,9 @@ This probe attempts to establish a TCP connection on port 79 of your server, and ## Via the OVH Control Panel. -You can configure probes when you add (or modify) a server farm, in advanced settings. +You can configure probes when you add (or modify) a server cluster, in advanced settings. -![Advanced settings for a farm](images/farm_advanced_settings.png){.thumbnail} +![Advanced settings for a cluster](images/farm_advanced_settings.png){.thumbnail} This is how you access the probe type’s configuration. diff --git a/pages/network/load_balancer/create_probes/guide.en-ca.md b/pages/network/load_balancer/create_probes/guide.en-ca.md index cebe6b13d2f..ab75d4a0602 100644 --- a/pages/network/load_balancer/create_probes/guide.en-ca.md +++ b/pages/network/load_balancer/create_probes/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: 'Working with probes' excerpt: 'Find out about the general principles behind probes, and why they are used' -updated: 2019-02-12 +updated: 2025-07-04 --- ## Objective diff --git a/pages/network/load_balancer/create_probes/guide.en-gb.md b/pages/network/load_balancer/create_probes/guide.en-gb.md index cebe6b13d2f..00195fb6e58 100644 --- a/pages/network/load_balancer/create_probes/guide.en-gb.md +++ b/pages/network/load_balancer/create_probes/guide.en-gb.md @@ -1,14 +1,14 @@ --- title: 'Working with probes' excerpt: 'Find out about the general principles behind probes, and why they are used' -updated: 2019-02-12 +updated: 2025-07-04 --- ## Objective -With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination farm. +With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination cluster. -There may be instances where a server in your farm becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. +There may be instances where a server in your cluster becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. However, the reasons behind certain types of unavailability can be harder to pinpoint. For example, if a new version of code is being deployed, the application may momentarily experience a glitch, and return a 500 error. In this particular case, a solution would be to mark the servers concerned as unavailable in the API before you begin the maintenance work, apply the configuration and update, then mark the server as available again. This method is not ideal, but it works. For more information on deploying a blue-green architecture with an OVH Load Balancer, please read our guide: . @@ -20,7 +20,7 @@ Since this service is still very new, its basic features are only available in t ## Requirements -- a correctly configured OVH Load Balancer, with farms and servers set +- a correctly configured OVH Load Balancer, with clusters and servers set ## Instructions @@ -28,7 +28,7 @@ Since this service is still very new, its basic features are only available in t The API for probes in the OVH Load Balancer is designed to be flexible and scalable. -The probes can be configured directly on the farms. All of the servers from a single farm will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single farm. +The probes can be configured directly on the clusters. All of the servers from a single cluster will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single cluster. You can view the list of available probes and their settings with the following API call: @@ -39,7 +39,7 @@ You can view the list of available probes and their settings with the following For more information on this call, please read the *Available probes* section at the bottom of this guide. -The probes in this list can be configured on `http` and `tcp` farms via the following calls: +The probes in this list can be configured on `http` and `tcp` clusters via the following calls: > [!api] > @@ -67,14 +67,14 @@ For more information on these calls, please read the *Probe configuration* secti #### Check if the server accepts TCP connections. -This is the simplest method to set up. It is compatible with `tcp` and `http` farms. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. +This is the simplest method to set up. It is compatible with `tcp` and `http` clusters. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. In practice, this gives a probe: |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|"tcp"| All other probe fields can keep their default values. Just apply the configuration to the zone concerned, and the probe will begin to work. @@ -88,7 +88,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.method|GET| |probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| @@ -99,7 +99,7 @@ All other probe fields can keep their default values. Finally, apply the configu #### Use an external HTTP test. -What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the farm. +What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the cluster. If you are using a `tcp` probe, it will manage to connect. As a result, it will consider the service to be available, even though this is not the case. @@ -110,7 +110,7 @@ For example, in this situation, you can have a HTTP server on port 8080\. It wil |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.port|8080| |probe.method|GET| @@ -131,7 +131,7 @@ Just apply the configuration to the zone concerned, and the probe will begin to ##### Configure a probe. -Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. +Probes can be configured on a new cluster (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. > [!faq] > @@ -177,7 +177,7 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **port** >> >> ->> >> > The port that the probe must use, if it is different to the port configured on the farm. +>> >> > The port that the probe must use, if it is different to the port configured on the cluster. >> >> > This enables you to delegate a server’s status validation to a separate service on the machine, and carry out arbitrary probes. >> > >> >> **method** @@ -203,21 +203,21 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **forceSsl** >> >> ->> >> > This defines whether the probe must work in SSL/TLS, even if the farm is configured to connect via standard TCP. +>> >> > This defines whether the probe must work in SSL/TLS, even if the cluster is configured to connect via standard TCP. >> >> > This can be useful when, for example, your OVH Load Balancer is configured to monitor HTTPS traffic in TCP without decrypting it. > Other settings can be edited via this call. Since this guide focuses on probes, they are not documented here. -If a port other than the farm’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured farm to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. +If a port other than the cluster’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured cluster to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. > [!warning] > -> When a probe is configured on a farm, it must be activated on the servers. +> When a probe is configured on a cluster, it must be activated on the servers. > ##### Activate probes on a server. -For a probe to be active, it must be configured on the farm and activated on the servers concerned. With this call, you can activate the probe being taken into account: +For a probe to be active, it must be configured on the cluster and activated on the servers concerned. With this call, you can activate the probe being taken into account: > [!faq] > @@ -348,7 +348,7 @@ This probe attempts to establish a HTTP connection to the server. If the server |URL|URL in the form: \[\[https?://]www.example.com]/path/to/check| |matches|`default`, `contains` or `matches`| -If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the farm’s SSL configuration. +If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the cluster’s SSL configuration. > [!primary] > @@ -406,9 +406,9 @@ This probe attempts to establish a TCP connection on port 79 of your server, and ## Via the OVH Control Panel. -You can configure probes when you add (or modify) a server farm, in advanced settings. +You can configure probes when you add (or modify) a server cluster, in advanced settings. -![Advanced settings for a farm](images/farm_advanced_settings.png){.thumbnail} +![Advanced settings for a cluster](images/farm_advanced_settings.png){.thumbnail} This is how you access the probe type’s configuration. diff --git a/pages/network/load_balancer/create_probes/guide.en-sg.md b/pages/network/load_balancer/create_probes/guide.en-sg.md index cebe6b13d2f..00195fb6e58 100644 --- a/pages/network/load_balancer/create_probes/guide.en-sg.md +++ b/pages/network/load_balancer/create_probes/guide.en-sg.md @@ -1,14 +1,14 @@ --- title: 'Working with probes' excerpt: 'Find out about the general principles behind probes, and why they are used' -updated: 2019-02-12 +updated: 2025-07-04 --- ## Objective -With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination farm. +With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination cluster. -There may be instances where a server in your farm becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. +There may be instances where a server in your cluster becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. However, the reasons behind certain types of unavailability can be harder to pinpoint. For example, if a new version of code is being deployed, the application may momentarily experience a glitch, and return a 500 error. In this particular case, a solution would be to mark the servers concerned as unavailable in the API before you begin the maintenance work, apply the configuration and update, then mark the server as available again. This method is not ideal, but it works. For more information on deploying a blue-green architecture with an OVH Load Balancer, please read our guide: . @@ -20,7 +20,7 @@ Since this service is still very new, its basic features are only available in t ## Requirements -- a correctly configured OVH Load Balancer, with farms and servers set +- a correctly configured OVH Load Balancer, with clusters and servers set ## Instructions @@ -28,7 +28,7 @@ Since this service is still very new, its basic features are only available in t The API for probes in the OVH Load Balancer is designed to be flexible and scalable. -The probes can be configured directly on the farms. All of the servers from a single farm will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single farm. +The probes can be configured directly on the clusters. All of the servers from a single cluster will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single cluster. You can view the list of available probes and their settings with the following API call: @@ -39,7 +39,7 @@ You can view the list of available probes and their settings with the following For more information on this call, please read the *Available probes* section at the bottom of this guide. -The probes in this list can be configured on `http` and `tcp` farms via the following calls: +The probes in this list can be configured on `http` and `tcp` clusters via the following calls: > [!api] > @@ -67,14 +67,14 @@ For more information on these calls, please read the *Probe configuration* secti #### Check if the server accepts TCP connections. -This is the simplest method to set up. It is compatible with `tcp` and `http` farms. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. +This is the simplest method to set up. It is compatible with `tcp` and `http` clusters. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. In practice, this gives a probe: |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|"tcp"| All other probe fields can keep their default values. Just apply the configuration to the zone concerned, and the probe will begin to work. @@ -88,7 +88,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.method|GET| |probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| @@ -99,7 +99,7 @@ All other probe fields can keep their default values. Finally, apply the configu #### Use an external HTTP test. -What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the farm. +What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the cluster. If you are using a `tcp` probe, it will manage to connect. As a result, it will consider the service to be available, even though this is not the case. @@ -110,7 +110,7 @@ For example, in this situation, you can have a HTTP server on port 8080\. It wil |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.port|8080| |probe.method|GET| @@ -131,7 +131,7 @@ Just apply the configuration to the zone concerned, and the probe will begin to ##### Configure a probe. -Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. +Probes can be configured on a new cluster (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. > [!faq] > @@ -177,7 +177,7 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **port** >> >> ->> >> > The port that the probe must use, if it is different to the port configured on the farm. +>> >> > The port that the probe must use, if it is different to the port configured on the cluster. >> >> > This enables you to delegate a server’s status validation to a separate service on the machine, and carry out arbitrary probes. >> > >> >> **method** @@ -203,21 +203,21 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **forceSsl** >> >> ->> >> > This defines whether the probe must work in SSL/TLS, even if the farm is configured to connect via standard TCP. +>> >> > This defines whether the probe must work in SSL/TLS, even if the cluster is configured to connect via standard TCP. >> >> > This can be useful when, for example, your OVH Load Balancer is configured to monitor HTTPS traffic in TCP without decrypting it. > Other settings can be edited via this call. Since this guide focuses on probes, they are not documented here. -If a port other than the farm’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured farm to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. +If a port other than the cluster’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured cluster to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. > [!warning] > -> When a probe is configured on a farm, it must be activated on the servers. +> When a probe is configured on a cluster, it must be activated on the servers. > ##### Activate probes on a server. -For a probe to be active, it must be configured on the farm and activated on the servers concerned. With this call, you can activate the probe being taken into account: +For a probe to be active, it must be configured on the cluster and activated on the servers concerned. With this call, you can activate the probe being taken into account: > [!faq] > @@ -348,7 +348,7 @@ This probe attempts to establish a HTTP connection to the server. If the server |URL|URL in the form: \[\[https?://]www.example.com]/path/to/check| |matches|`default`, `contains` or `matches`| -If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the farm’s SSL configuration. +If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the cluster’s SSL configuration. > [!primary] > @@ -406,9 +406,9 @@ This probe attempts to establish a TCP connection on port 79 of your server, and ## Via the OVH Control Panel. -You can configure probes when you add (or modify) a server farm, in advanced settings. +You can configure probes when you add (or modify) a server cluster, in advanced settings. -![Advanced settings for a farm](images/farm_advanced_settings.png){.thumbnail} +![Advanced settings for a cluster](images/farm_advanced_settings.png){.thumbnail} This is how you access the probe type’s configuration. diff --git a/pages/network/load_balancer/create_probes/guide.en-us.md b/pages/network/load_balancer/create_probes/guide.en-us.md index cebe6b13d2f..00195fb6e58 100644 --- a/pages/network/load_balancer/create_probes/guide.en-us.md +++ b/pages/network/load_balancer/create_probes/guide.en-us.md @@ -1,14 +1,14 @@ --- title: 'Working with probes' excerpt: 'Find out about the general principles behind probes, and why they are used' -updated: 2019-02-12 +updated: 2025-07-04 --- ## Objective -With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination farm. +With the OVH Load Balancer, you can distribute a front-end’s incoming traffic across a set of servers in a destination cluster. -There may be instances where a server in your farm becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. +There may be instances where a server in your cluster becomes unavailable for a number of reasons, including oversaturation, an incident, or scheduled maintenance. When the OVH Load Balancer detects a connection error, it will try to redirect traffic to another server. The connection will be slower, but it will continue to work. However, the reasons behind certain types of unavailability can be harder to pinpoint. For example, if a new version of code is being deployed, the application may momentarily experience a glitch, and return a 500 error. In this particular case, a solution would be to mark the servers concerned as unavailable in the API before you begin the maintenance work, apply the configuration and update, then mark the server as available again. This method is not ideal, but it works. For more information on deploying a blue-green architecture with an OVH Load Balancer, please read our guide: . @@ -20,7 +20,7 @@ Since this service is still very new, its basic features are only available in t ## Requirements -- a correctly configured OVH Load Balancer, with farms and servers set +- a correctly configured OVH Load Balancer, with clusters and servers set ## Instructions @@ -28,7 +28,7 @@ Since this service is still very new, its basic features are only available in t The API for probes in the OVH Load Balancer is designed to be flexible and scalable. -The probes can be configured directly on the farms. All of the servers from a single farm will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single farm. +The probes can be configured directly on the clusters. All of the servers from a single cluster will have exactly the same probe applied. However, probe activation and deactivation is specific for each server. As a result, it is possible to only monitor certain servers within a single cluster. You can view the list of available probes and their settings with the following API call: @@ -39,7 +39,7 @@ You can view the list of available probes and their settings with the following For more information on this call, please read the *Available probes* section at the bottom of this guide. -The probes in this list can be configured on `http` and `tcp` farms via the following calls: +The probes in this list can be configured on `http` and `tcp` clusters via the following calls: > [!api] > @@ -67,14 +67,14 @@ For more information on these calls, please read the *Probe configuration* secti #### Check if the server accepts TCP connections. -This is the simplest method to set up. It is compatible with `tcp` and `http` farms. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. +This is the simplest method to set up. It is compatible with `tcp` and `http` clusters. If no other probes are configured, you can activate it to start. It works by periodically attempting to establish a connection on each of your servers. If the connection fails twice in a row, the server is put aside until it responds again. In practice, this gives a probe: |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|"tcp"| All other probe fields can keep their default values. Just apply the configuration to the zone concerned, and the probe will begin to work. @@ -88,7 +88,7 @@ In practice, if you want to configure the probe to send a "GET" request on [http |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.method|GET| |probe.url|[http://api.example.com/status](http://api.example.com/status){.external}| @@ -99,7 +99,7 @@ All other probe fields can keep their default values. Finally, apply the configu #### Use an external HTTP test. -What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the farm. +What happens if, for example, your service is an IMAP server that relies on an LDAP server for authentication? The server may accept connections, but experience a temporary connection issue with the LDAP server. If this happens, the customers redirected to this server would be able to connect, but wouldn’t be able to authenticate. As a result, the server would need to be removed from the cluster. If you are using a `tcp` probe, it will manage to connect. As a result, it will consider the service to be available, even though this is not the case. @@ -110,7 +110,7 @@ For example, in this situation, you can have a HTTP server on port 8080\. It wil |Field|Value and description| |---|---| |serviceName|Your OVH Load Balancer ID| -|farmId|Your TCP or HTTP farm| +|farmId|Your TCP or HTTP cluster| |probe.type|http| |probe.port|8080| |probe.method|GET| @@ -131,7 +131,7 @@ Just apply the configuration to the zone concerned, and the probe will begin to ##### Configure a probe. -Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. +Probes can be configured on a new cluster (`POST`) or an existing one (`PUT`). Since the two methods are equivalent, only the second (`PUT`) method is presented here. > [!faq] > @@ -177,7 +177,7 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **port** >> >> ->> >> > The port that the probe must use, if it is different to the port configured on the farm. +>> >> > The port that the probe must use, if it is different to the port configured on the cluster. >> >> > This enables you to delegate a server’s status validation to a separate service on the machine, and carry out arbitrary probes. >> > >> >> **method** @@ -203,21 +203,21 @@ Probes can be configured on a new farm (`POST`) or an existing one (`PUT`). Sinc >> > >> >> **forceSsl** >> >> ->> >> > This defines whether the probe must work in SSL/TLS, even if the farm is configured to connect via standard TCP. +>> >> > This defines whether the probe must work in SSL/TLS, even if the cluster is configured to connect via standard TCP. >> >> > This can be useful when, for example, your OVH Load Balancer is configured to monitor HTTPS traffic in TCP without decrypting it. > Other settings can be edited via this call. Since this guide focuses on probes, they are not documented here. -If a port other than the farm’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured farm to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. +If a port other than the cluster’s base port is configured on the probe, the `proxyprotocol` and `ssl` settings are reset. As an example, we will take a configured cluster to use `proxyprotocol` on **port 4242**, and an associated probe using **port 8080**. The probe will not send the `proxyprotocol` header when it connects on **port 8080**. The same goes for `ssl`, but it can be forced. > [!warning] > -> When a probe is configured on a farm, it must be activated on the servers. +> When a probe is configured on a cluster, it must be activated on the servers. > ##### Activate probes on a server. -For a probe to be active, it must be configured on the farm and activated on the servers concerned. With this call, you can activate the probe being taken into account: +For a probe to be active, it must be configured on the cluster and activated on the servers concerned. With this call, you can activate the probe being taken into account: > [!faq] > @@ -348,7 +348,7 @@ This probe attempts to establish a HTTP connection to the server. If the server |URL|URL in the form: \[\[https?://]www.example.com]/path/to/check| |matches|`default`, `contains` or `matches`| -If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the farm’s SSL configuration. +If the URL is specified, the domain name and protocol are operational. If a domain name is specified, the “Host” field of the request will be filled in, and the request will be sent to HTTP/1.1. If the protocol is specified, it must be consistent with the cluster’s SSL configuration. > [!primary] > @@ -406,9 +406,9 @@ This probe attempts to establish a TCP connection on port 79 of your server, and ## Via the OVH Control Panel. -You can configure probes when you add (or modify) a server farm, in advanced settings. +You can configure probes when you add (or modify) a server cluster, in advanced settings. -![Advanced settings for a farm](images/farm_advanced_settings.png){.thumbnail} +![Advanced settings for a cluster](images/farm_advanced_settings.png){.thumbnail} This is how you access the probe type’s configuration. diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-asia.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-asia.md index 95e82fe5bc4..c71907b8d17 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-asia.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: ProxyProtocol get Source IP excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2018-10-12 +updated: 2025-07-04 --- ## Introduction @@ -76,7 +76,7 @@ You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren ## Configuration ### Add backends -Create a new farm for each port on backend. +Create a new cluster for each port on backend. > [!api] > diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-au.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-au.md index 95e82fe5bc4..c71907b8d17 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-au.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-au.md @@ -1,7 +1,7 @@ --- title: ProxyProtocol get Source IP excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2018-10-12 +updated: 2025-07-04 --- ## Introduction @@ -76,7 +76,7 @@ You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren ## Configuration ### Add backends -Create a new farm for each port on backend. +Create a new cluster for each port on backend. > [!api] > diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-ca.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-ca.md index 95e82fe5bc4..c71907b8d17 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-ca.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: ProxyProtocol get Source IP excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2018-10-12 +updated: 2025-07-04 --- ## Introduction @@ -76,7 +76,7 @@ You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren ## Configuration ### Add backends -Create a new farm for each port on backend. +Create a new cluster for each port on backend. > [!api] > diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md index aa9173af899..bc87d65174c 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'ProxyProtocol get Source IP' excerpt: 'Get real visitor IP using OVH Load Balancer with ProxyProtocol' -updated: 2018-10-12 +updated: 2025-07-04 --- ## Introduction @@ -76,7 +76,7 @@ You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren ## Configuration ### Add backends -Create a new farm for each port on backend. +Create a new cluster for each port on backend. > [!api] > diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-sg.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-sg.md index 95e82fe5bc4..c71907b8d17 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-sg.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: ProxyProtocol get Source IP excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2018-10-12 +updated: 2025-07-04 --- ## Introduction @@ -76,7 +76,7 @@ You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren ## Configuration ### Add backends -Create a new farm for each port on backend. +Create a new cluster for each port on backend. > [!api] > diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-us.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-us.md index 95e82fe5bc4..c71907b8d17 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-us.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-us.md @@ -1,7 +1,7 @@ --- title: ProxyProtocol get Source IP excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2018-10-12 +updated: 2025-07-04 --- ## Introduction @@ -76,7 +76,7 @@ You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren ## Configuration ### Add backends -Create a new farm for each port on backend. +Create a new cluster for each port on backend. > [!api] > diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-asia.md b/pages/network/load_balancer/create_redirectlocation/guide.en-asia.md index 0619b5b295b..0643b7fd90e 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-asia.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-asia.md @@ -2,7 +2,7 @@ title: 'Working with redirections' universe: cloud excerpt: 'Integrate your web services behind a Load Balancer with redirections' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -43,7 +43,7 @@ You can either do this on a new front-end as you create it, or on an existing fr In the `Front-ends`{.action} section of the OVH Control Panel, click on `Add a front-end`{.action} to create a new one. -In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. @@ -51,7 +51,7 @@ In the advanced settings, enter the `HTTP redirection`{.action}. In the `Front-ends`{.action} section of the OVH Control Panel, select the front-end you would like to edit. To do this, click the `...`{.action} button, then select `Edit`{.action} in the menu that appears. Please ensure that the front-end you have chosen uses either `HTTP` or `HTTPS` protocol. -In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-au.md b/pages/network/load_balancer/create_redirectlocation/guide.en-au.md index 7e1fe733fa4..ebe8d2a190e 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-au.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-au.md @@ -2,7 +2,7 @@ title: 'Working with redirections' universe: cloud excerpt: 'Integrate your web services behind a Load Balancer with redirections' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -43,7 +43,7 @@ You can either do this on a new front-end as you create it, or on an existing fr In the `Front-ends`{.action} section of the OVH Control Panel, click on `Add a front-end`{.action} to create a new one. -In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. @@ -51,7 +51,7 @@ In the advanced settings, enter the `HTTP redirection`{.action}. In the `Front-ends`{.action} section of the OVH Control Panel, select the front-end you would like to edit. To do this, click the `...`{.action} button, then select `Edit`{.action} in the menu that appears. Please ensure that the front-end you have chosen uses either `HTTP` or `HTTPS` protocol. -In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-ca.md b/pages/network/load_balancer/create_redirectlocation/guide.en-ca.md index 50f2d226b23..f55ae21be5b 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-ca.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-ca.md @@ -2,7 +2,7 @@ title: 'Working with redirections' universe: cloud excerpt: 'Integrate your web services behind a Load Balancer with redirections' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -43,7 +43,7 @@ You can either do this on a new front-end as you create it, or on an existing fr In the `Front-ends`{.action} section of the OVH Control Panel, click on `Add a front-end`{.action} to create a new one. -In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. @@ -51,7 +51,7 @@ In the advanced settings, enter the `HTTP redirection`{.action}. In the `Front-ends`{.action} section of the OVH Control Panel, select the front-end you would like to edit. To do this, click the `...`{.action} button, then select `Edit`{.action} in the menu that appears. Please ensure that the front-end you have chosen uses either `HTTP` or `HTTPS` protocol. -In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-gb.md b/pages/network/load_balancer/create_redirectlocation/guide.en-gb.md index 656ccf20a0b..834781612d7 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-gb.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-gb.md @@ -2,7 +2,7 @@ title: 'Working with redirections' universe: cloud excerpt: 'Integrate your web services behind a Load Balancer with redirections' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -43,7 +43,7 @@ You can either do this on a new front-end as you create it, or on an existing fr In the `Front-ends`{.action} section of the OVH Control Panel, click on `Add a front-end`{.action} to create a new one. -In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. @@ -51,7 +51,7 @@ In the advanced settings, enter the `HTTP redirection`{.action}. In the `Front-ends`{.action} section of the OVH Control Panel, select the front-end you would like to edit. To do this, click the `...`{.action} button, then select `Edit`{.action} in the menu that appears. Please ensure that the front-end you have chosen uses either `HTTP` or `HTTPS` protocol. -In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-sg.md b/pages/network/load_balancer/create_redirectlocation/guide.en-sg.md index ea3142ee4da..c76bab95b3d 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-sg.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-sg.md @@ -2,7 +2,7 @@ title: 'Working with redirections' universe: cloud excerpt: 'Integrate your web services behind a Load Balancer with redirections' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -43,7 +43,7 @@ You can either do this on a new front-end as you create it, or on an existing fr In the `Front-ends`{.action} section of the OVH Control Panel, click on `Add a front-end`{.action} to create a new one. -In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. @@ -51,7 +51,7 @@ In the advanced settings, enter the `HTTP redirection`{.action}. In the `Front-ends`{.action} section of the OVH Control Panel, select the front-end you would like to edit. To do this, click the `...`{.action} button, then select `Edit`{.action} in the menu that appears. Please ensure that the front-end you have chosen uses either `HTTP` or `HTTPS` protocol. -In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. diff --git a/pages/network/load_balancer/create_redirectlocation/guide.en-us.md b/pages/network/load_balancer/create_redirectlocation/guide.en-us.md index 698cd68f0aa..8cb09175785 100644 --- a/pages/network/load_balancer/create_redirectlocation/guide.en-us.md +++ b/pages/network/load_balancer/create_redirectlocation/guide.en-us.md @@ -2,7 +2,7 @@ title: 'Working with redirections' universe: cloud excerpt: 'Integrate your web services behind a Load Balancer with redirections' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -43,7 +43,7 @@ You can either do this on a new front-end as you create it, or on an existing fr In the `Front-ends`{.action} section of the OVH Control Panel, click on `Add a front-end`{.action} to create a new one. -In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for a front-end, select `HTTP`{.action} or `HTTPS`{.action} protocol. Configure the information as requested. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. @@ -51,7 +51,7 @@ In the advanced settings, enter the `HTTP redirection`{.action}. In the `Front-ends`{.action} section of the OVH Control Panel, select the front-end you would like to edit. To do this, click the `...`{.action} button, then select `Edit`{.action} in the menu that appears. Please ensure that the front-end you have chosen uses either `HTTP` or `HTTPS` protocol. -In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default farm`{.action}, as it will not be used. +In the editing page for the front-end, complete the configuration if needed. However, please note that there is no need to set a `Default cluster`{.action}, as it will not be used. In the advanced settings, enter the `HTTP redirection`{.action}. diff --git a/pages/network/load_balancer/create_route/guide.en-asia.md b/pages/network/load_balancer/create_route/guide.en-asia.md index e62467bb83e..d5445e767ad 100644 --- a/pages/network/load_balancer/create_route/guide.en-asia.md +++ b/pages/network/load_balancer/create_route/guide.en-asia.md @@ -1,16 +1,16 @@ --- title: 'Working with HTTP routes' -excerpt: 'Find out how to direct your requests dynamically, to a specific farm' -updated: 2018-04-09 +excerpt: 'Find out how to direct your requests dynamically, to a specific cluster' +updated: 2025-07-04 --- ## Objective -The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default farm, or its default redirection. +The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default cluster, or its default redirection. In some cases, you can go a step further and route, redirect or block traffic according to a range of criteria. For example, in the case of a HTTP(S) service, you can filter traffic depending on the HTTP method, the URL, and even a cookie or header value! In the OVH Load Balancer service, these are called `routes`{.action}. A route is a particular action to carry out if one or more conditions are met. -**This guide will show you how to direct your requests dynamically, to a specific farm.** +**This guide will show you how to direct your requests dynamically, to a specific cluster.** ## Requirements @@ -21,7 +21,7 @@ In some cases, you can go a step further and route, redirect or block traffic ac > [!primary] > -> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular farm, or reject incoming requests from certain IPs. +> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular cluster, or reject incoming requests from certain IPs. > Since this feature is still very new, it is only available in the API. This guide will explain the general principles behind routing, and provide practical examples of routes being used. @@ -64,7 +64,7 @@ When you want to configure a route or rules, the first thing you need to do is l When a request arrives at your OVH Load Balancer service, the routes are evaluated successively following the principles below: -1. firstly, reject and rewrite routes, then the farm routes +1. firstly, reject and rewrite routes, then the cluster routes 1. within categories, the routes are evaluated in order of ascending weight 1. if two routes are the same weight, the first route created is evaluated first 1. only the first action from all the validated rules is executed @@ -104,7 +104,7 @@ For more information on this call, please read the [Edit routes](#edit-routes){. ### Route configuration. -With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the farms can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. +With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the clusters can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. For more information on these calls, please read the [Edit routes](#edit-routes){.internal} section at the bottom of this guide. @@ -160,9 +160,9 @@ Next, apply the configuration to the zone concerned, and the rule will begin to This feature helped propel the expansion of the web at its very early stages, by exposing several websites behind a single IP address using the “host” field of HTTP headers. -For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the farms, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. +For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the clusters, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. -With routes, you can share the same front-end, and choose the server farm dynamically, with the “host” field. +With routes, you can share the same front-end, and choose the server cluster dynamically, with the “host” field. To do this, you will need: @@ -179,7 +179,7 @@ In practice, to route the domain www.example.com, this would give the following |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct this domain to| +|action.target|ID of the cluster to direct this domain to| And on this route, we will attach a rule: @@ -231,7 +231,7 @@ Finally, apply the configuration. ### Route depending on a URL and HTTP method. -On some specific infrastructures, certain requests need to be routed to a specific farm. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. +On some specific infrastructures, certain requests need to be routed to a specific cluster. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. If, for example, the request is sent: @@ -246,11 +246,11 @@ In practice, this gives a route like this: |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route batch analytics to dedicated farm"| +|displayName|"Route batch analytics to dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct these operations to| +|action.target|ID of the cluster to direct these operations to| And on this route, we will attach two rules: @@ -289,7 +289,7 @@ In practice, we would need two identical routes: |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|Your pre-production farm’s ID| +|action.target|Your pre-production cluster’s ID| Then we will attach the following two rules to each of the routes (one rule per route): @@ -309,9 +309,9 @@ The second rule simply tests to see if a cookie exists. It is also possible to t Next, apply the configuration to the zone concerned. -### Route WebSockets to a dedicated farm. +### Route WebSockets to a dedicated cluster. -When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server farm dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: +When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server cluster dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: ``` Upgrade: websocket @@ -324,11 +324,11 @@ In this case, only the first header needs to be detected. This can be done very |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route WebSockets to a dedicated farm"| +|displayName|"Route WebSockets to a dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm dedicated to WebSockets| +|action.target|ID of the cluster dedicated to WebSockets| And on this route, we will attach a rule: @@ -383,7 +383,7 @@ With this call, you can create a route. Only the action is mandatory. A route ca |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| The possible action types are listed below: @@ -391,7 +391,7 @@ The possible action types are listed below: |---|---| |redirect|Redirects a request to `action.target`, with the HTTP `action.status` code| |reject|Rejects a request with the HTTP `action.status` code| -|farm|Routes a request to the farm with the ID entered in `action.target`| +|farm|Routes a request to the cluster with the ID entered in `action.target`| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -421,7 +421,7 @@ Answer |weight|Priority of your route| |action.type|Name of the action type for your route| |action.status|Associated HTTP status code| -|action.target|ID number of the associated farm or URL template| +|action.target|ID number of the associated cluster or URL template| |rules|List of rules that must be validated to trigger the route’s action More detail on this is available in the [Edit rules](#edit-rules){.internal} section.| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -444,7 +444,7 @@ With this call, you can modify an HTTP route if you know its ID. You will need t |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -649,7 +649,7 @@ Answer #### Redirection -This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no farms will receive the request. +This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -686,7 +686,7 @@ For example, for: #### Reject. -This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no farms will receive the request. +This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -716,17 +716,17 @@ Only the HTTP error codes listed in the API can be specified. The most common on #### Routing. -This action redirects requests to a specific farm, other than the default farm configured on the front-end. The destination farm must be the same type as the front-end ("http" or "tcp"). +This action redirects requests to a specific cluster, other than the default cluster configured on the front-end. The destination cluster must be the same type as the front-end ("http" or "tcp"). |Setting|Value| |---|---| |type|`farm`| |status|not available| -|target|The destination farm’s ID number. This must be the same type.| +|target|The destination cluster’s ID number. This must be the same type.| > [!primary] > -> This action is also available in TCP. In this case, the destination farm type must be "tcp". +> This action is also available in TCP. In this case, the destination cluster type must be "tcp". > ### Available rules. @@ -850,7 +850,7 @@ This rule filters requests depending on their existence, or the value of a speci #### HTTP header. -This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server farm. +This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server cluster. |Fields|Value| |---|---| @@ -861,7 +861,7 @@ This rule filters requests depending on their existence, or the value of a speci #### Cookie. -With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production farm. +With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production cluster. |Fields|Value| |---|---| diff --git a/pages/network/load_balancer/create_route/guide.en-au.md b/pages/network/load_balancer/create_route/guide.en-au.md index dc8c9d837e4..c0c7367bdba 100644 --- a/pages/network/load_balancer/create_route/guide.en-au.md +++ b/pages/network/load_balancer/create_route/guide.en-au.md @@ -1,16 +1,16 @@ --- title: 'Working with HTTP routes' -excerpt: 'Find out how to direct your requests dynamically, to a specific farm' -updated: 2018-04-09 +excerpt: 'Find out how to direct your requests dynamically, to a specific cluster' +updated: 2025-07-04 --- ## Objective -The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default farm, or its default redirection. +The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default cluster, or its default redirection. In some cases, you can go a step further and route, redirect or block traffic according to a range of criteria. For example, in the case of a HTTP(S) service, you can filter traffic depending on the HTTP method, the URL, and even a cookie or header value! In the OVH Load Balancer service, these are called `routes`{.action}. A route is a particular action to carry out if one or more conditions are met. -**This guide will show you how to direct your requests dynamically, to a specific farm.** +**This guide will show you how to direct your requests dynamically, to a specific cluster.** ## Requirements @@ -21,7 +21,7 @@ In some cases, you can go a step further and route, redirect or block traffic ac > [!primary] > -> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular farm, or reject incoming requests from certain IPs. +> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular cluster, or reject incoming requests from certain IPs. > Since this feature is still very new, it is only available in the API. This guide will explain the general principles behind routing, and provide practical examples of routes being used. @@ -64,7 +64,7 @@ When you want to configure a route or rules, the first thing you need to do is l When a request arrives at your OVH Load Balancer service, the routes are evaluated successively following the principles below: -1. firstly, reject and rewrite routes, then the farm routes +1. firstly, reject and rewrite routes, then the cluster routes 1. within categories, the routes are evaluated in order of ascending weight 1. if two routes are the same weight, the first route created is evaluated first 1. only the first action from all the validated rules is executed @@ -104,7 +104,7 @@ For more information on this call, please read the [Edit routes](#edit-routes){. ### Route configuration. -With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the farms can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. +With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the clusters can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. For more information on these calls, please read the [Edit routes](#edit-routes){.internal} section at the bottom of this guide. @@ -160,9 +160,9 @@ Next, apply the configuration to the zone concerned, and the rule will begin to This feature helped propel the expansion of the web at its very early stages, by exposing several websites behind a single IP address using the “host” field of HTTP headers. -For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the farms, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. +For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the clusters, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. -With routes, you can share the same front-end, and choose the server farm dynamically, with the “host” field. +With routes, you can share the same front-end, and choose the server cluster dynamically, with the “host” field. To do this, you will need: @@ -179,7 +179,7 @@ In practice, to route the domain www.example.com, this would give the following |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct this domain to| +|action.target|ID of the cluster to direct this domain to| And on this route, we will attach a rule: @@ -231,7 +231,7 @@ Finally, apply the configuration. ### Route depending on a URL and HTTP method. -On some specific infrastructures, certain requests need to be routed to a specific farm. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. +On some specific infrastructures, certain requests need to be routed to a specific cluster. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. If, for example, the request is sent: @@ -246,11 +246,11 @@ In practice, this gives a route like this: |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route batch analytics to dedicated farm"| +|displayName|"Route batch analytics to dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct these operations to| +|action.target|ID of the cluster to direct these operations to| And on this route, we will attach two rules: @@ -289,7 +289,7 @@ In practice, we would need two identical routes: |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|Your pre-production farm’s ID| +|action.target|Your pre-production cluster’s ID| Then we will attach the following two rules to each of the routes (one rule per route): @@ -309,9 +309,9 @@ The second rule simply tests to see if a cookie exists. It is also possible to t Next, apply the configuration to the zone concerned. -### Route WebSockets to a dedicated farm. +### Route WebSockets to a dedicated cluster. -When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server farm dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: +When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server cluster dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: ``` Upgrade: websocket @@ -324,11 +324,11 @@ In this case, only the first header needs to be detected. This can be done very |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route WebSockets to a dedicated farm"| +|displayName|"Route WebSockets to a dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm dedicated to WebSockets| +|action.target|ID of the cluster dedicated to WebSockets| And on this route, we will attach a rule: @@ -383,7 +383,7 @@ With this call, you can create a route. Only the action is mandatory. A route ca |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| The possible action types are listed below: @@ -391,7 +391,7 @@ The possible action types are listed below: |---|---| |redirect|Redirects a request to `action.target`, with the HTTP `action.status` code| |reject|Rejects a request with the HTTP `action.status` code| -|farm|Routes a request to the farm with the ID entered in `action.target`| +|farm|Routes a request to the cluster with the ID entered in `action.target`| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -421,7 +421,7 @@ Answer |weight|Priority of your route| |action.type|Name of the action type for your route| |action.status|Associated HTTP status code| -|action.target|ID number of the associated farm or URL template| +|action.target|ID number of the associated cluster or URL template| |rules|List of rules that must be validated to trigger the route’s action More detail on this is available in the [Edit rules](#edit-rules){.internal} section.| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -444,7 +444,7 @@ With this call, you can modify an HTTP route if you know its ID. You will need t |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -649,7 +649,7 @@ Answer #### Redirection -This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no farms will receive the request. +This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -686,7 +686,7 @@ For example, for: #### Reject. -This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no farms will receive the request. +This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -716,17 +716,17 @@ Only the HTTP error codes listed in the API can be specified. The most common on #### Routing. -This action redirects requests to a specific farm, other than the default farm configured on the front-end. The destination farm must be the same type as the front-end ("http" or "tcp"). +This action redirects requests to a specific cluster, other than the default cluster configured on the front-end. The destination cluster must be the same type as the front-end ("http" or "tcp"). |Setting|Value| |---|---| |type|`farm`| |status|not available| -|target|The destination farm’s ID number. This must be the same type.| +|target|The destination cluster’s ID number. This must be the same type.| > [!primary] > -> This action is also available in TCP. In this case, the destination farm type must be "tcp". +> This action is also available in TCP. In this case, the destination cluster type must be "tcp". > ### Available rules. @@ -850,7 +850,7 @@ This rule filters requests depending on their existence, or the value of a speci #### HTTP header. -This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server farm. +This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server cluster. |Fields|Value| |---|---| @@ -861,7 +861,7 @@ This rule filters requests depending on their existence, or the value of a speci #### Cookie. -With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production farm. +With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production cluster. |Fields|Value| |---|---| diff --git a/pages/network/load_balancer/create_route/guide.en-ca.md b/pages/network/load_balancer/create_route/guide.en-ca.md index 017713dd805..ffd818701bf 100644 --- a/pages/network/load_balancer/create_route/guide.en-ca.md +++ b/pages/network/load_balancer/create_route/guide.en-ca.md @@ -1,16 +1,16 @@ --- title: 'Working with HTTP routes' -excerpt: 'Find out how to direct your requests dynamically, to a specific farm' -updated: 2018-04-09 +excerpt: 'Find out how to direct your requests dynamically, to a specific cluster' +updated: 2025-07-04 --- ## Objective -The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default farm, or its default redirection. +The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default cluster, or its default redirection. In some cases, you can go a step further and route, redirect or block traffic according to a range of criteria. For example, in the case of a HTTP(S) service, you can filter traffic depending on the HTTP method, the URL, and even a cookie or header value! In the OVH Load Balancer service, these are called `routes`{.action}. A route is a particular action to carry out if one or more conditions are met. -**This guide will show you how to direct your requests dynamically, to a specific farm.** +**This guide will show you how to direct your requests dynamically, to a specific cluster.** ## Requirements @@ -21,7 +21,7 @@ In some cases, you can go a step further and route, redirect or block traffic ac > [!primary] > -> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular farm, or reject incoming requests from certain IPs. +> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular cluster, or reject incoming requests from certain IPs. > Since this feature is still very new, it is only available in the API. This guide will explain the general principles behind routing, and provide practical examples of routes being used. @@ -64,7 +64,7 @@ When you want to configure a route or rules, the first thing you need to do is l When a request arrives at your OVH Load Balancer service, the routes are evaluated successively following the principles below: -1. firstly, reject and rewrite routes, then the farm routes +1. firstly, reject and rewrite routes, then the cluster routes 1. within categories, the routes are evaluated in order of ascending weight 1. if two routes are the same weight, the first route created is evaluated first 1. only the first action from all the validated rules is executed @@ -104,7 +104,7 @@ For more information on this call, please read the [Edit routes](#edit-routes){. ### Route configuration. -With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the farms can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. +With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the clusters can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. For more information on these calls, please read the [Edit routes](#edit-routes){.internal} section at the bottom of this guide. @@ -160,9 +160,9 @@ Next, apply the configuration to the zone concerned, and the rule will begin to This feature helped propel the expansion of the web at its very early stages, by exposing several websites behind a single IP address using the “host” field of HTTP headers. -For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the farms, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. +For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the clusters, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. -With routes, you can share the same front-end, and choose the server farm dynamically, with the “host” field. +With routes, you can share the same front-end, and choose the server cluster dynamically, with the “host” field. To do this, you will need: @@ -179,7 +179,7 @@ In practice, to route the domain www.example.com, this would give the following |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct this domain to| +|action.target|ID of the cluster to direct this domain to| And on this route, we will attach a rule: @@ -231,7 +231,7 @@ Finally, apply the configuration. ### Route depending on a URL and HTTP method. -On some specific infrastructures, certain requests need to be routed to a specific farm. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. +On some specific infrastructures, certain requests need to be routed to a specific cluster. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. If, for example, the request is sent: @@ -246,11 +246,11 @@ In practice, this gives a route like this: |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route batch analytics to dedicated farm"| +|displayName|"Route batch analytics to dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct these operations to| +|action.target|ID of the cluster to direct these operations to| And on this route, we will attach two rules: @@ -289,7 +289,7 @@ In practice, we would need two identical routes: |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|Your pre-production farm’s ID| +|action.target|Your pre-production cluster’s ID| Then we will attach the following two rules to each of the routes (one rule per route): @@ -309,9 +309,9 @@ The second rule simply tests to see if a cookie exists. It is also possible to t Next, apply the configuration to the zone concerned. -### Route WebSockets to a dedicated farm. +### Route WebSockets to a dedicated cluster. -When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server farm dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: +When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server cluster dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: ``` Upgrade: websocket @@ -324,11 +324,11 @@ In this case, only the first header needs to be detected. This can be done very |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route WebSockets to a dedicated farm"| +|displayName|"Route WebSockets to a dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm dedicated to WebSockets| +|action.target|ID of the cluster dedicated to WebSockets| And on this route, we will attach a rule: @@ -383,7 +383,7 @@ With this call, you can create a route. Only the action is mandatory. A route ca |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| The possible action types are listed below: @@ -391,7 +391,7 @@ The possible action types are listed below: |---|---| |redirect|Redirects a request to `action.target`, with the HTTP `action.status` code| |reject|Rejects a request with the HTTP `action.status` code| -|farm|Routes a request to the farm with the ID entered in `action.target`| +|farm|Routes a request to the cluster with the ID entered in `action.target`| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -421,7 +421,7 @@ Answer |weight|Priority of your route| |action.type|Name of the action type for your route| |action.status|Associated HTTP status code| -|action.target|ID number of the associated farm or URL template| +|action.target|ID number of the associated cluster or URL template| |rules|List of rules that must be validated to trigger the route’s action More detail on this is available in the [Edit rules](#edit-rules){.internal} section.| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -444,7 +444,7 @@ With this call, you can modify an HTTP route if you know its ID. You will need t |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -649,7 +649,7 @@ Answer #### Redirection -This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no farms will receive the request. +This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -686,7 +686,7 @@ For example, for: #### Reject. -This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no farms will receive the request. +This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -716,17 +716,17 @@ Only the HTTP error codes listed in the API can be specified. The most common on #### Routing. -This action redirects requests to a specific farm, other than the default farm configured on the front-end. The destination farm must be the same type as the front-end ("http" or "tcp"). +This action redirects requests to a specific cluster, other than the default cluster configured on the front-end. The destination cluster must be the same type as the front-end ("http" or "tcp"). |Setting|Value| |---|---| |type|`farm`| |status|not available| -|target|The destination farm’s ID number. This must be the same type.| +|target|The destination cluster’s ID number. This must be the same type.| > [!primary] > -> This action is also available in TCP. In this case, the destination farm type must be "tcp". +> This action is also available in TCP. In this case, the destination cluster type must be "tcp". > ### Available rules. @@ -850,7 +850,7 @@ This rule filters requests depending on their existence, or the value of a speci #### HTTP header. -This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server farm. +This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server cluster. |Fields|Value| |---|---| @@ -861,7 +861,7 @@ This rule filters requests depending on their existence, or the value of a speci #### Cookie. -With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production farm. +With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production cluster. |Fields|Value| |---|---| diff --git a/pages/network/load_balancer/create_route/guide.en-gb.md b/pages/network/load_balancer/create_route/guide.en-gb.md index 7ee6ccdda94..ab337b70f4a 100644 --- a/pages/network/load_balancer/create_route/guide.en-gb.md +++ b/pages/network/load_balancer/create_route/guide.en-gb.md @@ -1,16 +1,16 @@ --- title: 'Working with HTTP routes' -excerpt: 'Find out how to direct your requests dynamically, to a specific farm' -updated: 2018-04-09 +excerpt: 'Find out how to direct your requests dynamically, to a specific cluster' +updated: 2025-07-04 --- ## Objective -The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default farm, or its default redirection. +The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default cluster, or its default redirection. In some cases, you can go a step further and route, redirect or block traffic according to a range of criteria. For example, in the case of a HTTP(S) service, you can filter traffic depending on the HTTP method, the URL, and even a cookie or header value! In the OVH Load Balancer service, these are called `routes`{.action}. A route is a particular action to carry out if one or more conditions are met. -**This guide will show you how to direct your requests dynamically, to a specific farm.** +**This guide will show you how to direct your requests dynamically, to a specific cluster.** ## Requirements @@ -21,7 +21,7 @@ In some cases, you can go a step further and route, redirect or block traffic ac > [!primary] > -> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular farm, or reject incoming requests from certain IPs. +> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular cluster, or reject incoming requests from certain IPs. > Since this feature is still very new, it is only available in the API. This guide will explain the general principles behind routing, and provide practical examples of routes being used. @@ -64,7 +64,7 @@ When you want to configure a route or rules, the first thing you need to do is l When a request arrives at your OVH Load Balancer service, the routes are evaluated successively following the principles below: -1. firstly, reject and rewrite routes, then the farm routes +1. firstly, reject and rewrite routes, then the cluster routes 1. within categories, the routes are evaluated in order of ascending weight 1. if two routes are the same weight, the first route created is evaluated first 1. only the first action from all the validated rules is executed @@ -104,7 +104,7 @@ For more information on this call, please read the [Edit routes](#edit-routes){. ### Route configuration. -With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the farms can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. +With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the clusters can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. For more information on these calls, please read the [Edit routes](#edit-routes){.internal} section at the bottom of this guide. @@ -160,9 +160,9 @@ Next, apply the configuration to the zone concerned, and the rule will begin to This feature helped propel the expansion of the web at its very early stages, by exposing several websites behind a single IP address using the “host” field of HTTP headers. -For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the farms, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. +For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the clusters, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. -With routes, you can share the same front-end, and choose the server farm dynamically, with the “host” field. +With routes, you can share the same front-end, and choose the server cluster dynamically, with the “host” field. To do this, you will need: @@ -179,7 +179,7 @@ In practice, to route the domain www.example.com, this would give the following |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct this domain to| +|action.target|ID of the cluster to direct this domain to| And on this route, we will attach a rule: @@ -231,7 +231,7 @@ Finally, apply the configuration. ### Route depending on a URL and HTTP method. -On some specific infrastructures, certain requests need to be routed to a specific farm. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. +On some specific infrastructures, certain requests need to be routed to a specific cluster. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. If, for example, the request is sent: @@ -246,11 +246,11 @@ In practice, this gives a route like this: |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route batch analytics to dedicated farm"| +|displayName|"Route batch analytics to dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct these operations to| +|action.target|ID of the cluster to direct these operations to| And on this route, we will attach two rules: @@ -289,7 +289,7 @@ In practice, we would need two identical routes: |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|Your pre-production farm’s ID| +|action.target|Your pre-production cluster’s ID| Then we will attach the following two rules to each of the routes (one rule per route): @@ -309,9 +309,9 @@ The second rule simply tests to see if a cookie exists. It is also possible to t Next, apply the configuration to the zone concerned. -### Route WebSockets to a dedicated farm. +### Route WebSockets to a dedicated cluster. -When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server farm dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: +When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server cluster dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: ``` Upgrade: websocket @@ -324,11 +324,11 @@ In this case, only the first header needs to be detected. This can be done very |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route WebSockets to a dedicated farm"| +|displayName|"Route WebSockets to a dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm dedicated to WebSockets| +|action.target|ID of the cluster dedicated to WebSockets| And on this route, we will attach a rule: @@ -383,7 +383,7 @@ With this call, you can create a route. Only the action is mandatory. A route ca |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| The possible action types are listed below: @@ -391,7 +391,7 @@ The possible action types are listed below: |---|---| |redirect|Redirects a request to `action.target`, with the HTTP `action.status` code| |reject|Rejects a request with the HTTP `action.status` code| -|farm|Routes a request to the farm with the ID entered in `action.target`| +|farm|Routes a request to the cluster with the ID entered in `action.target`| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -421,7 +421,7 @@ Answer |weight|Priority of your route| |action.type|Name of the action type for your route| |action.status|Associated HTTP status code| -|action.target|ID number of the associated farm or URL template| +|action.target|ID number of the associated cluster or URL template| |rules|List of rules that must be validated to trigger the route’s action More detail on this is available in the [Edit rules](#edit-rules){.internal} section.| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -444,7 +444,7 @@ With this call, you can modify an HTTP route if you know its ID. You will need t |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -649,7 +649,7 @@ Answer #### Redirection -This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no farms will receive the request. +This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -686,7 +686,7 @@ For example, for: #### Reject. -This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no farms will receive the request. +This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -716,17 +716,17 @@ Only the HTTP error codes listed in the API can be specified. The most common on #### Routing. -This action redirects requests to a specific farm, other than the default farm configured on the front-end. The destination farm must be the same type as the front-end ("http" or "tcp"). +This action redirects requests to a specific cluster, other than the default cluster configured on the front-end. The destination cluster must be the same type as the front-end ("http" or "tcp"). |Setting|Value| |---|---| |type|`farm`| |status|not available| -|target|The destination farm’s ID number. This must be the same type.| +|target|The destination cluster’s ID number. This must be the same type.| > [!primary] > -> This action is also available in TCP. In this case, the destination farm type must be "tcp". +> This action is also available in TCP. In this case, the destination cluster type must be "tcp". > ### Available rules. @@ -850,7 +850,7 @@ This rule filters requests depending on their existence, or the value of a speci #### HTTP header. -This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server farm. +This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server cluster. |Fields|Value| |---|---| @@ -861,7 +861,7 @@ This rule filters requests depending on their existence, or the value of a speci #### Cookie. -With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production farm. +With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production cluster. |Fields|Value| |---|---| diff --git a/pages/network/load_balancer/create_route/guide.en-sg.md b/pages/network/load_balancer/create_route/guide.en-sg.md index dd183ddafa7..3d0094cf466 100644 --- a/pages/network/load_balancer/create_route/guide.en-sg.md +++ b/pages/network/load_balancer/create_route/guide.en-sg.md @@ -1,16 +1,16 @@ --- title: 'Working with HTTP routes' -excerpt: 'Find out how to direct your requests dynamically, to a specific farm' -updated: 2018-04-09 +excerpt: 'Find out how to direct your requests dynamically, to a specific cluster' +updated: 2025-07-04 --- ## Objective -The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default farm, or its default redirection. +The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default cluster, or its default redirection. In some cases, you can go a step further and route, redirect or block traffic according to a range of criteria. For example, in the case of a HTTP(S) service, you can filter traffic depending on the HTTP method, the URL, and even a cookie or header value! In the OVH Load Balancer service, these are called `routes`{.action}. A route is a particular action to carry out if one or more conditions are met. -**This guide will show you how to direct your requests dynamically, to a specific farm.** +**This guide will show you how to direct your requests dynamically, to a specific cluster.** ## Requirements @@ -21,7 +21,7 @@ In some cases, you can go a step further and route, redirect or block traffic ac > [!primary] > -> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular farm, or reject incoming requests from certain IPs. +> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular cluster, or reject incoming requests from certain IPs. > Since this feature is still very new, it is only available in the API. This guide will explain the general principles behind routing, and provide practical examples of routes being used. @@ -64,7 +64,7 @@ When you want to configure a route or rules, the first thing you need to do is l When a request arrives at your OVH Load Balancer service, the routes are evaluated successively following the principles below: -1. firstly, reject and rewrite routes, then the farm routes +1. firstly, reject and rewrite routes, then the cluster routes 1. within categories, the routes are evaluated in order of ascending weight 1. if two routes are the same weight, the first route created is evaluated first 1. only the first action from all the validated rules is executed @@ -104,7 +104,7 @@ For more information on this call, please read the [Edit routes](#edit-routes){. ### Route configuration. -With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the farms can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. +With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the clusters can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. For more information on these calls, please read the [Edit routes](#edit-routes){.internal} section at the bottom of this guide. @@ -160,9 +160,9 @@ Next, apply the configuration to the zone concerned, and the rule will begin to This feature helped propel the expansion of the web at its very early stages, by exposing several websites behind a single IP address using the “host” field of HTTP headers. -For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the farms, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. +For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the clusters, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. -With routes, you can share the same front-end, and choose the server farm dynamically, with the “host” field. +With routes, you can share the same front-end, and choose the server cluster dynamically, with the “host” field. To do this, you will need: @@ -179,7 +179,7 @@ In practice, to route the domain www.example.com, this would give the following |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct this domain to| +|action.target|ID of the cluster to direct this domain to| And on this route, we will attach a rule: @@ -231,7 +231,7 @@ Finally, apply the configuration. ### Route depending on a URL and HTTP method. -On some specific infrastructures, certain requests need to be routed to a specific farm. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. +On some specific infrastructures, certain requests need to be routed to a specific cluster. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. If, for example, the request is sent: @@ -246,11 +246,11 @@ In practice, this gives a route like this: |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route batch analytics to dedicated farm"| +|displayName|"Route batch analytics to dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct these operations to| +|action.target|ID of the cluster to direct these operations to| And on this route, we will attach two rules: @@ -289,7 +289,7 @@ In practice, we would need two identical routes: |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|Your pre-production farm’s ID| +|action.target|Your pre-production cluster’s ID| Then we will attach the following two rules to each of the routes (one rule per route): @@ -309,9 +309,9 @@ The second rule simply tests to see if a cookie exists. It is also possible to t Next, apply the configuration to the zone concerned. -### Route WebSockets to a dedicated farm. +### Route WebSockets to a dedicated cluster. -When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server farm dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: +When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server cluster dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: ``` Upgrade: websocket @@ -324,11 +324,11 @@ In this case, only the first header needs to be detected. This can be done very |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route WebSockets to a dedicated farm"| +|displayName|"Route WebSockets to a dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm dedicated to WebSockets| +|action.target|ID of the cluster dedicated to WebSockets| And on this route, we will attach a rule: @@ -383,7 +383,7 @@ With this call, you can create a route. Only the action is mandatory. A route ca |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| The possible action types are listed below: @@ -391,7 +391,7 @@ The possible action types are listed below: |---|---| |redirect|Redirects a request to `action.target`, with the HTTP `action.status` code| |reject|Rejects a request with the HTTP `action.status` code| -|farm|Routes a request to the farm with the ID entered in `action.target`| +|farm|Routes a request to the cluster with the ID entered in `action.target`| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -421,7 +421,7 @@ Answer |weight|Priority of your route| |action.type|Name of the action type for your route| |action.status|Associated HTTP status code| -|action.target|ID number of the associated farm or URL template| +|action.target|ID number of the associated cluster or URL template| |rules|List of rules that must be validated to trigger the route’s action More detail on this is available in the [Edit rules](#edit-rules){.internal} section.| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -444,7 +444,7 @@ With this call, you can modify an HTTP route if you know its ID. You will need t |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -649,7 +649,7 @@ Answer #### Redirection -This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no farms will receive the request. +This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -686,7 +686,7 @@ For example, for: #### Reject. -This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no farms will receive the request. +This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -716,17 +716,17 @@ Only the HTTP error codes listed in the API can be specified. The most common on #### Routing. -This action redirects requests to a specific farm, other than the default farm configured on the front-end. The destination farm must be the same type as the front-end ("http" or "tcp"). +This action redirects requests to a specific cluster, other than the default cluster configured on the front-end. The destination cluster must be the same type as the front-end ("http" or "tcp"). |Setting|Value| |---|---| |type|`farm`| |status|not available| -|target|The destination farm’s ID number. This must be the same type.| +|target|The destination cluster’s ID number. This must be the same type.| > [!primary] > -> This action is also available in TCP. In this case, the destination farm type must be "tcp". +> This action is also available in TCP. In this case, the destination cluster type must be "tcp". > ### Available rules. @@ -850,7 +850,7 @@ This rule filters requests depending on their existence, or the value of a speci #### HTTP header. -This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server farm. +This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server cluster. |Fields|Value| |---|---| @@ -861,7 +861,7 @@ This rule filters requests depending on their existence, or the value of a speci #### Cookie. -With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production farm. +With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production cluster. |Fields|Value| |---|---| diff --git a/pages/network/load_balancer/create_route/guide.en-us.md b/pages/network/load_balancer/create_route/guide.en-us.md index c0c2d76704d..1b24758c0b8 100644 --- a/pages/network/load_balancer/create_route/guide.en-us.md +++ b/pages/network/load_balancer/create_route/guide.en-us.md @@ -1,16 +1,16 @@ --- title: 'Working with HTTP routes' -excerpt: 'Find out how to direct your requests dynamically, to a specific farm' -updated: 2018-04-09 +excerpt: 'Find out how to direct your requests dynamically, to a specific cluster' +updated: 2025-07-04 --- ## Objective -The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default farm, or its default redirection. +The OVH Load Balancer service redirects the front-end’s incoming traffic to the servers that make up the front-end’s default cluster, or its default redirection. In some cases, you can go a step further and route, redirect or block traffic according to a range of criteria. For example, in the case of a HTTP(S) service, you can filter traffic depending on the HTTP method, the URL, and even a cookie or header value! In the OVH Load Balancer service, these are called `routes`{.action}. A route is a particular action to carry out if one or more conditions are met. -**This guide will show you how to direct your requests dynamically, to a specific farm.** +**This guide will show you how to direct your requests dynamically, to a specific cluster.** ## Requirements @@ -21,7 +21,7 @@ In some cases, you can go a step further and route, redirect or block traffic ac > [!primary] > -> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular farm, or reject incoming requests from certain IPs. +> Although this guide focuses on HTTP routes, the same principle applies to TCP (with TCP routes). This can be used to direct HTTP/2 traffic to a particular cluster, or reject incoming requests from certain IPs. > Since this feature is still very new, it is only available in the API. This guide will explain the general principles behind routing, and provide practical examples of routes being used. @@ -64,7 +64,7 @@ When you want to configure a route or rules, the first thing you need to do is l When a request arrives at your OVH Load Balancer service, the routes are evaluated successively following the principles below: -1. firstly, reject and rewrite routes, then the farm routes +1. firstly, reject and rewrite routes, then the cluster routes 1. within categories, the routes are evaluated in order of ascending weight 1. if two routes are the same weight, the first route created is evaluated first 1. only the first action from all the validated rules is executed @@ -104,7 +104,7 @@ For more information on this call, please read the [Edit routes](#edit-routes){. ### Route configuration. -With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the farms can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. +With these basic principles around the action and rules available, and the order in which routes are evaluated, these routes can be edited the same way as the clusters can. When you create a route, you can attach rules to it. The possible values for rules and actions are defined by the API calls. For more information on these calls, please read the [Edit routes](#edit-routes){.internal} section at the bottom of this guide. @@ -160,9 +160,9 @@ Next, apply the configuration to the zone concerned, and the rule will begin to This feature helped propel the expansion of the web at its very early stages, by exposing several websites behind a single IP address using the “host” field of HTTP headers. -For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the farms, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. +For example, if your infrastructure is made up of a VPS for your website, an OVH Load Balancer to ensure SSL/TLS termination, and redirection to a maintenance page with a backup server in the clusters, you would originally have needed one Additional IP per website, routed to your OVH Load Balancer, and one front-end per IP. -With routes, you can share the same front-end, and choose the server farm dynamically, with the “host” field. +With routes, you can share the same front-end, and choose the server cluster dynamically, with the “host” field. To do this, you will need: @@ -179,7 +179,7 @@ In practice, to route the domain www.example.com, this would give the following |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct this domain to| +|action.target|ID of the cluster to direct this domain to| And on this route, we will attach a rule: @@ -231,7 +231,7 @@ Finally, apply the configuration. ### Route depending on a URL and HTTP method. -On some specific infrastructures, certain requests need to be routed to a specific farm. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. +On some specific infrastructures, certain requests need to be routed to a specific cluster. For example, to manage rare but data-intensive requests without impacting production, such as analytical requests that would work from a read-only duplicate of the data with a server that has a higher volume of memory. If, for example, the request is sent: @@ -246,11 +246,11 @@ In practice, this gives a route like this: |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route batch analytics to dedicated farm"| +|displayName|"Route batch analytics to dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm to direct these operations to| +|action.target|ID of the cluster to direct these operations to| And on this route, we will attach two rules: @@ -289,7 +289,7 @@ In practice, we would need two identical routes: |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|Your pre-production farm’s ID| +|action.target|Your pre-production cluster’s ID| Then we will attach the following two rules to each of the routes (one rule per route): @@ -309,9 +309,9 @@ The second rule simply tests to see if a cookie exists. It is also possible to t Next, apply the configuration to the zone concerned. -### Route WebSockets to a dedicated farm. +### Route WebSockets to a dedicated cluster. -When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server farm dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: +When a website has interactive features based on WebSockets — a chatbot, for example — you may want to direct these connections to a server cluster dedicated to this task. This is actually quite simple. When a browser attempts to open a WebSockets connection, it sends a standard HTTP request with these headers: ``` Upgrade: websocket @@ -324,11 +324,11 @@ In this case, only the first header needs to be detected. This can be done very |---|---| |serviceName|Your OVH Load Balancer service ID| |frontendId|Your front-end ID| -|displayName|"Route WebSockets to a dedicated farm"| +|displayName|"Route WebSockets to a dedicated cluster"| |weight|(empty)| |action.type|"farm"| |action.status|(empty)| -|action.target|ID of the farm dedicated to WebSockets| +|action.target|ID of the cluster dedicated to WebSockets| And on this route, we will attach a rule: @@ -383,7 +383,7 @@ With this call, you can create a route. Only the action is mandatory. A route ca |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| The possible action types are listed below: @@ -391,7 +391,7 @@ The possible action types are listed below: |---|---| |redirect|Redirects a request to `action.target`, with the HTTP `action.status` code| |reject|Rejects a request with the HTTP `action.status` code| -|farm|Routes a request to the farm with the ID entered in `action.target`| +|farm|Routes a request to the cluster with the ID entered in `action.target`| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -421,7 +421,7 @@ Answer |weight|Priority of your route| |action.type|Name of the action type for your route| |action.status|Associated HTTP status code| -|action.target|ID number of the associated farm or URL template| +|action.target|ID number of the associated cluster or URL template| |rules|List of rules that must be validated to trigger the route’s action More detail on this is available in the [Edit rules](#edit-rules){.internal} section.| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -444,7 +444,7 @@ With this call, you can modify an HTTP route if you know its ID. You will need t |weight||Route priority, between 1 (carry out first) and 255 (carry out after the others)| |action.type|Required|Name of the action type to execute if all of the rules associated with the route are validated| |action.status||HTTP status code for `reject` and `redirect` actions| -|action.target||ID number of the target farm for `farm` actions, or the URL template for `redirect` actions| +|action.target||ID number of the target cluster for `farm` actions, or the URL template for `redirect` actions| For further information on the actions managed and the format of parameters, please read the [Available actions](#available-actions){.internal} section further down. @@ -649,7 +649,7 @@ Answer #### Redirection -This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no farms will receive the request. +This action sends a redirection to the visitor. This redirection type can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -686,7 +686,7 @@ For example, for: #### Reject. -This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no farms will receive the request. +This action returns an HTTP error status code to the visitor. The HTTP error code can be configured with the status field. When this action is selected, no clusters will receive the request. |Setting|Value| |---|---| @@ -716,17 +716,17 @@ Only the HTTP error codes listed in the API can be specified. The most common on #### Routing. -This action redirects requests to a specific farm, other than the default farm configured on the front-end. The destination farm must be the same type as the front-end ("http" or "tcp"). +This action redirects requests to a specific cluster, other than the default cluster configured on the front-end. The destination cluster must be the same type as the front-end ("http" or "tcp"). |Setting|Value| |---|---| |type|`farm`| |status|not available| -|target|The destination farm’s ID number. This must be the same type.| +|target|The destination cluster’s ID number. This must be the same type.| > [!primary] > -> This action is also available in TCP. In this case, the destination farm type must be "tcp". +> This action is also available in TCP. In this case, the destination cluster type must be "tcp". > ### Available rules. @@ -850,7 +850,7 @@ This rule filters requests depending on their existence, or the value of a speci #### HTTP header. -This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server farm. +This rule filters requests depending on their existence, or the value of a specific HTTP header value. You can use it to detect the opening of a WebSocket connection, and direct it to a dedicated server cluster. |Fields|Value| |---|---| @@ -861,7 +861,7 @@ This rule filters requests depending on their existence, or the value of a speci #### Cookie. -With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production farm. +With this rule, you can filter requests depending on the existence or value of a specific HTTP cookie. You can use it to direct voluntary visitors to a pre-production cluster. |Fields|Value| |---|---| diff --git a/pages/network/load_balancer/create_stickiness/guide.en-asia.md b/pages/network/load_balancer/create_stickiness/guide.en-asia.md index 832a943cf2d..18d203eb5f4 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-asia.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: 'Tracking connections' excerpt: 'This guide will show you a number of ways you can track connections on the OVH Load Balancer.' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -27,31 +27,31 @@ There are two main connection tracking methods that can be configured on your se |Tracking connections|Details| |---|---| -|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the farm.| +|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the cluster.| |SourceIp|A hash algorithm will be applied to the source IP address of the request received by the OVH Load Balancer. The following elements will affect traffic redirection: - if the configured weight changes -- if a server in the farm is re-enabled -- if a server in the farm is no longer responding +- if a server in the cluster is re-enabled +- if a server in the cluster is no longer responding > [!warning] > > Once you have refreshed your configuration, the connections will be rebalanced, and your HTTP sessions will be lost as a result. > -### Modify a server farm’s connection tracking method via the OVH Control Panel. +### Modify a server cluster’s connection tracking method via the OVH Control Panel. -To modify connection tracking for a farm, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the farm you want to edit, and click `Edit`{.action} (*3* on the screenshot below): +To modify connection tracking for a cluster, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the cluster you want to edit, and click `Edit`{.action} (*3* on the screenshot below): -![Modify a farm](images/farm_edit.png){.thumbnail} +![Modify a cluster](images/farm_edit.png){.thumbnail} In the `Advanced settings`, you will be able to access the `Track session` section: ![Modifying connection tracking](images/tracking_session.png){.thumbnail} -Once you have configured the farm, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing farm. +Once you have configured the cluster, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing cluster. Please remember to deploy the configuration. There are two ways of doing this: @@ -62,11 +62,11 @@ There are two ways of doing this: ![Apply a Load Balancer configuration](images/apply_configuration.png){.thumbnail} -### Modify a server farm’s connection tracking method via the API. +### Modify a server cluster’s connection tracking method via the API. -#### View details on a server farm. +#### View details on a server cluster. -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on a HTTP farm. +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on a HTTP cluster. > [!api] > @@ -76,21 +76,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently enabled for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection tracking method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently enabled for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection tracking method currently set for the cluster| -#### Modify a server farm’s connection tracking method. +#### Modify a server cluster’s connection tracking method. -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on a HTTP farm. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on a HTTP cluster. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: > [!api] > @@ -100,8 +100,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.stickiness|Connection tracking method chosen for the farm| +|farmId*|The cluster’s ID number| +|BackendHttp.stickiness|Connection tracking method chosen for the cluster| #### Apply the modifications. diff --git a/pages/network/load_balancer/create_stickiness/guide.en-au.md b/pages/network/load_balancer/create_stickiness/guide.en-au.md index f4d6279d1aa..1876bfdec16 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-au.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-au.md @@ -1,7 +1,7 @@ --- title: 'Tracking connections' excerpt: 'This guide will show you a number of ways you can track connections on the OVH Load Balancer.' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -27,31 +27,31 @@ There are two main connection tracking methods that can be configured on your se |Tracking connections|Details| |---|---| -|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the farm.| +|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the cluster.| |SourceIp|A hash algorithm will be applied to the source IP address of the request received by the OVH Load Balancer. The following elements will affect traffic redirection: - if the configured weight changes -- if a server in the farm is re-enabled -- if a server in the farm is no longer responding +- if a server in the cluster is re-enabled +- if a server in the cluster is no longer responding > [!warning] > > Once you have refreshed your configuration, the connections will be rebalanced, and your HTTP sessions will be lost as a result. > -### Modify a server farm’s connection tracking method via the OVH Control Panel. +### Modify a server cluster’s connection tracking method via the OVH Control Panel. -To modify connection tracking for a farm, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the farm you want to edit, and click `Edit`{.action} (*3* on the screenshot below): +To modify connection tracking for a cluster, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the cluster you want to edit, and click `Edit`{.action} (*3* on the screenshot below): -![Modify a farm](images/farm_edit.png){.thumbnail} +![Modify a cluster](images/farm_edit.png){.thumbnail} In the `Advanced settings`, you will be able to access the `Track session` section: ![Modifying connection tracking](images/tracking_session.png){.thumbnail} -Once you have configured the farm, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing farm. +Once you have configured the cluster, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing cluster. Please remember to deploy the configuration. There are two ways of doing this: @@ -62,11 +62,11 @@ There are two ways of doing this: ![Apply a Load Balancer configuration](images/apply_configuration.png){.thumbnail} -### Modify a server farm’s connection tracking method via the API. +### Modify a server cluster’s connection tracking method via the API. -#### View details on a server farm. +#### View details on a server cluster. -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on a HTTP farm. +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on a HTTP cluster. > [!api] > @@ -76,21 +76,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently enabled for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection tracking method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently enabled for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection tracking method currently set for the cluster| -#### Modify a server farm’s connection tracking method. +#### Modify a server cluster’s connection tracking method. -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on a HTTP farm. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on a HTTP cluster. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: > [!api] > @@ -100,8 +100,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.stickiness|Connection tracking method chosen for the farm| +|farmId*|The cluster’s ID number| +|BackendHttp.stickiness|Connection tracking method chosen for the cluster| #### Apply the modifications. diff --git a/pages/network/load_balancer/create_stickiness/guide.en-ca.md b/pages/network/load_balancer/create_stickiness/guide.en-ca.md index 397250d2869..8e30ec75e64 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-ca.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: 'Tracking connections' excerpt: 'This guide will show you a number of ways you can track connections on the OVH Load Balancer.' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -27,31 +27,31 @@ There are two main connection tracking methods that can be configured on your se |Tracking connections|Details| |---|---| -|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the farm.| +|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the cluster.| |SourceIp|A hash algorithm will be applied to the source IP address of the request received by the OVH Load Balancer. The following elements will affect traffic redirection: - if the configured weight changes -- if a server in the farm is re-enabled -- if a server in the farm is no longer responding +- if a server in the cluster is re-enabled +- if a server in the cluster is no longer responding > [!warning] > > Once you have refreshed your configuration, the connections will be rebalanced, and your HTTP sessions will be lost as a result. > -### Modify a server farm’s connection tracking method via the OVH Control Panel. +### Modify a server cluster’s connection tracking method via the OVH Control Panel. -To modify connection tracking for a farm, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the farm you want to edit, and click `Edit`{.action} (*3* on the screenshot below): +To modify connection tracking for a cluster, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the cluster you want to edit, and click `Edit`{.action} (*3* on the screenshot below): -![Modify a farm](images/farm_edit.png){.thumbnail} +![Modify a cluster](images/farm_edit.png){.thumbnail} In the `Advanced settings`, you will be able to access the `Track session` section: ![Modifying connection tracking](images/tracking_session.png){.thumbnail} -Once you have configured the farm, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing farm. +Once you have configured the cluster, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing cluster. Please remember to deploy the configuration. There are two ways of doing this: @@ -62,11 +62,11 @@ There are two ways of doing this: ![Apply a Load Balancer configuration](images/apply_configuration.png){.thumbnail} -### Modify a server farm’s connection tracking method via the API. +### Modify a server cluster’s connection tracking method via the API. -#### View details on a server farm. +#### View details on a server cluster. -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on a HTTP farm. +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on a HTTP cluster. > [!api] > @@ -76,21 +76,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently enabled for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection tracking method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently enabled for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection tracking method currently set for the cluster| -#### Modify a server farm’s connection tracking method. +#### Modify a server cluster’s connection tracking method. -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on a HTTP farm. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on a HTTP cluster. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: > [!api] > @@ -100,8 +100,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.stickiness|Connection tracking method chosen for the farm| +|farmId*|The cluster’s ID number| +|BackendHttp.stickiness|Connection tracking method chosen for the cluster| #### Apply the modifications. diff --git a/pages/network/load_balancer/create_stickiness/guide.en-gb.md b/pages/network/load_balancer/create_stickiness/guide.en-gb.md index 1c26b261537..166a4022ecb 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-gb.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'Tracking connections' excerpt: 'This guide will show you a number of ways you can track connections on the OVH Load Balancer.' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -27,31 +27,31 @@ There are two main connection tracking methods that can be configured on your se |Tracking connections|Details| |---|---| -|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the farm.| +|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the cluster.| |SourceIp|A hash algorithm will be applied to the source IP address of the request received by the OVH Load Balancer. The following elements will affect traffic redirection: - if the configured weight changes -- if a server in the farm is re-enabled -- if a server in the farm is no longer responding +- if a server in the cluster is re-enabled +- if a server in the cluster is no longer responding > [!warning] > > Once you have refreshed your configuration, the connections will be rebalanced, and your HTTP sessions will be lost as a result. > -### Modify a server farm’s connection tracking method via the OVH Control Panel. +### Modify a server cluster’s connection tracking method via the OVH Control Panel. -To modify connection tracking for a farm, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the farm you want to edit, and click `Edit`{.action} (*3* on the screenshot below): +To modify connection tracking for a cluster, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the cluster you want to edit, and click `Edit`{.action} (*3* on the screenshot below): -![Modify a farm](images/farm_edit.png){.thumbnail} +![Modify a cluster](images/farm_edit.png){.thumbnail} In the `Advanced settings`, you will be able to access the `Track session` section: ![Modifying connection tracking](images/tracking_session.png){.thumbnail} -Once you have configured the farm, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing farm. +Once you have configured the cluster, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing cluster. Please remember to deploy the configuration. There are two ways of doing this: @@ -62,11 +62,11 @@ There are two ways of doing this: ![Apply a Load Balancer configuration](images/apply_configuration.png){.thumbnail} -### Modify a server farm’s connection tracking method via the API. +### Modify a server cluster’s connection tracking method via the API. -#### View details on a server farm. +#### View details on a server cluster. -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on a HTTP farm. +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on a HTTP cluster. > [!api] > @@ -76,21 +76,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently enabled for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection tracking method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently enabled for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection tracking method currently set for the cluster| -#### Modify a server farm’s connection tracking method. +#### Modify a server cluster’s connection tracking method. -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on a HTTP farm. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on a HTTP cluster. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: > [!api] > @@ -100,8 +100,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.stickiness|Connection tracking method chosen for the farm| +|farmId*|The cluster’s ID number| +|BackendHttp.stickiness|Connection tracking method chosen for the cluster| #### Apply the modifications. diff --git a/pages/network/load_balancer/create_stickiness/guide.en-sg.md b/pages/network/load_balancer/create_stickiness/guide.en-sg.md index b46ea44e155..c35b5302a39 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-sg.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: 'Tracking connections' excerpt: 'This guide will show you a number of ways you can track connections on the OVH Load Balancer.' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -27,31 +27,31 @@ There are two main connection tracking methods that can be configured on your se |Tracking connections|Details| |---|---| -|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the farm.| +|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the cluster.| |SourceIp|A hash algorithm will be applied to the source IP address of the request received by the OVH Load Balancer. The following elements will affect traffic redirection: - if the configured weight changes -- if a server in the farm is re-enabled -- if a server in the farm is no longer responding +- if a server in the cluster is re-enabled +- if a server in the cluster is no longer responding > [!warning] > > Once you have refreshed your configuration, the connections will be rebalanced, and your HTTP sessions will be lost as a result. > -### Modify a server farm’s connection tracking method via the OVH Control Panel. +### Modify a server cluster’s connection tracking method via the OVH Control Panel. -To modify connection tracking for a farm, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the farm you want to edit, and click `Edit`{.action} (*3* on the screenshot below): +To modify connection tracking for a cluster, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the cluster you want to edit, and click `Edit`{.action} (*3* on the screenshot below): -![Modify a farm](images/farm_edit.png){.thumbnail} +![Modify a cluster](images/farm_edit.png){.thumbnail} In the `Advanced settings`, you will be able to access the `Track session` section: ![Modifying connection tracking](images/tracking_session.png){.thumbnail} -Once you have configured the farm, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing farm. +Once you have configured the cluster, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing cluster. Please remember to deploy the configuration. There are two ways of doing this: @@ -62,11 +62,11 @@ There are two ways of doing this: ![Apply a Load Balancer configuration](images/apply_configuration.png){.thumbnail} -### Modify a server farm’s connection tracking method via the API. +### Modify a server cluster’s connection tracking method via the API. -#### View details on a server farm. +#### View details on a server cluster. -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on a HTTP farm. +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on a HTTP cluster. > [!api] > @@ -76,21 +76,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently enabled for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection tracking method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently enabled for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection tracking method currently set for the cluster| -#### Modify a server farm’s connection tracking method. +#### Modify a server cluster’s connection tracking method. -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on a HTTP farm. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on a HTTP cluster. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: > [!api] > @@ -100,8 +100,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.stickiness|Connection tracking method chosen for the farm| +|farmId*|The cluster’s ID number| +|BackendHttp.stickiness|Connection tracking method chosen for the cluster| #### Apply the modifications. diff --git a/pages/network/load_balancer/create_stickiness/guide.en-us.md b/pages/network/load_balancer/create_stickiness/guide.en-us.md index ebf38b2ec7a..097db2ee286 100644 --- a/pages/network/load_balancer/create_stickiness/guide.en-us.md +++ b/pages/network/load_balancer/create_stickiness/guide.en-us.md @@ -1,7 +1,7 @@ --- title: 'Tracking connections' excerpt: 'This guide will show you a number of ways you can track connections on the OVH Load Balancer.' -updated: 2021-02-05 +updated: 2025-07-04 --- ## Objective @@ -27,31 +27,31 @@ There are two main connection tracking methods that can be configured on your se |Tracking connections|Details| |---|---| -|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the farm.| +|Cookie|Configures a session cookie, which will be used to distribute traffic from a single HTTP session to the same server in the cluster.| |SourceIp|A hash algorithm will be applied to the source IP address of the request received by the OVH Load Balancer. The following elements will affect traffic redirection: - if the configured weight changes -- if a server in the farm is re-enabled -- if a server in the farm is no longer responding +- if a server in the cluster is re-enabled +- if a server in the cluster is no longer responding > [!warning] > > Once you have refreshed your configuration, the connections will be rebalanced, and your HTTP sessions will be lost as a result. > -### Modify a server farm’s connection tracking method via the OVH Control Panel. +### Modify a server cluster’s connection tracking method via the OVH Control Panel. -To modify connection tracking for a farm, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the farm you want to edit, and click `Edit`{.action} (*3* on the screenshot below): +To modify connection tracking for a cluster, you need to edit it by going to the `Server clusters`{.action} section (*1* on the screenshot below), then click the `...`{.action} edit button (*2* on the screenshot below) for the cluster you want to edit, and click `Edit`{.action} (*3* on the screenshot below): -![Modify a farm](images/farm_edit.png){.thumbnail} +![Modify a cluster](images/farm_edit.png){.thumbnail} In the `Advanced settings`, you will be able to access the `Track session` section: ![Modifying connection tracking](images/tracking_session.png){.thumbnail} -Once you have configured the farm, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing farm. +Once you have configured the cluster, click `Add`{.action} or `Edit`{.action}, depending on whether you are configuring a new or existing cluster. Please remember to deploy the configuration. There are two ways of doing this: @@ -62,11 +62,11 @@ There are two ways of doing this: ![Apply a Load Balancer configuration](images/apply_configuration.png){.thumbnail} -### Modify a server farm’s connection tracking method via the API. +### Modify a server cluster’s connection tracking method via the API. -#### View details on a server farm. +#### View details on a server cluster. -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on a HTTP farm. +With this call instruction, you can view details on a server cluster if you know its ID. In this example, we will work on a HTTP cluster. > [!api] > @@ -76,21 +76,21 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| +|farmId*|The cluster’s ID number| |Response (BackendHttp)|Meaning| |---|---| -|farmId|The farm’s ID number| -|balance|Balance type currently enabled for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection tracking method currently set for the farm| +|farmId|The cluster’s ID number| +|balance|Balance type currently enabled for the cluster| +|zone|Name of the zone in which the cluster is configured| +|port|Port used to contact the servers configured on the cluster| +|probe|Type of probe currently configured on the cluster| +|displayName|Name given to this cluster| +|stickiness|Connection tracking method currently set for the cluster| -#### Modify a server farm’s connection tracking method. +#### Modify a server cluster’s connection tracking method. -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on a HTTP farm. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: +With this call instruction, you can edit the settings of a server cluster if you know its ID. In this example, we will work on a HTTP cluster. To modify the tracking method, the BackendHttp.stickiness field must be updated with an available connection tracking method: > [!api] > @@ -100,8 +100,8 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| |serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.stickiness|Connection tracking method chosen for the farm| +|farmId*|The cluster’s ID number| +|BackendHttp.stickiness|Connection tracking method chosen for the cluster| #### Apply the modifications. diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-asia.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-asia.md index 2f2a1f7ea54..91942d73b40 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-asia.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: 'Routing an Additional IP' excerpt: 'Find out how to route an Additional IP and link it to the OVH Load Balancer' -updated: 2022-10-06 +updated: 2025-07-04 --- > [!primary] @@ -32,12 +32,12 @@ For more information on the OVH Load Balancer solution, you can read our [Introd > > Once you have confirmed the changes in the list of Additional IPs associated with the Load Balancer, you need to be able to refresh them. Several conditions need to be met for this to work. > -> - If the Load Balancer is in a vRack, all of the farms must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any farms in a vRack. +> - If the Load Balancer is in a vRack, all of the clusters must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any clusters in a vRack. > > - At least one existing front-end. All of the front-ends must be valid. They can be enabled and disabled, with either: > - a valid route (with routing rules) > - a redirection (`redirectLocation`{.action}) -> - a default farm +> - a default cluster > > - Nothing else should be refreshed for the Load Balancer. A Load Balancer cannot be refreshed several times at once. Doing so would not make any changes to the resulting configuration. > diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-au.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-au.md index a8acffb2dd4..654a0e6aef4 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-au.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-au.md @@ -1,7 +1,7 @@ --- title: 'Routing an Additional IP' excerpt: 'Find out how to route an Additional IP and link it to the OVH Load Balancer' -updated: 2022-10-06 +updated: 2025-07-04 --- > [!primary] @@ -32,12 +32,12 @@ For more information on the OVH Load Balancer solution, you can read our [Introd > > Once you have confirmed the changes in the list of Additional IPs associated with the Load Balancer, you need to be able to refresh them. Several conditions need to be met for this to work. > -> - If the Load Balancer is in a vRack, all of the farms must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any farms in a vRack. +> - If the Load Balancer is in a vRack, all of the clusters must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any clusters in a vRack. > > - At least one existing front-end. All of the front-ends must be valid. They can be enabled and disabled, with either: > - a valid route (with routing rules) > - a redirection (`redirectLocation`{.action}) -> - a default farm +> - a default cluster > > - Nothing else should be refreshed for the Load Balancer. A Load Balancer cannot be refreshed several times at once. Doing so would not make any changes to the resulting configuration. > diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-ca.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-ca.md index c95b9fbc0ad..6dc9d22f940 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-ca.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: 'Routing an Additional IP' excerpt: 'Find out how to route an Additional IP and link it to the OVH Load Balancer' -updated: 2022-10-06 +updated: 2025-07-04 --- > [!primary] @@ -32,12 +32,12 @@ For more information on the OVH Load Balancer solution, you can read our [Introd > > Once you have confirmed the changes in the list of Additional IPs associated with the Load Balancer, you need to be able to refresh them. Several conditions need to be met for this to work. > -> - If the Load Balancer is in a vRack, all of the farms must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any farms in a vRack. +> - If the Load Balancer is in a vRack, all of the clusters must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any clusters in a vRack. > > - At least one existing front-end. All of the front-ends must be valid. They can be enabled and disabled, with either: > - a valid route (with routing rules) > - a redirection (`redirectLocation`{.action}) -> - a default farm +> - a default cluster > > - Nothing else should be refreshed for the Load Balancer. A Load Balancer cannot be refreshed several times at once. Doing so would not make any changes to the resulting configuration. > diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-gb.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-gb.md index 15d15d1e5ac..3f84a735f6f 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-gb.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'Routing an Additional IP' excerpt: 'Find out how to route an Additional IP and link it to the OVH Load Balancer' -updated: 2022-10-06 +updated: 2025-07-04 --- > [!primary] @@ -32,12 +32,12 @@ For more information on the OVH Load Balancer solution, you can read our [Introd > > Once you have confirmed the changes in the list of Additional IPs associated with the Load Balancer, you need to be able to refresh them. Several conditions need to be met for this to work. > -> - If the Load Balancer is in a vRack, all of the farms must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any farms in a vRack. +> - If the Load Balancer is in a vRack, all of the clusters must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any clusters in a vRack. > > - At least one existing front-end. All of the front-ends must be valid. They can be enabled and disabled, with either: > - a valid route (with routing rules) > - a redirection (`redirectLocation`{.action}) -> - a default farm +> - a default cluster > > - Nothing else should be refreshed for the Load Balancer. A Load Balancer cannot be refreshed several times at once. Doing so would not make any changes to the resulting configuration. > diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-sg.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-sg.md index e32b1c08fcc..9eb2bde92d7 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-sg.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: 'Routing an Additional IP' excerpt: 'Find out how to route an Additional IP and link it to the OVH Load Balancer' -updated: 2022-10-06 +updated: 2025-07-04 --- > [!primary] @@ -32,12 +32,12 @@ For more information on the OVH Load Balancer solution, you can read our [Introd > > Once you have confirmed the changes in the list of Additional IPs associated with the Load Balancer, you need to be able to refresh them. Several conditions need to be met for this to work. > -> - If the Load Balancer is in a vRack, all of the farms must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any farms in a vRack. +> - If the Load Balancer is in a vRack, all of the clusters must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any clusters in a vRack. > > - At least one existing front-end. All of the front-ends must be valid. They can be enabled and disabled, with either: > - a valid route (with routing rules) > - a redirection (`redirectLocation`{.action}) -> - a default farm +> - a default cluster > > - Nothing else should be refreshed for the Load Balancer. A Load Balancer cannot be refreshed several times at once. Doing so would not make any changes to the resulting configuration. > diff --git a/pages/network/load_balancer/howto_route_ipfo/guide.en-us.md b/pages/network/load_balancer/howto_route_ipfo/guide.en-us.md index ede676b1881..5e2d8e612a9 100644 --- a/pages/network/load_balancer/howto_route_ipfo/guide.en-us.md +++ b/pages/network/load_balancer/howto_route_ipfo/guide.en-us.md @@ -1,7 +1,7 @@ --- title: 'Routing an Additional IP' excerpt: 'Find out how to route an Additional IP and link it to the OVH Load Balancer' -updated: 2022-10-06 +updated: 2025-07-04 --- > [!primary] @@ -32,12 +32,12 @@ For more information on the OVH Load Balancer solution, you can read our [Introd > > Once you have confirmed the changes in the list of Additional IPs associated with the Load Balancer, you need to be able to refresh them. Several conditions need to be met for this to work. > -> - If the Load Balancer is in a vRack, all of the farms must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any farms in a vRack. +> - If the Load Balancer is in a vRack, all of the clusters must also be in the vRack. The Load Balancer must also have its vLAN. Otherwise, there should not be any clusters in a vRack. > > - At least one existing front-end. All of the front-ends must be valid. They can be enabled and disabled, with either: > - a valid route (with routing rules) > - a redirection (`redirectLocation`{.action}) -> - a default farm +> - a default cluster > > - Nothing else should be refreshed for the Load Balancer. A Load Balancer cannot be refreshed several times at once. Doing so would not make any changes to the resulting configuration. > diff --git a/pages/network/load_balancer/retrieve_servers_state/guide.en-asia.md b/pages/network/load_balancer/retrieve_servers_state/guide.en-asia.md index 287e68d5d53..4bcea4e03ab 100644 --- a/pages/network/load_balancer/retrieve_servers_state/guide.en-asia.md +++ b/pages/network/load_balancer/retrieve_servers_state/guide.en-asia.md @@ -2,19 +2,19 @@ title: Retrieve server health status universe: cloud excerpt: Retrieve server status -updated: 2022-03-29 +updated: 2025-07-04 --- ## Presentation -The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired farm. +The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired cluster. Each server can be configured for the load balancer to check its status frequently. Once a server is detected as "down", the load balancer no longer sends any data to it and distributes the load among the remaining servers. -This can be practical in the case of server maintenance: you can take the server out of the farm, perform maintenance and then reintegrate it into the farm. +This can be practical in the case of server maintenance: you can take the server out of the cluster, perform maintenance and then reintegrate it into the cluster. -However, when a server is removed from the farm by the load balancer beyond our control, it can be interesting to know about it and why. +However, when a server is removed from the cluster by the load balancer beyond our control, it can be interesting to know about it and why. This tutorial explains how to know the health status of each server for each instance of your OVH Load Balancer. diff --git a/pages/network/load_balancer/retrieve_servers_state/guide.en-au.md b/pages/network/load_balancer/retrieve_servers_state/guide.en-au.md index 287e68d5d53..4bcea4e03ab 100644 --- a/pages/network/load_balancer/retrieve_servers_state/guide.en-au.md +++ b/pages/network/load_balancer/retrieve_servers_state/guide.en-au.md @@ -2,19 +2,19 @@ title: Retrieve server health status universe: cloud excerpt: Retrieve server status -updated: 2022-03-29 +updated: 2025-07-04 --- ## Presentation -The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired farm. +The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired cluster. Each server can be configured for the load balancer to check its status frequently. Once a server is detected as "down", the load balancer no longer sends any data to it and distributes the load among the remaining servers. -This can be practical in the case of server maintenance: you can take the server out of the farm, perform maintenance and then reintegrate it into the farm. +This can be practical in the case of server maintenance: you can take the server out of the cluster, perform maintenance and then reintegrate it into the cluster. -However, when a server is removed from the farm by the load balancer beyond our control, it can be interesting to know about it and why. +However, when a server is removed from the cluster by the load balancer beyond our control, it can be interesting to know about it and why. This tutorial explains how to know the health status of each server for each instance of your OVH Load Balancer. diff --git a/pages/network/load_balancer/retrieve_servers_state/guide.en-ca.md b/pages/network/load_balancer/retrieve_servers_state/guide.en-ca.md index 287e68d5d53..eb51a353dfa 100644 --- a/pages/network/load_balancer/retrieve_servers_state/guide.en-ca.md +++ b/pages/network/load_balancer/retrieve_servers_state/guide.en-ca.md @@ -6,15 +6,15 @@ updated: 2022-03-29 --- ## Presentation -The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired farm. +The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired cluster. Each server can be configured for the load balancer to check its status frequently. Once a server is detected as "down", the load balancer no longer sends any data to it and distributes the load among the remaining servers. -This can be practical in the case of server maintenance: you can take the server out of the farm, perform maintenance and then reintegrate it into the farm. +This can be practical in the case of server maintenance: you can take the server out of the cluster, perform maintenance and then reintegrate it into the cluster. -However, when a server is removed from the farm by the load balancer beyond our control, it can be interesting to know about it and why. +However, when a server is removed from the cluster by the load balancer beyond our control, it can be interesting to know about it and why. This tutorial explains how to know the health status of each server for each instance of your OVH Load Balancer. diff --git a/pages/network/load_balancer/retrieve_servers_state/guide.en-gb.md b/pages/network/load_balancer/retrieve_servers_state/guide.en-gb.md index 287e68d5d53..4bcea4e03ab 100644 --- a/pages/network/load_balancer/retrieve_servers_state/guide.en-gb.md +++ b/pages/network/load_balancer/retrieve_servers_state/guide.en-gb.md @@ -2,19 +2,19 @@ title: Retrieve server health status universe: cloud excerpt: Retrieve server status -updated: 2022-03-29 +updated: 2025-07-04 --- ## Presentation -The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired farm. +The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired cluster. Each server can be configured for the load balancer to check its status frequently. Once a server is detected as "down", the load balancer no longer sends any data to it and distributes the load among the remaining servers. -This can be practical in the case of server maintenance: you can take the server out of the farm, perform maintenance and then reintegrate it into the farm. +This can be practical in the case of server maintenance: you can take the server out of the cluster, perform maintenance and then reintegrate it into the cluster. -However, when a server is removed from the farm by the load balancer beyond our control, it can be interesting to know about it and why. +However, when a server is removed from the cluster by the load balancer beyond our control, it can be interesting to know about it and why. This tutorial explains how to know the health status of each server for each instance of your OVH Load Balancer. diff --git a/pages/network/load_balancer/retrieve_servers_state/guide.en-sg.md b/pages/network/load_balancer/retrieve_servers_state/guide.en-sg.md index 287e68d5d53..4bcea4e03ab 100644 --- a/pages/network/load_balancer/retrieve_servers_state/guide.en-sg.md +++ b/pages/network/load_balancer/retrieve_servers_state/guide.en-sg.md @@ -2,19 +2,19 @@ title: Retrieve server health status universe: cloud excerpt: Retrieve server status -updated: 2022-03-29 +updated: 2025-07-04 --- ## Presentation -The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired farm. +The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired cluster. Each server can be configured for the load balancer to check its status frequently. Once a server is detected as "down", the load balancer no longer sends any data to it and distributes the load among the remaining servers. -This can be practical in the case of server maintenance: you can take the server out of the farm, perform maintenance and then reintegrate it into the farm. +This can be practical in the case of server maintenance: you can take the server out of the cluster, perform maintenance and then reintegrate it into the cluster. -However, when a server is removed from the farm by the load balancer beyond our control, it can be interesting to know about it and why. +However, when a server is removed from the cluster by the load balancer beyond our control, it can be interesting to know about it and why. This tutorial explains how to know the health status of each server for each instance of your OVH Load Balancer. diff --git a/pages/network/load_balancer/retrieve_servers_state/guide.en-us.md b/pages/network/load_balancer/retrieve_servers_state/guide.en-us.md index 287e68d5d53..4bcea4e03ab 100644 --- a/pages/network/load_balancer/retrieve_servers_state/guide.en-us.md +++ b/pages/network/load_balancer/retrieve_servers_state/guide.en-us.md @@ -2,19 +2,19 @@ title: Retrieve server health status universe: cloud excerpt: Retrieve server status -updated: 2022-03-29 +updated: 2025-07-04 --- ## Presentation -The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired farm. +The OVH Load Balancer service acts by default as a proxy. That is to say that it distributes the load (requests) it receives between all the servers of the desired cluster. Each server can be configured for the load balancer to check its status frequently. Once a server is detected as "down", the load balancer no longer sends any data to it and distributes the load among the remaining servers. -This can be practical in the case of server maintenance: you can take the server out of the farm, perform maintenance and then reintegrate it into the farm. +This can be practical in the case of server maintenance: you can take the server out of the cluster, perform maintenance and then reintegrate it into the cluster. -However, when a server is removed from the farm by the load balancer beyond our control, it can be interesting to know about it and why. +However, when a server is removed from the cluster by the load balancer beyond our control, it can be interesting to know about it and why. This tutorial explains how to know the health status of each server for each instance of your OVH Load Balancer. diff --git a/pages/network/load_balancer/use-lb/guide.en-asia.md b/pages/network/load_balancer/use-lb/guide.en-asia.md index f6870600f64..9604e214d7c 100644 --- a/pages/network/load_balancer/use-lb/guide.en-asia.md +++ b/pages/network/load_balancer/use-lb/guide.en-asia.md @@ -1,126 +1,124 @@ --- -title: Managing the Load Balancer from the customer control panel -excerpt: Summary of the main features and Load Balancer ownership through the customer control panel -updated: 2017-12-01 +title: Managing your Load Balancer service via the Control Panel +excerpt: An overview of the main features, and how to get started using the Load Balancer service from the Control Panel +updated: 2025-07-04 --- ## Objective -The goal of this guide is to assist you when you first operate your Load Balancer by introducing the solution’s main features. +This guide is designed to help you get started using the Load Balancer, by introducing the main features of the solution. ## Requirements -- Access to your customer control panel -- Owning a [Load Balancer](https://www.ovh.com/asia/solutions/load-balancer/) +- You must have access to your OVH Control Panel. +- You must have ordered a [Load Balancer.](https://www.ovh.com/fr/solutions/load-balancer) -## In practice +## Instructions -### Managing your Load Balancer from the customer control panel +### Managing your Load Balancer via the Control Panel To manage your Load Balancer via the Control Panel, go to the `Bare Metal Cloud`{.action} section, click `Network`{.action} and `Load Balancer`{.action}. The main page for the service will then appear: ![Load Balancer](images/lbip-main.png){.thumbnail} -On this home page, you will find the following information: +On this page, you will see the following information: -|Element|Function| +|Element|Purpose| |---|---| -|Status|Summary of your Load Balancer with IP, front-ends, operational farms and added servers| -|Usage|A summary of your LoadBalancer usage| -|Graphs|Here you will find the graphs in relation to your service and based on simultaneous connections or the number of requests per minute| -|Details|Your IPv4 and the Additional IPs attached as well as the number of outbound IPv4 (details available by clicking on the ellipsis)| -|Configuration|This is where you can customize the name of your service (which will appear at the top in the left column) The cipher(s), which are customizable, as well as the data centre where your Load Balancer is located| -|Subscription|You will find below all the administrative details pertaining to your offer| +|Status|An overview of your Load Balancer with the IP, front-ends, functional clusters and servers added| +|Use|A summary of how to use your Load Balancer| +|Graphs|In this section, you will see the graphs linked to service, by concurrent connections or requests per minute| +|Information|Your IPv4 and IPv6 address and the Additional IPs linked to them, as well as the number of outgoing IPv4s (see more details by clicking on the `...`{.action} button)| +|Configuration|Here, you can customise the name of your solution (which will appear at the top of the left-hand column) The cipher(s) are customisable, as well as the availability zones where your Load Balancer is based| +|Subscription|Here, you will see the admin details for your solution| -To add a `front-end`{.action} or some `server farms`{.action}, simply click on their respective buttons. A context menu will then help you to configure each part of your service. +To add `front-ends`{.action} or `Server clusters`{.action}, simply click on their respective buttons. A form will then help you configure each part of your solution. -### Managing your frontends +### Managing front-ends -In order to add front-ends, all you need to do is go to the `Frontends`{.action} section and click on `Add a front-end`{.action}. You will then gain access to the following menu: +To add front-ends, simply go to the `Front-ends`{.action} section, and click `Add a front-end`{.action}. The following menu will then appear: -![Add front-end](images/iplb-add-front-end.png){.thumbnail} +![Add front-end](images/add_frontend.png){.thumbnail} -Details of a front-end component +Details of front-end parts: -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your frontend if you wish; this can be very useful when you have several of them to identify them quickly| +|Name|If you want, you can choose a name for your front-end. This is very useful when you have several front-ends, so you can tell them apart quickly| |Protocol|You can choose between HTTP, HTTPS, TCP, SSL TCP (or TLS) and UDP| -|Port|Choose which listening port to use| -|Data centre|You can choose between your data centre or all of them to create your front-end| -|Default farm|If you have several configured farms, you can choose one by default for each front-end| +|Port|Choose the listening port you wish to use| +|Datacentre|Choose between your availability zone or all availability zones to create your front-end| +|Default cluster|If you have several clusters configured, you can choose one of them as a default for each front-end| -You also have access to advanced settings: +You can also access advanced settings: ![Advanced settings](images/advanced_frontend.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| |Dedicated Additional IP|List of Additional IPs for remote servers| -|Restricting access to some IPs|List that allows restricting remote access to the Load Balancer, only in IPv4| -|HTTP redirection|Adding an HTTP redirect URL| -|HTTP header|Add an HTTP header here| +|Restrict access to IPs|List for restricting remote access to the Load Balancer, for IPv4 only| +|HTTP redirection|Add a HTTP redirection URL| +|HTTP header|Add a HTTP header here| -### Managing your server cluster +### Managing your clusters -In order to add a server cluster, all you need to do is go to the `Server clusters`{.action} section and click on `Add a server cluster`{.action}. You will gain access to the same main features as for the frontend However, advanced options will be different: +To add a server cluster, simply go to the `Server clusters`{.action} section, and click `Add a server cluster`{.action}. You will get the same main options as for the front-end. However, the advanced options are different: -![Adding a farm](images/iplb-cluster-adv.png){.thumbnail} +![Add a cluster](images/advanced_cluster.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Distribution mode|Choice between Round-robin, First, Last, Source or URI for your IP balancing| -|Session tracking|Session tracking can be done through Cookie or IP Source, to be determined here| -|Probe|Probe choice and activation| +|Distribution method|Choosing between Round-robin, First, Last, Source or URI for your IP load balancing| +|Track session|You can track sessions via Cookie or source IP, this can be defined here| +|Probe|Choosing and activating a probe| ### Managing your servers -Once your server farm has been created, you need to add servers to it. Below are the details for advanced options: +Once you have created your server cluster, you just need to add servers to it. Details on these options are below, as well as advanced options: -![Add a server](images/iplb-cluster-add-server.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-1.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-2.png){.thumbnail} +![Add server](images/add_server.png){.thumbnail} +![Add server](images/add_server_advanced.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your server if you wish; this can be very useful when you have several of them to identify them quickly| -|IPv4 address|Adding the IP of the service that will be used as a server| +|Name|If you want, you can choose a name for your server. This is very useful when you have several servers, so you can tell them apart quickly| +|IPv4 address|Adding the IP address of the service that will act as a server| |Port|Server port| -|Backup server|Making sure to specify that this is a backup server| -|Use the farm’s availability probe|Choosing the probe that was approved during the creation of the farm| -|Encrypting requests with SSL|Encrypting requests with an SSL certificate| -|Cookie|Adding a customized session cookie| -|Certificate chain|Adding a certificate chain| -|Load balancing weight|Choosing the balancing weight for load distribution| +|Backup server|Selecting which server is a backup server| +|Use the server cluster’s probe|Choosing the probe that was validated when you created the cluster| +|Encrypt requests with SSL|Encrypting requests with an SSL certificate| +|Cookie|Add a customised session cookie| +|Certificate chain|Add a certificate chain| +|Balancing weight|Choose the balancing weight for the load balancer| +|PROXY Protocol version|**Only if you have configured it**, choose the version of the PROXY protocol you wish to use on the server.
You can find more information on the PROXY protocol and how to use it with the OVHcloud Load Balancer in [this guide](/pages/network/load_balancer/create_proxyprotocol/).| -### Managing SSL Certificates - -An SSL certificate can be added to the Load Balancer in the `SSL Certificate`{.action} section You will then have two possibilities: either ordering an SSL certificate through OVH or adding an external certificate. +### Managing SSL certificates +You can add an SSL certificate to the Load Balancer in the `SSL Certificate`{.action} section. You have two options: you can order an SSL certificate from OVH, or add an external certificate. #### OVH SSL certificate +To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click `Order an SSL certificate`{.action} and browse the options available: -To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click on `Order an SSL Certificate`{.action} and let us guide you: - -![Ordering an SSL Certificate](images/iplb-order-ssl.png){.thumbnail} +![Ordering an SSL certificate](images/ordering_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Types of certificate|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| -|Fully Qualified Domain Name (FQDN)|Affected domains| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Certificate type|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| +|Fully Qualified Domain Name (FQDN)|Domain(s) concerned| #### Adding an external SSL certificate - If you already have your own SSL certificate, you can add it directly: -![Adding an SSL Certificate](images/iplb-add-ssl.png){.thumbnail} +![Adding an SSL certificate](images/external_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your certificate if you wish; this can be very useful when you have several of them to identify them quickly| -|Private key|Field where a private key can be added to the service| -|Certificate|Certificate field| -|Chain|Field where a root certificate can be added if necessary| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Private key|Field for entering the private key to add to the service| +|Certificate|Field for adding the certificate| +|Chain|Field for adding the root certificate, if required| -## Going further +## Go further -Discuss with our user community at . \ No newline at end of file +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.en-au.md b/pages/network/load_balancer/use-lb/guide.en-au.md index 9533456e2e9..9604e214d7c 100644 --- a/pages/network/load_balancer/use-lb/guide.en-au.md +++ b/pages/network/load_balancer/use-lb/guide.en-au.md @@ -1,126 +1,124 @@ --- -title: Managing the Load Balancer from the customer control panel -excerpt: Summary of the main features and Load Balancer ownership through the customer control panel -updated: 2017-12-01 +title: Managing your Load Balancer service via the Control Panel +excerpt: An overview of the main features, and how to get started using the Load Balancer service from the Control Panel +updated: 2025-07-04 --- ## Objective -The goal of this guide is to assist you when you first operate your Load Balancer by introducing the solution’s main features. +This guide is designed to help you get started using the Load Balancer, by introducing the main features of the solution. ## Requirements -- Access to your customer control panel -- Owning a [Load Balancer](https://www.ovh.com.au/solutions/load-balancer/) +- You must have access to your OVH Control Panel. +- You must have ordered a [Load Balancer.](https://www.ovh.com/fr/solutions/load-balancer) -## In practice +## Instructions -### Managing your Load Balancer from the customer control panel +### Managing your Load Balancer via the Control Panel To manage your Load Balancer via the Control Panel, go to the `Bare Metal Cloud`{.action} section, click `Network`{.action} and `Load Balancer`{.action}. The main page for the service will then appear: ![Load Balancer](images/lbip-main.png){.thumbnail} -On this home page, you will find the following information: +On this page, you will see the following information: -|Element|Function| +|Element|Purpose| |---|---| -|Status|Summary of your Load Balancer with IP, front-ends, operational farms and added servers| -|Usage|A summary of your LoadBalancer usage| -|Graphs|Here you will find the graphs in relation to your service and based on simultaneous connections or the number of requests per minute| -|Details|Your IPv4 and the Additional IPs attached as well as the number of outbound IPv4 (details available by clicking on the ellipsis)| -|Configuration|This is where you can customize the name of your service (which will appear at the top in the left column) The cipher(s), which are customizable, as well as the data centre where your Load Balancer is located| -|Subscription|You will find below all the administrative details pertaining to your offer| +|Status|An overview of your Load Balancer with the IP, front-ends, functional clusters and servers added| +|Use|A summary of how to use your Load Balancer| +|Graphs|In this section, you will see the graphs linked to service, by concurrent connections or requests per minute| +|Information|Your IPv4 and IPv6 address and the Additional IPs linked to them, as well as the number of outgoing IPv4s (see more details by clicking on the `...`{.action} button)| +|Configuration|Here, you can customise the name of your solution (which will appear at the top of the left-hand column) The cipher(s) are customisable, as well as the availability zones where your Load Balancer is based| +|Subscription|Here, you will see the admin details for your solution| -To add a `front-end`{.action} or some `server farms`{.action}, simply click on their respective buttons. A context menu will then help you to configure each part of your service. +To add `front-ends`{.action} or `Server clusters`{.action}, simply click on their respective buttons. A form will then help you configure each part of your solution. -### Managing your frontends +### Managing front-ends -In order to add front-ends, all you need to do is go to the `Frontends`{.action} section and click on `Add a front-end`{.action}. You will then gain access to the following menu: +To add front-ends, simply go to the `Front-ends`{.action} section, and click `Add a front-end`{.action}. The following menu will then appear: -![Add front-end](images/iplb-add-front-end.png){.thumbnail} +![Add front-end](images/add_frontend.png){.thumbnail} -Details of a front-end component +Details of front-end parts: -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your frontend if you wish; this can be very useful when you have several of them to identify them quickly| +|Name|If you want, you can choose a name for your front-end. This is very useful when you have several front-ends, so you can tell them apart quickly| |Protocol|You can choose between HTTP, HTTPS, TCP, SSL TCP (or TLS) and UDP| -|Port|Choose which listening port to use| -|Data centre|You can choose between your data centre or all of them to create your front-end| -|Default farm|If you have several configured farms, you can choose one by default for each front-end| +|Port|Choose the listening port you wish to use| +|Datacentre|Choose between your availability zone or all availability zones to create your front-end| +|Default cluster|If you have several clusters configured, you can choose one of them as a default for each front-end| -You also have access to advanced settings: +You can also access advanced settings: ![Advanced settings](images/advanced_frontend.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| |Dedicated Additional IP|List of Additional IPs for remote servers| -|Restricting access to some IPs|List that allows restricting remote access to the Load Balancer, only in IPv4| -|HTTP redirection|Adding an HTTP redirect URL| -|HTTP header|Add an HTTP header here| +|Restrict access to IPs|List for restricting remote access to the Load Balancer, for IPv4 only| +|HTTP redirection|Add a HTTP redirection URL| +|HTTP header|Add a HTTP header here| -### Managing your server cluster +### Managing your clusters -In order to add a server cluster, all you need to do is go to the `Server clusters`{.action} section and click on `Add a server cluster`{.action}. You will gain access to the same main features as for the frontend However, advanced options will be different: +To add a server cluster, simply go to the `Server clusters`{.action} section, and click `Add a server cluster`{.action}. You will get the same main options as for the front-end. However, the advanced options are different: -![Adding a farm](images/iplb-cluster-adv.png){.thumbnail} +![Add a cluster](images/advanced_cluster.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Distribution mode|Choice between Round-robin, First, Last, Source or URI for your IP balancing| -|Session tracking|Session tracking can be done through Cookie or IP Source, to be determined here| -|Probe|Probe choice and activation| +|Distribution method|Choosing between Round-robin, First, Last, Source or URI for your IP load balancing| +|Track session|You can track sessions via Cookie or source IP, this can be defined here| +|Probe|Choosing and activating a probe| ### Managing your servers -Once your server farm has been created, you need to add servers to it. Below are the details for advanced options: +Once you have created your server cluster, you just need to add servers to it. Details on these options are below, as well as advanced options: -![Add a server](images/iplb-cluster-add-server.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-1.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-2.png){.thumbnail} +![Add server](images/add_server.png){.thumbnail} +![Add server](images/add_server_advanced.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your server if you wish; this can be very useful when you have several of them to identify them quickly| -|IPv4 address|Adding the IP of the service that will be used as a server| +|Name|If you want, you can choose a name for your server. This is very useful when you have several servers, so you can tell them apart quickly| +|IPv4 address|Adding the IP address of the service that will act as a server| |Port|Server port| -|Backup server|Making sure to specify that this is a backup server| -|Use the farm’s availability probe|Choosing the probe that was approved during the creation of the farm| -|Encrypting requests with SSL|Encrypting requests with an SSL certificate| -|Cookie|Adding a customized session cookie| -|Certificate chain|Adding a certificate chain| -|Load balancing weight|Choosing the balancing weight for load distribution| +|Backup server|Selecting which server is a backup server| +|Use the server cluster’s probe|Choosing the probe that was validated when you created the cluster| +|Encrypt requests with SSL|Encrypting requests with an SSL certificate| +|Cookie|Add a customised session cookie| +|Certificate chain|Add a certificate chain| +|Balancing weight|Choose the balancing weight for the load balancer| +|PROXY Protocol version|**Only if you have configured it**, choose the version of the PROXY protocol you wish to use on the server.
You can find more information on the PROXY protocol and how to use it with the OVHcloud Load Balancer in [this guide](/pages/network/load_balancer/create_proxyprotocol/).| -### Managing SSL Certificates - -An SSL certificate can be added to the Load Balancer in the `SSL Certificate`{.action} section You will then have two possibilities: either ordering an SSL certificate through OVH or adding an external certificate. +### Managing SSL certificates +You can add an SSL certificate to the Load Balancer in the `SSL Certificate`{.action} section. You have two options: you can order an SSL certificate from OVH, or add an external certificate. #### OVH SSL certificate +To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click `Order an SSL certificate`{.action} and browse the options available: -To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click on `Order an SSL Certificate`{.action} and let us guide you: - -![Ordering an SSL Certificate](images/iplb-order-ssl.png){.thumbnail} +![Ordering an SSL certificate](images/ordering_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Types of certificate|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| -|Fully Qualified Domain Name (FQDN)|Affected domains| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Certificate type|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| +|Fully Qualified Domain Name (FQDN)|Domain(s) concerned| #### Adding an external SSL certificate - If you already have your own SSL certificate, you can add it directly: -![Adding an SSL Certificate](images/iplb-add-ssl.png){.thumbnail} +![Adding an SSL certificate](images/external_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your certificate if you wish; this can be very useful when you have several of them to identify them quickly| -|Private key|Field where a private key can be added to the service| -|Certificate|Certificate field| -|Chain|Field where a root certificate can be added if necessary| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Private key|Field for entering the private key to add to the service| +|Certificate|Field for adding the certificate| +|Chain|Field for adding the root certificate, if required| -## Going further +## Go further -Discuss with our user community at . \ No newline at end of file +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.en-ca.md b/pages/network/load_balancer/use-lb/guide.en-ca.md index eab482b9a35..9604e214d7c 100644 --- a/pages/network/load_balancer/use-lb/guide.en-ca.md +++ b/pages/network/load_balancer/use-lb/guide.en-ca.md @@ -1,126 +1,124 @@ --- -title: Managing the Load Balancer from the customer control panel -excerpt: Summary of the main features and Load Balancer ownership through the customer control panel -updated: 2017-12-01 +title: Managing your Load Balancer service via the Control Panel +excerpt: An overview of the main features, and how to get started using the Load Balancer service from the Control Panel +updated: 2025-07-04 --- ## Objective -The goal of this guide is to assist you when you first operate your Load Balancer by introducing the solution’s main features. +This guide is designed to help you get started using the Load Balancer, by introducing the main features of the solution. ## Requirements -- Access to your customer control panel -- Owning a [Load Balancer](https://www.ovh.com/ca/en/solutions/load-balancer/) +- You must have access to your OVH Control Panel. +- You must have ordered a [Load Balancer.](https://www.ovh.com/fr/solutions/load-balancer) -## In practice +## Instructions -### Managing your Load Balancer from the customer control panel +### Managing your Load Balancer via the Control Panel To manage your Load Balancer via the Control Panel, go to the `Bare Metal Cloud`{.action} section, click `Network`{.action} and `Load Balancer`{.action}. The main page for the service will then appear: ![Load Balancer](images/lbip-main.png){.thumbnail} -On this home page, you will find the following information: +On this page, you will see the following information: -|Element|Function| +|Element|Purpose| |---|---| -|Status|Summary of your Load Balancer with IP, front-ends, operational farms and added servers| -|Usage|A summary of your LoadBalancer usage| -|Graphs|Here you will find the graphs in relation to your service and based on simultaneous connections or the number of requests per minute| -|Details|Your IPv4 and the Additional IPs attached as well as the number of outbound IPv4 (details available by clicking on the ellipsis)| -|Configuration|This is where you can customize the name of your service (which will appear at the top in the left column) The cipher(s), which are customizable, as well as the data centre where your Load Balancer is located| -|Subscription|You will find below all the administrative details pertaining to your offer| +|Status|An overview of your Load Balancer with the IP, front-ends, functional clusters and servers added| +|Use|A summary of how to use your Load Balancer| +|Graphs|In this section, you will see the graphs linked to service, by concurrent connections or requests per minute| +|Information|Your IPv4 and IPv6 address and the Additional IPs linked to them, as well as the number of outgoing IPv4s (see more details by clicking on the `...`{.action} button)| +|Configuration|Here, you can customise the name of your solution (which will appear at the top of the left-hand column) The cipher(s) are customisable, as well as the availability zones where your Load Balancer is based| +|Subscription|Here, you will see the admin details for your solution| -To add a `front-end`{.action} or some `server farms`{.action}, simply click on their respective buttons. A context menu will then help you to configure each part of your service. +To add `front-ends`{.action} or `Server clusters`{.action}, simply click on their respective buttons. A form will then help you configure each part of your solution. -### Managing your frontends +### Managing front-ends -In order to add front-ends, all you need to do is go to the `Frontends`{.action} section and click on `Add a front-end`{.action}. You will then gain access to the following menu: +To add front-ends, simply go to the `Front-ends`{.action} section, and click `Add a front-end`{.action}. The following menu will then appear: -![Add front-end](images/iplb-add-front-end.png){.thumbnail} +![Add front-end](images/add_frontend.png){.thumbnail} -Details of a front-end component +Details of front-end parts: -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your frontend if you wish; this can be very useful when you have several of them to identify them quickly| +|Name|If you want, you can choose a name for your front-end. This is very useful when you have several front-ends, so you can tell them apart quickly| |Protocol|You can choose between HTTP, HTTPS, TCP, SSL TCP (or TLS) and UDP| -|Port|Choose which listening port to use| -|Data centre|You can choose between your data centre or all of them to create your front-end| -|Default farm|If you have several configured farms, you can choose one by default for each front-end| +|Port|Choose the listening port you wish to use| +|Datacentre|Choose between your availability zone or all availability zones to create your front-end| +|Default cluster|If you have several clusters configured, you can choose one of them as a default for each front-end| -You also have access to advanced settings: +You can also access advanced settings: ![Advanced settings](images/advanced_frontend.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| |Dedicated Additional IP|List of Additional IPs for remote servers| -|Restricting access to some IPs|List that allows restricting remote access to the Load Balancer, only in IPv4| -|HTTP redirection|Adding an HTTP redirect URL| -|HTTP header|Add an HTTP header here| +|Restrict access to IPs|List for restricting remote access to the Load Balancer, for IPv4 only| +|HTTP redirection|Add a HTTP redirection URL| +|HTTP header|Add a HTTP header here| -### Managing your server cluster +### Managing your clusters -In order to add a server cluster, all you need to do is go to the `Server clusters`{.action} section and click on `Add a server cluster`{.action}. You will gain access to the same main features as for the frontend However, advanced options will be different: +To add a server cluster, simply go to the `Server clusters`{.action} section, and click `Add a server cluster`{.action}. You will get the same main options as for the front-end. However, the advanced options are different: -![Adding a farm](images/iplb-cluster-adv.png){.thumbnail} +![Add a cluster](images/advanced_cluster.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Distribution mode|Choice between Round-robin, First, Last, Source or URI for your IP balancing| -|Session tracking|Session tracking can be done through Cookie or IP Source, to be determined here| -|Probe|Probe choice and activation| +|Distribution method|Choosing between Round-robin, First, Last, Source or URI for your IP load balancing| +|Track session|You can track sessions via Cookie or source IP, this can be defined here| +|Probe|Choosing and activating a probe| ### Managing your servers -Once your server farm has been created, you need to add servers to it. Below are the details for advanced options: +Once you have created your server cluster, you just need to add servers to it. Details on these options are below, as well as advanced options: -![Add a server](images/iplb-cluster-add-server.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-1.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-2.png){.thumbnail} +![Add server](images/add_server.png){.thumbnail} +![Add server](images/add_server_advanced.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your server if you wish; this can be very useful when you have several of them to identify them quickly| -|IPv4 address|Adding the IP of the service that will be used as a server| +|Name|If you want, you can choose a name for your server. This is very useful when you have several servers, so you can tell them apart quickly| +|IPv4 address|Adding the IP address of the service that will act as a server| |Port|Server port| -|Backup server|Making sure to specify that this is a backup server| -|Use the farm’s availability probe|Choosing the probe that was approved during the creation of the farm| -|Encrypting requests with SSL|Encrypting requests with an SSL certificate| -|Cookie|Adding a customized session cookie| -|Certificate chain|Adding a certificate chain| -|Load balancing weight|Choosing the balancing weight for load distribution| +|Backup server|Selecting which server is a backup server| +|Use the server cluster’s probe|Choosing the probe that was validated when you created the cluster| +|Encrypt requests with SSL|Encrypting requests with an SSL certificate| +|Cookie|Add a customised session cookie| +|Certificate chain|Add a certificate chain| +|Balancing weight|Choose the balancing weight for the load balancer| +|PROXY Protocol version|**Only if you have configured it**, choose the version of the PROXY protocol you wish to use on the server.
You can find more information on the PROXY protocol and how to use it with the OVHcloud Load Balancer in [this guide](/pages/network/load_balancer/create_proxyprotocol/).| -### Managing SSL Certificates - -An SSL certificate can be added to the Load Balancer in the `SSL Certificate`{.action} section You will then have two possibilities: either ordering an SSL certificate through OVH or adding an external certificate. +### Managing SSL certificates +You can add an SSL certificate to the Load Balancer in the `SSL Certificate`{.action} section. You have two options: you can order an SSL certificate from OVH, or add an external certificate. #### OVH SSL certificate +To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click `Order an SSL certificate`{.action} and browse the options available: -To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click on `Order an SSL Certificate`{.action} and let us guide you: - -![Ordering an SSL Certificate](images/iplb-order-ssl.png){.thumbnail} +![Ordering an SSL certificate](images/ordering_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Types of certificate|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| -|Fully Qualified Domain Name (FQDN)|Affected domains| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Certificate type|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| +|Fully Qualified Domain Name (FQDN)|Domain(s) concerned| #### Adding an external SSL certificate - If you already have your own SSL certificate, you can add it directly: -![Adding an SSL Certificate](images/iplb-add-ssl.png){.thumbnail} +![Adding an SSL certificate](images/external_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your certificate if you wish; this can be very useful when you have several of them to identify them quickly| -|Private key|Field where a private key can be added to the service| -|Certificate|Certificate field| -|Chain|Field where a root certificate can be added if necessary| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Private key|Field for entering the private key to add to the service| +|Certificate|Field for adding the certificate| +|Chain|Field for adding the root certificate, if required| -## Going further +## Go further -Discuss with our user community at . \ No newline at end of file +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.en-sg.md b/pages/network/load_balancer/use-lb/guide.en-sg.md index 9c708ab1ea6..9604e214d7c 100644 --- a/pages/network/load_balancer/use-lb/guide.en-sg.md +++ b/pages/network/load_balancer/use-lb/guide.en-sg.md @@ -1,126 +1,124 @@ --- -title: Managing the Load Balancer from the customer control panel -excerpt: Summary of the main features and Load Balancer ownership through the customer control panel -updated: 2017-12-01 +title: Managing your Load Balancer service via the Control Panel +excerpt: An overview of the main features, and how to get started using the Load Balancer service from the Control Panel +updated: 2025-07-04 --- ## Objective -The goal of this guide is to assist you when you first operate your Load Balancer by introducing the solution’s main features. +This guide is designed to help you get started using the Load Balancer, by introducing the main features of the solution. ## Requirements -- Access to your customer control panel -- Owning a [Load Balancer](https://www.ovh.com/sg/solutions/load-balancer/) +- You must have access to your OVH Control Panel. +- You must have ordered a [Load Balancer.](https://www.ovh.com/fr/solutions/load-balancer) -## In practice +## Instructions -### Managing your Load Balancer from the customer control panel +### Managing your Load Balancer via the Control Panel To manage your Load Balancer via the Control Panel, go to the `Bare Metal Cloud`{.action} section, click `Network`{.action} and `Load Balancer`{.action}. The main page for the service will then appear: ![Load Balancer](images/lbip-main.png){.thumbnail} -On this home page, you will find the following information: +On this page, you will see the following information: -|Element|Function| +|Element|Purpose| |---|---| -|Status|Summary of your Load Balancer with IP, front-ends, operational farms and added servers| -|Usage|A summary of your LoadBalancer usage| -|Graphs|Here you will find the graphs in relation to your service and based on simultaneous connections or the number of requests per minute| -|Details|Your IPv4 and the Additional IPs attached as well as the number of outbound IPv4 (details available by clicking on the ellipsis)| -|Configuration|This is where you can customize the name of your service (which will appear at the top in the left column) The cipher(s), which are customizable, as well as the data centre where your Load Balancer is located| -|Subscription|You will find below all the administrative details pertaining to your offer| +|Status|An overview of your Load Balancer with the IP, front-ends, functional clusters and servers added| +|Use|A summary of how to use your Load Balancer| +|Graphs|In this section, you will see the graphs linked to service, by concurrent connections or requests per minute| +|Information|Your IPv4 and IPv6 address and the Additional IPs linked to them, as well as the number of outgoing IPv4s (see more details by clicking on the `...`{.action} button)| +|Configuration|Here, you can customise the name of your solution (which will appear at the top of the left-hand column) The cipher(s) are customisable, as well as the availability zones where your Load Balancer is based| +|Subscription|Here, you will see the admin details for your solution| -To add a `front-end`{.action} or some `server farms`{.action}, simply click on their respective buttons. A context menu will then help you to configure each part of your service. +To add `front-ends`{.action} or `Server clusters`{.action}, simply click on their respective buttons. A form will then help you configure each part of your solution. -### Managing your frontends +### Managing front-ends -In order to add front-ends, all you need to do is go to the `Frontends`{.action} section and click on `Add a front-end`{.action}. You will then gain access to the following menu: +To add front-ends, simply go to the `Front-ends`{.action} section, and click `Add a front-end`{.action}. The following menu will then appear: -![Add front-end](images/iplb-add-front-end.png){.thumbnail} +![Add front-end](images/add_frontend.png){.thumbnail} -Details of a front-end component +Details of front-end parts: -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your frontend if you wish; this can be very useful when you have several of them to identify them quickly| +|Name|If you want, you can choose a name for your front-end. This is very useful when you have several front-ends, so you can tell them apart quickly| |Protocol|You can choose between HTTP, HTTPS, TCP, SSL TCP (or TLS) and UDP| -|Port|Choose which listening port to use| -|Data centre|You can choose between your data centre or all of them to create your front-end| -|Default farm|If you have several configured farms, you can choose one by default for each front-end| +|Port|Choose the listening port you wish to use| +|Datacentre|Choose between your availability zone or all availability zones to create your front-end| +|Default cluster|If you have several clusters configured, you can choose one of them as a default for each front-end| -You also have access to advanced settings: +You can also access advanced settings: ![Advanced settings](images/advanced_frontend.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| |Dedicated Additional IP|List of Additional IPs for remote servers| -|Restricting access to some IPs|List that allows restricting remote access to the Load Balancer, only in IPv4| -|HTTP redirection|Adding an HTTP redirect URL| -|HTTP header|Add an HTTP header here| +|Restrict access to IPs|List for restricting remote access to the Load Balancer, for IPv4 only| +|HTTP redirection|Add a HTTP redirection URL| +|HTTP header|Add a HTTP header here| -### Managing your server cluster +### Managing your clusters -In order to add a server cluster, all you need to do is go to the `Server clusters`{.action} section and click on `Add a server cluster`{.action}. You will gain access to the same main features as for the frontend However, advanced options will be different: +To add a server cluster, simply go to the `Server clusters`{.action} section, and click `Add a server cluster`{.action}. You will get the same main options as for the front-end. However, the advanced options are different: -![Adding a farm](images/iplb-cluster-adv.png){.thumbnail} +![Add a cluster](images/advanced_cluster.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Distribution mode|Choice between Round-robin, First, Last, Source or URI for your IP balancing| -|Session tracking|Session tracking can be done through Cookie or IP Source, to be determined here| -|Probe|Probe choice and activation| +|Distribution method|Choosing between Round-robin, First, Last, Source or URI for your IP load balancing| +|Track session|You can track sessions via Cookie or source IP, this can be defined here| +|Probe|Choosing and activating a probe| ### Managing your servers -Once your server farm has been created, you need to add servers to it. Below are the details for advanced options: +Once you have created your server cluster, you just need to add servers to it. Details on these options are below, as well as advanced options: -![Add a server](images/iplb-cluster-add-server.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-1.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-2.png){.thumbnail} +![Add server](images/add_server.png){.thumbnail} +![Add server](images/add_server_advanced.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your server if you wish; this can be very useful when you have several of them to identify them quickly| -|IPv4 address|Adding the IP of the service that will be used as a server| +|Name|If you want, you can choose a name for your server. This is very useful when you have several servers, so you can tell them apart quickly| +|IPv4 address|Adding the IP address of the service that will act as a server| |Port|Server port| -|Backup server|Making sure to specify that this is a backup server| -|Use the farm’s availability probe|Choosing the probe that was approved during the creation of the farm| -|Encrypting requests with SSL|Encrypting requests with an SSL certificate| -|Cookie|Adding a customized session cookie| -|Certificate chain|Adding a certificate chain| -|Load balancing weight|Choosing the balancing weight for load distribution| +|Backup server|Selecting which server is a backup server| +|Use the server cluster’s probe|Choosing the probe that was validated when you created the cluster| +|Encrypt requests with SSL|Encrypting requests with an SSL certificate| +|Cookie|Add a customised session cookie| +|Certificate chain|Add a certificate chain| +|Balancing weight|Choose the balancing weight for the load balancer| +|PROXY Protocol version|**Only if you have configured it**, choose the version of the PROXY protocol you wish to use on the server.
You can find more information on the PROXY protocol and how to use it with the OVHcloud Load Balancer in [this guide](/pages/network/load_balancer/create_proxyprotocol/).| -### Managing SSL Certificates - -An SSL certificate can be added to the Load Balancer in the `SSL Certificate`{.action} section You will then have two possibilities: either ordering an SSL certificate through OVH or adding an external certificate. +### Managing SSL certificates +You can add an SSL certificate to the Load Balancer in the `SSL Certificate`{.action} section. You have two options: you can order an SSL certificate from OVH, or add an external certificate. #### OVH SSL certificate +To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click `Order an SSL certificate`{.action} and browse the options available: -To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click on `Order an SSL Certificate`{.action} and let us guide you: - -![Ordering an SSL Certificate](images/iplb-order-ssl.png){.thumbnail} +![Ordering an SSL certificate](images/ordering_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Types of certificate|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| -|Fully Qualified Domain Name (FQDN)|Affected domains| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Certificate type|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| +|Fully Qualified Domain Name (FQDN)|Domain(s) concerned| #### Adding an external SSL certificate - If you already have your own SSL certificate, you can add it directly: -![Adding an SSL Certificate](images/iplb-add-ssl.png){.thumbnail} +![Adding an SSL certificate](images/external_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your certificate if you wish; this can be very useful when you have several of them to identify them quickly| -|Private key|Field where a private key can be added to the service| -|Certificate|Certificate field| -|Chain|Field where a root certificate can be added if necessary| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Private key|Field for entering the private key to add to the service| +|Certificate|Field for adding the certificate| +|Chain|Field for adding the root certificate, if required| -## Going further +## Go further -Discuss with our user community at . \ No newline at end of file +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.en-us.md b/pages/network/load_balancer/use-lb/guide.en-us.md index 46a84301581..9604e214d7c 100644 --- a/pages/network/load_balancer/use-lb/guide.en-us.md +++ b/pages/network/load_balancer/use-lb/guide.en-us.md @@ -1,126 +1,124 @@ --- -title: Managing the Load Balancer from the customer control panel -excerpt: Summary of the main features and Load Balancer ownership through the customer control panel -updated: 2017-12-01 +title: Managing your Load Balancer service via the Control Panel +excerpt: An overview of the main features, and how to get started using the Load Balancer service from the Control Panel +updated: 2025-07-04 --- ## Objective -The goal of this guide is to assist you when you first operate your Load Balancer by introducing the solution’s main features. +This guide is designed to help you get started using the Load Balancer, by introducing the main features of the solution. ## Requirements -- Access to your customer control panel -- Owning a [Load Balancer](https://www.ovh.com/world/solutions/load-balancer/) +- You must have access to your OVH Control Panel. +- You must have ordered a [Load Balancer.](https://www.ovh.com/fr/solutions/load-balancer) -## In practice +## Instructions -### Managing your Load Balancer from the customer control panel +### Managing your Load Balancer via the Control Panel To manage your Load Balancer via the Control Panel, go to the `Bare Metal Cloud`{.action} section, click `Network`{.action} and `Load Balancer`{.action}. The main page for the service will then appear: ![Load Balancer](images/lbip-main.png){.thumbnail} -On this home page, you will find the following information: +On this page, you will see the following information: -|Element|Function| +|Element|Purpose| |---|---| -|Status|Summary of your Load Balancer with IP, front-ends, operational farms and added servers| -|Usage|A summary of your LoadBalancer usage| -|Graphs|Here you will find the graphs in relation to your service and based on simultaneous connections or the number of requests per minute| -|Details|Your IPv4 and the Additional IPs attached as well as the number of outbound IPv4 (details available by clicking on the ellipsis)| -|Configuration|This is where you can customize the name of your service (which will appear at the top in the left column) The cipher(s), which are customizable, as well as the data centre where your Load Balancer is located| -|Subscription|You will find below all the administrative details pertaining to your offer| +|Status|An overview of your Load Balancer with the IP, front-ends, functional clusters and servers added| +|Use|A summary of how to use your Load Balancer| +|Graphs|In this section, you will see the graphs linked to service, by concurrent connections or requests per minute| +|Information|Your IPv4 and IPv6 address and the Additional IPs linked to them, as well as the number of outgoing IPv4s (see more details by clicking on the `...`{.action} button)| +|Configuration|Here, you can customise the name of your solution (which will appear at the top of the left-hand column) The cipher(s) are customisable, as well as the availability zones where your Load Balancer is based| +|Subscription|Here, you will see the admin details for your solution| -To add a `front-end`{.action} or some `server farms`{.action}, simply click on their respective buttons. A context menu will then help you to configure each part of your service. +To add `front-ends`{.action} or `Server clusters`{.action}, simply click on their respective buttons. A form will then help you configure each part of your solution. -### Managing your frontends +### Managing front-ends -In order to add front-ends, all you need to do is go to the `Frontends`{.action} section and click on `Add a front-end`{.action}. You will then gain access to the following menu: +To add front-ends, simply go to the `Front-ends`{.action} section, and click `Add a front-end`{.action}. The following menu will then appear: -![Add front-end](images/iplb-add-front-end.png){.thumbnail} +![Add front-end](images/add_frontend.png){.thumbnail} -Details of a front-end component +Details of front-end parts: -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your frontend if you wish; this can be very useful when you have several of them to identify them quickly| +|Name|If you want, you can choose a name for your front-end. This is very useful when you have several front-ends, so you can tell them apart quickly| |Protocol|You can choose between HTTP, HTTPS, TCP, SSL TCP (or TLS) and UDP| -|Port|Choose which listening port to use| -|Data centre|You can choose between your data centre or all of them to create your front-end| -|Default farm|If you have several configured farms, you can choose one by default for each front-end| +|Port|Choose the listening port you wish to use| +|Datacentre|Choose between your availability zone or all availability zones to create your front-end| +|Default cluster|If you have several clusters configured, you can choose one of them as a default for each front-end| -You also have access to advanced settings: +You can also access advanced settings: ![Advanced settings](images/advanced_frontend.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| |Dedicated Additional IP|List of Additional IPs for remote servers| -|Restricting access to some IPs|List that allows restricting remote access to the Load Balancer, only in IPv4| -|HTTP redirection|Adding an HTTP redirect URL| -|HTTP header|Add an HTTP header here| +|Restrict access to IPs|List for restricting remote access to the Load Balancer, for IPv4 only| +|HTTP redirection|Add a HTTP redirection URL| +|HTTP header|Add a HTTP header here| -### Managing your server cluster +### Managing your clusters -In order to add a server cluster, all you need to do is go to the `Server clusters`{.action} section and click on `Add a server cluster`{.action}. You will gain access to the same main features as for the frontend However, advanced options will be different: +To add a server cluster, simply go to the `Server clusters`{.action} section, and click `Add a server cluster`{.action}. You will get the same main options as for the front-end. However, the advanced options are different: -![Adding a farm](images/iplb-cluster-adv.png){.thumbnail} +![Add a cluster](images/advanced_cluster.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Distribution mode|Choice between Round-robin, First, Last, Source or URI for your IP balancing| -|Session tracking|Session tracking can be done through Cookie or IP Source, to be determined here| -|Probe|Probe choice and activation| +|Distribution method|Choosing between Round-robin, First, Last, Source or URI for your IP load balancing| +|Track session|You can track sessions via Cookie or source IP, this can be defined here| +|Probe|Choosing and activating a probe| ### Managing your servers -Once your server farm has been created, you need to add servers to it. Below are the details for advanced options: +Once you have created your server cluster, you just need to add servers to it. Details on these options are below, as well as advanced options: -![Add a server](images/iplb-cluster-add-server.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-1.png){.thumbnail} -![Add a server](images/iplb-cluster-add-server-2.png){.thumbnail} +![Add server](images/add_server.png){.thumbnail} +![Add server](images/add_server_advanced.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your server if you wish; this can be very useful when you have several of them to identify them quickly| -|IPv4 address|Adding the IP of the service that will be used as a server| +|Name|If you want, you can choose a name for your server. This is very useful when you have several servers, so you can tell them apart quickly| +|IPv4 address|Adding the IP address of the service that will act as a server| |Port|Server port| -|Backup server|Making sure to specify that this is a backup server| -|Use the farm’s availability probe|Choosing the probe that was approved during the creation of the farm| -|Encrypting requests with SSL|Encrypting requests with an SSL certificate| -|Cookie|Adding a customized session cookie| -|Certificate chain|Adding a certificate chain| -|Load balancing weight|Choosing the balancing weight for load distribution| +|Backup server|Selecting which server is a backup server| +|Use the server cluster’s probe|Choosing the probe that was validated when you created the cluster| +|Encrypt requests with SSL|Encrypting requests with an SSL certificate| +|Cookie|Add a customised session cookie| +|Certificate chain|Add a certificate chain| +|Balancing weight|Choose the balancing weight for the load balancer| +|PROXY Protocol version|**Only if you have configured it**, choose the version of the PROXY protocol you wish to use on the server.
You can find more information on the PROXY protocol and how to use it with the OVHcloud Load Balancer in [this guide](/pages/network/load_balancer/create_proxyprotocol/).| -### Managing SSL Certificates - -An SSL certificate can be added to the Load Balancer in the `SSL Certificate`{.action} section You will then have two possibilities: either ordering an SSL certificate through OVH or adding an external certificate. +### Managing SSL certificates +You can add an SSL certificate to the Load Balancer in the `SSL Certificate`{.action} section. You have two options: you can order an SSL certificate from OVH, or add an external certificate. #### OVH SSL certificate +To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click `Order an SSL certificate`{.action} and browse the options available: -To order an SSL certificate, simply go to the `SSL Certificate`{.action} section, then click on `Order an SSL Certificate`{.action} and let us guide you: - -![Ordering an SSL Certificate](images/iplb-order-ssl.png){.thumbnail} +![Ordering an SSL certificate](images/ordering_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Types of certificate|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| -|Fully Qualified Domain Name (FQDN)|Affected domains| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Certificate type|Free (Let's Encrypt), Comodo DV or Comodo EV (For more details, [see this page](/links/web/hosting-options-ssl))| +|Fully Qualified Domain Name (FQDN)|Domain(s) concerned| #### Adding an external SSL certificate - If you already have your own SSL certificate, you can add it directly: -![Adding an SSL Certificate](images/iplb-add-ssl.png){.thumbnail} +![Adding an SSL certificate](images/external_ssl.png){.thumbnail} -|Element|Function| +|Element|Purpose| |---|---| -|Name|You can name your certificate if you wish; this can be very useful when you have several of them to identify them quickly| -|Private key|Field where a private key can be added to the service| -|Certificate|Certificate field| -|Chain|Field where a root certificate can be added if necessary| +|Name|If you want, you can choose a name for your certificate. This is very useful when you have several certificates, so you can tell them apart quickly| +|Private key|Field for entering the private key to add to the service| +|Certificate|Field for adding the certificate| +|Chain|Field for adding the root certificate, if required| -## Going further +## Go further -Discuss with our user community at . \ No newline at end of file +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use_api_details/guide.en-asia.md b/pages/network/load_balancer/use_api_details/guide.en-asia.md index 8911c46e25b..07f09c380c5 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-asia.md +++ b/pages/network/load_balancer/use_api_details/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Details of API functions excerpt: Details of API functionalities -updated: 2022-04-04 +updated: 2025-07-04 --- ## Objective @@ -33,12 +33,12 @@ Details of the API functionality for the Load Balancer OVH > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP cluster. > ## Services and zones @@ -123,7 +123,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List existing farms and their type +#### List existing clusters and their type > [!faq] > @@ -184,7 +184,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List the different types of farms that can be used +#### List the different types of clusters that can be used > [!faq] > @@ -414,9 +414,9 @@ The service will be discontinued on the expiry date. ## HTTP Protocol Accessing HTTP protocol related elements (Frontend, Firmware, etc.). -### HTTP farms +### HTTP clusters -#### List HTTP farms attached to a Load Balancer OVH service +#### List HTTP clusters attached to a Load Balancer OVH service > [!faq] > @@ -439,7 +439,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> The name of the zone (String of characters) > -#### Adding a new HTTP farm to a Load Balancer OVH service +#### Adding a new HTTP cluster to a Load Balancer OVH service > [!faq] > @@ -463,23 +463,23 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **balance** >> >> ->> >> Your farm's load distribution method (Value) +>> >> Your cluster's load distribution method (Value) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if undefined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if undefined (Number, 1..65535) >> > >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (Probe HTTP) +>> >> The type of probe to use on your cluster (Probe HTTP) >> >> > >> >> > - **forceSsl** >> >> > @@ -507,7 +507,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > >> >> > - **port** >> >> > ->> >> >> The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> >> The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> > >> >> > - **type** >> >> > @@ -518,7 +518,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> The address to be used by the probe for HTTP type probes. The type is ignored if this parameter is set to (String of characters) > -#### Getting the details of an HTTP farm +#### Getting the details of an HTTP cluster > [!faq] > @@ -538,10 +538,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > -#### Modify the properties of an HTTP farm +#### Modify the properties of an HTTP cluster > [!faq] > @@ -561,13 +561,13 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **BackendHttp** * >> > >> >> - **displayName** >> >> > ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **balance** >> >> > @@ -575,7 +575,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **port** >> >> > ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> > @@ -586,7 +586,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > The type of connection persistence (Value) > -#### Delete an HTTP farm +#### Delete an HTTP cluster > [!faq] > @@ -606,12 +606,12 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > ### HTTP Servers -#### List the servers linked to the HTTP farm +#### List the servers linked to the HTTP cluster > [!faq] > @@ -631,7 +631,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **cookie** >> > @@ -646,7 +646,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> Filter Values by server status (Value) > -#### Adding a server to an HTTP farm +#### Adding a server to an HTTP cluster > [!faq] > @@ -666,7 +666,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -690,7 +690,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -707,14 +707,14 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A server with high weight receives more requests (Number) +>> >> The weight of your server for your cluster. A server with high weight receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to an HTTP farm +#### Get the details of a server linked to an HTTP cluster > [!faq] > @@ -738,7 +738,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of an HTTP server @@ -765,7 +765,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendHttpServer** * >> > @@ -808,10 +808,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **weight** >> >> > ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Removing a server from an HTTP farm +#### Removing a server from an HTTP cluster > [!faq] > @@ -835,7 +835,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends HTTP @@ -860,7 +860,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the HTTP farm to which the HTTP frontend is linked (Number) +>> >> The identifier of the HTTP cluster to which the HTTP frontend is linked (Number) >> > >> > **port** >> > @@ -901,7 +901,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default HTTP farm identifier for your frontend (Number) +>> >> The default HTTP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -933,7 +933,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1019,7 +1019,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **ssl** >> >> > ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete an HTTP frontend @@ -1099,7 +1099,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -1175,7 +1175,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -1389,11 +1389,11 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## Protocol TCP -Access the elements related to the TCP protocol (Frontend, Farm, etc.). +Access the elements related to the TCP protocol (Frontend, cluster, etc.). -### TCP Farms +### TCP clusters -#### List TCP farms attached to a Load Balancer OVH service +#### List TCP clusters attached to a Load Balancer OVH service > [!faq] > @@ -1416,7 +1416,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new TCP farm to a Load Balancer OVH service +#### Add a new TCP cluster to a Load Balancer OVH service > [!faq] > @@ -1436,19 +1436,19 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **balance** >> > ->> >> Your farm's load sharing method (Value) +>> >> Your cluster's load sharing method (Value) >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (HTTP probe) +>> >> The type of probe to use on your cluster (HTTP probe) >> >> >> >> - **forceSsl** >> >> @@ -1476,7 +1476,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **port** >> >> ->> >> > The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> > The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> >> >> - **type** >> >> @@ -1488,14 +1488,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a TCP farm +#### Get the details of a TCP cluster > [!faq] > @@ -1515,10 +1515,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a TCP farm +#### Modify the properties of a TCP cluster > [!faq] > @@ -1538,7 +1538,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcp** * >> > @@ -1548,11 +1548,11 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> @@ -1563,7 +1563,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> > The type of connection persistence (Value) > -#### Delete a TCP farm +#### Delete a TCP cluster > [!faq] > @@ -1583,12 +1583,12 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### TCP Servers -#### List the servers linked to the TCP farm +#### List the servers linked to the TCP cluster > [!faq] > @@ -1608,7 +1608,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **cookie** >> > @@ -1623,7 +1623,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Add a server to a TCP farm +#### Add a server to a TCP cluster > [!faq] > @@ -1643,7 +1643,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -1663,7 +1663,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -1680,14 +1680,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A high weight server receives more requests (Number) +>> >> The weight of your server for your cluster. A high weight server receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a TCP farm +#### Get the details of a server linked to a TCP cluster > [!faq] > @@ -1711,7 +1711,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > > #### Modify the properties of a TCP server @@ -1738,7 +1738,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcpServer** * >> > @@ -1777,10 +1777,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **weight** >> >> ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Delete a server from a TCP farm +#### Delete a server from a TCP cluster > [!faq] > @@ -1804,7 +1804,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends TCP @@ -1829,7 +1829,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the TCP farm to which the TCP frontend is linked (Number) +>> >> The identifier of the TCP cluster to which the TCP frontend is linked (Number) >> > >> > **port** >> > @@ -1868,7 +1868,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default TCP farm identifier for your frontend (Number) +>> >> The default TCP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -1888,7 +1888,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the TCP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the TCP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1964,7 +1964,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **ssl** >> >> ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete a TCP frontend @@ -2040,7 +2040,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -2112,7 +2112,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -2326,9 +2326,9 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## UDP Protocol -Access the UDP protocol elements (Frontend, Farm, etc.). +Access the UDP protocol elements (Frontend, cluster, etc.). -### UDP Farms +### UDP clusters #### List UDP trusses attached to a Load Balancer OVH service @@ -2353,7 +2353,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new UDP farm to a Load Balancer OVH service +#### Add a new UDP cluster to a Load Balancer OVH service > [!faq] > @@ -2373,18 +2373,18 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a UDP farm +#### Get the details of a UDP cluster > [!faq] > @@ -2404,10 +2404,10 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a UDP farm +#### Modify the properties of a UDP cluster > [!faq] > @@ -2427,20 +2427,20 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdp** * >> > >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) > -#### Delete a UDP farm +#### Delete a UDP cluster > [!faq] > @@ -2460,12 +2460,12 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### UDP Servers -#### List the servers linked to the UDP farm +#### List the servers linked to the UDP cluster > [!faq] > @@ -2485,7 +2485,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** >> > @@ -2496,7 +2496,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Adding a server to a UDP farm +#### Adding a server to a UDP cluster > [!faq] > @@ -2516,7 +2516,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -2528,14 +2528,14 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a UDP farm +#### Get the details of a server linked to a UDP cluster > [!faq] > @@ -2559,7 +2559,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of a UDP server @@ -2586,7 +2586,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdpServer** * >> > @@ -2603,7 +2603,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> > If your server is activated or not (Boolean) > -#### Removing a server from a UDP farm +#### Removing a server from a UDP cluster > [!faq] > @@ -2627,7 +2627,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm UDP (Number) +>> >> The identifier of your cluster UDP (Number) > ### Frontends UDP @@ -2652,7 +2652,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the UDP farm to which the UDP frontend is linked (Number) +>> >> The identifier of the UDP cluster to which the UDP frontend is linked (Number) >> > >> > **port** >> > @@ -2687,7 +2687,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** * >> > ->> >> The default UDP farm identifier for your frontend (Number) +>> >> The default UDP cluster identifier for your frontend (Number) >> > >> > **disabled** >> > @@ -3115,7 +3115,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** >> > ->> >> Identification table of farms that you wish to attach to this private network +>> >> Identification table of clusters that you wish to attach to this private network >> > >> > **natIp** >> > @@ -3155,7 +3155,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The identifier of the private network > -#### Modify the list of farms attached to a private network +#### Modify the list of clusters attached to a private network > [!faq] > @@ -3179,7 +3179,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> Table of farm identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all farms where it was configured. +>> >> Table of cluster identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all clusters where it was configured. > ## Go further diff --git a/pages/network/load_balancer/use_api_details/guide.en-au.md b/pages/network/load_balancer/use_api_details/guide.en-au.md index 8911c46e25b..07f09c380c5 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-au.md +++ b/pages/network/load_balancer/use_api_details/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Details of API functions excerpt: Details of API functionalities -updated: 2022-04-04 +updated: 2025-07-04 --- ## Objective @@ -33,12 +33,12 @@ Details of the API functionality for the Load Balancer OVH > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP cluster. > ## Services and zones @@ -123,7 +123,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List existing farms and their type +#### List existing clusters and their type > [!faq] > @@ -184,7 +184,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List the different types of farms that can be used +#### List the different types of clusters that can be used > [!faq] > @@ -414,9 +414,9 @@ The service will be discontinued on the expiry date. ## HTTP Protocol Accessing HTTP protocol related elements (Frontend, Firmware, etc.). -### HTTP farms +### HTTP clusters -#### List HTTP farms attached to a Load Balancer OVH service +#### List HTTP clusters attached to a Load Balancer OVH service > [!faq] > @@ -439,7 +439,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> The name of the zone (String of characters) > -#### Adding a new HTTP farm to a Load Balancer OVH service +#### Adding a new HTTP cluster to a Load Balancer OVH service > [!faq] > @@ -463,23 +463,23 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **balance** >> >> ->> >> Your farm's load distribution method (Value) +>> >> Your cluster's load distribution method (Value) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if undefined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if undefined (Number, 1..65535) >> > >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (Probe HTTP) +>> >> The type of probe to use on your cluster (Probe HTTP) >> >> > >> >> > - **forceSsl** >> >> > @@ -507,7 +507,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > >> >> > - **port** >> >> > ->> >> >> The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> >> The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> > >> >> > - **type** >> >> > @@ -518,7 +518,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> The address to be used by the probe for HTTP type probes. The type is ignored if this parameter is set to (String of characters) > -#### Getting the details of an HTTP farm +#### Getting the details of an HTTP cluster > [!faq] > @@ -538,10 +538,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > -#### Modify the properties of an HTTP farm +#### Modify the properties of an HTTP cluster > [!faq] > @@ -561,13 +561,13 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **BackendHttp** * >> > >> >> - **displayName** >> >> > ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **balance** >> >> > @@ -575,7 +575,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **port** >> >> > ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> > @@ -586,7 +586,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > The type of connection persistence (Value) > -#### Delete an HTTP farm +#### Delete an HTTP cluster > [!faq] > @@ -606,12 +606,12 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > ### HTTP Servers -#### List the servers linked to the HTTP farm +#### List the servers linked to the HTTP cluster > [!faq] > @@ -631,7 +631,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **cookie** >> > @@ -646,7 +646,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> Filter Values by server status (Value) > -#### Adding a server to an HTTP farm +#### Adding a server to an HTTP cluster > [!faq] > @@ -666,7 +666,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -690,7 +690,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -707,14 +707,14 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A server with high weight receives more requests (Number) +>> >> The weight of your server for your cluster. A server with high weight receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to an HTTP farm +#### Get the details of a server linked to an HTTP cluster > [!faq] > @@ -738,7 +738,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of an HTTP server @@ -765,7 +765,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendHttpServer** * >> > @@ -808,10 +808,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **weight** >> >> > ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Removing a server from an HTTP farm +#### Removing a server from an HTTP cluster > [!faq] > @@ -835,7 +835,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends HTTP @@ -860,7 +860,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the HTTP farm to which the HTTP frontend is linked (Number) +>> >> The identifier of the HTTP cluster to which the HTTP frontend is linked (Number) >> > >> > **port** >> > @@ -901,7 +901,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default HTTP farm identifier for your frontend (Number) +>> >> The default HTTP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -933,7 +933,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1019,7 +1019,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **ssl** >> >> > ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete an HTTP frontend @@ -1099,7 +1099,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -1175,7 +1175,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -1389,11 +1389,11 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## Protocol TCP -Access the elements related to the TCP protocol (Frontend, Farm, etc.). +Access the elements related to the TCP protocol (Frontend, cluster, etc.). -### TCP Farms +### TCP clusters -#### List TCP farms attached to a Load Balancer OVH service +#### List TCP clusters attached to a Load Balancer OVH service > [!faq] > @@ -1416,7 +1416,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new TCP farm to a Load Balancer OVH service +#### Add a new TCP cluster to a Load Balancer OVH service > [!faq] > @@ -1436,19 +1436,19 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **balance** >> > ->> >> Your farm's load sharing method (Value) +>> >> Your cluster's load sharing method (Value) >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (HTTP probe) +>> >> The type of probe to use on your cluster (HTTP probe) >> >> >> >> - **forceSsl** >> >> @@ -1476,7 +1476,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **port** >> >> ->> >> > The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> > The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> >> >> - **type** >> >> @@ -1488,14 +1488,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a TCP farm +#### Get the details of a TCP cluster > [!faq] > @@ -1515,10 +1515,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a TCP farm +#### Modify the properties of a TCP cluster > [!faq] > @@ -1538,7 +1538,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcp** * >> > @@ -1548,11 +1548,11 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> @@ -1563,7 +1563,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> > The type of connection persistence (Value) > -#### Delete a TCP farm +#### Delete a TCP cluster > [!faq] > @@ -1583,12 +1583,12 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### TCP Servers -#### List the servers linked to the TCP farm +#### List the servers linked to the TCP cluster > [!faq] > @@ -1608,7 +1608,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **cookie** >> > @@ -1623,7 +1623,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Add a server to a TCP farm +#### Add a server to a TCP cluster > [!faq] > @@ -1643,7 +1643,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -1663,7 +1663,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -1680,14 +1680,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A high weight server receives more requests (Number) +>> >> The weight of your server for your cluster. A high weight server receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a TCP farm +#### Get the details of a server linked to a TCP cluster > [!faq] > @@ -1711,7 +1711,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > > #### Modify the properties of a TCP server @@ -1738,7 +1738,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcpServer** * >> > @@ -1777,10 +1777,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **weight** >> >> ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Delete a server from a TCP farm +#### Delete a server from a TCP cluster > [!faq] > @@ -1804,7 +1804,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends TCP @@ -1829,7 +1829,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the TCP farm to which the TCP frontend is linked (Number) +>> >> The identifier of the TCP cluster to which the TCP frontend is linked (Number) >> > >> > **port** >> > @@ -1868,7 +1868,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default TCP farm identifier for your frontend (Number) +>> >> The default TCP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -1888,7 +1888,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the TCP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the TCP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1964,7 +1964,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **ssl** >> >> ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete a TCP frontend @@ -2040,7 +2040,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -2112,7 +2112,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -2326,9 +2326,9 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## UDP Protocol -Access the UDP protocol elements (Frontend, Farm, etc.). +Access the UDP protocol elements (Frontend, cluster, etc.). -### UDP Farms +### UDP clusters #### List UDP trusses attached to a Load Balancer OVH service @@ -2353,7 +2353,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new UDP farm to a Load Balancer OVH service +#### Add a new UDP cluster to a Load Balancer OVH service > [!faq] > @@ -2373,18 +2373,18 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a UDP farm +#### Get the details of a UDP cluster > [!faq] > @@ -2404,10 +2404,10 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a UDP farm +#### Modify the properties of a UDP cluster > [!faq] > @@ -2427,20 +2427,20 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdp** * >> > >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) > -#### Delete a UDP farm +#### Delete a UDP cluster > [!faq] > @@ -2460,12 +2460,12 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### UDP Servers -#### List the servers linked to the UDP farm +#### List the servers linked to the UDP cluster > [!faq] > @@ -2485,7 +2485,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** >> > @@ -2496,7 +2496,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Adding a server to a UDP farm +#### Adding a server to a UDP cluster > [!faq] > @@ -2516,7 +2516,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -2528,14 +2528,14 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a UDP farm +#### Get the details of a server linked to a UDP cluster > [!faq] > @@ -2559,7 +2559,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of a UDP server @@ -2586,7 +2586,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdpServer** * >> > @@ -2603,7 +2603,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> > If your server is activated or not (Boolean) > -#### Removing a server from a UDP farm +#### Removing a server from a UDP cluster > [!faq] > @@ -2627,7 +2627,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm UDP (Number) +>> >> The identifier of your cluster UDP (Number) > ### Frontends UDP @@ -2652,7 +2652,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the UDP farm to which the UDP frontend is linked (Number) +>> >> The identifier of the UDP cluster to which the UDP frontend is linked (Number) >> > >> > **port** >> > @@ -2687,7 +2687,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** * >> > ->> >> The default UDP farm identifier for your frontend (Number) +>> >> The default UDP cluster identifier for your frontend (Number) >> > >> > **disabled** >> > @@ -3115,7 +3115,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** >> > ->> >> Identification table of farms that you wish to attach to this private network +>> >> Identification table of clusters that you wish to attach to this private network >> > >> > **natIp** >> > @@ -3155,7 +3155,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The identifier of the private network > -#### Modify the list of farms attached to a private network +#### Modify the list of clusters attached to a private network > [!faq] > @@ -3179,7 +3179,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> Table of farm identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all farms where it was configured. +>> >> Table of cluster identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all clusters where it was configured. > ## Go further diff --git a/pages/network/load_balancer/use_api_details/guide.en-ca.md b/pages/network/load_balancer/use_api_details/guide.en-ca.md index 8911c46e25b..07f09c380c5 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-ca.md +++ b/pages/network/load_balancer/use_api_details/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Details of API functions excerpt: Details of API functionalities -updated: 2022-04-04 +updated: 2025-07-04 --- ## Objective @@ -33,12 +33,12 @@ Details of the API functionality for the Load Balancer OVH > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP cluster. > ## Services and zones @@ -123,7 +123,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List existing farms and their type +#### List existing clusters and their type > [!faq] > @@ -184,7 +184,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List the different types of farms that can be used +#### List the different types of clusters that can be used > [!faq] > @@ -414,9 +414,9 @@ The service will be discontinued on the expiry date. ## HTTP Protocol Accessing HTTP protocol related elements (Frontend, Firmware, etc.). -### HTTP farms +### HTTP clusters -#### List HTTP farms attached to a Load Balancer OVH service +#### List HTTP clusters attached to a Load Balancer OVH service > [!faq] > @@ -439,7 +439,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> The name of the zone (String of characters) > -#### Adding a new HTTP farm to a Load Balancer OVH service +#### Adding a new HTTP cluster to a Load Balancer OVH service > [!faq] > @@ -463,23 +463,23 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **balance** >> >> ->> >> Your farm's load distribution method (Value) +>> >> Your cluster's load distribution method (Value) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if undefined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if undefined (Number, 1..65535) >> > >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (Probe HTTP) +>> >> The type of probe to use on your cluster (Probe HTTP) >> >> > >> >> > - **forceSsl** >> >> > @@ -507,7 +507,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > >> >> > - **port** >> >> > ->> >> >> The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> >> The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> > >> >> > - **type** >> >> > @@ -518,7 +518,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> The address to be used by the probe for HTTP type probes. The type is ignored if this parameter is set to (String of characters) > -#### Getting the details of an HTTP farm +#### Getting the details of an HTTP cluster > [!faq] > @@ -538,10 +538,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > -#### Modify the properties of an HTTP farm +#### Modify the properties of an HTTP cluster > [!faq] > @@ -561,13 +561,13 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **BackendHttp** * >> > >> >> - **displayName** >> >> > ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **balance** >> >> > @@ -575,7 +575,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **port** >> >> > ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> > @@ -586,7 +586,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > The type of connection persistence (Value) > -#### Delete an HTTP farm +#### Delete an HTTP cluster > [!faq] > @@ -606,12 +606,12 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > ### HTTP Servers -#### List the servers linked to the HTTP farm +#### List the servers linked to the HTTP cluster > [!faq] > @@ -631,7 +631,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **cookie** >> > @@ -646,7 +646,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> Filter Values by server status (Value) > -#### Adding a server to an HTTP farm +#### Adding a server to an HTTP cluster > [!faq] > @@ -666,7 +666,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -690,7 +690,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -707,14 +707,14 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A server with high weight receives more requests (Number) +>> >> The weight of your server for your cluster. A server with high weight receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to an HTTP farm +#### Get the details of a server linked to an HTTP cluster > [!faq] > @@ -738,7 +738,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of an HTTP server @@ -765,7 +765,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendHttpServer** * >> > @@ -808,10 +808,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **weight** >> >> > ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Removing a server from an HTTP farm +#### Removing a server from an HTTP cluster > [!faq] > @@ -835,7 +835,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends HTTP @@ -860,7 +860,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the HTTP farm to which the HTTP frontend is linked (Number) +>> >> The identifier of the HTTP cluster to which the HTTP frontend is linked (Number) >> > >> > **port** >> > @@ -901,7 +901,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default HTTP farm identifier for your frontend (Number) +>> >> The default HTTP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -933,7 +933,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1019,7 +1019,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **ssl** >> >> > ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete an HTTP frontend @@ -1099,7 +1099,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -1175,7 +1175,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -1389,11 +1389,11 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## Protocol TCP -Access the elements related to the TCP protocol (Frontend, Farm, etc.). +Access the elements related to the TCP protocol (Frontend, cluster, etc.). -### TCP Farms +### TCP clusters -#### List TCP farms attached to a Load Balancer OVH service +#### List TCP clusters attached to a Load Balancer OVH service > [!faq] > @@ -1416,7 +1416,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new TCP farm to a Load Balancer OVH service +#### Add a new TCP cluster to a Load Balancer OVH service > [!faq] > @@ -1436,19 +1436,19 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **balance** >> > ->> >> Your farm's load sharing method (Value) +>> >> Your cluster's load sharing method (Value) >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (HTTP probe) +>> >> The type of probe to use on your cluster (HTTP probe) >> >> >> >> - **forceSsl** >> >> @@ -1476,7 +1476,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **port** >> >> ->> >> > The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> > The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> >> >> - **type** >> >> @@ -1488,14 +1488,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a TCP farm +#### Get the details of a TCP cluster > [!faq] > @@ -1515,10 +1515,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a TCP farm +#### Modify the properties of a TCP cluster > [!faq] > @@ -1538,7 +1538,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcp** * >> > @@ -1548,11 +1548,11 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> @@ -1563,7 +1563,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> > The type of connection persistence (Value) > -#### Delete a TCP farm +#### Delete a TCP cluster > [!faq] > @@ -1583,12 +1583,12 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### TCP Servers -#### List the servers linked to the TCP farm +#### List the servers linked to the TCP cluster > [!faq] > @@ -1608,7 +1608,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **cookie** >> > @@ -1623,7 +1623,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Add a server to a TCP farm +#### Add a server to a TCP cluster > [!faq] > @@ -1643,7 +1643,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -1663,7 +1663,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -1680,14 +1680,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A high weight server receives more requests (Number) +>> >> The weight of your server for your cluster. A high weight server receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a TCP farm +#### Get the details of a server linked to a TCP cluster > [!faq] > @@ -1711,7 +1711,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > > #### Modify the properties of a TCP server @@ -1738,7 +1738,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcpServer** * >> > @@ -1777,10 +1777,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **weight** >> >> ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Delete a server from a TCP farm +#### Delete a server from a TCP cluster > [!faq] > @@ -1804,7 +1804,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends TCP @@ -1829,7 +1829,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the TCP farm to which the TCP frontend is linked (Number) +>> >> The identifier of the TCP cluster to which the TCP frontend is linked (Number) >> > >> > **port** >> > @@ -1868,7 +1868,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default TCP farm identifier for your frontend (Number) +>> >> The default TCP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -1888,7 +1888,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the TCP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the TCP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1964,7 +1964,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **ssl** >> >> ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete a TCP frontend @@ -2040,7 +2040,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -2112,7 +2112,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -2326,9 +2326,9 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## UDP Protocol -Access the UDP protocol elements (Frontend, Farm, etc.). +Access the UDP protocol elements (Frontend, cluster, etc.). -### UDP Farms +### UDP clusters #### List UDP trusses attached to a Load Balancer OVH service @@ -2353,7 +2353,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new UDP farm to a Load Balancer OVH service +#### Add a new UDP cluster to a Load Balancer OVH service > [!faq] > @@ -2373,18 +2373,18 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a UDP farm +#### Get the details of a UDP cluster > [!faq] > @@ -2404,10 +2404,10 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a UDP farm +#### Modify the properties of a UDP cluster > [!faq] > @@ -2427,20 +2427,20 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdp** * >> > >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) > -#### Delete a UDP farm +#### Delete a UDP cluster > [!faq] > @@ -2460,12 +2460,12 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### UDP Servers -#### List the servers linked to the UDP farm +#### List the servers linked to the UDP cluster > [!faq] > @@ -2485,7 +2485,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** >> > @@ -2496,7 +2496,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Adding a server to a UDP farm +#### Adding a server to a UDP cluster > [!faq] > @@ -2516,7 +2516,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -2528,14 +2528,14 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a UDP farm +#### Get the details of a server linked to a UDP cluster > [!faq] > @@ -2559,7 +2559,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of a UDP server @@ -2586,7 +2586,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdpServer** * >> > @@ -2603,7 +2603,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> > If your server is activated or not (Boolean) > -#### Removing a server from a UDP farm +#### Removing a server from a UDP cluster > [!faq] > @@ -2627,7 +2627,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm UDP (Number) +>> >> The identifier of your cluster UDP (Number) > ### Frontends UDP @@ -2652,7 +2652,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the UDP farm to which the UDP frontend is linked (Number) +>> >> The identifier of the UDP cluster to which the UDP frontend is linked (Number) >> > >> > **port** >> > @@ -2687,7 +2687,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** * >> > ->> >> The default UDP farm identifier for your frontend (Number) +>> >> The default UDP cluster identifier for your frontend (Number) >> > >> > **disabled** >> > @@ -3115,7 +3115,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** >> > ->> >> Identification table of farms that you wish to attach to this private network +>> >> Identification table of clusters that you wish to attach to this private network >> > >> > **natIp** >> > @@ -3155,7 +3155,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The identifier of the private network > -#### Modify the list of farms attached to a private network +#### Modify the list of clusters attached to a private network > [!faq] > @@ -3179,7 +3179,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> Table of farm identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all farms where it was configured. +>> >> Table of cluster identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all clusters where it was configured. > ## Go further diff --git a/pages/network/load_balancer/use_api_details/guide.en-gb.md b/pages/network/load_balancer/use_api_details/guide.en-gb.md index 37e0920ab0d..bcf469a2634 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-gb.md +++ b/pages/network/load_balancer/use_api_details/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Details of API functions excerpt: Details of API functionalities -updated: 2022-04-04 +updated: 2025-07-04 --- ## Objective @@ -33,12 +33,12 @@ Details of the API functionality for the Load Balancer OVH > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP cluster. > ## Services and zones @@ -123,7 +123,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List existing farms and their type +#### List existing clusters and their type > [!faq] > @@ -184,7 +184,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List the different types of farms that can be used +#### List the different types of clusters that can be used > [!faq] > @@ -414,9 +414,9 @@ The service will be discontinued on the expiry date. ## HTTP Protocol Accessing HTTP protocol related elements (Frontend, Firmware, etc.). -### HTTP farms +### HTTP clusters -#### List HTTP farms attached to a Load Balancer OVH service +#### List HTTP clusters attached to a Load Balancer OVH service > [!faq] > @@ -439,7 +439,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> The name of the zone (String of characters) > -#### Adding a new HTTP farm to a Load Balancer OVH service +#### Adding a new HTTP cluster to a Load Balancer OVH service > [!faq] > @@ -463,23 +463,23 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **balance** >> >> ->> >> Your farm's load distribution method (Value) +>> >> Your cluster's load distribution method (Value) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if undefined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if undefined (Number, 1..65535) >> > >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (Probe HTTP) +>> >> The type of probe to use on your cluster (Probe HTTP) >> >> > >> >> > - **forceSsl** >> >> > @@ -507,7 +507,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > >> >> > - **port** >> >> > ->> >> >> The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> >> The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> > >> >> > - **type** >> >> > @@ -518,7 +518,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> The address to be used by the probe for HTTP type probes. The type is ignored if this parameter is set to (String of characters) > -#### Getting the details of an HTTP farm +#### Getting the details of an HTTP cluster > [!faq] > @@ -538,10 +538,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > -#### Modify the properties of an HTTP farm +#### Modify the properties of an HTTP cluster > [!faq] > @@ -561,13 +561,13 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **BackendHttp** * >> > >> >> - **displayName** >> >> > ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **balance** >> >> > @@ -575,7 +575,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **port** >> >> > ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> > @@ -586,7 +586,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > The type of connection persistence (Value) > -#### Delete an HTTP farm +#### Delete an HTTP cluster > [!faq] > @@ -606,12 +606,12 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > ### HTTP Servers -#### List the servers linked to the HTTP farm +#### List the servers linked to the HTTP cluster > [!faq] > @@ -631,7 +631,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **cookie** >> > @@ -646,7 +646,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> Filter Values by server status (Value) > -#### Adding a server to an HTTP farm +#### Adding a server to an HTTP cluster > [!faq] > @@ -666,7 +666,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -690,7 +690,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -707,14 +707,14 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A server with high weight receives more requests (Number) +>> >> The weight of your server for your cluster. A server with high weight receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to an HTTP farm +#### Get the details of a server linked to an HTTP cluster > [!faq] > @@ -738,7 +738,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of an HTTP server @@ -765,7 +765,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendHttpServer** * >> > @@ -808,10 +808,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **weight** >> >> > ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Removing a server from an HTTP farm +#### Removing a server from an HTTP cluster > [!faq] > @@ -835,7 +835,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends HTTP @@ -860,7 +860,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the HTTP farm to which the HTTP frontend is linked (Number) +>> >> The identifier of the HTTP cluster to which the HTTP frontend is linked (Number) >> > >> > **port** >> > @@ -901,7 +901,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default HTTP farm identifier for your frontend (Number) +>> >> The default HTTP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -933,7 +933,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1019,7 +1019,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **ssl** >> >> > ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete an HTTP frontend @@ -1099,7 +1099,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -1175,7 +1175,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -1389,11 +1389,11 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## Protocol TCP -Access the elements related to the TCP protocol (Frontend, Farm, etc.). +Access the elements related to the TCP protocol (Frontend, cluster, etc.). -### TCP Farms +### TCP clusters -#### List TCP farms attached to a Load Balancer OVH service +#### List TCP clusters attached to a Load Balancer OVH service > [!faq] > @@ -1416,7 +1416,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new TCP farm to a Load Balancer OVH service +#### Add a new TCP cluster to a Load Balancer OVH service > [!faq] > @@ -1436,19 +1436,19 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **balance** >> > ->> >> Your farm's load sharing method (Value) +>> >> Your cluster's load sharing method (Value) >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (HTTP probe) +>> >> The type of probe to use on your cluster (HTTP probe) >> >> >> >> - **forceSsl** >> >> @@ -1476,7 +1476,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **port** >> >> ->> >> > The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> > The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> >> >> - **type** >> >> @@ -1488,14 +1488,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a TCP farm +#### Get the details of a TCP cluster > [!faq] > @@ -1515,10 +1515,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a TCP farm +#### Modify the properties of a TCP cluster > [!faq] > @@ -1538,7 +1538,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcp** * >> > @@ -1548,11 +1548,11 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> @@ -1563,7 +1563,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> > The type of connection persistence (Value) > -#### Delete a TCP farm +#### Delete a TCP cluster > [!faq] > @@ -1583,12 +1583,12 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### TCP Servers -#### List the servers linked to the TCP farm +#### List the servers linked to the TCP cluster > [!faq] > @@ -1608,7 +1608,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **cookie** >> > @@ -1623,7 +1623,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Add a server to a TCP farm +#### Add a server to a TCP cluster > [!faq] > @@ -1643,7 +1643,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -1663,7 +1663,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -1680,14 +1680,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A high weight server receives more requests (Number) +>> >> The weight of your server for your cluster. A high weight server receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a TCP farm +#### Get the details of a server linked to a TCP cluster > [!faq] > @@ -1711,7 +1711,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > > #### Modify the properties of a TCP server @@ -1738,7 +1738,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcpServer** * >> > @@ -1777,10 +1777,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **weight** >> >> ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Delete a server from a TCP farm +#### Delete a server from a TCP cluster > [!faq] > @@ -1804,7 +1804,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends TCP @@ -1829,7 +1829,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the TCP farm to which the TCP frontend is linked (Number) +>> >> The identifier of the TCP cluster to which the TCP frontend is linked (Number) >> > >> > **port** >> > @@ -1868,7 +1868,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default TCP farm identifier for your frontend (Number) +>> >> The default TCP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -1888,7 +1888,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the TCP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the TCP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1964,7 +1964,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **ssl** >> >> ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete a TCP frontend @@ -2040,7 +2040,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -2112,7 +2112,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -2326,9 +2326,9 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## UDP Protocol -Access the UDP protocol elements (Frontend, Farm, etc.). +Access the UDP protocol elements (Frontend, cluster, etc.). -### UDP Farms +### UDP clusters #### List UDP trusses attached to a Load Balancer OVH service @@ -2353,7 +2353,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new UDP farm to a Load Balancer OVH service +#### Add a new UDP cluster to a Load Balancer OVH service > [!faq] > @@ -2373,18 +2373,18 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a UDP farm +#### Get the details of a UDP cluster > [!faq] > @@ -2404,10 +2404,10 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a UDP farm +#### Modify the properties of a UDP cluster > [!faq] > @@ -2427,20 +2427,20 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdp** * >> > >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) > -#### Delete a UDP farm +#### Delete a UDP cluster > [!faq] > @@ -2460,12 +2460,12 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### UDP Servers -#### List the servers linked to the UDP farm +#### List the servers linked to the UDP cluster > [!faq] > @@ -2485,7 +2485,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** >> > @@ -2496,7 +2496,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Adding a server to a UDP farm +#### Adding a server to a UDP cluster > [!faq] > @@ -2516,7 +2516,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -2528,14 +2528,14 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a UDP farm +#### Get the details of a server linked to a UDP cluster > [!faq] > @@ -2559,7 +2559,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of a UDP server @@ -2586,7 +2586,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdpServer** * >> > @@ -2603,7 +2603,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> > If your server is activated or not (Boolean) > -#### Removing a server from a UDP farm +#### Removing a server from a UDP cluster > [!faq] > @@ -2627,7 +2627,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm UDP (Number) +>> >> The identifier of your cluster UDP (Number) > ### Frontends UDP @@ -2652,7 +2652,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the UDP farm to which the UDP frontend is linked (Number) +>> >> The identifier of the UDP cluster to which the UDP frontend is linked (Number) >> > >> > **port** >> > @@ -2687,7 +2687,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** * >> > ->> >> The default UDP farm identifier for your frontend (Number) +>> >> The default UDP cluster identifier for your frontend (Number) >> > >> > **disabled** >> > @@ -3115,7 +3115,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** >> > ->> >> Identification table of farms that you wish to attach to this private network +>> >> Identification table of clusters that you wish to attach to this private network >> > >> > **natIp** >> > @@ -3155,7 +3155,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The identifier of the private network > -#### Modify the list of farms attached to a private network +#### Modify the list of clusters attached to a private network > [!faq] > @@ -3179,7 +3179,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> Table of farm identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all farms where it was configured. +>> >> Table of cluster identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all clusters where it was configured. > ## Go further diff --git a/pages/network/load_balancer/use_api_details/guide.en-sg.md b/pages/network/load_balancer/use_api_details/guide.en-sg.md index 8911c46e25b..07f09c380c5 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-sg.md +++ b/pages/network/load_balancer/use_api_details/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Details of API functions excerpt: Details of API functionalities -updated: 2022-04-04 +updated: 2025-07-04 --- ## Objective @@ -33,12 +33,12 @@ Details of the API functionality for the Load Balancer OVH > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP cluster. > ## Services and zones @@ -123,7 +123,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List existing farms and their type +#### List existing clusters and their type > [!faq] > @@ -184,7 +184,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List the different types of farms that can be used +#### List the different types of clusters that can be used > [!faq] > @@ -414,9 +414,9 @@ The service will be discontinued on the expiry date. ## HTTP Protocol Accessing HTTP protocol related elements (Frontend, Firmware, etc.). -### HTTP farms +### HTTP clusters -#### List HTTP farms attached to a Load Balancer OVH service +#### List HTTP clusters attached to a Load Balancer OVH service > [!faq] > @@ -439,7 +439,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> The name of the zone (String of characters) > -#### Adding a new HTTP farm to a Load Balancer OVH service +#### Adding a new HTTP cluster to a Load Balancer OVH service > [!faq] > @@ -463,23 +463,23 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **balance** >> >> ->> >> Your farm's load distribution method (Value) +>> >> Your cluster's load distribution method (Value) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if undefined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if undefined (Number, 1..65535) >> > >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (Probe HTTP) +>> >> The type of probe to use on your cluster (Probe HTTP) >> >> > >> >> > - **forceSsl** >> >> > @@ -507,7 +507,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > >> >> > - **port** >> >> > ->> >> >> The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> >> The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> > >> >> > - **type** >> >> > @@ -518,7 +518,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> The address to be used by the probe for HTTP type probes. The type is ignored if this parameter is set to (String of characters) > -#### Getting the details of an HTTP farm +#### Getting the details of an HTTP cluster > [!faq] > @@ -538,10 +538,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > -#### Modify the properties of an HTTP farm +#### Modify the properties of an HTTP cluster > [!faq] > @@ -561,13 +561,13 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **BackendHttp** * >> > >> >> - **displayName** >> >> > ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **balance** >> >> > @@ -575,7 +575,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **port** >> >> > ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> > @@ -586,7 +586,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > The type of connection persistence (Value) > -#### Delete an HTTP farm +#### Delete an HTTP cluster > [!faq] > @@ -606,12 +606,12 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > ### HTTP Servers -#### List the servers linked to the HTTP farm +#### List the servers linked to the HTTP cluster > [!faq] > @@ -631,7 +631,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **cookie** >> > @@ -646,7 +646,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> Filter Values by server status (Value) > -#### Adding a server to an HTTP farm +#### Adding a server to an HTTP cluster > [!faq] > @@ -666,7 +666,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -690,7 +690,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -707,14 +707,14 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A server with high weight receives more requests (Number) +>> >> The weight of your server for your cluster. A server with high weight receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to an HTTP farm +#### Get the details of a server linked to an HTTP cluster > [!faq] > @@ -738,7 +738,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of an HTTP server @@ -765,7 +765,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendHttpServer** * >> > @@ -808,10 +808,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **weight** >> >> > ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Removing a server from an HTTP farm +#### Removing a server from an HTTP cluster > [!faq] > @@ -835,7 +835,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends HTTP @@ -860,7 +860,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the HTTP farm to which the HTTP frontend is linked (Number) +>> >> The identifier of the HTTP cluster to which the HTTP frontend is linked (Number) >> > >> > **port** >> > @@ -901,7 +901,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default HTTP farm identifier for your frontend (Number) +>> >> The default HTTP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -933,7 +933,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1019,7 +1019,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **ssl** >> >> > ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete an HTTP frontend @@ -1099,7 +1099,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -1175,7 +1175,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -1389,11 +1389,11 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## Protocol TCP -Access the elements related to the TCP protocol (Frontend, Farm, etc.). +Access the elements related to the TCP protocol (Frontend, cluster, etc.). -### TCP Farms +### TCP clusters -#### List TCP farms attached to a Load Balancer OVH service +#### List TCP clusters attached to a Load Balancer OVH service > [!faq] > @@ -1416,7 +1416,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new TCP farm to a Load Balancer OVH service +#### Add a new TCP cluster to a Load Balancer OVH service > [!faq] > @@ -1436,19 +1436,19 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **balance** >> > ->> >> Your farm's load sharing method (Value) +>> >> Your cluster's load sharing method (Value) >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (HTTP probe) +>> >> The type of probe to use on your cluster (HTTP probe) >> >> >> >> - **forceSsl** >> >> @@ -1476,7 +1476,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **port** >> >> ->> >> > The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> > The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> >> >> - **type** >> >> @@ -1488,14 +1488,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a TCP farm +#### Get the details of a TCP cluster > [!faq] > @@ -1515,10 +1515,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a TCP farm +#### Modify the properties of a TCP cluster > [!faq] > @@ -1538,7 +1538,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcp** * >> > @@ -1548,11 +1548,11 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> @@ -1563,7 +1563,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> > The type of connection persistence (Value) > -#### Delete a TCP farm +#### Delete a TCP cluster > [!faq] > @@ -1583,12 +1583,12 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### TCP Servers -#### List the servers linked to the TCP farm +#### List the servers linked to the TCP cluster > [!faq] > @@ -1608,7 +1608,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **cookie** >> > @@ -1623,7 +1623,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Add a server to a TCP farm +#### Add a server to a TCP cluster > [!faq] > @@ -1643,7 +1643,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -1663,7 +1663,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -1680,14 +1680,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A high weight server receives more requests (Number) +>> >> The weight of your server for your cluster. A high weight server receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a TCP farm +#### Get the details of a server linked to a TCP cluster > [!faq] > @@ -1711,7 +1711,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > > #### Modify the properties of a TCP server @@ -1738,7 +1738,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcpServer** * >> > @@ -1777,10 +1777,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **weight** >> >> ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Delete a server from a TCP farm +#### Delete a server from a TCP cluster > [!faq] > @@ -1804,7 +1804,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends TCP @@ -1829,7 +1829,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the TCP farm to which the TCP frontend is linked (Number) +>> >> The identifier of the TCP cluster to which the TCP frontend is linked (Number) >> > >> > **port** >> > @@ -1868,7 +1868,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default TCP farm identifier for your frontend (Number) +>> >> The default TCP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -1888,7 +1888,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the TCP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the TCP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1964,7 +1964,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **ssl** >> >> ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete a TCP frontend @@ -2040,7 +2040,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -2112,7 +2112,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -2326,9 +2326,9 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## UDP Protocol -Access the UDP protocol elements (Frontend, Farm, etc.). +Access the UDP protocol elements (Frontend, cluster, etc.). -### UDP Farms +### UDP clusters #### List UDP trusses attached to a Load Balancer OVH service @@ -2353,7 +2353,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new UDP farm to a Load Balancer OVH service +#### Add a new UDP cluster to a Load Balancer OVH service > [!faq] > @@ -2373,18 +2373,18 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a UDP farm +#### Get the details of a UDP cluster > [!faq] > @@ -2404,10 +2404,10 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a UDP farm +#### Modify the properties of a UDP cluster > [!faq] > @@ -2427,20 +2427,20 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdp** * >> > >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) > -#### Delete a UDP farm +#### Delete a UDP cluster > [!faq] > @@ -2460,12 +2460,12 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### UDP Servers -#### List the servers linked to the UDP farm +#### List the servers linked to the UDP cluster > [!faq] > @@ -2485,7 +2485,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** >> > @@ -2496,7 +2496,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Adding a server to a UDP farm +#### Adding a server to a UDP cluster > [!faq] > @@ -2516,7 +2516,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -2528,14 +2528,14 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a UDP farm +#### Get the details of a server linked to a UDP cluster > [!faq] > @@ -2559,7 +2559,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of a UDP server @@ -2586,7 +2586,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdpServer** * >> > @@ -2603,7 +2603,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> > If your server is activated or not (Boolean) > -#### Removing a server from a UDP farm +#### Removing a server from a UDP cluster > [!faq] > @@ -2627,7 +2627,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm UDP (Number) +>> >> The identifier of your cluster UDP (Number) > ### Frontends UDP @@ -2652,7 +2652,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the UDP farm to which the UDP frontend is linked (Number) +>> >> The identifier of the UDP cluster to which the UDP frontend is linked (Number) >> > >> > **port** >> > @@ -2687,7 +2687,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** * >> > ->> >> The default UDP farm identifier for your frontend (Number) +>> >> The default UDP cluster identifier for your frontend (Number) >> > >> > **disabled** >> > @@ -3115,7 +3115,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** >> > ->> >> Identification table of farms that you wish to attach to this private network +>> >> Identification table of clusters that you wish to attach to this private network >> > >> > **natIp** >> > @@ -3155,7 +3155,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The identifier of the private network > -#### Modify the list of farms attached to a private network +#### Modify the list of clusters attached to a private network > [!faq] > @@ -3179,7 +3179,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> Table of farm identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all farms where it was configured. +>> >> Table of cluster identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all clusters where it was configured. > ## Go further diff --git a/pages/network/load_balancer/use_api_details/guide.en-us.md b/pages/network/load_balancer/use_api_details/guide.en-us.md index 8911c46e25b..07f09c380c5 100644 --- a/pages/network/load_balancer/use_api_details/guide.en-us.md +++ b/pages/network/load_balancer/use_api_details/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Details of API functions excerpt: Details of API functionalities -updated: 2022-04-04 +updated: 2025-07-04 --- ## Objective @@ -33,12 +33,12 @@ Details of the API functionality for the Load Balancer OVH > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP cluster. > ## Services and zones @@ -123,7 +123,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List existing farms and their type +#### List existing clusters and their type > [!faq] > @@ -184,7 +184,7 @@ Details of the API functionality for the Load Balancer OVH >> >> The identifier of your Load Balancer, ex: IP-1.2.3.4 (String of characters) > -#### List the different types of farms that can be used +#### List the different types of clusters that can be used > [!faq] > @@ -414,9 +414,9 @@ The service will be discontinued on the expiry date. ## HTTP Protocol Accessing HTTP protocol related elements (Frontend, Firmware, etc.). -### HTTP farms +### HTTP clusters -#### List HTTP farms attached to a Load Balancer OVH service +#### List HTTP clusters attached to a Load Balancer OVH service > [!faq] > @@ -439,7 +439,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> The name of the zone (String of characters) > -#### Adding a new HTTP farm to a Load Balancer OVH service +#### Adding a new HTTP cluster to a Load Balancer OVH service > [!faq] > @@ -463,23 +463,23 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **balance** >> >> ->> >> Your farm's load distribution method (Value) +>> >> Your cluster's load distribution method (Value) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if undefined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if undefined (Number, 1..65535) >> > >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (Probe HTTP) +>> >> The type of probe to use on your cluster (Probe HTTP) >> >> > >> >> > - **forceSsl** >> >> > @@ -507,7 +507,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > >> >> > - **port** >> >> > ->> >> >> The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> >> The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> > >> >> > - **type** >> >> > @@ -518,7 +518,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> The address to be used by the probe for HTTP type probes. The type is ignored if this parameter is set to (String of characters) > -#### Getting the details of an HTTP farm +#### Getting the details of an HTTP cluster > [!faq] > @@ -538,10 +538,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > -#### Modify the properties of an HTTP farm +#### Modify the properties of an HTTP cluster > [!faq] > @@ -561,13 +561,13 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **BackendHttp** * >> > >> >> - **displayName** >> >> > ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **balance** >> >> > @@ -575,7 +575,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **port** >> >> > ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> > @@ -586,7 +586,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> > The type of connection persistence (Value) > -#### Delete an HTTP farm +#### Delete an HTTP cluster > [!faq] > @@ -606,12 +606,12 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) > ### HTTP Servers -#### List the servers linked to the HTTP farm +#### List the servers linked to the HTTP cluster > [!faq] > @@ -631,7 +631,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your HTTP farm (Number) +>> >> The identifier of your HTTP cluster (Number) >> > >> > **cookie** >> > @@ -646,7 +646,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> Filter Values by server status (Value) > -#### Adding a server to an HTTP farm +#### Adding a server to an HTTP cluster > [!faq] > @@ -666,7 +666,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -690,7 +690,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -707,14 +707,14 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A server with high weight receives more requests (Number) +>> >> The weight of your server for your cluster. A server with high weight receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to an HTTP farm +#### Get the details of a server linked to an HTTP cluster > [!faq] > @@ -738,7 +738,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of an HTTP server @@ -765,7 +765,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendHttpServer** * >> > @@ -808,10 +808,10 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **weight** >> >> > ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Removing a server from an HTTP farm +#### Removing a server from an HTTP cluster > [!faq] > @@ -835,7 +835,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends HTTP @@ -860,7 +860,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the HTTP farm to which the HTTP frontend is linked (Number) +>> >> The identifier of the HTTP cluster to which the HTTP frontend is linked (Number) >> > >> > **port** >> > @@ -901,7 +901,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default HTTP farm identifier for your frontend (Number) +>> >> The default HTTP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -933,7 +933,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1019,7 +1019,7 @@ Accessing HTTP protocol related elements (Frontend, Firmware, etc.). >> >> >> >> - **ssl** >> >> > ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete an HTTP frontend @@ -1099,7 +1099,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -1175,7 +1175,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -1389,11 +1389,11 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## Protocol TCP -Access the elements related to the TCP protocol (Frontend, Farm, etc.). +Access the elements related to the TCP protocol (Frontend, cluster, etc.). -### TCP Farms +### TCP clusters -#### List TCP farms attached to a Load Balancer OVH service +#### List TCP clusters attached to a Load Balancer OVH service > [!faq] > @@ -1416,7 +1416,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new TCP farm to a Load Balancer OVH service +#### Add a new TCP cluster to a Load Balancer OVH service > [!faq] > @@ -1436,19 +1436,19 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **balance** >> > ->> >> Your farm's load sharing method (Value) +>> >> Your cluster's load sharing method (Value) >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **probe** >> > ->> >> The type of probe to use on your farm (HTTP probe) +>> >> The type of probe to use on your cluster (HTTP probe) >> >> >> >> - **forceSsl** >> >> @@ -1476,7 +1476,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **port** >> >> ->> >> > The port that the probe should use to test the servers attached to your farm. Ignored for 'oco' probes. If not defined, the farm port is used (Number) +>> >> > The port that the probe should use to test the servers attached to your cluster. Ignored for 'oco' probes. If not defined, the cluster port is used (Number) >> >> >> >> - **type** >> >> @@ -1488,14 +1488,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> > **stickiness** >> > ->> >> The type of connection persistence to use for your farm (Value) +>> >> The type of connection persistence to use for your cluster (Value) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a TCP farm +#### Get the details of a TCP cluster > [!faq] > @@ -1515,10 +1515,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a TCP farm +#### Modify the properties of a TCP cluster > [!faq] > @@ -1538,7 +1538,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcp** * >> > @@ -1548,11 +1548,11 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) >> >> >> >> - **probe** >> >> @@ -1563,7 +1563,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> > The type of connection persistence (Value) > -#### Delete a TCP farm +#### Delete a TCP cluster > [!faq] > @@ -1583,12 +1583,12 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### TCP Servers -#### List the servers linked to the TCP farm +#### List the servers linked to the TCP cluster > [!faq] > @@ -1608,7 +1608,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **cookie** >> > @@ -1623,7 +1623,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Add a server to a TCP farm +#### Add a server to a TCP cluster > [!faq] > @@ -1643,7 +1643,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -1663,7 +1663,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **probe** >> > @@ -1680,14 +1680,14 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **weight** * >> > ->> >> The weight of your server for your farm. A high weight server receives more requests (Number) +>> >> The weight of your server for your cluster. A high weight server receives more requests (Number) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a TCP farm +#### Get the details of a server linked to a TCP cluster > [!faq] > @@ -1711,7 +1711,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > > #### Modify the properties of a TCP server @@ -1738,7 +1738,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendTcpServer** * >> > @@ -1777,10 +1777,10 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **weight** >> >> ->> >> > The weight of your server for your farm (Number) +>> >> > The weight of your server for your cluster (Number) > -#### Delete a server from a TCP farm +#### Delete a server from a TCP cluster > [!faq] > @@ -1804,7 +1804,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### Frontends TCP @@ -1829,7 +1829,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the TCP farm to which the TCP frontend is linked (Number) +>> >> The identifier of the TCP cluster to which the TCP frontend is linked (Number) >> > >> > **port** >> > @@ -1868,7 +1868,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The default TCP farm identifier for your frontend (Number) +>> >> The default TCP cluster identifier for your frontend (Number) >> > >> > **defaultSslId** >> > @@ -1888,7 +1888,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> > >> > **ssl** >> > ->> >> Whether requests sent to the TCP farm should be encrypted with SSL or not (Boolean) +>> >> Whether requests sent to the TCP cluster should be encrypted with SSL or not (Boolean) >> > >> > **zone** * >> > @@ -1964,7 +1964,7 @@ Access the elements related to the TCP protocol (Frontend, Farm, etc.). >> >> >> >> - **ssl** >> >> ->> >> > Whether requests sent to the HTTP farm should be encrypted with SSL or not (Boolean) +>> >> > Whether requests sent to the HTTP cluster should be encrypted with SSL or not (Boolean) > #### Delete a TCP frontend @@ -2040,7 +2040,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> >> >> - **target** >> >> ->> >> > The farm identifier, or the template for the URL (String of characters) +>> >> > The cluster identifier, or the template for the URL (String of characters) >> >> >> >> - **type** >> >> @@ -2112,7 +2112,7 @@ Routes are evaluated one by one, testing their routing rules. The first route va >> >> > >> >> > - **target** >> >> > ->> >> >> The farm identifier, or the template for the URL (String of characters) +>> >> >> The cluster identifier, or the template for the URL (String of characters) >> >> > >> >> > - **type** >> >> > @@ -2326,9 +2326,9 @@ Routes are evaluated one by one, testing their routing rules. The first route va > ## UDP Protocol -Access the UDP protocol elements (Frontend, Farm, etc.). +Access the UDP protocol elements (Frontend, cluster, etc.). -### UDP Farms +### UDP clusters #### List UDP trusses attached to a Load Balancer OVH service @@ -2353,7 +2353,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The name of your zone, ex: all (String of characters) > -#### Add a new UDP farm to a Load Balancer OVH service +#### Add a new UDP cluster to a Load Balancer OVH service > [!faq] > @@ -2373,18 +2373,18 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **displayName** >> > ->> >> The name you wish to give to your farm (String of characters) +>> >> The name you wish to give to your cluster (String of characters) >> > >> > **port** >> > ->> >> The listening port on your farm. Inherited from the frontend if not defined (Number, 1..65535) +>> >> The listening port on your cluster. Inherited from the frontend if not defined (Number, 1..65535) >> > >> > **zone** * >> > >> >> The name of your zone, ex: all (String of characters) > -#### Get the details of a UDP farm +#### Get the details of a UDP cluster > [!faq] > @@ -2404,10 +2404,10 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > -#### Modify the properties of a UDP farm +#### Modify the properties of a UDP cluster > [!faq] > @@ -2427,20 +2427,20 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdp** * >> > >> >> - **displayName** >> >> ->> >> > The name of the farm (String of characters) +>> >> > The name of the cluster (String of characters) >> >> >> >> - **port** >> >> ->> >> > The farm's listening port (Number, 1..65000) +>> >> > The cluster's listening port (Number, 1..65000) > -#### Delete a UDP farm +#### Delete a UDP cluster > [!faq] > @@ -2460,12 +2460,12 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > ### UDP Servers -#### List the servers linked to the UDP farm +#### List the servers linked to the UDP cluster > [!faq] > @@ -2485,7 +2485,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** >> > @@ -2496,7 +2496,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> Filter Values by Server Status (Value) > -#### Adding a server to a UDP farm +#### Adding a server to a UDP cluster > [!faq] > @@ -2516,7 +2516,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **address** * >> > @@ -2528,14 +2528,14 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **port** >> > ->> >> The listening port of your server. Inherited from your farm if not defined (Number, 1..65535) +>> >> The listening port of your server. Inherited from your cluster if not defined (Number, 1..65535) >> > >> > **status** * >> > >> >> If your server is activated or not (Boolean) > -#### Get the details of a server linked to a UDP farm +#### Get the details of a server linked to a UDP cluster > [!faq] > @@ -2559,7 +2559,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) > #### Modify the properties of a UDP server @@ -2586,7 +2586,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm (Number) +>> >> The identifier of your cluster (Number) >> > >> > **BackendUdpServer** * >> > @@ -2603,7 +2603,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> > If your server is activated or not (Boolean) > -#### Removing a server from a UDP farm +#### Removing a server from a UDP cluster > [!faq] > @@ -2627,7 +2627,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> The identifier of your farm UDP (Number) +>> >> The identifier of your cluster UDP (Number) > ### Frontends UDP @@ -2652,7 +2652,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** >> > ->> >> The identifier of the UDP farm to which the UDP frontend is linked (Number) +>> >> The identifier of the UDP cluster to which the UDP frontend is linked (Number) >> > >> > **port** >> > @@ -2687,7 +2687,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **defaultFarmId** * >> > ->> >> The default UDP farm identifier for your frontend (Number) +>> >> The default UDP cluster identifier for your frontend (Number) >> > >> > **disabled** >> > @@ -3115,7 +3115,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** >> > ->> >> Identification table of farms that you wish to attach to this private network +>> >> Identification table of clusters that you wish to attach to this private network >> > >> > **natIp** >> > @@ -3155,7 +3155,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> >> The identifier of the private network > -#### Modify the list of farms attached to a private network +#### Modify the list of clusters attached to a private network > [!faq] > @@ -3179,7 +3179,7 @@ Access the UDP protocol elements (Frontend, Farm, etc.). >> > >> > **farmId** * >> > ->> >> Table of farm identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all farms where it was configured. +>> >> Table of cluster identifiers that you wish to attach to this private network. The Value "null" removes the vrack network id from all clusters where it was configured. > ## Go further diff --git a/pages/network/load_balancer/use_api_reference/guide.en-asia.md b/pages/network/load_balancer/use_api_reference/guide.en-asia.md index daec23af197..d04fc58f657 100644 --- a/pages/network/load_balancer/use_api_reference/guide.en-asia.md +++ b/pages/network/load_balancer/use_api_reference/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Load Balancer API Quick Reference excerpt: Quick description of the different API functions used to manage the Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## List of API functions @@ -16,12 +16,12 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, Cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within the same protocol. > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP Cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP Cluster. > ## Frontend @@ -77,7 +77,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/udp/frontend/{frontendId} > -## Server farm +## Server cluster > [!primary] > @@ -85,7 +85,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > It is necessary to execute the API function that corresponds to the type of service desired. > -### Return the list of IDs of existing farms +### Return the list of IDs of existing clusters > [!api] > @@ -94,7 +94,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm > -### Create a Farm +### Create a cluster > [!api] > @@ -103,7 +103,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/udp/farm > -### Return the parameters applied to a farm +### Return the parameters applied to a cluster > [!api] > @@ -112,7 +112,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Edit parameters related to a particular farm +### Edit parameters related to a particular cluster > [!api] > @@ -121,7 +121,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Delete a Farm +### Delete a cluster > [!api] > @@ -134,11 +134,11 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> As for the frontend and farm, each category is composed of 3 API functions. +> As for the frontend and cluster, each category is composed of 3 API functions. > It is necessary to properly execute the API function that corresponds to the type of the desired service. > -### Return the list of server IDs linked to a particular farm +### Return the list of server IDs linked to a particular cluster > [!api] > @@ -147,7 +147,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId}/server > -### Creates a server for a particular farm +### Creates a server for a particular cluster > [!api] > diff --git a/pages/network/load_balancer/use_api_reference/guide.en-au.md b/pages/network/load_balancer/use_api_reference/guide.en-au.md index daec23af197..d04fc58f657 100644 --- a/pages/network/load_balancer/use_api_reference/guide.en-au.md +++ b/pages/network/load_balancer/use_api_reference/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Load Balancer API Quick Reference excerpt: Quick description of the different API functions used to manage the Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## List of API functions @@ -16,12 +16,12 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, Cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within the same protocol. > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP Cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP Cluster. > ## Frontend @@ -77,7 +77,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/udp/frontend/{frontendId} > -## Server farm +## Server cluster > [!primary] > @@ -85,7 +85,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > It is necessary to execute the API function that corresponds to the type of service desired. > -### Return the list of IDs of existing farms +### Return the list of IDs of existing clusters > [!api] > @@ -94,7 +94,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm > -### Create a Farm +### Create a cluster > [!api] > @@ -103,7 +103,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/udp/farm > -### Return the parameters applied to a farm +### Return the parameters applied to a cluster > [!api] > @@ -112,7 +112,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Edit parameters related to a particular farm +### Edit parameters related to a particular cluster > [!api] > @@ -121,7 +121,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Delete a Farm +### Delete a cluster > [!api] > @@ -134,11 +134,11 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> As for the frontend and farm, each category is composed of 3 API functions. +> As for the frontend and cluster, each category is composed of 3 API functions. > It is necessary to properly execute the API function that corresponds to the type of the desired service. > -### Return the list of server IDs linked to a particular farm +### Return the list of server IDs linked to a particular cluster > [!api] > @@ -147,7 +147,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId}/server > -### Creates a server for a particular farm +### Creates a server for a particular cluster > [!api] > diff --git a/pages/network/load_balancer/use_api_reference/guide.en-ca.md b/pages/network/load_balancer/use_api_reference/guide.en-ca.md index 359ae47ca4f..c767387c6e7 100644 --- a/pages/network/load_balancer/use_api_reference/guide.en-ca.md +++ b/pages/network/load_balancer/use_api_reference/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Load Balancer API Quick Reference excerpt: Quick description of the different API functions used to manage the Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## List of API functions @@ -16,12 +16,12 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, Cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within the same protocol. > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP Cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP Cluster. > ## Frontend @@ -77,7 +77,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/udp/frontend/{frontendId} > -## Server farm +## Server cluster > [!primary] > @@ -85,7 +85,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > It is necessary to execute the API function that corresponds to the type of service desired. > -### Return the list of IDs of existing farms +### Return the list of IDs of existing clusters > [!api] > @@ -94,7 +94,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm > -### Create a Farm +### Create a cluster > [!api] > @@ -103,7 +103,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/udp/farm > -### Return the parameters applied to a farm +### Return the parameters applied to a cluster > [!api] > @@ -112,7 +112,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Edit parameters related to a particular farm +### Edit parameters related to a particular cluster > [!api] > @@ -121,7 +121,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Delete a Farm +### Delete a cluster > [!api] > @@ -134,11 +134,11 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> As for the frontend and farm, each category is composed of 3 API functions. +> As for the frontend and cluster, each category is composed of 3 API functions. > It is necessary to properly execute the API function that corresponds to the type of the desired service. > -### Return the list of server IDs linked to a particular farm +### Return the list of server IDs linked to a particular cluster > [!api] > @@ -147,7 +147,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId}/server > -### Creates a server for a particular farm +### Creates a server for a particular cluster > [!api] > diff --git a/pages/network/load_balancer/use_api_reference/guide.en-gb.md b/pages/network/load_balancer/use_api_reference/guide.en-gb.md index 359ae47ca4f..c767387c6e7 100644 --- a/pages/network/load_balancer/use_api_reference/guide.en-gb.md +++ b/pages/network/load_balancer/use_api_reference/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Load Balancer API Quick Reference excerpt: Quick description of the different API functions used to manage the Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## List of API functions @@ -16,12 +16,12 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, Cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within the same protocol. > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP Cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP Cluster. > ## Frontend @@ -77,7 +77,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/udp/frontend/{frontendId} > -## Server farm +## Server cluster > [!primary] > @@ -85,7 +85,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > It is necessary to execute the API function that corresponds to the type of service desired. > -### Return the list of IDs of existing farms +### Return the list of IDs of existing clusters > [!api] > @@ -94,7 +94,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm > -### Create a Farm +### Create a cluster > [!api] > @@ -103,7 +103,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/udp/farm > -### Return the parameters applied to a farm +### Return the parameters applied to a cluster > [!api] > @@ -112,7 +112,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Edit parameters related to a particular farm +### Edit parameters related to a particular cluster > [!api] > @@ -121,7 +121,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Delete a Farm +### Delete a cluster > [!api] > @@ -134,11 +134,11 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> As for the frontend and farm, each category is composed of 3 API functions. +> As for the frontend and cluster, each category is composed of 3 API functions. > It is necessary to properly execute the API function that corresponds to the type of the desired service. > -### Return the list of server IDs linked to a particular farm +### Return the list of server IDs linked to a particular cluster > [!api] > @@ -147,7 +147,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId}/server > -### Creates a server for a particular farm +### Creates a server for a particular cluster > [!api] > diff --git a/pages/network/load_balancer/use_api_reference/guide.en-sg.md b/pages/network/load_balancer/use_api_reference/guide.en-sg.md index 359ae47ca4f..c767387c6e7 100644 --- a/pages/network/load_balancer/use_api_reference/guide.en-sg.md +++ b/pages/network/load_balancer/use_api_reference/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Load Balancer API Quick Reference excerpt: Quick description of the different API functions used to manage the Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## List of API functions @@ -16,12 +16,12 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, Cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within the same protocol. > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP Cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP Cluster. > ## Frontend @@ -77,7 +77,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/udp/frontend/{frontendId} > -## Server farm +## Server cluster > [!primary] > @@ -85,7 +85,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > It is necessary to execute the API function that corresponds to the type of service desired. > -### Return the list of IDs of existing farms +### Return the list of IDs of existing clusters > [!api] > @@ -94,7 +94,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm > -### Create a Farm +### Create a cluster > [!api] > @@ -103,7 +103,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/udp/farm > -### Return the parameters applied to a farm +### Return the parameters applied to a cluster > [!api] > @@ -112,7 +112,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Edit parameters related to a particular farm +### Edit parameters related to a particular cluster > [!api] > @@ -121,7 +121,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Delete a Farm +### Delete a cluster > [!api] > @@ -134,11 +134,11 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> As for the frontend and farm, each category is composed of 3 API functions. +> As for the frontend and cluster, each category is composed of 3 API functions. > It is necessary to properly execute the API function that corresponds to the type of the desired service. > -### Return the list of server IDs linked to a particular farm +### Return the list of server IDs linked to a particular cluster > [!api] > @@ -147,7 +147,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId}/server > -### Creates a server for a particular farm +### Creates a server for a particular cluster > [!api] > diff --git a/pages/network/load_balancer/use_api_reference/guide.en-us.md b/pages/network/load_balancer/use_api_reference/guide.en-us.md index 359ae47ca4f..c767387c6e7 100644 --- a/pages/network/load_balancer/use_api_reference/guide.en-us.md +++ b/pages/network/load_balancer/use_api_reference/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Load Balancer API Quick Reference excerpt: Quick description of the different API functions used to manage the Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## List of API functions @@ -16,12 +16,12 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> The Frontend, Farm and Server are specific to the +> The Frontend, Cluster and Server are specific to the > protocol (among HTTP, TCP or UDP) in which they are defined. > Although they can be "combined" with each other, this is only possible within the same protocol. > of the same protocol. Thus, it is not possible to use a Frontend -> UDP with an HTTP Farm. But it is possible (in the absence of other -> limitation) to use an HTTP Frontend with an HTTP Farm. +> UDP with an HTTP Cluster. But it is possible (in the absence of other +> limitation) to use an HTTP Frontend with an HTTP Cluster. > ## Frontend @@ -77,7 +77,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/udp/frontend/{frontendId} > -## Server farm +## Server cluster > [!primary] > @@ -85,7 +85,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > It is necessary to execute the API function that corresponds to the type of service desired. > -### Return the list of IDs of existing farms +### Return the list of IDs of existing clusters > [!api] > @@ -94,7 +94,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm > -### Create a Farm +### Create a cluster > [!api] > @@ -103,7 +103,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/udp/farm > -### Return the parameters applied to a farm +### Return the parameters applied to a cluster > [!api] > @@ -112,7 +112,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Edit parameters related to a particular farm +### Edit parameters related to a particular cluster > [!api] > @@ -121,7 +121,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/udp/farm/{farmId} > -### Delete a Farm +### Delete a cluster > [!api] > @@ -134,11 +134,11 @@ For a complete reference to the API functions of the OVH Load Balancer service, > [!primary] > -> As for the frontend and farm, each category is composed of 3 API functions. +> As for the frontend and cluster, each category is composed of 3 API functions. > It is necessary to properly execute the API function that corresponds to the type of the desired service. > -### Return the list of server IDs linked to a particular farm +### Return the list of server IDs linked to a particular cluster > [!api] > @@ -147,7 +147,7 @@ For a complete reference to the API functions of the OVH Load Balancer service, > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/udp/farm/{farmId}/server > -### Creates a server for a particular farm +### Creates a server for a particular cluster > [!api] > diff --git a/pages/network/load_balancer/use_presentation/guide.en-asia.md b/pages/network/load_balancer/use_presentation/guide.en-asia.md index c32478369ab..8a8f72d2ad5 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-asia.md +++ b/pages/network/load_balancer/use_presentation/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Introduction to the OVHcloud Load Balancer excerpt: Find out more about the OVHcloud Load Balancer solution -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -44,7 +44,7 @@ With this new solution, you will get: |Basic parts|Function| |---|---| |Front-end|The front-end defines the protocol type (HTTP/TCP/UDP) of the OVHcloud Load Balancer service. This part also has the service’s listening port| -|Farm|The farm receives the incoming traffic from the front-end. This part takes care of the load balancing| +|Cluster|The cluster receives the incoming traffic from the front-end. This part takes care of the load balancing| |Server|These are the servers that receive the final traffic, and respond via the application| With these three basic parts that make up the Load Balancer, you can configure it to use nearly all possible load balancing methods. @@ -65,13 +65,13 @@ The OVHcloud Load Balancer service can automatically detect when a server is not #### Scale your infrastructure easily -You can add or remove farms, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. +You can add or remove clusters, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. ![Scale your infrastructure easily](images/facilitate_maintenance.png){.thumbnail} #### Make maintenance easier -If there is any maintenance scheduled for your solution, you can now easily place a farm in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. +If there is any maintenance scheduled for your solution, you can now easily place a cluster in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. ![Make maintenance easier](images/scale_easily.png){.thumbnail} diff --git a/pages/network/load_balancer/use_presentation/guide.en-au.md b/pages/network/load_balancer/use_presentation/guide.en-au.md index c32478369ab..8a8f72d2ad5 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-au.md +++ b/pages/network/load_balancer/use_presentation/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Introduction to the OVHcloud Load Balancer excerpt: Find out more about the OVHcloud Load Balancer solution -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -44,7 +44,7 @@ With this new solution, you will get: |Basic parts|Function| |---|---| |Front-end|The front-end defines the protocol type (HTTP/TCP/UDP) of the OVHcloud Load Balancer service. This part also has the service’s listening port| -|Farm|The farm receives the incoming traffic from the front-end. This part takes care of the load balancing| +|Cluster|The cluster receives the incoming traffic from the front-end. This part takes care of the load balancing| |Server|These are the servers that receive the final traffic, and respond via the application| With these three basic parts that make up the Load Balancer, you can configure it to use nearly all possible load balancing methods. @@ -65,13 +65,13 @@ The OVHcloud Load Balancer service can automatically detect when a server is not #### Scale your infrastructure easily -You can add or remove farms, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. +You can add or remove clusters, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. ![Scale your infrastructure easily](images/facilitate_maintenance.png){.thumbnail} #### Make maintenance easier -If there is any maintenance scheduled for your solution, you can now easily place a farm in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. +If there is any maintenance scheduled for your solution, you can now easily place a cluster in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. ![Make maintenance easier](images/scale_easily.png){.thumbnail} diff --git a/pages/network/load_balancer/use_presentation/guide.en-ca.md b/pages/network/load_balancer/use_presentation/guide.en-ca.md index c32478369ab..8a8f72d2ad5 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-ca.md +++ b/pages/network/load_balancer/use_presentation/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Introduction to the OVHcloud Load Balancer excerpt: Find out more about the OVHcloud Load Balancer solution -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -44,7 +44,7 @@ With this new solution, you will get: |Basic parts|Function| |---|---| |Front-end|The front-end defines the protocol type (HTTP/TCP/UDP) of the OVHcloud Load Balancer service. This part also has the service’s listening port| -|Farm|The farm receives the incoming traffic from the front-end. This part takes care of the load balancing| +|Cluster|The cluster receives the incoming traffic from the front-end. This part takes care of the load balancing| |Server|These are the servers that receive the final traffic, and respond via the application| With these three basic parts that make up the Load Balancer, you can configure it to use nearly all possible load balancing methods. @@ -65,13 +65,13 @@ The OVHcloud Load Balancer service can automatically detect when a server is not #### Scale your infrastructure easily -You can add or remove farms, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. +You can add or remove clusters, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. ![Scale your infrastructure easily](images/facilitate_maintenance.png){.thumbnail} #### Make maintenance easier -If there is any maintenance scheduled for your solution, you can now easily place a farm in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. +If there is any maintenance scheduled for your solution, you can now easily place a cluster in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. ![Make maintenance easier](images/scale_easily.png){.thumbnail} diff --git a/pages/network/load_balancer/use_presentation/guide.en-gb.md b/pages/network/load_balancer/use_presentation/guide.en-gb.md index ef828456e58..498df3dcae2 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-gb.md +++ b/pages/network/load_balancer/use_presentation/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Introduction to the OVH Load Balancer excerpt: Find out more about the OVH Load Balancer solution -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -44,7 +44,7 @@ With this new solution, you will get: |Basic parts|Function| |---|---| |Front-end|The front-end defines the protocol type (HTTP/TCP/UDP) of the OVH Load Balancer service. This part also has the service’s listening port| -|Farm|The farm receives the incoming traffic from the front-end. This part takes care of the load balancing| +|Cluster|The cluster receives the incoming traffic from the front-end. This part takes care of the load balancing| |Server|These are the servers that receive the final traffic, and respond via the application| With these three basic parts that make up the Load Balancer, you can configure it to use nearly all possible load balancing methods. @@ -65,13 +65,13 @@ The OVH Load Balancer service can automatically detect when a server is not resp #### Scale your infrastructure easily -You can add or remove farms, front-ends or servers from the OVH Load Balancer solution without interrupting your service. +You can add or remove clusters, front-ends or servers from the OVH Load Balancer solution without interrupting your service. ![Scale your infrastructure easily](images/facilitate_maintenance.png){.thumbnail} #### Make maintenance easier -If there is any maintenance scheduled for your solution, you can now easily place a farm in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. +If there is any maintenance scheduled for your solution, you can now easily place a cluster in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. ![Make maintenance easier](images/scale_easily.png){.thumbnail} diff --git a/pages/network/load_balancer/use_presentation/guide.en-sg.md b/pages/network/load_balancer/use_presentation/guide.en-sg.md index c32478369ab..8a8f72d2ad5 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-sg.md +++ b/pages/network/load_balancer/use_presentation/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Introduction to the OVHcloud Load Balancer excerpt: Find out more about the OVHcloud Load Balancer solution -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -44,7 +44,7 @@ With this new solution, you will get: |Basic parts|Function| |---|---| |Front-end|The front-end defines the protocol type (HTTP/TCP/UDP) of the OVHcloud Load Balancer service. This part also has the service’s listening port| -|Farm|The farm receives the incoming traffic from the front-end. This part takes care of the load balancing| +|Cluster|The cluster receives the incoming traffic from the front-end. This part takes care of the load balancing| |Server|These are the servers that receive the final traffic, and respond via the application| With these three basic parts that make up the Load Balancer, you can configure it to use nearly all possible load balancing methods. @@ -65,13 +65,13 @@ The OVHcloud Load Balancer service can automatically detect when a server is not #### Scale your infrastructure easily -You can add or remove farms, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. +You can add or remove clusters, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. ![Scale your infrastructure easily](images/facilitate_maintenance.png){.thumbnail} #### Make maintenance easier -If there is any maintenance scheduled for your solution, you can now easily place a farm in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. +If there is any maintenance scheduled for your solution, you can now easily place a cluster in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. ![Make maintenance easier](images/scale_easily.png){.thumbnail} diff --git a/pages/network/load_balancer/use_presentation/guide.en-us.md b/pages/network/load_balancer/use_presentation/guide.en-us.md index c32478369ab..8a8f72d2ad5 100644 --- a/pages/network/load_balancer/use_presentation/guide.en-us.md +++ b/pages/network/load_balancer/use_presentation/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Introduction to the OVHcloud Load Balancer excerpt: Find out more about the OVHcloud Load Balancer solution -updated: 2018-01-17 +updated: 2025-07-04 --- ## Objective @@ -44,7 +44,7 @@ With this new solution, you will get: |Basic parts|Function| |---|---| |Front-end|The front-end defines the protocol type (HTTP/TCP/UDP) of the OVHcloud Load Balancer service. This part also has the service’s listening port| -|Farm|The farm receives the incoming traffic from the front-end. This part takes care of the load balancing| +|Cluster|The cluster receives the incoming traffic from the front-end. This part takes care of the load balancing| |Server|These are the servers that receive the final traffic, and respond via the application| With these three basic parts that make up the Load Balancer, you can configure it to use nearly all possible load balancing methods. @@ -65,13 +65,13 @@ The OVHcloud Load Balancer service can automatically detect when a server is not #### Scale your infrastructure easily -You can add or remove farms, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. +You can add or remove clusters, front-ends or servers from the OVHcloud Load Balancer solution without interrupting your service. ![Scale your infrastructure easily](images/facilitate_maintenance.png){.thumbnail} #### Make maintenance easier -If there is any maintenance scheduled for your solution, you can now easily place a farm in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. +If there is any maintenance scheduled for your solution, you can now easily place a cluster in downtime mode to prevent it from receiving traffic. If you need to do this, it’s easy to add your server again once the maintenance has finished. ![Make maintenance easier](images/scale_easily.png){.thumbnail} diff --git a/pages/network/load_balancer/use_presentation/images/diag_gen.png b/pages/network/load_balancer/use_presentation/images/diag_gen.png index fc4bad58c23e7602397a550be4c62799663a9ea6..650e413503f8e8ae554639c1fdd10d25fb1df2f6 100644 GIT binary patch literal 68828 zcmeFZXHb+)*EM>9B8mYO5Xm4zMo@xE<^~A^l5<9afU?z+Pl|YJ;BO~G8c&`i4X+2h?c#t ziXf+h5ad+c*)!lT^$0^4_y^BfRYn4Du!YkX{BqjjABBGqq&WQi;X?xOJH4r_sse&| zFe8ZH3k2B*fAX6{5SLpBvS5rLf^QIn+%c(IMHu|Y854P#``};j*^{h+qn&e<)p14; zmdo%5FWO3l0{oHi30gslaGvn=1rCOdG3+sT34*@=kNVT0rBQb;{Vng+lbv|pTl-KQk+pVP<$SEumCcdg+ep|R2a{$W{4#4koONmkfES9f3B*?FS^eG1VGj5~`o z7#Mo3HJyyz<(8L0C6OYDU1J2{Dt*+R(0u01b{`sJzH8Pd z$%^=y&qgwJw^%wl7FDOE{bIk0=NBU>a2nx?l6zmiJY2C#Ow+t(Hr0)1M3ROeu?C@K zo)Vg0SJ$5Mw3s;w1tSfuzdDf>4Z{9n%#=TL;W|LL&IS zN&nYSDu<|yx4d~pBI0neD#kl4Hle$y?3|p1EcnhyA|#Kql>u?g?(6H@$Z}}TmpqM+ zXkY7Alf)!F5p3_djF{o!{vU(Eu=Eug`BtC;k{G53pT7W)sXnYR61Dlpf+iy)tN1dx zW`QO^G-;+0(( zM99SJ(@9sRb?P!vOjm=mTHD%IQD7KRIGt>oXU(Qr-ShcsCr;{SWhC%n)RL>`zN=vJ znDzBQNp>V6AeG=Hg51gnKHHZ?ty7^x21M2cCV>O)-Sn||u%}tbfR>Vy>eK-7b00jP z49tQwzsZb8XLS#wT8ur;B93RSx+dNf2t>VCWy=gi=wGQ^!b2Wq=jYdPiHV(PphJd6 z*9A$SOE0JL7T_Ngq1Y%xSMm!A>ivNWJaJFoR&c%%BWJ)$lT2G8bQV~L{&CG{yBW%8;$3z+!_SBVf~!`hA)?_9$f(F6npgw{4T zg-pN%_Rs`(X$L&(OmE)2Nv^caYMTk>zHx`2-wfC<{(=2n1zu=^QMe?Qo`Hd<=C`gd zMP|I|Wm2OaK7}Z@FFs&@;+uv^lA3nl8JhibGsHdyT6+fh-&HhmkxYJQi z$~9R~Ccu5ykK7(gBKE(in*} zWeZ8k#u%`=Du1v#M^%4uKq zRAMV@>*i&|I7}i}t%Mis!??YpV+K_`zmb1Hls;8!Z*PzDs2fwUvMyG64!1-xF=^~o zMGI-nq0dQicO)KCwP|<>X-NFm*0wnE(W+YmGv&feTILB{Mvqoo{5cq9Xtf}52E0EN z__hLUFJy)({(<4t+EeC??6RN>0w4~!EWT-eo==KK74{2_bagqM14~*-155fY@8ffv zrjU5Y;3itsLjMZzSHqTxX2k{1&n)QB&`_;F2?p0oNW^pKgpJq-%-ow#g(-r;L>+}B z!>%s8Nui{)v$Cps1KxcX#?{QttHDc!+1XW!n8S`YL`#Mect{+KN9{>bbWUz=4Kwwn z3TPx|07DJWGP>vO0v`@wz-GB}7O9M2kZJ1Z>4|8bjF)|{It)DOL=HS^{EtcTz}UjV z!Xgvf#A_a~QMuHO>0+BH6H_Sn!=F8S)-U^?CqJoX_uR3v{*-pF8=$5jlj6ZE!#sI&g;9IBCOI3qE|P)WP6)y!`AcmWKGrlMV!#>!yPl78D$#`6#{Pp)KLlit+&Z zV&{h+5aaoIK2W+y5%>`7@0%zPKH)HYbVFXfN@eHf#!6x&IwIDW{*l1*)8HCkiR!0Z zL#vvbPlrNW#()Kj!UbE&zgN}!4=(49Z1zN;f&kcPi$MEk<$wIR8R@dvH_DB6@3<0> z#0XrMt3E&*(Mh?E?tQ<)o)PvsJ-F$xV745WxQ6IklAK0hrC#A42yH@#n~BgQT; zo;Zp6Xz~4evj^-;AJz7k_FYEuBp@nCsi>$tc2-gOX%Fz&bK31I2wx}t9~7G37Va`- zXJkwj!)eL0BSrf#g0BTUyspR|Gj!+30YoJI4%5f!ZEz!K~tVJ!GagGmku-GaAojj<@HWqbGJbMVye`cH2S4UM}IAbH~;RB9HW83emnlw>*4@+CM26|)K``_|RiarS2Ou9Qgj?g(x!JZslb}}2f#cbUK zz>YLKGI0qvaPP>7SN!-YU37*-E`+>q5}7>gaBTpawf@EC6&RS>0Gr=pi;LIR=ZWcX z*i7F>s!M~hi^ueUF|s>nsTjx*M`Gw>j154cp2e+8@@iQ(ua|)QP%?AM|9xe5Ok{>Q z{f`Q;m^J_>Bjwx(VjLVGk+u>T7?_)pO`v3|c^7yimi40`lh9;LMrLMa8-U&`s(6SS zE}~zV@wi7?C71$?s%VPpoMs`yv?h&SjaZ zVrmUnW##4Dm_U@R+=phk1CneZDCi7XAVw2x!~INlwXE8FfJ78+ZE0D_LrPRkPmNUK z_J$4!K0DfQ7T^w8tfc}-O-P{RQE=u2S>XZjf+6&RIa#Q*ubPI2OC4%2`8L@=-3xrA zjnic3n`!6)D*JD=KF}jZxTN6>T){@keR#e63rJ<0cO}E*lD5I>p9)81t6K|!71cnf zj5PrJJ0&C}BoPHrnst2U_dTRYpJ=IZUE35OE2vJ&-@cvDfQC&6P?7f%Ea`kkc3TWA z;My#{0-OeWlo6N{MwArlYOn<;t{me2TksZr0r@1p?}HL1Cnu*MTsj>K+>d*>i8`4U zgPUB?d^SVlt)(Y|bur)&brp_8kgrqvNJd9zunt4&6vo;qAOU=Me|=fhJ^x`UN<&?J zL|t9|W03m4j|YG)lOpCVWKVPBGNOH>NhT{0CBVya7Y~6oK;8#{&mxroT!T<-owVxT zD8RFMbT7BF#uJ-0&Pj{B|cc@|X6#oe(2KRvnrzJmU|?Lg75mEXUA zv!K{)cQ__qUnW90F~YMi@%ye6qGAAg*MOr54G4fY!C;UGvPXp?xYfm)c=q-DfJpxa zmSz!T5S;adX~&t+1g?dL9js{}D-a1t66u~YMC;bLE=w-<<$Feer8z?nl{^Em3Mx?^ z9IQ@!XIi>rvwz3tB1m(Aa5#Q;4i1OcO(xuO-QAL=AR@BZ<}Pq_{tMA-7pd-yD6k`b zByeAtbt<+@7H4IF0)xF|2<$gSwa@mc0{mZeL3BmY1(Dz(^oanbPkC{+Ai)5NFm(-plw@jqu7!ajf`=HvtJbM zwaL}h)pXOdvj9Fmj4~GTqFIq!N}z5A>t{e0YcB<~wzj5%0%JlQ0}_vxmlr(I-mb*>pmQDZMUDYU+~{iCwRBVB-C+rr{#4kungex85wCJL7m!CS9mL!}nx`xB2eg zc&?I>Yw(>j=vlLnC0CiS$;b?K_Of<9g#;HclnFF@86_oUJ=KLXo~Y~}3(+#yfD_SA zlg~9R(aK=fH#UrNLD>`we7G?bbQ!!^4^)t8S*bqziAut2UkGS*Kt23qfRph}l{8&X zsL^q%hfB65*;>6?>S14n2E`3)`b4rp8jPuu(nY(w3eL~qNS~%IBlNj;W3_uu*zs}h z+afQhOs~asKw&e&Yhe z8BP*43Nir$3iO!qt$|UH_QX|1Ayr)2@)4HN^aGqw$&s^|L1*w}LFJ@}z;DCyXiW|nl=N%RVneubIH&SfXow+Kn z7H1PSH2UJ%5?{5_!SGAGHdAYBR*+S|QKAjszkwdkIHbE3K?E298dq9$rkp$+F2{be z?)S^m?s%7%^PHfx=HtO3@j}X}=DYbPZG@XurRf;k&^nJA+LNa6t=}o+{Cr$3Y9B71 zEK_U5r3yJsY{lfhnv3JKu;d6U>+*;EX+`TfQBY6#1 zUCBHC*o$~J_HX@p?#btaDJ*XG=y7{1<4s80{mRW(?YLEGan$#ajNk6Nn2SNRgwDOj zn#~^K`b!weJ-&K^MP|q=Q>hCn;E_ilvpcC&p z)Ze&%VH+GUCZ0IzQXuqMsHm1@nEugHng@BrRoc>lT886GjW54{tITV}{z%s9U<*`a zOJ`Ive7ku3D>sWXP|Q_+gCyKGv*srX70G!Q z+@CiNopf{0&tkpIgRdpJ@~thnRPWjNW*jK0TuA=*<(SH)6YC>aA@+1)j!$vh>=*T3 znUBjcxsvLIF z&w{V%rFYu(Z^fPHJCmc&X&jYPc6wypQMXt3K^f87$TAun^lTs2c^rRg=5suJ$iKdM z&ETXC|LA9`uks$tUTIvj(1DnCx`^P@MzMLVPP)1eYL$i>v-Mh39Cuig=%T-R@H@^? z)UD4g3-;XI5aP8ynI{->?%3(MDrQ)+Ykh(?s@`0kmQ5IN^Dn6RjeQi&nYfv9;u*hi z{?XxuG2wt2>Hzbh!v33j*tGtcq{K(puo{WJi>HRP)pE5_oTep4&+R%FC%P*Z2D7%? zpC;Ka*Uh|AojBt?b(4wZ==_AL#q9&Ol^-d&$BLcbmyhsWay(D6H2MeLe%7uRj%TD? z@InWvU>e1_xG(ecGQS;R?yUSFH~*V>?x1$_nmY);Fn}RUbKR`v*Bs z{WE$pn%d45$lkL~KHlfqVaUBYawof1YTCkAch={(ipY99wvU7`tU}pT={R>~FtU$j zOw;Lecg}^*rBs*AJ%_~(ts$oA?4?Qac}DDpD_QNY4|BYNvr)d8%TXP||w-(Fyh1`ZYV@*;2tBlAU>fhr_y*<$?TWpN_?)7oBNIpt4N0N|=Py z7OXE`hb;mgFT#fC{COi#kM3uq2$EFD2E1RC+(=cn(4uebJicG3AnWc>rEIiYgH=8H zy1OQYxu|A%@_pY}f7Hz&BQDTlOwxbh_>eu>t>ausT09~5&x-kEU*}@Vbqjl%?&H*B zWf~He0~L$$U%MQgmg=JU2X%Dw-Kl~q6i(4@b(F_{jMT{!>Z;skyD5vwIb`Keh1>Rr z>1f?MZ`n9o__JB;@T-aC%)=z#MvKi~g-7YFN4$5GgfoNeedH!Ph%6pfEWS4y5johr zw_3H|V01K16_Tc7gt@1*dayu{LnJ5ve@MYJDETd|IH2_)Pbc@Z?WzRLYpk_c>mVb^pQ6#Hg|+LCh2F;vurQK52wbvEJUkp zkaT+z(09zZ9rEZQosW3uN@`vHgtu?L!sCs0V&(H7LSXKQ0_A5Z_I3 zh@6DbC+&!lx8k(M-mjf(<1rcLOrnnc+E$A)3YpD?Fz*e0Wr2)^@x3=DGhX#~K3FOY zE-5tHQR-x5$9`X|m}_d}t+?O&Cp)}z!y*b*XyS0hn4cPNFvBLY)72o1^<^t5;@?g@ z=;5^)*6pp!cTKUOd`c#=vr+2HB8!1X9B|}-oa(FlHwZz!<(N4zjgL5K3MSVZ@4F_= zr*SIh4D~tHxi{ZR^Pf$L_pXlonW3N&86cuxsZ+LS;XrxRu6R*rW7n`$>SEc3x3JnL z%)3D~xsEr?%;b}`CFqMw$7PS&g$O$OGDH46TWNZk^j=|_x5BKaY9nTk%v>JRRJp%h zE9}WI-|$EyZ;gAxO)k6qwN|e_pf3X-YJ)Q$RWPVyPMudh1*QeK`Y5-N$IS+W#I%RX z-zZ=Q;EK`6`dAg(L*7|1#kBb^L7%erj2V) z2c4821c%(1Z+K0B@pQE@mSDe7*Ru0fPn|UBWRha6sJ82MNfV~-dfX2u>7JUMEdd=A z*?G=CKEeU)1&XqSVVw)FvE?$2eL4=JS3Z)0Ji6eJ$Xi7^p7+w10jm}%*P7n-3D59{ z3^?Yl>oVe4zIxGXua*J*-(UhybyFX~fpL1`({nmZM&+oqz()*`jmAV`bH7dy0Fx|* zmzr$0T$^~_t$KPWD`^3~pJ|_N>t$&-xywCGes=z;aN}f5F=@Px_rh`_ugm0xoP#DB z=YrqcnQj>mEfhDpuu75?b?yRSYTDilVmualpUwn)ClJNHm%^|HWzr;5t^-<;7qDB} z4`6AXqzU?2fATBF_Qmz|hCKnP2zoT3lzXR3uSzr#eV={d;wdZ1=zK}`#?MKuJBfG0 z4(AdDFWsvc6I~DF?Ai7n_4v8dc~~za$R8WI`AAJx9)w9=WU)Z! zW1nMux@N|4suZK0){2Aa(m-#FIwa|YX??@MHhBfvzle>l`Aq^lJG<4$j7k^TLeIr> zOhqa-eKOa6N%|@?6}zXLpSsvtIPsX7Prw4tw0l)3w1rwS(|6@VR|XFSi(3kd#rj1Z z&N1(BORuiJ5YF4~&&Jy}xu5K}Ml?64EqpY|y6L<*FbX;wdZ3q7^k!fZ1o{~4%+&17 zB+@M}EqUn;&?^6+=zDX;)rI-EM{L0v*79w8Z)u%V=#G^(HL|qk?rqc^a6aN3?6hGs z&F^uTuKiW@*w*vc&cnfHq~(ND6@j%FbwfiRna7XUy21J5uaPwv0NGHrSWsghm06(g z`b|%sb+GkM+iDb_hgTH8s5|9W1f!?P%2ws!y1VlS8Xo)vp~EQ!qXMym#frAnZlw~f zF@eSNI;QaiqRnA>KOY-%V?vU*L5{c${Ya$WN{bY+N5{pDN6Mm7Vl%vIl<+KGD3@%{ zrHk)5$6{Kj=lef*o+;%U6XUbc^Cw#WKGO2}wdG2QV0`4m>BHLBEJ|qtHZ(e>=a1?* zL$_!iAGI+}QL8jiZpx_wD#P2RzrZ{C?iHlr-D)-1j75~!18>{Vgx$zZRxXLr$#_?F zUV7(5y79ayfwd~5UC^u-#;{P9HRzJVcL_448AEehY#?vdF|`a?at+sELoTJxk5&GH zw0=+h6DPLv;jlU$==fTH(6_{g97^v8K$us3_%J5`+Eqc2zh$DLU?A%)NUU4_!@EFh zI8poBTRXY1qw2dmI`>_@J`v-G&k9tJ92R_3MHm(B#hO!I61|cvt=L-a{UOns*3$3t zXCfoli2WZ6Sq7Vi=!`O(eo=i*&27Yi9&nF?E`UBT?p^8uye(h^5|7;?d!<=*S_&<@ z2NN`C?sYCUd7nC8O>Qy4w(RY_U2Z8a_bW-TdW{|XYnlB`Rm<3W5zm8|;Vot5Vg)Jy zh@Ogsf-E!M#G3tun@*`UMr=*42gTWGeSMmseTK-pQ7fEA{CYD$OD@n7oZJ!;Xx9Ze zEfYh%rm?w0-@e}@5p{5iz>WxYK5Op!(@nm(60|e_M;_bLEp}uvy4z{gV_K+`w`5bi zS)pMh>^U5Hz}=g&ayK`KTA}vPdvwDn$l&NIdcdyPkmvzmkYW%21e`^XTm?J3<+8oK zy+S$Fo|V}Cc>3tPNwuGz*qqpb?{4f@oqj2$}&-m+oM)1UP^ zP7g8r6d8JjGsT%=zyITEyriJJh#C9(_DO!lciq4i)#lFn4^$2wn>~x01E;L9t0!~K z<5dccymt<|ecx}&k(-ZMmw8p1yUxeB%k3DJ7#v(mUE&wWPMbY85W~&|EksQPgJN^f zP5;lrAEETtiv0^{c6N3T*U7J;73(Q@h<4ZL9l$;i=?&x1;IQxgW7MPrRfv6gqu(CWm~-S3gYWuc{9QZV?65l}PVD$vASaJ6;kQ z+L$_@P}ftbv?%IUJf?f4HSBrrebvW>eD~6O=Jy8a76Z3Cv&&1gXQuoDs}D#8RypJf zgmfo%@6L~KpE%I$_b&@R&AUs{o2GXnp(PTnIVmLiHk7|NMEWyNo=PZjZ9$4w%8$12 z(QHX?=LO6k_x%R)j<#oIaSx=%*7%b>JLxQ&zvI=1rOx+ZeZ|ck4&LM}E|P`5Fne%m zPWIru;KxP#<CQ@LughfC8Jl zIPa=>dmr&Di5+cE3dR_W87DBEpQ_e{Nyc@R)`(h^@P{M_1i>Hz%gc8)r(#Kk1tHl4b8ByzMO zHdHVLeQChm2`AE6>~f-qeA`ff_e-vmH)99H*dJMT){ zNx|W^GP36j+6N(~nsFZOsya*iB@qk`Yc*S8*u9&{-NlmJ%auk4Mg#8)Bnzz^=XO6! zJTeS^XJb=VzG9anxbr-xK=vD7$;RDvQXgeHQSALihduuk?{%~bG4+wi>xgwZ>yMc; z`8nvMrwa6pBN?&WhPmyj9x4ZPSUqmBosWWs!-dE7pC%Wtxl0f=wZ#k!yt~-Gs&*tW zn{z9=&Ua(u8rEp_D9erY=rDiiXz{?sc=h~(i15+D^>yhxtSUcqLP|w*GAmNvzw})Q zcKK{W`o>+RT z-a!l6#%4EjGLj-XRthtICa!U)d4pAt{?t2sd|u(8R%!Exlv=K?sp%vcXc;MCi1IJF zD?V;#MYP#K%j$MkGbZEk@bI~di;EaM{yIUvH_sY${)=GeUrk6vK0uQt4f!T0=>Pky2k33Z?RnKRc5QB6UaZ0YMw=O>k|yF(R}YC%NF0M!n6UsP*){6` zJ&Ef#F}0{mt3XMCS!i}PLtAu4Y;3HAb4TcAHpe$){g58oz2}46e*d5d8>iJx#QWK<%CrM0#7zAOFZ>(Bslut2Vq0%?WqZ0rN*;wWqxO;>z`r3N(Benn*f;et0e zH+Nwa2m%h+Dw)7_Vxc~v&0^-SjsUc0;r!l1-{`Z^hKp%|Dz_9I)~`$tAHBdgZjoA| zb(mt2M4aP8wv&moVZSqymbd?Pywir1@p2Mhx5t@9h|H-p#O>Z zZ;LASf&VB6PmrL+K3DwXWrbvu70Udk!+ySf9Xw=^>RVe6E4MGlk z!Wx!zAM^5-MA1Y7GN4m+naEE{%Xp_1r|<&H-v?%h0}K88xX1jH{bx8`0uU`Jdd|!# zu*As0+VdMbI71-)92^{;#>+!x#PX`R3YwV|dBtqI(`IqelPUY%yWcZUh3gaHXfMFa zk#+;mmmG0;+QLlDS%E!6L)8IrUa%>Iz@C;H89BKa8+y+bi{EiJ4JZcOx8EN2U0MCP z6E6e>5MWb@m%~jp!3z5SMFSzp<)&(q;GoC>YSWS{VEKp)Y_zF@Mw?zjbxFiH1=!75 zH$g@F15~tK)h>%G+(1Y00#4{9c&lIfg+@nEf)-FIIPUjeUz z^p$ZSU|pzyFhstqXEUOcf`t@0f9**iS;?6PxYie=xw$zOH!-jyZ>^@rH$YdoJRu?Bgp-wZfE#wJ3@x51Bj5EJC{$83$8fZxtT&n@JuoclEI-@)>pv}xO?fg{(C}L1eCdF~UEcS3%F1T?g%;+|~>VE>{ zkDhu+{=!{4=fr1BN+Rpnx>;rAui`zNf(XuF4yOGMZJ7^-oMxxw;{yD`M_j)?ah}1LKM}+<(Br`Kh~`CToept8PmwJ4 z7h?5*KI;lj=$a>SrA8~0e<3OZ#4epo`cEwoPer;g^c(|q0mQtir>Tgi#n%M06JbOH zdD_1~rb&VuQu+TOc5Pr+#VK*0GW|~_t}#DEMB^&}ZHhb;lrEy3y5{-R0KcOFRlj~x zMLtLSp7L^Xv~d|lqlHlF+Q5Ff95OM0uK+np9xySm?VF1W-&bZco61+ZB^z>XnOe&N z@COntBu^Tel@kN|=#y)^Tvpbh7(ZS)R`E-1rG#WfVNaQ?8Uru7#Y9I7qoH+i&?;qe zJ&@PA#BZK~zJg51u5WW0cm?8pE*bRws}Ch5>$9MfP5_Sjb)a~Dfj{*&!ukF`Hb0^> zfcW7k2dLB@g80kR#Jzkbtaq{)Aal6l^?Nuaz_)*zT!p|oksazrFh}GSXq@Aut|cgt zYC%X#;5o_uEB&%+PvFNIVttOhAu-bq_q4WIrqv^;;zRQQA%K(OXZzAD2S|=No`U9& z6*n*##T_uw{~j<&=?Q@#Hy~d${C^5^8?0p@?p(cv)4AHkf$Td-1D4|VVpJ3$KTxv( z*%zWIgd0;9jL8omV;MtQR&6F2^#b4QHV&!#aY#K2brE16`%%FlDY_3;R6wEAq$Z>f z!j8VJY59(f(*?BLdsP^D`mj0a$Mk=fw^B&pm4GCr1w`QJ5b1PJ(9?GSAnm7z8!?*h zo_GDPzaU)=Kw1$ztvq7yHbtFCxnB(q1t3BvuHnpG42498KE7B~Q=X#x7YjxDM4%Or zS_WDHh#NgXCIn=3$X#6Q1ry-=`@=pv8k7CnM3X!X(Lvc)$cHUQW&k#Plux1Kcnq+?dL#zRN~^cEdz|J3It&6Xwc)o03IbXXHUOT(}u}VX6>m0 zUGrSHxW9oM1*&ONI?-@0KY7*$B9Ky0%{=e3*ZXESLP6qf2*tfy8Ys$cKp0iX7cu+B zKx!;?>Dj;NjPGxnA+IIj@G+(RT0y;Y&?#_FOli(Txap+U*xEPRDBNaGU zj)&F02(6Md&_HU(pE8zzoW;wC_QCq%WWgXV9e3)%VT?0Z7FB}H%$yMfWhgjNdY&WD zmIg8dpzeynsk=bdg4N#0Yv_Km2*s=lP}|C@0_KXof#RNz3F z;EPFd9RTHidDR9Ab1;E|{*>OEjVVA_TMcDhf5?F#7q@H%fI^9UWfRJg0FoQ7@=me- zdIAKgp|Dm4vMvM{NG71Iu>vJnOi;OFTe@_vDEggih46Nz7G_~_vG7t*<9x(0pA{o; ziKCE-&6b#T?g9x>(ODqt+RFnXDyW{<2D#}5oEjAja2=DG`=oCxha)EH32(1MeDeijfLZkb1j8^%WbEn8% zIn})>TAjdfW4~^ZA1=%^=s*;dk12uhOEOCZt47Si!88-W7;1n@866$9@B{$ZBC#{- z29yYANJFJv#@uJG$Zqq<$;r8%e*S3;-pqJ;3Y3p9KIjugTPOp&`}(#kJhzwjUahUI z-MHGK7%sX$xBr}wc>k{Lz^%0wC7*Sdt1X5wFDAS6>6}Pk#a+ZP{t1qkVjL|3`&jV1 zKqx^rKx6RHhY<=t4NcG`@bkZa`d>@@Z%q9EcPpHTdG65A_3KO=oE#(xSeNUYHHUcy z*K|+vb)7}MK#5D7Jsn$4rK>%}Wk-T(2!B6*RP45M>^kUKQ8XfcHrc%D1yclaw->|I z{((GqXG|uYZ8m9~j+YW0Y%5=47Mjs{uqEg9NSJr_yBo@8GkI2+7-viEPyg9gnzvw~ z1wMXc|3M#P0*G+%^Z)uWTY#(dWgpARMmN0-CmfzhdLPI#@_QdgcIL-r9Q*q-j_<8Z zj-oILucvIsJ&sG8!)Oi`fowH85(IbFVf;A+Q4N@NpCJ_6N1OLMZW_l5Nzk+9)YTb8 z%HE%!pC77r;qcEWO1hXB(r;!_Hukug#tj25d3Kuuy(Gex0d&zRzdjv5*TLxPI6a_D z%Xqs{zKph)31)N|pYu@J+Ho=J8qbmkLdk-mTK5fD1sNx##>2c}{YSX-@K3YY(a`R6 z)V$VJBFETEQtK!*xE_)k_k=tcLH@`+kiCeAhk%oEwW;OX)d*Cmw!mrp@6T_S>S91O zx%)LGB}E=)QY~1w&`V9FuR*LN@0`$I6enEu3*fJ(H0He4#?Hlc zd;ypq(s>QMut7Yb5f#4jY$HsC?AYfX_9EYk4? z_K!TqA|qHM8cCvBu0O(L0Di8zvT|1q%uahA2L8Qfz~66!qkOFb<_5D`nAZ#ZB+2wX zN`Vq4I3yjQ4i+IBih*^AW7stLK9;_-G$Xh-3Q5vicJ0%Cx3SHW@140nW< zWMpI^jV8-ac&C&)rDY$L{9zj759}V;A117LovfC6d@HyWx*i26SluUgs zovs5XBWZ^4;ZEL^H_aLq{6?aJAR&w=@&n2b-K zK0PlhE879+V*DN#W&Zcmf98D_pSXf{GPi0Ny3Z<3WK+Q{YY!-!Adya9Xv%ZYl-l$f z8ojHp0-O8fRSWB$i~BJd4-Cz4+RB24raES!d50^C`7(d*5vmtKnqjA&bxt%*|-X~pHc+E zOlQG1&iD&ctTCEmOqw z3=X;*fHN<=`KH|gm+(fWU{SYuV;y@9Yu58{6`aG)Sr-#CRZzftv@3s~01S`=1r5az z6IwD@BOKvWNbl1{s{&Dr&Cu|$1E6vnoNys1ye8cF7tN+!J;7~hdF@i~dsXdlfllxO zN`tVKwY5j%ALA1rG^Jvm>uF=F^YON5cpr1wz`#HY1C}U&JItljMtlCInjE%^(iFlk zdcyynM!_C*M`QqO7E$APTVh>ZU3;3P)jDO&vpx@eyx2$_z5+eDmV?786I`D?ZuW%S z(=#kG7t00+&z;tmW)7w00d{%_?Q|En6W?!dZ&Mw32!^9ca;fmNMTIEwMd7xdQ6a_q$jSI%uGlYaY{5}1njOZ&- zY+9lcc$yKw6St$7(K#PJ>^icN3c}u=JdThojW$x=m2yvELbreCKb$&<_Y`F(FdaC~D6#(b+{6Pom8#}|lZWEy|{@lXY3(!iNX;-7~T=Tm0) z0ffIo@*X5_8=_SK-WmbCy$y}|_bKID*GF^>47Rc`q`dPXZ!Ul#iym^Y2+V2&8qi4k zMx-qqQ3^L=gqZSX#H^qdrpJU1Tpn8ZxFd@Jbj_XExVRGm06VcaAnZJ%CnZV-O{lep z=#Y5600nU0<3~i9iv91KE`Y4ediRs{1l%8vrT+V@vihM;fAD*Gl3Y?eKh)Nc5DJ~1 zo~{QNDKYUIh~InIqw(VfH0z>#TdOD+I?NV_j^e7RWm1N}?OZ^*G!h7lg5>IZ*y{1) zW#wYqlfQdSOe16TQO{*Rt%Z%hh)V0T=52yq&xU(@ZQ8oTXwqXj_>o@|EZ&XvdsIGI`DHFsO^f#H;z)+3v8k`S&pf z%Fsu9r<#b-YbuhGebRu}m!sKEX-N+fovr3tEyF|P@x_Wj+6)K@X(g6oG+jhxH;*aO zBOR6y94SG11{aFl=-`0(@V%M8?kRfskDm~r*UhrWhrqqAjt`?_aU#wW58t8Oc@}^P zZk@N=KAr+S3*Q(2*E88*Mg7{WPwV-L_b(&gzrHLp#Pp1gdYh}Mb<==Alr@Ku@ZfiK zL5%0S2@X}S9%aI|{!?$BYaSRoCBp5bj@uz9(2L#)c-APC5$rCB7;`=A6GW@Z$TV+( zYe|I+pvRSitMNW<2uFc&awp?h3I$IirM)I}a`xocu8GP4->XCH6qf+(y#b@-DRSA@ zl=!#Aq}wU~BJA++a3KpAh#fc3uifBhh2aiLhIVI>nH+&-Stp^(XN4cYQDBeN58itm z4%+t&mnF%)fY;!4HhyW%*J5R9WkpmPJ_M7nU&aVJJ&?JO=QLuG%eHLkR8v$G5z__= zV@PNh{RYg(*hqi3OFUn3HLy)qkq#5Qp7_)m;A#`J4HK}9ADP3tzGRdZIlkW>kJV{O?H|-ch$Ebp*T8oswEP9uLfO+u1Q84)4pp!asr+_@!Z>El zEBJl^*ZAi{5-#Abc^^niOS?i1Kru`*ni(Vn0Y(^MMg<+Iv&gj(h^C-SNrgq12}HlV zd#6sFBBZ2R7zbD5qL||7f{>21mo3WQGvqOFYu^JU8Ejo$BUuf^LpVBupMA#0Hh*A1 zUS;))(xXF~Omv!>no>bg-CzR!o5w0CDe1XjV>1q#jZq9T08Je`LgRa#9weZ$Yikb~ z)08b4;dtjk)od)q_J>e()x7|q>GlB7QsI9Ew0YM9jvE+LW`{66pTR8I-gb|1phNE8 zSZr%;#l>n9tW&hFNXy9F)lygYQpT7tD_n{ChZVUtS`@>0_x6qsz&;knzr||@KiJ(3 zAaI%j;kTKgnbGG)V+Q<&9oDbj4i6{5=p=asAA;4AH!EOS!5>dZ8YPiM{%&@3uq8mE4Dy zl1>e|>`4vPI$--8h6+Ro?IU8eU98Hz>UWP`M+z%p*49jno94^i*jc(57?u3RCm5O^ z*H3QjnV?P~+LpLi<<{2zZY;KZs&E)rU~t-r(&b{6HAkCiJ~#}BoC}-a@T0a8TpRC4sWCxk0&3$-TPyc zn)}^xz4YL`XueUS6{bxks7}U)ag=8rT;(r6qj@S{@#;!tNn2o>9)vD?3&y znKm{OZMn5M(@>zlKDGXS@_a~1^FwL9YN7WmON@QKz+^Ehhk?R$%H43CC(~oT|0Hv! zL_#O_r+=aTL!0M))paoU=^GiHXrjfymkKmUz&+0?6gHXRy?P+F`;L_E zd6$J9Lv&m=r-y14_AqUql7p%F=TniW*gC^R*VXRw#yG3~CN0a2uv5Czi9S6VC&upu zsTR~{#R@w1*)Q@XM{}TKNokkVr%SP#wzl^xMo!qw_Y_YkwVCUE`=72!KAijUabK6R zM@5IVbK~Rcg5Ei^cgqT4A_w^~y&uJ6P=!LB7 z9sysgXJd9=HTMoHGbvD}mpuSEHcUe6qFeQmt#WNYXngmX;=B1oTh#il^FEQwzezwjXB!!JFWJHCsspD| zW8azl#|J(A{cdQW1WQC6fiE0F&Ntlv-|OJ?`(9XboYAg1o2d1N;W0F8)Qe;Wvf~+x z1*;E9PDe9Gz^pdB)Ka*J6$}wgH95|#+-tiG9_o63@~ZdQmE4V@l7@#~kCQ}I-j;bTVh|D_6U7+RRmyYrQ9M;~pF9TeDuvee z_C6w@K)ME-dd7Q)_{-IrE5V-&UmL9y>9kvwbgW#BIX=FNK}E4%=jj~If?|D2&5ScoLC+0*Ez5IWp9`HK*;%;{w*37PTIKkZjndOTNuyO`2XoqG zwk?kc2+KC+nuf|&-|}>KdR3e5h=&I5*OWav671bGQq~(qyRUo+nQ`$ak?S<%Zc)2O z9Yy6FQ)QjJy;5hQ*@?}s(Z5O7w7|-(ZfEZ=yoD}_o*quS8AsDq&r#UdkxtHGv79F0 zEz;9J!+w>h)hx4x#`&Z5@|oo!mzL;Z_2^?&0_<^UHMJQzl z-j%n4f`ayzc6N2{2iwcOQ0C_a>jF-2Ac?0t-pw+i!j9OlGDf4RNi=)qJDa($qf>If zZB=M%+gWjFbFpA9k5yVKQ)<0o^kThqqUC}YG9q7@I9h6Q`gh8PMBLZ_FlIepPm z*bt+N<&woGOC6pr6Ad;>djt7QRr^O+-;HQrqvP+~>fk3+-|d&pN}`GY-_>PJsTJN< z-*qw4g%2s~ZqgVQEru-g7J)(z_ii%EsyUL%WogB;Z1qR3MT~=UlYHyRplM56^VqsY zi_?d?tOuQklj9$9i=SE-B=>rCGk+Widculff#0qXF1HV>mKoT zJE?_&^Q=D7RVF&+80giZKBgZV_+A z=J;X{jdzzLUl&ig7x45Y?b&?bJ0Wj9nkJ#N6{QekZg;>HlN&QMn|&AF#+AjN1HXbth1jg-X!as?-Cl%Z*%aB zx|5eU_$}wP#^73^(4<^SbnKnA?TvVc6N7ixdDgh`O;JiE-Cetx$tbfv);20l@Fhbx zVd*FpThwI5t!b#ABJ>$0s1<6ya_ zX7=QM-OYUKLe`kc*UYIFEe^gJf975q`kpY#m6l`*YksX(09Rp?b<6DYJrWmtH4WG; zINux|v=egu?DLi(Da_$ux!RQ}lErNsvhI^(aXfpMDIiN9>(TybxqkCapWV<6Bk4?G z?i|N^8U6)ay|dG;!55iI+4r|57pw|;6;{2(^(yo|zCQJ?=c8zgo&8!Wr&N3J{iq%L zA-BZ%hMQ7LzjJ05c>$?{l?-z@t;hW?DnOLpN`>{FydmVFltlNYm{h%dEJTM8oQp6QZX&;vsJ{57YQ^JsSPFUP>=UVO%St`>leK|p z6U(E%(ds=Bx}O9x_Cm|`f`aQB+aujMUTZr<#82cg)`lLs0>f^L`@>@QrppP#$8!D; zdvE;~W%|AWv$~2(t%4$LAl(fTt8{ml(%sDfDl16Kz|bMmIW*GJ(hZU$-5?zUGw=Pd z`+5I@_lNg~?;LyVu`xdLJoj_m=Y7R_omZf=BLW0&Ynz@Z486M+f;Rn7)6plH&`|g= z^2_cr&CzxU*J9bye~Vf!&vVc(qCoC#9Ji*E@hmVujT` zug>|GxpQfX%~;aI%{wZNg(CQ zJQ;T(V&m5M*qEE8r|0QIKyqWch7TxyV)3r^zGbW&_XMQz6Q%qxdk-XK8uUu-^tZIK zM{FEI?mv$k5MEF@U|Y(4`eJuWz;(K!tdCimB{j#2>EddT_vi5EhLk3o2#52ZnbVCs zJ>0vty>ZM{EB4w|~Am zRce6$1+0HeU`zfc{2aIA>r+D)w7&Za#eB~36z(~lNML6rUY9gcV*7fAFJuSCI#7F6 zR#i<6YG`!M89@tj9(T>iBiUn%NIIq4i+ZPGO{5bAQf(Vl1V)P^LfC!9HjbWicX3A- zb-(0ZnoPZDNn*aK&W4;X^_J=wGQ&kS=q8_1!`Ywf7xL|CnAvGurP`0q^YJ|z{;4BT zrlXKXw`zJXO472SxqLP~zoI~8 z^QJ@!9KK3$$PxB;&sVZ$M{??V(@GJL^`>kPCLLuhYA4pFYOm5!x6o1#9MYPm zUL00fF$f&@$2y+G&^t~${T+<-ZS*jPA^5h1zig*OOjob8j*1%YnJfG89UhQ~UWGB9 zPI-1H)}8$nsSw?jH#+ngf4IsxHbYC6pIfU0I`-Y>S#ue^!lOHlDV}?mFb{@pwkA8o z?89Jz1FzMmRjEEL_g-f(VM-&A8W{)8V<@;Qhmx4vc8-mz@Yi(7e=EIZ;e*>fR4|cH z=uC=WbPqQ=s4Vviamtx*J8a-aSv~4xrehy|km`VWW~$f}PZIIxTIHa;v3pcWVt<^CjDsikRL8=jwY_r>Ph0}U`i{QVmVH4cqx!N>r`1Dvm!H$mJhU|PLT zz&>TSQ@`sz-FSMtNzk$zk^Lz|*}zC&AAR!v{T~)6T%0~UD7=94f&vwIjvIpG?6FI( z`w1Zr=tTT9<){l27ycO|u1OsG+~+Q}*{!Y?RUKcORwpjVbxnfseBPinpEqkX4 z^JB8g`R!wEKd!-8JbZ$*fQo}~$wG-1!HIi{sL|33+nR9-PX^O*pC-=1*A;#e@Z~xO zz5gnI0{T#$RLA84jV8J}>k{*h0rk3xtm9;k)T4IzTFhV_In}0ozA5ZnCWm`MIE1b% z*=2mTi7-4|cnWS3^0|R~7dyTOy2k(M95Zq^G5PvT)~}fNq8}CT3SMbFnJwfr$2;xf zl+I^2l~HBMsn_M&s7<0ZkFT70Xu$6*_g1)~I@Cnu>Wts~yqtuJpjX{Ql9N5{%NCjU zff?CzZwFYb!{CpK@R4#ZlI^XbH`0a6AQX~G%avK@G0!aH!FXqJ#+6SvYD`Q=z)aIV z=E-W0nKAU^K`cp3baXV*%+j(3j*s)EFWyr3RFAGp z4uwzd)}LtE3p%L)yc*;RsvomdVt z>Wr;w{84^(rOY_{rE$a&uX0K+g2iPq3bh{aDgr~Q;d)6_w>?m^@uR~t#e=3Z;Vi&) zJ!r8$)yv42t=%mneSvW&sq#UKl$kN zVNKe_PhQODeb<@r=M`ObAC#-o&B|{o!v2p;3A39w`6;6g+G)zmPRQC?H+859?VL- z;yJII8Z@r#sgXq!%@vBasIti~P_f52^CBAZth_WFSiXjkl^RxQU+~UO zW)ID^)h*VcmHa-97Af+Lj`y&bb{`6p5z~lN9)Fd0-!H^0&o+MRPHbwFsI<_^9a|Xd z?6VOpUr|?pO4ei)6zJr>zCKa-A2@xFAn5F7U^o)n^e$0085^>*|Jfj@%P0e1lNvYh zeqD!te{0TBUc1=CZr-zVCb3&SsQ(?}Ti0@OvS6C_s>D}f=Cl_%tImxT?CcXI^SPPY z+oQwGK(X0olR;x@FI~e`HSI$q)j^7v?SpNH@epHw^ zuT8H9#A?c{Z5GwWFIny7I>ilB!wwuq6WZa{oj;cJT`(B?%84GuzD6xjNh4iw@?wSJ zt+OQ{tv&XLfysZ!HI+x!ri$pVAC#1^@nd4D_tDS98w-5)H*QU7j}hcI2`HyNq(54W zYA&X^><>Qbi)zkS@$#CUiBkSMRk*gdV&IZ+)%>Q~v*91J{=x6xy&(a53S@3t#P2Z>i2O-y|} z^z>j7eOVu9g}HcgO{uo2jDL00O4FS8wKht+m`08$MiLqx+L*7T(0BhhWFhe6`#}(; zt$(<1K1B;0#S>`2bdKMG0FV@g6^)390N<#8; zI8G7LT!F6DU+*zd;tlK&B z!C$Hl@jQx88Mmc8w!k!WrH_oY8{&M)92 zBh9h2($!MMy#Kg7Vyio06>?ij4M9!6=pO%jNw)DUb1$!HmB{ky?8Uj*NCoyl*~K)Y zeR}}jXp`=`g56Kc&qfe*{K6O}y-jxLqQ zwT+`6Yb?FcW_&r$sLw8P_09kHG42sE;F#{J?TUXLCF+k#aRKk^S>`Lj;k>MNm@qtC zpXVN#t10l;*^h`iUM98`SBFGQ6)bI$a@#UHlEnlf%e>Y8T;G!`RcTnt( zR^uT@B=p~msq5#UFuf>dY!oVWbVkb6oG}CtmjR4eVD0eYeiEZ%3iq@y_XB ziCDrb&(9V1QQLi*A;Yq1QfTsV|8hMCJBwmjOV31?fQ!a6Oy}uK49ui#BWjc&zfnlJ zZH|=--fC)ZW5tr7Zb3D^LQb(AZ%I3OSjk63uk$}H!0D!b73bQIBXkv)+4hmyYpIc+ zKl;`P>b4{65ph*Y2XtJRHcy%uOTh}E)#?%$;%dQK_GwkT2-33oke}&l38@^A+iqh{ zor_@oX5<@8YwhOdW(#T)SD+@7aPA9g9%>r254zcyn9hs-SC{ZEJ-(E8yYizM1Ibp~ z18a?zT{;o;Pt-;i>atW0>t z_=)_<2KuIBgER*>+h2V4Q#nQ3Ro%m)@YqutF*VaedCLYzU*D3n%X)UEN7O^!^(V}} zhmnk?x+c*Z^fgV3ah?o*uw!I+7_={o%ggBHh7+yMBF@zJ)e|bNk~k6Hu3Z9t3P@$06Ea} zVVOC$V(l{9ayX&n!;1=BVO_spuY^ z`kEP70NWLmINF}auDbn?yUqC>0~TbRxu%#|Q;JTO|q>@ei+hN?HxgFe=(*0=6y1#&6RJ8L1FET$n<8>fa z#Qvndl%FEKruNZSlj=-@nVM!3Y}!g*RlUS5Ws#C4u`_J~cOE)pOJ-K}_<0W`n~=w( zwQ+9b>I2@}N}rj# zi3MEX%Js4Gi0b`_aog$=MaoAuny=!B%fQc)i0%P79l5`v|SG{fyD$D%~(v0 z&%Q4xV&V-lVSTAoS@opjDr@hyGY3^PhO_?FS4j)Zw^jGy+9 z;cZ2s&I6XZY{H*K|FLp)$@%c|lCyZe)Uc4RM7tBfx<`=7Fy}2?H1G6ep-KQM%aW8m z$i;(dXxy_|Ke1^vDqO$DJvn@kzT<%)h4Oo2tVXu-)oWeBweAo}9-*P!dKwJ2a_@Tt zSb9SmbSUO9KsYaMB%VjqKexU~4SR}e%2-mq%$%^B{i?a;YBpjQ5fRBShRTc{@Tl#M zpO)+ETHb)q?2fx5vA^(*X3lmZItMwpNyPC$4JJQDCOBLeG$;)UMjj>%u7yS80}Vqc z=3&e)FWwGXc1(;d4aO;%nQOpiLxmxxD%FUP=cKLZ36O!l`UB^6Q zlLZ+~6Y3~IPCc1}%AFsYbt^a1Cvpga2hI$LP`_{UB1rP;b9Crbf04;@(&sFsMVeVe z`feU^ZS&UcjiN^O0`^f4&j!148@?&2{z8pm_n|lpOF$&YV}40tw=l%8GTRJS??7Zby>R2b3RgGW@)khz0GMmOH;52x~88n#0$&$mE+U-Ofk2t2}zC4Si2Ry`fcm@XR|c-Sxf0`DpV9 zHx}c5Ts_ef7XG5sx__$B(aFGil_RDya`sGW1#`q%g;-&FL>5C#(CfO? zB{Gapt{cZ{EENQ^CKK`*rEovg$Czj#?P)0yh`6W5K0#*T2J|^jJb6WKTGR#%R43HM zVQ%sVkih$=tvaz%mfja+IN$S8Q~<3_dYG9+k7g?dF%`7Oy87exd$h5VLnGuWuGa7C zl9?V-QABUm!NW(k-OP*TvWjupMmr{FpQa0<2a_l#qdE6S<0$E$4aSUYhwF+d^@ZjA zJ{42b7BB0R3WRU<=!lv-{w&xbH7*Qet34h&b$?!7?Do<0)s$8cY+^eNc-V#I>oqn= z7S+;R^%4q%rSLgR`Uv-=%}&nTH0;-FDj}aX-8J{}P2E)3f^`JpY0u-#qoS&5pWh}s zFHdY%%p8-Cm&VhCOOl8KG)ij>!6lY^EN6Q9^a=@H5?W!akQ1F%q}-p)Z0F9h4r=Cowq{OtW=_>1)&W#ie3C5?X)1*|8YVIWYJAZf~{O)Px{v4`#Ve zTi!NuUFVtp=4?6)PDI~Y&Q6F>;wDgxkMmg#DBz(u`Gm?fLkE-JcaW0ZW#)Qdq}D}A z6~Z9&K)3RWeMQa6B}ivFsF)H|eaB~Je60Zoi-Ptl6oB{WTe`o2EA3=B*(0L*o0m~k zUp}}oSOv`CnBKnGz0=y-ItWoct~H_=GXdjvemFWK70zR4|Ku+m0r^+9jkKU>yR`}0 z%Vz)|hJy<7%;f-uKRk*Y4wxf=qxxMJ&|T?j@bK`ixzzt6R|Zh4k7x_LLcfqA04yr< zstGwbROz#`wXF{Uei1uF{*t*1(PlZD<}CKWOs53;{*#4eK35>to&&M0bS{kzl9C-M zw)aGs6#Jt7z)28$S|J4oq6|K^mX>S0kdFnmP?W9%T4{hE%=h5(G0wa5;aCsa+WuLP zw}`(kBo-sWqT>)6;)5a0#(LeB(|-b(Z6qR5kk*>B^#@dsR4 zDilvR^$i?_YteU})YQ~TH_vKgdd0qAppNu7Ega;nY4gEgq%<%|36gUD48e66!>L5e zWM>Wi;Ptlvw@!Gl0!Zk$fjj;83t73jYvm^stCMoXhi^b_I*wT$P(Gn?Ain5dzkWf@ z><|g-ktAqBKt?($C*j`2DgEAw?RPhv1YACd9|p<1|4P}~+Il$+IHDml^o{GTg#SW3?I1*pd)F~!*R|&DYRJzDSZ^}Va7xP|n$|!* z;MQId5V)VpsI{B*tVrL-NpV$;Dfy4oI!6Oyb!eoLLBn%goD_BXd-s|d1}i`={*Uh_ z;N{E0DZ9E^n3yg=3&Hmuh>Ry-3Ejfv_*jED9MEhd0Ri=$?I08P1w3Xh0b0lc#!psEX=xpj|7c)PZQRk6<%yfN6$iT^dH6%3Pr zdI;Vju8DfTfLeA=Xiq4StXf|dqh0x(TR3VGpoKtNR8|clwMsmT<^?a8`I;-%0#qve zCfrlpWNl7&fVs+Wrk+sCstHgIFfucv8KB#I4Oy)U$Q}5}TAyE&uvEi{vi^87j;~7* zlNk(H`=VqKQrgf;QbKomOVhyMfN?U!0+@pyh!vC}UKh!|k9>d`CJacer7qXj09rD2 z)iu-(7-d~n)Q9xs8E`&-yh1MN0j71cjtqG^F60(t2GfOIgB zRpWu!4)C31yoz}^qrj}4<71%xC<`dl^~!0&=YXL9ZUq{t!LesjrX%%U>~|imcR9}+ zduSTKv$~zs7-=GrWr0YbE??RJncAu$ApBobP~l@+Gg41*O54NJ?+FVCczpp!x+rux zXkGvZlCrDp5bqKj1xTpi!Ak#h|4B+)a|L!&$<~4IO&k`}%jZNm3EDtaeUBRN)?hr{ zYB8`K5s1->Mzh-iMr*JHAbvoZkUok@_u>Y?Ym8gW3H&k^h2r7XTk+VDQvQJ8jqK4)OitNTFZRwYInSvo}_rG>4N^PTU8#qy998 zRn`WK3n>N&4~=+Rfg1Lmv|N;zuj&55cfg;`&#BDpwqFI42v(pzXbwy8%afj-9tO;^ znGi$&I~Tu&mOP|sg!(x;>dFZA!2v{ZOsHtM1Z*2e{#>f3V0^^te{BPxz2e;p#G~h+ z2b|O{p=mvbIJ(sg@a7!@-79Vn5|N)sri1%sz=;C&$#>XT;4 z33>+NaG~caIzBlunjM+-s?S=c{{f_uS`fFh3bM;Qy5aT_G`X@S1s`?PCGh zk7nrZ%}p@z2UJUv&MF@Rm;n72fJO?5dt(0nw_V`P2ILj@$z(LIzx}uE2?vLG+7GZ> z%XIAAfrw8oIQinJp_?R&h>T1#*45pA1!(wgk`I{2Km(giarATj>kCFZ2{fdEu}0R= z1yfYNxic%f@Pg05)|v|;QS04^rb3YPO)Xb}TK zaOjsREeDfZy&whO{7K^36!e0x$23)jhRKVr2$kW>+L(gDe7{J9c0?epg@z2krq2ZX z>EEx#f@E6VBFNv%0oFWd9s>il6l{M?3wR$5(Ps`@Jp#wc2xNHz+2!TsQG#XbOtPTy z-~sS%D(iL(A(aI;|Nr>1^4GI^^gv#^N=)VQ%YUgE5^&!HI?2l~{5u%H$)mvX$kbaN zN9P7)8>3*f71oJ`+~~O?>;XQ`_r#-%YFRiqkxu@@RkiDhYYzbkS^yCIL|gkG2!0O- z-|Pms3XTsEpf3)9@bk5`AysrWk1US5Mx5fZ%ef4`_M z5E+wZ{0sX5qT|aqv;Z;88~|b}34<%_mE4^1ucl2!JseIMgpt00f-?x<28BOp;a>^gls8GY|gje}b^4;*=hMwHWA| zd?NYpm%vsy{WBQ%RAxkFF$O4e4orMPJeS?v*btlm6b{@FoWG%70~`=|#w5pMtM+?$ zP5^lur!Ndb)|tIiD6#$72YMGkP{^lk=neK2Xn}&Y;sM6kUA-+@S>UB1Av6ODE>Ef; zNOXgZ-Z!O%yUz7C)F$MWvIBJmn7pXvCW{HC>_rViH>2F+f!7yWq-?e_LF~#u{9moPOT`DA-{N zvO+~HP{$kq!PvJQ&w^(kK(m9^Qk?w`Vt4CG3^g>4zGUIvxdnQzJ*h3E{ZQu^bxli@ zkEW-*%?{p!CsXe@`HX(=w%>j^(7u#NUn|?`;lQQ4+m~wAnV2{m9wW@}c`)l6;|+6l zym2G^?(L_4-l!nwpnLc8{*%g##&Pt#rC6>K>uHqG9Q<#t8~HEX(@(d&HwD+mHeBn_ zzMC3Xo9fLM58vShI^Dq`@B8uNhqQXWhH{3A4&7v=%KcwgGnLjcfQMi8rsc-fz}_X{ ztv?1{)5Qq#2nd`pGW~%=O1SVB4o?C!hE7;m7*=eZboBU!=oipgwL3pQ4|u*FbTJ#5 z&%WbM0#%C6){l7DL^;sI4XQ@rpwoIgc6rkA5AZKMx3fUwH27G(`3H2wKp%o|a7WPR z%lrGlPN5GEM=Rh#fX}yd>)Il z%H*T>rU^)tfueju)`K@9xNq1>3iJNtz_tHb`Zkxg*&h$5s0-)aF(poENvmMXJK&T+ zpa0uB|A!F34F3NIggRDi*nMQv#b$sndZ(t@kO}c<;FM?+jl%lN!0G7d*ihiK>Hq56 zLbl)}0L>(wK{lRD2Pg{;-La|CD>7hXkIjyw5^+=Bz{ zz>62&3r^oa5Yb5s1Ye1Q+7|Am-*ZweqELery@|oRu`Lkl^SH2DAycs@31BE5Xe6I^ zge_6fRIr34Wj>AVU5V5yjyv*0v5?%GJ9c-@(JJJXRRa?2;6J$-^6M3A>2K~-(hVLy zYueLCoey}%Dc5wTc`b(2v-Xw~wEYHBi(ZZPaYP?qcWm&*TPHP{>t=7P5r?#wn(Jzg z^6Y3ZjStduiS+<^*U2kXt`r_clt9JZ(MjQ*UzQ-Hahoy&wi>$hL1f?BVK3-a^aN^xZ1KHR2)XS3>YW_0vL2N53+G1d zr!aXq>|Cu;(E}JydIjIqLR&C)rPeB{`!hb7{}3%V9SGY?N8c3+k^{Wxru%Bu;Gqo%SSbqN2G*AM8^6=zIF21BdspA4PW$%s|R>k z4Cr@#joJ@khmkLL6XM+y2$9R^IOa)U0wyyaIT}pvjoPN29Qczw{dx=}Ou=mnFi`gf zjDQd?VbLTR+S@VRX2!s`0_q9pFs?*Ov;3Qpg&It(o^$S#7-06)Sx+MuI!9WlUk4s+ z?eL;FRywVa{YHU((dO~AvN?OQK^Z_~fQsZcsRj0X1#sGs)HF0G9kH|OQUf+mMDGgW zOm(s)VUxE*-|6KLm>41?rVVdew!QfNmF7g4eOo}O0X#?3q`YIph7^iNp{u;ercp6Y z)VTpTVoz{nC0=QSNoA^omk*k~@xi*bfOVajoo%Se%v`$V6Ezqq7@sG6bu?PD3#<^O zAf`lzR29Z#cw=AbP8iE?BFuRUvsaAEmW|$38M2*zqoikley9Bf(9HZccDuqF2D?1S z$jDHRjEXYm1j?UM-^zx){jFHSs-A1uSXI1# zzIJj-7Wb6df{_HT`wkhG_$%>V{A4Z#aV}bJwRBQ0bDd*8-S#B!t3KOj7DI(yJZ3?G z-qG0m(HGe=bYHWL4fPy@y$|Mm(1n|~YD(x)`GbYt2Y$v)YrTcH2GLc&%4loHzr0$l zZxZf`(RW_aGVqS{q^s8pTJwE7c-UH{$EwK|PkQ;41|YIJn9{urqykldZH|nLl>4@P zxP@dh`1U&y*lp{B8JvZoLI0DAm-GJU9b++Se8WPoOBYeel;Ah(oSKDx+%2E?lDY7s zMt&6uMiNti=e6+iIx{6ECZ?#E+D-!4^s~CK7_4`-!`wxS_V4@R(Fr7xWZW5pAyLY_ zj#~Tz3mY8WDqGKNPbgd-f^;qwQMeMX<3*V%b}=q>4{cGbB|m9XL5ARGAP$e2()CjzTKOUm4B$ z4cPgWl*#%$IK~S5cDu~Zj#E|JVpn`$nGy)d*BUrX4Gj(Dc6N0kQxX!s6{#?=FatCN z>vYvdgZX`v-vEE~^TR5$j!5MUFNSXct(Ph+w9M4A>4Y8@VX9*9EdRlOK}v7wsoZnC zqLK21g$eh4w7T=M)?6Y^H{(n0)476|#A>OLYu*cBqeE6tM^DebwXsp_e^Hz4P}dCv zZ9am7OHVAJ2HDu?C#|hLc>?mIjVv3@Uy4PwF+=oeUM9UQfw;|rR|1HOER!<%^FKLz zh0QCXepKUHe#kH>(;T*v-QHTbVj#H}7DX*`!3>zU>4`~6dfH&Nunlkhd7Qq3H)?A^ zrcXuKlp&fE@#Ar5`_|~o4^JvukkW!w?^3N}x(?^59#5GYdrWCFt`)`}Y7C?{X~Vbb z%D`L911AhQ6;XB^^a z`Qx-4+K%rj(ciRiP8D@l*bos*y&Ke79RAf`k+E69*=d#4cd!BoABqBb0yF~9oeS|k zw!&?yrgy(7Etb^p`WQ=hK#U^Oe?^&3Y0=T!s@@k<&q6 z@Y_S1wApfBVT}Uis@IAh16r)wF{w4mWY5l<9H*;O%j{pq^sZiXigWopZ+ug-jg9aMYlmb5K)(mKP==-){qDfqKAdBrMSN2nA!XaU&Ke&7< z*leba{!ejxati&Nj<8b|>XZo(RBHllvHG{5dzly<$y>cEE^AQ%mrLA6DDof@dGgT7 zwseWrW%OvS>%uITB4ZKTzTT$PQBgp{aSs}V^mbz;o5(G8!n9t~&F?j49_AykBW&4Urw53idFDFd`&6VYodE; z+dF`}Fnna~uxDrSGLqPnGPfQWKva0RK?N9Qii*k7cc{%ykjwS~iohtnZ%zwh{EM#| z!bB;3mZPPqfyCPR%7taV+l7#1rtNv>8?E!ELc5b!<2ISxEh-s9CHwp4B)Ig9@x6G2 zlmfpgApN$LkdP1}O(w*N{Y-VEWjfU;e9>AxBFI8ylvJ>DYBs6&%-vdxQ!7?TQa!I4mIS(is)##eMuaq?m;D=oUfpKpNN@tLJY?3It%sc- z;I1B?S&$x&V1~qrM5e&bIsX-%;dW6GDy4nM`klqmfYQ7|EP5$?@K15j@~f!8k}WU< z()PT;gkX#eP@0%Dub8T;LHVQEXSun;-{7ojBKq4=2*Js&_mZSeH;Gyu~NNd zjA~t0RzKpAiYiw*H-RNE*RP(fm~pm|m31Lz?Qu9`YWd5;&~5v(ns55E$F21>xd^!} zfNa>~GSjXS8X6kx?;OQsAsBcyctK=*5A7qECdkz*MGAEE6^2*W`@Rn(7#HPbpMChY zh_|>mk8<^!($z=ohcYca)a)t*U6%9XGd~U+oWNU)9$eF=6mnbFhhNS()Z2e8F5W5L z-QDe)EYfvF!!`}whJ(b3gnxgp01{28mG&qGrn_HTQscLWSPw~&R zQ`M=n%>iIekf6(QvZ<-5_I%ZGNvUDwQZvWn^-s*xk2H%!a=`jUD@ZKd$jpNDnsNT={rXl<`(K?c8o=m%exx~xTV0e|`Ry&%{FGIFkIfz%g#Ln{M%?)oWU1vfwjZ@fAa?T~2i9)Z3t}I5u@w!>;%;lZnZ(&xL9e zlfT|dugvaCl`jeGgPg5xaBwhkuE`HgwA*kvkjboF(qIYZT?Hh|&<5o*%p(D~%7gX0 zNZP971OoMVv5l972jcfb19cx#`0ICH4gQ7CYvw!44{1e6co?9>C4O}YBbq6G`nvEowZywJ3?)mwFt(QqlCMC0R6i*W3 zBt&H4J5^}oav7xgH8^Pc(wsDU`B z+lR4Mv6hnz4v~_PDwTJulr#RcL!MjdtTZ6^{rM9vgvSfG@ya03XaEBTu^Z5uD?`&P zzk^nw-G;?bW=s@t(q6sTHv*0#|MlwwR*lHg%aO0`^$&S-r-F^IQn~x)-~)W#1n{!3 z(*vn5v2Fb|v#_c)pWIooh-xXswh~jVK)!_bYl{T)8>B(^xnkGl7=|B)*H0ejvmvB= zn2zH$)|vB!)zYX_CDPVDN<)DjtHg-XT;0B;)w0O1j95WS^N?-n~d{u#Xlx`$Hd6T_PVR2c!ToN;Z6+-GXN~1 z30UZyM}NN0ooqctcNT)qf2?+?xr?B!v==}*(BtD|XKi9H3a!64S0~dHtCOH& z&++*8B!03St2|?)aPb(Nq%n|#URPBnepY^d@j*k+k!Vb3SA4#TRi?n93=q7EH-hbVV9~%gZ@6q9?X=M}PVHqif0Us2 zjj4UZBq89X9+`MAe^4dNRA%J^G9xfDM@l$?(mj`AJsL30D13Z;9DV{{D$TZ}cGb5x zj@9>54{r&COw?Y#-dlpA3Mv5=9je%#djYM9c)E0k-{V9H^Q)^&U3OT~f$H6uJ zZSJ!%bvWbqc(dbk5xNLfA6-4EPkdynL~T5=29zm;Q||Whp@EVsgsWz2cH%KDgBpe7 z6A*V11!f>^5z+XcEu{MabGZxzM?@g$;$Gt$eHb_-zyS4mZ3dD!Irv+N@v)7nGD&$c$P7To=p3{E2297P4eihhh1*}%Au z&w}c-boCne+(r-?@4OqA5L}guZLjo&`B(F?_R=?T4Fo+(pYsU{dT*FUiJbhR@|+#U zmPPq(M`=NG-0chBjEGSTgc>>eccD=g*@BNQ@HGoFbgGS8iHr;0mz z-B*48IXf|azxv15Z@ak%g)27Fch7R!&(i|bHi_*c3eMpc=315{p~SB<|9GtCqN>&{ zDSIA?oE=UnN0&1Z{uw`a=!XJIqv#PZW9QTnKsf@8LEW7J%5(LDhv{AzkbZ5S^F%c^ zgH0bt+xBTZFvH^!c^}gtGcXpLD|suh4j<*R<4%u7!$|kE7&M~IbrF01r}fTEzRo~I z_v~m?8GCsGYbxDtKL=i=JUgEC{`BX^d`qq8*%4St^!(;{9fADO&w=KgC#0XZWCC%i zj<;Pj5(K=3+kr!b-cSy>cqt#p;{8FcKLB#nyw9Sg(~d+2;k5PkwJuxDPi`Bu*~uR@ zWtUvC;%8$=n%v?6LMUo*O@7{C&b)$%ci`!y-22@};j zePE?fYzR3+xLJ}j@Od;DB#;Ds2Lqpz!9=9S13!JWzwjd>OEhX{6`WVUftggthv{O+ zOSm+!->&onj=MZn2ce~pSXS2got`mgCAJiGp$(|~8*@ThzPwTc)(33pd6d}MuRt+u zpQY%b{)Ss!d}zNiC_x#+&K9JpkFTCQE~rLo_|L7~3F6p#AcAD{u)`GzS|vlBM#LNW zY&h=Lt(64W#&0LS%8B@#u_~W5ev-lWQJpgTrV@#DXxj&5R<9giIEL0;K$)CqEgJ&-n5EjlGg1o+ScG}|<>Ze3y`25g9zZTY46y`N$E zE9H->{Juq~cfC7(Bc%ZTQL#9_#>NGe)#(x5UHq+lMC8|`kw!NXOqhmcEJ?0Y+I!+Quq zG104oUUp;73bm>%BEP2vC5V4se@Bmxm~U=Un2>KckJs1dEXJ~5!?t1z3!?`T*Wlrr;Y#7=7m zuO{p+cMr?yfbCL&M-%lDek=z@9^U@&v`=UImeG{+0Ym?_RL_&}$VemEkE_*? z=d-yKCDvq5_jpq;w^a}PK+|$G>D{1J!v&uA3NVy z`tbA@i_U%d9qmfnm1Z69k;jI(gp_Cf{mJ~zhK1wswF}RIi|KFwWth+)N(rOY)vBY$ zcLvU2{8IQtV8*X8g~1B&Vx-1xLcxmxVF^vMQyS495=@KpTDF=YkTKxr5=4bX6C;`RVS##N%X#5iXl z%DsmpaK|0EAiiLks9EEC?bj-=_>-|R87k{d=-v9$nd&)O**FC7(~hRU+c}m>@$eoK z%a+h~AHF81HY&8?m33Y%9UdNLrtw*)AFPXXlx@*rq`{6SBnep=+^BduXR*12`jqcl zt7#nXlOav*y*v!a%*tx1wdPpNRr7vDx`=!3W{ZmV{_TfahnyxS*@VKm>%T-3@7->s zsTuiG+%;v*djfL4SIcWP;bsXzkNj;i9{E{B_i>~%I}MPjZFOp~*1w(VJ2M2)h#z!v zQ*{YiYTKk#IXZ#|D+Bovzw7)++;~w=4zim^7S363Q}s$wQ6z8U%@22R@Ep%)R^f@R zx}ZGezr7!v9-f0Q4}Vlr?l#UY`7qL@ogzU|OXp&UG;`C4hDWOC^Mc5JJF$LPhY9I; zBE`w>9C{}md$}=_?ZYv4_4J{(e@g3{iEP5lif7_`_(59W40MJDgjSdLFcb8CeoMBA zQL9Ospqbcz!%(!aAb%%l^*w#S$#R@p#*Ydfpn>r&h~lU?)(fg89i1haQJ{a9MS3V?WGin z#h?j)p1z;?-*1(!ZhkV!|JBPcEPS~SrEyddVUth@ygp@_e$|!u#%fAhL(iZ0V@r|z z9y;-LTd>)E{C?)9J&Hk5^tNIXDLz-MQJj_y8Nh)iNv``<4pyn&mynaoKX^EBQ6RkL zMj#?8+OzfnmX0C3MLatPHkN;BMPq8Lb? zlHFkYlbf~}YbKHNLh@PkY_en1d6&k@Vx{Za0M;EUjVAaT80@Pe;#|rE`+R)99L>{{ zkc+(L;2}CbI)aT?G?*2!<~T7GoiNWZ-gA0STOZR?)bk@$4-{MxsV_Y-!4(c`sfA(= zZf-|C=-ru_?DosG1jF&o`ztQW>s}lrK$N% zfw8_^WK826D@&0dze%dL^;%sKj|JpiHh}L0!fU&Ab}q+;{mxS(uZ54zso*}(IT7_@ z3U4{;VaAD#QOrCO+{E~be}R>R0%!4ht1ghRsdFxzC`0evFUv+nJU6B1uKl*eJ z+h5_=>{^~fO-+qi2Pr1(*R|UFviE}PLC1zBnbbeZ_!R|uB6$Y8mPv#`HdP5hL2S`W zrQ7|azzNLX@_H+4vzz67*8pGdQPQ#BD^yZSN<(a@fv}P9PL-JNMs_>~-6!NWPOo9q z5Z(I5<2;Sa*PqF@;WX=w6>iH=0~hd1r;e`Lp9SIn!B+Y6Lqbs=Z{uL)wjGMyt=f?T zFvGgjFPG`XPKDWNZ?&j^h>9zmBmI$uX4OTtORc5Z;}-A1Dm{a?HrwSo7T?1VkkXV8 z(umAy@G3~WP3OcZ!$T&Q)t{strl46k{)oxN*$Yfi!fb-p?W>B7u8-sCYUT?*_X4L@ zd~K$$62iM*fuM*Dh(*sO)c*`mkYafF^~rb1Cm@EFGk!rq7>s9$HnKb}-rd{7ZU+*H z9{sb28%Xo9Eez2O(+z6rxlvK5HkAqUM=Nlc&D9{BTTCch;#-#7q-Kj;JaqnYx&j;7x$1PL;u2>}1%O-kRF8qfR2Dx%;diMf# z&Am#v>S++1yhSQka%I2?(FT-&A`PY>+FEmMt$)<7)(TeQ*|Y^7Oe~IvF?JeYjR@nG ze=5bSd0YBz_TkRQP*YMi>}CW<;)(~|hp(;h@Kzy|?||HyVXec)KW`XxiGqIq-7gKM z`+a)*%tn&d5YscUsgIdM^xVuerj-s$_c z41g=UxN1K?7aUW0NS7q95x06T)Tw@at*Kea7!h7X_c#ef5ItQi)=*0s>UFn<&RklU z*L`UHPqx^_*xW^lzs3N$0>(q$uZFn3C+v7lE7$CFA7Q9EyrQ9+>(E=eaRP5=K?aH1xOiMmx;H1xP-w5lM&uV!7PtFTQTUctFkxLM{_*Mmb?zSu^&w78Q{m~bIMXRBEV zv5*!d@vAGuAv51}+VmA@Y%9Ec-6`^r`hwAu6ZMsf@DEdpT*jVf)UCeUALN6HM*|N= z{jpM$VAumD7h~A_@%muOwkqPv#w`pyWt@VHDw1#6dHG?rFi$;m9 zR2jWHd$2;w{a-TEn#Nq(@6Q8T3Y(0|hb_o(Qr*JbXX_7IvM-GYW$B1%)8T)F;-t({ zv`}j)4HJ?`!%A!aw-#V(DvLM+Fo*p2)JZNTM%Yt*FQ;}_jzLx~v+a%+b|Jb&sTt766d#D+ne5jptvOr32RAt+%xq=lxKPo2 z>{TqC&_-K=#3mp4UXr8}QeA3#Gv${?wU+IYc8HGpE>%reQ_1=!1q~eeL7-^Iud>mh z!t#(!pzLo8m-p!0^<6TTGZ$aT8nTz}WeBCU5wDaJT=oUO$i>MVcrl7T8~Gy^!}=6Y#B_yM48Oqm=h&0E>lQCeG5pya z#~X>?cfwfl9Fz!|qIo|qwWTc@b`HpoXrjqKs+#eJ7Yf}zc)bgu1N>;Ao7bOeHCifq zO~JDPdW7xD?>TEs*g4e$4P?qHKQm$;IFJ7Ym1_9?iw8~Hh^cWCsi>)B&rSwrUoM4p zjJ*%u!6|KVz`x&l)t?UD)$5cpB$&D<+Bv?r4C5%{z*OYe`~?%F3B8SFl72_d(v)PA zBR>Y`C)M5gdvyK;F zF8wdQ0?iQ+(AaToy2`z$jy}iNu*!DzEo8LH$d8qa96N{n^P2-|fk@q#f*`_`jmqu? zTri8oF2Cvoi*$z%v0KGwtED{(Gh9a+W;SM#^AZa!#UMljuSzaIZQk@^tF5FUn6(F} zPu{^M;3M$DM44HuXgtyNgR#zP*!Bw#C(gMb80%y2$z=%blI6E5)e@N2>CXPOL}MHZz$X< zkcU63ad44N{0>DGI9}13*_|BjR;D{IcImC=XCeAca7%{^w;3c$*PON_C0ixWPc@ui z9g-$xNI11#8$~r9a$||Z?)-nvN5}W%-W|q@c9HoBYELy zh;WEB&>gV6jcWF^%N3erS4e<6Mu>rH*qFdK zW?Z#p;w|gHd^h4CKKzX<^S^nKC9z-%m+rAXfvQW9?6+XA?zI6y@uXu|LD53K7U=sj``ag=KxH=kB8HM&^e`C<(p1BrYqPIT$(R zSe3D`jn^IRv_eeb_fYrLPZ_};egp=zTEWcf?UfP`B!Aiwb-|XVg(>c}vOa0*k z8}@2eOgSZaWAXXc!&)#e5^5us+zy3>r^njnC2lp;QQTDfsyn^EX%O_INnN;|XH^

flwK*{_ZmYf^zAvLTs>jmx{t=_bXEF$%dd?`dcMS6rGHktboTr4&m zrz)@dPc*Ng>xMn+@IIz$+EKQ@Gxw^)YYD3e0Jp$m)sU|dACI^3Cd&6Ao1%ap3HH=k zKfA2YLG+3wcJs4S=1U>rRKqR>m%>^*e%)|RQ^7g&lCU8*BwFz%+R`xfJZOzRf@8f1 zh4!u6-_|;U3PZ5CxmmMRuOsOT@b+7d@!>YNu~i)1>Kfu1;=QRzRM4^K1`pjLmDn61 zo%F+TCU)!v$@$ojUySPnv`jr-2Lk_6LK;$x;JaN7QkD@9<*9iNDmS`Al6rl-=lYsE zG1y3R2tuo%x$Vx5D@{-VfEo{*o*eGGeFQze z&mN{Mx2#{h_sI;@d@O~*6lbnIZNQK$fl5*@H`1d&=}>_VmJrOR7h`r(0{s6Oz)<

zxj&hn7t)ou@cE2i8{2GbELH^ye~4dU)fWVm$lDMQuVj{FcURB%afBAE>1LY7LW z2y>HlNji$=pN7b)-=tcULY4Vx$ZFtvL}Qi0HT70*KAf@aAdK-J5cs0-y#b-UK_Nv{ z0dO?J^+t(qHMY_$P&acrD(E}sOokfW{x=!8zt8BJlPe~YFPFiA)s|nUvv&t#AaPo> zWu;1*+zlRb@xcCaP&OSb?F);NzQwN@rV}iE1>WGs^(2za7?`wHi5ZsbUoRuC~JqsvJVm7=v@2syywMi80lb7-B4@?dd4LkWTl8x z2D-EoRRy@Orj`}TMATmKQq(B&gykEWN{i!~`g=ZCFz>L~*I}2hxlJ{(>&CW=Wmv{G zBkn}dVw_bcs4C_+)G#a0z4Cmh7oGf79SB#f)=hmNaB{uh+ldzS0WKXRv#e?3EmmPe z6F3lNSHhRBZp>G(?Wo%SJAZZga>h?k8652e`y7jG`E3)3NBk<07${cW9~G>O;}L0& zQ3rd$GCWDnnR0+GVXx9%zXu5Whd6?(#8WzkIhBOs<%PPh1K7}$QuqO@fFhtX;6Dk)A z;-;txd1>g4!>Wh$qqDY!@*>FDBD1~-M)p}2=qsE?zExfnrC-BlP((uam`Jo;oagDI z6VVutX-D0^0*>U?!k2(u?8Z5#o;9!JkWU>gODJNTrapO6JnkZ>F~IPzlH$fa)N1sD zB;<4KGzI~#U2Rkd>&@IMw zUCs6e!I?Ih_){^ekCDeYDrOus0%X4rI-i1fVMyJuYvX*lCe0y+F$U%1XBUj5K@Kqu zmOe-`xYQ{7kTp2GrHuX&aQmb$%w#m>s!@{+R`{4`$w(hxOV0y4UZpBAo%_f&rpD$z z<*LnZ$1Ob)yBd-wrxr0ti4=s%=o zrUz1P_+%l@ntTq-)+9j-)a7_dBs--%O1*3@s$Q^r5(P>9Eb- z;At(z%}m`%g$^ckj6*$Ltpd0e+myGBSvMnpv9e*l>NgahecnBS+ikP9snpwZ}8?Fh;6RMs@P)7>5%GoH^r?y{eAOS_-Pq z!B6b)J8uezUuD@X?_2DVjFPUt5;DLsCX;P1KDTPxC7ZnBhdzw(?>TiQIes_tGDGZIz@GVM{G)I9vhm=PERq2qC;O8>&FK_FYIN0IpQ% zUYUKkF5Du{%=z3^EkZTud7Mj(%|@ z-~NY!^&`y43Q_Aqf1j)q_S}yb-}4@w4U&D^SQpN48hjh|W`2b7Hr#3jXqE9WVd7o9 z`!RFs7KROV2dFg$#uXQCLV1)2l}*czJpWif{{2(7Bb0cmHu}du+9*Jnq<#>)azjp( zj}pGaqc90z2}~KHx}x6h4On4z5MK}5J(^8 zQ3RnW-ba)hGexh@Pr9A3bT?dj!_g0TKBK312Typ91!vxe4y;pe*M{A3IBHaB>i0sZ zqI(;!L@xmwZ}FsO!@~#Hurrl>bv!!uZH7;4^3X#cc=4Q6vCDih$dpFg^YO;vWxxY< zM-8pC6YQQD({YChii5b!j>{UJuu^IbO?`QpSer3WF`I6*7OFkju4W zz&+=g?;fsD)5+iAqU@!Kp6zy zVH!pEIfrqsz1koL3ys>_OasBg=5#EpHY-rmOOy3&%Oi2AR)=xLDgoA( zP%C}VacFL~tgEQ)t|Jelc9Zw!&)Y4;?Q9!*gviCUE!Pkrk@D~BcPesxBJ@^F_SQ>w zI5&*tUs$gp(g~5RcspZd?0z_h9iJ+)OTZy}6Y99Q5?BVVb(NgFR&^~b&vj)hnh)UU zJ!81BzJ|AUU6HxntOv|;23#TX3;Om<>^2^^kO`Lb2V9y-{?CwT)4Lppgo;y0eXe#% zMQW;!1OlAPgqNTFW0*j4OizA(2R@3WFZ~XOV_3`F{djL>hV5I|kNQ60%D8{iH?c>nv4h^iwO z-nG&>5=fOIuFl)j<7$QCRp$*6zjsfIRg&~;8S3--f!l-0G7xTG?oWB~rO*qZAX{O? z&-O?)jXCQ~pw4I79l82~xpv#1{H%KAJOQhPRPu{@b@Yk1QvZ zbQ`k4fVR_VAGOHhk96V1i$1a@kWh&k?g;j@J}TM{TG}(ut9)8o_OxQzS+2Z+#b^|4 z#$vk9?pCUahIqGLIX&Z_n~SrN7VfSu;os{u11(-%#)R%(Iyn+Z3=?FAdb^$fqYiF1 z(@0k~dAnO#tO1II-5Rp_-PmfeE=Qk>Raw0pE|2JFPT)q11>JlDyX*|B*w%D6RfsH~ zc%D=mtbgC^TmrVa{%w+^_4N~&?&1BrYb2L~*PD}yLo8ei>Qf6F0*~c4pKjOBTidX% z{t208xIpE1Z;Mr8?ofD|)S|+A$YB-9tX#&v*T$U)Y5Q*vJM$r8j#0#P;WvJ*JX`~! z9pu+;Np~gj^Kz^MGUTNRG&)1Z@}+q^%Kva^c{NH47s9@XJ5_hOzvwQBG3pl+$-J6Rjv=}w(!hUd)_3$i7(i}y#0V^5Am9OWDp8kdvf zi3W%w*W$)20>#^CVYUw9Y9Rj>?jlB0He3RcIL?77U!4`aY#VQa`yu*+4k$6%5KP`^ z$XActpLb1CPwY)rA=X~a#vVlMHIz~jR>tG?LK`*JWH3rjE$#nhziooAlQA^#%io^& zkRnO~_TePXiN_lIKcX~sS)<`ycw07F3(JQ?PZfAkZ+W9Y1OMo}sICI9SySgYu6qf} zQ6OIU(|3%hb$&;?GK(zby`jJ)Vx8*v4Mdc^SBUgXO_Js@Lp}ib+0Uz{doDjpUEe55 z!^}s(W1_X=Jg4|O?aHfXph({BH}#nb?4o#o{v_zk$x_1>e7T+?<@Wj#^wOpD#h|Rb znrE3c5eF|%T6(;*#P|LzR{vZ3Hv~|NSeN_Sr(Y+U6mXP+CP3yD%OrOHS$8 zJBHc&-AJ4j)Ypv1ZpA<-$TB)t*{i!BS+&`TVZ`WJrA1E93&BeVj}x?zK{;jrlmT9Y zbwZ38*xOvmivg8CBNx4Kfr0O0F*Yr%gm2T^B2et~;-p>;I`#MmEoo@`y3ZEsGmC&QM>(&!;kPRrZVQ+m6HGO*#%x(itVRM*P6;|xs=gr2loEQHRC3*zBY`CKU?l%+PvR+ikg z%%(IA`92OFx=pnMay1NbF{f&H;jwb&E8BTYdKr0wI&=yPU~96JP9|t zfFtPeDvDnD<)>m50k_yM4v96Im(*%R z&_Mbzg@h>>NMIXPT*;na@G#T~&BT^+bP#FRUCPq{)^c1a7dY}Ce?-KU#%$p?@Iulx z{xTBE^!Iu)&-F6C#=S?7Tia!*r-asyn4G%GT5o;;^gLtwUflPLFuzwf`Ih?a2~tPQ z-in>))D^Vu_vPayTJPG_J2xE~osu>HVcQQoc0~G;=V9#Imqom!Ie*fleYIY6Jsey@ z6#Vp_qeu?E#$#?wY#(%aCT5Mqq-6D%^Le2|yz}nyp-TkNdHk~+!}YpBbzO)Z&q9Z80n(%! zL=#UtlsXQJ&mE3|Xoj}ZckrEj;4tZr#&Rx09kiJ&j_aGB6<>2feJCqm2g%zIywLWF zI)Q7H6Y;9H&~@MQ?6cI5zP&w;t}b6S(q&&u)~FnG|Nd4)ER(v5>xuAq3Ow^iKq~YzceDRlj~6zZuinLty~ zK`!g^0vBU!OC9#@DYSH;-AYNTWF^0RI(b0OOX%DgWG$?tZL2NlUx!z-+%U)S)90Qe z^_(NzbK^C*wVpp$K>XXeHlmQp7p26UX3$=nx1dtEGkr+!qkHow*ku<_y;J{^@Qd;; z`t*9A@o1~*>6*VxjV#d>)mg@@xi%UF;m=xP%{N*d!1iDcHN>9aFI!gYDO8=$_0!fG zoxGgDb1!ZX;|M_H++?)ZwtIwKBguSf#Z*gk^%$b`Q- zz=9_f!7XJ&auy@Tdpr;V1A5Of-IjwZxT^2z@D zKKkTd2UlQs^U4xW0EU&t32nmO%MBGfZ6ajw>A`OG@^4Z!dM|P=iubQ>m(K1%aCJ>> zX2ynnPJQ9g*IBTio$+i6RmzXCNh8pG{}ZfTNx3zLMG``^h6cja2PNuBdC>4U%ZBmQ z=L8&!fUQG%Ga4JOh41AW`#NY8qZz^{R5endQM&<4{wMtv`kGcr-t$ZnOII#H4bC5ve3miGHX@{jCy9}sRS*|N#(bnDCa zHZ22dUu+Gr3O@2#zb&n9h%Dw~Fc8L;ta9!Lv|kRsg6$sKgsJSG$y))XWhbF@rr+Fg z7uQC_6KJ=68#cs=6ebLRmK%VyTT1RH^_8$usiCDiSn@I}FO)~2e@kdVb9y7}HQ_&k#W7rYwMXqec&3vFP6**>8{z9p&}hrd=gEXN z*57375vFIM3e!k%(cA_igd=#$Iv4u;^EiwBu#2>|qjGzl%g@*#M2^qx?7)nA%>8@hgD}`(NY>?7gx`G~atKgrZOxCMBQG`#=XQr8L zGpNPcjvGpvU3I?=h{od$;4FzPpQf$_ZxTrm2iyC28Bthx`Q3JoIAhU$Q9w*5Cum+~ zh28OUo*WG4ic(DrsnSB`+&0c-7Q7dbvYurKAk#MwWn^E`xHn?;IG}u!ZqOvgnaLcr zj5Wju?aluK0&2G1#W%74#GGc+{O3BDyoB4Zd41caOjm9;=4#m0+ljkLYNGIdi7yA((r+fJ)2@daO0Hh3 zXe&vyrBX8c>BbM^s@|(AgScrdSaTCnmnp3Y9&D17sTJ@99SR!y`85-W9cfej4hRcE0EvQ$Wutv-u0ri3{-C z+KKp;*wAQI`FIamwJ{{`srF;@T5rCEWBUnpdxpXYP^p)6psd8~@Bdc|U^XtVfnoYz=;pc#QGMGfbxKaU$Kvi*vwkjd|`z@A+j~xW;9{4)7^`0=+^E+PvB&e zWMESE&h^@*c%{w#P`L>=QiNU!B4WEext$#Bfy&l`WwC`JD$;MW=R)V~6WwH|(V3S> zwv<%hyO!xEKoI?ntqV5uaVGuKZ~m>W#A~UhS9YIx<+?kA1WD?Dq1jjkt3NfbUAC|6 zX&GkzQIxfNB2OZ;Vcg4Up^}zfI{IMPwNQ*<;%hR^oBERl{GvYF4&|>(&l7Nq+^YfG zomt%PFgBKRz2Kn;8GXa>Z6a z1FUT?ZUF1;*&(1$R>lzYHHg?PGjPfb%=gl)>#oGl2mPmzDJ^}5CF-bWMkBA=*>O7| z^3DHQI;M!hh}Th{Ht*EbALi!e%Dx8r(V9P4c1{PN2%XGE%9ouezBo{dC~Mf9iahUl z{7xau)6XyayVj>kZ`?|eoPoTo@z{>sTW{JbP zV;=_%Y?N-|_P@Q~$M8vW^99kf7F;fM@m_2mS_L;ixoeE$hL>Klu1`|Vylxwenb!Q8 z_k-$%W9udMl89CxH?1@l`XkqJ(S>~#Sc z+ISR)?~=$T2CR;e=A@)FJS>QR2Hsf;>ntYt47BC8HyaEMNNZi}v%=5bVl=VwUnKA2Vm+PP-zGDl z3CuU*f`el7Xm@BC?moen#iDB!?WHryJnYa7CiWjxvb$@gLszeE(6?!T97V6JoRw=g*4y1T8pEIv7z7TWbtq-5=_M5Ej?ez+qv|VR9AE8qSNulnnGA;MSqKOX)jxUGiD0}*KohkFc8i5m*w&46e(yb z?USt}m08#X;&Tn$famHQZoIh~u9NjPO(Po)?4YD>L>j0js0L#O z9dnZ9Pan%0$}?6nN!q%;&-Zd(a(~`Qv~Xluq3b-ENN{xxni3?}dZV1+epI76fLr3P z^cP5W!Dm@+o$D*;-T6?GS7yJ$pd-CoV=LCHU;1Xs9BuZrj@?hQ@tSbS^-9Jw@^2w* z*HSOC-v{`^9!#ZhaD6@^3la#YJ$I`x!@MWTrb~d(+FLYjPuFw%nWJr;S^U|tg?gbJ z9!qvT39$LSVY~`C6P+-|p7z_OwuY>Cgs~4O8@&8nP(?uq+po>9W4eFX<|aQ_;lJ!T zMMXZfb#WRe^@FGG*C$*mrrw=`6WkwA@lw;a#~jI(KLX75>5a&_EU_7Roeet6&~f-49>in)FAzI~M9Nr8(W7|x6z!BVo#pFX!q2UW%JyT6LKp_7d(_z( z9rlL9+i08dktkW=c8OdF$ZuR2ubSEs_!p5Gzf0!zvKhe*|2(FS5CAc)|8KiMn!vA;Q;XzF!$*DEjd5k9m!vW4 zBtpiZU&c7|$y>}j+S*<|-t;R68I%r|ND3|8xlEUQ0VFDY=#OL20UfhU7@Q=3KZ=mQ zm(cH_#dM}mNTNF1S?wI7g6Q{x?EVawm;>f|DwJzatw^xCdVNAmD!(FA@?A#DqIs-TW9OFxnb**N8(3%A|5LsZiV&TCrJ86GY$~IUWUfF zp}aDYW$~C`*ueEgUEAYyB9S?6W6L52<|>}aouIGxcW2clJVE#sxE|y&E*^ZVzdB11pW~k4N!@eZw%ov*sBNMtV|jY|s-mXCiK61!U`a!6 zRLc{79>qP;i@!OM2}$wy5I#fgwd_G(CF$3aW-xH-_7i`rx=TIp!oSU3Ko?EKPVI8F4o zsYa_2c}O#TqZw-?HABZ^_kt7>mTIy-a^<`B8_5$!X?DUock@|sB{0?~w=`d>9hg;j zyre%OoqKh6J}ul|6Z|`QUmXS#QwrvLEAPA5S*K4r6jwWr{=*=fpea5}5@@>eo4A;W zrvw|nKB~IjaJNWH3R6?l0MX^cN(+`1HzIaO*wvjRHJYvkrmspTfCM9N>Z5;h&L2N8 z3zba(&Hn|0so=c#2@4AOb`7A@k1K|mgVH}IE}B<}o;`Y$nVwu}!*0!0eAhsyOn*cK z?Gr_5oZnnoXEdYiXTp5eFE!5Xa4RS(Ly?{Pt*3_JHMO@z2Lc+Mv)+GbKDcE>2C{<IHzeO>_m(v`a5iU~!zuale&{4+DkD{8sB#?Zu_WAt@#FS(p zLQl)+ls20+51U79VXyBK&>AgJirLiK8QsMMWndJ$+}J~oLi9BSp`)athUbxT#$CTx znlse7Ou4J5_Du0jsq!?Uv;EwcB8;+01)oRL$wp^t7_#Vq-&rorSzV!bgM!al8HT<; zKHbGVA@RU*StUN|_XbzyZdkFRCZ`G|h|is5_OE&1k_DPIq-PX3AeS($#{#*je$))Kw#Z(75%D3V0_95WNzVcj-W4>{Hp zUmIV$9sg+fcJBTc!d>}U9b94up5m&v zm*V!=HKZodo@p#{F8Yo4r`t=-KBU^2dbJBRLC2C9pU(jBtHp5*0~NSH+Kh=utj2<} z(MXaf&NSKuTRb1+ys!Q-lnKntt?s5LjQRflzEDwN3$5qgs=W2> zC7!H0Sl0^XGK-YB#xcvItoe7I^MD|}$=sqT=KC6pA#VC0Ppm_uu*SN9B&8Xgofdi> zyx~h-2WCb}uWnKpZrMFeGfLRJ-dKJi?9?e_rDCo6&qw-+$l2!i005gd`|o!>D`N_8 z7G_b4t)D4v-1+$Wup7>3wGiFSCmHImd=l+hToyea)HEA^5A|KUp1L{#<2vc$?ZS{P zh^}&c-t4(OY_)&foj7sGZBdk1s7Z3gkW1}ec$so^tDsKlT1l@Hx_kHy>sgaxJ0&d@Cl{Z75EC-k%e zelw)HTuA~keK%=JlYR&C5(>5yoYh8b%)28xJA6SnjJlRt0m*F7f52=c+0mX|V#I^0 z0Bgm|Gkn8IqG;Jq4u0MfR;j8a54HgF0Dr+qGRwq9gLAozLvutK)df_)4Zw2_gIBlx z{jK)gP6XUP$j3fmGH@;#f60sdNMfcZP9rdKyOF2`^(8wAJ-`8t5}#0vT?KqcnjyRfHeIdp3$ z9^E7rw?p*4v+N(>E@H8x+dhQd!{|mFQX!{oyiL4~td{x|1ih@V^LFF>mvd;)0NMq; z{g}T;vmEOiL2Tavoo=M{oZrYwR4QyKaN7`BRD^Hm{Kk21Z+u^Yg67<+Ivp*&+BbO7 zL&CoBW?pwaOb=h_9x^z59%&|1MJSopL~c?I|1@vV>0W7iu>o12>VoM5gk zqkNuz=(yKCrf@>h7d;LH=ymSFh6f~GmK>OxNo<_}uGX?T$n2;Z#k=$u<3)FHBmlyi ze%iszXvKMOZ8+FJhs+VKffy)NzrFcfs*rrOfGUUZt4FS&h|e5VHdMT&gDl_R`x$7o z{DeXxZw!d)iSlvK=IedIT-^x0pns^T9u{A#a7+**7N3?P&4@uwFq*XH#qsjWg(|RC zj79&qsOIGuNtyjugqE+JvIKpf{U<44E;Me zGesV5>14%=tkp|ave+HdH%fHzh!QVhx$eR+hTND)`Vuii{p0n&!7seu`JBhgATL~1 z4SN>nFt9s1%_LdzoOY0-%{1VOEI1(BUceE;UwQzec^=J^wBLF)ni&1)OwXP6_O`*{ zzlu~?G}X4MDLqk_jGP}-TWhcSCiUE|md-1PL4pm2+pxxrYMB=gCrTfd zb04R1KXRZV6Y{&<*4-B~Y1&9t&~$Zt-vU$L8$vh|mfVO!J5&&4!`ZVG_Bl)##zPPI zeEh%UU6{}aH2DUZ^y?p7-tE}x_|R}dU}})M_V<-SZez7j%$h@^c9&PIbzSz~nHg2> zT6wl7RijUWW0tTB6y%PXgRs?rst7ewdIt*T$``+GVbS@5wDYr=Ta{MNkrzAcCn8FI zURCR|f_d_dC8h=0%{cCcznY_#?Fi-VfleRLXd~^%W6xN*VT)SJlsEa-I{1OS-tcZp zksa?lyHh}bvaW%lVV2}-Alv$D*YIElJT>&iO~^csBZHn1tF+3hKx*aP`;ThCTF)<(NM*x7+6di$<4wL*t{=<^ z&B*qe&-?Uj#oHHU*^y-;HpmL9+t^f#?+SLXDD(Qh&kMbED!%SG$MO2}@Dz}@WX(l2 z)&OzQXAjgO0{<}f(|&WoPV(TT=@@vv>Ahd5j?p%}>37@h6CMdXLmb{Cr~f3s*gTuH zRYhi!?(lxK+;S@I;?>~Zba=01krU7kVe>K*aqinp=Fs><;Ofr3)it{cd#%;XjTKXP z!!E|VjXbSD-P$?jb>-1BQw0kJem|D~)60v^n_I*vH`=%9Db?jo0k;rf4eHeR8_Vtq zTO4?l?8exKBy_*hi|}Vwgi=Nlzl7rh4SMCG_w`_wIb@;Qq;EyLk4Mo%=FqvtTUgn)0TGE~95^TzU&(3~x)6_5b|$>Z(# zyw&2?T#$$eKW_=SXYr|BBSVtF^y8~?(8!PLUS8;ov3T@dXU`w+q7QY)N<|1)z5Tl# zS@*i3v$ev$jV2@wsNYM6ws#AC?l=F0MCMG-lZbq;_7H!0uy#D-A_)jmUI+>5!f5mB z=w>iWt|#L9Y|&sfVX+Pau#zwgJ#Ue<<-_9ujEF&SDPboeV_F*>nWl42B1hdld_#TK zepT~J18@h!1Q|j$lj8h+oB+8>1+cM{sWi@gc01ZaDz>_)F#lN4axXw&r)9@eB+Aiw+*|4} zukvjrtX41zY6LM}x<+D8C(;zyd@uH%kR@RWEmes#NI?_*frwVCoHzCT3?`&a+StbA ze?e`Q6GWM#?7@+?O_P#u+OL6P6wO>IMUa0gRs$+muv9Fw+Jc#YS1R6f-LYUmOlcHQ ztS|I5{__Lh!sHsyi8q%$N~3VnG9VB!OR?ZEuLw{+gtn9(=^x!PRrRxwz|f!M!u7g; zc>R++5;sn(m|SGt&@jK0F8Cb>lC=zDV=w3#dQjg~wk2b`1lpPrIau^jcB;QRH27Pi zA@0Rq$|~d|jlNA5*_QYI`0BsUE-?wd&RB@7*v8dp8NT;_^09Ybkkd zL!lcZQaC5yY@vCA#%HDECjS=Oo)z{{-b_i^6dvq?YFj<__X7sR1o;z6I}>xE7K-l3 zKBIa2DqqcE&}2`QB>mximuvxasz?^BWnTNM%gA(Rqv~fP!T1^f=IL2fbOIJ(1+46c zqBW4|vuf;bmuia{S{&`zgb6!y}WX8>7bq<(X$^E-*%oCs(FvJm$7h3fp;v_KqtieecyMs-Rn&!5cOzjd!pWbS8g`DFus zOH{>BEhpl+WDfZ$v*wq%ysvtyw3ZtByD~*;;BqAAK@jT4u~H5Curz0PXATRCwl#|u zoXouh11bQ6IR;0>k;6rQ%Y;OTPsGEB9LdxqRZ2`+Ea4bwk%Hp#x*dK{mUH3n_-1$@SxDd9tyD{o9L`;|A!jB1^Xm;|2>6(r%cwQsUduHEO!h>*_>n{pV~sy| zZG{Xo&Dk!aqtQAbur4`aIw@%A#2EqUxi!XkS`+K7(R`9LCz4q)4J7YJ+exFfgN(E$ zn|}dU>nuDi2A-f$2Y;c7V4KN22|>4Xv`qiI(&(HK@#^fG7dtDf>H<%- zFPC0FI)h)X<8j7n=3^12!KJr;#a^)0@s`2Oq&#{(BRGG(_Y36LH=?P7T+s=Mh>Qyv zb@|K5Ul!*;cqx;iw&tPsoZgiFZok=0P=VZbsbRn}L7(AsSpy_M@q{AzDCf z#jWVgPvA(1C$w3ptM=_eQzLIXKY{qERCFQ{-TwRwcT+?|0Vm5Q#+Z z`{v&2oR`Pj6vE(fluYpx*~;rjND*UfyY1T@hEnXggpJySAhcgX(O}qu*5DA(4&NbN zPcAq+5FBw*mBmwyvLkkPp|e_m(lT5wl%3~u2zY%QbadwOpjkf~np2V<>mU`I)uM4Z ze&cxm)FrV2#aGQ;NWg51D&LVFRuq!o3en#KYcbd`8MIg5q4WW=kuoz7wpMK5Dp?ki zht*@&KKZ-R+L6U>jXoLya5|EHCcD zC5f^;#vB9JFdgDRq3{xU&_RLE-<0rmZmu%J%FV+j}=5-D3}d#d9qspzbyhVg0ep_ygJs@p&@v&&;dRFZg4kO$BB9G z^PFPK4gNp1ods7NOS7;c1Ofzy;1VRb1b26b9bALM#y!Ck9D)V+g9mrF;10n(xLa@t zcAN9w_x^(K+iM}S_Dpwmbxl=Q_e?*gW$5VSf5H^DyZjOtD}4Ss`lD2RyCtjNF=V+- zafm7Wnr7Bs_0fl|kt(*zjGM^N$>P(Y?ze*~uphPLA3vQranodW`R0DtBp$)^ zSIFOIj~=Bq12ImT^4;V#61jwTWrf+FS-6Jf5zD(hlY9O{3sSH5L9YB~bWQu-iXONcOi?kmLbIYm8YOMOQW-HXS8sh>@FC9A%^H^ zn>-vdYPh1D$iOzwj2qNC9E@IOd>wfncH0Go%Hd=JGD?K~=f0CCEdsNe+<)8+k3DP6 zIO`LN9GiXFx+2*63pLHp=ZS&`$~gUT9L|Osz21}SH0oT;ouZ)G{*VeGoUMES3%^gT ziF0IVL?w{?tYvHx2QJoFAOImva-|Y@?EGA1|7a}r>4Lib$u0YhJ6W95r!_kR?FJ%7 zTT7DTFhgtpr6tD7IyF_*k{sIdfNvjo(}cV-HcJSPJKd~0ULSZ)4wVMUGu9m|=r5$s zF)z-4Xq>5xoO9P?H8yaT64+E8Gbp>^n#^WqpycLE+-Qc(HQnH|%1VuGEu_r0K?8N+ zuEeHsN*8(j(<>X^VRcOVncZC>3p_s`1<3tNZCot+Kv#)~ejQL$MMn`S8(2!~#AnpfeX z81jXh=qEVTu=&S194?Q2ax{PuB-M)>#zQXN@z$Ms!kFw%9bjEN52Vi7p%m)OX$)-^{A1`*J z>&lhgf0>|AlA>{DYqA?V5NKdOVLTMG&s@-@OgIv|mXlW+_H;j}W4FE&rprS~*pnYtF%`6V!c;OBnz0w$;F2-bJC?}Xom65(BQYO3 zSi!Q;71~bQ<%ivcRbYP61Ra*#BuyN!uDtLF$-{2LZ@(_>H+afcy3L zFRSxpE2IAJ^ccZ%3r+&gkymva$ zdWuAF=R6lChF3yoNS5|~&8B8_wODO9+IoA}7SmvFe>1sgPL_CZ`pR?w;l)W+gg}tu z>)muM9ZsD)ggM_z;1@)xEee+pV!|UD=)64@3~p%rtmH= zRg%!piXeQeBX^UHQKdc*ZD-b)y>HppiRzU~5eMD|TkE!A(!Ge^yMXK7+FEd#;3k(J zF0&~(zDCH$C23zeI5m2JBZF!8!t^!Y@-Gx) z#Xl#Rvy;$qt^mfzID0&KK|)HaTBPS|o?9%&VKhOE^`C#iv1Mm2FV%m)LL3i}b(Z<} ztmj|ZNU__||9chaGi>S+^8YI(gj(TQ>i-@qCOzL~|21zrc~4_(cT#oU$HK9_)F4SE37fUdOFY$lhi_Jz^>RS#H>5T zbwvxMtFabRCY131Ho4*SqG$8uHUm!BS5a(}T(10VgX`!x_h@-++~^a!4HeUCpph4w z4znuBxfl4XLnjuGL6&m4#Q!!7HGBP@`l{WP1#GyVa-Wn<*^Yg8b#nN$X7KlM$M@wc zJ{j^rpkC+%agqBLPTI|P$@2_z<$N{qe|4FqmV4iwUwG|&PspD1I6P+4EF6=4!i_;n zfl2{nk4WSQ-j8WJq`K1-_<8RdgCooPuRaNtj5wMzOY&Jaf5rO^up=Jw!$fJcY0X2& z@yx#aI&ss1J*KYD?bEo4w@Vj$GAuGW&g)P9xT?wOKg%KqWWjrblkqpG=RD)1W|P4w z$rvfwFU~D9jr4eWByupNt|INB#}{l;Evv*#-CjZ5D&=2Vj5>0kj&!&$dSH&*zn6fq z-b+ty-Qj;IT)G71zwt%!btbfP8-({%=OX0^`u3C6^rdL*Or`a<0~(cv+Jnf9Kz1U? zPF^hxLfV1i2;W(uP5W1U7&|+Dl^J8!pt=|+iq2$ijEBB11B_+`8J-|5@O>MMm3LUrR?-$`!^4FzR`qQVYMT^fMYUW z`R#6LS=OY+zxP#!{mJ(T%vI6JVEv6w&RG4#U7OUJ=SLR&b(&8gtj`3Rz1*g6Gie-N zI{DbDb+em2+rcu4!aiY$26NPFazb`}R?ii~uDJw;DU|F8G5N#r6%KL z5c=FOv5*5bk557tuTkqcXl@Ln3~O1{2%=k$^M_Qpw|dzR`iEl$M; zC42T;=18_KMWrqz#G2wR=edoE0{?NQ@}2&X8QIT)7!d&(>qiVX$E|8~fiRnORUQn* z;^9``yl+gJJm&}W2*K?V%`(XIX8~$psAqYB%E=^EXK_aPcyYKDmKcnHEH4wKY%yE) z64%%1D|Qh3m8R+GL&K3v7@3GY_q-=Ed0F5)<|tzG1@XYRO;bo(tZZQ!0rQOOXS6rC zXm(mKeE!&U-hnk`KoF`XeV)MyS)#I|uNjtcxx8v*F}aroEq}jryFv7U!%)Q{8q$3l z;aVU7FTjRn32;r}_RPt8T6;C!vbLp?nPe!er;c0S7)5oI5)vSJowY~0c#gmmIMW3* zT*X<3$ET8M*!j#lEl7M;LKt)uBjp*CaRBcPsl<$B`Hq-`Gk&K+>9;kzR8_OKLIK8% z;mykbTd1F)N6M38=9_80qe*{=q_ZKZA#2DZ+Tan*&O4_nEjfmO2JO4r*SYrJ)a}k& z;oPM|N5v4GHARoZ-g!NV+o?l|_(KxdJ~j`;Ql2710=0dW?CUDv(tRoOBWW_v^Ds|7N;| zmJaG9{uS%sQWu02fm`h7@uhxPR2q5PltcKt)`HJ#mS=BhQJI20jf>|r`cJ2v=*lp% zjrPI^R{m1>j@{!+TK^b1xX8qy?a)Rv`t729_~{e*opbR5tgTQ>uw7e~J2u-6aMmFQ zrf+7F$GGoeGaxcjP;%`ZPL~t4`mXTa9@1C;K>4gmZhP3AWDr%y=;g+@EFjTdNyBrl zY4>;hO2n)w!Xv&2;_Y5=?nHEnV39vQmeoQid`3fmeDb0_l`hINn@%D24Dny*-XH{( zmKH&<2ve09EYRS}Y*X~yPEHg56^{;ExwUk**Ot~ClAqW-(95K3r)Wj|BYXl3J5jolj=gT<$)p zjD>q6geAc8Qy!8p#@#5QhL9smvxZGUg#r}3>}K*8OR1eZaSP$~`voO0zdPz?8Fmrc z{{H6($IV_D-R#KX>_%W$y?HgOGpWFAjzqryWw7eqZ~tHu_2C}g;4mjzA@}cTHH`H1 zzC|JTaPlF76#;W6)W6Oj8eMi*zt)rlVr(Z=ht-#_HeW-Exfr9H0rx&q`@)B-alZYm4)Xy{Z!e9 zWET)qJQd4$TskCr$6|DX4Ks<&_BK(~BF5ZuucKlS&*NCd*X7PMK@--uUnblu;C@^D zN#CVyWb5_G$LGBe8*es7c9xZ%BeJhw*~!UP2HB&3RQeis6xMZTPTDYIA|Dd@u(+g9 za7KDxLbZCTUcRtGw+g?NQ#kbBVSz-~PJEgR?l-*-&G9z~x<|EUP;M?jYZR7_5ZENgeSjq0g7E4^K0b&|OLZ#c;wo})TKuDsC5 z)204sqOL1~u5E*Nhh+wtInyg@@@^)Pz`BR_-I+2MOtSb3DKCuv8UCA>89}i1z z_;}qER+m$)7iqcdR8VRHJuo_f8;@-kOwcBoIg?NO{jr&(%ZGS~AD!o|dn^*UU3%Q% zSI;q#t-3hcs@E3~BJ%E1`NW>cV7#i8kH4a?iK5;Y1;;NbQA6KhL% z?NGJf4ff+Hq2WQRCX}_9nl$zCVA%D8`%N;Pm-8Z-CP$FX-+=RWe|HS>2y*gn)O;tD z-f7uJCigBjr=k5DiN7{gSHzlj&M4i#rPix4)^XM1x)%n(zNt<#UZ`I(mCRHszP-ZC zkI6{|z2%|mK@r2x4B8T?Ajjul4!OgKR~h4%4VUee{hAW3JEfi&ZjSm!c_SPZ6sc z)Juk{72$K58ImN(DCia;`i)W2;5(TKcdsgE+BTpuAQl0R8hhB%5Um}fF z{n*-IWLv^{AI7~QwZVjX*6W$U@D8KX1sB)s(`S-5QvRa6enyn83#pn-W(1)xOKwt=`D`WM8Lv+_7!Q9c!r5g`XYf@U1xTyz0A2@?=Tgf3X2~Jq_A#KuTj4?SyICz5|^&5pjCzaF}+`fNhyVr zIEbj4Cvb^#f*xtwyhdEc?9)&NfV2KY^)@i$VWfbbq<1q2jb6yn79Gzl~ zQdy7xva>dig{v-MSKgUUiC;`g0f+Z?TF_9lsqKmWcm}eNdgNr%Uzr^(|5<_C>*fz8 zgaBmvLSWTkoJMLsHRSj0>mJw7Dn?XyZqsMp7U&33G2n6Ihkq>PtbX5HZXKBtM&vuJ zcZa5@rKe+q8(1%wrGN7d^FS-vreeJIP5DtngrjH`9JUw-WBi7Qhu1ZF%1&<;3zzck zNSMp$3D}p(n_3`d8K%jnE^hSbF!u*{G6?CNo!O?H0Z8fkdU}yEt`f24Te2ti`4fEC zguxhZGK?-SBGi_#))dB~`Y;a-T(y;t_JhMU?h#6z3xvA58kEr#TIZC{qMp^Xo(&i4IwNdqpyhvvYsfXq-rfd&Ktq zHK}Z#Wd+%3g}fk#B2g?Dr*I30>68K?xP*Za-5nikB|r%Jz{Tr7y_!MS##)Yj+58RV zIZJZX0S)ssipQUn?h`6EgjT&SPSTc|BBvU(s$xeWS|8tMRpznR8HhI29Yt!6jn|O! z;9E$C4%SPMP9|#3;v*;af?%`6#9Sy8gJ=4>d z6>8Fm` zWl|n*ZaM#Y`~Q8Cu3TeQ8#+LnQizxQVzWLF}U+vn4j}g%P=SurLnQGN7faD z!QST#7NMjB*>Z*vHooWujJ5T_x8{?!=2F1BgnzCJgpP;eEY>MS(A|itz91X!ey5>v z%VC|MHIH9aS;@<7HIXYKFFz#k-?Jz8hxRnS`-!WY{J4Oa?Edqth5aay|H71%p8vT} zkjR^W`)F;Q>U6#AULOneuPOX3z{`isQz%gmq=F4XiP9*tCNd!i+c>?GP4;{&`kNF)UYN*4Za z;jl^)MfNC{(f^uPfOl1#2nXlYRdPdPdfEL#PtVq`?ojNmJl21w7RE(r$p1PuX|CXh z#e>?q73Wywkt9B>uSS0DNtoZM(hWAX6Au-Lx8ssfC6#6r=YHlYJCDf=o!Pq zt4jxztECOgzJCR?I(tLvIJxsNsrrZds;XJ>VTj}kj+Lx&e%_MfJ+aZ@5m{i1a#B_Z z$+-&nnrVpH`7LTR4paAtCfZ+)Rz7}y{u?P%HY>DHsgZeJ0*jrv!SdFY7A}A%_3+~e z8V)ZA)}->&`5-HLHleW}Rlfo%YJqzVfQE1ydt7P2rkfxkdA&B|iCP@_H3^7))LUP-;f zpfDJNJJlnzNuhjFmjmdjNHLXbHhti^x_8|5>^yuK#rI8;;kedPk;J?br5c(tuEVEK zlSh8Fy?Z5XdXgQy{1Y1jd9-3nFZUcXaB>$_Rm)~AIZ|G5bJxQ`-jH`c)w`Eh+NNI< z{LH*g>k^0L(uU>AsN%_2Q7xXS+p+V1KjLtR&9gFU?g+9I=dz*IIP7Yw-FuH>^~GE3 zi_LCDRu7lUuHEv2{=`S?N;J!a8PSE|2$F(|SiVZH7{z7D&|IqT>z8Tg$8aoJW^`=> zRqq6aSN$f|B&RYb)}92s#ymA3$tISv?>T;cv|PS25w4%Nk+qV8XNS2#6S-Jzfzx77 z7~xQC9x<1{eR#}VIS^+f&PJ8$JR$qCD5$GH2|~|90l@2Qh#?OAEinXO$+5zs?|8_Y zUftnSROl>}I`V}B9*hz%K4&3{t54qpq@Z&NGG=KmG0MO@XB1Q}PEN<+fu@tbsWgnv zPFg?AnE=a?2)HuU*??@?prWG2FJHc}l=OBz*D67Qf&XQZq_}KvfB$cJ0U(;Z^v}8+ z+c|ILe*gYPFK6t|09r+=X?QFO{R)dYt|Oy3wXr|c%Er4_b4TbcOoosDX%w8?H;6Ir z1pP`58}~H}n?{Kk3Wa)vPiwCb5)rYG03d@q+?Suc3NLt&KE}C{>#&>neUeNHj}0#s z$~-v&P!r#}%F5Gqr~pS7`2t2jv?Vm`=T?~JtgE|w`^{#o@*|snR)h&aDHz&Y+3_R6 zBxJ1)qI+NxAy>SYxK_2H^d#J2o*w~5@VX`eimkviJ!+-Z^LiFWMCS#i@SezKtx}R?d=I&fq`9gjIQVv-3pYUz zFaFF=++ST?-O(nY&{2Aa@3f4MLSp{D=9F0A)1PoaBJhQU`3QSM=STLUznV*;m>Hdx zCZ6IEJvu=R=AZWVr!h2Aft&jxyDn`jow0xl3={+Zu1XdCdO+&(^|(Ln6CT;OnVQv; zfywj*u(X?CVp{kl2Ghs;V<(!ix4l2oOMyzo`9ek^wyM;={(KB&pXc>-wRy%~3 z04726SuD2#PHCSed@E-Hj1ijDDAR#eW- zduuf7NMaS|U{Z>MXf6`>03&m*@e5M00X-vNMfx#{IP^+q^%c-|Sn~7hk+#K3xcpFNeYo zE{2hp%NyzBeeB;j)#LZL*sTT(n2U#-7?fbk<%t>rn>w4zyJuF#NDQU4(9oa_>6*jM zr5^k}tv36C4Li;GN0GP#qA**ry+2akys zY?zsn^0)u$XtA9a(3RkumxadYF~{ZhOJ3k;alaG?^`bCT^S<=&s1NHgetL#&bb_(P z-Mk8|3)JJ&U&J6-7q}Y?KdG6}-MV48^|be!>V-NJ6P;^+q6!KMqMqS@2Y}G?$zb+! z%6qZh{L<=yPLYx-KwbZt{@YGWOneVFV}9<)L+lJAB*@EqJHl=;>IF|bBFW)diBu^M zd*gv^`I{RxIFT|mBw=ub|NVm-JC^1>L8QhP`pNx*Zb3>M7ee=qbO^08KYx%9IYj?CN zDXU9LeAdBixv=xq;XKRO$jDLCTG(4ZkT<~m(W9u@b2osIfZ6&AsmW*3JyHjtp~Po^ zs+Xqbto!UfmArdvxXan*fGy*Q~1e?E%~slRmmL>V-C~bSC_acH8^d2TUF*D#PEue3y0&i)lpEw(#9zY;QK!9 z0lsTnUJ?Bh>kPq_>4l$X)w0P~I~bVPKV>CE)xO4I0rrGvOJn0LszyN3U28&~9-u%b z0_^2=Pimbq8cZup9o(NvjhcaBxQ3UsiSgO-t*kgu8yhco048E_0j~20ZCGQ1@n~1f{vFb--mbQmmYJz$pLCf8B%C^4Zf>8MpTE^t zS4Y*b@itbLLT{i+6>{1Ab#m%*c>(K7W9;R1ANm@P*~<<H zZbO$!@N88GV7mOA)LDs(Ot{$7k!BxLYies-tAN3m*Vfm!w`foXCaib7k*J{?9v&88 zN=fXR~kq!atcZM18V7k#9|+f=9hTUyX<2;O;&RC3B6 znW2CeFwBY8Y_S6zi#ByYMc2L;mzUl-0M%ttf{%$=8Xp)Km;w0GE1*Zu?9JJdw*khm z8hqMST17GP#7CQ8K54P&>_BKqxNud&W@_?86VCA3SDxGiNLO|oc+5RLJ=>ROXRjlA zdwa89J-85{VUFhm^xP8Q*7gMj1qrbOw-~daTn;0Gh@@$WiK>hHtHKOc$uL1OC)j{% zt-I3_4p)k3(|8J%&fd!xPfQCqslI2P&s}6>>nm@m7$crU4nd~|fg@(dz0th1Rv z6HdwBB1b9z4>Rq*irf?A<1fD8!j#g&OG}{pQ~4o@C?L{N2Uu+-q6T~ej$a3KiF;F1)8pit z0~KknVc;4DCZ-<{4mVUnhyeWXa&o$w&iB6bE9Zxuw(BI3>w2RTupDb~y8FmID$9?X z!jj*gxHq`S`;h%wb35)w6bzfaC?g8=p`N}3|Z0+675 zD^+MY7(Kf%EzgJg3Bg%`GK~5#kcLMgaw#s3*c05U0q!zf*B!$ zao6+$HX4d-*D(%7Cc+3(LK2dP?zy?S51|sq%4ScTIB4l%N|GzW^C1YKZ(oXuxK>sN zxkQE0l2GHq$IAz4voP%66HLL&g-<31W@|H2EqBw?_fzdhNASml zPLtzZZ?YjRnrJx}A7wGEf7}(m{KB$_QY`oL>4$Q1cff_q4Elq&$xd!k* zfbTwZzdGLa2zUnv`9k)CnRzBgBN`3^4&#-CUJ_J+Dd}~-xLl*L`NYJ;S<2!ODR`=o zcOC$#DHDe{8#Cm80^8k1lcDRmzrT;P);Yi@W+QVEKE#6MqE6+R10(Sq6aNT+`9^^6fyyWe%MeL2~NhdY!?lV^vfj%gzq2}BTjik>N5ady?uM1T2W$G>AW z*=gf6XmT&j%r!J5#IAD89{);<@oG&@88^J=ssK`0w%Ak+mlti>m={^A@9snkFCvc{ zgOfijbLmFfx#gsI^YG{l#wjkeIDBtV5XKg4>UtvdxPrtbB(6n46bl0ZuTrZ-m^A9T zZ{zgQg|Br>iL^^YlM!AL_4C|;eaqA#Liqh#!m*a1`>!Ooajh=eXnx4D!P@CJ zm9(7$#o;T_7h2s;Yf%zd5Zq1McKWbve1mfL9}}_hcU8^@MlbfJdqJ;TMr=Cq8ZzQ8 z3JVLbBq~rh=4%r;lIo7&7`L|HG}Cud`o6GhqAuM`xTYUQ|moxRh3}z4r}y z?GXrF{Z@JJ4BLjGwA(iCoe0ASh>&HQhgo=XRaK6Ez^kcq8X6kZpTzwMg zGAO@ZH@D>r2?-(PnB=f^c6R2+4(Vpb$2)$?wcAlzC zt-M)!FL>*rN7QOc8BL^a`(W@pf&@fMMpWj*Z`I)9gTG$l;$72nh8m!*k(2B8qw`y4 z%ajC@)5akYiHp^0BsxjHbh~0(rRR2i-lM}o&hY%~HDV+)ViY2$RkIF3OHfN~Y`Y7~ zMy4!oCA%qUm@Apc^H9#b-D_%7LGl?KQjh9$9s#3a*XHGoG%_H(rFZ|%c}5E9VUU@l zW2L^_=W9WK1SI}$)GypeUgIWq!=76SC($=VXOVNaR!j^u^8;g8L*F`1^iLTbk62gnG)N@A}V?!G#lfCUx>XjOQoRiqjrHX8)^4P>?EsB}v&`0m9 zudSJk=G=IP0|RTMJ~PmwcWEiF8V4d7Y3WfHl*N`yH^{fpJqkpkaXt-3+ykdZy${r} zNL%NheVG$q$Km;MrJ`;-HRkIvYc>m2%-27NAr9Hq_mQAUm$Y<~p!Jo2yOa*pLdH;@ zYE~@@=F1o=8RfO}cc6pj)r#_et3?`x&xwN8Jfg?uN!+4x3noa=&v<_nr4(NnZ)FrO z_|G3*HGnc)d5CKt=1Yo-(mtIFt;IxvCq1=zYw+n<>Z$T@YGEO^=a9t)oN&n~BYZR% z+RV?2N%@7EgvnxAt1*xw>)U2zas~a_SeSpT7P54ZX)}_U1fyfzY&nS8)nQ7|) zFVUX5qZjozhU1u-c!Gl|rwB^wSF?C@E<(4fs?Pa34y|$4RZ#o!k8K^-pTgTeO!)^M zDZYZ}=#e0BW;dIsnAg&=qI8+17XeI%;oY( u;C{{g5M(m literal 63892 zcmeEuWmJ`07w!v+0V0Zk(gGVvLAoRa1vcFwDH75R(iniK)TX3GTDm(FkP=Y3L%O?T z-}P?KIrolnf8YD(Ucd2;RNesa}LTH6tV7;eD-$BHmlCIvsd?1Yqma(VjF zrR&$Rw9XEfAm}cHeEdl5<;d!|o2Txc*9Q7Pz|oXDHq2C#t}W`m&H$Til<7@bag-^Y z`981ligj;^`TES@DE*pzbX?r%-0%HMGk31MMf?&Yl*aAEM_d#i`cBeL_@J8OPQeA< zJC^0VmV@z*-af70QJb{GPfeZlyX${kHkWiK;9B^ple8o3zfy$_76w7Sd@+wPe}Sg- zA|(F)jY?ABBIa*X&;Aeph~y^ZTfRD0xzl02M!B)PvSLk(4>icJ+-GvL7_V|Z;N#=- z`M?bsnkZez@@=U({PO`_Yx^Q+q@-o|G6ZSFo8NIUFfgE-y8-1;h}?mETXOWO_kX{7 zCA^0+CifPIe|8Ph!b-O~8vA(Z@?}dha`JrIn~;_O*wqwAmYT)rM6Cz)qlVN*XC`b4rr1jJ?SOK3YK_N+z77C?==WA?l zZ>Q2Nw;8{H0&_)fT)&A686w}tKf+mU^hS_7@GNOc%O#_|tn6VEH~tN8`to}*F*Y`qTpFz4Hduk-e(*PL29>Nnzn-uqnv6F}5QL|) zT2k$xr-}kU9lX|905A5C3%UtG^A;~&R0tB`mddL1t)sdV5MZ@6TI+AWD1@*e{rvn+ zR+g9Z=z#@nfCYT{wvIfX2R{DuCyUaraTk1QB0b%oLKTH-n{@$k0^2(X*xOD{US3}F z(wlEo$oIo~+kwwLpoT#0^;9E;aysO+-Jzj`L?aJ8I0PQNdcm`UOaVa{Ew{#MMLeAF z78~MEuIQzy3|2%D1~xT|B-zHRL3dA-uVX>M*;!dj@5S!^Vn=dRtEOuy5X5PM@{;C%V>#O^-$H8ytIx%B4z)A$o$wCBu4LWq_!L{?hboJvQL zBrt@-1^Cq7K7IO>ZRg}n0!36lYSK;v%n(mNT=qUh4u5WLZqH`8XwCu5tLsjE8JfCi zN;P{Dp&YS912s@Qamko9PS5b4I84EY?(zY6f)p&~m$2+JBrd^T$0wpR#B49b)w9|g zh6Ppb>R*Q%kh2R5t~L`jN6g5gv8zuKsKl`#>7G7!r><1`&bm-6=&ma~&pdsMoW61F z{9EqQ{ZN`{C8%NMngEy!AV^Wp^kZ84t67lPdNKtz^i!6fLZrfNXFi+0Z6lcFJ2;z{ z`ajpBrsWRlvw+Fk4Ii|2VL=WzVE>o^$K{u9Zi+|;!M$>=l3BTBx9`^r+OUdGz|MTI zo#%543hWH5t=F7UM0PD|i@Sul&`Y(xr6}`|6Z)*Wy7O2i#y$n$#Bs0_4RjhA!}VJOSsS75aj^DkD98-W>@-HiiltA^;BDR?-5jcb@Y3 z^Ayj2BMa1+OXXvq+GTzMHr|Zqu{qi8Q@R%^;}!H6x?2vfkc5>gWaDd2PK`Edd+erP zf;TW>2qT!zEaaFz3w)#nz_1BCA)Lba>2q^)buw(Z04z;#2=f@<@ec=UMqPnsMF3VP7qOx2vE9B< zM06Gnq$LbnBO@m#XLWjSWpI)KNpn!JJ>CdBI$LdsG<1?`Tec@%KF;Po8`}hu87dIO zcnh8-0hTXcj{WF8vzh~+$j6Z3-e+*8@lo&`ni?AW1>Ad@bDxFe7@>mp|6sS^S)(3+ z-H>nq<5X~P_VRkH(SRd0EM;;YOY$A?st z^hm#d5K}A|ud1=V{KN}YV%ixi)zQ(hK|>5_dBI=(&@7*(GMbM52K;fhjxfV(zVC)5 zK2`%W#vQnMcz6b-Qhp1g)D|gF7^G}fc3Xe<-6dZUB_kt~n3tJZkpM603%n$<#s~3E zg0=FfYnAUu*TDJ(z7CnYrrT!pF6E+h!AbWA0yrtiw6L_yXJKU>WB3m%L!V=>f5KhU zmq5LL|2{DvI87j!bq_P^dT=wG;J3w>T6aTXOq-1bo;w(t>Llp(>e-#^Sx^JBh(7}W zVIxZbmG>yFQ%9tJ8o%EGLuKntZ&%%$87-lyz_ZJ%s*W$g%YY%UV9`@#@+AltZ7Ho zea%?_U@|IU<4mf&$&gr7(HN3gK(7qpC!Sp9@9%F3@3yW3;BruRsQa7I@GsthSAJF&r^f+kWy>TZZmA3i~h|yMY5fdWUjCB9)otQu^pMiW3t>|<3ZdebTn|6BZdML#x1M>d;`_WIMc*Mc1l$cqgr4ekU ztd?4_g4W+cB^aSl9_lMr#MOGF$o7tomC+)Tj=5B9NPqM;1Qj&B{$}X<{P~P}Pv7ed zj_Noi=&mf$Z~`j45Rp|`dBj;i=>y=bK?k-&2Q2_n?%E3TG4p5`M-7`ruMIJ~03c<$ zapjtV0pPt;rDs@R;9Zak`M9}t?<1pxlHc`$H57a|aw)%N*29j3lNxMGK*U}Wz(6{j zs*;5#-y0vAYE&HrjG*<%pCYn?G8|>BJs=Iv{w?@E1|U1q0lM{9RaLDZ06b^^5_k;e z75@Uy`<)#b6chxK=W>pIn&mDvT`pKlw5DT9EebOPK?*Cf&g&=kTZcmfvqpz>|`)vP5=yy}Xa`?nSuL{W+JM+{ptW2(~)Qmx_wR7%<}~f@$$O z%j&foxDachc!s8kM<0gPVrUYejlS@9jDqC|kVb$5MKuCE{mZm`!NCy1AEFmc&CxDS zsi`@o0su|GGD~%j2-2d(fhqD3J2Emdl8=~}cK2 zbbmx87Xu#_1S4xsrt`{xuo6Jl&j`QxM|0H@z$-tnu3lp_Bsika0!Uf*=g%KA5Eu_I zR{5jl0hXnaH5w%_;KBBHNq6zA0Kv}d>FH^qXIkB5>81pnK??x`{%T_sA~HI9vKZhY zCGgizFfN4>o8}8Q0eoSNQZXCo`=yDz2t9!5+Fcea!2Acm2NM7e?lMmWgIpV*?&&K1 z$fE(3T2xeYc`#S!0LlVn4fYOWJiY`4+l2GWfLz!e1G?yO%nL9T3J!q3!UJ-Z%|~!s zkm>D}cn-Fe!3a!md~kv=?~LUMv4$@NDp(K&9{gp?JO0yhiUgz%#O0$`aUccdz+MqY zi+82|5Yz%AbSpDJXwl%uwCu9~aapa;4_(!sRd+|E!Yc+wF9+c;^%6es;nL@vopQ{P zBWy7H&j9G`i1-Vnb%1yigXCJ|M261=|bqV3-3W)GFJo>iKlnNN3e`*%?uD2${l37?=k6YaFmtcl`Z&CT& z0Z8bfD0fyc$aout$ROdRoqHY_?DgbM>P)X=5{Jgc>xGQuS29${d< z=<#C8?HC8OS*OgF@>hmXw;fN_4Bqj<#zRLZ)hXfQS(E4&s-aH74D0{VXx?6K^8qY~ zp?MZIBo8mIH^ZH4`_liyY=b=@(MB+dh6AR5aL_;&tkP{w;vEEq<^rHql9lb?qw+c3 z+L0dyq|~WZQ{jPQkjQ89`a{vZWtCiJqgsgtuN|GQ?F<%oblvR2G*m@CZzF zWC$O2f0@;=gWKI3i_xE`#IF|$?Y2`+4!jXPN~fwhy5}6?NNmq~KS?NyHe)m@74S8E z0|Os?*o|QL2<^vyCFbMkxKmEwmhsWZ<#zJjmC83Ei@(Y1@>^`{B}34sU<&2y&&=iJ z@rOl_GWWu7Ye(_Oz#sop!U>5DSlZZ}|H#v;uHzOE(7xd+*tej=5?yZ_uT}AgoUhrK z^}8Nv^4sqsw0iFX2dPyEI1FPBBb3M1+NF#BMQ#uqT30}h5F5a|^dU4B{6C=ygg2uyw7&iZ%)P7RVLUPsRA&zuPEmkaA?+x zJ}x-W?AxfQDA{zy@OMI#oK5C}tttv3BL<6iFSGW3tI0Jg=c1EO@E`5#a}oe%AgL1t z9&`Dvcye%O9G{P3Y?ZEK-_kuI*LkvfEoT*72|nW#cJzca=yO7ajYs?$)^4_eiC9cvKf7_!eu5&FF@w8$1A+Q zL%q~I&TjES7p0vVgkB@_`g0cNbUOEeBB)$6y*6Y#+lzfoW$@btG71W}=aN6KG^uGl zP3u`M;Z2*!IDVWWz9WFLCs^{so5&FI22OdDG?_msBqVr-6T9m9xSIOVZ~x&*N!5rD zkBFCYjhJrXwqzt!KPU?GSh;`zl)yc=K5q?Ol;rm*NAL2GnOK0 z;mZosT>qVS*(Xa=e<*D|Pv1lr$vGEdqlPreX6`=CjGaVjBqt5-d46&LZp#XiaRo@q zalnTB#Bi#Qzj-~t!1l$9!*6)(HJce28YOkXl<8Z}MY_)o@i;-8&u=-HSRMxY{6<%w z@=_)qQ74GtU;9YCU@WE?PI<8Sd!;U~C28Z~xWzO{) z{I;zv)_%0pB$_>GE6qhE%*A<6Q<*e8-?AIu;5Yk*n|^r9@kF5h-iC+P*$LIaPJM;0 zdQzPl^|{iA?Wlrky8zdvVe-240IH$ftr^cCu7Q-gGvVb?bf$jI3OTNtm&(TR411QF z>bJm^9^&@zloMGD^=M+@&D}zUaz}1~&95V_bzk=r_?E&}x_fla>vIJelxayL9y1V@ zRvYt&MD_@z7`D5@a*`VB(l2X*RZ-5M zaAEC=0H0g~uf3fXCja1Pi}q_3y9drK!3vf4=6=~5ymnAqc9D}onP{iL1P{|vwEpGWP;h9mhfzjLk)u0-M08hR@-r`9%6GQDNg!xeXVYJWB2FS1baU4xRcc7I5Kr2me3f1oaC-( zC%Xm8k-g1cvH_Y}r~YX5T_)M$h4=^emv>w3?wz9ghK636czb)_29Tvd45#e{n0D^3 zkDmnOt;E__2RXd(tI0B6^w0_s6?E2+_3pjBJJEgm%7W#6#=v)bYm<9s)GsRnsDF7) z9xcTiWvT?$A4W}h&0o@X98G=ymbvRRwd?$l&i#q8tfR+J0o!h0(h zMz#yvQ&t$Xad4Y)5y)4sr{a^o3}NXDJ_UzfQie_a+0RXLBh zy`N>JzBek8?RfoE&Q-5U-D85$`clclvX8RKT6w=`{CCr~V*cZ6mR5slRp`pX;gI?z z#of00lP}D;W@w6L;;YtzE4_jzGY8A(`RLljwV^aApC2o$pSqLBma=H-yBEk65rntF zU3sb`cm>YEmPUm`vT$iNEENzMKLzUKoK}XuVdB=!V$lK1TPln9Z!bIg9B5h$sd+ku z88j>wguDMM55}g-_Yz8b)9qi`ueH2MySWh~uiP`f>aZS(`%wOpy4Rc+jOp@z5 zAF0#X+qLyyK;x;MD|&67l`>GLu<=U-Ms2QIk9S+xIfT8AA4)L;W#54;RmrvJ-SY#r zPRpjz^7$FTgPP;vEfM$9eM%P%ZoGwGXYMYOtJc7GEUnr06HcMh#S88SZb3Dz!F%XB z-N>pnaF2?eH|C5P1BE8vUJM~cZoNDm2IXj-zc-5ATQVf?5>6PtGV&iyH#eOpSx&b8 zy#GkuYq6F&{va$+(a+3NgSdF)W23us%Y++SW_*6^xxHd7aGPp)MKE72fh+Ka zjDzkXow-p<(z1>a$wFOwon5pyx_sWgDq1~zn`h^6b0awOU``;KhaH*CU((PK6~_^& z_9N|#i$r>TIPKNdEJie9QYT*NAwRl>E2n_fTyof`L;Iubi%PoX@txy%R@D2s`G9+Dj`kr;{*IssL__0LrXV;l?2 zHVn0N_|=ZF(dV^f?TfQ>zf_E$9b}<5y4;Xqm$42_afUWDt8`MhTFCqZLNDe zo(T`uFb-^ceyU&BAfAzbEynx0dPZcGbqrn0x(zVC3@zAw6V+|-O;DoQ(5rS?qf1Cg zSa_R&g){yvi1eAF8KLx9ipY+cSzCQPfyMFs(KK4iz}dntSZK1k+vo@Ctfq`}U*=3> zJuZ=a(4NGbx{OZxnVA@tM=L57t{upNLLe=;vKhgb-yB>}Usy?Sop8(McAhJGqd}Q$ z%tH6s*Pv(dxBUL$EK{FEUVLEX;0$i7?VOU3@vQm!W_VoGA%L`qP0x918kzjuh%n>s6Z<@-2)X)elzq>u+qGcBJ*0d(1?JDP(jn;9rCa zh+u5b{_&IL@Nv8ZxJ|!B1%32vUK!|~a9JdECSbSI{~?gtrMaLx?EkD9N5$oP8^3>vwD^y;-Q~Zdp}m1DPC2I zFAA4zGW~l@TztYvZH7Um9sv&VXpQ-Pdf`Gzy`#~@fuZY}4EurGNu|5DeL=iP&mxSe_kpa@Od2f!OX01BPy=HJd}ytRqUh=O?tLzY4H23eDbTNfv6L% zCI9_ob&w)J>@ilhDq5}^Q_{(PHZA{-%z}-f^^ZYcG2kVa8fe zG&T%Q^rD_L@R6x%YPwp3vP(9K$hpd-^443F^XdEgg$|h}QycPu4o$B|t{X4UE~dT9 zZrdMq8r=8kJ=d0aMl85eOs$N-3%2@bxD?;EmGkND zPSsYrltPU{2-oL*4|It4?wStI!{?57&opK7os>=c8Ml&~R(n`>Qr9butM{n{CoCOQ zB)ZS4yfb-2b?pKWag28#mADYM5TyQi)q>0Srt!GyM60quM?O8i!B zR7<_n`wM%=#jchIx7c6otIT-kqJK8KTbg*gQ0PV?)UA+jxMUI%lg0O>!l$UhgyzP^mO(mDTw6-yrK0@|{?iuNR z=8wzzn%yiRD|1pCzrNK8I3o{rYtfDirr$HXW_HlR0BoPQvF&-Qn<2yt(I{ef)l?+aCV4EkjB3e_x?{)p1D zGMmWRZGS9Ct7qmmEd=FA;^X5FKHTe5MRRj<7Kwo3$)Ik=$7zO7IYx|1Cr`YNZMmwp ziY)tupO=^#Z`^lx+PJ?{5hAYcx$NMz`o?+KQR$WpOAM~% z8ldDCaexaosLX)cQp4BToueP1OWCYS{5FLaw6KeIl@NW~e8*?jlfQHbP4G@`=xr(2 zE>L^tDSDP$d!B>d6SZ=lb@dQC@N$6=M{)knKx!lZf)9g(ds`@$~K`rhkI&NXFlNOqvWqzTe;4{o=H5zVQ8?BVRFMs^DI6FxP71Q0;J|zU9TN>!3qPNZ= zNGmFZV{neh6lz%B`^nYqIak<1HF^&j;5oOv6?qHSH>ZTR*nlHL7PZ^uTDPOfXFGAK z2iN5;!D!0)^I4D~AXs(8+lbJAd)NvHhS9S@(0}fI2EYBS34CSZsf@l9X6L zb#MjGPkapo#w1+ub-=I(cQ-dTFP$>0N?nv^JEMi`O|Whb9vB}ZJsA2ZvkOJ7tOG(a{8n}-m3mWC&a3d;b>QzN9A*f3t zUx|J8Io{O-7Vt>|SSJO_l5lqp?&m8of_}a)F;Q{##3wQfP<7P+jW?i5X^?@N886$z zWFITasBnOOfX3?GF}LRyts4gfJbZixpk3!1Im(U&P0{=-GSIt*hT%@qlr}v*y&|j-VnaT1)p};;s|2ye{M&XaEiD}+CLvj;BZkCy zG4>k)D?z^%^ruQdI}50?z)WEK`YI~h2oNVl_~65kRKflY-)4>FvRV$F2$?jt zyI>+-_-Lly!58ZEL2M=`cVfGiD>w~I9iYYbg5W8t#QW^{1Xh26#@auF8A11{eki^|L7MfqDkcatLnXFWLK)j1M)&pC5g*Yy+xGd0QP@q5)f)=ms zz^`9+^86IudMMC@!6i+fI?jcqIuQkC<3$tTjpF_)Pb}C z(QH&04LY^9AZW$dU@w{C|0kN{)*e_B4^x7pt9YNltGV9Srv%Jl`nRd23#*tKt^%Ee z-py;52w?2Q^zdKa>PS%P6PT4zdG>6&4pdyxAkM_{FcV*ddrP3LW1=b~uk*x(AsKoZ zZj_Y9<1L0;r4)!Z7B*0kE7k=V$n4`QnF zEqoB+S3np4Kjbupk&~|pwEI0#5pws~x#b;S|2Nd_g}HfUAAlgR-d-As94Ve<5va0K@d5_3Hx(_SeDwdC9JJt0{5aT zQyj1$Ab}LQ4U}b|SU!ny02sv#UxDs@2i#tb!gTL}ZbvaDmMj*)F%W|YeKRZwfH(9J zw!La7kSdYE@~Xmdg}c5|cO2CJxF}!>@IZ^V0uoWHGaP#HueDhBjnviqgHRC*!I=$9 zbVLmoz9^K-nT@d{;Y3K_Cl2?c{~7%Ss0`FW(@UEJ=#R1!X*APpT2c`)=>lOOfWVFn zc`yz|M11@9##o7YZ!QX;6|u{uD>z!svW@ec2n)issOQB2(SqY zoLBE-+*2Mj@fQ>)*<65YYNV)?3)3O}pYa0&V-tc8-otz_{onq$?|+^A9NNFiSyU>x zHzqZK&;yP9f>;<%3$B1pzE&;hNFgehoMHhgG<=0sx(&39?CkYsaEBbJGPI=mi}D_k zA@LO$l_mb7GGRzd5|BYQSo|FxBOpv<1~y4-D)+Be*0&#nSWi@xmF;!x?Y9)nErL)F zT_coyDM)~7){MFgVLtOC$Q5)bMc@|h-{H+OUGc0y`PpinW)mmuB?Mag0O1=f;A&?B zEokN+YXdBO^q)RefN@ed=dRvUi_#ZMllmN&^z)kxRWIMl-vzy}j)L>cj=0R0eD{B&6B< z6SNwvQN|C1FV4mjW^~5Xb%JYo!>yKlP)Ka}lbxSmUk2;;KqG$~2pPq(9K?WnwqV>$ zMg@s%3kT`|SC}r8VmzM7rQok`VZix1JQ$-lSj0xMfpF6}D`WvUTEGpo-}ykfvW6lm zt)6vc0IM{@a+Skz$)~}v1YnamaG+B-m_6MDBFp5ToVPM8Or{ z!Tx?d(DH}a;aqJP2vGJFjJ7f;MN)ts;#ft}g}rQ*!Aw9}*i<|iQ-#C5@%tTQk*Ppj3n;DOlOxcNUn-)9g|m);v1x*| z-0%SoJ*|6OqMlURP_&XSv6``~blzIHX>>URy~JQ~$BTJ$7W-;Fe_e4bjoG_H8ik{g zVWvs@SAp2|-~$A7Q9pGz2mZ=X3uxc3Dzvp}^{nE|U_qO-m>p^Zx@LE*G7Of>Vh>qm z53T)_Rso#$1wh_=z!hq0Z7%{X*4O_{gIWND3eiA|g-T6NPiFxF22pr41|*4Lko-@B zY8Z3JLCwL~qV+$WEL0N=V-WETP(SVib!2uRZ~~;YfirM;oHIUfDJz-f&9}RFK7jDS z5>H=Z6hJ|wD&FN3trvC^d$j4c{_kdXiuh z(^Wwa1FmL(IL%XS2!gA_4ew#KilA5Zr_uml`sc0cfn4C?f#Jb$e*==k_z6yAM8rdF zfFRWfph^N2`M21tuiiOIi}UNY)M_ zHXo2zND33g-(mKqU+;b9^;f$ObW?^mi3J0Uhf|{9dip6pVPK6Mn2-WS95E8ZH5$XE z2&xz|&TEZ8maYR-O1{IeOSEFI4CdF{0xn!1m0G~{8J430*t9#IEtg_Nf}pJ8Ao)-$ z4QBcY3vR`tJ_-D8*u7D}j{#el|Jqr>ZfG0`in>Cux-%j@of1fQ#jzA5hDenfsEQEg zz3KAhBp}@YIs;Aow9|_w0v{$k*+3oOL%lvlfMoPXHb+Tyo2&XA&VGj4o!;W9QkpG`dfM$L{s zL)failG5e~sagD%EdmQ_*s^~L-u5(L(-Q`oxvq@>ZDdc;%CK3Id?+}FRufif{Qo;| zXkh!ofBx^i+WG%q1V9D;{2zZF_5Th1|Gc5mq8_ePRD*g8N9T@ROp*KjD68Qval$_c z#C790p>O?fT#+@D?nO8i%Q4`CSAf_wG*`JTIeWXgdb@uSjKy4DU#lFCrg3UqlU3xB z(~7+=A21Z9mNt&cZ7wpAjrywg!9vuz3p{{Pby(FZD^=@vt3TgTZZn~$j?VVp%i1`i z#CSSHuyYgKqMPT23ZL5^j!#S(AdIGEktzJ0Qnd22_4-GX=>5yZ2$lG2O!X0bw6lqE!7r9|84expbN=nL$DowFE zBkn6JUo$55%gSrtaD(eA&pnWb7-?r_W?WlRcA_<99gLZ6)o#e#v>5l^3Y?*^C)yAn z>@*j7SnVN_GhSR=%vV-gx&{h8kiu3hNMsNZ{`2m-yo{*&PdODbq$&PtzK&`uk4t;0 zq7crmu0BT~n|Sg8MzN`41t422>{EQarw1$H1U(YZl&krMT_T}rN{?hNV(C}1ge#EG zTLQA|8x7Y`K1;6-5AN-5+qaG=+-)FZJS;c9i2aH|8f4GE|9%BLiK=xI;jY$sDzFAk zof0Wb2Ze;x^AQH>g3ADu15*UCn~Y7CdE=~_`$F6LZWK^`m%Zf{ zJahQ^+thQA9RJe0p~sGnj)UD4aqe#rX&(i_d|EUT z1YH#0l{RF+&v+{Lm`;_@pevht=qCvvnz5#TB2aW&SoFWGHcC){e5qkg~NAF zL)FJAzdINheoWp+lBPVhFZNUN#lKNFVoXkqO8xfj+vT1mCl;9bVJMw^L4NVc3d&NN zUH{3|hGRz)i;1y&$Rg|Nvhwl+SR4A15;h4rcra9NWVJd4ioKR<96T4T3f}eS)p-7$ zv3Qu3+#7H|xEkq;KQK&r_+ED~g5-eA!Q=*R!7B>w*m9DLfTCfm=RQ8@3~=sKCNLyh zeSS<^I5XAS8h~IjQ)4zQ8oydVI-i^CV2nfox+W6dF}DmeaP_}~^TalhgU+mh;EcKM zD-c*mB1|}AqF%jvr3fSq4cRaS8M+IKuPdA9XFm6kWz(7wV5n-R&M0n1fQZ?s3lF?& zjLq>0uk4E~3m)MjapOj3w>hs_eXa3)ueF9E=@>mbIq-o6)cQ?diNJ0`+l-%rN3T@6 z-V$Vb?h?3$j-9uON`-}mL->Pd0CDmi#9U~w+}%AyH)hvl%J69lcW#&z=U@9p_0Jar?(^Zj#!*Ixy9ZSxXmUZe9{Bj z=!S-jZI`^KC|aE8?n_D(Bz*4-;;FzJ$lKKXc2n>(&wobl$Y)p&UV2j-BE!O-fd9GT zZSL)i0N7>oR(k$mLk}_K1843B4-T&iMQ4Sl!UxB%gTp8(kfLJm_yNAg>5B*ox)Z?W zc?}<-v(c!Fv+IMyw}3Jd^OoPlRcaC+*uT~C&2ZD++<|;FN+{xgaSORi$V&k`JlU zXQ4Tfd6($(JCh*h=1vl%3O_}iyQk-=4eUZ#unVm;*i)eE^49ZZP%Lk5_}=K|EnFpRPRSsWpQgy3v9Yne@bGY3U~sWY%!N2e zAb4hUbodP4+}xsd8GQL|Jh$-f#Xt}!7>~8Iva(v8aB_GShiLw(G51kM97{%eBvbvn zRRp5*=g%5%3ybAWU_?eU*t>FQ2Aw-^@4JYU9ulich-JY~DW>Q#|B?)-tf(AY6B~HB zGz<{q38UCm8PYwOSbS7!id0CQxx4$Z2H0f;3+CK{3(X7$dpiu?;@u;FA`(N}fabn| z9CI(E13TFGD7C;Io?0=S^HEtI%p@C&FGK2#N^J}vsJC`;*#~c+pa?q5OrR05dP30A z0_gwTbZTutA_5eh1z^B5#0P*lelvlfRt80A8r~y$KN&Llyg9kk)YMenIK2rQJ%SuF zNyEm0Q{pEwToAGmk*|?rbT_U%Q~HZ)nB4lm}wiS312{!gQ2X=ltDpNBv+lL}vyClfJmU)XE zk&H1GJyP)H<`i5}7fM33$|LB}+!Y z+<*t!zgmFPZ-${upm?o~sl`z|rVV2WmZNeHK$v_ayZ@>4E%r;XKC5u+LwaOmW1~-$ z+&%a?#^*jbW!PQccX9Dj1&@hw@5>WHj6N8!6=^M7Tb`Jh=mr(Of5t@tDP-EMndh#u zDg&7+V`Jisz5$POT!tn65auslEY2)BRYd|cNyFT;i~ENA&(tgPn2^u*$*>=`L}neO zEhX!+X$}q!9%#d-#tENV7sw#raZ)Z5oEIX1=Qe|C%tI!lQWo|kgt?*NRQRw}8F+&S zrM-uPwfI**<>~ts!6*bUXC>zqoXxvZQ2<3zsaCwBeUp>u8z8P_VC^fE4a&_zl9K-D zTEwuwfpT$>5=0PJUe*>yk6hl^KwGgzXTzNxCXA0oVt-3)(Pc28K|Tx5qG?zGAPR(0 zQ6PiBkJUdDVG=7)6jeFH+XTNSfcU)@a8<2Ds;9at2YY+MR(}y!22=LPzOlOG)zmiX zjf~|hZ=0hh@=XPZ`*aPJ3S`^X=<_pbxCxZ?%mfc=AT=%?PCo~@e!u?aN7mY#7a{W_ z?%rk-XGO*C+mtO^u<;`>j(4fn%PYxwRkyUn;lfiWlthsyh%Lb)RvO`Q9b`@^P$*P^ zpTRVAw9Yv=3)gxXglgD`;6Z-kIB|WK-+Yq-lffsh22ZxhdFj$6s`iDVQWUqXwTZ=* z1}0!6j$(BbQAmq{{pQp+0(jq;v36B_9%XuzAc@?&uZV9=M+9XM7nR*sAnoPosr_Y0T&0y)&?AEtC;8r1ku&ig~412nsk3C-Y>NDtjYfFjhC+<10IT@0O1r5 zUv6GlQZveik#g8S33OJU{>c3OdKiI>O-QJn-kfg4051m&yq|qns^$~D^d=*s(*1Go zfr3@3!idK^ILwqW|K0%aD(kT)=;U;gU~t!N0PsG*{tz%!M!}c~dv7zwdvBBejo%O7 z70iE%C$hJ0Nq)BEU&w z>h6khF)@{HHuFO(sm&~SX;FEs7a>a~n=;1dYO*LvDXEPh$&_f=$+cj=d}xiK-67yN zFBBwxm+j^Ny7gCLzOcc6!?^Zx03=7}Ua628WfaEFbjgqwpMCKY?Gzc56YRD>X0|jj zHo{D238u5XPwnW(39WQSCKvS6AOR;G1f28<03f0Z0DycM{2HgTGp;L6FaZiFiD!BX zOz8?j0Wbzsi4Xex1XPU`z-TL8%;>e1<@2gpGD2XjA$|sVf+G)icPbFi4W_V1yj0*O z^O{Qz+&Yj35UDX{1)6*02NcF-ZM>(bRG4mYgO|5(f4~$zr@(aI(q zFCz;j9utJKTGt%!_#NTc2aK;2;x`; z=Cm5s+uMMQo}7qAcAAm{=O`eBog?u#a~fh~Cs}8JQ=5OyD07fQFead0;;W zNaZHQ!~PQ!bpdISarM|@983?#O93nW0Pa8VzLh-zU@)3pxNw1BZcR6+7q?hR}+)_^OEmV+@kg&n5?m$!5zWG4<5>#;W6FB0C zjkx=xc~>ubP=|xmrgZvUBS4oFm1_9l@Y4*xXDA*tbOWAlsSRJ% zp1{pxS8740MVNkRDaLDDf*4uA2>>$UBk?qrtO&e?XD^b7T{=p;zPtXr?-0u`M3E)3 zE$OgKc{s;EH`;t9jc=KluTC%8piq@KJ7(A}ID3QKbvgPL`$Wl3IQol+&5MXxMz2M) zk&|9@^4Xh{($Fwt-j&w}=+g7e`?uRr2)@+hjP+mL1a&Xblu3uT$30YM{@k`v*{Mb6 zV|NQ@Z-qU3a;vg=lqI&WVuo37Gq&1kZOyiSpi0%MCW64SYKLLj<6MA}O6YT|xQjXQ zQ09+>!Nu<@>pi9A^-tDHJx#Ub#0OmZg`Oc*TwM>sZ|gbz7KJtGwQ#_+xBrtpszENg z4=CST?6$zg#e8(Q_gT14kJbEceP`!S7Qsrz-)&xGN1d*F*}+22D_$W>Rho&_7 z(a1Q4;iVkixyZ#+$Fof#QB}`opYED3zdw$>KG9UW)AOOcRUv)utFnz%h&MVxs>BR& z-jfvffl+X)=F6?_Y_!jLP@czP{;t2JPPAkrr3t~AR{iO^Pv7R2>Z+NQ6mh~~!tp)t zj5?p=S2o8#%bh#a<>Tws5SW|Fy?%k4on2iMFK1iBgk0Chj#%5kRqg^cDEhR6Ulj%N z=J=%Uxu9-=?d6B8LdkU-HJaV0A<^vq3iLj!+QJ8Y!pBF6=C!MHU#=y260=0ByKts> zE@m7b`3Pm*5$r_$+|7+YE>tBI2&_F`Q>7Ml=5XTlsINkIWR%)6v$UzZtezZi4JL^= zbL^r%9+w=5`e?jbq6mqmb?BLpP(*=WcvSlU@F7O>Teog)Ae-p&LjfulNfIZ&OsM{x zMeUx;&u2YNviB zoibyzzFmviRiD*pJIhV}Y{u1Ti0#yic>4%{u6Q_FZt+uH|ac0%E@s<&3w(nNJzME-fwTgir|| z|5zI>N8`cvhvD_J?j1lhgiB9xJn$c(wz)(HMA6%e?c}2q*{;IJnfjG!f6`oE?j=;s zuMt?BALTD^)S+_-JIbpi+^09ZQ?f-pGAtBS<7-mKV$ghR9?uFRzSb>!k9&6~Ef(RG zw{jvX-G(b8@i-cF-Ozmv21}YV%54YCvM{Paj^tjk3 ztO!n%j>iq8c!(m^yox6_H+!qji+)6!^mY2Al20DxAMXu{!V>kZ+nuWg#bJ zV<(}pthPwVM1bGC@DK@3Qj4Hw`vTPdeRg(M$S7=+4f*szTqK9ZmFAtISf6u-SUvku zUOjXmdwkWMr>1IIM|%bXdbSpN_Qm7q13@B>7}b)Gk-5rW4oKxq(_#nD{X}+;6wL>p z$To)}NTWQxS5m9Yy>LrJgrk)!*?GK*yw2|t>nPRkwDp}*|@EW zuK0(4NS-_49s8mq^0Hdvr?`NG;7dfaM8><+kM5x4hU@{I!#FcjQyb6*Zg>hag9yLx zS;>H7JwlD;^c>-pS}*v0&Cl1<-7TqkqPeQuyyP#LTQ=bmu#9W#=+EQL>UCTlueLtB zkfO3CkGN;N>*IvDL-M-dFv$4a9&^mJ)Rqdp_CtI)T(-Q48?x)UPeJ!W%RBxov zDEML4=5zrCmGG0aO@aHse2)OfEd2rFHj0mjXK()K*QyOt=2MUic_{#$%-*g8FDakx zx;b)PfigPB$ZTqZQOmwevl6>MQ8-T|m@2<&?-AF=PIxAuG@T!xex~KbOF!nWT{>p=Uu7ibr-vW-(iUhPoUoGal7!7Ilrr-rx3#so{_O13 z8w5Hed5}m-zpscupJ&&GNB`DCAKm50pP|>h=%HQbuAWqaE=gdkI6WnGUW^>nV_eZi zJF?{Wr%`5qa^NIa^Kqaav3tX2mCL{5l`F~9ms`V>)SlRkrsI|Q<`@V678%1__^BzQ zIZT?nIu#}vkr?_LtR(Z;rMqQU(_>)1d&C9JzS~k>YHrP5WYYHVh~Qz|K$B~XOUX(1 zS&OY(B-v^9$;Pg_hBR}P9o6kqD_D(%(1CLFWXPx-v&+4qjKbt;WnKv_-#pi9~C zi~~i+7r^{}>)6)r-9lV|_^ES%FoB+dFmN^YA@>&ey?A%}-^X>neI0I0?7n_ER@+`D zCC_tlw92HkIn=Ua{<|Kd_&=8g?uQRO4QRuLV9m}BED>Q8IQbv!eT7$*Tl?*%LsDt! z2I=nZPHE|u?(Pt2q&uWTP*Iddxv`s!&s?8Ab+ENWfBA}|){{N0bJv*u!Rb2G*hJP$(oBnA}#28B&d^rz?^p8>@}R~4~t zwb0h~dGIC*{$uLil?QOHIe+Kf^*a83W3Ng_N*^jP921+Vq z778uX`A>dD@}9k9-*&lMb-_>l>e@g3X>TgMgRZ?pUhxMNUW%V%4XHtDS$li?IKW~c zOfruZ`rL}B=coV0&9g|li7&rie!BKNiqjq@9sRo=aTU^jVuE>!%_t&VclncwjN&%o zD)@@`=7z@Sx4ih@_p7PzZi3rR+W2d3O48I!@-CYTZu&!JMvm-z%lq+_r}4}^1e?@U zut6zO4gpOdFI?W$Qv>8v3((tHySg4eN`1x8jMw;)5qoUJ&j029W#{-Qf5?r?5J78t z!NFBQ!QR#4*1`8H^0u7^*wv*&TKnbmIww0J8pmJw(}ey`kME#}rwDeNKla%}HGuK(&;ys^Z2HBGo{XRQC4_X|YPoFyeio+9&0@ZPruGANyR3N7&Q@SJi& zL%2{4L_X9Rqc*u$SJ&bJ$B!w^bmK|hw{MAWx6ihkUf=zpc-K*(%`KnA)E1b19Vf@@ z+@T~~@AtO8b;IeCtI^)jBZ5(vt6$Uk^gAg-7KGZIc5NG99jK7OPG6g1O{0 zQFG_NzA8*%l7~17W512`yKkE(uc6wjnl5eUQyHk@3{4gmOt-do|K`w+8VKVxdE)@5 z7pZ_?Eiev>Q*|E}uLf)CKW%@8Y7op{$8a#&Cz-?F&Q4E7sq21v0&gmdp=mygpPtgQm%g-b0_81Zo!aCCo$?1Ul<-U7R*4oqa^k!>aD(1g@L+IOAoYnaJ zxpayUq75DO(0cZS4l3CmFB1<4*P#WNz;YnI8aBkCLKd4fR6|-apq$R9pU?IRvM}^o6M$`(Id| z1FONj`-Z*g`(HZwXF@mi)%`J#iUgZcn5xtps?4MXJt_-se=m<_!DlSGcS@XYd-LIB zYr_(JLbJWb3*ZyE0Ubts-x@9Z7jX)NgY*9(V}*c)5pM>^<8(d;Iz@;g!HAM-fO13# z3-2s96y$vuAptYX$5X*322w2;I&>!UjUKJ_n+gki?4G5*;@VC({_zL__U4>m^KSjmGL-4_pqlMmt9yEpRRBc!S&^`3*!(Zc_PxZtARt4B#D8wCqujOYfo~TJu zC2KeNFNW4B^fH%qh(tHF3@{=Az`@WO3^xS0J&zN;{?z_Ha0IA1pXY6C8Ux-gOkx?r z_wHZ*_~*}`8i;53{9m2{_L$b$S#zxN6)hQ5`agK^fDqu$|JZ=_?CtE{qh~MP!AJboiE>U>u%-=C-dOI%#gr77n4!wxy1 zPa6GW_8*1;5I(Tn-t^++IV#1W%@bV^4NSo_AF|#5l!3nfN4wqSt_x)Vpy@!Y1?-Jt z$S@TDQv&Zg2qE79LjxQt1vvSP#U8>$AP)8o6@1w8TKyVmN_y_i z0UlPiGv&3PV=gTdphr(HE<$pE|62gGCU@BK)jnYEQCwxw0#=2ZVBQcc_^c1jL;uni zDuA{Cyx<`O_jP{S+1m2^GPrpIKz!%4;bCkTUPA9yF9vnYsXJ&z z{$hnz)p>DoF_e0?LP70~GXV2~)J>OqriP{g^xs=?_-+aCTI`@1j~V)v_wSQ?dm9#W z-15BcoqLZqOybC()vR;%R0Fs)h=D|jq6%n0p)E4AsT%F1hXO#-#Px9*mLG-0}Lwngr$H z$DL2DE`TcTOA~>asgePbA>y87kR9c_CmD*qSS3_HnwCB}Icdnr%KDfK9`runo{0xg z36!xW1B!v={yFi*Vo-o2r0jJ3(kkM@dG_d$js3t-Z7J zJ}(qXz=~&7haU93#qQqj?XP3P;_w?F8F^iG*wPBlg<-I1H}0J;>A|1Hw>U42sTJ?B zbHFqdefcL#SDd7aEG$fU|1|GLzG|g_i23le_yd*`&fH z`hN;>FjF%3l}Iuz(CF-9LZuhj`mYF~#p(wU*md_2vgmK*2>$dvM)U7$f)Ks2(z4c& zQ3imGcbdwKFb$hjn+Pqre9%6VLgNCQ0@_lbF@u)O*lL=&=q5mBYU( zoPS@2>QwQd(}BmY)AgDFRoT$}L@V)s%WyQV?nl7tpuIl4iV8$pSOcm7St{+Umnz`+ zi$w09(h%??zXn#MUDC?pHA^GsfR*DiE)XGr)0fsBIzT~suLW#Cr|x}c9j}ExcQoGz zTHoFF_N}Q4Z2UfdLpGn6Li7 z95D?I4G6V^pkXR>3OY6P-`DSVW^Q~c{}1sB6Bz=0O3QbYfB6ce|Ndk;By{NnLKnJw zp-b~a5d4k5IHWo0DBK4|g^KA`0hk0DghJOU`4nxs{UdY%8X~Y&N1ak>=bIftAw&U= zMMhC*J#zz(Yom(;imS?dDi>@LnDW1D#eJl;d8-P2B&Z|NRj#XGQT`t$*CW^XnHc!d z|67uy^q>Y9O%D%Qaj`-ezoOPNG1)rM1O}_+aB)hfQBM5|DC%rLRRdO4{6oPi=YiIb+FEk8*gO*F?Zmp2&4+60l zX^c7{I3S=v`pn|)@UU=$Ys*FvFxY^00$WNSA4+%G)UbQkj$UGu3LJvYlF(IX73+7o zk%rjn-SfI;VBxvWbkDq;mIk4mbJnY+1W<0AP%J=4!6LmhqffWX{Ezwttk`ux{*SVz z0)t%tKLDG6$l_jTmAV41xVD}Gbc)>E-2Cc5@|O+f{UbE*r}thAUZ7IR z69DZ||Gb6oPXH*Ar5yg`y-!E^9MAv^R1U%;2$Hm0zb8vw@<4tI#1}=r;5|b7|4B#J zaG;(luZLWEyZ3S-i6iJ_#?FO=Fg(H@5&z9eVYM&2XS4qgT~6pKBvT@P>KoP6t?mg2 zuvg<2z`Q|(r0>_=-Q5K4X?d6Qr~627fKOujIqwWcYhlIJ7lz_jxQ+;aM80>v{V{+kw5e_fz1Ta|KF$CCW}eJ3BifQSaUF zPC(_K3mw@azv7PZt9a#OyD84!FL$s&Dy~<9G#jyiXcX#4=h#Qd8*9|47K8Q1d?{0Y>2ewf+sj z`;}=>2cP6FwQkW+{291VgolNWdI5$ofA0Cr!Nv7kz!Zu|fpT5zI1D>*8O8MOYPLh_ zp}w4;4z>5e;==swtPiFl45mQ}Y^g08^=rexq4xTBj${4S&feaF>ceDO3fxx&V#SCW z)miT(TB_>mfJE+vVJd9g1EzG;5=W~M>t6X~_s4t3EN?;yCc}czbw3Q~#W#P(b!o$- z{$~>bl_T`$|Fxw9@{<3rpX=9?jl0YG`g(B+a`JZZY!&ZU*QPoGr01+R{%02*cQ-89 z3#zu@3YstM9ehL&Mx&08(4{jauiFI~qK7|8otx;kh%ctyQK+ zKohgt5x*9>QZuRl?Vrt#1)u?CDr^|^BJDq%dReq4fG^_7pShFczVLi)Vq!v`F-C(K z{Q7gCYViYo5ImrNH(7zU86X^WKzYQPHu!wd<}D_`de%?8)7L(UwbVCW`p)Kv^#5{i z*)ZL~CKEc{e;;5=>9f_ziOKC^@btEfR_NNrOS7jPrzH8L>~)iyE;0CxB1uHf<- zJ1`^)s;Z-!xtsLfE~&p19FupE28-w_DzcN;$ES$(vT zzGLXO0cQOGEJjSw%sii6Xq3=upCec}o>^U48GC(mYX^)GKYse;-we!z^g*A03iN<= zMjymXwY5Fs<;f090J8PBl;XyY7T{!T%~Z`P4b`TBG0U3!Q~sm8DjPNW4RuT5BN^$c zN~tQdDHzhg8DIf1V$>k!;|!Fx7HimDOvSj6fz}Bl=5z<}B&rNzfgZ=Y^=nr@Ut=!~ zv7-)tJ4Siw90isRXg0A0T^HOPbLoyG*C^VKzaYH{2(v$xah^tJ6?ctEgjFkf8U_%b@tx+j?mgbT~UZ-*g?zV$kBC%I#*_OMfY`9d#@$<{zC6=V|A7nGupYe zMyviwOTCqC=Im8{-s=#}mXXyC?*5eH^HnGB8I#r|nhlSaOXKr~ZiTI^8&ma7_CDVp zdy?!>-rlEI=3EVP~C6T0}m zC7VeziVd*S8ZWa^QSAv#?Yj%64%0_ zCwA?Skdf-zpR~^hna8iseq@$u&V76P8JJuB5?-3jBo4NR8Nx;Mgev-|D4m)!^UzI( z^y=P}mPn;N8m7h1DVNmdtxUZQQk?=mA$0ZpRyie->AH-ZNJ=VU%ry~n-z;=g@pW|Z zX%(AfOD9Jj+z1RerFNO2W{v*Bis^Bq=jDA*&&_?Z2DGo(s`P0upEW+BB=x^o@VWCp zULPDkLy~@J&Np6Wn-VX<@ecpUSJ{Q5%$|iv?)6l%@=}Th9_TGH{606=GO%+tc7A1*QzhLtF_m3qPA(lkCIFXk6q^C5+q2vpvX<5Z*?F^>%fynwfDhI3t8pdWV}PH8H>*KOZiwwndS% z(1{@WhJ$7oi>M=mut||##ux|u95z94Xa)HJ(oILEK=;N6eHJos6_ppzaUT#861o&A zk`C%WdLiRJQ){68B+ddI=&yz0-#(QP&yP7?a*LnCf3E-V5(yys6C8NVx4R41gk+RZmRJ-()Aw>Epr8aBw2Fym~M zRdsmHFNr67jU>J0`uSyYVMzRt^cV=Yj=|ti9ZF10+yNPcEDy=(({Eid5*P?swHPBW z4*ORXZd*4!+1&jaSIPwV%!Aoo3 zw#DoU^}_asrlwj&~-up>4Bw}4ypUI62@}CFa4aGnel!*zgO@W zJt|H{@g26cmTiVDl>nmXU&X-PKgMs+u9%*!A75C(KX^Lf7(%6`Fcnb(Mv_tT^d(M& zzwcL%ocT^ZqYUe}EW=1Et{*!$+*w5c)KCg6!UDhByydNU{hAC|;N6%}lYe=9wlV=s zKKP(ZFqw~xyPZvuOB?eRIj!{VbKpDfR28)JTsZL1tvlD4N>-C;8}(VT|@(8;4vB)|y z5rd@({$hG4r%ct==pe9&gO&QBxp`4bSNF_CG&2<-^5R;6fO`)NXxMGuW{(vz=;?rU zX8hUPDFH+hn8pax;rKJSZ)U~NNV*n=wRv9~bS1<8&`4d+zXgYkk$S$+`|8rtwNGXo z0tT9R(`Lab+-{1+>UZOQ57g7idJ%KUrwoqA773W#Uc0=~>`1bZh$PJzzw$H4r~_95 z=8SLVdS9Jx>58Hp)joApe)@E#eK3uofgN0}CQz`+|M*+O`G-Y+#{l3?Hu~a1c=!CV zIZwva=TM9%s%a}19dHKcr^o=pq;FkR)FFk>9DaZJwMx6t$2=*;Qv_Ae0hv!uc-cE*=XiVHQmBSNE1;+x`0Na(f5 z2I&buG+eE=;{|uCeqyVx0&2fDHi9&OBb$So+L&`SA2Ab%fp()g?|GY84B#Xh%euvP zu+XCi-f(|X?|OR8h9teta^x$rw?3Fw=;YvFxN_uMA17C8KqxHGkIoWrFPAl?!eK*X zuEgJ!WwD$8Jv*K~FC{{78pEUf&+d(=Y{YLu+>A3U*B_OwlJdEIsh&JOqgt1n2QG zM6de7A5|vG*fw!;%n4ZGohJxr(Ng}_#XYP<{iJ*2@d3SVDet0*#i;e!!SjY$;m_b2 zwH?xaStmXt<>27kd0-+Gq5zhg$~U?mDjZZ518@;(N&%&Db2$yi4pwFOi#X}%^u`^a zzBth20P2HOS_Abwfuo6RZri6V3;TXJl(FWMfn8>l!x)yIaLX|sscg{`ks^mCj^h44 zp(LJ;=O`y$VevR`8HG?04mzo;POP*Bm;r;uC39!$lK^=t+2ZZ?c@-O4! z_@3(M{OtlwU;Pdya@GRx%zL6mL7XkV#eWd9MnHtod&*4Tqclx>8Q37L8Q3=b_m=cB z@DCU)8C_jVaEDe8AZM}tMfUxg@`{3W;kUv*vJJ^Fw&yits8E|(a>e8iVu^8N?HRR1}2ihDwUEo$x*2?<&TN`MP zfYV%lhks;dmj_`bxFH*lW@OGL%VUJYHrHGQXnzKi&+^J`*tb6qgp+3AZpBmnAeMc{ z9hW7Htg3oym5r=jCJJq$2@uA9c7)uigN%lOfx%W!R<_pza9FwhQ+MJ&ye+e4p9Sn$ zewY`2Q?9~ zSZjJr=@&Tp7t%{EuXtq^G-ZC!B*Q(^kqq=D7V z^%@j$Yz>~0f4keU+m4zA_uo#e9gQHvqF2m6u*Y;sRGcKQyta4q1Wt6inCFghC%CBV z8g6}@nt1sr*yMjR(-_o)*&d>87Ve;Hho?yT!@WEW#M<&B9l;`bsZvi`lNR=^%B6X@ z9v27G;qV>vRh?`U-a!y9H^}miK`U8@$K~P5fqvagGn00Cs|Zm07ZNAPvFoN9$ItHM zpIz-V9O&WoqQX*XP{N2mXmiL!=U0_t&0OW;!PrkFvG3$?9MGt?-;^3&jMfdp;UdT=)#ruh zGZoziy=Sll`a8j()J-586=R0y&q!K%T6}MR!)O_d{OV)4t1?mXFC3|a;zh-JURBGs zX9v6a!aldnAZeMMo16Q*IbL{Y_3YW=b?HV(%j!yUx&7Z9UPlM8w*_Gw@vxXRZ5%|B z_ma_>)p9E*bura)S5B4mR74|XtMS~>`Es$p&|&9nZ&*A~O-V!?B-JfbeK2B?BAP9I zZbeQ&LMGE^VcC5;YNX@;KGaS^+BPD5jGHSkzfBT%?aYhy=lkLJuFzXBg6lM!eUDaM z=Jw8~btK_`p9DPrc`5h0ni(FZ!1M=o?ix-ytNwyd6hOsz5E)5W=@51>xJE9XgS>_Rq(5Lw;o8%_f_S zbfpYZ`=F~=yi7UzP`Y8JA(AV9^qhP$IXW?oE07Jp9{IJ;^*kshni?D3tU_)jtaN{r32Ly*zQ-=R040LKIN!s%wuYIAsCzov9YoQGw?y$U5-g!?49w?TbYJvm zd;>)ic-ko1?=SaURoptCS)uf3tIPFaM_ZeX&Z@_Z801B`1`vg%!NtO*NPf8GhB5#^ z11{BqC~XK%!^9onr@{%U$73at#V5_ZV0*UupKX8AVB|rA5%r-~oJ=qKk-T?fLqeMF zIze7vf2GCAmQo!(xzI+QGed~cve1hfGhHdLCIe8ch0o&Ef4vxq)N7rxUt@S_`n`?cXM(35FVjv6=!tXIy^E@3!_4`&pFBa0DNY((jyo-(uHj^s_V5l#w(|FWS zSGO1a0l1siS23f&Ec`j)@jryp8(&+IUs7z(A`edmqW+4$0Uuo&OzFnW#nPR!w#Rf_ znMN!eX&RYAehRvBeH6MZJxjFhGK*KY!FJ?t!j-!7?vU;!k8j+48}24=y$vguKnpJ= zOi@NsXYa>00KSHdoLe@6Yrg#udYI(+rH4u}l@$8?#m(q{A3hcwirzC$C z`+bFM*H*;C);)g(VBU%jnRRnM$o0vOs~-)qxRWy>@&eWl=u?|z(r+d;g`}>y1uzF% z*iZ}}G))B6K3*(+HlP{gTrxH`w(~6L?3*?)a&ydNH9D8gu-;e+WT7F!dQpNXggGF|=-;Z*Br=!a= zlRenI^qQLPrR*Fp{M0cc9`(A#)B}MsLf7B>8gA|#s4kz;9nmAe1ulzr}bg6w&~RR!KGrK1*v)lrruDL|B^OiA|lcI>3s2* z)#yVjeuB(fq+D3EB@7eHaNKFl)Yex{DYkIlHwqohWcJ+C6DG5mKIxB@RN!nkBLQNI z0&HvdKW$_f?X!c3%VnHo{$=qsSTIg!+us-fxFG~?edWc)n7p6T*B}LdJRwfx-lBy2 za;{3iGK(=TQ8jllaB1&+WY46^y)(}!egKpivB||sqvnlfuhHt|kVbhQc8g)=l)C{6 zK>RsKN^E=M@cFY;=&^Mjc7fwa>&_l%NU38WinGq7(P@qkr{daW!3;2W5R>Yf5O@nZ zrwhr20)GdHRwOG@q1nHkN*1EQM~(?Yml?p}5Q%t~ZSR^PJZUlwK36Uh3?NFtBX`ai zT(z3{*roNTc;({(E?P{cS$F>0+1oQy4m};Bo|Czzo7iJ0+VHMS+#`RiX*7%sm zh-MZRM1$5IHyjYIH6cxmhcXt>nGFTPk&x^#B5H*$Hy~QPks0LHIg0B3}7C$>C^m=`eQtiLm99lkP5T!WQ%e%lfE{yBh}PR zUjiPt0c81PvlsEK_`C4#_2Xf6$^K4KY)H1t$(;NMiGx`04xY<{JQoJJ)rW)7?|IO6 zF}CI>7ASb&@qM;0MS<29nkoNqs>HWFTgHmeK4|(GwZA``LW+?N_ClYRxA(K_A3HmV zr-;%v!VytEIU4QB;Z#y=MjoATuTPLzKFuRKqUY*Y49#FZ=Gz5Ygtl~M9=?1bukA3O zD-`LLXeuR{qL^jHhe+Ta7vZbP!>Q9<c+`-`mQk&<7j$tz~+wr+b1^j3r( zFTARTTozmXl%e8LC%^GE1VWGrF9s2VNSq`7pjgYFWbp9qw}bG;HY}D?#RJj2{P1E< zwP_w_km1S0-*)1`%=D34l-*N&q{;Qe3iPDdgpn0;^P@}BW!p}CK+AMIuj9;D<~WOX zV;}D42a6Jv9DWc4nMykc7rLgk?74`R@tQUpgI&=fX8eL4OoZ&ps#2fGHg8om=o>7&gcov#6e$WK#8^ zO-RUD&#!VD-o8Eg0YYnTC3C4BpwDKZ{^HMzW|hAkWa0=l%m?1Qo!x^i`Jt17RgL); z#NJIF-9oE@XI3$Fv0#(P<#d@#{HT4m*Z|4X4syy(jyH1HcSwGKtlJQHoJz`SssQ+m z*j4BNHas;ZNc^nid#r@nV@4v9LcnnZFOOJsJ-{e8aRgdstJvfxVH;s_JD6sIon{<} zSQKJ^$92*tA=T9#xKZoRPC-LYT7#t3ln65h@v|J{fIZ>m&tn>3R>1uqi^cBM-(ER~ zn>|YAWRHlG8o;+;ebdd^3pX}kPuky`NGf=INq6Cwxzhzf5TL}o>W?cSf(zZ`Uh%Al z^-Ms|c63RM2!Bw-PQ+F6)`QtLkCZ)zUZAX!I%nG z38Rpqp`r7RAf=345~z$rE=rTcu9m=4(!IoC{TPQX9UTyXDZe+rypYh=m7Ez~>;_%l z;b@`H(<{PRHm-)!Gub61RbO^Gx23U)P7`M_^x_diyK7a*K~rs&3EM31W4`C#ORMAH zV2D&GYMW$cLay4)OPDY=NR z#(a(Jm2OaiSVdh58L(nQ7gXvT2zd^9#r_&E?*@fzl`H8y^4N499tM;a)O-5)jQ{@g zGgV$Y8pr*0Hkayhyz#i0_T=kZ(Oa!M2`Gl-@;Ujd>*|tEL{NcJ$BZbffR(Fu^=J(h zQ4F!?_ok?FDsg_kwFaL5UIGI^kXXIN9Ntyg7@_lKMaCl&Fd)3lPuCe-e%ZfPrIRwb zvX&%%n*`PY#c3cJvq`wVGZKC@Kpvvr+C0hH_l9Z~P-Ez+D2X|m5ij;>OQI4Z)&6<< z#n2*H5=ScY>I2)B$pQd_){I=7g5{@mu)sJ`VD&qh5g8gJui(EVljhK$dyMg-1PMHo zg4HW4Qgef+afsF)w5S4HI?Mw^PlZG&!o%b>?fLL6Ya1e@NvI`tVHVk$rNmU3&P(k< z>SVw*;WG>tEm`@T*kW!&hls0|NH?t1<^ho@!{wKB3y@oMP^Tz(vk+LqBwjEtV|Z5I z>FbKL5rs=i1lx;&ckN)Gr%9HbtE%3nD-=3;aZx5LB$VN__>&NW69Zcpvvbo(ejJDR zX->I>CiP7?l_ND#3FcQ{s}J+z92h*R2-6FaD--(XyERFgxP53YpQo<%ha3A~GLC~tJ-E6%{2QngZEQ9xVYeuEy0xB+QfG-pz(U5=W+F%Cfun2zv%abE` z!VS!7*%VlZauoN=95t!>S8vp1zt^C=52r-LM2;w|cDDxE%S}xmni*b|PYjvXE3o)Y z@^FhdM0{0?&FtWD5UEgMApHJi_^XheBPC0doHRDZWk3{CZZhFasFW?7|z~Te)#q^G4xo} z7OB+*H($rr3A~%cgHCsoao=Hu62?)3@FIB#|9I!m&jYPV zSN-nw8oO0DDLF&!1VnYmrLBDAh_LQr%}z5OFL|1j-AY0H{&G-1%BjhoIiR|UTf|Fr zO(3qU;lMaBJO)o(CJgg%xNJCTkpr4zA6?Vt3DRnU zg)TYTZ}s)5(iisbN%7+U{@!h{_~da}7swNiJZiT??On*n7OQyyJpGTJZ(IXnqoZbzYiC3<^Q&(v?wU8R3#pcuM$A|39~4QPPpgoDujsD(zb;2bEFLG!L(1bthxYBc+5Bl~NJZysjyP8LItTV9soS$f)>wv2H#R#hP@x$%ieNNswInJQCT zFD-mwhsKrncg35xt#N}N@+A9s`0-=FNC**hy2G^3*m-58<*iY2KJZARPyN=CVj~0t z@<)>)XVD@2q2lg=72L;1nO%4g#&Bi9PeOGVnZc zvB}D~59|f5BuRCR)?%YhYn~D3yQ#G82xu`(Ynn@;Qr(=>X2N~Mf>p4i^TxRP@7a4& z>_nGqsml$#M&*rib=YI_P4W*b_@Iq+iYxtVI3z?Q9ZV@fww6WKdA88I{o$Az`UexC zc07qDj#hYTYn;~Yu!wB7O_c#NMK{a}Y$dzu4D-Qw*c%v(tGq?i)#-sinA|3=6slkh z@dQI(5OyfxgaBs!4Vy2PU$U1f0jV}A?7dYah9Q7^6O)8+JbFVtVN}1(C%j-v(Fegy zq|}k|1}qIFu5R2@N^N%HSuZ8h5OR=t$kHbLrR2JJ$a_5yvueMl;JAxf==5awaOF74 zGN#@>L-R6RW;vz_c*?NrC&~PfDl++jGKwp9C{5^0wWQ;>qCVYs?eplMJlfKG-J`h; z>w$*gkIWD1-__evWvo*lG~hTeJ9%L$Jpp%kSh!MsB92dqUJt8x2T>#Jp}12;V`x|v zH5$sDa1sk@`{IqRuMCuN+oNsao>tn`W=sTYg;m2uW4w@FM*j5M8_4=qt~~Qd3YA!d zpi>t%1Q&?0j0nSzy2z~`D8J;G=lO5 zN1|^)gaADTm1+$E!Aix8#wm_){|AOA>0lThK~c4YQCoboKk*m~K@`4-yOOUfe0sc! zNHvCMUdE&rL-A)C!ON9Vt|nVAYRBjYwMANus8o@GTm--MxN|X=DMPhkIuhuLu6tfx zL7kWZFUYF!s{k%v^~_4@Ap&)vm)ND+5qkL`?x1RAN2-XRy= zReMs0W_5%LS?)nZ-b1W8IuWfV1N69ok45(WL_hrGB(Is!j^5lBO!QD-nZe|PVFujB zu4>2AGQ}WJMJFM2KK$)b{uQngDfv4)fgo;u5ZlM|7PB$V9?jLzw(n|^xWxQ;nv#`F zkzmTYSlw{U)30O+eUG!R$ zVASGCX+i~G7(EUZk~lj{&`F<2+G*+=v#lf=s6`l^RJk__&! zVh*j44XcnXq#Uy|PtNG4@_2|MkBs1m9wlqF9(6+!?u>7uiY`)Tn}oGZrB7Ricb&{N zhZ5kNTrVVtN@eBACDHN8KroajR1Riagd+Pw(0}7it@=-+O$4G&kb;Af#iN-R9QNSt zzSuWKR|?1J>tS^DQI_Ou+6@W%vm#3noK8yieq60cFu{P17_} z{eW~!&+vCtO~#nOE=O#HntT$(hUf-mnXltg9GnWHHYus2)O0Zs+!091jymqdRb0zH zHHTh|hhEi(Ud%X_p_Ap5}Vyoq0~tUG_zWsl!TG!?B)nID7HbV5onR#gscN zy9+YzA=LBOga)TKQp1oY8W#EGCh9S$B2O&`V>?rECHGss2RO;Q_=Mr>un>**G*(GV zf`i^O_40fq!3STkheQOfR=>?tXd95lb4Z;LtK?-#|Hh*XgniCt{eqx-Uk*?KNw zGFU5WPo(nsB8BTvKi6uMwND4>;G=%jMf}NZczr|mA63vp{$?Ly6Dp@b4J*or8n~GE zLLhj<)pBZruSF(S=#&|H=A-C68KvV1)}vSv+>AQbhEAm&l?g%;~`*RAt1&i|D9ykaOF`Oz$Mm_2q(e`aM6;G`biN(qQ`!V z@_a(NsDP3YbM5@SAjx} zjkc2r+awK{wwpwtIT7rpiFonp)uc?ky={~@klQFoh#tsHZvMo1Y@Nkj@}^AQOfji5 zk35QrPA*LWoTF3`8!A7C0{Et2KVc#_&I=RrWOS8HfG>{D684@cwA3%>XB2uO()75~ z^=n!JK~A+Kx?&sLL?@*}8p@nH=LAE%T1>ERRpePg7QH*>|ol2lr#R899VjH(NDP zK@5*HmV8c)IzaTD7KWO)Ngy+2MeX% zoejj^@TBY0MJS>`tY|zbE|=bJedFw|V_H76J#i2NXBI^c%iobBd?(BRMfP>{EwqH) zmaez$4E?@e5c)h8%Le{DBICq$#W(ss|Qgpn-D*hl@mSjGnkvF`D;DU}6IQJRt#6Lb9dE zI%7i!sq1GVT{sJK%*MmRahIMqzcI54&a1oPA_{`xrX2Zz)C> zbr}D7lxUt}m|4acR#-e2FHz(vjwotgRdmA^hLj207bz;nro}Wj8;1BX7JZKj%GXx( zdD(paJK)o?DX(S(r4**YeMuoDGTG&e&rV>jieZ_-q07#XFL zqLCO?3=c>pr~5Wt|L!H&RXKGPq1*~HCx7t7A3FHMRX#F=VA2W7$FaAwqtX<6T>8|f z$qM1Y{<(4O)8A=N&vZml7V%CKG#-vO)^7T|`*N}8FOE!gggengEJ4vWorXs=2EC9K zytFy#!<psgZQMyE z15IQysDR$!aA{q`(FDa9mOae9^I>z9~tm291QlyWWcK_bg z`JR03^y3;C$UZ|QVAp>U$8?gMTL4!aa#t*id;GQNXdR1m?hf8tcb1_roPPgHw5eEl zErV%qAcLy18rb(Z?vhhXUxN>xk_xzct7o|1&}4lIq&wamkydg>zPycj_>IwGkJpuA zF|4nSy~x=o=$Of_G5`C;d--Mk6J{kY=%a!XJq{Nm2JccV7_VjrnTIOdw3D#?n1x_- zeq6km$}*aD&0%EVBMCP_&|@FoTda`lJ#DpoaB3#mXIIhAN=z;iv=uy z&r2`umO=|^mmlb#FO8S9p2CX~J4Q3zIpD3ECWNbpJbvI15`$gni%}tbeWPMV=6&NY zd>rEWIR0xID7~pHy9c7AhZJ`gK8gB$N!n5qIsQW7raGjN$kO-*F9<&=a29P#9(&cb zqn*BW)3nicWAr0aM1^ez4i~-M5z&uCuQin*95N@(%bRA5!tqUW5{(+(cS^{wqfr%>F`OL8u5GPbpX-Wuuh*)7 zPqSW1>Rq}N%?Zx=nMO8mn6#CoGl7LiW%X67jaA@pfBxm~Z#|WQ6QY+jwiO!|KZgE% zJXcnBJ$ujOdG?%(EnYvm1kqtd-Oxg=>+3_*%)^Q4Uw1hCI-;1S+bno^&!WP^1sPcw z$xg-TP_RpWEk71`dLg#`*kKv%BW~KMeVu_e8>rMvKJGppF*u~GXC5N^nfuJCx4r`X zP|I?uq=`M?@JlNX44qmvq&Gvgqr3f6#9=Soo9rzACAPq|avsu~QQE)tcP)3n##fEh z+v4M>Oi!hwH*Xw|*c$?Wx)=~Y{Tsmh^cQiToTxKfMQBpIxCQFxkmd*C0ZnLoh3gk> zV!I)YvQx1Y|Iq@VUz^r;H#oPV-(B_p(SNGq;SbV{kKF53vQ`r68Nps?Vt;-_#_VNK zSX_Npr^yq2u(hE_)%F}~YFHVC45Ml>!p{Ey^WAO;1sN|ds^3qXUKwnQ!KgMndaljI zxRQBtnWIx<*N9!o?b~)31^JHAt7{MJr;D{0|BJb=ermIewx-2P@Zu2Mio26iw8cwt z_u}r7;=!R%Tne;EaVYK@+}$0DTOjz&d++y0e9uf~@=GR1p0n24a`vXVXztkBpbiYv zc)+2fMD4VsJJWAD|A#&`aSdl^ZL2j_wR&Kee3~0(slurf|+C|o(}F+mh?Xo z^ehxZt%q4R=(nqwkK|zEM*YL8z&i`=@tgXB(>~>5KNrHeRc{K(7wC^P4R$p{1jUBr zu~rAlC%FSSIm|5C8#bPu)_AWASz1ZN=E2yN+JP|#cY#cEINIi72C-)*>o;eeUmh9D z?pLN89lu|7$7k?#^P9BM^qEc2^ccgqbMBuM4^)~9I2)1Gzbc6qa<(8B(jVa+-5I&_ zy&H$Ct8Y?nffhogTO?JCQeG_CM+9TCeJA{qVj8lmPjSRM%=mJa0}{YAz*n zqDc6vrueN>;dxd_pVhS&ZDX`;*(S5It&7(p_V`UDT9=7)zx<8GV z8D-5AB*5KRTmXy@X#AEbQ}R5}8XP}A-2FQj_jw~3wv-<6WXawq(RZ0isYL6})MM>m z2fkLI({4jZJC91ohyWKX?dI=J{eNQ2vyXM|m=VT&)JFZjX?Gy!V9Dm$?n+5f4^Q$U zrlW#)>{91f?OCmSS1d=6OM*mt0iGPvW}rm6A6O#UZr^mLpUxKVC@_*LULwxw1y8#K znu7?MIer+%_1p+=Da-~l@X>!0Vz{MoWkLJ>r0RW!jvSouN+SK@kG%S^PQ?9tW7WA< z7p~s0VN=p>bIoNV`PIlBOWo4bkZfv27>$KE%))S?>Cm7n;aiqi1#}DDs=(}mVTX8` zh5=?l@B!Q5Ygt)OqPC~$Jh3){e-eG|b)M;JY@hM3+-%CI$TH>FDYvqsx%+VbqCTYf zc#4O6kvKvxUmrmj%05GD;U{2;xaL<8X7CvOYIw6|nh`Gr8IG9FAhzm5ASLLU&J!pe z<$b1FpLh8CsEZVLo0@nh*BZis9Je17*y8N^7mHcw1&R6l91R*N0KmYrcH5CjY&O`c zbi6t{OVa(N;~U@PZkptQyF&28M(#w$3@T?&Y%SKfZ)-t2Ff;~>+@SKb_vM%r51`Bn z#Wn80VY4zc`EHXU|LG%B1;=1-U2bkjC1r7+>e*VD*L_6CYSBgQnM#iU7jdVQ6Y#@; zNq1h1?7%0~)~C3MP@_P=Y=aXt%k>B%j`n*~xAh4(zJNn;qk4Bes>G|}L)Y=5^RMNu z-W3diWBDULuKd%sf&hA-iSTJq6R?W1UwL?ZJ%sy%D{g*h%fv-D?gSI#Elq1=5W&%r zvxy-jDw9{eBd?N~kj?lT+h0o5`mS4xF0U69r_a)@fa%nn)uh;aUp!vU;`6q9p|Uj| z8q$m!3}f%7S{?DD*9Cz(uj;?kjj*tG$Bc794bde#*G~gcshMFGn($>WJN1h#K(nu4 zp7TL4z^!^`$?Vv_C2u{&8Q17x5q9qXEW6U?EI870$MhY?Z1}95hX&&#bi_|+E4sk| zefeAY*TBioBSzP%I*XU+t=A(3@P&B_o6XK>FxXp4DH!Gvv17rW2A7*Q&hJ)PcweW zc3)SThbK{mAYMw!gvW);tGOL~&qWx9iN`{5{_H zxR2`#5DH)`PT{NDY{39lrhxlgXILa?Bg9D}YPzBwxN{xf4(VRZ2cxC@8WYXnc63BPc#C1k&(kJB+(mcRr!<B(Y;^Gpz=cAR|8~=8oNw+82jW8^0blN9Byu8O@gq~Zc zU0(p{_@MiNUtaZIDWi8YRoc=27|$2LNpsQ<@yoqqEmRsl%^XSJ?4o$^#cMw{P2Od? zwHT!UkzW%r&F;+#uO+M`5k0LcbMu(jB4EHHV;_KneK0uH(M;fW1zP0f(Qib$1sMvO zL^R`{b*zZMOLOpfqhb!obF0^b#sjx)++S|JoW&)b(QVN^+uM=FjL}W9qoyt`S=jW0 zYo-{}KI^y##ctCmL|i=24gErk;P4^OHP+)P#((F(*8>N8Jrjcrz>QwIU)ME?+aKiE zovZdgNq=9a$wjXU!~wr7`X#znzepE%=GzTdIcNl&_=^S-HQm~nrD5X`P1>o>fkFtcic zXJ)DR>%*wr%AJmOhoy>ti7!z*e+U%?3|^Qdr}91V-{9x7PT073>^Ue9-2u5mF0bz7 z{YkBu+5&z!$nW=otxzp19arLsQP*>N-9>(6bsl7 zi+?6A1<%fh^wvv;6;`f8rvBEh?;~>s<~NIf+jeW*6ua&Atrp||^3&gv3*8TxpR#qv(!?;L*_XH#!~C}^OxaH z{(qSMPZ1hbn_*mL5C1xw!0i5%%(y`4V92_u0g~o1^kOlm7B|Mo_JV5=kW-X+2-x|j@E^CCMJ;G+Li-A_o z!uSf~QZNA5p-unJp;-I`8k5dS(#};v{BXlW z;x#cO#C@lh*WGrC?C+u}A(~YG%=6b{V1kr+4{S-mo~d#hn{X{;x^0Ay8b@Wf?$?ow&33{950LG0)_h07o673?BmyQ5@`M9higd0O1>Ia>?SaTCjI~b&_ zO`-8R<=x?E#lCa1?lvQR6jheIv(7qJIF%Y|zsI8tIaNRvmV}|W=H7`f`T64gL#C{} z{CS-+BK3p{T@S$Z8S8>sj4e}39lEU_wS1Gapg4?!t9u&`g@HB8WS>%YazNAofQ@tvb z(m*e+icIVF^KC1iG_=zfRK~Aro5r_vIeK->clqyK@lJ6t$<6y_Do28CG&I*|YoBI| zS14rr%J&eRLTX4No+pHVGV4c$?LID)KvDeT4T3mcA=7RH%kEX!0v~5{%_etZq#om_ z4U2?KZ|j}5RXeg`oxmJepu16_>g@v_8BWnPT^Vgy{Z8^iBLItOG2*89M6voO_dmw4 z{vIfr$lpectGyH)(a3FHZPSla0by#jcDFvN%ZC9n4qT?W%y)q#hTz$6_;1WB5fE!> z@P}ydjFSxN1xF9i>)s`(5RG#B;nb-?g7IPO&hNqQBI(ZV{AoV`V*Hh=w~CuANodri z15k2-@_gckP^>{>O!L|s;WIn1FS}S3w8kRxj$b?br3Z(t{OeHex)=VS)6y>{x!m2F zOk$NczJS3|HR=C(Y~+PD;l}N;x4_KU4$iUeduT`Gp&^t8C!ZNh%TZBMbFCHddpdj} z<~C!h8f2&BxXOpJ`o3^uWh`;Zd_V4PkxP*{=j_-hz;JXB35JbNo9jbDM16 zpYh!sN)4o~T_`J4IHP{W92GO5_t$F=*O~QvG``dDzI!b-(A0Z#)~k4x+v_&&^}g8z zw_A#IB19pO%+;LH2)>eoWi0V?I=4ZMRFx+n&*#{`#4_>$ zmx&a=j3d~$)!2SSb`O4J&Y_?3M|x$6*D*XUqZ@96ajO|xn!@pEtwi`nT*Z)^Dk>jV zpq*sAviS1N&Q0081F>bM{*HoHxWeAc&%=h^u=9af0{o*t7ro!(tCo{m4Omz^C0?rE zs-D3CMioY3+P9UxT+cNaFK4Ix4Ad)eCQwj&5ZIWiKWuGlsEZ^bDB}<7@^7&NdNLNhaKY4Btlrz$F{m^(ZP6dCM zuQy*z?FjuygctepG9?T(-40FQSS%hk6h=KD@lbu|7FXxB78^Ibf>$WtbKi9Bpg z==kx}@7=kR{7J3oguoaQ7}}v*eo213Hsej z81-O_jpUc7?P>V*A=W4+^cx>eBaIpjBnh+#A^a$Tfg2Kr9ui1jOqo=@v$pe1wEj1N zb@)sYt8?Xgwm;0ioltp{bKr6;A1w7D7n_}US&C|Bi4{PAWcLJw!)=#f#*s6RZ;It)phLv zIUEo_h=8qd-6@xGY0uW@^{znu4#l@skl7Vd9UsPo_U@|BB+D7Cx8R4Y<=uHR}pZr)sSm zG3!kEF*YCgcD|opM8~U6^pu;GkEl5f7w)H z6V)b!?X1)3WCZ7@P_H&(7R7y`_pfnU#^w1<7ZB~nG|gf3Cf4r8W!M+5$&CpMx+CVX z0P~7akufK3C%YB;;_ppDyh@H1?>K7Vvry&Dp(0|5C$ME~9M=M-M&(Kc5Qs9N^*D8q zU&S4FgZKTTq|3>E0XtS|33|SRBO*5)UOEXPk8i_NEeeyo}Dp=Rmu6b;W#9bCx++T+09 zNma-@ADf{-Is20fz1U+cJLve#(N%I6Am&idpTA;F%!DtwjUG~oR6&<4!Bj8IC$q(_ zhKHpGmaPxtsa!7+0(*HC^z@eEA4J;<@ck=#W@tbC%H?iAG=ExYL+=l5Qfru`;@uC3 zF{UcQ!ecVg+xmG`dEaCsfk+z>5`&Ku^7zflJst>C#r=M5ym~>@?!);Oi<&e>S18on z`)_`9#LcpLqbrxB=;q^9jE|k<^G(&w>sX9eIrQOMeYrsyp@zZ}y!{Qd)J_t{p=8uy z&1K&f9$8XvJ?`S6>N7}ijyCe#vN(4~Ei3{SD&BBcxXB24TKH^vLy>-!mn^2OHO_l^ z$EvR*!XalWB7JyDM!?tQ8#yqVW;&MZb7cd-dT$@ZZp>ou(OCWR2`d6xToqF4u7Eg&9-kI-{~L6h0MGEcqMEl4_=;M zQGxp^_QOrKkO_I7!@Xr>{X8#z|yP z8dqmw!mxZY5ySUPuGvT5|^vT zmyQY5w&)UeOB+@=tk>nkG0oLr(x5fH!%HpOk%S$nGMt_>-2h1AHwWX*2iuk}wm^T* zQ+F%PyOBI7n9<`+`|35uk~*S@(;QZ>3nD$fR=JxbYNreBWK(4_p_m-}O;=%N+e@O} zh^a1@iuVw1c>t?ur~e9}?#5UbjJrA2!=>|Dn?wuUj*Q*rkz1AfGQip?r0Uocz{AF4 zbc=f07D)2^G!8g^_>BWgZNagXW^DH^U+}T){)H&sBIOVvS3FRFwjD|0p|bpE{+F4m z&2mVkAu*GTc@XA#bieU4k;^lSoc248y|vwK|KO&Jw{e*f|rvMXK|9KGJxaCF!X*MWZE_r?pl#ShegQ(#8M zk9A733+ItnpA?^kptNht*+)`4XutH}DtCm1PeK%KXH?*|0qCV>W!}O;mQ<+Y1FWIj z>ZnspovtM`SL)k47qV_DRVHP9=XZ6nHcGMR&bAQbv_&%PQ%x-5U)HETXY3y6E+KSiXqG$0! z$hVDEKD>|MgS@@huaqs*K>G;I$@ZWcqj@!4*^_`{iAVO@DLoXgNXe7Z??%v_CW&aX zlX)!Z2Yf{w6@Ts2ApW^0;KAZMQty~ygx?#pi@-lUY3cW|!a84N>@BW-3Prwomuk#= z2Z@D0)TB2~6|EDBC-GSRqQ?3Cw@l2bH*&SbgtEQ!-&{@jF|KnjkAKOY>5_@zGB&AD z1$ttOhK$@swS=k8}`Cm zg(UVya7S#Mu@I+!q<3spienPpd{1Fx-gr#nY!IgTRfk|DD6h{bt$LuS=jvd9j^5>| z7#aSsId||anW(Qgn+RtVHEuO!n+!)fH`B=LrcE?8Amd>+WFVVYci`!WTY`^R-&5G4 zCL>lj$wp@2+$~+{lvg0m{!nh^8O&Gt*hJNugfBFTs|(5+wm^MZMxEY4RTDYRWrs?3 z>Ozg`e1YMylXV(G|IIE_2(pt{P-US?S?J$@4Qj7JWqshP_q0JC`W%<0xYX3);K(%hN|X?Bm)+)Pz~peva2JNMz3#*H!dB%*O@&{ zelOQjkPch?EP2!vnvTCW22iyvEKq9i+E@P0J>r-5PJj$oWd1nN!ys3S9QRrf^ExT{ zP56-3x=gcDmbW`^4C(y%*UJC6L7PUx?D2w-E4oY+&ck%6?~Q_^{3Dc@U}1>vH0E~Y z4;H*nFd<>(O>>EJ+9>R?^s=2y>W#*@sKY?_%qLaph~ zq^JI-yy5XTCnh~VaeR&%Hlv%sU1tSr-9mQJoK?Q{WPL3LDbJCR@b+o4UJ7KU#+BgQ z3@qsgUIh#@IaT+Wp76GtQbM29wTq7)$?pH_q!hCU%W9JM`p-03txVEs-YFER}ceE1f{^AfZRcXhYJ_7>gAdSQ!a`2>?l28#a`+7{+BH=RW>(^eN zf{e<63Gp3CnWJ@Rb;=dqdF=1`15tq&k| z=_Z}>{{@h z{ER&R<8&7Y#ObKYnSjc?l8+ao^!EDsb5j?^ucb>O{1SyBo;tLg0>Q2P8`o5F(6|%_$7GZP;^EI$>8`+eEfZ@r2-eZ zY%rS1Ab>S+b;k8%CF+Sf<)^30azly$rDUu_UtHMCc6i^~KK07VU!aU(_MmNGAa2p^ zsr2FnGK*LMG4ac;PUGnbr;S0>UdEMN+dyj;U%DXAn}yv3sY|b)H8;BO`z9$gbtW3m z8yZS|AI>DAzy{pC61Tj!GHEy+@&3@f6ne&<6z1dm^ z?wmo{y)pN!wXAUS^`e4bu}W4t9mJKR)!YAaD?U_dF!ALdwgN8c*V^`=oC7qP#Ybvr z7eVsY+O`1l@De@?h4q;!D&Fm#h;;5TvbCGT#faN2?II=ONSkPn{mR~>Lf8Rr^GiMN zt76cdsNnG4k55m!BF9LPx@*!2fNpETBblEXD|Fw+o-j$Nuf|%gT zagKnxuTr}oLtuv$XM0I2mT?(%yhy}0Q|ttbW@*CYUm^9VqpX88`VHwP zk>qTNAq8=6N8Pk(e<|!t)%#gT#XDa&yPXrekvZ!{iL%Z4LXnIjQEE*JW7 zX~e=&H$KqiX7WTFU+~TmF6K}wdsq~|;SAd?$7CV*GU>T}$QJrjNXygfBZ=X2?m&9P zPx2Gf2IL>QHP+gy6ZBWJ=c4)1W?k@F zx**V`D~yS4KXB&uszg`sV9=m(UBhT~J|}LyEqiViiBjpvi7KcYvkqEq5U-|6i96t(f?ZJ2!C+c+-8!=?V}>f&Wra235>Dp%oWoOCB&E3Hbid?dBqyPk8a$1j&8NFkH%WrMgs8KS|C~N3jxTCFVUcS9|q`?&9Qi1A5|H@?rnnKOcFFP`xuygsh#wca+Pc(H>?2J_ak+vit}T984H z)q=ww~Q5}ayb?SC+C9~Qx+&Ig%@wXC0FI+v43eM$m zi$FB%&qQ({Fo%)&jYy8pKDSme9WLm%E{|x54>e6<_w?>bu>m(l=6slkiDvm4<5%Qr z?>vG`?M(e!kp~bB)_b9_^JfHyz!#j=?>jC znf=SP=tzqliUqZj^}j-ADILClNqJvic?*a+z7DWQ!EzyX>X3>kJ{Z1Vg#!Wed7 zo-n!NdPC(a-3_sXV4S{Za{F(RM^t}=%yNyx{o*8|Z>hMnG%2B7{8(m58C<&`chs6% zsdljfBRVQ6Ja;Q|%455e!)z(_R(X3WQJEzNLS5D{5JySFa~q<;L=j{&J$quods{AV zJkJ+W!XQQJF&sg9;(KP?M_v}lLs=Q{$ctmOTMz2-W1~>o6-%rM#5D4E6>SGiZ#-I_ zv^6^1qzP(0B}xfx8mAE*`*V-#3gJ6dtcPOZnAB*~_&soV!&YZiq ziobL8$nEw6HP-P0H`#pQDN&`NBcmaw+Z6f$mBET@&&7h;eOaOiH~m%Lwwfb`fJQq$ z-Cja!x+$oo-z52Qs|e+b-?L?wNCsBv(^h&}wF&dox?ynTz7mv6-hfxPvn}m1lgGgz zEV;|>ri1%kw@65G8y`NXy#*6S;;XUrPVK&rL+7?=);WtpOA@BpD}QUibd_;W^O}lR z_vw@?u`RH+hcfL==n6kc4%LXosUhN|-wL7aSZ9n0_*>?jyA9IBYBCAw zrmKZX-7S4fS6668*z%{ zJ#l!+vIqg2oatPM6YbUR`lkEQWD77IG}gQA$7K59lAu?%zsGnRJF*QQuG zN$aMEZ{fa&@0&Q@5-sLLcxYD-6rHyTCBF~DE&%l~npZu^<863`CvUnHF;n{$aku}{ z;&O?c>CF1thYN=eHy!ahU>}>+*0d8dt<@SqC}Xd5!Bx0Pc|_AA;7^>B{8+yL3#Z2* zO-5hZB^*X&-|MdVv`6Fk7r+>i!KZr)a^YS#1@G`+U2Kab4z9E!tozhK_F@jgO`_uC zjM-Z0597uXEkmx3zvY^Qg3$+q_#>WV)bRnt?@!RkWYUGn%zHdd?d+Ju5awtMX|>vF z)*x@SUC6e>vtEp!iP}S{b&C(e32~Sq&6;c)Z*q4v34bmStDj>BCDJ2 zXH`k7x_yd>{kGn8+szGz0K02I%NLuO@mp!z0Y3#=5^GF_K8s$OE%h~?OwN)PoNRim zhrRDrZXv&%rpT;x7wWE7-4pQ_F`La^Zu`$Tsc_FHYFf|f^`cO8etgdwM_nNuaL(=uDl|*0uH5fFFq^;1>?9eE4|@`G#KvPrGi|K$(inuQlw${mqD`1|RcLI}R~s zHk@*H*^}Tx&0&C;s#&G^n`lU1Fn$dd@N@-Xw;5&)TJXegG;`&<9HfgS+}lwgjv~q| z^pjdZncH|7`2&Ap$GJG#0aw=GFT}J);*S@aAJun6*P_(gDafeL() z?}1}9-`@jtTm^nb2nrhia|~UiO=2x%m#=5GMz=5c&yO(LTJ#amCT@ zd@GI}Z_O!dL1MvMowxZoTO05eCtc~)(+twa!-ojK_qbqN{4QUiG*g=o)V{`C`7Y^~WBncO%A1WbT2sfeB2-!&z+r%4k0}kpME|H@0tUoHv{er)PiVyO%9ZAU#-unjk~Tuipyi zey0`H+pN+^rE%^@5i`E8Irffus!ZHG+2c*YM%u8b+*V7P9)Ab+Vo;?dW<-)AcdY{}3_!=kos| zVgP7t?loTQfPu@D5A67XiAKR^GiHAccF^LxKNb8_ZUe&XatmR0)`yv9iMEsdv&Nxm z*x(;}cd4df{cW0IJNON7t?L{XFXepjRYp!#ex<4e5}nc3`=O6USR6BCo5a+93xMLQ;OEs*m=j#m6OiCr)qjW8-e7k5 zzEUw>*ijGR1r4|*_XD$kc*#DT=(XvML%%iin{qcGa{brl6Q^16x-6wW7 zMdZTM=((X@Cb{gp)3?@<)4k|Jk3TudhdUW6aqAy1R2#r!I)}tC4*b^Z9gm}A0KVJd zQP&{_V>lHGAW8&p6cuR2M00g{EmJbfUqQDr`5PDh75^vyTX@sQlbLxOh6vNX_>zXP zW~!(8A`w}u^r$7HoB!zY*=3VL4Rhjd?Kb-v3&egJ_=lmG@dmW6IBXGYMHw#HMjZn7 zBW=p;c&{>~lAJAxDQz>`bjQqKTO4e*A;f@5OGrX{`G;)67v_pKsU)>xLA_(|I%sjP z&*OgZ+nTqb9DR~VIjHJ^x%*|Ef-*yx>6av21c!Mwq<470!c0?Cur=YN1`LrkYrT?G z2MPhr(H;9$t;a39|8|_pUbLoToI0bG$S+B}L{!#FbGvJaZ&^cWnT(Kqa4qn3M|6~; zjN>cy`4(9z#clf&;P%JMdkf@mpvjrnB#5My(W9QAtqeU;UnUXmE#A5zoCBZR{HYs=7SD|3ebX|S zmP>PXT`Z=rORL3xkGcL<)Cu=~)H%jA+eB+Ono$*PGYLI_nM&>lO6nGBJ#7%8LYf7#xRkIxGl#19K z{vPR)##4pdHMWZ2w$XH@LRA^~qfF@d*`0POJhuC1rkv@7vSFsw2jj|~r`6=aZljX^ zr^+e>&AbPKkmtD;;%+-U(kO}^Y1R~pouOV0bRtr-ceAy_Qx`q?4b=!I_TAH-UT;?F z;0GSqAd7wAd5kogZp05KKo4~e#!;s%lbG#XK#(RImdX29Z@`j}a>QLItwZA~=g?O4 zHwW>(=xAF<5&F#{9>NzM__oTd!n+BBp^?+vf27k#Mvo@tU7AJd@=xhty)j_bzFE=K z6KlSU`OVy|F)>{8>2^_mgX?xC{Qfe!$MY3pcI+46*_n&(XKo9OoIuf^vAZBfjCKjK zTY!gTT8{UjzWB9)uel}3Of=T9H;(Qh?HN2%wG zG`f?21SRjU^+a#JM4a6=va^!%Vm3%fRK@BmGES_vzpXXkRT$H#+#cOm`FS6Vh$AjK zfg#$JsxC$xzFl-9kh2mw2udJUp>So+QxBKI6Fju%oh2{8hvn50jur21h5ULi*%1WN ze5FQC5V_yLSl~Eh^hUX zImI$kvSMDQ4>+Bf*{30{+R57~zL5ddZr7_)gvZ zdN+Yzuv^WdGaWf>;ZBzcXTL=})fgqm#~ROFVgV~LG<-YUhJbQ)Eo+W9ZZn%bVy6%X zIy&#|{`e^(b3OzDfp7{W#r9_}+fH!rVr4lGS;*~_Jrh$`JQJ&Z#mgdn6A;Sf?+#RB zL0M2HPP02wOVSA6BD`a95=!bb|F@UPQ?{xkh*aC&M3!DKzvXU+#zTMgTj&BF^;N0S zj(_X>hYjlD;9rxk&DF`?;AHhrj^ohKukQ*x5x6XiMNV9QWm4??YeQgBXH`?Kle$~= zrp%YL(0F_Ge>Ef`33Zf~F5hvFM;!Q~Fun1#T)(}YJGu`J`Tc5<6?H)6-^!J(bxe13 zsXV>Nb$2;_UxIgQHM;lVQrm*z-g#KQ*(2PRC-8V6I!tDxWOUj^`7182@DFbq8(o&S z%U2oNud91D5~N%Ap|tArO-1fUzIgcflZ*sEDFca8ivC?ZIZ&JTjKdr(c#)$%16U3% z5aOPP!mBbT8a{#L#k?b3Xu1d#lWe`gqI4UgNmuX@s5LK@jbPZSAN4XKe4KEL#xfOPI zolvORPt`M^BWj1q3b$$ym7SsEd)(;${K?cnrzV7h*lN173 zacy#`yAzek22?mc=(b<1*iL?CZ0&(zsKoSc=oWC_gm+ z7SQi|Eo)zg|NkDCxjoMRU*CCCz9Du3a*u6CWXl&Qr7I_TSjuKvA|#z$nm2k2`oLp+DR`IsINlHHT4 zFR|CFP}8P?20uX4s}QGqdIGE12=r-Qe0&(P_zLU`Q?LoDOX0ceBS)XM{Ic)xdT0%8nB)gm(|_Qm7A6n0wTQPR6* zXov+>SFI)q3_iJCiQ`L6L)>Cetvpj=54-SH$vHfKR;C^^_$fouBAcNcYd{WNCXAdBYp2x2HOhe^onVes6O-9lfIT zJ?1&+ctkQK5AtB7%a@EC&2u!3;Mq6yuiv7jWFg9K&!>KQ*Z)>BlKM)Ak?s(;MVjr? z^d}d(I&xH0rWrB^JWF2hdmkF^&(Uc-uOJx7!A1HqGj&SEIv&h%SsrVLBHN%e*yGbg zNjAwbk@)MMk(t=aEB3u>t(fR3TJ!!cix}nTcYTNlSS*-JYmc_*w0r$XL>S>wGO%svwg(=xWAz855@;%zcg9 z(e~B6Sbzq7J#>=KV~oO0D6ciekA?0~aYXpxGJ-Rf_OKFRT5BOEdTYEf^4;NrOkeU6 z;=^FI)q3`g+ic?J?wmuMyBBvN-t_;(T3hB{%e|#*j>*P9oSvFEXdJXA&NrXQ_Qv6Y zt0*})?be}$+p-NS$^?XBOs~P<8@qHV!AR%zHI8hhx8EMBH-wx_45~8RZ1B`U10=D+ z_akWH59yP;SOkDHK7is`Y;Pz72nBrrsetS^v!aWMp{V48JaG-B^>KstMnRY#&*jb+ zhNH$?hJ3}mZ)a`H&M$^?X?8=Ve^?{>$T5sHt#hQm&FG`EB9-<;CV#a)%7EM}xR;8? zIytVn+K^lqtD3nLi_v}T1zlVd(yG-q%gm^zX=q%ec4)R71CX8P@6)|a3YoL|ReVeE zLQgZujS^zRGT+($t-a&dWN&^hwYEx_Z;V zR-c;+S;VAeeH%Xxf&XWefATSmot)d-Pd&C79z8Sir5k2H1*31ZKeT2E?d@zUU^=bS zS!}c7PeX`b9ARWuj~TyoeRp#q5QM9uK3%=QVEb(wN^a0UbUa;N{?}-0{2;8sA zKxSvmp2ZK$IQQs&8kJ)|q}=$>;5!i0$BtVq@}CNp&!41m{DbC_>K15K)4Ap9eR;7n zdL}ai>y6Tcd+r&sv@Hm|*~DnM!d7a%^@SHVg6QaOtt6VT*?=EGLX+)KwUruM-q*t8 zl68en2xMK8(3DozL;XW3^pPJz&0=W-DTcC|k+;>_vi!~2+BO;c)m_UdUiufOx;O;u77c$AX%%geJmke_gKL})n#-{81 zM9=^4l(VBouO@udE~Kl^q~xi98nFbpHN;tcFUt4CPG^5b?O~m>rF)yI^CjLUbop%G zknXBLCdVkhr{|V9?9?4hJs<}|R$Oq@+!YTzSh@ado~v3^$c?ErWC;pD5Wa*=sHxLC z;72%SZc!x8@@(U22iEx()!N3Yg^c^|FAHP1D#T??s}X$`MrS82qs?iDdh=u@5GM>E zf8%p%G(uImb7J8xm6eczu&NL_me=63PI_F+9-B$u5}byz+%S17zu;&qJoWkN9>=ox z(z2K_L_~PqNtqXO)Jiqy|(>2rSs^70cb*`qHXydvEP#bR}omq4! zn=u3<5IdtEi7l|u=ue;X)QE8H1cjW#3;#8mHfCwpK#GrUL@Z0spB`J(X1pCU_j2fU zYV5t4^+mOGhOjx8zo@Y^K@n?{1l#fSzg9rgb6QE2Gr7pH!$0g=n&`Wz=S9dG!JEqu zt$wrf`vT$OOiWuKXhj!+U^t{W8Z#sB{K{p`YM}-vykA8!Q71M^+B&Pj#%yD^3$7%i z{WIME@$WU8MZ;JIm-Gnetm`_D688gDPXPr!z6X|~7Fv$#BarPzL`9r~=CZ5w;%<(I zl%lg958ngXl9DdTV{F-V{lj6<8+WUE8ow@UVc&_S0*2m^V68y{!bu`Ie)|32xK+;s zP0AU+JGufoX0Nnp54oQ!@I1cDn1y{A`uz#Q+3UWAl9N$GA;w18;A__3VZF_Td+$P~ zNp~n`gwc2*bZ+z_YOCL%NwfV=4FB(?B7kZp=z;AJmj+e>${#7o{PkgBi%jie>X1l^ zQ*V=&Hy&RAwerL9L-B%5(q`@L`TjU34D+hWYQw3z-$movKs;9vm)1VvcJ<02QnS%JyD=o`$CYYqL?}4*n|7{3A|9_E{>C3B?{(vpR;VruOPyIHj10i4sq}bv-@OX)|+Zc_AY>5g#%3 z=5se7EzlMa2v?DQCxC@Slc+#$J)R?h2#$zCwUR@$t&aPRpdtnVJs11g+U6fyW0*B% zX80I<0sdQdfbq1rf<>HVig?;5*gu7r7GNNK(uNQ>z(C&+goH#o`d^O#V9px|F|tx$ zk(#GBuI=HHZ#xeHB&N@`tN*r@Bj#UCF_{G|tF;=<7#+gHHv|esG~f3Y`-*+O0pn;` z11(l!jd2Y&j+T%{(#H4HD%;g9h*40p9ow=I&1lI;xQxW7pit(JSz24Vxzz1~#mw`7 zpdPsnDQ~NFO&!u;ou?|`FS56d{v9*QaKkyn?OL*^ckF`iS2(ET-+Rubt*yE%i9Ww~=LUb@4RBqs0yNk;@Kma(km zkoLe@6Q-<9N%7ctNcEcO2lFuEoUZC~3UQn+!aZ8ECBRpKm?3Q$AfbbUKsdo7DFPQn z#kV|ob`$EnuiEO^WsEWC5VADvgK6VMKLxs_DJPiJTT4)quQ{~2T_gODXl_MMC^%g9)=#8}3@FG(mn6(+Jb z_DQy6$dVxwQX;fiBl|K)-dTz)*~#)f^Z9=Mf{*KR%@171Ip@C5eLwH}^>Q9F66wjx zj}z;h|#kVKe4)+8X88nd_p(j1eWUdIx(s8HqaIe*GlAt z#Krky2S>TUfENH|>?aG($a-Lf<=tz%tEGY?=YACl7mv;THyWrub0SSHjZaYbv4Yy# zZA#=(R>`9vst5+IuIf}B%nRcZYjCS z!u52B#I?1#DNcqfdn^P+%2b1ak)tOIcqWhj-64Hq3APOXc&Jje?T4v{n zkv5hVvbnP(-SWGwd zi>lGD|GV-%Ze8`Fby~2v(cnpN2jKOZ+DC0MVXMnpT3Qw0NGLiAW!nD#aWARDZoOAf zdWHpUGUrLLdaBX6h)A4n#ntJfcfe$Szoc@Ck%J=GC0#K=Jkw870OO0-V1HWcT)gQj zwg2wP#ud8+tS*B;*p1gq?KBe3(gzj-xsc`tViGuK^VVL!G<27f+f?E~)V96$d0N^7 zFF@{L15|h1m>{`Yf0%t9WU-`LL)IslBT8)fWR*hM#Ol7Bc547PxM%{btSrb+m1gImjCgNH|D;QYsUwn?s_^S+JhF15Ick8zCx z%@&3l!sr_G{nt{87YlSpmk$rvJ0_Z*?`}VT{#=uRL;9&WZ7g;y@O-S3o1%5Kxy_$* zL!xy8$X3G!x=K0pCv$&#;`CY&`caZPzDgm7S?<2>$aOo3aKa7ql) z+rU3lh2h$0s&8tGU?#kXgNllZ*HbU)m-_%bq0oSlsIcH2Y4S>YaEG7%c?NikF!UV8 zN))cvsx3zemU8p(Xz5c|#oOI&0KS$1SLC;*URUG8FIlTwzD5`lmArxUDzZI&i z+&P3t1* zZj5t0@#yf7FHh;#u&#a0o~Mll9L!0KHZ}=^;jJ9IP%{n8rq#BTe>(ueqZ_5~=r|K| zE%xIZ3e2pePGLjFfj1U%`2%=MsX;C&R;1( z^3KT+sC_@cBoRXSn=@19k>r&AudWf5wTLA#fwcz{q<_Pld-j{cp zb7*M1bZF8uFo;p~=zKhFSM)(lP3;f`aksZ8UB)}LPZd$3Z2rVU*|r66!L@<-TKC&I zLU+DFtjbm)2ngoUqen4eV}o8oEBEcWb$ypR2Z2i*Jq!HVsVPDm8v!_U6|OXOoCp|3 z0+K^GkIGe~%$m*8|9A1d<0Ek>25{LvC91bO0?BKKG0VBaJK1tTH-;RG_{i0{nXpeBe zSj70>pIv7Xf`aqK1ZG%cq{UFQ$1h0rhzb^v6~Tj~jY5D6Jnr+Zm&jy#&V^vb_>3o3 z8W%##{*`$b43+y$HHnIeoyp3|uFuNOrPq@d26m3Fm{&2@6qA|qCjdyQ-QK$sMMp<> z#z+o;?W5m5m))QJ0w#3ovRdrPM?A1>ZGAJ;)xi;S) zU%V2)L{CrpLJvbZP$hv9VCh@2b{@9m!=3I7LH=JM&7T~a0#3fV$|Fmm?aWE44A9Gv z&Gi_(u_d!%njyjcjrimrQ>-9XKN}9r=CFG&$|$@=c$rtINhCY3h+7vp$3~sPXd4xX z2KFrxf0H`mXkr)v?qc*H4b=vP z0P`h{gP%MBZ{1Wuo(d6s7RKPnqkFG4T3c#Fn;hAi=M#AJJG;8tfSEPL<$Y8JAP3Z@ zY-k&zK9Ud3L_2*>>Xc?Ex>J^co{=O&8yhuQ=e8m3+!Em#4o`r9;=O59sjWd^(xFLM zShyuKCufIdy!;F$iLxX~)6tQ@v@dh*YO1~Mf3{EsK3*X-XXxpG#W%PA$pLBg<1 zDa%IsF9xyZc_nOmSE-b~$#~XJX)N^@sK}_QMu=4-k!!He<K5?f$RMJKuR$j zUfrG5Vzp%XV(ifU8z7_9?d|OH1ZY_c9M`S;&P-P%u-H&;R6|qRJst)3&#OPX(qjs7 zf+%*8ix)38kL*Y?Rzh#Z>W>rvNtA(B9r2MWAhD(L-ew6}5sO@yV>HDaHcO@#MKM{I~T^ zOyHOijIh(N&z-vg^gyp);)nZ=N`VYk%n&*Ixmg@=oaiyjAU#+nbF zXWom5$oc&F^Km$EwmbDgqnF;#%J%j2*yTKVvS%0=_!rsrDl&021wz&K%jiJgO6O$* z(RFlr@~efF*FU_XrI^t?%E?K5H}v?PxjDF2_~1Z=hKYMeI~nQj^<{<)7$8Vg>X~Zb zf1ey{pUH*{mk!G^q=bKfcZjidd>q2~kxJ>dlO*N|=Te(&`#3h{D zw@MZQ%pg)l#l)Ps*eU>7CP5u1cm%@femSt^EhX+a3JMD5Cpa9||AbmIKR_)N^4zVp zyMGM-`wfxzdTHyVY}};MyZ9RwS1nK|g=;S?a9=)uexMlgYjD5Oey!^JY2XyE5I*_^ zkvO#aXR3bt20&T4pio0rUDY-a0a~Hahr63}uO6C3Fliif+bT8x2e-QSTy%m4{!Yt1 zDwz{G6zMGkR7XcghxYl4iVL3}Qqt4{>S8E?8$8Y70CxM<*H=)KnHjh`Rey7N%1?PL za&Cb^fVUk2(fOf19kR#<&7n|bFx(PB-+y<~a;_aHP_K3jl*hxv!zM8?F-8t&)Nj+9 z{%wf`w(9`Myd`8vl7y7hYUl9qaG;OJOW$}Bh3Ql1_maj<=9>7K(#-f$=ZQ%H1OJCA zApN^_PmrW{U%x5eW#7Gb^02$RTaKKjZK}u45qLqJa7&sa)eIn?@c_OwV{2}H7dIPV zQ@C#mm>>@^ERYf(UtX9K9V3JuQi5QKr|9rjX_{hrO-)0yk(82h1cdT`w?TOmDROE# z2^yIc<}NP$PrzZ82W(w8u#F4KadeQjN+Uy@a>TiD9X{LhFFL>ehibaQlT#^&Dy{v@ zpj`hE9obpY4|fJD7XeXk;<--TI1{&$Pmz7iz|GyHq;4l$X^!HVnVBgyHMP{O?d?~M zw$fVu(H;W%OJelMkxC)$yPlw4fgwaNS>@;L;s_o2cXoYN9TtNkoqT+LJ<*AyuHjL= z`y<@OSGOBRuG^Mr*h~Q#5e^)F0-QT18!+whEx2|}e^qbLr;KsFwwss9mS=t$uU>cQ z*{MD)>$=Tv#h^qd3~{Eu>Y~+x%y_P^A4h4~u4K-Q3gb}6UA-Fg@_8M5!zqcLK#Q7pTmwTbnrt`!|u`2QrT0THD&HmX?)y#t!)~-rBe?Vu7+cgwsA#zpQampamRQAalyjP+j{#*~pc! zgVc?udA#^c-rC2c(Ag-aci+uK4or_snSzpU2DTSn>t2O(LSYaraiNV3=0Qy&m zBD)9}eE=*bxP#3J>&kheM;C%vP0SB13wsL5p{#^FqVEuu$+h=`E91mduH8QmNm4HJCg=9}8dLL{j|GNm10?Y{BV%KSZQIDmL!W~Fu=&5&B$GB12T9Vy_*>RW=T@ig z*bXU~nZxb5b@1kbwrjg#hw+z0GYtu#guEMkX_^O&*Yv7?xf>kAAumPn9wpGy*THuW z;9CFe>+3VHm*!a03vXwI(aSO9a0eIg^ZGA1|3TAzrS{_Cmwf-?hG5bjgYrWNggzcm znw!(Mel@XihxyV!D@p5%)yCiviW{gj?3|sonnkj4xw+|pT8{lS7-#L{%i6d*-$QD4 zQ8lon>|WHBr&S&jH@dpT?%UXms2Jg6W@I#>19xkbPOP5q^?ZHw!BLsq_HEVya6Tl! z19xw2ZDj&V`DH0dNqr#h;=`BJ7M@{Eu|oV;a=s75^yZ*B-f`OYD?YuQBR?ToaOxKT zv161h_#&Piw)C#0r6nj--RUK8^4ZU zj`Z^KdT^g1z2SPo9*=?Z59DO44wZTOn|y5{Mi#x)$@#MjAOns0Hdfdx+6BvA{lm;= z7!D`T^#=95{cBE${ZIaXic&=;Of!j5wx@uw1Hn+ za*H?diZ_`$uINokO}BAtugmu|T!ej4Ep4JayL&|;>P(j8meD_g4%0p zdirV~=m=Vt4iy44=gkKDwVqRMbs!|}6@U|JV{QG#8jWVYGvGc1a?CK8MS+Rv*$vG+ zDpMx>6a7q@e0@Q+=mx)R;vT1$?nos+8-_Zut?9uiG*+jslq1%M?JDl>1$w>4^mH?C zW7+M!y@BE1AqL0C$HQe7Rmop&l22;NBiMcuWJt_*i-VKbee4&lK?pPihdKs-PQrhP~d3dB;vX1~R2-+}zw0?~itcEl@e#e=;Qf zAxNE!lnldyCG9LpKNc!jtd(C8+jYq%C@X>mX?VdDE0X;6yZTgEpUmB~bfSX@i@z!7 z0|Efo+`>CyW=T18ejE}=6y%R-|D~?3Bs`?xMPz{~#gHfrs?z}eqsKucc2+dx&{o3C z?3;To3{k@*K<>ZIS%6m42T&{l7Q5~v;}LNZFpYDs_$D(7!R{F=-kV<_Dx>o0dSHNX z7O$zPaL4@W>!pob8wx2)ZPSCJZ*{ik9K2Z$4tN|8i8s=4G(O&K`~Sn!K-b zzl#(c7MPSnz=A=ZwMVg^dp{fP%v?Xc_PVoEf5SNP1XS%sdU|@6vWrB;yszRwpg@p7 z1TZPV@0D5Hq8tqAYX!|zC6@QEc!#><*eUXCwJJmd8l7>&_RjNrNZGC)n?(+YUg1?P5%E#iDur>`bfg+5nqgp z%n1)$@W7k`3^t+A`Q}VE#O_I{6b#aSJNznPR@ugLX@q$?J<8)T{EGIaaNFB!r2E?6 z)XbW0c8!x3PYt{7vnE2o7yYU;6nr3@{$nA3xcy&0wBPC;H9yWviY5 [!warning] > -> Warning, once linked to your vRack, the farms of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** +> Warning, once linked to your vRack, the clusters of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** > ## Listing Load Balancer services eligible for vRack @@ -67,7 +67,7 @@ Example configuration : The natIp beach must of course be contained in your subnet. -Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your farms. +Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your clusters. To find out the minimum range size to be assigned to natIp, an API call is available. @@ -76,9 +76,9 @@ To find out the minimum range size to be assigned to natIp, an API call is avail > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/vrack/networkCreationRules > -## Setting up a farm linked to a vRack +## Setting up a cluster linked to a vRack -You can now create your server farm in the vRack. To do so, configure your TCP or HTTP farm as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. +You can now create your server cluster in the vRack. To do so, configure your TCP or HTTP cluster as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. > [!api] > diff --git a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-au.md b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-au.md index fcb3def9dde..64a2ded9500 100644 --- a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-au.md +++ b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Configuring the vRack on the load balancer excerpt: How to configure vRack on a Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -14,7 +14,7 @@ Before starting, if you haven't read it yet, we advise you to read the general p > [!warning] > -> Warning, once linked to your vRack, the farms of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** +> Warning, once linked to your vRack, the clusters of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** > ## Listing Load Balancer services eligible for vRack @@ -67,7 +67,7 @@ Example configuration : The natIp beach must of course be contained in your subnet. -Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your farms. +Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your clusters. To find out the minimum range size to be assigned to natIp, an API call is available. @@ -76,9 +76,9 @@ To find out the minimum range size to be assigned to natIp, an API call is avail > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/vrack/networkCreationRules > -## Setting up a farm linked to a vRack +## Setting up a cluster linked to a vRack -You can now create your server farm in the vRack. To do so, configure your TCP or HTTP farm as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. +You can now create your server cluster in the vRack. To do so, configure your TCP or HTTP cluster as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. > [!api] > diff --git a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-ca.md b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-ca.md index 013d55c362c..c4a31817051 100644 --- a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-ca.md +++ b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Configuring the vRack on the load balancer excerpt: How to configure vRack on a Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -14,7 +14,7 @@ Before starting, if you haven't read it yet, we advise you to read the general p > [!warning] > -> Warning, once linked to your vRack, the farms of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** +> Warning, once linked to your vRack, the clusters of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** > ## Listing Load Balancer services eligible for vRack @@ -67,7 +67,7 @@ Example configuration : The natIp beach must of course be contained in your subnet. -Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your farms. +Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your clusters. To find out the minimum range size to be assigned to natIp, an API call is available. @@ -76,9 +76,9 @@ To find out the minimum range size to be assigned to natIp, an API call is avail > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/vrack/networkCreationRules > -## Setting up a farm linked to a vRack +## Setting up a cluster linked to a vRack -You can now create your server farm in the vRack. To do so, configure your TCP or HTTP farm as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. +You can now create your server cluster in the vRack. To do so, configure your TCP or HTTP cluster as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. > [!api] > diff --git a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-gb.md b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-gb.md index dd37f728694..49cd100c94e 100644 --- a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-gb.md +++ b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Configuring the vRack on the load balancer excerpt: How to configure vRack on a Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -14,7 +14,7 @@ Before starting, if you haven't read it yet, we advise you to read the general p > [!warning] > -> Warning, once linked to your vRack, the farms of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** +> Warning, once linked to your vRack, the clusters of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** > ## Listing Load Balancer services eligible for vRack @@ -67,7 +67,7 @@ Example configuration : The natIp beach must of course be contained in your subnet. -Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your farms. +Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your clusters. To find out the minimum range size to be assigned to natIp, an API call is available. @@ -76,9 +76,9 @@ To find out the minimum range size to be assigned to natIp, an API call is avail > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/vrack/networkCreationRules > -## Setting up a farm linked to a vRack +## Setting up a cluster linked to a vRack -You can now create your server farm in the vRack. To do so, configure your TCP or HTTP farm as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. +You can now create your server cluster in the vRack. To do so, configure your TCP or HTTP cluster as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. > [!api] > diff --git a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-sg.md b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-sg.md index bc62f3b0904..ee3a9d538ba 100644 --- a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-sg.md +++ b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Configuring the vRack on the load balancer excerpt: How to configure vRack on a Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -14,7 +14,7 @@ Before starting, if you haven't read it yet, we advise you to read the general p > [!warning] > -> Warning, once linked to your vRack, the farms of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** +> Warning, once linked to your vRack, the clusters of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** > ## Listing Load Balancer services eligible for vRack @@ -67,7 +67,7 @@ Example configuration : The natIp beach must of course be contained in your subnet. -Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your farms. +Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your clusters. To find out the minimum range size to be assigned to natIp, an API call is available. @@ -76,9 +76,9 @@ To find out the minimum range size to be assigned to natIp, an API call is avail > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/vrack/networkCreationRules > -## Setting up a farm linked to a vRack +## Setting up a cluster linked to a vRack -You can now create your server farm in the vRack. To do so, configure your TCP or HTTP farm as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. +You can now create your server cluster in the vRack. To do so, configure your TCP or HTTP cluster as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. > [!api] > diff --git a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-us.md b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-us.md index 7c19740f862..5a5a8cf85a4 100644 --- a/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-us.md +++ b/pages/network/load_balancer/vrack_and_loadbalancer/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Configuring the vRack on the load balancer excerpt: How to configure vRack on a Load Balancer -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -14,7 +14,7 @@ Before starting, if you haven't read it yet, we advise you to read the general p > [!warning] > -> Warning, once linked to your vRack, the farms of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** +> Warning, once linked to your vRack, the clusters of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.*** > ## Listing Load Balancer services eligible for vRack @@ -67,7 +67,7 @@ Example configuration : The natIp beach must of course be contained in your subnet. -Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your farms. +Once your network is created, you will need to retrieve its `vrackNetworkId` for the configuration of your clusters. To find out the minimum range size to be assigned to natIp, an API call is available. @@ -76,9 +76,9 @@ To find out the minimum range size to be assigned to natIp, an API call is avail > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/vrack/networkCreationRules > -## Setting up a farm linked to a vRack +## Setting up a cluster linked to a vRack -You can now create your server farm in the vRack. To do so, configure your TCP or HTTP farm as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. +You can now create your server cluster in the vRack. To do so, configure your TCP or HTTP cluster as usual and simply fill in the `vrackNetworkId` you previously obtained in the field of the same name. > [!api] > diff --git a/pages/network/load_balancer/zones/guide.en-asia.md b/pages/network/load_balancer/zones/guide.en-asia.md index e91a32ce875..f88b5ee5eba 100644 --- a/pages/network/load_balancer/zones/guide.en-asia.md +++ b/pages/network/load_balancer/zones/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Working with zones excerpt: Use zones to increase availability and decrease latency -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -68,13 +68,13 @@ This special `all` zone will allow you to deploy the same configuration on all z If the goal is to reduce latency, we can imagine directing requests coming from the zone1 load balancer to backend servers geographically close to zone1, and similarly, directing requests coming from the zone2 load balancer to backend servers close to zone2. -To achieve this, you need to specify a frontend in each zone that uses a farm in the same zone. -This will allow us to declare backend servers in different farms per zone and to control which backend servers are used in which zone. +To achieve this, you need to specify a frontend in each zone that uses a cluster in the same zone. +This will allow us to declare backend servers in different clusters per zone and to control which backend servers are used in which zone. -![Operation with several zones and several farms](images/multi_zones_multi_backends.png){.thumbnail} +![Operation with several zones and several clusters](images/multi_zones_multi_backends.png){.thumbnail} For example, if we have backend servers in the data centers of Gravelines (gra) and Beauharnois (bhs), you can order a Load Balancer service in the `gra` and `bhs` areas and configure : -- A frontend in the gra zone with as default farm in the gra zone which contains servers in the Gravelines datacenter -- A frontend in the bhs zone with a default farm in the bhs zone that contains servers in the Beauharnois datacenter +- A frontend in the gra zone with as default cluster in the gra zone which contains servers in the Gravelines datacenter +- A frontend in the bhs zone with a default cluster in the bhs zone that contains servers in the Beauharnois datacenter diff --git a/pages/network/load_balancer/zones/guide.en-au.md b/pages/network/load_balancer/zones/guide.en-au.md index e91a32ce875..f88b5ee5eba 100644 --- a/pages/network/load_balancer/zones/guide.en-au.md +++ b/pages/network/load_balancer/zones/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Working with zones excerpt: Use zones to increase availability and decrease latency -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -68,13 +68,13 @@ This special `all` zone will allow you to deploy the same configuration on all z If the goal is to reduce latency, we can imagine directing requests coming from the zone1 load balancer to backend servers geographically close to zone1, and similarly, directing requests coming from the zone2 load balancer to backend servers close to zone2. -To achieve this, you need to specify a frontend in each zone that uses a farm in the same zone. -This will allow us to declare backend servers in different farms per zone and to control which backend servers are used in which zone. +To achieve this, you need to specify a frontend in each zone that uses a cluster in the same zone. +This will allow us to declare backend servers in different clusters per zone and to control which backend servers are used in which zone. -![Operation with several zones and several farms](images/multi_zones_multi_backends.png){.thumbnail} +![Operation with several zones and several clusters](images/multi_zones_multi_backends.png){.thumbnail} For example, if we have backend servers in the data centers of Gravelines (gra) and Beauharnois (bhs), you can order a Load Balancer service in the `gra` and `bhs` areas and configure : -- A frontend in the gra zone with as default farm in the gra zone which contains servers in the Gravelines datacenter -- A frontend in the bhs zone with a default farm in the bhs zone that contains servers in the Beauharnois datacenter +- A frontend in the gra zone with as default cluster in the gra zone which contains servers in the Gravelines datacenter +- A frontend in the bhs zone with a default cluster in the bhs zone that contains servers in the Beauharnois datacenter diff --git a/pages/network/load_balancer/zones/guide.en-ca.md b/pages/network/load_balancer/zones/guide.en-ca.md index e91a32ce875..f88b5ee5eba 100644 --- a/pages/network/load_balancer/zones/guide.en-ca.md +++ b/pages/network/load_balancer/zones/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Working with zones excerpt: Use zones to increase availability and decrease latency -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -68,13 +68,13 @@ This special `all` zone will allow you to deploy the same configuration on all z If the goal is to reduce latency, we can imagine directing requests coming from the zone1 load balancer to backend servers geographically close to zone1, and similarly, directing requests coming from the zone2 load balancer to backend servers close to zone2. -To achieve this, you need to specify a frontend in each zone that uses a farm in the same zone. -This will allow us to declare backend servers in different farms per zone and to control which backend servers are used in which zone. +To achieve this, you need to specify a frontend in each zone that uses a cluster in the same zone. +This will allow us to declare backend servers in different clusters per zone and to control which backend servers are used in which zone. -![Operation with several zones and several farms](images/multi_zones_multi_backends.png){.thumbnail} +![Operation with several zones and several clusters](images/multi_zones_multi_backends.png){.thumbnail} For example, if we have backend servers in the data centers of Gravelines (gra) and Beauharnois (bhs), you can order a Load Balancer service in the `gra` and `bhs` areas and configure : -- A frontend in the gra zone with as default farm in the gra zone which contains servers in the Gravelines datacenter -- A frontend in the bhs zone with a default farm in the bhs zone that contains servers in the Beauharnois datacenter +- A frontend in the gra zone with as default cluster in the gra zone which contains servers in the Gravelines datacenter +- A frontend in the bhs zone with a default cluster in the bhs zone that contains servers in the Beauharnois datacenter diff --git a/pages/network/load_balancer/zones/guide.en-gb.md b/pages/network/load_balancer/zones/guide.en-gb.md index e91a32ce875..f88b5ee5eba 100644 --- a/pages/network/load_balancer/zones/guide.en-gb.md +++ b/pages/network/load_balancer/zones/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Working with zones excerpt: Use zones to increase availability and decrease latency -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -68,13 +68,13 @@ This special `all` zone will allow you to deploy the same configuration on all z If the goal is to reduce latency, we can imagine directing requests coming from the zone1 load balancer to backend servers geographically close to zone1, and similarly, directing requests coming from the zone2 load balancer to backend servers close to zone2. -To achieve this, you need to specify a frontend in each zone that uses a farm in the same zone. -This will allow us to declare backend servers in different farms per zone and to control which backend servers are used in which zone. +To achieve this, you need to specify a frontend in each zone that uses a cluster in the same zone. +This will allow us to declare backend servers in different clusters per zone and to control which backend servers are used in which zone. -![Operation with several zones and several farms](images/multi_zones_multi_backends.png){.thumbnail} +![Operation with several zones and several clusters](images/multi_zones_multi_backends.png){.thumbnail} For example, if we have backend servers in the data centers of Gravelines (gra) and Beauharnois (bhs), you can order a Load Balancer service in the `gra` and `bhs` areas and configure : -- A frontend in the gra zone with as default farm in the gra zone which contains servers in the Gravelines datacenter -- A frontend in the bhs zone with a default farm in the bhs zone that contains servers in the Beauharnois datacenter +- A frontend in the gra zone with as default cluster in the gra zone which contains servers in the Gravelines datacenter +- A frontend in the bhs zone with a default cluster in the bhs zone that contains servers in the Beauharnois datacenter diff --git a/pages/network/load_balancer/zones/guide.en-sg.md b/pages/network/load_balancer/zones/guide.en-sg.md index e91a32ce875..f88b5ee5eba 100644 --- a/pages/network/load_balancer/zones/guide.en-sg.md +++ b/pages/network/load_balancer/zones/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Working with zones excerpt: Use zones to increase availability and decrease latency -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -68,13 +68,13 @@ This special `all` zone will allow you to deploy the same configuration on all z If the goal is to reduce latency, we can imagine directing requests coming from the zone1 load balancer to backend servers geographically close to zone1, and similarly, directing requests coming from the zone2 load balancer to backend servers close to zone2. -To achieve this, you need to specify a frontend in each zone that uses a farm in the same zone. -This will allow us to declare backend servers in different farms per zone and to control which backend servers are used in which zone. +To achieve this, you need to specify a frontend in each zone that uses a cluster in the same zone. +This will allow us to declare backend servers in different clusters per zone and to control which backend servers are used in which zone. -![Operation with several zones and several farms](images/multi_zones_multi_backends.png){.thumbnail} +![Operation with several zones and several clusters](images/multi_zones_multi_backends.png){.thumbnail} For example, if we have backend servers in the data centers of Gravelines (gra) and Beauharnois (bhs), you can order a Load Balancer service in the `gra` and `bhs` areas and configure : -- A frontend in the gra zone with as default farm in the gra zone which contains servers in the Gravelines datacenter -- A frontend in the bhs zone with a default farm in the bhs zone that contains servers in the Beauharnois datacenter +- A frontend in the gra zone with as default cluster in the gra zone which contains servers in the Gravelines datacenter +- A frontend in the bhs zone with a default cluster in the bhs zone that contains servers in the Beauharnois datacenter diff --git a/pages/network/load_balancer/zones/guide.en-us.md b/pages/network/load_balancer/zones/guide.en-us.md index e91a32ce875..f88b5ee5eba 100644 --- a/pages/network/load_balancer/zones/guide.en-us.md +++ b/pages/network/load_balancer/zones/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Working with zones excerpt: Use zones to increase availability and decrease latency -updated: 2022-04-04 +updated: 2025-07-04 --- ## Introduction @@ -68,13 +68,13 @@ This special `all` zone will allow you to deploy the same configuration on all z If the goal is to reduce latency, we can imagine directing requests coming from the zone1 load balancer to backend servers geographically close to zone1, and similarly, directing requests coming from the zone2 load balancer to backend servers close to zone2. -To achieve this, you need to specify a frontend in each zone that uses a farm in the same zone. -This will allow us to declare backend servers in different farms per zone and to control which backend servers are used in which zone. +To achieve this, you need to specify a frontend in each zone that uses a cluster in the same zone. +This will allow us to declare backend servers in different clusters per zone and to control which backend servers are used in which zone. -![Operation with several zones and several farms](images/multi_zones_multi_backends.png){.thumbnail} +![Operation with several zones and several clusters](images/multi_zones_multi_backends.png){.thumbnail} For example, if we have backend servers in the data centers of Gravelines (gra) and Beauharnois (bhs), you can order a Load Balancer service in the `gra` and `bhs` areas and configure : -- A frontend in the gra zone with as default farm in the gra zone which contains servers in the Gravelines datacenter -- A frontend in the bhs zone with a default farm in the bhs zone that contains servers in the Beauharnois datacenter +- A frontend in the gra zone with as default cluster in the gra zone which contains servers in the Gravelines datacenter +- A frontend in the bhs zone with a default cluster in the bhs zone that contains servers in the Beauharnois datacenter From 0108bf840ced9c3882c8b56791df335bb2ed5f52 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 4 Jul 2025 17:34:06 +0200 Subject: [PATCH 3/4] Control Panel steps Added the steps that were already present in the FR version of the document. --- .../load_balancer/zones/guide.en-gb.md | 38 ++++++++++++++++++- 1 file changed, 36 insertions(+), 2 deletions(-) diff --git a/pages/network/load_balancer/zones/guide.en-gb.md b/pages/network/load_balancer/zones/guide.en-gb.md index f88b5ee5eba..eef36e4fada 100644 --- a/pages/network/load_balancer/zones/guide.en-gb.md +++ b/pages/network/load_balancer/zones/guide.en-gb.md @@ -14,9 +14,27 @@ This increases the availability of your Load Balancer service in case a zone is It is also possible, if configured appropriately, to use multiple zones to minimize latency for your visitors. -## Add a zone +## Instructions -### From the API +### Add a zone + +#### From the OVHcloud Control Panel + +You can order an additional zone from the [OVHcloud Control Panel](/manager) in the `Bare Metal Cloud`{.action} section, then `Load Balancer`{.action}. + +Select your Load Balancer, then in the `Home`{.action} tab and the `Configuration`{.action} menu, click `Add`{.action} in the "Availability zones" section. + +![Add a Load Balancer zone from the manager](images/add_Zone_IPLB.png){.thumbnail} + +Then select the zone(s) you wish to order and click `Add`{.action}. +  +![Selection of a Load Balancer zone from the manager](images/Select_Zone_IPLB.png){.thumbnail} + +A purchase order will be generated, which you'll need to pay. + +![Pay the Load Balancer zone order from the manager](images/Paybill_Zone_IPLB.png){.thumbnail} + +#### From the API To order a zone via the API, you first need to create a cart. @@ -56,6 +74,22 @@ Finally, you can validate your cart ("cart") via Don't forget to pay the order form thus generated. +### Add a zone + +Once your zone order is finalized, you can add it from your OVHcloud Control Panel. + +Select the Load Balancer you wish to modify, then create a new frontend, or edit an existing one, via the `Frontends`{.action} tab. + +In the `Datacenter`{.action} field, choose the zone you wish to associate with your frontend. + +![Zone selection](images/Select-Datacenter.png){.thumbnail} + +Once the frontend is configured, click `Add`{.action} or `Modify`{.action} depending on whether you are configuring a new frontend or an existing one. + +Don't forget to deploy the configuration. To do this, click `Apply configuration`{.action} in the reminder banner stating that the configuration is not applied. + +![Applying a Load Balancer Configuration](images/apply-configuration.PNG){.thumbnail} + ## Use multiple zones ### For high availability From 86097ac6c85a1d4a33799e37ef3d88cfb4791362 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 11 Jul 2025 16:27:43 +0200 Subject: [PATCH 4/4] ProxyProtocol Article update The EN versions had not been kept on par with the FR versions. --- .../create_proxyprotocol/guide.en-asia.md | 378 ++++++++++++------ .../create_proxyprotocol/guide.en-au.md | 378 ++++++++++++------ .../create_proxyprotocol/guide.en-ca.md | 378 ++++++++++++------ .../create_proxyprotocol/guide.en-gb.md | 378 ++++++++++++------ .../create_proxyprotocol/guide.en-sg.md | 378 ++++++++++++------ .../create_proxyprotocol/guide.en-us.md | 378 ++++++++++++------ .../create_proxyprotocol/guide.fr-ca.md | 147 ++++--- .../create_proxyprotocol/guide.fr-fr.md | 12 +- 8 files changed, 1573 insertions(+), 854 deletions(-) diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-asia.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-asia.md index c71907b8d17..2ebb05b2e40 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-asia.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-asia.md @@ -1,161 +1,277 @@ --- -title: ProxyProtocol get Source IP -excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2025-07-04 +title: "Configuring an OVHcloud Load Balancer with ProxyProtocol" +excerpt: Integrate your TCP services behind a Load Balancer with ProxyProtocol +updated: 2025-07-11 --- -## Introduction -In this case, we want to get sourceIP, scheme trouth OVH API LoadBalancing, without install our SSL Certitificate on it. This is helpful if you have many domains with many SSL certificates. +## Objective -## Requirements -We assume you have already an OVH Load Balancer HTTP configured, if not follow ..refs:fr/fr/cloud/iplb/configure-iplb +The OVHcloud Load Balancer acts as a proxy. Like a human proxy, it acts as an intermediary, so the client addresses the proxy and the proxy addresses the service provider, on behalf of the client. In this configuration, only the proxy knows both the true client (the user of your service) and the true service provider (one of your servers). -You have : +For the visitor, this isn't an issue. They don't need to know the exact server responding to their request; that's an implementation detail. However, for statistical and security reasons, it's sometimes essential for the final server to know the client's true address. By default, it only sees the proxy (in this case, your OVHcloud Load Balancer service). -- An OVH Load Balancer service -- Nginx (or Apache with mod_proxyprotocol) on an OVH backend -- A domain (option) -- An SSL certificate (option) +If you are using an HTTP frontend, we recommend the guide "[Configuring an OVHcloud Load Balancer service - HTTP Headers](/pages/network/load_balancer/create_headers)" which describes the standard way to use HTTP headers to retrieve the IP address, port, and source protocol. -### Nginx Configuration -For this example we use this minimal nginx configuration on each backend. +**If you are using a TCP frontend, then this guide is for you.** -```bash -log_format proxyprotocol '$proxy_protocol_addr - $remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" "$request_time"'; -server { - listen 80; - listen [::]:80; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 443 ssl; - listen [::]:443 ssl; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 8080 proxyprotocol; - listen [::]:8080 proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -server { - listen 4443 ssl proxyprotocol; - listen [::]:4443 ssl proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -``` +## Legal Obligations -- Port 80 / 443 are used for direct connexion to backend (for test, management, ...) -- Port 8080 / 4443 are used with LoadBalancer +You may be required to retain logs and certain traffic data under applicable laws and regulations. It is your responsibility to comply with these obligations. -You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren't cross-compatible. +**For example:** -### Infrastructure -|Backend#|Public IP|Zone| -|---|---|---| -|backend_1|213.186.0.1|rbx| -|backend_2|213.186.0.2|rbx| +- [Investigatory Powers Act 2016 (IPA), Section 87](https://www.legislation.gov.uk/ukpga/2016/25/section/87): This section notably empowers the Secretary of State, with Judicial Commissioner approval, to require telecommunications operators to retain "relevant communications data" for up to 12 months. This data is broadly defined but includes information to identify the source and destination of a communication, its date, time, and duration, and specifically covers **Internet Connection Records (ICRs)**, which log website visits and app usage. This requirement is for purposes such as national security and preventing/detecting serious crime. -## Configuration +## Prerequisites -### Add backends -Create a new cluster for each port on backend. +This is an advanced guide. It assumes you're already familiar with the main features of your OVHcloud Load Balancer service, especially **frontends** and **clusters**. If you're not, we recommend checking out the guide "[Configure an OVHcloud Load Balancer HTTP/HTTPS service](/pages/network/load_balancer/create_http_https)." While this guide focuses more on TCP services, the general principles are the same. -> [!api] +You need: + +- an OVHcloud Load Balancer service with a functional TCP frontend and farm; +- Nginx or Apache with mod_proxyprotocol on an OVHcloud server. + +> [!warning] +> Since ProxyProtocol fields can be forged by a malicious client, they should only be considered if they come from a trusted source. > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|balance|roundrobin|roundrobin| -|port|8080|4443| -|probe|tcp|tcp| -|stickiness|sourceIP|sourceIP| -|zone *|rbx|rbx| - -|Parameter|Return 1|Return 2| -|---|---|---| -|id|1000|10001| +> Therefore, it's essential to limit their use to trusted IP addresses, specifically the outbound IP addresses of your OVHcloud Load Balancer service. Major servers like Nginx and Apache have modules capable of managing this security and trust aspect. + +## In Practice + +### Obtaining the list of your outbound IP addresses + +#### From the OVHcloud Control Panel + +The list of IPv4 outbound addresses potentially used by your OVHcloud Load Balancer service can be found on the homepage of your OVHcloud Load Balancer service under "Outbound IPv4". + +![Outbound IPv4 address of your OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} + +#### From the OVHcloud API + +- List of IP addresses used by your OVHcloud Load Balancer service: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server -> -|Parameter|Call 1|Call 2|Call 3|Call 4| -|---|---|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4|ip.1.2.3.4|ip.1.2.3.4| -|farmId *|1000|1000|1001|1001| -|address *|213.186.0.1|213.186.0.2|213.186.0.1|213.186.0.2| -|backup|false|false|false|false| -|chain||||| -|cookie||||| -|port||||| -|probe|true|true|true|true| -|proxyProtocolVersion|v1|v1|v1|v1| -|ssl|false|false|false|false| -|status *|active|active|active|active| -|weight|1|1|1|1| - -|Parameter|Return 1|Return 2|Return 3|Return 4| -|---|---|---|---|---| -|id|2000|20001|20002|20003| - -### Add frontend +> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp +> + +### Introduction to ProxyProtocol + +ProxyProtocol was developed by the [HAProxy](http://haproxy.org/){.external} Load Balancer team as the TCP counterpart to standard HTTP headers like X-Forwarded-For. It was designed to forward at minimum: + +- the L4 protocol name used (TCP4 for IPv4 or TCP6 for IPv6); +- the source IPv4 or IPv6 address; +- the source port. + +When ProxyProtocol is enabled for one of your servers, the OVHcloud Load Balancer service adds a prefix with the ProxyProtocol before sending the rest of the request. Since this modification is intrusive, it is essential to ensure that the server is compatible with this protocol, and if so, which versions are supported. + +Indeed, this protocol exists in 2 versions: + +- version 1, in text format; +- version 2, in optimized and extensible binary format. + +Version 1 is largely sufficient for most uses (although less optimized) and is often the only version supported by compatible software. Version 2, being a binary format, is faster to parse. It also adds the ability to indicate whether the original connection was encrypted (the equivalent of the X-Forwarded-Proto header) as well as the domain specified in the Common Name field of the certificate used, if applicable. + +To learn more about ProxyProtocol, please consult the [ProxyProtocol specification](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. + +### Activating ProxyProtocol for one of your servers + +ProxyProtocol must be enabled for each server registered in a server farm. Since this feature is intrusive and cannot be activated transparently, this allows you to test it on a particular machine and then progressively deploy the configuration to an active farm. + +Your OVHcloud Load Balancer service supports 4 ProxyProtocol modes: + +| Mode | Description | +|---|---| +| v1 | Version 1 in text format. This is the most widely supported version. | +| v2 | Version 2 in binary format without any options. This is an optimized version of version 1. | +| v2-ssl | v2, with a field describing the SSL connection, if applicable. | +| v2-ssl-cn | v2-ssl, with the "Common Name" field of the certificate used, if applicable. | + +When ProxyProtocol is enabled for one of your servers, probes automatically insert this header **unless** a specific port has been specified for the probes. In this case, the probe will connect normally to the probe port. + +#### From the OVHcloud Control Panel + +In the `Clusters`{.action} section, select the farm containing the server on which to enable ProxyProtocol, then click the edit button for the relevant server. + +ProxyProtocol is configured via the `ProxyProtocol version`{.action} option. You will find the 4 modes described above. + +![Activating ProxyProtocol on a server in a farm](images/edit_server.png){.thumbnail} + +Once the desired mode is selected, click `Update`{.action}, then `Deploy zone: YOUR ZONE`{.action} to apply your changes in the relevant zone. + +#### From the OVHcloud API + +Activating ProxyProtocol via the API is done in the same way as from the OVHcloud Control Panel. +The corresponding API field in the server is proxyProtocolVersion. + +- Modify an existing `Server`{.action}: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|allowedSource||| -|dedicatedIpfo||| -|defaultBackendId|1000|1001| -|defaultSslId||| -|disabled|false|false| -|hsts||| -|httpHeader||| -|port *|80|443| -|redirectLocation||| -|ssl||| -|zone *|rbx|rbx| - -### Apply changes +> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server/{serverId} +> + +- Apply changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> -### Firewall -Don't forget to allow IPLoadbalancing traffic to your backends: +### Server-side ProxyProtocol configuration -> [!api] +#### Nginx + +Nginx supports ProxyProtocol version 1. It can extract the main information from it, namely the client's IP address and source port as seen by your OVHcloud Load Balancer service. In Nginx, this information is exposed through the `proxy_protocol_addr` variable. Similar to its HTTP counterpart `X-Forwarded-For`, Nginx will use this variable to take the correct source address into account in the logs with the `ngx_http_realip` module. + +To use ProxyProtocol with Nginx, you can configure the server section of your configuration with: + +```nginx +1. server { +2. # Enable the Proxy protocol on port 80 +3. listen 80 proxy_protocol; +4. +5. # Trust the proxy protocol provided informations from your OVHcloud Load Balancer service +6. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +7. set_real_ip_from 10.108.0.0/14; +8. real_ip_header proxy_protocol; +9. +10. # (optional) Set some headers +11. proxy_set_header X-Real-IP $proxy_protocol_addr; +12. proxy_set_header X-Forwarded-For $proxy_protocol_addr; +13. +14. # Insert your regular configuration here +15. ... +16. } +``` + +Once configured, you can reload the configuration: + +```bash +service nginx reload +``` + +> [!primary] +> +> This example uses the HTTP protocol for more simplicity. If you are using HTTP, we strongly recommend using HTTP headers instead of ProxyProtocol, unless your OVHcloud Load Balancer service is configured in TCP. This can happen in the case of SSL termination for HTTP/2, for example. > -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp -> -Get IP range used by OVH Load Balancer: 10.108.0.0/16 + +For more information on configuring ProxyProtocol in Nginx, please consult the project's official documentation: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external} + +#### Apache + +The management of ProxyProtocol in Apache is still young. An unofficial implementation compatible with Apache 2.4 is available on Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) but has not been maintained since 2014. An official implementation is found in the `mod_remoteip` module which is also used to manage headers from the X-Forwarded-For family. + +`mod-proxy-protocol` supports ProxyProtocol versions 1 and 2. However, it does not allow specifying a list of source IP addresses authorized to use ProxyProtocol, although this is mentioned in the module's projects. + +`mod_remoteip` also supports ProxyProtocol versions 1 and 2. It also adds the ability to specify a list of addresses for which ProxyProtocol should not be enabled. This remains limiting from a configuration perspective. This module is only available in the experimental Apache 2.5 version, although the documentation mentions availability from Apache 2.4.26. + +Regardless of the approach chosen, we strongly recommend restricting connections to your servers to the outbound addresses of your OVHcloud Load Balancer service. +This can be easily configured with `iptables`: ```bash -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 8080 -j ACCEPT -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 4443 -j ACCEPT -``` \ No newline at end of file +# Trust connections from your OVHcloud Load Balancer service, ONLY +iptables -A INPUT -s 10.108.0.0/14 -p tcp --dport 80 -j ACCEPT +iptables -A INPUT -p tcp --dport 80 -j DROP +``` + +##### **With mod-proxy-protocol** + +- Since this module is unofficial, you will first need to download the sources, compile, and install it: + +```bash +# Install build tools +sudo apt install git apache2-dev + +# Grab the sources +git clone [https://github.com/roadrunner2/mod-proxy-protocol.git](https://github.com/roadrunner2/mod-proxy-protocol.git) +cd mod-proxy-protocol + +# Build and install the module +sudo apxs -i -a -c mod_proxy_protocol.c +``` + +- Then configure Apache: + +```apache +1. +2. ProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod-proxy-protocol` module, please consult [its documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. + +##### **With mod_remoteip** + +- Since the module is experimental, you will first need to install an experimental version of Apache, which is not recommended in a production environment unless you know exactly what you're doing! +- Then configure Apache: + +```apache +1. +2. RemoteIPProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Enable the 'remoteip' module and configuration +a2enmod remoteip + +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod_remoteip` module, please consult [its documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. + +#### HAProxy + +ProxyProtocol was designed by the HAProxy team, making it the software that best manages this protocol. This can be useful in a scenario where tracking the client's true source IP address is essential, but the target software does not support this protocol. This would be the case, for example, for MySQL and PostgreSQL, to name just two. + +In this case, a trick is to place a local HAProxy instance in front of the software and ensure logging of requests and their advanced filtering in the local HAProxy instance. + +This guide provides an example of a possible configuration for TCP port 3306 used by MySQL. This configuration is not intended to be a complete example but rather to serve as a basis for a functional setup. + +- Install HAProxy + +```bash +sudo apt install haproxy +``` + +- Configure your proxy + +```haproxy +1. listen mysql +2. # Listen on all interfaces, port 3306, tcp mode (ie: not HTTP) +3. mode tcp +4. option tcplog +5. bind *:3306 +6. +7. # Expect ProxyProtocol header if and only if from a trusted network +8. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +9. tcp-request connection expect-proxy layer4 if { src 10.108.0.0/14 } +10. +11. # Declare local server, on a non standard port to avoid collisions +12. server mysql 127.0.0.1:3316 check +``` + +- Finally, activate the new configuration with: + +```bash +service haproxy reload +``` + +## Go Further + +Discuss with our [user community](/links/community). diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-au.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-au.md index c71907b8d17..2ebb05b2e40 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-au.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-au.md @@ -1,161 +1,277 @@ --- -title: ProxyProtocol get Source IP -excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2025-07-04 +title: "Configuring an OVHcloud Load Balancer with ProxyProtocol" +excerpt: Integrate your TCP services behind a Load Balancer with ProxyProtocol +updated: 2025-07-11 --- -## Introduction -In this case, we want to get sourceIP, scheme trouth OVH API LoadBalancing, without install our SSL Certitificate on it. This is helpful if you have many domains with many SSL certificates. +## Objective -## Requirements -We assume you have already an OVH Load Balancer HTTP configured, if not follow ..refs:fr/fr/cloud/iplb/configure-iplb +The OVHcloud Load Balancer acts as a proxy. Like a human proxy, it acts as an intermediary, so the client addresses the proxy and the proxy addresses the service provider, on behalf of the client. In this configuration, only the proxy knows both the true client (the user of your service) and the true service provider (one of your servers). -You have : +For the visitor, this isn't an issue. They don't need to know the exact server responding to their request; that's an implementation detail. However, for statistical and security reasons, it's sometimes essential for the final server to know the client's true address. By default, it only sees the proxy (in this case, your OVHcloud Load Balancer service). -- An OVH Load Balancer service -- Nginx (or Apache with mod_proxyprotocol) on an OVH backend -- A domain (option) -- An SSL certificate (option) +If you are using an HTTP frontend, we recommend the guide "[Configuring an OVHcloud Load Balancer service - HTTP Headers](/pages/network/load_balancer/create_headers)" which describes the standard way to use HTTP headers to retrieve the IP address, port, and source protocol. -### Nginx Configuration -For this example we use this minimal nginx configuration on each backend. +**If you are using a TCP frontend, then this guide is for you.** -```bash -log_format proxyprotocol '$proxy_protocol_addr - $remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" "$request_time"'; -server { - listen 80; - listen [::]:80; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 443 ssl; - listen [::]:443 ssl; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 8080 proxyprotocol; - listen [::]:8080 proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -server { - listen 4443 ssl proxyprotocol; - listen [::]:4443 ssl proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -``` +## Legal Obligations -- Port 80 / 443 are used for direct connexion to backend (for test, management, ...) -- Port 8080 / 4443 are used with LoadBalancer +You may be required to retain logs and certain traffic data under applicable laws and regulations. It is your responsibility to comply with these obligations. -You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren't cross-compatible. +**For example:** -### Infrastructure -|Backend#|Public IP|Zone| -|---|---|---| -|backend_1|213.186.0.1|rbx| -|backend_2|213.186.0.2|rbx| +- [Investigatory Powers Act 2016 (IPA), Section 87](https://www.legislation.gov.uk/ukpga/2016/25/section/87): This section notably empowers the Secretary of State, with Judicial Commissioner approval, to require telecommunications operators to retain "relevant communications data" for up to 12 months. This data is broadly defined but includes information to identify the source and destination of a communication, its date, time, and duration, and specifically covers **Internet Connection Records (ICRs)**, which log website visits and app usage. This requirement is for purposes such as national security and preventing/detecting serious crime. -## Configuration +## Prerequisites -### Add backends -Create a new cluster for each port on backend. +This is an advanced guide. It assumes you're already familiar with the main features of your OVHcloud Load Balancer service, especially **frontends** and **clusters**. If you're not, we recommend checking out the guide "[Configure an OVHcloud Load Balancer HTTP/HTTPS service](/pages/network/load_balancer/create_http_https)." While this guide focuses more on TCP services, the general principles are the same. -> [!api] +You need: + +- an OVHcloud Load Balancer service with a functional TCP frontend and farm; +- Nginx or Apache with mod_proxyprotocol on an OVHcloud server. + +> [!warning] +> Since ProxyProtocol fields can be forged by a malicious client, they should only be considered if they come from a trusted source. > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|balance|roundrobin|roundrobin| -|port|8080|4443| -|probe|tcp|tcp| -|stickiness|sourceIP|sourceIP| -|zone *|rbx|rbx| - -|Parameter|Return 1|Return 2| -|---|---|---| -|id|1000|10001| +> Therefore, it's essential to limit their use to trusted IP addresses, specifically the outbound IP addresses of your OVHcloud Load Balancer service. Major servers like Nginx and Apache have modules capable of managing this security and trust aspect. + +## In Practice + +### Obtaining the list of your outbound IP addresses + +#### From the OVHcloud Control Panel + +The list of IPv4 outbound addresses potentially used by your OVHcloud Load Balancer service can be found on the homepage of your OVHcloud Load Balancer service under "Outbound IPv4". + +![Outbound IPv4 address of your OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} + +#### From the OVHcloud API + +- List of IP addresses used by your OVHcloud Load Balancer service: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server -> -|Parameter|Call 1|Call 2|Call 3|Call 4| -|---|---|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4|ip.1.2.3.4|ip.1.2.3.4| -|farmId *|1000|1000|1001|1001| -|address *|213.186.0.1|213.186.0.2|213.186.0.1|213.186.0.2| -|backup|false|false|false|false| -|chain||||| -|cookie||||| -|port||||| -|probe|true|true|true|true| -|proxyProtocolVersion|v1|v1|v1|v1| -|ssl|false|false|false|false| -|status *|active|active|active|active| -|weight|1|1|1|1| - -|Parameter|Return 1|Return 2|Return 3|Return 4| -|---|---|---|---|---| -|id|2000|20001|20002|20003| - -### Add frontend +> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp +> + +### Introduction to ProxyProtocol + +ProxyProtocol was developed by the [HAProxy](http://haproxy.org/){.external} Load Balancer team as the TCP counterpart to standard HTTP headers like X-Forwarded-For. It was designed to forward at minimum: + +- the L4 protocol name used (TCP4 for IPv4 or TCP6 for IPv6); +- the source IPv4 or IPv6 address; +- the source port. + +When ProxyProtocol is enabled for one of your servers, the OVHcloud Load Balancer service adds a prefix with the ProxyProtocol before sending the rest of the request. Since this modification is intrusive, it is essential to ensure that the server is compatible with this protocol, and if so, which versions are supported. + +Indeed, this protocol exists in 2 versions: + +- version 1, in text format; +- version 2, in optimized and extensible binary format. + +Version 1 is largely sufficient for most uses (although less optimized) and is often the only version supported by compatible software. Version 2, being a binary format, is faster to parse. It also adds the ability to indicate whether the original connection was encrypted (the equivalent of the X-Forwarded-Proto header) as well as the domain specified in the Common Name field of the certificate used, if applicable. + +To learn more about ProxyProtocol, please consult the [ProxyProtocol specification](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. + +### Activating ProxyProtocol for one of your servers + +ProxyProtocol must be enabled for each server registered in a server farm. Since this feature is intrusive and cannot be activated transparently, this allows you to test it on a particular machine and then progressively deploy the configuration to an active farm. + +Your OVHcloud Load Balancer service supports 4 ProxyProtocol modes: + +| Mode | Description | +|---|---| +| v1 | Version 1 in text format. This is the most widely supported version. | +| v2 | Version 2 in binary format without any options. This is an optimized version of version 1. | +| v2-ssl | v2, with a field describing the SSL connection, if applicable. | +| v2-ssl-cn | v2-ssl, with the "Common Name" field of the certificate used, if applicable. | + +When ProxyProtocol is enabled for one of your servers, probes automatically insert this header **unless** a specific port has been specified for the probes. In this case, the probe will connect normally to the probe port. + +#### From the OVHcloud Control Panel + +In the `Clusters`{.action} section, select the farm containing the server on which to enable ProxyProtocol, then click the edit button for the relevant server. + +ProxyProtocol is configured via the `ProxyProtocol version`{.action} option. You will find the 4 modes described above. + +![Activating ProxyProtocol on a server in a farm](images/edit_server.png){.thumbnail} + +Once the desired mode is selected, click `Update`{.action}, then `Deploy zone: YOUR ZONE`{.action} to apply your changes in the relevant zone. + +#### From the OVHcloud API + +Activating ProxyProtocol via the API is done in the same way as from the OVHcloud Control Panel. +The corresponding API field in the server is proxyProtocolVersion. + +- Modify an existing `Server`{.action}: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|allowedSource||| -|dedicatedIpfo||| -|defaultBackendId|1000|1001| -|defaultSslId||| -|disabled|false|false| -|hsts||| -|httpHeader||| -|port *|80|443| -|redirectLocation||| -|ssl||| -|zone *|rbx|rbx| - -### Apply changes +> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server/{serverId} +> + +- Apply changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> -### Firewall -Don't forget to allow IPLoadbalancing traffic to your backends: +### Server-side ProxyProtocol configuration -> [!api] +#### Nginx + +Nginx supports ProxyProtocol version 1. It can extract the main information from it, namely the client's IP address and source port as seen by your OVHcloud Load Balancer service. In Nginx, this information is exposed through the `proxy_protocol_addr` variable. Similar to its HTTP counterpart `X-Forwarded-For`, Nginx will use this variable to take the correct source address into account in the logs with the `ngx_http_realip` module. + +To use ProxyProtocol with Nginx, you can configure the server section of your configuration with: + +```nginx +1. server { +2. # Enable the Proxy protocol on port 80 +3. listen 80 proxy_protocol; +4. +5. # Trust the proxy protocol provided informations from your OVHcloud Load Balancer service +6. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +7. set_real_ip_from 10.108.0.0/14; +8. real_ip_header proxy_protocol; +9. +10. # (optional) Set some headers +11. proxy_set_header X-Real-IP $proxy_protocol_addr; +12. proxy_set_header X-Forwarded-For $proxy_protocol_addr; +13. +14. # Insert your regular configuration here +15. ... +16. } +``` + +Once configured, you can reload the configuration: + +```bash +service nginx reload +``` + +> [!primary] +> +> This example uses the HTTP protocol for more simplicity. If you are using HTTP, we strongly recommend using HTTP headers instead of ProxyProtocol, unless your OVHcloud Load Balancer service is configured in TCP. This can happen in the case of SSL termination for HTTP/2, for example. > -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp -> -Get IP range used by OVH Load Balancer: 10.108.0.0/16 + +For more information on configuring ProxyProtocol in Nginx, please consult the project's official documentation: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external} + +#### Apache + +The management of ProxyProtocol in Apache is still young. An unofficial implementation compatible with Apache 2.4 is available on Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) but has not been maintained since 2014. An official implementation is found in the `mod_remoteip` module which is also used to manage headers from the X-Forwarded-For family. + +`mod-proxy-protocol` supports ProxyProtocol versions 1 and 2. However, it does not allow specifying a list of source IP addresses authorized to use ProxyProtocol, although this is mentioned in the module's projects. + +`mod_remoteip` also supports ProxyProtocol versions 1 and 2. It also adds the ability to specify a list of addresses for which ProxyProtocol should not be enabled. This remains limiting from a configuration perspective. This module is only available in the experimental Apache 2.5 version, although the documentation mentions availability from Apache 2.4.26. + +Regardless of the approach chosen, we strongly recommend restricting connections to your servers to the outbound addresses of your OVHcloud Load Balancer service. +This can be easily configured with `iptables`: ```bash -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 8080 -j ACCEPT -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 4443 -j ACCEPT -``` \ No newline at end of file +# Trust connections from your OVHcloud Load Balancer service, ONLY +iptables -A INPUT -s 10.108.0.0/14 -p tcp --dport 80 -j ACCEPT +iptables -A INPUT -p tcp --dport 80 -j DROP +``` + +##### **With mod-proxy-protocol** + +- Since this module is unofficial, you will first need to download the sources, compile, and install it: + +```bash +# Install build tools +sudo apt install git apache2-dev + +# Grab the sources +git clone [https://github.com/roadrunner2/mod-proxy-protocol.git](https://github.com/roadrunner2/mod-proxy-protocol.git) +cd mod-proxy-protocol + +# Build and install the module +sudo apxs -i -a -c mod_proxy_protocol.c +``` + +- Then configure Apache: + +```apache +1. +2. ProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod-proxy-protocol` module, please consult [its documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. + +##### **With mod_remoteip** + +- Since the module is experimental, you will first need to install an experimental version of Apache, which is not recommended in a production environment unless you know exactly what you're doing! +- Then configure Apache: + +```apache +1. +2. RemoteIPProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Enable the 'remoteip' module and configuration +a2enmod remoteip + +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod_remoteip` module, please consult [its documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. + +#### HAProxy + +ProxyProtocol was designed by the HAProxy team, making it the software that best manages this protocol. This can be useful in a scenario where tracking the client's true source IP address is essential, but the target software does not support this protocol. This would be the case, for example, for MySQL and PostgreSQL, to name just two. + +In this case, a trick is to place a local HAProxy instance in front of the software and ensure logging of requests and their advanced filtering in the local HAProxy instance. + +This guide provides an example of a possible configuration for TCP port 3306 used by MySQL. This configuration is not intended to be a complete example but rather to serve as a basis for a functional setup. + +- Install HAProxy + +```bash +sudo apt install haproxy +``` + +- Configure your proxy + +```haproxy +1. listen mysql +2. # Listen on all interfaces, port 3306, tcp mode (ie: not HTTP) +3. mode tcp +4. option tcplog +5. bind *:3306 +6. +7. # Expect ProxyProtocol header if and only if from a trusted network +8. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +9. tcp-request connection expect-proxy layer4 if { src 10.108.0.0/14 } +10. +11. # Declare local server, on a non standard port to avoid collisions +12. server mysql 127.0.0.1:3316 check +``` + +- Finally, activate the new configuration with: + +```bash +service haproxy reload +``` + +## Go Further + +Discuss with our [user community](/links/community). diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-ca.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-ca.md index c71907b8d17..2ebb05b2e40 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-ca.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-ca.md @@ -1,161 +1,277 @@ --- -title: ProxyProtocol get Source IP -excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2025-07-04 +title: "Configuring an OVHcloud Load Balancer with ProxyProtocol" +excerpt: Integrate your TCP services behind a Load Balancer with ProxyProtocol +updated: 2025-07-11 --- -## Introduction -In this case, we want to get sourceIP, scheme trouth OVH API LoadBalancing, without install our SSL Certitificate on it. This is helpful if you have many domains with many SSL certificates. +## Objective -## Requirements -We assume you have already an OVH Load Balancer HTTP configured, if not follow ..refs:fr/fr/cloud/iplb/configure-iplb +The OVHcloud Load Balancer acts as a proxy. Like a human proxy, it acts as an intermediary, so the client addresses the proxy and the proxy addresses the service provider, on behalf of the client. In this configuration, only the proxy knows both the true client (the user of your service) and the true service provider (one of your servers). -You have : +For the visitor, this isn't an issue. They don't need to know the exact server responding to their request; that's an implementation detail. However, for statistical and security reasons, it's sometimes essential for the final server to know the client's true address. By default, it only sees the proxy (in this case, your OVHcloud Load Balancer service). -- An OVH Load Balancer service -- Nginx (or Apache with mod_proxyprotocol) on an OVH backend -- A domain (option) -- An SSL certificate (option) +If you are using an HTTP frontend, we recommend the guide "[Configuring an OVHcloud Load Balancer service - HTTP Headers](/pages/network/load_balancer/create_headers)" which describes the standard way to use HTTP headers to retrieve the IP address, port, and source protocol. -### Nginx Configuration -For this example we use this minimal nginx configuration on each backend. +**If you are using a TCP frontend, then this guide is for you.** -```bash -log_format proxyprotocol '$proxy_protocol_addr - $remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" "$request_time"'; -server { - listen 80; - listen [::]:80; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 443 ssl; - listen [::]:443 ssl; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 8080 proxyprotocol; - listen [::]:8080 proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -server { - listen 4443 ssl proxyprotocol; - listen [::]:4443 ssl proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -``` +## Legal Obligations -- Port 80 / 443 are used for direct connexion to backend (for test, management, ...) -- Port 8080 / 4443 are used with LoadBalancer +You may be required to retain logs and certain traffic data under applicable laws and regulations. It is your responsibility to comply with these obligations. -You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren't cross-compatible. +**For example:** -### Infrastructure -|Backend#|Public IP|Zone| -|---|---|---| -|backend_1|213.186.0.1|rbx| -|backend_2|213.186.0.2|rbx| +- [Investigatory Powers Act 2016 (IPA), Section 87](https://www.legislation.gov.uk/ukpga/2016/25/section/87): This section notably empowers the Secretary of State, with Judicial Commissioner approval, to require telecommunications operators to retain "relevant communications data" for up to 12 months. This data is broadly defined but includes information to identify the source and destination of a communication, its date, time, and duration, and specifically covers **Internet Connection Records (ICRs)**, which log website visits and app usage. This requirement is for purposes such as national security and preventing/detecting serious crime. -## Configuration +## Prerequisites -### Add backends -Create a new cluster for each port on backend. +This is an advanced guide. It assumes you're already familiar with the main features of your OVHcloud Load Balancer service, especially **frontends** and **clusters**. If you're not, we recommend checking out the guide "[Configure an OVHcloud Load Balancer HTTP/HTTPS service](/pages/network/load_balancer/create_http_https)." While this guide focuses more on TCP services, the general principles are the same. -> [!api] +You need: + +- an OVHcloud Load Balancer service with a functional TCP frontend and farm; +- Nginx or Apache with mod_proxyprotocol on an OVHcloud server. + +> [!warning] +> Since ProxyProtocol fields can be forged by a malicious client, they should only be considered if they come from a trusted source. > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|balance|roundrobin|roundrobin| -|port|8080|4443| -|probe|tcp|tcp| -|stickiness|sourceIP|sourceIP| -|zone *|rbx|rbx| - -|Parameter|Return 1|Return 2| -|---|---|---| -|id|1000|10001| +> Therefore, it's essential to limit their use to trusted IP addresses, specifically the outbound IP addresses of your OVHcloud Load Balancer service. Major servers like Nginx and Apache have modules capable of managing this security and trust aspect. + +## In Practice + +### Obtaining the list of your outbound IP addresses + +#### From the OVHcloud Control Panel + +The list of IPv4 outbound addresses potentially used by your OVHcloud Load Balancer service can be found on the homepage of your OVHcloud Load Balancer service under "Outbound IPv4". + +![Outbound IPv4 address of your OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} + +#### From the OVHcloud API + +- List of IP addresses used by your OVHcloud Load Balancer service: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server -> -|Parameter|Call 1|Call 2|Call 3|Call 4| -|---|---|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4|ip.1.2.3.4|ip.1.2.3.4| -|farmId *|1000|1000|1001|1001| -|address *|213.186.0.1|213.186.0.2|213.186.0.1|213.186.0.2| -|backup|false|false|false|false| -|chain||||| -|cookie||||| -|port||||| -|probe|true|true|true|true| -|proxyProtocolVersion|v1|v1|v1|v1| -|ssl|false|false|false|false| -|status *|active|active|active|active| -|weight|1|1|1|1| - -|Parameter|Return 1|Return 2|Return 3|Return 4| -|---|---|---|---|---| -|id|2000|20001|20002|20003| - -### Add frontend +> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp +> + +### Introduction to ProxyProtocol + +ProxyProtocol was developed by the [HAProxy](http://haproxy.org/){.external} Load Balancer team as the TCP counterpart to standard HTTP headers like X-Forwarded-For. It was designed to forward at minimum: + +- the L4 protocol name used (TCP4 for IPv4 or TCP6 for IPv6); +- the source IPv4 or IPv6 address; +- the source port. + +When ProxyProtocol is enabled for one of your servers, the OVHcloud Load Balancer service adds a prefix with the ProxyProtocol before sending the rest of the request. Since this modification is intrusive, it is essential to ensure that the server is compatible with this protocol, and if so, which versions are supported. + +Indeed, this protocol exists in 2 versions: + +- version 1, in text format; +- version 2, in optimized and extensible binary format. + +Version 1 is largely sufficient for most uses (although less optimized) and is often the only version supported by compatible software. Version 2, being a binary format, is faster to parse. It also adds the ability to indicate whether the original connection was encrypted (the equivalent of the X-Forwarded-Proto header) as well as the domain specified in the Common Name field of the certificate used, if applicable. + +To learn more about ProxyProtocol, please consult the [ProxyProtocol specification](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. + +### Activating ProxyProtocol for one of your servers + +ProxyProtocol must be enabled for each server registered in a server farm. Since this feature is intrusive and cannot be activated transparently, this allows you to test it on a particular machine and then progressively deploy the configuration to an active farm. + +Your OVHcloud Load Balancer service supports 4 ProxyProtocol modes: + +| Mode | Description | +|---|---| +| v1 | Version 1 in text format. This is the most widely supported version. | +| v2 | Version 2 in binary format without any options. This is an optimized version of version 1. | +| v2-ssl | v2, with a field describing the SSL connection, if applicable. | +| v2-ssl-cn | v2-ssl, with the "Common Name" field of the certificate used, if applicable. | + +When ProxyProtocol is enabled for one of your servers, probes automatically insert this header **unless** a specific port has been specified for the probes. In this case, the probe will connect normally to the probe port. + +#### From the OVHcloud Control Panel + +In the `Clusters`{.action} section, select the farm containing the server on which to enable ProxyProtocol, then click the edit button for the relevant server. + +ProxyProtocol is configured via the `ProxyProtocol version`{.action} option. You will find the 4 modes described above. + +![Activating ProxyProtocol on a server in a farm](images/edit_server.png){.thumbnail} + +Once the desired mode is selected, click `Update`{.action}, then `Deploy zone: YOUR ZONE`{.action} to apply your changes in the relevant zone. + +#### From the OVHcloud API + +Activating ProxyProtocol via the API is done in the same way as from the OVHcloud Control Panel. +The corresponding API field in the server is proxyProtocolVersion. + +- Modify an existing `Server`{.action}: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|allowedSource||| -|dedicatedIpfo||| -|defaultBackendId|1000|1001| -|defaultSslId||| -|disabled|false|false| -|hsts||| -|httpHeader||| -|port *|80|443| -|redirectLocation||| -|ssl||| -|zone *|rbx|rbx| - -### Apply changes +> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server/{serverId} +> + +- Apply changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> -### Firewall -Don't forget to allow IPLoadbalancing traffic to your backends: +### Server-side ProxyProtocol configuration -> [!api] +#### Nginx + +Nginx supports ProxyProtocol version 1. It can extract the main information from it, namely the client's IP address and source port as seen by your OVHcloud Load Balancer service. In Nginx, this information is exposed through the `proxy_protocol_addr` variable. Similar to its HTTP counterpart `X-Forwarded-For`, Nginx will use this variable to take the correct source address into account in the logs with the `ngx_http_realip` module. + +To use ProxyProtocol with Nginx, you can configure the server section of your configuration with: + +```nginx +1. server { +2. # Enable the Proxy protocol on port 80 +3. listen 80 proxy_protocol; +4. +5. # Trust the proxy protocol provided informations from your OVHcloud Load Balancer service +6. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +7. set_real_ip_from 10.108.0.0/14; +8. real_ip_header proxy_protocol; +9. +10. # (optional) Set some headers +11. proxy_set_header X-Real-IP $proxy_protocol_addr; +12. proxy_set_header X-Forwarded-For $proxy_protocol_addr; +13. +14. # Insert your regular configuration here +15. ... +16. } +``` + +Once configured, you can reload the configuration: + +```bash +service nginx reload +``` + +> [!primary] +> +> This example uses the HTTP protocol for more simplicity. If you are using HTTP, we strongly recommend using HTTP headers instead of ProxyProtocol, unless your OVHcloud Load Balancer service is configured in TCP. This can happen in the case of SSL termination for HTTP/2, for example. > -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp -> -Get IP range used by OVH Load Balancer: 10.108.0.0/16 + +For more information on configuring ProxyProtocol in Nginx, please consult the project's official documentation: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external} + +#### Apache + +The management of ProxyProtocol in Apache is still young. An unofficial implementation compatible with Apache 2.4 is available on Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) but has not been maintained since 2014. An official implementation is found in the `mod_remoteip` module which is also used to manage headers from the X-Forwarded-For family. + +`mod-proxy-protocol` supports ProxyProtocol versions 1 and 2. However, it does not allow specifying a list of source IP addresses authorized to use ProxyProtocol, although this is mentioned in the module's projects. + +`mod_remoteip` also supports ProxyProtocol versions 1 and 2. It also adds the ability to specify a list of addresses for which ProxyProtocol should not be enabled. This remains limiting from a configuration perspective. This module is only available in the experimental Apache 2.5 version, although the documentation mentions availability from Apache 2.4.26. + +Regardless of the approach chosen, we strongly recommend restricting connections to your servers to the outbound addresses of your OVHcloud Load Balancer service. +This can be easily configured with `iptables`: ```bash -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 8080 -j ACCEPT -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 4443 -j ACCEPT -``` \ No newline at end of file +# Trust connections from your OVHcloud Load Balancer service, ONLY +iptables -A INPUT -s 10.108.0.0/14 -p tcp --dport 80 -j ACCEPT +iptables -A INPUT -p tcp --dport 80 -j DROP +``` + +##### **With mod-proxy-protocol** + +- Since this module is unofficial, you will first need to download the sources, compile, and install it: + +```bash +# Install build tools +sudo apt install git apache2-dev + +# Grab the sources +git clone [https://github.com/roadrunner2/mod-proxy-protocol.git](https://github.com/roadrunner2/mod-proxy-protocol.git) +cd mod-proxy-protocol + +# Build and install the module +sudo apxs -i -a -c mod_proxy_protocol.c +``` + +- Then configure Apache: + +```apache +1. +2. ProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod-proxy-protocol` module, please consult [its documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. + +##### **With mod_remoteip** + +- Since the module is experimental, you will first need to install an experimental version of Apache, which is not recommended in a production environment unless you know exactly what you're doing! +- Then configure Apache: + +```apache +1. +2. RemoteIPProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Enable the 'remoteip' module and configuration +a2enmod remoteip + +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod_remoteip` module, please consult [its documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. + +#### HAProxy + +ProxyProtocol was designed by the HAProxy team, making it the software that best manages this protocol. This can be useful in a scenario where tracking the client's true source IP address is essential, but the target software does not support this protocol. This would be the case, for example, for MySQL and PostgreSQL, to name just two. + +In this case, a trick is to place a local HAProxy instance in front of the software and ensure logging of requests and their advanced filtering in the local HAProxy instance. + +This guide provides an example of a possible configuration for TCP port 3306 used by MySQL. This configuration is not intended to be a complete example but rather to serve as a basis for a functional setup. + +- Install HAProxy + +```bash +sudo apt install haproxy +``` + +- Configure your proxy + +```haproxy +1. listen mysql +2. # Listen on all interfaces, port 3306, tcp mode (ie: not HTTP) +3. mode tcp +4. option tcplog +5. bind *:3306 +6. +7. # Expect ProxyProtocol header if and only if from a trusted network +8. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +9. tcp-request connection expect-proxy layer4 if { src 10.108.0.0/14 } +10. +11. # Declare local server, on a non standard port to avoid collisions +12. server mysql 127.0.0.1:3316 check +``` + +- Finally, activate the new configuration with: + +```bash +service haproxy reload +``` + +## Go Further + +Discuss with our [user community](/links/community). diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md index bc87d65174c..2ebb05b2e40 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-gb.md @@ -1,161 +1,277 @@ --- -title: 'ProxyProtocol get Source IP' -excerpt: 'Get real visitor IP using OVH Load Balancer with ProxyProtocol' -updated: 2025-07-04 +title: "Configuring an OVHcloud Load Balancer with ProxyProtocol" +excerpt: Integrate your TCP services behind a Load Balancer with ProxyProtocol +updated: 2025-07-11 --- -## Introduction -In this case, we want to get sourceIP, scheme trouth OVH API LoadBalancing, without install our SSL Certitificate on it. This is helpful if you have many domains with many SSL certificates. +## Objective -## Requirements -We assume you have already an OVH Load Balancer HTTP configured, if not follow [this guide](/pages/network/load_balancer/use-lb). +The OVHcloud Load Balancer acts as a proxy. Like a human proxy, it acts as an intermediary, so the client addresses the proxy and the proxy addresses the service provider, on behalf of the client. In this configuration, only the proxy knows both the true client (the user of your service) and the true service provider (one of your servers). -You have : +For the visitor, this isn't an issue. They don't need to know the exact server responding to their request; that's an implementation detail. However, for statistical and security reasons, it's sometimes essential for the final server to know the client's true address. By default, it only sees the proxy (in this case, your OVHcloud Load Balancer service). -- An OVH Load Balancer service -- Nginx (or Apache with mod_proxyprotocol) on an OVH backend -- A domain (option) -- An SSL certificate (option) +If you are using an HTTP frontend, we recommend the guide "[Configuring an OVHcloud Load Balancer service - HTTP Headers](/pages/network/load_balancer/create_headers)" which describes the standard way to use HTTP headers to retrieve the IP address, port, and source protocol. -### Nginx Configuration -For this example we use this minimal nginx configuration on each backend. +**If you are using a TCP frontend, then this guide is for you.** -```bash -log_format proxyprotocol '$proxy_protocol_addr - $remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" "$request_time"'; -server { - listen 80; - listen [::]:80; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 443 ssl; - listen [::]:443 ssl; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 8080 proxyprotocol; - listen [::]:8080 proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -server { - listen 4443 ssl proxyprotocol; - listen [::]:4443 ssl proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -``` +## Legal Obligations -- Port 80 / 443 are used for direct connexion to backend (for test, management, ...) -- Port 8080 / 4443 are used with LoadBalancer +You may be required to retain logs and certain traffic data under applicable laws and regulations. It is your responsibility to comply with these obligations. -You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren't cross-compatible. +**For example:** -### Infrastructure -|Backend#|Public IP|Zone| -|---|---|---| -|backend_1|213.186.0.1|rbx| -|backend_2|213.186.0.2|rbx| +- [Investigatory Powers Act 2016 (IPA), Section 87](https://www.legislation.gov.uk/ukpga/2016/25/section/87): This section notably empowers the Secretary of State, with Judicial Commissioner approval, to require telecommunications operators to retain "relevant communications data" for up to 12 months. This data is broadly defined but includes information to identify the source and destination of a communication, its date, time, and duration, and specifically covers **Internet Connection Records (ICRs)**, which log website visits and app usage. This requirement is for purposes such as national security and preventing/detecting serious crime. -## Configuration +## Prerequisites -### Add backends -Create a new cluster for each port on backend. +This is an advanced guide. It assumes you're already familiar with the main features of your OVHcloud Load Balancer service, especially **frontends** and **clusters**. If you're not, we recommend checking out the guide "[Configure an OVHcloud Load Balancer HTTP/HTTPS service](/pages/network/load_balancer/create_http_https)." While this guide focuses more on TCP services, the general principles are the same. -> [!api] +You need: + +- an OVHcloud Load Balancer service with a functional TCP frontend and farm; +- Nginx or Apache with mod_proxyprotocol on an OVHcloud server. + +> [!warning] +> Since ProxyProtocol fields can be forged by a malicious client, they should only be considered if they come from a trusted source. > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|balance|roundrobin|roundrobin| -|port|8080|4443| -|probe|tcp|tcp| -|stickiness|sourceIP|sourceIP| -|zone *|rbx|rbx| - -|Parameter|Return 1|Return 2| -|---|---|---| -|id|1000|10001| +> Therefore, it's essential to limit their use to trusted IP addresses, specifically the outbound IP addresses of your OVHcloud Load Balancer service. Major servers like Nginx and Apache have modules capable of managing this security and trust aspect. + +## In Practice + +### Obtaining the list of your outbound IP addresses + +#### From the OVHcloud Control Panel + +The list of IPv4 outbound addresses potentially used by your OVHcloud Load Balancer service can be found on the homepage of your OVHcloud Load Balancer service under "Outbound IPv4". + +![Outbound IPv4 address of your OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} + +#### From the OVHcloud API + +- List of IP addresses used by your OVHcloud Load Balancer service: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server -> -|Parameter|Call 1|Call 2|Call 3|Call 4| -|---|---|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4|ip.1.2.3.4|ip.1.2.3.4| -|farmId *|1000|1000|1001|1001| -|address *|213.186.0.1|213.186.0.2|213.186.0.1|213.186.0.2| -|backup|false|false|false|false| -|chain||||| -|cookie||||| -|port||||| -|probe|true|true|true|true| -|proxyProtocolVersion|v1|v1|v1|v1| -|ssl|false|false|false|false| -|status *|active|active|active|active| -|weight|1|1|1|1| - -|Parameter|Return 1|Return 2|Return 3|Return 4| -|---|---|---|---|---| -|id|2000|20001|20002|20003| - -### Add frontend +> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp +> + +### Introduction to ProxyProtocol + +ProxyProtocol was developed by the [HAProxy](http://haproxy.org/){.external} Load Balancer team as the TCP counterpart to standard HTTP headers like X-Forwarded-For. It was designed to forward at minimum: + +- the L4 protocol name used (TCP4 for IPv4 or TCP6 for IPv6); +- the source IPv4 or IPv6 address; +- the source port. + +When ProxyProtocol is enabled for one of your servers, the OVHcloud Load Balancer service adds a prefix with the ProxyProtocol before sending the rest of the request. Since this modification is intrusive, it is essential to ensure that the server is compatible with this protocol, and if so, which versions are supported. + +Indeed, this protocol exists in 2 versions: + +- version 1, in text format; +- version 2, in optimized and extensible binary format. + +Version 1 is largely sufficient for most uses (although less optimized) and is often the only version supported by compatible software. Version 2, being a binary format, is faster to parse. It also adds the ability to indicate whether the original connection was encrypted (the equivalent of the X-Forwarded-Proto header) as well as the domain specified in the Common Name field of the certificate used, if applicable. + +To learn more about ProxyProtocol, please consult the [ProxyProtocol specification](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. + +### Activating ProxyProtocol for one of your servers + +ProxyProtocol must be enabled for each server registered in a server farm. Since this feature is intrusive and cannot be activated transparently, this allows you to test it on a particular machine and then progressively deploy the configuration to an active farm. + +Your OVHcloud Load Balancer service supports 4 ProxyProtocol modes: + +| Mode | Description | +|---|---| +| v1 | Version 1 in text format. This is the most widely supported version. | +| v2 | Version 2 in binary format without any options. This is an optimized version of version 1. | +| v2-ssl | v2, with a field describing the SSL connection, if applicable. | +| v2-ssl-cn | v2-ssl, with the "Common Name" field of the certificate used, if applicable. | + +When ProxyProtocol is enabled for one of your servers, probes automatically insert this header **unless** a specific port has been specified for the probes. In this case, the probe will connect normally to the probe port. + +#### From the OVHcloud Control Panel + +In the `Clusters`{.action} section, select the farm containing the server on which to enable ProxyProtocol, then click the edit button for the relevant server. + +ProxyProtocol is configured via the `ProxyProtocol version`{.action} option. You will find the 4 modes described above. + +![Activating ProxyProtocol on a server in a farm](images/edit_server.png){.thumbnail} + +Once the desired mode is selected, click `Update`{.action}, then `Deploy zone: YOUR ZONE`{.action} to apply your changes in the relevant zone. + +#### From the OVHcloud API + +Activating ProxyProtocol via the API is done in the same way as from the OVHcloud Control Panel. +The corresponding API field in the server is proxyProtocolVersion. + +- Modify an existing `Server`{.action}: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|allowedSource||| -|dedicatedIpfo||| -|defaultBackendId|1000|1001| -|defaultSslId||| -|disabled|false|false| -|hsts||| -|httpHeader||| -|port *|80|443| -|redirectLocation||| -|ssl||| -|zone *|rbx|rbx| - -### Apply changes +> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server/{serverId} +> + +- Apply changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> -### Firewall -Don't forget to allow IPLoadbalancing traffic to your backends: +### Server-side ProxyProtocol configuration -> [!api] +#### Nginx + +Nginx supports ProxyProtocol version 1. It can extract the main information from it, namely the client's IP address and source port as seen by your OVHcloud Load Balancer service. In Nginx, this information is exposed through the `proxy_protocol_addr` variable. Similar to its HTTP counterpart `X-Forwarded-For`, Nginx will use this variable to take the correct source address into account in the logs with the `ngx_http_realip` module. + +To use ProxyProtocol with Nginx, you can configure the server section of your configuration with: + +```nginx +1. server { +2. # Enable the Proxy protocol on port 80 +3. listen 80 proxy_protocol; +4. +5. # Trust the proxy protocol provided informations from your OVHcloud Load Balancer service +6. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +7. set_real_ip_from 10.108.0.0/14; +8. real_ip_header proxy_protocol; +9. +10. # (optional) Set some headers +11. proxy_set_header X-Real-IP $proxy_protocol_addr; +12. proxy_set_header X-Forwarded-For $proxy_protocol_addr; +13. +14. # Insert your regular configuration here +15. ... +16. } +``` + +Once configured, you can reload the configuration: + +```bash +service nginx reload +``` + +> [!primary] +> +> This example uses the HTTP protocol for more simplicity. If you are using HTTP, we strongly recommend using HTTP headers instead of ProxyProtocol, unless your OVHcloud Load Balancer service is configured in TCP. This can happen in the case of SSL termination for HTTP/2, for example. > -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp -> -Get IP range used by OVH Load Balancer: 10.108.0.0/16 + +For more information on configuring ProxyProtocol in Nginx, please consult the project's official documentation: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external} + +#### Apache + +The management of ProxyProtocol in Apache is still young. An unofficial implementation compatible with Apache 2.4 is available on Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) but has not been maintained since 2014. An official implementation is found in the `mod_remoteip` module which is also used to manage headers from the X-Forwarded-For family. + +`mod-proxy-protocol` supports ProxyProtocol versions 1 and 2. However, it does not allow specifying a list of source IP addresses authorized to use ProxyProtocol, although this is mentioned in the module's projects. + +`mod_remoteip` also supports ProxyProtocol versions 1 and 2. It also adds the ability to specify a list of addresses for which ProxyProtocol should not be enabled. This remains limiting from a configuration perspective. This module is only available in the experimental Apache 2.5 version, although the documentation mentions availability from Apache 2.4.26. + +Regardless of the approach chosen, we strongly recommend restricting connections to your servers to the outbound addresses of your OVHcloud Load Balancer service. +This can be easily configured with `iptables`: ```bash -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 8080 -j ACCEPT -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 4443 -j ACCEPT -``` \ No newline at end of file +# Trust connections from your OVHcloud Load Balancer service, ONLY +iptables -A INPUT -s 10.108.0.0/14 -p tcp --dport 80 -j ACCEPT +iptables -A INPUT -p tcp --dport 80 -j DROP +``` + +##### **With mod-proxy-protocol** + +- Since this module is unofficial, you will first need to download the sources, compile, and install it: + +```bash +# Install build tools +sudo apt install git apache2-dev + +# Grab the sources +git clone [https://github.com/roadrunner2/mod-proxy-protocol.git](https://github.com/roadrunner2/mod-proxy-protocol.git) +cd mod-proxy-protocol + +# Build and install the module +sudo apxs -i -a -c mod_proxy_protocol.c +``` + +- Then configure Apache: + +```apache +1. +2. ProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod-proxy-protocol` module, please consult [its documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. + +##### **With mod_remoteip** + +- Since the module is experimental, you will first need to install an experimental version of Apache, which is not recommended in a production environment unless you know exactly what you're doing! +- Then configure Apache: + +```apache +1. +2. RemoteIPProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Enable the 'remoteip' module and configuration +a2enmod remoteip + +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod_remoteip` module, please consult [its documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. + +#### HAProxy + +ProxyProtocol was designed by the HAProxy team, making it the software that best manages this protocol. This can be useful in a scenario where tracking the client's true source IP address is essential, but the target software does not support this protocol. This would be the case, for example, for MySQL and PostgreSQL, to name just two. + +In this case, a trick is to place a local HAProxy instance in front of the software and ensure logging of requests and their advanced filtering in the local HAProxy instance. + +This guide provides an example of a possible configuration for TCP port 3306 used by MySQL. This configuration is not intended to be a complete example but rather to serve as a basis for a functional setup. + +- Install HAProxy + +```bash +sudo apt install haproxy +``` + +- Configure your proxy + +```haproxy +1. listen mysql +2. # Listen on all interfaces, port 3306, tcp mode (ie: not HTTP) +3. mode tcp +4. option tcplog +5. bind *:3306 +6. +7. # Expect ProxyProtocol header if and only if from a trusted network +8. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +9. tcp-request connection expect-proxy layer4 if { src 10.108.0.0/14 } +10. +11. # Declare local server, on a non standard port to avoid collisions +12. server mysql 127.0.0.1:3316 check +``` + +- Finally, activate the new configuration with: + +```bash +service haproxy reload +``` + +## Go Further + +Discuss with our [user community](/links/community). diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-sg.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-sg.md index c71907b8d17..2ebb05b2e40 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-sg.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-sg.md @@ -1,161 +1,277 @@ --- -title: ProxyProtocol get Source IP -excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2025-07-04 +title: "Configuring an OVHcloud Load Balancer with ProxyProtocol" +excerpt: Integrate your TCP services behind a Load Balancer with ProxyProtocol +updated: 2025-07-11 --- -## Introduction -In this case, we want to get sourceIP, scheme trouth OVH API LoadBalancing, without install our SSL Certitificate on it. This is helpful if you have many domains with many SSL certificates. +## Objective -## Requirements -We assume you have already an OVH Load Balancer HTTP configured, if not follow ..refs:fr/fr/cloud/iplb/configure-iplb +The OVHcloud Load Balancer acts as a proxy. Like a human proxy, it acts as an intermediary, so the client addresses the proxy and the proxy addresses the service provider, on behalf of the client. In this configuration, only the proxy knows both the true client (the user of your service) and the true service provider (one of your servers). -You have : +For the visitor, this isn't an issue. They don't need to know the exact server responding to their request; that's an implementation detail. However, for statistical and security reasons, it's sometimes essential for the final server to know the client's true address. By default, it only sees the proxy (in this case, your OVHcloud Load Balancer service). -- An OVH Load Balancer service -- Nginx (or Apache with mod_proxyprotocol) on an OVH backend -- A domain (option) -- An SSL certificate (option) +If you are using an HTTP frontend, we recommend the guide "[Configuring an OVHcloud Load Balancer service - HTTP Headers](/pages/network/load_balancer/create_headers)" which describes the standard way to use HTTP headers to retrieve the IP address, port, and source protocol. -### Nginx Configuration -For this example we use this minimal nginx configuration on each backend. +**If you are using a TCP frontend, then this guide is for you.** -```bash -log_format proxyprotocol '$proxy_protocol_addr - $remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" "$request_time"'; -server { - listen 80; - listen [::]:80; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 443 ssl; - listen [::]:443 ssl; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 8080 proxyprotocol; - listen [::]:8080 proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -server { - listen 4443 ssl proxyprotocol; - listen [::]:4443 ssl proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -``` +## Legal Obligations -- Port 80 / 443 are used for direct connexion to backend (for test, management, ...) -- Port 8080 / 4443 are used with LoadBalancer +You may be required to retain logs and certain traffic data under applicable laws and regulations. It is your responsibility to comply with these obligations. -You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren't cross-compatible. +**For example:** -### Infrastructure -|Backend#|Public IP|Zone| -|---|---|---| -|backend_1|213.186.0.1|rbx| -|backend_2|213.186.0.2|rbx| +- [Investigatory Powers Act 2016 (IPA), Section 87](https://www.legislation.gov.uk/ukpga/2016/25/section/87): This section notably empowers the Secretary of State, with Judicial Commissioner approval, to require telecommunications operators to retain "relevant communications data" for up to 12 months. This data is broadly defined but includes information to identify the source and destination of a communication, its date, time, and duration, and specifically covers **Internet Connection Records (ICRs)**, which log website visits and app usage. This requirement is for purposes such as national security and preventing/detecting serious crime. -## Configuration +## Prerequisites -### Add backends -Create a new cluster for each port on backend. +This is an advanced guide. It assumes you're already familiar with the main features of your OVHcloud Load Balancer service, especially **frontends** and **clusters**. If you're not, we recommend checking out the guide "[Configure an OVHcloud Load Balancer HTTP/HTTPS service](/pages/network/load_balancer/create_http_https)." While this guide focuses more on TCP services, the general principles are the same. -> [!api] +You need: + +- an OVHcloud Load Balancer service with a functional TCP frontend and farm; +- Nginx or Apache with mod_proxyprotocol on an OVHcloud server. + +> [!warning] +> Since ProxyProtocol fields can be forged by a malicious client, they should only be considered if they come from a trusted source. > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|balance|roundrobin|roundrobin| -|port|8080|4443| -|probe|tcp|tcp| -|stickiness|sourceIP|sourceIP| -|zone *|rbx|rbx| - -|Parameter|Return 1|Return 2| -|---|---|---| -|id|1000|10001| +> Therefore, it's essential to limit their use to trusted IP addresses, specifically the outbound IP addresses of your OVHcloud Load Balancer service. Major servers like Nginx and Apache have modules capable of managing this security and trust aspect. + +## In Practice + +### Obtaining the list of your outbound IP addresses + +#### From the OVHcloud Control Panel + +The list of IPv4 outbound addresses potentially used by your OVHcloud Load Balancer service can be found on the homepage of your OVHcloud Load Balancer service under "Outbound IPv4". + +![Outbound IPv4 address of your OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} + +#### From the OVHcloud API + +- List of IP addresses used by your OVHcloud Load Balancer service: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server -> -|Parameter|Call 1|Call 2|Call 3|Call 4| -|---|---|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4|ip.1.2.3.4|ip.1.2.3.4| -|farmId *|1000|1000|1001|1001| -|address *|213.186.0.1|213.186.0.2|213.186.0.1|213.186.0.2| -|backup|false|false|false|false| -|chain||||| -|cookie||||| -|port||||| -|probe|true|true|true|true| -|proxyProtocolVersion|v1|v1|v1|v1| -|ssl|false|false|false|false| -|status *|active|active|active|active| -|weight|1|1|1|1| - -|Parameter|Return 1|Return 2|Return 3|Return 4| -|---|---|---|---|---| -|id|2000|20001|20002|20003| - -### Add frontend +> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp +> + +### Introduction to ProxyProtocol + +ProxyProtocol was developed by the [HAProxy](http://haproxy.org/){.external} Load Balancer team as the TCP counterpart to standard HTTP headers like X-Forwarded-For. It was designed to forward at minimum: + +- the L4 protocol name used (TCP4 for IPv4 or TCP6 for IPv6); +- the source IPv4 or IPv6 address; +- the source port. + +When ProxyProtocol is enabled for one of your servers, the OVHcloud Load Balancer service adds a prefix with the ProxyProtocol before sending the rest of the request. Since this modification is intrusive, it is essential to ensure that the server is compatible with this protocol, and if so, which versions are supported. + +Indeed, this protocol exists in 2 versions: + +- version 1, in text format; +- version 2, in optimized and extensible binary format. + +Version 1 is largely sufficient for most uses (although less optimized) and is often the only version supported by compatible software. Version 2, being a binary format, is faster to parse. It also adds the ability to indicate whether the original connection was encrypted (the equivalent of the X-Forwarded-Proto header) as well as the domain specified in the Common Name field of the certificate used, if applicable. + +To learn more about ProxyProtocol, please consult the [ProxyProtocol specification](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. + +### Activating ProxyProtocol for one of your servers + +ProxyProtocol must be enabled for each server registered in a server farm. Since this feature is intrusive and cannot be activated transparently, this allows you to test it on a particular machine and then progressively deploy the configuration to an active farm. + +Your OVHcloud Load Balancer service supports 4 ProxyProtocol modes: + +| Mode | Description | +|---|---| +| v1 | Version 1 in text format. This is the most widely supported version. | +| v2 | Version 2 in binary format without any options. This is an optimized version of version 1. | +| v2-ssl | v2, with a field describing the SSL connection, if applicable. | +| v2-ssl-cn | v2-ssl, with the "Common Name" field of the certificate used, if applicable. | + +When ProxyProtocol is enabled for one of your servers, probes automatically insert this header **unless** a specific port has been specified for the probes. In this case, the probe will connect normally to the probe port. + +#### From the OVHcloud Control Panel + +In the `Clusters`{.action} section, select the farm containing the server on which to enable ProxyProtocol, then click the edit button for the relevant server. + +ProxyProtocol is configured via the `ProxyProtocol version`{.action} option. You will find the 4 modes described above. + +![Activating ProxyProtocol on a server in a farm](images/edit_server.png){.thumbnail} + +Once the desired mode is selected, click `Update`{.action}, then `Deploy zone: YOUR ZONE`{.action} to apply your changes in the relevant zone. + +#### From the OVHcloud API + +Activating ProxyProtocol via the API is done in the same way as from the OVHcloud Control Panel. +The corresponding API field in the server is proxyProtocolVersion. + +- Modify an existing `Server`{.action}: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|allowedSource||| -|dedicatedIpfo||| -|defaultBackendId|1000|1001| -|defaultSslId||| -|disabled|false|false| -|hsts||| -|httpHeader||| -|port *|80|443| -|redirectLocation||| -|ssl||| -|zone *|rbx|rbx| - -### Apply changes +> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server/{serverId} +> + +- Apply changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> -### Firewall -Don't forget to allow IPLoadbalancing traffic to your backends: +### Server-side ProxyProtocol configuration -> [!api] +#### Nginx + +Nginx supports ProxyProtocol version 1. It can extract the main information from it, namely the client's IP address and source port as seen by your OVHcloud Load Balancer service. In Nginx, this information is exposed through the `proxy_protocol_addr` variable. Similar to its HTTP counterpart `X-Forwarded-For`, Nginx will use this variable to take the correct source address into account in the logs with the `ngx_http_realip` module. + +To use ProxyProtocol with Nginx, you can configure the server section of your configuration with: + +```nginx +1. server { +2. # Enable the Proxy protocol on port 80 +3. listen 80 proxy_protocol; +4. +5. # Trust the proxy protocol provided informations from your OVHcloud Load Balancer service +6. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +7. set_real_ip_from 10.108.0.0/14; +8. real_ip_header proxy_protocol; +9. +10. # (optional) Set some headers +11. proxy_set_header X-Real-IP $proxy_protocol_addr; +12. proxy_set_header X-Forwarded-For $proxy_protocol_addr; +13. +14. # Insert your regular configuration here +15. ... +16. } +``` + +Once configured, you can reload the configuration: + +```bash +service nginx reload +``` + +> [!primary] +> +> This example uses the HTTP protocol for more simplicity. If you are using HTTP, we strongly recommend using HTTP headers instead of ProxyProtocol, unless your OVHcloud Load Balancer service is configured in TCP. This can happen in the case of SSL termination for HTTP/2, for example. > -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp -> -Get IP range used by OVH Load Balancer: 10.108.0.0/16 + +For more information on configuring ProxyProtocol in Nginx, please consult the project's official documentation: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external} + +#### Apache + +The management of ProxyProtocol in Apache is still young. An unofficial implementation compatible with Apache 2.4 is available on Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) but has not been maintained since 2014. An official implementation is found in the `mod_remoteip` module which is also used to manage headers from the X-Forwarded-For family. + +`mod-proxy-protocol` supports ProxyProtocol versions 1 and 2. However, it does not allow specifying a list of source IP addresses authorized to use ProxyProtocol, although this is mentioned in the module's projects. + +`mod_remoteip` also supports ProxyProtocol versions 1 and 2. It also adds the ability to specify a list of addresses for which ProxyProtocol should not be enabled. This remains limiting from a configuration perspective. This module is only available in the experimental Apache 2.5 version, although the documentation mentions availability from Apache 2.4.26. + +Regardless of the approach chosen, we strongly recommend restricting connections to your servers to the outbound addresses of your OVHcloud Load Balancer service. +This can be easily configured with `iptables`: ```bash -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 8080 -j ACCEPT -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 4443 -j ACCEPT -``` \ No newline at end of file +# Trust connections from your OVHcloud Load Balancer service, ONLY +iptables -A INPUT -s 10.108.0.0/14 -p tcp --dport 80 -j ACCEPT +iptables -A INPUT -p tcp --dport 80 -j DROP +``` + +##### **With mod-proxy-protocol** + +- Since this module is unofficial, you will first need to download the sources, compile, and install it: + +```bash +# Install build tools +sudo apt install git apache2-dev + +# Grab the sources +git clone [https://github.com/roadrunner2/mod-proxy-protocol.git](https://github.com/roadrunner2/mod-proxy-protocol.git) +cd mod-proxy-protocol + +# Build and install the module +sudo apxs -i -a -c mod_proxy_protocol.c +``` + +- Then configure Apache: + +```apache +1. +2. ProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod-proxy-protocol` module, please consult [its documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. + +##### **With mod_remoteip** + +- Since the module is experimental, you will first need to install an experimental version of Apache, which is not recommended in a production environment unless you know exactly what you're doing! +- Then configure Apache: + +```apache +1. +2. RemoteIPProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Enable the 'remoteip' module and configuration +a2enmod remoteip + +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod_remoteip` module, please consult [its documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. + +#### HAProxy + +ProxyProtocol was designed by the HAProxy team, making it the software that best manages this protocol. This can be useful in a scenario where tracking the client's true source IP address is essential, but the target software does not support this protocol. This would be the case, for example, for MySQL and PostgreSQL, to name just two. + +In this case, a trick is to place a local HAProxy instance in front of the software and ensure logging of requests and their advanced filtering in the local HAProxy instance. + +This guide provides an example of a possible configuration for TCP port 3306 used by MySQL. This configuration is not intended to be a complete example but rather to serve as a basis for a functional setup. + +- Install HAProxy + +```bash +sudo apt install haproxy +``` + +- Configure your proxy + +```haproxy +1. listen mysql +2. # Listen on all interfaces, port 3306, tcp mode (ie: not HTTP) +3. mode tcp +4. option tcplog +5. bind *:3306 +6. +7. # Expect ProxyProtocol header if and only if from a trusted network +8. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +9. tcp-request connection expect-proxy layer4 if { src 10.108.0.0/14 } +10. +11. # Declare local server, on a non standard port to avoid collisions +12. server mysql 127.0.0.1:3316 check +``` + +- Finally, activate the new configuration with: + +```bash +service haproxy reload +``` + +## Go Further + +Discuss with our [user community](/links/community). diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.en-us.md b/pages/network/load_balancer/create_proxyprotocol/guide.en-us.md index c71907b8d17..2ebb05b2e40 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.en-us.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.en-us.md @@ -1,161 +1,277 @@ --- -title: ProxyProtocol get Source IP -excerpt: Get real visitor IP using OVH Load Balancer with ProxyProtocol -updated: 2025-07-04 +title: "Configuring an OVHcloud Load Balancer with ProxyProtocol" +excerpt: Integrate your TCP services behind a Load Balancer with ProxyProtocol +updated: 2025-07-11 --- -## Introduction -In this case, we want to get sourceIP, scheme trouth OVH API LoadBalancing, without install our SSL Certitificate on it. This is helpful if you have many domains with many SSL certificates. +## Objective -## Requirements -We assume you have already an OVH Load Balancer HTTP configured, if not follow ..refs:fr/fr/cloud/iplb/configure-iplb +The OVHcloud Load Balancer acts as a proxy. Like a human proxy, it acts as an intermediary, so the client addresses the proxy and the proxy addresses the service provider, on behalf of the client. In this configuration, only the proxy knows both the true client (the user of your service) and the true service provider (one of your servers). -You have : +For the visitor, this isn't an issue. They don't need to know the exact server responding to their request; that's an implementation detail. However, for statistical and security reasons, it's sometimes essential for the final server to know the client's true address. By default, it only sees the proxy (in this case, your OVHcloud Load Balancer service). -- An OVH Load Balancer service -- Nginx (or Apache with mod_proxyprotocol) on an OVH backend -- A domain (option) -- An SSL certificate (option) +If you are using an HTTP frontend, we recommend the guide "[Configuring an OVHcloud Load Balancer service - HTTP Headers](/pages/network/load_balancer/create_headers)" which describes the standard way to use HTTP headers to retrieve the IP address, port, and source protocol. -### Nginx Configuration -For this example we use this minimal nginx configuration on each backend. +**If you are using a TCP frontend, then this guide is for you.** -```bash -log_format proxyprotocol '$proxy_protocol_addr - $remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" "$request_time"'; -server { - listen 80; - listen [::]:80; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 443 ssl; - listen [::]:443 ssl; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log; -} -server { - listen 8080 proxyprotocol; - listen [::]:8080 proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -server { - listen 4443 ssl proxyprotocol; - listen [::]:4443 ssl proxyprotocol; - - server_name domain.tld www.domain.tld; - root /var/www/domain.tld/htdocs; - - ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; - ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; - access_log /var/www/domain.tld/logs/access.log proxyprotocol; -} -``` +## Legal Obligations -- Port 80 / 443 are used for direct connexion to backend (for test, management, ...) -- Port 8080 / 4443 are used with LoadBalancer +You may be required to retain logs and certain traffic data under applicable laws and regulations. It is your responsibility to comply with these obligations. -You can't use ProxyProtocol and HTTP on the same port, and theses protocols aren't cross-compatible. +**For example:** -### Infrastructure -|Backend#|Public IP|Zone| -|---|---|---| -|backend_1|213.186.0.1|rbx| -|backend_2|213.186.0.2|rbx| +- [Investigatory Powers Act 2016 (IPA), Section 87](https://www.legislation.gov.uk/ukpga/2016/25/section/87): This section notably empowers the Secretary of State, with Judicial Commissioner approval, to require telecommunications operators to retain "relevant communications data" for up to 12 months. This data is broadly defined but includes information to identify the source and destination of a communication, its date, time, and duration, and specifically covers **Internet Connection Records (ICRs)**, which log website visits and app usage. This requirement is for purposes such as national security and preventing/detecting serious crime. -## Configuration +## Prerequisites -### Add backends -Create a new cluster for each port on backend. +This is an advanced guide. It assumes you're already familiar with the main features of your OVHcloud Load Balancer service, especially **frontends** and **clusters**. If you're not, we recommend checking out the guide "[Configure an OVHcloud Load Balancer HTTP/HTTPS service](/pages/network/load_balancer/create_http_https)." While this guide focuses more on TCP services, the general principles are the same. -> [!api] +You need: + +- an OVHcloud Load Balancer service with a functional TCP frontend and farm; +- Nginx or Apache with mod_proxyprotocol on an OVHcloud server. + +> [!warning] +> Since ProxyProtocol fields can be forged by a malicious client, they should only be considered if they come from a trusted source. > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|balance|roundrobin|roundrobin| -|port|8080|4443| -|probe|tcp|tcp| -|stickiness|sourceIP|sourceIP| -|zone *|rbx|rbx| - -|Parameter|Return 1|Return 2| -|---|---|---| -|id|1000|10001| +> Therefore, it's essential to limit their use to trusted IP addresses, specifically the outbound IP addresses of your OVHcloud Load Balancer service. Major servers like Nginx and Apache have modules capable of managing this security and trust aspect. + +## In Practice + +### Obtaining the list of your outbound IP addresses + +#### From the OVHcloud Control Panel + +The list of IPv4 outbound addresses potentially used by your OVHcloud Load Balancer service can be found on the homepage of your OVHcloud Load Balancer service under "Outbound IPv4". + +![Outbound IPv4 address of your OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} + +#### From the OVHcloud API + +- List of IP addresses used by your OVHcloud Load Balancer service: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server -> -|Parameter|Call 1|Call 2|Call 3|Call 4| -|---|---|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4|ip.1.2.3.4|ip.1.2.3.4| -|farmId *|1000|1000|1001|1001| -|address *|213.186.0.1|213.186.0.2|213.186.0.1|213.186.0.2| -|backup|false|false|false|false| -|chain||||| -|cookie||||| -|port||||| -|probe|true|true|true|true| -|proxyProtocolVersion|v1|v1|v1|v1| -|ssl|false|false|false|false| -|status *|active|active|active|active| -|weight|1|1|1|1| - -|Parameter|Return 1|Return 2|Return 3|Return 4| -|---|---|---|---|---| -|id|2000|20001|20002|20003| - -### Add frontend +> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp +> + +### Introduction to ProxyProtocol + +ProxyProtocol was developed by the [HAProxy](http://haproxy.org/){.external} Load Balancer team as the TCP counterpart to standard HTTP headers like X-Forwarded-For. It was designed to forward at minimum: + +- the L4 protocol name used (TCP4 for IPv4 or TCP6 for IPv6); +- the source IPv4 or IPv6 address; +- the source port. + +When ProxyProtocol is enabled for one of your servers, the OVHcloud Load Balancer service adds a prefix with the ProxyProtocol before sending the rest of the request. Since this modification is intrusive, it is essential to ensure that the server is compatible with this protocol, and if so, which versions are supported. + +Indeed, this protocol exists in 2 versions: + +- version 1, in text format; +- version 2, in optimized and extensible binary format. + +Version 1 is largely sufficient for most uses (although less optimized) and is often the only version supported by compatible software. Version 2, being a binary format, is faster to parse. It also adds the ability to indicate whether the original connection was encrypted (the equivalent of the X-Forwarded-Proto header) as well as the domain specified in the Common Name field of the certificate used, if applicable. + +To learn more about ProxyProtocol, please consult the [ProxyProtocol specification](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. + +### Activating ProxyProtocol for one of your servers + +ProxyProtocol must be enabled for each server registered in a server farm. Since this feature is intrusive and cannot be activated transparently, this allows you to test it on a particular machine and then progressively deploy the configuration to an active farm. + +Your OVHcloud Load Balancer service supports 4 ProxyProtocol modes: + +| Mode | Description | +|---|---| +| v1 | Version 1 in text format. This is the most widely supported version. | +| v2 | Version 2 in binary format without any options. This is an optimized version of version 1. | +| v2-ssl | v2, with a field describing the SSL connection, if applicable. | +| v2-ssl-cn | v2-ssl, with the "Common Name" field of the certificate used, if applicable. | + +When ProxyProtocol is enabled for one of your servers, probes automatically insert this header **unless** a specific port has been specified for the probes. In this case, the probe will connect normally to the probe port. + +#### From the OVHcloud Control Panel + +In the `Clusters`{.action} section, select the farm containing the server on which to enable ProxyProtocol, then click the edit button for the relevant server. + +ProxyProtocol is configured via the `ProxyProtocol version`{.action} option. You will find the 4 modes described above. + +![Activating ProxyProtocol on a server in a farm](images/edit_server.png){.thumbnail} + +Once the desired mode is selected, click `Update`{.action}, then `Deploy zone: YOUR ZONE`{.action} to apply your changes in the relevant zone. + +#### From the OVHcloud API + +Activating ProxyProtocol via the API is done in the same way as from the OVHcloud Control Panel. +The corresponding API field in the server is proxyProtocolVersion. + +- Modify an existing `Server`{.action}: > [!api] > -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend -> -|Parameter|Call 1|Call 2| -|---|---|---| -|serviceName *|ip-1.2.3.4|ip.1.2.3.4| -|allowedSource||| -|dedicatedIpfo||| -|defaultBackendId|1000|1001| -|defaultSslId||| -|disabled|false|false| -|hsts||| -|httpHeader||| -|port *|80|443| -|redirectLocation||| -|ssl||| -|zone *|rbx|rbx| - -### Apply changes +> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server/{serverId} +> + +- Apply changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> -### Firewall -Don't forget to allow IPLoadbalancing traffic to your backends: +### Server-side ProxyProtocol configuration -> [!api] +#### Nginx + +Nginx supports ProxyProtocol version 1. It can extract the main information from it, namely the client's IP address and source port as seen by your OVHcloud Load Balancer service. In Nginx, this information is exposed through the `proxy_protocol_addr` variable. Similar to its HTTP counterpart `X-Forwarded-For`, Nginx will use this variable to take the correct source address into account in the logs with the `ngx_http_realip` module. + +To use ProxyProtocol with Nginx, you can configure the server section of your configuration with: + +```nginx +1. server { +2. # Enable the Proxy protocol on port 80 +3. listen 80 proxy_protocol; +4. +5. # Trust the proxy protocol provided informations from your OVHcloud Load Balancer service +6. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +7. set_real_ip_from 10.108.0.0/14; +8. real_ip_header proxy_protocol; +9. +10. # (optional) Set some headers +11. proxy_set_header X-Real-IP $proxy_protocol_addr; +12. proxy_set_header X-Forwarded-For $proxy_protocol_addr; +13. +14. # Insert your regular configuration here +15. ... +16. } +``` + +Once configured, you can reload the configuration: + +```bash +service nginx reload +``` + +> [!primary] +> +> This example uses the HTTP protocol for more simplicity. If you are using HTTP, we strongly recommend using HTTP headers instead of ProxyProtocol, unless your OVHcloud Load Balancer service is configured in TCP. This can happen in the case of SSL termination for HTTP/2, for example. > -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp -> -Get IP range used by OVH Load Balancer: 10.108.0.0/16 + +For more information on configuring ProxyProtocol in Nginx, please consult the project's official documentation: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external} + +#### Apache + +The management of ProxyProtocol in Apache is still young. An unofficial implementation compatible with Apache 2.4 is available on Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) but has not been maintained since 2014. An official implementation is found in the `mod_remoteip` module which is also used to manage headers from the X-Forwarded-For family. + +`mod-proxy-protocol` supports ProxyProtocol versions 1 and 2. However, it does not allow specifying a list of source IP addresses authorized to use ProxyProtocol, although this is mentioned in the module's projects. + +`mod_remoteip` also supports ProxyProtocol versions 1 and 2. It also adds the ability to specify a list of addresses for which ProxyProtocol should not be enabled. This remains limiting from a configuration perspective. This module is only available in the experimental Apache 2.5 version, although the documentation mentions availability from Apache 2.4.26. + +Regardless of the approach chosen, we strongly recommend restricting connections to your servers to the outbound addresses of your OVHcloud Load Balancer service. +This can be easily configured with `iptables`: ```bash -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 8080 -j ACCEPT -iptables -A INPUT -s 10.108.0.0/16 -p tcp --dport 4443 -j ACCEPT -``` \ No newline at end of file +# Trust connections from your OVHcloud Load Balancer service, ONLY +iptables -A INPUT -s 10.108.0.0/14 -p tcp --dport 80 -j ACCEPT +iptables -A INPUT -p tcp --dport 80 -j DROP +``` + +##### **With mod-proxy-protocol** + +- Since this module is unofficial, you will first need to download the sources, compile, and install it: + +```bash +# Install build tools +sudo apt install git apache2-dev + +# Grab the sources +git clone [https://github.com/roadrunner2/mod-proxy-protocol.git](https://github.com/roadrunner2/mod-proxy-protocol.git) +cd mod-proxy-protocol + +# Build and install the module +sudo apxs -i -a -c mod_proxy_protocol.c +``` + +- Then configure Apache: + +```apache +1. +2. ProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod-proxy-protocol` module, please consult [its documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. + +##### **With mod_remoteip** + +- Since the module is experimental, you will first need to install an experimental version of Apache, which is not recommended in a production environment unless you know exactly what you're doing! +- Then configure Apache: + +```apache +1. +2. RemoteIPProxyProtocol On +3. ... +4. +``` + +- Replace `%h` variables with `%a` in the `LogFormat` directives of the Apache configuration. +- Finally, activate the new configuration with: + +```bash +# Enable the 'remoteip' module and configuration +a2enmod remoteip + +# Restart apache to load the new module ("reload" is enough if the module was already enabled) +service apache2 restart +``` + +To learn more about configuring the `mod_remoteip` module, please consult [its documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. + +#### HAProxy + +ProxyProtocol was designed by the HAProxy team, making it the software that best manages this protocol. This can be useful in a scenario where tracking the client's true source IP address is essential, but the target software does not support this protocol. This would be the case, for example, for MySQL and PostgreSQL, to name just two. + +In this case, a trick is to place a local HAProxy instance in front of the software and ensure logging of requests and their advanced filtering in the local HAProxy instance. + +This guide provides an example of a possible configuration for TCP port 3306 used by MySQL. This configuration is not intended to be a complete example but rather to serve as a basis for a functional setup. + +- Install HAProxy + +```bash +sudo apt install haproxy +``` + +- Configure your proxy + +```haproxy +1. listen mysql +2. # Listen on all interfaces, port 3306, tcp mode (ie: not HTTP) +3. mode tcp +4. option tcplog +5. bind *:3306 +6. +7. # Expect ProxyProtocol header if and only if from a trusted network +8. # See [https://www.ovh.com/manager/cloud/index.html#/network/iplb/](https://www.ovh.com/manager/cloud/index.html#/network/iplb/) for an up to date list +9. tcp-request connection expect-proxy layer4 if { src 10.108.0.0/14 } +10. +11. # Declare local server, on a non standard port to avoid collisions +12. server mysql 127.0.0.1:3316 check +``` + +- Finally, activate the new configuration with: + +```bash +service haproxy reload +``` + +## Go Further + +Discuss with our [user community](/links/community). diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.fr-ca.md b/pages/network/load_balancer/create_proxyprotocol/guide.fr-ca.md index 7d12b07732d..a957f8a3ba9 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.fr-ca.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.fr-ca.md @@ -1,87 +1,100 @@ --- -title: Travailler avec le proxyProtocol -universe: cloud -excerpt: Intégrez vos services TCP derriere un Load Balancer avec le proxyProtocol -updated: 2018-10-12 +title: "Configuration d'un service OVHcloud Load Balancer avec le proxyProtocol" +excerpt: Intégrez vos services TCP derrière un Load Balancer avec le proxyProtocol +updated: 2022-03-25 --- -## Introduction -Le service OVH Load Balancer agit comme un mandataire ou "Proxy". Comme un mandataire humain, il agit comme un intermédiaire, de telle sorte que le client s'adresse au mandataire et le mandataire au fournisseur de service, au nom du client. Dans cette configuration, seul le mandataire connaît à la fois le véritable client (l'utilisateur de votre service) et le véritable fournisseur de service (l'un de vos serveurs). +## Objectif -Pour le visiteur, cela ne pose aucun soucis. Il n'a pas besoin de connaître avec précision le serveur qui répond à sa requête. C'est un détail d'implémentation. En revanche, pour des raisons de statistique et de sécurité, il est parfois indispensable que le serveur final ait connaissance de la véritable adresse du client, or, par défaut, il ne voit que le mandataire (en l’occurrence, votre service OVH Load Balancer). +Le service OVHcloud Load Balancer agit comme un mandataire ou « Proxy ». Comme un mandataire humain, il agit comme un intermédiaire, de telle sorte que le client s'adresse au mandataire et le mandataire au fournisseur de service, au nom du client. Dans cette configuration, seul le mandataire connaît à la fois le véritable client (l'utilisateur de votre service) et le véritable fournisseur de service (l'un de vos serveurs). -Si vous utilisez un `Frontend`{.action} HTTP, nous vous recommandons le [guide](/pages/network/load_balancer/create_headers){.ref} qui décrit la manière standard d'utiliser les En-Têtes HTTP pour retrouver l'adresse IP, le port ainsi que le protocole source. +Pour le visiteur, cela ne pose aucun souci. Il n'a pas besoin de connaître avec précision le serveur qui répond à sa requête. C'est un détail d'implémentation. En revanche, pour des raisons de statistiques et de sécurité, il est parfois indispensable que le serveur final ait connaissance de la véritable adresse du client. Or, par défaut, il ne voit que le mandataire (en l’occurrence, votre service OVHcloud Load Balancer). -Si vous utilisez un `Frontend`{.action} TCP, alors ce guide est pour vous. +Si vous utilisez un frontend HTTP, nous vous recommandons le guide « [Configuration d'un service OVHcloud Load Balancer - Les en-têtes HTTP](/pages/network/load_balancer/create_headers) » qui décrit la manière standard d'utiliser les en-têtes HTTP pour retrouver l'adresse IP, le port ainsi que le protocole source. + +**Si vous utilisez un frontend TCP, alors ce guide vous est destiné.** ## Prérequis -Ce guide est un guide avancé. Il fait l'hypothèse que vous vous êtes déjà familiarisé avec les fonctionnalités principales de votre service OVH Load Balancer, en particulier, les `Frontend`{.action} et les `Fermes`{.action}. Si ce n'est pas encore le cas, nous vous recommandons de visiter le [guide](/pages/network/load_balancer/create_http_https){.ref}. Ce guide est plus particulièrement orienté sur les services HTTP mais les principes généraux sont les mêmes. -Vous devez disposez de : +Ce guide est un guide avancé. Il fait l'hypothèse que vous vous êtes déjà familiarisé avec les fonctionnalités principales de votre service OVHcloud Load Balancer, en particulier les **frontend** et les **clusters**. Si ce n'est pas encore le cas, nous vous recommandons de consulter le guide « [Configurer un service OVHcloud Load Balancer HTTP/HTTPS](/pages/network/load_balancer/create_http_https) ». Ce guide est plus particulièrement orienté sur les services TCP mais les principes généraux sont les mêmes. + +Vous devez disposer de : + +- un service OVHcloud Load Balancer avec un frontend et un cluster TCP fonctionnels; +- Nginx ou Apache avec mod_proxyprotocol sur un serveur OVHcloud. + +> [!warning] +> Les champs ProxyProtocol pouvant être forgés par un client malicieux, ils ne doivent être pris en compte que s’ils viennent d’une source de confiance. +> +> Il est donc indispensable de limiter leur utilisation à des adresses IP de confiance, en l’occurrence les adresses IP de sortie de votre service OVHcloud Load Balancer. Les principaux serveurs tels que Nginx et Apache disposent de modules capable de gérer cet aspect de sécurité et de confiance. -- Un service OVH Load Balancer avec un `Frontend`{.action} et une `Ferme`{.action} TCP fonctionnels -- Nginx ou Apache avec mod_proxyprotocol sur un serveur OVH +## En pratique -## Avertissement -Les champs ProxyProtocol pouvant être forgés par un client malicieux, ils ne doivent être pris en compte que s’ils viennent d’une source de confiance. +### Obtenir la liste de vos adresses IP de sortie -Il est donc indispensable de limiter leurs utilisations à des IP de confiance, en l’occurrence, les IPs de sortie de votre service OVH Load Balancer. Les principaux serveurs tels que Nginx et Apache disposent de modules capable de gérer cet aspect de sécurité et de confiance. +#### Depuis l'espace client OVHcloud -Vous pouvez obtenir la liste de vos IPs de sortie via le Manager et via l'API. +La liste des IPv4 de sortie potentiellement utilisées par votre service OVHcloud Load Balancer se trouve sur la page d'accueil de votre service OVHcloud Load Balancer sous le nom « IPv4 de sortie ». -### Via le Manager -La liste des IPv4 de sortie potentiellement utilisées par votre service OVH Load Balancer se trouve sur la page d'accueil de votre service OVH Load Balancer dans le manager sous le nom "IPv4 de sortie". +![Adresse IPv4 de sortie de votre service OVHcloud Load Balancer](images/iplb_service.png){.thumbnail} -![Adresse IPv4 de sortie de votre service OVH Load Balancer](images/iplb_service.png){.thumbnail} +#### Depuis l'API OVHcloud -### Via l'API -- Liste des IPs utilisées par votre service OVH Load Balancer +- Liste des adresses IP utilisées par votre service OVHcloud Load Balancer : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/natIp > -## Presentation du ProxyProtocol -Le ProxyProtocol a été développé par l'équipe du Load Balancer [HAPRoxy](http://haproxy.org/){.external} comme l'homologue en TCP des En-Têtes HTTP standards telles que X-Forwarded-For. Il a été pensé pour faire suivre au minimum : +### Présentation du ProxyProtocol -- le nom du protocole L4 utilisé (TCP4 pour l'IPv4 ou TCP6 pour l'IPv6) ; -- l'adresse IPv4 ou IPv6 source ; +Le ProxyProtocol a été développé par l'équipe du Load Balancer [HAPRoxy](http://haproxy.org/){.external} comme l'homologue en TCP des en-têtes HTTP standards tels que X-Forwarded-For. Il a été pensé pour faire suivre au minimum : + +- le nom du protocole L4 utilisé (TCP4 pour l'IPv4 ou TCP6 pour l'IPv6); +- l'adresse IPv4 ou IPv6 source; - le port source. -Quand le ProxyProtocol est activé pour un de vos serveurs, le service OVH Load Balancer ajoute un préfixe avec le ProxyProtocol avant d'envoyer la suite de la requête. Cette modification étant intrusive, il est indispensable de bien s'assurer que le serveur est bien compatible avec ce protocole, et, le cas échéant, quelles sont les version gérées. +Quand le ProxyProtocol est activé pour un de vos serveurs, le service OVHcloud Load Balancer ajoute un préfixe avec le ProxyProtocol avant d'envoyer la suite de la requête. Cette modification étant intrusive, il est indispensable de bien s'assurer que le serveur est bien compatible avec ce protocole, et, le cas échéant, quelles sont les version gérées. + +En effet, ce protocole existe en 2 versions : -En effet, ce protocole existe en 2 versions: - La version 1, au format texte - La version 2, au format binaire optimisé et extensible +- la version 1, au format texte; +- la version 2, au format binaire optimisé et extensible. -La version 1 étant largement suffisante pour la plupart des usages (bien que moins optimisée), elle est souvent la seule version gérée par les logiciels compatibles. La version 2 étant un format binaire, est plus rapide à analyser. Elle ajoute également la possibilité d'indiquer si la connexion d'origine était chiffrée (l'équivalent de l'En-Tête X-Forwarded-Proto) ainsi que le domaine spécifiée dans le champ Common Name du certificat utilisé le cas échéant. +La version 1 étant largement suffisante pour la plupart des usages (bien que moins optimisée), elle est souvent la seule version gérée par les logiciels compatibles. La version 2 étant un format binaire, elle est plus rapide à analyser. Elle ajoute également la possibilité d'indiquer si la connexion d'origine était chiffrée (l'équivalent de l'en-tête X-Forwarded-Proto) ainsi que le domaine spécifié dans le champ Common Name du certificat utilisé le cas échéant. Pour en savoir plus sur le ProxyProtocol, nous vous invitons à consulter la [spécification du ProxyProtocol](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt){.external}. -## Activation du ProxyProtocol pour un de vos serveurs -Le ProxyProtocol doit être activé pour chaque serveur enregistré dans une Ferme de serveurs. Cette fonctionnalité étant intrusive et ne pouvant être activée de manière transparente, cela permet de la tester sur une machine en particulier puis de déployer progressivement la configuration sur une ferme active. +### Activation du ProxyProtocol pour un de vos serveurs -Votre service OVH Load Balancer gère 4 modes pour le ProxyProtocol: +Le ProxyProtocol doit être activé pour chaque serveur enregistré dans un cluster de serveurs. Cette fonctionnalité étant intrusive et ne pouvant être activée de manière transparente, cela permet de la tester sur une machine en particulier puis de déployer progressivement la configuration sur un cluster actif. + +Votre service OVHcloud Load Balancer gère 4 modes pour le ProxyProtocol: |Mode|Description| |---|---| |v1|Version 1 au format texte. C'est la version la plus largement gérée.| |v2|Version 2 au format binaire sans aucune option. Il s'agit d'une version optimisée de la version 1.| -|v2-ssl|v2, avec un champs décrivant la connexion SSL, si applicable.| +|v2-ssl|v2, avec un champ décrivant la connexion SSL, si applicable.| |v2-ssl-cn|v2-ssl, avec le champ "Common Name" du certificat utilisé, si applicable.| -Lorsque le ProxyProtocol est activé pour l'un de vos serveurs, les sondes insèrent automatiquement cet entête *sauf* si un port spécifique a été spécifié pour les sondes. Dans ce cas, la sonde se connectera de manière classique sur le port de la sonde. +Lorsque le ProxyProtocol est activé pour l'un de vos serveurs, les sondes insèrent automatiquement cet en-tête **sauf** si un port spécifique a été spécifié pour les sondes. Dans ce cas, la sonde se connectera de manière classique sur le port de la sonde. + +#### Depuis l'espace client OVHcloud -### Via le Manager -Dans la section `Fermes`{.action}, sélectionnez la Ferme contenant le serveur sur lequel activer le ProxyProtocol puis cliquez le bouton d'édition du Serveur concerné. +Dans la section `Clusters`{.action}, sélectionnez le cluster contenant le serveur sur lequel activer le ProxyProtocol puis cliquez sur le bouton d'édition du serveur concerné. Le ProxyProtocol se configure via l'option `Version du ProxyProtocol`{.action}. Vous y retrouverez les 4 modes décrits ci-dessus. -![Activation du ProxyProtocol sur un serveur d'une ferme](images/edit_server.png){.thumbnail} +![Activation du ProxyProtocol sur un serveur d'un cluster](images/edit_server.png){.thumbnail} Une fois le mode souhaité sélectionné, cliquez sur `Mettre à jour`{.action} puis sur `Déployer la zone: VOTRE ZONE`{.action} pour appliquer vos changements dans la zone concernée. -### Via l'API -L'activation du ProxyProtocol via l'API se fait de la même manière que via le Manager. Le champs d'API correspondant dans le Serveur est proxyProtocolVersion. +#### Depuis l'API OVHcloud + +L'activation du ProxyProtocol via l'API se fait de la même manière que depuis l'espace client OVHcloud. +Le champ d'API correspondant dans le serveur est proxyProtocolVersion. - Modifier un `Serveur`{.action} existant : @@ -97,19 +110,20 @@ L'activation du ProxyProtocol via l'API se fait de la même manière que via le > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Configuration du ProxyProtocol coté serveur +### Configuration du ProxyProtocol coté serveur + +#### Nginx -### Nginx -Nginx gère la version 1 du ProxyProtocol. Il est capable d'en extraire les principales informations, à savoir l'adresse IP et le port source du client tels que vu par votre service OVH Load Balancer. Dans Nginx, ces informations sont exposées à travers la variable proxy_protocol_addr. De même que pour son homologue HTTP X-Forwarded-For Nginx se servir de cette variable pour prendre en compte la bonne adresse source dans les logs avec le module ngx_http_realip. +Nginx gère la version 1 du ProxyProtocol. Il est capable d'en extraire les principales informations, à savoir l'adresse IP et le port source du client tels que vus par votre service OVHcloud Load Balancer. Dans Nginx, ces informations sont exposées à travers la variable proxy_protocol_addr. De même que pour son homologue HTTP X-Forwarded-For, Nginx se servira de cette variable pour prendre en compte la bonne adresse source dans les logs avec le module ngx_http_realip. Pour utiliser le ProxyProtocol avec Nginx, vous pouvez configurer le section server de votre configuration avec : -```nginx +```bash 1. server { 2. # Enable the Proxy protocol on port 80 3. listen 80 proxy_protocol; 4. -5. # Trust the proxy protocol provided informations from your OVH Load Balancer service +5. # Trust the proxy protocol provided informations from your OVHcloud Load Balancer service 6. # See https://www.ovh.com/manager/cloud/index.html#/network/iplb/ for an up to date list 7. set_real_ip_from 10.108.0.0/14; 8. real_ip_header proxy_protocol; @@ -131,27 +145,30 @@ service nginx reload > [!primary] > -> Cet exemple utilise le protocole HTTP pour plus de simplicité. Si vous utilisez du HTTP, nous vous recommandons vivement d'utiliser les En-Têtes HTTP au lieu du ProxyProtocol sauf si votre service OVH Load Balancer est configuré en TCP. Cela peut se produire dans le cas d'une terminaison SSL pour du HTTP/2 par exemple. +> Cet exemple utilise le protocole HTTP pour plus de simplicité. Si vous utilisez du HTTP, nous vous recommandons vivement d'utiliser les en-têtes HTTP au lieu du ProxyProtocol, sauf si votre service OVHcloud Load Balancer est configuré en TCP. Cela peut se produire dans le cas d'une terminaison SSL pour du HTTP/2 par exemple. > Pour plus d'informations sur la configuration du ProxyProtocol dans Nginx, nous vous invitons à consulter la documentation officielle du projet: [https://www.nginx.com/resources/admin-guide/proxy-protocol/](https://www.nginx.com/resources/admin-guide/proxy-protocol/){.external} -### Apache -La gestion du ProxyProtocol dans Apache est encore jeune. Une implémentation non-officielle et compatible avec Apache 2.4 est disponible sur Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) mais n'est plus maintenue depuis 2014. Une implémentation officielle se trouve dans le module mod_remoteip qui est également utilisé pour gérer les En-Têtes de la famille X-Forwarded-For. +#### Apache -mod-proxy-protocol gère les version 1 et 2 du ProxyProtocol. En revanche, il ne permet pas de spécifier une liste d'IP source autorisées à utiliser le ProxyProtocol, bien que ce soit évoqué dans les projets du module. +La gestion du ProxyProtocol dans Apache est encore jeune. Une implémentation non-officielle et compatible avec Apache 2.4 est disponible sur Github ([https://github.com/roadrunner2/mod-proxy-protocol](https://github.com/roadrunner2/mod-proxy-protocol){.external}) mais n'est plus maintenue depuis 2014. Une implémentation officielle se trouve dans le module mod_remoteip qui est également utilisé pour gérer les en-têtes de la famille X-Forwarded-For. -mod_remoteip gère également les version 1 et 2 du ProxyProtocol. Il ajoute également la possibilité de spécifier une liste d'adresses pour lesquelles le ProxyProtocol ne doit pas être activé. Ce qui reste limitant d'une point de vue de la configuration. Ce module est uniquement disponible dans la version expérimentale Apache 2.5 bien que la documentation mentionne une disponibilité à partir de Apache 2.4.26. +mod-proxy-protocol gère les versions 1 et 2 du ProxyProtocol. En revanche, il ne permet pas de spécifier une liste d'adresses IP source autorisées à utiliser le ProxyProtocol, bien que ce soit évoqué dans les projets du module. -Quel que soit l'approche choisie, nous vous recommandons vivement de bien restreindre les connexions à vos serveurs aux adresses de sortie de votre service OVH Load Balancer. Cela peut être aisément configuré avec iptables: +mod_remoteip gère également les versions 1 et 2 du ProxyProtocol. Il ajoute également la possibilité de spécifier une liste d'adresses pour lesquelles le ProxyProtocol ne doit pas être activé. Ce qui reste limitant du point de vue de la configuration. Ce module est uniquement disponible dans la version expérimentale Apache 2.5, bien que la documentation mentionne une disponibilité à partir de Apache 2.4.26. + +Quelle que soit l'approche choisie, nous vous recommandons vivement de bien restreindre les connexions à vos serveurs aux adresses de sortie de votre service OVHcloud Load Balancer.
+Cela peut être aisément configuré avec iptables: ```bash -# Trust connections from your OVH Load Balancer service, ONLY +# Trust connections from your OVHcloud Load Balancer service, ONLY iptables -A INPUT -s 10.108.0.0/14 -p tcp --dport 80 -j ACCEPT iptables -A INPUT -p tcp --dport 80 -j DROP ``` -#### Avec mod-proxy-protocol +##### **Avec mod-proxy-protocol** + - Ce module n'étant pas officiel, il faudra commencer par en télécharger les sources, compiler et installer : ```bash @@ -175,7 +192,7 @@ sudo apxs -i -a -c mod_proxy_protocol.c 4. ``` -- Remplacez les variables %h par %a dans les directives LogFormat de la configuration Apache +- Remplacez les variables `%h` par `%a` dans les directives LogFormat de la configuration Apache - Enfin, activez la nouvelle configuration avec : ```bash @@ -183,10 +200,11 @@ sudo apxs -i -a -c mod_proxy_protocol.c service apache2 restart ``` -Pour en savoir plus sur la configuration du module mod-proxy-protocol nous vous invitons à consulter sa documentation: [http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external} +Pour en savoir plus sur la configuration du module mod-proxy-protocol nous vous invitons à consulter [sa documentation](http://roadrunner2.github.io/mod-proxy-protocol/mod_proxy_protocol.html){.external}. -#### Avec mod_remoteip -- Le module étant expérimental, il faudra au préalable installé une version expérimentale de Apache, ce qui n'est pas recommandé dans une environnement de production, à moins de savoir précisément ce que l'on fait ! +##### **Avec mod_remoteip** + +- Le module étant expérimental, il faudra au préalable installer une version expérimentale de Apache, ce qui n'est pas recommandé dans un environnement de production, à moins de savoir précisément ce que l'on fait ! - Puis configurer Apache : ```apache @@ -196,7 +214,7 @@ Pour en savoir plus sur la configuration du module mod-proxy-protocol nous vous 4. ``` -- Remplacez les variables %h par %a dans les directives LogFormat de la configuration Apache +- Remplacez les variables `%h` par `%a` dans les directives LogFormat de la configuration Apache - Enfin, activez la nouvelle configuration avec : ```bash @@ -207,14 +225,15 @@ a2enmod remoteip service apache2 restart ``` -Pour en savoir plus sur la configuration du module mod_remoteip nous vous invitons à consulter sa documentation: [https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external} +Pour en savoir plus sur la configuration du module mod_remoteip, nous vous invitons à consulter [sa documentation](https://httpd.apache.org/docs/trunk/mod/mod_remoteip.html#remoteipproxyprotocol){.external}. + +#### HAProxy -### HAProxy -Le ProxyProtocol a été conçu par l'équipe de HAProxy. Il est donc le logiciel gérant le mieux ce protocole. Cela pourra être utile dans un scénario où le suivi de la véritable IP source du client est indispensable mais le logiciel cible ne gère pas ce protocole. Ce sera le cas par exemple de MySQL et PostgreSQL pour n'en citer que 2. +Le ProxyProtocol a été conçu par l'équipe de HAProxy. Il est donc le logiciel gérant le mieux ce protocole. Cela pourra être utile dans un scénario où le suivi de la véritable adresse IP source du client est indispensable, mais le logiciel cible ne gère pas ce protocole. Ce sera le cas par exemple de MySQL et PostgreSQL pour n'en citer que 2. -Dans ce cas, une astuce est de placer une instance HAProxy locale, en frontal du logiciel et assurer la journalisation des requête et leur filtrage avancé dans l'instance HAProxy locale. +Dans ce cas, une astuce est de placer une instance HAProxy locale, en frontal du logiciel et assurer la journalisation des requêtes et leur filtrage avancé dans l'instance HAProxy locale. -Ce guide vous propose un exemple de configuration possible pour le port TCP 3306 utilisé par MySQL. Cette configuration n'a pas vocation a être un exemple complet mais plutôt à servir de base de manière à partir sur une configuration fonctionnelle. +Ce guide vous propose un exemple de configuration possible pour le port TCP 3306 utilisé par MySQL. Cette configuration n'a pas vocation a être un exemple complet mais plutôt à servir de base, de manière à partir sur une configuration fonctionnelle. - Installez HAProxy @@ -244,3 +263,7 @@ sudo apt install haproxy ```bash service haproxy reload ``` + +## Aller plus loin + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md b/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md index c0f551a16b4..f9c97f262d2 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md @@ -25,11 +25,11 @@ Vous pouvez être tenus de conserver des logs et certaines données relatives au ## Prérequis -Ce guide est un guide avancé. Il fait l'hypothèse que vous vous êtes déjà familiarisé avec les fonctionnalités principales de votre service OVHcloud Load Balancer, en particulier les **frontend** et les **fermes**. Si ce n'est pas encore le cas, nous vous recommandons de consulter le guide « [Configurer un service OVHcloud Load Balancer HTTP/HTTPS](/pages/network/load_balancer/create_http_https) ». Ce guide est plus particulièrement orienté sur les services TCP mais les principes généraux sont les mêmes. +Ce guide est un guide avancé. Il fait l'hypothèse que vous vous êtes déjà familiarisé avec les fonctionnalités principales de votre service OVHcloud Load Balancer, en particulier les **frontend** et les **clusters**. Si ce n'est pas encore le cas, nous vous recommandons de consulter le guide « [Configurer un service OVHcloud Load Balancer HTTP/HTTPS](/pages/network/load_balancer/create_http_https) ». Ce guide est plus particulièrement orienté sur les services TCP mais les principes généraux sont les mêmes. Vous devez disposer de : -- un service OVHcloud Load Balancer avec un frontend et une ferme TCP fonctionnels; +- un service OVHcloud Load Balancer avec un frontend et un cluster TCP fonctionnels; - Nginx ou Apache avec mod_proxyprotocol sur un serveur OVHcloud. > [!warning] @@ -77,7 +77,7 @@ Pour en savoir plus sur le ProxyProtocol, nous vous invitons à consulter la [sp ### Activation du ProxyProtocol pour un de vos serveurs -Le ProxyProtocol doit être activé pour chaque serveur enregistré dans une ferme de serveurs. Cette fonctionnalité étant intrusive et ne pouvant être activée de manière transparente, cela permet de la tester sur une machine en particulier puis de déployer progressivement la configuration sur une ferme active. +Le ProxyProtocol doit être activé pour chaque serveur enregistré dans un cluster de serveurs. Cette fonctionnalité étant intrusive et ne pouvant être activée de manière transparente, cela permet de la tester sur une machine en particulier puis de déployer progressivement la configuration sur un cluster actif. Votre service OVHcloud Load Balancer gère 4 modes pour le ProxyProtocol: @@ -92,11 +92,11 @@ Lorsque le ProxyProtocol est activé pour l'un de vos serveurs, les sondes insè #### Depuis l'espace client OVHcloud -Dans la section `Fermes`{.action}, sélectionnez la ferme contenant le serveur sur lequel activer le ProxyProtocol puis cliquez sur le bouton d'édition du serveur concerné. +Dans la section `Clusters`{.action}, sélectionnez le cluster contenant le serveur sur lequel activer le ProxyProtocol puis cliquez sur le bouton d'édition du serveur concerné. Le ProxyProtocol se configure via l'option `Version du ProxyProtocol`{.action}. Vous y retrouverez les 4 modes décrits ci-dessus. -![Activation du ProxyProtocol sur un serveur d'une ferme](images/edit_server.png){.thumbnail} +![Activation du ProxyProtocol sur un serveur d'un cluster](images/edit_server.png){.thumbnail} Une fois le mode souhaité sélectionné, cliquez sur `Mettre à jour`{.action} puis sur `Déployer la zone: VOTRE ZONE`{.action} pour appliquer vos changements dans la zone concernée. @@ -127,7 +127,7 @@ Nginx gère la version 1 du ProxyProtocol. Il est capable d'en extraire les prin Pour utiliser le ProxyProtocol avec Nginx, vous pouvez configurer le section server de votre configuration avec : -```nginx +```bash 1. server { 2. # Enable the Proxy protocol on port 80 3. listen 80 proxy_protocol;