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..b86b71fbb4d 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: 2018-10-12 +title: "Configuring an OVHcloud Load Balancer with ProxyProtocol" +excerpt: Integrate your TCP services behind a Load Balancer with ProxyProtocol +updated: 2025-07-30 --- -## 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 farm 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/ 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/){.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 +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/ 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). \ No newline at end of file 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..ec6496e0936 100644 --- a/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md +++ b/pages/network/load_balancer/create_proxyprotocol/guide.fr-fr.md @@ -112,7 +112,7 @@ Le champ d'API correspondant dans le serveur est proxyProtocolVersion. > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server/{serverId} > -- Appliquer les modifications: +- Appliquer les modifications : > [!api] > @@ -123,7 +123,7 @@ Le champ d'API correspondant dans le serveur est proxyProtocolVersion. #### 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 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. +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 : @@ -137,12 +137,12 @@ Pour utiliser le ProxyProtocol avec Nginx, vous pouvez configurer le section ser 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; +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. ... +14. # Insert your regular configuration here +15. ... 16. } ``` @@ -157,15 +157,15 @@ service nginx reload > 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} +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/){.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. +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-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. +`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. -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. +`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: @@ -201,7 +201,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 @@ -223,7 +223,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 @@ -234,7 +234,7 @@ 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){.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 @@ -244,13 +244,13 @@ Dans ce cas, une astuce est de placer une instance HAProxy locale, en frontal du 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 +- Installez HAProxy : ```bash sudo apt install haproxy ``` -- Configurez votre proxy +- Configurez votre proxy : ```haproxy 1. listen mysql @@ -275,4 +275,4 @@ service haproxy reload ## 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 diff --git a/pages/network/load_balancer/use-lb/guide.de-de.md b/pages/network/load_balancer/use-lb/guide.de-de.md index 17895e06aa9..6adcd0223ea 100644 --- a/pages/network/load_balancer/use-lb/guide.de-de.md +++ b/pages/network/load_balancer/use-lb/guide.de-de.md @@ -1,7 +1,7 @@ --- title: Verwaltung des Loadbalancers über das Kundencenter excerpt: Zusammenfassung der wesentlichen Funktionen zur Verwaltung des Loadbalancers über das Kundencenter -updated: 2017-12-01 +updated: 2025-07-30 --- ## Einleitung @@ -28,8 +28,8 @@ Auf der Hauptseite finden Sie folgende Informationen: |Status|Zusammenfassung Ihres Loadbalancers mit dem Namen des Dienstes, den Frontends, den funktionsfähigen Farmen und den hinzugefügten Servern| |Verwendung|Zusammenfassung der Verwendung Ihres Loadbalancers| |Graphen|Hier finden Sie die mit Ihrer Dienstleistung verbundenen Graphen zur Anzahl der Simultanverbindungen oder der Anfragen pro Minute| -|Informationen|Ihre IPv4 und die verbundenen Additional IPs sowie die Anzahl der ausgehenden IPv4 (Details durch Klicken auf die Auslassungspunkte)| -|Konfiguration|Hier können Sie den Namen Ihres Angebots (er erscheint oben und in der Spalte links) sowie die Ciphers anpassen. Außerdem wird hier das Rechenzentrum Ihres Loadbalancers angezeigt.| +|Information|Ihre IPv4- und IPv6-Adressen und die damit verbundenen Additional IPs sowie die Anzahl der ausgehenden IPv4-Adressen (weitere Informationen erhalten Sie, wenn Sie auf die Schaltfläche `...`{.action} klicken)| +|Konfiguration|Hier können Sie den Namen Ihrer Lösung anpassen (der oben in der linken Spalte angezeigt wird). Die Verschlüsselung(en) kann/können angepasst werden, ebenso wie die Verfügbarkeitszone, in der sich Ihr Loadbalancer befindet| |Abo|Hier finden Sie die administrativen Details zu Ihrem Angebot| Um ein `Frontend`{.action} oder eine `Serverfarm`{.action} hinzuzufügen, gehen Sie in den jeweiligen Tab und klicken Sie einfach auf die entsprechenden Schaltflächen. Ein Formular hilft Ihnen anschließend dabei, jeden Bestandteil Ihres Dienstes zu konfigurieren. @@ -47,7 +47,7 @@ Details zu den Elementen eines Frontends: |Name|Wenn Sie möchten, können Sie Ihrem Frontend einen Namen geben. Wenn Sie mehrere Frontends besitzen, können Sie diese so schneller unterscheiden.| |Protokoll|Sie haben die Wahl zwischen HTTP, HTTPS, TCP, SSL TCP (TLS) und UDP| |Port|Wählen Sie den zu verwendenden Eingangsport aus| -|Rechenzentrum|Für die Erstellung Ihres Frontends können Sie zwischen Ihrem Rechenzentrum oder allen wählen| +|Rechenzentrum|Wählen Sie zwischen Ihrer Verfügbarkeitszone oder allen Verfügbarkeitszonen, um Ihr Front-End zu erstellen| |Standardfarm|Wenn Sie mehrere Serverfarmen eingestellt haben, können Sie für jedes Frontend eine Standardfarm auswählen.| Sie haben außerdem Zugriff auf die erweiterten Einstellungen: @@ -89,6 +89,7 @@ Nachdem Ihre Serverfarm angelegt wurde, müssen Sie ihr nur noch Server zuweisen |Cookie|Fügen Sie einen personalisierten Sitzungscookie hinzu| |Zertifikatskette|Fügen Sie eine Zertfikatskette hinzu| |Verteilungsgewicht|Auswahl des Verteilungsgewichts für die Lastverteilung| +|Proxy-Protokollversion|**Nur wenn Sie das Proxy-Protokoll bereits konfiguriert haben**, wählen Sie die Proxy-Protokollversion aus, die Sie auf diesem Server verwenden möchten.
Weitere Informationen zum Proxy-Protokoll und dessen Verwendung mit dem Loadbalancer von OVHcloud finden Sie in [dieser Anleitung](/pages/network/load_balancer/create_proxyprotocol/).| ### Verwaltung der SSL-Zertifikate Im Bereich `SSL-Zertifikate`{.action} ist es möglich, den Loadbalancer um eine SSL-Verschlüsselung zu ergänzen. Sie haben zwei Möglichkeiten: Sie können ein SSL-Zertifikat über OVH bestellen oder ein externes Zertifikat hinzufügen. @@ -118,4 +119,4 @@ Wenn Sie bereits über ein eigenes SSL-Zertifikat verfügen, können Sie es dire ## Weiterführende Informationen -Für den Austausch mit unserer User Community gehen Sie auf . \ No newline at end of file +Treten Sie unserer [User Community](/links/community) bei. \ No newline at end of file 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..8d2a654a040 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-30 --- ## 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](/links/network/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 addresses 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 zone 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..8d2a654a040 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-30 --- ## 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](/links/network/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 addresses 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 zone 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..8d2a654a040 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-30 --- ## 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](/links/network/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 addresses 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 zone 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-gb.md b/pages/network/load_balancer/use-lb/guide.en-gb.md index 8e94ed605fc..8d2a654a040 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-30 --- ## Objective @@ -11,7 +11,7 @@ This guide is designed to help you get started using the Load Balancer, by intro ## Requirements - You must have access to your OVH Control Panel. -- You must have ordered a [Load Balancer.](/links/network/load-balancer) +- You must have ordered a [Load Balancer](/links/network/load-balancer). ## Instructions @@ -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 addresses 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 zone 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.en-sg.md b/pages/network/load_balancer/use-lb/guide.en-sg.md index 9c708ab1ea6..8d2a654a040 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-30 --- ## 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](/links/network/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 addresses 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 zone 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..8d2a654a040 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-30 --- ## 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](/links/network/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 addresses 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 zone 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.es-es.md b/pages/network/load_balancer/use-lb/guide.es-es.md index 6695081a1b3..ec4e36981f4 100644 --- a/pages/network/load_balancer/use-lb/guide.es-es.md +++ b/pages/network/load_balancer/use-lb/guide.es-es.md @@ -1,13 +1,15 @@ --- title: Gestionar el servicio Load Balancer desde el área de cliente excerpt: Principales funcionalidades y toma de contacto con el servicio Load Balancer en el área de cliente -updated: 2017-12-01 +updated: 2025-07-30 --- ## Objetivo + Esta guía explica los primeros pasos con el servicio Load Balancer y presenta sus principales funcionalidades. ## Requisitos + - Tener acceso al [área de cliente](/links/manager). - Haber contratado un [Load Balancer](/links/network/load-balancer). @@ -26,8 +28,8 @@ En dicha página, encontrará la siguiente información: |Estado|Resumen del Load Balancer, con el nombre asignado al servicio, los frontends, las granjas operativas y los servidores añadidos| |Uso|Resumen del uso del Load Balancer| |Gráficas|Gráficas del servicio, en conexiones simultáneas o peticiones por minuto| -|Información|IPv4 y las Additional IP asociadas, así como el número de IPv4 salientes (para ver el detalle, haga clic en los tres puntos)| -|Configuración|Personalización del nombre del servicio (que puede ver en la parte superior y en la columna izquierda) y de los ciphers, y datacenter en el que está localizado el Load Balancer| +Información|Sus direcciones IPv4 e IPv6 y las direcciones Additional IP asociadas, así como el número de IPv4 de salida (para más información, haga clic en el botón `...`{.action})| +|Configuración|Personalice aquí el nombre de su producto. También encontrará el cipher o los ciphers que pueden personalizarse, así como la zona de disponibilidad en la que se encuentra el Load Balancer| |Suscripción|Información administrativa del servicio| A continuación se explica cómo realizar las principales operaciones de administración del Load Balancer, relativas a los frontends, las granjas, los servidores y los certificados. @@ -45,7 +47,7 @@ Estos son los parámetros que pueden configurarse en un frontend: |Nombre|Puede asignarle un nombre a su frontend para poder identificarlo rápidamente| |Protocolo|Elija entre HTTP, HTTPS, TCP, SSL TCP (o TLS) o UDP| |Puerto|Seleccione el puerto de escucha| -|Datacenter|Seleccione entre su datacenter o todos para la creación del frontend| +|Datacenter|Puede elegir entre una zona de disponibilidad en particular o todas las zonas de disponibilidad para la creación del frontend| |Granja por defecto |Si tiene varias granjas configuradas, podrá elegir una por defecto para cada frontend| En función de la configuración anterior, aparecerán algunas de las siguientes posibilidades de configuración avanzada: @@ -89,6 +91,7 @@ Una vez haya creado la granja, solo tendrá que añadir los servidores haciendo |Cookie|Añada una cookie de sesión personalizada| |Cadena de certificación|Añada una cadena de certificación| |Peso de balanceo|Elija el peso del balanceo para el reparto de la carga| +|Versión del protocolo de PROXY|**Sólo si ya lo ha configurado**, elija la versión del protocolo de PROXY que desea utilizar en este servidor.
Encontrará más información sobre el protocolo PROXY y su uso con el servicio Load Balancer de OVHcloud en [esta guía](/pages/network/load_balancer/create_proxyprotocol/).| ### Administrar los certificados SSL En la pestaña `Certificados SSL`{.action}, puede añadir un SSL al Load Balancer, eligiendo entre dos opciones: contratar un certificado SSL en OVH o añadir un certificado externo. @@ -120,4 +123,4 @@ Si ya tiene su propio certificado SSL, puede añadirlo directamente: ## Más información -Interactúe con nuestra comunidad de usuarios en . \ No newline at end of file +Interactúe con nuestra [comunidad de usuarios](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.es-us.md b/pages/network/load_balancer/use-lb/guide.es-us.md index 214ef4c3932..0e1b7b03059 100644 --- a/pages/network/load_balancer/use-lb/guide.es-us.md +++ b/pages/network/load_balancer/use-lb/guide.es-us.md @@ -1,15 +1,17 @@ --- title: Gestionar el servicio Load Balancer desde el área de cliente excerpt: Principales funcionalidades y toma de contacto con el servicio Load Balancer en el área de cliente -updated: 2017-12-01 +updated: 2025-07-30 --- ## Objetivo + Esta guía explica los primeros pasos con el servicio Load Balancer y presenta sus principales funcionalidades. ## Requisitos + - Tener acceso al [área de cliente](/links/manager). -- Haber contratado un [Load Balancer](https://www.ovh.com/world/es/soluciones/load-balancer/). +- Haber contratado un [Load Balancer](/links/network/load-balancer). ## Procedimiento @@ -26,8 +28,8 @@ En dicha página, encontrará la siguiente información: |Estado|Resumen del Load Balancer, con el nombre asignado al servicio, los frontends, las granjas operativas y los servidores añadidos| |Uso|Resumen del uso del Load Balancer| |Gráficas|Gráficas del servicio, en conexiones simultáneas o peticiones por minuto| -|Información|IPv4 y las Additional IP asociadas, así como el número de IPv4 salientes (para ver el detalle, haga clic en los tres puntos)| -|Configuración|Personalización del nombre del servicio (que puede ver en la parte superior y en la columna izquierda) y de los ciphers, y datacenter en el que está localizado el Load Balancer| +Información|Sus direcciones IPv4 e IPv6 y las direcciones Additional IP asociadas, así como el número de IPv4 de salida (para más información, haga clic en el botón `...`{.action})| +|Configuración|Personalice aquí el nombre de su producto. También encontrará el cipher o los ciphers que pueden personalizarse, así como la zona de disponibilidad en la que se encuentra el Load Balancer| |Suscripción|Información administrativa del servicio| A continuación se explica cómo realizar las principales operaciones de administración del Load Balancer, relativas a los frontends, las granjas, los servidores y los certificados. @@ -45,7 +47,7 @@ Estos son los parámetros que pueden configurarse en un frontend: |Nombre|Puede asignarle un nombre a su frontend para poder identificarlo rápidamente| |Protocolo|Elija entre HTTP, HTTPS, TCP, SSL TCP (o TLS) o UDP| |Puerto|Seleccione el puerto de escucha| -|Datacenter|Seleccione entre su datacenter o todos para la creación del frontend| +|Datacenter|Puede elegir entre una zona de disponibilidad en particular o todas las zonas de disponibilidad para la creación del frontend| |Granja por defecto |Si tiene varias granjas configuradas, podrá elegir una por defecto para cada frontend| En función de la configuración anterior, aparecerán algunas de las siguientes posibilidades de configuración avanzada: @@ -90,6 +92,7 @@ Una vez haya creado la granja, solo tendrá que añadir los servidores haciendo |Cookie|Añada una cookie de sesión personalizada| |Cadena de certificación|Añada una cadena de certificación| |Peso de balanceo|Elija el peso del balanceo para el reparto de la carga| +|Versión del protocolo de PROXY|**Sólo si ya lo ha configurado**, elija la versión del protocolo de PROXY que desea utilizar en este servidor.
Encontrará más información sobre el protocolo PROXY y su uso con el servicio Load Balancer de OVHcloud en [esta guía](/pages/network/load_balancer/create_proxyprotocol/).| ### Administrar los certificados SSL En la pestaña `Certificados SSL`{.action}, puede añadir un SSL al Load Balancer, eligiendo entre dos opciones: contratar un certificado SSL en OVH o añadir un certificado externo. @@ -120,4 +123,4 @@ Si ya tiene su propio certificado SSL, puede añadirlo directamente: ## Más información -Interactúe con nuestra comunidad de usuarios en . \ No newline at end of file +Interactúe con nuestra [comunidad de usuarios](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.fr-ca.md b/pages/network/load_balancer/use-lb/guide.fr-ca.md index 9a16afc7bb8..7624aa5fce4 100644 --- a/pages/network/load_balancer/use-lb/guide.fr-ca.md +++ b/pages/network/load_balancer/use-lb/guide.fr-ca.md @@ -1,89 +1,88 @@ --- -title: Gestion du service de Répartiteur de charge via l'espace client -excerpt: Résumé des principales fonctionnalités et prise en main du service de Répartiteur de charge via l'espace client -updated: 2017-12-01 +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: 2025-07-30 --- ## Objectif -Ce guide a pour but de vous aider lors de la première prise en main de votre Répartiteur de charge en vous présentant les fonctionnalités principales de l'offre. +Ce guide a pour but de vous aider lors de la première prise en main de votre Load Balancer en vous présentant les fonctionnalités principales de l'offre. ## Prérequis -- Avoir accès à votre espace client -- Avoir commandé un [Répartiteur de charge](https://www.ovh.com/ca/fr/solutions/load-balancer/) +- Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. +- Être connecté à votre [espace client OVHcloud](/links/manager) ## En pratique -### Gérer son Répartiteur de charge via l'espace client +### Gérer son Load Balancer via l'espace client Pour gérer votre Load Balancer via l'espace client, rendez-vous dans la partie `Bare metal Cloud`{.action} puis cliquez sur `Network`{.action} et `Load Balancer`{.action}. Sélectionnez votre service. ![Load Balancer](images/lbip-main.png){.thumbnail} -Sur cette page principale, vous trouverez les informations suivantes: +Sur la page de résumé de votre service Load Balancer, vous trouverez les menus suivants : -|Élément|Fonction| +|Menu|Détails| |---|---| -|Statut|Résumé de votre Répartiteur de charge avec le nom du service, les serveurs frontaux (frontends), les fermes fonctionnelles et les serveurs ajoutés| -|Utilisation|Un récapitulatif de l'utilisation de votre Répartiteur de charge| -|Graphiques|Ici vous trouverez les graphiques liés à votre service en connexions simultanées ou en nombre de requêtes par minute| -|Informations|Votre IPv4 et les Additional IP liées ainsi que le nombre d'IPv4 de sortie (détail en cliquant sur les points de suspension)| -|Configuration|Ici vous pourrez personnaliser le nom de votre solution (qui apparaîtra en haut et dans la colonne de gauche). Le(s) texte(s) chiffré(s), qui sont personnalisables, ainsi que le centre de données où se situe votre Répartiteur de charge| -|Abonnement|Vous trouverez ici les détails administratifs de votre solution| +|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|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 un `serveur frontal`{.action} ou des `fermes de serveurs`{.action}, cliquez simplement sur leurs boutons respectifs. Un formulaire vous aidera ensuite à configurer chaque partie de votre service. +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. -### Gérer ses serveurs frontaux +### Gérer ses frontends -Afin d'ajouter des serveurs frontaux, il vous suffit de vous rendre dans la partie `Serveurs frontaux`{.action} et de cliquer sur `Ajouter un serveur frontal`{.action}. Vous aurez alors accès au menu suivant: +Afin d'ajouter des frontends, il vous suffit de vous rendre dans l'onglet `Frontends`{.action} et de cliquer sur `Ajouter un frontend`{.action}. Vous aurez alors accès au menu suivant : -![Ajouter un serveur frontal](images/iplb-add-front-end.png){.thumbnail} +![Ajout frontend](images/add_frontend.png){.thumbnail} -Détails des éléments d'un serveur frontal: +Détails des éléments d'un frontend : |Élément|Fonction| |---|---| -|Nom|Si vous le souhaitez, vous pouvez nommer votre serveur frontal, très utile quand vous en avez plusieurs afin de les identifier rapidement| +|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| -|Centre de données|Vous pouvez choisir entre votre centre de données ou tous pour la création du serveur frontal| -|Ferme par défaut|Si vous avez plusieurs fermes paramétrées, vous pourrez en choisir une par défaut pour chaque serveur frontal| +|Datacenter|Vous pouvez choisir entre une zone de disponibilité en particulier ou toutes les zones de disponibilité 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: +Vous avez également accès à des paramètres avancés : -![Paramètres avancés](images/advanced_frontend.png){.thumbnail} +![Parametres avances](images/advanced_frontend.png){.thumbnail} |Élément|Fonction| |---|---| -|Additional IP dédiée|La liste des Additional IP des serveurs distants| -|Resteindre l'accès à des IP|Liste permettant de restreindre l'accès distant au répartiteur de charge, uniquement en IPv4| +|Dedicated Additional IP|La liste des Additional IP des serveurs distants| +|Restreindre l'accès à des IPs|Liste permettant de restreindre l'accès distant au Load Balancer, uniquement en IPv4| |Redirection HTTP|Ajout d'une URL de redirection HTTP| -|Entête HTTP|Ajout ici d'un en-tête HTTP| +|Entête HTTP|Ajout d'un en-tête HTTP| ### Gérer ses fermes -Afin d'ajouter une ferme de serveurs, il vous suffit de vous rendre dans la partie `Fermes de serveurs`{.action} et de cliquer sur `Ajouter une ferme de serveurs`{.action}. Vous accéderez aux mêmes options principales que pour le serveur frontal. Les options avancées seront par contre différentes: +Afin d'ajouter une ferme de serveurs, il vous suffit de vous rendre dans l'onglet `Fermes de serveurs`{.action} et de cliquer sur `Ajouter une ferme de serveurs`{.action}. Vous accéderez aux mêmes options principales que pour le frontend. Les options avancées seront par contre différentes : -![Ajout d'une ferme](images/iplb-cluster-adv.png){.thumbnail} +![Ajout d'une ferme](images/advanced_cluster.png){.thumbnail} |Élément|Fonction| |---|---| |Mode de répartition|Choix entre Round-robin, First, Last, Source ou URI pour votre balancement d'IP| -|Suivi de session|Le suivi de session peut se faire par Cookie ou IP source, à définir ici| +|Suivi de session|Le suivi de session peut se faire par cookie ou IP Source, à définir ici| |Sonde|Choix et activation de la sonde| ### Gérer ses serveurs -Une fois votre ferme de serveurs créée il vous reste à y ajouter des serveurs. Ci-essous le détail des options ainsi que des options avancées: +Une fois votre ferme de serveurs créée, il vous reste à y ajouter des serveurs. Retrouvez ci-dessous le détail des options ainsi que des options avancées : -![Ajout de serveur](images/iplb-cluster-add-server.png){.thumbnail} -![Ajout de serveur](images/iplb-cluster-add-server-1.png){.thumbnail} -![Ajout de serveur](images/iplb-cluster-add-server-2.png){.thumbnail} +![Ajout serveur](images/add_server.png){.thumbnail} +![Ajout serveur](images/add_server_advanced.png){.thumbnail} |Élément|Fonction| |---|---| -|Nom|Si vous le souhaitez, vous pouvez nommer votre serveur; ceci est très utile quand vous en avez plusieurs afin de les identifier rapidement| +|Nom|Si vous le souhaitez, vous pouvez nommer votre serveur, afin de l'identifier rapidement quand vous en avez plusieurs| |Adresse IPv4|Ajout de l'IP du service qui agira comme serveur| |Port|Port du serveur| |Serveur de secours|Préciser que ce serveur est un serveur de secours| @@ -92,32 +91,35 @@ Une fois votre ferme de serveurs créée il vous reste à y ajouter des serveurs |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 PROXY|**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 -Il est possible d'ajouter un SSL au Répartiteur de charge dans la section `Certificat SSL`{.action}. Vous aurez alors deux possibilités: commander un certificat SSL via OVH ou ajouter un certificat externe. +Il est possible d'ajouter un SSL au Load Balancer depuis l'onglet `Certificats SSL`{.action}. Vous aurez alors deux possibilités : commander un certificat SSL via OVHcloud ou ajouter un certificat externe. -#### Certificat SSL OVH +#### Certificat SSL OVHcloud -Pour commander un certificat SSL il suffit d'aller dans la section `Certificat SSL`{.action} puis de cliquer sur `Commander un certificat SSL`{.action} et de vous laisser guider: +Pour commander un certificat SSL, sélectionnez l'onglet `Certificat SSL`{.action} puis cliquez sur `Commander un certificat SSL`{.action}. -![Commande d'un certificat SSL](images/iplb-order-ssl.png){.thumbnail} +![Commande d'un certificat SSL](images/ordering_ssl.png){.thumbnail} |Élément|Fonction| |---|---| +|Nom|Si vous le souhaitez, vous pouvez nommer votre certificat, afin de l'identifier rapidement quand vous en avez plusieurs| |Type de certificat|Gratuit (Let's Encrypt), Comodo DV ou Comodo EV (Pour plus de détails, [consultez cette page](/links/web/hosting-options-ssl))| |Fully Qualified Domain Name (FQDN)|Le(s) domaine(s) concerné(s)| #### Ajout d'un certificat SSL externe -Si vous possédez déjà votre propre certificat SSL, il vous est possible de l'ajouter directement: +Si vous possédez déjà votre propre certificat SSL, il vous est possible de l'ajouter directement : -![Ajout d'un certificat SSL](images/iplb-add-ssl.png){.thumbnail} +![Ajout d'un certificat SSL](images/external_ssl-00.png){.thumbnail} +![Ajout d'un certificat SSL](images/external_ssl.png){.thumbnail} |Élément|Fonction| |---|---| -|Nom|Choisssez si vous le souhaitez un nom à votre certificat, très utile quand vous en avez plusieurs afin de les identifier rapidement| -|Clé privée|Champ d'ajout de la clef privée à ajouter au service| +|Nom|Choisissez si vous le souhaitez un nom à votre certificat, afin de l'identifier rapidement quand vous en avez plusieurs| +|Clef privée|Champ d'ajout de la clef privée à ajouter au service| |Certificat|Champ d'ajout du certificat| |Chaîne|Champ d'ajout du certificat racine si nécessaire| 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 8272ae49e94..7624aa5fce4 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-30 --- ## 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 toutes les zones de disponibilité 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 PROXY|**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 diff --git a/pages/network/load_balancer/use-lb/guide.it-it.md b/pages/network/load_balancer/use-lb/guide.it-it.md index b33e08e412d..6b84573fa49 100644 --- a/pages/network/load_balancer/use-lb/guide.it-it.md +++ b/pages/network/load_balancer/use-lb/guide.it-it.md @@ -1,7 +1,7 @@ --- title: Gestire il Load Balancer dallo Spazio Cliente OVH excerpt: Principali funzionalità e gestione del servizio Load Balancer dallo Spazio Cliente OVH -updated: 2017-12-01 +updated: 2025-07-30 --- ## Obiettivo @@ -11,7 +11,7 @@ Questa guida ti mostra come utilizzare il Load Balancer e presenta le principali ## Prerequisiti - Avere accesso allo Spazio Cliente OVH -- Disporre di un [Load Balancer](https://www.ovh.it/soluzioni/ip-load-balancing/){.external} attivo +- Disporre di un [Load Balancer](/links/network/load-balancer) attivo ## Procedura @@ -28,8 +28,8 @@ In questa interfaccia sono disponibili le seguenti informazioni: |Stato|Riepilogo delle informazioni relative al tuo Load Balancer: nome del servizio, frontend, server farm attive e server aggiunti| |Utilizzo|Riepilogo dei dati relativi ai consumi del tuo Load Balancer| |Grafici|Grafici associati al tuo servizio, elaborati in base alle connessioni simultanee o al numero di richieste al minuto| -|Informazioni|IPv4 e Additional IP associati e numero di IPv4 di uscita (per visualizzare i dettagli, clicca sui tre puntini di sospensione)| -|Configurazione|Sezione in cui è possibile personalizzare il nome del tuo servizio (che verrà visualizzato in alto e nella colonna di sinistra), i Cipher e il datacenter in cui è localizzato il Load Balancer | +|Informazioni|I tuoi indirizzi IPv4 e IPv6 e gli Additional IP associati, e il numero di IPv4 di uscita (ottieni i dettagli cliccando sul pulsante `...`{.action})| +|Configurazione|Personalizza qui il nome della tua offerta. Trova anche i cipher, che sono personalizzabili, e la zona di disponibilità in cui si trova il tuo Load Balancer| |Abbonamento|Sezione in cui vengono mostrati i dettagli amministrativi del servizio| Per aggiungere `Frontend`{.action} e `Server Farm`{.action}, è sufficiente cliccare sul pulsante corrispondente: un form ti guiderà nella configurazione. @@ -47,7 +47,7 @@ Ecco gli elementi del frontend: |Nome|È possibile assegnare un nome al tuo frontend per identificarlo più facilmente| |Protocollo|Puoi scegliere tra HTTP, HTTPS, TCP, TCP SSL (TLS) e UDP| |Porta|Scegli la porta da utilizzare| -|Datacenter|Scegli un datacenter o seleziona “Tutti”| +|Datacenter|È possibile scegliere tra una zona di disponibilità specifica o tutte le zone di disponibilità per la creazione del front-end| |Farm predefinita|Se hai configurato più farm, puoi sceglierne una predefinita per ogni frontend| Inoltre, hai accesso alle opzioni avanzate @@ -62,6 +62,7 @@ Inoltre, hai accesso alle opzioni avanzate |Header HTTP|Aggiunta di un header HTTP| ### Gestisci le server farm + Per aggiungere una server farm, seleziona la scheda `Server Farm`{.action} e clicca su `Aggiungi una Server Farm`{.action}. Le opzioni principali disponibili sono le stesse del frontend. Le opzioni avanzate sono invece differenti: ![Aggiungi una Server Farm](images/advanced_cluster.png){.thumbnail} @@ -90,6 +91,7 @@ Una volta creata la farm, non ti resta che aggiungervi dei server. Di seguito, i |Cookie|Aggiunta di un cookie di sessione personalizzato| |Catena di certificazione|Aggiunta di una catena di certificazione| |Peso di bilanciamento|Scelta del peso di bilanciamento per la ripartizione del carico| +|Versione protocollo PROXY|**Solo se è già stato configurato**, scegliere la versione del protocollo PROXY da utilizzare su questo server.
Per maggiori informazioni sul protocollo PROXY e sul suo utilizzo con il servizio OVHcloud Load Balancer, consulta [questa guida](/pages/network/load_balancer/create_proxyprotocol/).| ### Gestisci i certificati SSL @@ -122,4 +124,4 @@ Se hai già attivato il tuo certificato SSL, è possibile aggiungerlo direttamen ## Per saperne di più -Contatta la nostra Community di utenti all’indirizzo . \ No newline at end of file +Contatta la nostra [Community di utenti](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.pl-pl.md b/pages/network/load_balancer/use-lb/guide.pl-pl.md index be439595033..7d8aceecb59 100644 --- a/pages/network/load_balancer/use-lb/guide.pl-pl.md +++ b/pages/network/load_balancer/use-lb/guide.pl-pl.md @@ -1,7 +1,7 @@ --- title: Zarządzanie usługą Load Balancer z Panelu klienta excerpt: Podsumowanie najważniejszych funkcji i rozpoczęcie korzystania z usługi Load Balancer z Panelu klienta -updated: 2018-01-12 +updated: 2025-07-30 --- ## Wprowadzenie @@ -27,8 +27,8 @@ Na stronie głównej znajdują się następujące informacje: |Status|Podsumowanie usługi Load Balancer zawierające adres IP, front-endy, farmy serwerów oraz dodane serwery| |Zużycie|Raport o wykorzystanym przesyle danych LoadBalancer| |Wykresy|Tu znajdują się wykresy dotyczące usługi pokazujące ilość jednoczesnych logowań lub ilość żądań na minutę| -|Informacje|Twoje IPv4 i powiązane adresy Additional IP oraz ilość IPv4 wyjściowych (szczegóły po kliknięciu wielokropka)| -|Konfiguracja|Tu możesz nadać swojej usłudze własną nazwę (która pojawi się u góry w lewej kolumnie), ustawić szyfrowanie oraz określić centrum danych, w którym znajduje się Twój Load Balancer| +|Informacje|Twoje adresy IPv4 i IPv6 oraz powiązane z nimi dodatkowe adresy IP, a także liczba wychodzących adresów IPv4 (więcej informacji kliknij przycisk `...`{.action})| +|Konfiguracja|W tym miejscu możesz spersonalizować nazwę usługi (która będzie widoczna na górze po lewej stronie). Spersonalizowane są algorytmy oraz strefa dostępności, w której znajduje się Load Balancer| |Abonament|Tu znajdują się szczegóły administracyjne Twojej oferty| W celu dodania `Front-endu`{.action} lub `Farmy serwerów`{.action}, należy po prostu kliknąć odpowiedni przycisk, po czym kontekstowe menu pomoże Ci skonfigurować poszczególne elementy usługi. @@ -46,7 +46,7 @@ Szczegóły elementów front-endu: |Nazwa|Zdecyduj czy chcesz nadać front-endowi nazwę, co może przydać się do szybkiej identyfikacji, jeśli ma się ich kilka| |Protokół|Możesz wybrać spośród HTTP, HTTPS, TCP, SSL TCP (lub TLS) oraz UDP| |Port|Tu wybierz port nasłuchu, którego będziesz używać| -|Datacenter|Wybór pomiędzy tylko swoim lub wszystkimi centrami danych przy tworzeniu front-endu| +|Datacenter||Wybierz strefę lub wszystkie strefy dostępności, aby utworzyć front-end| |Farma domyślna|Jeśli masz kilka skonfigurowanych farm serwerów, możesz wskazać domyślną farmę dla każdego front-endu| Masz również dostęp do ustawień zaawansowanych: @@ -90,6 +90,7 @@ Po utworzeniu farmy serwerów pozostaje dodać do niej serwery (poniżej przedst |Cookie|Dodanie indywidualnego pliku cookie sesji| |Łańcuch certyfikatu|Dodanie łańcucha certyfikatu SSL| |Waga (weight) równoważenia|Wybór wagi (weight) na potrzeby równoważenia obciążenia| +|Wersja protokołu PROXY|**Tylko jeśli jest już skonfigurowana**, wybierz wersję protokołu PROXY, której chcesz używać na tym serwerze.
Więcej informacji na temat protokołu PROXY i korzystania z niego z usługą Load Balancer można znaleźć w [tym przewodniku](/pages/network/load_balancer/create_proxyprotocol/).| ### Zarządzanie certyfikatami SSL @@ -122,4 +123,4 @@ Jeśli masz już swój certyfikat SSL, masz możliwość dodania go bezpośredni ## Sprawdź również -Przyłącz się do społeczności naszych użytkowników na stronie . \ No newline at end of file +Dołącz do [grona naszych użytkowników](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/use-lb/guide.pt-pt.md b/pages/network/load_balancer/use-lb/guide.pt-pt.md index 5ac328bfcab..7e67add21a3 100644 --- a/pages/network/load_balancer/use-lb/guide.pt-pt.md +++ b/pages/network/load_balancer/use-lb/guide.pt-pt.md @@ -1,7 +1,7 @@ --- title: Gestão do serviço Load Balancer através da Área de Cliente excerpt: Resumo das funções principais e utilização inicial do serviço Load Balancer através da Área de Cliente -updated: 2018-01-12 +updated: 2025-07-30 --- ## Objetivo @@ -28,8 +28,8 @@ Nesta página principal serão apresentadas as seguintes informações: |Estado|Resumo do Load Balancer com IP, Frontends, Farms ativas e servidores adicionados| |Utilização|Resumo da utilização do Load Balancer| |Gráficos|Gráficos associados à atividade do serviço em termos de ligações simultâneas ou de pedidos de ligação por minuto| -|Informações|Detalhes sobre os IPv4 e Additional IP associados, e sobre o número do IPv4 de saída (para ver mais info, clique nos três pontos)| -|Configuração|Opções de personalização do nome da oferta (visível em cima e na coluna à esquerda), da(s) cipher(s), do datacenter do Load Balancer| +|Information|Os seus endereços IPv4 e IPv6, os IPs suplementares a eles associados, bem como o número de IPv4 de saída (para mais informações, clique no botão `...`{.action})| +|Configuração|Aqui, pode personalizar o nome da sua solução (que surgirá no topo da coluna da esquerda). As cifras são personalizáveis, assim como a zona de disponibilidade onde o seu Load Balancer está baseado| |Subscrição|Detalhes administrativos do serviço| Para adicionar `Frontends`{.action} ou `Server Farms`{.action}, clique nos respetivos botões. Será apresentado um menu para auxiliar na configuração daqueles componentes do serviço. @@ -47,7 +47,7 @@ Detalhes dos Elementos de um Frontend |Nome|Opção que permite atribuir um nome ao frontend, para facilitar a sua identificação| |Protocolo|Selecione entre HTTP, HTTPS, TCP, SSL TCP (ou TLS) e UDP| |Porta|Selecione a porta de escuta| -|Datacenter|Pode optar pelo seu datacenter ou por todos quando criar o Frontend| +|Datacenter|Pode escolher entre uma zona de disponibilidade em particular ou todas as zonas de disponibilidade para a criação do Frontend| |Farm predefinida|Se tiver várias Farms configuradas, pode predefinir uma para cada Frontend| A gestão dos Frontends tem opções de configuração avançada. @@ -89,6 +89,7 @@ Depois de criada a Server Farm, só falta adicionar os servidores (veja abaixo o |Cookie|Adicione um cookie de sessão personalizada| |Cadeia de certificação|Adicione uma cadeia de certificação| |Peso do balanceamento|Seleção do peso de balanceamento para a repartição da carga| +|Versão do protocolo PROXY|**Unicamente se já o configurou**, escolha a versão do protocolo PROXY que pretende utilizar neste servidor.
Pode encontrar mais informações sobre o protocolo PROXY e sobre a sua utilização com o serviço OVHcloud Load Balancer em [este manual](/pages/network/load_balancer/create_proxyprotocol/).| ### Gestão dos Certificados SSL Pode adicionar um SSL ao Load Balancer na secção `Certificado SSL`{.action}. Aqui tem duas opções: solicitar um certificado SSL da OVH ou adicionar um certificado externo. @@ -118,4 +119,4 @@ Se já tem um certificado SSL, este pode ser associado ao serviço: ## Quer saber mais? -Troque impressões com a nossa comunidade em . \ No newline at end of file +Fale com a nossa [comunidade de utilizadores](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/zones/guide.en-asia.md b/pages/network/load_balancer/zones/guide.en-asia.md index e91a32ce875..7b7d18bfbb6 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-30 --- ## Introduction @@ -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](/links/manager). In the `Bare Metal Cloud`{.action} section, click `Network`{.action}, 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 @@ -68,13 +102,17 @@ 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 + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/zones/guide.en-au.md b/pages/network/load_balancer/zones/guide.en-au.md index e91a32ce875..7b7d18bfbb6 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-30 --- ## Introduction @@ -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](/links/manager). In the `Bare Metal Cloud`{.action} section, click `Network`{.action}, 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 @@ -68,13 +102,17 @@ 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 + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/zones/guide.en-ca.md b/pages/network/load_balancer/zones/guide.en-ca.md index e91a32ce875..7b7d18bfbb6 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-30 --- ## Introduction @@ -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](/links/manager). In the `Bare Metal Cloud`{.action} section, click `Network`{.action}, 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 @@ -68,13 +102,17 @@ 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 + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/zones/guide.en-gb.md b/pages/network/load_balancer/zones/guide.en-gb.md index e91a32ce875..7b7d18bfbb6 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-30 --- ## Introduction @@ -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](/links/manager). In the `Bare Metal Cloud`{.action} section, click `Network`{.action}, 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 @@ -68,13 +102,17 @@ 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 + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/zones/guide.en-sg.md b/pages/network/load_balancer/zones/guide.en-sg.md index e91a32ce875..7b7d18bfbb6 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-30 --- ## Introduction @@ -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](/links/manager). In the `Bare Metal Cloud`{.action} section, click `Network`{.action}, 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 @@ -68,13 +102,17 @@ 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 + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/zones/guide.en-us.md b/pages/network/load_balancer/zones/guide.en-us.md index e91a32ce875..7b7d18bfbb6 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-30 --- ## Introduction @@ -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](/links/manager). In the `Bare Metal Cloud`{.action} section, click `Network`{.action}, 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 @@ -68,13 +102,17 @@ 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 + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/zones/guide.fr-ca.md b/pages/network/load_balancer/zones/guide.fr-ca.md index 3f04e25bdeb..8253e4f8d6f 100644 --- a/pages/network/load_balancer/zones/guide.fr-ca.md +++ b/pages/network/load_balancer/zones/guide.fr-ca.md @@ -1,80 +1,128 @@ --- -title: Travailler avec les zones -excerpt: Utilisez les zones afin d'augmenter la disponibilité et diminuer la latence -updated: 2022-04-04 +title: "Configurer un service OVHcloud Load Balancer avec les zones" +excerpt: "Utilisez les zones afin d'augmenter la disponibilité et diminuer la latence" +updated: 2025-07-30 --- -## Introduction +## Objectif -Le service OVH Load Balancer est localisé dans une ou plusieurs zone(s) de disponibilité, -définie(s) lors de la souscription au service. +Le service OVHcloud Load Balancer est localisé dans une ou plusieurs zone(s) de disponibilité, définie(s) lors de la souscription au service. -Vous avez la possibilité de commander des zones supplémentaires pour votre service. +Vous pouvez commander des zones supplémentaires pour votre service. Vous augmentez ainsi la disponibilité de votre service Load Balancer en cas d'indisponibilité d'une zone. -Il est également possible, si configuré de façon appropriée, d'utiliser plusieurs zones afin de minimiser la latence pour vos visiteurs. +Via une configuration adéquate, vous pouvez également utiliser plusieurs zones afin de minimiser la latence pour vos visiteurs. -## Ajouter une zone +**Découvrez comment commander et gérer des zones supplémentaires.** -### Depuis l'API +## Prérequis -Pour commander une zone via l'API, vous devez tout d'abord créer un panier ("cart") +- Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. +- Être connecté à votre [espace client OVHcloud](/links/manager). +- Être connecté à l'[API OVHcloud](/links/api). + +## En pratique + +### Commander une zone supplémentaire + +#### Depuis l'espace client OVHcloud + +Vous pouvez commander une zone supplémentaire depuis l'[espace client OVHcloud](/links/manager). Dans la partie `Bare Metal Cloud`{.action}, cliquez sur `Network`{.action} puis sur `Load Balancer`{.action}. + +Sélectionnez votre Load Balancer puis, dans l'onglet `Accueil`{.action} et le menu `Configuration`{.action}, cliquez sur `Ajouter`{.action} dans la partie « Zones de disponibilité ». + +![Ajouter une zone load balancer depuis le manager](images/add_Zone_IPLB.png){.thumbnail} + +Sélectionnez alors le(s) zone(s) que vous souhaitez commander et cliquez sur `Ajouter`{.action}. + +![Selection d'une zone load balancer depuis le manager](images/Select_Zone_IPLB.png){.thumbnail} + +Un bon de commande est généré, il vous faudra le régler. + +![Payer la commande zone load balancer depuis le manager](images/Paybill_Zone_IPLB.png){.thumbnail} + +#### Depuis l'API OVHcloud + +Pour commander une zone via l'API, vous devez tout d'abord créer un panier (*cart*) > [!api] > > @api {v1} /order POST /order/cart > -Veuillez noter le numéro du panier ("cart"), il vous sera utile pour la suite. +Veuillez noter le numéro du panier (*cart*), il vous sera utile pour la suite. -Puis vous l'assigner via +Assignez-vous le panier via l'appel suivant : > [!api] > > @api {v1} /order POST /order/cart/{cartId}/assign > -Vous pouvez lister les options disponibles sur votre service Load Balancer via +Vous pouvez lister les options disponibles sur votre service Load Balancer via : > [!api] > > @api {v1} /order GET /order/cartServiceOption/ipLoadbalancing/{serviceName} > -Quand vous avez trouvé l'option correspondant à la zone souhaitée, vous pouvez l'ajouter à votre panier ("cart") via +Quand vous avez trouvé l'option correspondant à la zone souhaitée, vous pouvez l'ajouter à votre panier (*cart*) via : > [!api] > > @api {v1} /order POST /order/cartServiceOption/ipLoadbalancing/{serviceName} > -Enfin, vous pouvez valider votre panier ("cart") via +Enfin, vous pouvez valider votre panier (*cart*) via : > [!api] > @api {v1} /order POST /order/cart/{cartId}/checkout > -N'oubliez pas de payer le bon de commande ainsi généré. +N'oubliez pas de régler le bon de commande ainsi généré. -## Utiliser plusieurs zones +### Ajouter une zone -### Pour la haute disponibilité +Une fois que la commande de votre zone est finalisée, vous pouvez l'ajouter depuis votre espace client OVHcloud. -Si vous voulez utiliser plusieurs zones afin d'obtenir une haute disponibilité, vous pouvez utiliser la zone spéciale `all` lorsque vous déclarez un `frontend` et une `farm`. +Sélectionnez le Load Balancer que vous souhaitez modifier puis créez un nouveau frontend, ou éditez-en un existant, via l'onglet `Frontends`{.action} -Cette zone spéciale `all` va permettre de déployer la même configuration sur toutes les zones souscrites sur votre service Load Balancer, et vous évite de dupliquer la configuration pour toutes les zones. +Dans le champ `Datacenter`{.action}, choisissez la zone que vous souhaitez associer à votre frontend. -### Pour réduire la latence +![Choix de la zone](images/Select-Datacenter.png){.thumbnail} -Si le but est de réduire la latence, on peut imaginer diriger les requêtes venant depuis le load balancer de la zone1 vers des serveurs backends proches géographiquement de cette zone1, et similairement, diriger les requêtes venant depuis le load balancer de la zone2 vers des serveurs backends proches de la zone2. +Une fois le frontend configuré, cliquez sur `Ajouter`{.action} ou `Modifier`{.action} selon que vous configurez un nouveau frontend ou un frontend existant. -Pour réaliser cela, il faut spécifier un frontend dans chaque zone qui utilise une farm dans la même zone. -Cela va nous permettre de déclarer les serveurs backends dans des farms différentes par zone et de controler les serveurs backends utilisés en fonction de la zone. +N'oubliez pas de déployer la configuration. Pour ce faire, dans le bandeau de rappel vous précisant que la configuration n'est pas appliquée, cliquez sur `Appliquer la configuration`{.action}. + +![Application d'une Configuration d'un Load Balancer](images/apply-configuration.PNG){.thumbnail} + +### Utiliser plusieurs zones + +#### Pour la haute disponibilité + +Si vous voulez utiliser plusieurs zones afin d'obtenir une haute disponibilité, vous pouvez utiliser la valeur `Tous (ALL)` lorsque vous déclarez un frontend ou une ferme de serveurs. + +![utiliser plusieurs zones](images/Edit-frontend-All-iplb.png){.thumbnail} + +Cette valeur spéciale `Tous (ALL)` va permettre de déployer la même configuration sur toutes les zones souscrites sur votre service Load Balancer, et vous évite de dupliquer la configuration pour toutes les zones. + +#### Pour réduire la latence + +Si le but est de réduire la latence, vous pouvez diriger les requêtes venant depuis le load balancer de la zone1 vers des serveurs backends proches géographiquement de cette zone1.
+De façon similaire, vous pouvez diriger les requêtes venant depuis le load balancer de la zone2 vers des serveurs backends proches de la zone2. + +Afin de réaliser cela, il vous faut spécifier un frontend dans chaque zone qui utilise une ferme dans la même zone.
+Cela va vous permettre de déclarer les serveurs backends dans des fermes différentes par zone et de contrôler les serveurs backends utilisés en fonction de la zone. ![Fonctionnement avec plusieurs zones et plusieurs fermes](images/multi_zones_multi_backends.png){.thumbnail} -Par example, si on a des serveurs backends dans les datacentres de Gravelines (gra) et Beauharnois (bhs), -on peut commander un service Load Balancer dans les zones `gra` et `bhs` et configurer : +Par exemple, si vous avez des serveurs backends dans les datacentres de Gravelines (gra) et Beauharnois (bhs), +vous pouvez commander un service Load Balancer dans les zones `gra` et `bhs` et configurer : + +- un frontend dans la zone gra avec une ferme (farm) par défaut dans la zone gra qui contient des serveurs dans le datacentre de Gravelines; +- un frontend dans la zone bhs avec une ferme (farm) par défaut dans la zone bhs qui contient des serveurs dans le datacentre de Beauharnois. + +## Aller plus loin -- un frontend dans la zone gra avec comme ferme (farm) par défaut dans la zone gra qui contient des serveurs dans le datacentre de Gravelines -- un frontend dans la zone bhs avec comme ferme (farm) par défaut dans la zone bhs qui contient des serveurs dans le datacentre de Beauharnois +Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/zones/guide.fr-fr.md b/pages/network/load_balancer/zones/guide.fr-fr.md index 3c441358bfa..d4db7cf2999 100644 --- a/pages/network/load_balancer/zones/guide.fr-fr.md +++ b/pages/network/load_balancer/zones/guide.fr-fr.md @@ -27,7 +27,7 @@ Via une configuration adéquate, vous pouvez également utiliser plusieurs zones #### Depuis l'espace client OVHcloud -Vous pouvez commander une zone supplémentaire depuis l'[espace client OVHcloud](/links/manager) dans la partie `Bare Metal Cloud`{.action}, puis `Load Balancer`{.action}. +Vous pouvez commander une zone supplémentaire depuis l'[espace client OVHcloud](/links/manager). Dans la partie `Bare Metal Cloud`{.action}, cliquez sur `Network`{.action} puis sur `Load Balancer`{.action}. Sélectionnez votre Load Balancer puis, dans l'onglet `Accueil`{.action} et le menu `Configuration`{.action}, cliquez sur `Ajouter`{.action} dans la partie « Zones de disponibilité ». @@ -125,4 +125,4 @@ vous pouvez commander un service Load Balancer dans les zones `gra` et `bhs` et ## 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